PK17380: DFHRMUTL WITH SET_AUTO_START=AUTOINIT DOES NOT WRITE A RESTART RECORD

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 5697E9300
  PQ60109 introduced a method where users can programatically
  determine what the restart type should be. However, there is no
  current architected means of detecting a new Global Catalog
  Dataset (GCD). PQ60109 documents the following:
  "CICS ensures this global catalog record is deleted during
  restart, and written during a controlled shutdown. Therefore
  presence or absence of the record on the catalog indicates
  whether the CICS system was previously shutdown warmly or not
  (i.e. by the use of CEMT PERFORM SHUTDOWN).
     If the record exists on the global catalog, and the three
  count fields are zero, then DFHRMUTL may be used to modify
  the autostart override record to AUTOCOLD."
    Customer is using the programable interface as directed.
  However at times they clear out the DFHGCD datasets due to new
  releases, new regions and BCP tests and should be using AUTOCOLD
  . DFHRMUTL is ran against the new GCD with
  SET_AUTO_START=AUTOINIT but this does not write a restart record
  and the new GCD only contains a RMDM_OPTIONS record. This causes
  the application using the programable interface to incorrectly
  determine the next start up should be EMERGENCY. CICS does
  correctly come up INITIAL as it should but the application
  thinks differently. Because this same application controls many
  other auto ops procedures and due to incorrectly determining the
  next startup should be EMERGENCY, other procedures are put into
  play inappropriately causing the region to be cycled.
    There needs to be a documented way to use the interface to
  determine a new GCD is being used.
  

Local fix

• Customer currently checks for the presense of a RMDM_ANCHOR
  record. The non-existance of this record is indication of a new
  GCD.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHRMUTL does not write a               *
  *                      DFHRMDM_RESTART record to the DFHGCD.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In the reported problem, a CICS system was brought up and
  shutdown 'WARM'. In doing so, a DFHRMDM_RESTART record was
  written to the DFHGCD. The DFHGCD was then scratched and
  redefined and DFHRMUTL run against it for AUTOINIT purposes.
  However, this did not write a DFHRMDM_RESTART record to the
  DFHGCD.
  A batch job attempted to interpret fields within the
  DFHRMDM_RESTART record but was unable to do so, the
  documentation states that if a DFHRMDM_RESTART record does not
  exist then the CICS system was brought down 'non-warm'. The
  batch job assumed that the next CICS restart would be an
  EMERGENCY.
  
  Keywords: GCD INDOUBT DFHRMREC DFHRMRED DFHRMREH DFHRMREL
            DFHRMREO rmdm_restart_key rmdm_restart_counts
  

Problem conclusion

• DFHRMUTL has been modified to write a DFHRMDM_RESTART record to
  the DFHGCD.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PK12629

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

  UK11218

Modules/Macros

•    DESRMUTL DFHRMUTL
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK11218

     UP06/02/02 P F602

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.