OA63467: SYSTEM SHUTDOWN STALLED AFTER VTAM WAS BROUGHT DOWN, JES2 SHOULDHAVE BEEN NEXT, BUT WAS NOT SHUTDOWN.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• While doing an orderly GDPS system shutdown, applications were
  being shutdown as expected, including VTAM, next in line should
  have been JES2, but it was not shutdown.
  
  Investigation showed the shutdown stalled because CRON was not
  down.  Since CRON was still around, the stop order for parent
  JES2 was not sent out. It appeared that the CRON termination was
  underway, and the first shutdown pass for JES2 was already
  issued.  However, for some reason, the AM sent out another
  (second and unexpected) PREP_UNAVAILABLE order for CRON.  As a
  result, the Agent cleared CRON's shutdown variable, expecting
  another SHUTDOWN/MAKEUNAVAILABLE order.  This however never came
  through.  When CRON's shutdown timer popped to issue the next
  shutdown pass command, the Agent found no shutdown
  details/variable for it and issued:
  
  AOF743I SHUTDOWN WILL NOT (RE)PROCESS SUBSYSTEM CRON AS IT IS
  NOT IN SHUTDOWN
  

Local fix

• Manually shutdown JES2 and possibly other APLs, until this APAR
  can be installed.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IBM Z System Automation V4R2 and         *
  *                 V4R3 customers.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The termination of an application might *
  *                      stall when the AM sends a second        *
  *                      PREP_UNAVAILABLE order to the Agent     *
  *                      which is not followed by a second       *
  *                      MAKE_UNAVAILABLE order.                 *
  ****************************************************************
  The SA Agent should tolerate a second PREP_UNAVAILABLE order.
  When the termination of the resource is already under way then
  the next shutdown passes should be issued to make sure that the
  shutdown does continue.
  

Problem conclusion

• REXX module AOFRDWN4 has been modified to prevent the problem.
  

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:

  UJ08804 UJ08808

Modules/Macros

• AOFRDWN4
  

Fix information

• Fixed component name

  SYSTEM AUTO Z/O

• Fixed component ID

  5698SA300

Applicable component levels

• R420 PSY UJ08808

     UP22/08/20 P F208

• R430 PSY UJ08804

     UP22/08/20 P F208

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.