PH53620: CICS STARTUP NOT INITIAL AS EXPECTED AFTER CANCEL ARMRESTART

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A CICS region is using dummy MVS logstreams with an INITIAL
  start specified.  CICS is cancelled with /C jobname,ARMRESTART,
  and comes down as expected.
  
  
  
  ARM then restarts the region. But CICS will ignore the SIT or
  overrides for an INITIAL start and force an AUTO restart (i.e.
  EMERGENCY in this case) because this is an ARM restart with
  RESTART_METHOD=PERSISTENT. Because CICS doesn't come up INITIAL,
  when CICS tries to read the logs, the lack of logs causes the
  restart to fail with message:
  
  
  DFHRM0401 There is no system log or an empty system log has
  been detected.
  
  
  Additional Symptom(s) Search Keyword(s):  AUTOINIT  DFHRMUTL
  

Local fix

• Do not use persistent JCL for ARM in the restart_method defined
  for CICS in the ARM policy.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A CICS system restarted by ARM using    *
  *                      persistent JCL fails with message       *
  *                      DFHRM0401.                              *
  ****************************************************************
  The CICS subsystem can be registered with automatic restart
  manager (ARM) to be restarted automatically if it fails in an
  uncontrolled manner. The ARM policy identifies elements and
  restart groups with restart parameter values.
  If the CICS system logs are defined to be DUMMY, CICS regions
  can only be INITIAL started.However, when the ARM policy is
  defined to use persistent JCL on restart and extended recovery
  facility (XRF) is not used, then the CICS start type is forced
  to be AUTO. The restart then fails with ABEND U1800 and a
  DFHRM0401 message indicating an empty system log has been
  detected on a CICS restart which requires the log for recovery
  processing.
  

Problem conclusion

• CICS has been changed to issue a new message DFHKE0415 to inform
  the user that CICS will restart with start type AUTO.
  
  
  The CICS Messages manual will be updated with the following
  new message:
  DFHKE0415  <APPLID> CICS IS BEING RESTARTED WITH
  PERSISTENT JCL AND XRF=NO. CICS WILL RESTART WITH TYPE=AUTO.
  Explanation: An attempt to invoke a REGISTER request against the
  z/OS automatic restart manager (ARM) has succeeded. However, the
  system is being restarted with persistent JCL and without
  extended recovery facility (XRF). Any override for CICS start
  type from the JCL is ignored and forced to be AUTO.
  Note that any CICS regions using DUMMY system logs will fail to
  restart with message DFHRM0401.
  This is an informational message.
  System action: Restart continues.
  User response: None.
  Module: DFHKEAR
  

Temporary fix

Comments

APAR Information

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

  PH53591

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

  UI93406

Modules/Macros

• DFHKEAR  DFHMEKEC DFHMEKEE DFHMEKEK
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R400 PSY UI93406

     UP23/09/06 P F309

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.