z/OS JES2 Messages
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$HASP479

z/OS JES2 Messages
SA32-0989-01

$HASP479

Explanation

Read syntax diagramSkip visual syntax diagram
>>-UNABLE TO OBTAIN CKPT DATA SET LOCK – ----------------------->

>--+-I/O ERROR-------------+-----------------------------------><
   +-MEMBER=--memname------+   
   +-MEMBER=INITIALIZATION-+   
   '-VALIDATION ERROR------'   

JES2 initialization processing was not able to obtain control of the checkpoint data set.
  • If I/O ERROR appears in the message text, an I/O error occurred on all defined checkpoint data sets while JES2 was attempting to obtain the checkpoint data set lock.
  • If MEMBER=memname appears in the message text, another member in the MAS configuration has abnormally ended without releasing the checkpoint data set lock.

    The member that has not released the lock is identified by memname.

  • If MEMBER=INITIALIZATION appears in the message text, a system failure occurred while the operating system was initializing a JES2 member in the configuration. The JES2 member that the operating system was initializing did not release the checkpoint data set lock.
  • If VALIDATION ERROR appears in the message text, the lock record was not in the correct format. Verify that the data set is a valid JES2 checkpoint.

If you are doing a cold start and using a new checkpoint data set, or if you are doing a all-members warm start, the system may issue this message as part of normal processing, in which case it does not indicate an error condition. This is also true when performing an all-members warm start and using the CKPTn option to restart JES2.

System action

JES2 issues message $HASP454.

Operator response

Respond to message $HASP454.

System programmer response

Determine why the checkpoint data set lock is not being released.

Module

HASPIRDA

Routing Code: 1,2,10

Descriptor Code: 2,7

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014