Shutdown requested by the operating system

This type of shutdown can be initiated by the operating system as a result of a program check or an operating system abend.

A program check or system abend can cause either an individual transaction to abend or CICS® to terminate. (For further details, see Processing operating system abends and program checks.)

A CICS termination caused by an operating system request:
  • Does not guarantee that user tasks will complete.
  • Does not allow shutdown PLT programs to execute.
  • Does not write a warm keypoint or a warm-start-possible indicator to the global catalog.
  • Takes a system dump (unless system dumps are suppressed by the DUMP=NO system initialization parameter).
  • Does not close any open files. It is left to VSAM to close the files when VSAM is notified by MVS™ that the address space is terminating. This form of closing files means that a VSAM VERIFY is needed on the next open of the files closed in this way, but this is done automatically.

The next initialization of CICS must be an emergency restart, in order to preserve data integrity. An emergency restart is ensured if the next initialization of CICS specifies START=AUTO. This is because the recovery manager’s type-of-restart indicator is set to "emergency-restart-needed" during initialization, and is not reset in the event of an immediate or uncontrolled shutdown.



dfht216.html | Timestamp icon Last updated: Sunday, 4 June 2017