Commands recovered during emergency restart

Certain commands that successfully alter IMS™ resources are written to the system log as X'02' or X'22' log records and are reprocessed during emergency restart.

IMS type-1 commands that are recovered during emergency restart write an X'02' log record. Type-2 commands that are recovered during emergency restart write an X'22' log record. The following table lists the commands, along with the exceptions, that are recovered during emergency restart.

Table 1. Commands recovered during emergency restart
Command	Exceptions
/ASSIGN
/CHANGE	/CHANGE DESCRIPTOR
CREATE
/DELETE
DELETE
/END
/EXCLUSIVE
/EXIT
/HOLD
/LOCK	/LOCK LTERM, /LOCK NODE, /LOCK PTERM
/LOG
/MONITOR
/MSASSIGN
/PSTOP	/PSTOP LTERM
/PURGE	/PURGE APPC, /PURGE LTERM
/RELEASE
/RSTART
/SET	/SET LTERM, /SET TRAN
/SMCOPY
/START	/START APPC, /START ISOLOG, /START TRKARCH, /START PROG
/STOP	/STOP APPC
/TEST MFS	/TEST LINE, /TEST NODE, /TEST USER
/UNLOCK	/UNLOCK LTERM, /UNLOCK NODE, /UNLOCK PTERM, /UNLOCK SYSTEM
UPDATE DB
UPDATE MSLINK
UPDATE MSNAME
UPDATE MSPLINK
UPDATE PGM
UPDATE RTC
UPDATE TRAN	UPDATE TRAN START(TRACE), UPDATE TRAN STOP(TRACE)

Restriction: If an IMS outage (abend, modify, or cancel of IMS) occurs immediately after a command is entered, the command status might not be carried across an emergency restart or XRF takeover.

The command log records are logged asynchronously (no check write or wait write). If there is no other IMS activity that forces the log buffer to be written to the OLDS or WADS data set, the status set by the command, for restart purposes, did not occur.

There are many events in IMS where log records are check-written to the log. Any one of these events subsequent to the command causes the command log record to be written to the OLDS or WADS data set.