JES2 console messages during initialization

As soon as JES2 is started, the SPECIFY OPTIONS message is issued to the operator. The operator then specifies the COLD parameter (or FORMAT) option.

A cold start results in the initialization of all JES2 job and output queues. During the spool processing for cold start, JES2 examines all spool volumes that are online to determine if each is formatted; any unformatted spool volume is formatted at this time.

If COLD (or FORMAT) is not specified, JES2 will issue the following series of messages:

$HASP479 UNABLE TO OBTAIN CKPT DATA SET LOCK
$HASP454 SHOULD JES2 BYPASS THE MULTI-MEMBER
INTEGRITY LOCK?

Reply ‘Y’ to this message, and then JES2 issues the following messages:

 $HASP478 CONFIRM INITIAL CHECKPOINT READ FROM CKPTn
 $HASP434 INVALID CHECKPOINT RECORD ON CKPTn DATASET
 $HASP285 JES2 CHECKPOINT RECONFIGURATION IN PROGRESS
 $HASP289 CKPT1 AND/OR CKPT2 SPECIFICATIONS ARE REQUIRED
 $HASP272 ENTER RESPONSE

Reply ‘TERM’ to the $HASP289/272 message pair. You will then have to restart JES2. Be certain to specify COLD (or FORMAT) when you again receive the $HASP426 SPECIFY OPTIONS message.

If any of your checkpoint data sets reside on Coupling facility structures rather than on DASD, JES2 issues the following message to verify the XCF connection, the JES2 XCF group name for your multi-access spool (MAS), and the name of the JES2 member that belongs to the JES2 XCF group:

 IXZ0001I CONNECTION TO JESXCF COMPONENT ESTABLISHED,
          GROUP WSC      MEMBER WSC$SY01

For more information about how JES2 XCF groups are defined, see Defining JES2 to the cross-system coupling facility (XCF).

Regardless of where your checkpoint data sets reside, JES2 provides an informational message to display the size of the checkpoint that was determined from your initialization data set values. After receiving the checkpoint data set information, you must confirm that initialization should continue by responding ‘Y’ to the $HASP441 message. For example:

$HASP537 THE CURRENT CHECKPOINT USES 43 4K RECORDS
$HASP436 CONFIRM COLD START ON
 CKPT1 - STRNAME=J2WRKCKPT1
 CKPT2 - STRNAME=J2WRKCKPT2
 SPOOL - PREFIX=J2WRK  DSN=SYS2.HASPACE
 03 $HASP441 REPLY 'Y' TO CONTINUE INITIALIZATION OR 'N'
          TO TERMINATE IN RESPONSE
 $HASP478 INITIAL CHECKPOINT READ IS FROM CKPTn
          (STRNAME J2WRKCKPT1).

After you verify that JES2 should continue initialization, the member issues the following messages to start and format the JES2 address space:

$HASP493 JES2 COLD START IS IN PROGRESS
$HASP266 JES2 CKPT2 DATA SET IS BEING FORMATTED
$HASP267 JES2 CKPT2 DATA SET HAS BEEN SUCCESSFULLY FORMATTED
$HASP266 JES2 CKPT1 DATA SET IS BEING FORMATTED
$HASP267 JES2 CKPT1 DATA SET HAS BEEN SUCCESSFULLY FORMATTED
$HASP492 JES2 COLD START HAS COMPLETED

When initialization is complete, JES2 deletes the $HASP493 message and issues the $HASP492 COLD START HAS COMPLETED message.

When JES2 completes initialization, it either

Begins to process jobs automatically after the $HASP492 message
or
Waits for the operator to enter the $S command in response to the $HASP400 ENTER REQUESTS message.

JES2 issues the $HASP400 ENTER REQUESTS message if the PARM= keyword has been omitted from the S JES2 command and EXEC statement of the JES2 procedure.

A problem can occur if a JES2 spool volume (specified by the VOLUME= parameter on the SPOOLDEF initialization statement) is not mounted and ready when the primary JES2 member is started. At least one spool volume must be mounted because JES2 must have spool space available in order to process an MVS™ MOUNT command. In this situation, the operator must ready a spool volume and IPL again.

To be certain you have at least one spool volume available at all times, include an entry in the VATLSTxx parameter library member specifying at least one spool volume without suppressing the mount option. VATLST processing will then request that a volume be mounted during the IPL process. An example would be:

SPOOL1,0,2,3380

See z/OS MVS Initialization and Tuning Reference for more information about VATLSTxx member.