OA68127: $HASP095 JES2 CATASTROPHIC ABEND. CODE = S0C9 (RC = 00000009) AFTER ATTEMPTING TO $ACTIVATE,LEVEL=Z32

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• At JES2 V3R2, there is a new checkpoint level - z32.  While
  running in the previous z22 mode on V3R2, a $DACTIVATE command
  will show that JES2 is ready to move to the new z32 level.
  However, after issuing the activate with $ACTIVATE,LEVEL=Z32 an
  ABEND 0C9 will occur in JES2, leading to a catastrophic error
  bringing down JES2.
  
  
  Attempts to restart JES2 using the UNACT parm to move back to
  z22 level may result in subsequent queue rebuild errors,
  including $Q14 and $IV8 error codes.
  
  
  Recovery after this may not be possible without a JES2 COLD
  start.
  
  
  KNOWN IMPACT:
  JES2 will not be able to hot or warm start. JES2 COLD start may
  be required - this will clear the current SPOOL and CKPT data.
  However, this may be the only recovery method.
  
  
  VERIFICATION STEPS:
  1. Running JES2 V3R2
  2. $DACTIVATE shows that activation should succeed
  3. After $ACTIVATE,LEVEL=z32 is issued, JES2 takes ABEND 0C9
  4. Subsequent attempts to restart JES2 or UNACT back to z22 mode
  result in queue rebuild/verification errors such as $Q14 or $IV8
  

Local fix

• DO NOT $ACTIVATE to z32 checkpoint mode.  JES2 can operate at
  z/OS V3R2 at the previous checkpoint mode of z22, albeit with
  some new features unavailable.  Please remain on z22 mode until
  a fix for this issue is made available.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of HJE77F0.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Uninitialized fields after warm start   *
  *                      of z/OS 3.2 JES2 and a $ACTIVATE to     *
  *                      LEVEL=z32 results in ABEND0C9.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  JES2 warm start logic does not properly initialize fields
  when z/OS 3.2 JES2 (HJE77F0) is started and $ACTIVATEd to
  LEVEL=z32 checkpoint mode. Problems include:
  - ABENDS0C9 occurring in HASPNUC routine $CKPT due to
    $JQSSIZE being 0.
  - Switches to enable new z/OS 3.2 functions defaulting to
    enabled.
  - ABENDSDC2 occurring on a hot start due to an incorrect
    length passed into IARV64.
  - $IV8 $ERROR occurring while trying to warm start JES2 with
    PARM=UNACT to retro-activate to z22 mode.
  - $Q14 $ERROR occurring in $DOGJQE RETURN due to the
    mismatch of data for field JQETRAK_Z22.
  - $IX4 $ERROR occurring when attempting to use a poorly
    formatted DRX CTENT.
  

Problem conclusion

• TYPE/RESTART (WARM) IPL/REQUIRED (YES) CLPA (NO)
  
  The following logic was updated:
  - As part of $ACTIVATE command processing, the PSTACTIV
    routine was updated to properly initialize the $JQSSIZE
    field in the $HCT.
  - Initialization code has been updated to properly set
    the default switch values for new z/OS 3.2 functions.
  - On a non-hot start, the size of the CKPT I/O area will
    be saved and used when calling IARV64 on a hot start.
    This is why the APAR cannot be installed using a hot
    start.  Additionally, the definition of the new CKPT
    sections (CTENTs) has been updated to specify a MAXSIZE
    for the elements.
  - The $IV8 ABEND was caused by a job queue error created by
    the ABEND0C9.  To address this, the following changes were
    made:
  
      Before starting PARM=UNACT processing, a queue
      verification is done.  If it fails, a new $HASP4451 WTOR
      message is issued to determine if UNACTivate
      initialization should continue:
  
        $HASP4451 Queue error detected during UNACT processing.
        Reply "CONTINUE" to initialize JES2, "TERM" to shut
        down.
  
      If the reply is TERM, JES2 terminates with message:
        $HASP445 UNACTIVATE REQUEST FAILED, Queue verify failed
  
      If the reply is CONTINUE, UNACTivate processing is
      performed.  Another queue verify is performed, but any
      errors are ignored if the first queue verify failed.
  
      Warm start will continue as normal including detecting
      the queue validation error and a subsequent rebuild.
  - $DOGJQE code has been changed to properly track the
    original JQE value of field JQETRAK_Z22 so that valid
    error determination (Q14) can be made.
  - Field $DRIXPLN was not properly set in module HASPIRDA,
    due to an incorrect comparison instruction, leading to
    the poorly formatted DRX CTENT. This has been corrected.
  
  
  
  The information in the following JES2 manuals/publications
  is missing/incorrect:
  
  1.SA32-0989-70 z/OS 3.2 JES2 Messages            (for HJE77F0)
  
  In Chapter 8, "Four-hundreds", in the section for the $HASP445
  message, the following reason text needs to be added:
  
   Queue verify failed
    JES2 was started with PARM=UNACT to retro-activate. However,
    a queue error was encountered prior to performing the
    retro-activate.  A HASP4451 WTOR was issued to which a reply
    of TERMINATE was given.  JES2 initialization terminates.
  
  
  In Chapter 16, "Four-thousands", a new section for $HASP4451
   needs to be added:
  
   $HASP4451
   Explanation
  
    >>- Queue error detected during UNACT processing. Reply
        "CONTINUE" to initialize JES2, "TERM" to shut down. -><
  
    JES2 was started with PARM=UNACT to retro-activate. However,
    before the retro-activate function could start, a queue
    verify was done.  This verification detected a queue error.
    This queue error could cause the retro-activate to fail.
    It also will likely still exist after the retro-activate
    has completed, making it impossible to detect a retro-
    activate introduced queue error.
  
    It is always preferable to correct the queue error before
    attempting a retro-activate.  This can be done with either
    a warm/hot start without PARM=UNACT or using the $VERIFY
    command with REBUILD=COND.  In this case reply TERM.  JES2
    will terminate and can be restarted to correct the queue
    error.
  
    If it is not possible to correct the queue error, a reply
    of CONTINUE will proceed with the retro-activate function.
    One completed, normal warm start processing will do another
    queue verify and a rebuild if needed.
  
    Note that JES2 initialization processing does not update
    the checkpoint until initialization processing has
    completed.  This implies that, if a problem is encountered
    before initialization has completed, JES2 can be terminated
    without having altered the checkpoint data.
  
    System action
      JES2 waits for the operator to reply.
       CONTINUE
         JES2 will perform the retro-activate function and
         revert the checkpoint to the non-activated format.
         JES2 initialization will then proceed normally.
       TERM
         JES2 will issue the $HASP445 message and terminate.
  
    Operator response
      Notify the system programmer and reply CONTINUE or TERM
  
    System programmer response
      Attempt to start JES2 normally (without PARM=UNACT) to
      correct the queue error.  Use the $ACTIVATE command
      to retro-activate if successful.
      If the queue error cannot be resolved, reply CONTINUE
      to ignore queue errors and get JES2 started.
  
    Module
      HASPIRDA
    Routing code
      1,2,10,42
    Descriptor code
      2,7
  
  
  Searchable Keywords
   msgHASP445
   $HASP445
   msgHASP4451
   $HASP4451
   ABENDS0C9
   ABEND0C9
   ABENDSDC2
   ABENDDC2
  
  
  APAR OA68127 prereq's (and sup's) for FMID HJE77F0:
  Pre's: FA68030
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UJ97695

Modules/Macros

• $HASPEQU $SCID    HASMSCID HASPDREP HASPIRDA HASPJQS  HASPMSG
  HASPSERV HASPSXCK HASPXEQ
  

Fix information

• Fixed component name

  JES2

• Fixed component ID

  5752SC1BH

Applicable component levels

• R7F0 PSY UJ97695

     UP25/07/30 P F507 ¢

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.