OA55008: JES2 SHUTDOWN HANG USING $PJES2 OR $PJES2,TERM

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During a JES2 shutdown (using $PJES2 or $PJES2,TERM) the
  susbsystem can appear to "hang" and shutdown does not complete.
  
  A console dump taken at this time will show the XEQ PCE is in a
  $WAIT in HASPXEQ near label X$PWSPN. This code path is entered
  after checking for the x'20' bit in $HCT flag EXECFG1. This bit
  indicates that the EDS PCE is still processing.
  
  Checking the EDS PCE, we see that it is in a $WAIT near label
  ECAMTWT. This $WAIT is performed during EDS ASID creation
  (EDSCRT) processing as we wait for the root task response.
  
  This means that the EDS ASID was never able to fully initialize
  and the EDS PCE will be stuck in this $WAIT. Later, when $PJES2
  is used, the EDS PCE can not turn off the x'20' bit in EXECFG1,
  leading to a $WAIT in XEQ PCE, and thus $PJES2 cannot complete.
  
  One reason for EDSCRT processing to fail in this way is if
  access violations occur during EDS initialization. Possible
  messages can include:
  
  IRR812I PROFILE *.* (G) IN THE STARTED CLASS WAS USED
          TO START JES2EDS WITH JOBNAME JES2EDS.
  ICH408I USER(STCDFLT ) GROUP($STCDFLT) NAME(DEFAULT    )
    IEFVH1   CL(PROGRAM )
    INSUFFICIENT ACCESS AUTHORITY
    FROM ** (G)
    ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   )
  CSV028I ABEND306-30  JOBNAME=MSTJCL00  STEPNAME=RACF
  
  VERIFICATION STEPS:
  1. $PJES2 or $PJES2,TERM is issued.
  2. $HASP607 JES2 NOT DORMANT message is issued; shut down does
     not complete.
  3. A dump of JES2 taken at this stage should show the following:
     - XEQ PCE is currently in a $WAIT in HASPXEQ waiting for EDS
       and SPIN processing to complete
     - EDS PCE is currently in a $WAIT in EDCSRT routine waiting
       for response to ASID creation
     - Checking SYSLOG around the time stamp on the call to
       EDSCRT from the EDS PCE should reveal some type of security
       authorization error, or other reason for the ASID creation
       to fail.
  

Local fix

• Grant the necessary accesses to JES2EDS.
  
  If you are in the hang condition, use $PJES2,ABEND to complete
  shut down.
  
  On subsequent start of JES2, the JES2EDS ASID will initialize
  properly. $PJES2 can proceed afterwards.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of HJE77B0 using JES2                              *
  * email features.                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * EDS PCE may enter indefinite wait,                           *
  * causing subsequent $P JES2 command                           *
  * to hang.                                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If JES2 Email Delivery Services (EDS) address space
  initialization fails before an error recovery environment is
  established, EDS PCE may hang waiting for an address space
  response that will never come.  An example of such an early
  failure is when SAF authorization issues prevent the code in
  the EDS address space from running.
  
  Subsequent $P JES2 command waits for EDS PCE to complete its
  processing, but EDS PCE is unable to respond to the shutdown
  request.
  

Problem conclusion

• TYPE/RESTART(WARM) IPL/REQUIRED(YES) CLPA(YES)
  
  CLPA is needed only if HASCxxxx modules currently reside in
  the pageable link pack area (PLPA).
  
  JES2 EDS error recovery was enhanced to detect failures early
  in initialization process and to prevent unsatisfied wait
  condition.
  
  APAR OA55008 prereq's (and sup's) for FMID HJE77B0:
  Pre's: * NONE *
  

Temporary fix

Comments

• ×**** PE19/06/07 FIX IN ERROR. SEE APAR OA56707  FOR DESCRIPTION
  

APAR Information

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

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

  UA95438

Modules/Macros

• $EDS     HASPIRMA HASCEDS  HASMEDSM
  

Fix information

• Fixed component name

  JES2

• Fixed component ID

  5752SC1BH

Applicable component levels

• R7B0 PSY UA95438

     UP18/04/04 P F804

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.