jes2 initiator failure

[mad13142000]

Help.
MVS is hanging.
I set commnd00 to force jes2 to format the spool. When I re-ipl the system, it is now dying.

IEA357I ERRORS IN IEAPAK00 LIST
  | IEA357I IGC0J05B INVALID - MODULE IGNORED
  | IEA357I IGG08101 INVALID - MODULE IGNORED
  | IEA357I IGG08102 INVALID - MODULE IGNORED
  | IEA357I IGG08103 INVALID - MODULE IGNORED
  | IEA357I IGG08104 INVALID - MODULE IGNORED
  | IEA357I IGC11110 INVALID - MODULE IGNORED
  | IEA357I IGC12110 INVALID - MODULE IGNORED

I get past the system parameters, it tells me
IEE360I SMF NOW RECORDING ON SYS1.MANY ON MVSRES TIME=13.50.00
IGF992I  MIH INIT COMPLETE, PRI=000300, SEC=000015
IEE307I START    DELIMITER ERROR
and then stops.
no jobs are starting, and I can't start anything, because there are no init running

00001 JOBS    00000 INITIATORS
BSPSETPF STARTING           V=V  S
00000 TIME SHARING USERS

How do I force jes2 to properly start? I can't re-edit the Commnd00 until I can get into MVS...

I got Jes2 to format -
$HASP493 JES2 COLD-START IS IN PROGRESS
$HASP423 HASP00 IS BEING FORMATTED
$HASP412 MAXIMUM OF 1   READER(S)  EXCEEDED
$HASP412 MAXIMUM OF 1   PUNCH(ES)  EXCEEDED
$HASP000 ID 1    T=**.** I=3600 $SI1-I4
$HASP400 ENTER REQUESTS

How do I get an init to properly fire off so I can run jobs?

[David Hale-2]

Issue a $S

$DI will show you the init. Structure

$SIx will start the one you want

 

From: H390-MVS@... [mailto:H390-MVS@...] On Behalf
Of mad13142000
Sent: Thursday, September 10, 2009 1:03 PM
To: H390-MVS@...
Subject: [H390-MVS] jes2 initiator failure

 

 

Help.
MVS is hanging.
I set commnd00 to force jes2 to format the spool. When I re-ipl the system,
it is now dying.

IEA357I ERRORS IN IEAPAK00 LIST
| IEA357I IGC0J05B INVALID - MODULE IGNORED
| IEA357I IGG08101 INVALID - MODULE IGNORED
| IEA357I IGG08102 INVALID - MODULE IGNORED
| IEA357I IGG08103 INVALID - MODULE IGNORED
| IEA357I IGG08104 INVALID - MODULE IGNORED
| IEA357I IGC11110 INVALID - MODULE IGNORED
| IEA357I IGC12110 INVALID - MODULE IGNORED

I get past the system parameters, it tells me
IEE360I SMF NOW RECORDING ON SYS1.MANY ON MVSRES TIME=13.50.00
IGF992I MIH INIT COMPLETE, PRI=000300, SEC=000015
IEE307I START DELIMITER ERROR
and then stops.
no jobs are starting, and I can't start anything, because there are no init
running

00001 JOBS 00000 INITIATORS
BSPSETPF STARTING V=V S
00000 TIME SHARING USERS

How do I force jes2 to properly start? I can't re-edit the Commnd00 until I
can get into MVS...

I got Jes2 to format -
$HASP493 JES2 COLD-START IS IN PROGRESS
$HASP423 HASP00 IS BEING FORMATTED
$HASP412 MAXIMUM OF 1 READER(S) EXCEEDED
$HASP412 MAXIMUM OF 1 PUNCH(ES) EXCEEDED
$HASP000 ID 1 T=**.** I=3600 $SI1-I4
$HASP400 ENTER REQUESTS

How do I get an init to properly fire off so I can run jobs?

[somitcw-2]

--- In H390-MVS@...,
 "mad13142000" <mad13142000@...> wrote:

> Help.
> MVS is hanging.
> I set commnd00 to force jes2 to format the spool.
>When I re-ipl the system, it is now dying.
> IEA357I ERRORS IN IEAPAK00 LIST
> | IEA357I IGC0J05B INVALID - MODULE IGNORED
> | IEA357I IGG08101 INVALID - MODULE IGNORED
> | IEA357I IGG08102 INVALID - MODULE IGNORED
> | IEA357I IGG08103 INVALID - MODULE IGNORED
> | IEA357I IGG08104 INVALID - MODULE IGNORED
> | IEA357I IGC11110 INVALID - MODULE IGNORED
> | IEA357I IGC12110 INVALID - MODULE IGNORED

   Looks like SYS1.LPALIB on on your sys res is
damaged.  Did you allow a second copy of Hercules
to start and open a disk image before the first
copy had finished shutting down?  Is so, restoring
from back up would be a good thing to do.

> I get past the system parameters, it tells me
> IEE360I SMF NOW RECORDING ON SYS1.MANY ON MVSRES TIME=13.50.00
> IGF992I  MIH INIT COMPLETE, PRI=000300, SEC=000015
> IEE307I START    DELIMITER ERROR
> and then stops.

   Perhaps S JES2 or S JES2,,,FORMAT is mis-spelt?

   Enter s jes2 on the console.  If you use an
integreated console, it's /s jes2

> no jobs are starting, and I can't start anything,
>because there are no init running

   You should start jes2 before batch JOBs.

> 00001 JOBS    00000 INITIATORS
> BSPSETPF STARTING           V=V  S
> 00000 TIME SHARING USERS
> How do I force jes2 to properly start?

   s jes2 then reply format,noreq

   If you forget the noreq part, after JES2 starts,
enter $s

>I can't re-edit the Commnd00 until I can get into MVS...

   Why not?

   When running ZZSA, don't forget to change the
ARCHMODE from S/370 to something like ESAME

> I got Jes2 to format -
> $HASP493 JES2 COLD-START IS IN PROGRESS
> $HASP423 HASP00 IS BEING FORMATTED
> $HASP412 MAXIMUM OF 1   READER(S)  EXCEEDED
> $HASP412 MAXIMUM OF 1   PUNCH(ES)  EXCEEDED
> $HASP000 ID 1    T=**.** I=3600 $SI1-I4
> $HASP400 ENTER REQUESTS

   You need to enter $s after you receive:
$HASP400 ENTER REQUESTS

   R 00,format,noreq was missing noreq

> How do I get an init to properly fire off so I
>can run jobs?

$s

[Gerhard Postpischil]

mad13142000 wrote:
> I got Jes2 to format -
> $HASP493 JES2 COLD-START IS IN PROGRESS
> $HASP423 HASP00 IS BEING FORMATTED
> $HASP412 MAXIMUM OF 1   READER(S)  EXCEEDED
> $HASP412 MAXIMUM OF 1   PUNCH(ES)  EXCEEDED
> $HASP000 ID 1    T=**.** I=3600 $SI1-I4
> $HASP400 ENTER REQUESTS

At that point you may issue console commands:

S NET    (starts VTAM; wait a minute)

S TSO    (should give you TSO sessions to log in)

$SI      (start initiators to run batch jobs)

You may also try to correct the error in COMMND00 by using the
ZZSA stand-alone program (you should have a conf file for this).
I've never had to use it...

The other thing you've learned the hard way is never to make a
system change that you can't recover from. There are several
ways of doing this:  maintain parallel members (e.g., IEASYS88,
COMMND88, JES2BACK, etc.) and set it up so you can load (most
of) the system by specifying CLPA,SYSP=88 (or what-ever) to load
the recovery version. Another option is to generate a second
system pack (small catalog, small spool, etc.) to IPL from. The
brute force method is to make a host system (Windows, linux,
or?) copy of the MVSRES, MVSCAT, etc. file just before making
the change (make sure to copy the shadow files too, if there are
any for those packs). That allows you to test things and recover
by either switching the files back, or having a second .conf
file pointing to the backups.




Gerhard Postpischil
Bradford, VT

[mad13142000]

Thanks guys. I got it back, working fine...

[Wayne Bickerdike]

Please tell us what you did. Other people can learn from the answer.

Thankyou.

On Fri, Sep 11, 2009 at 4:32 AM, mad13142000 <mad13142000@...> wrote:

>
>
> Thanks guys. I got it back, working fine...
>
>  
>



--
Wayne V. Bickerdike