4. Operation › 4.3 Operations Reference › 4.3.4 Operational Status and Tracking › 4.3.4.4 Operational Status and Tracking Commands › 4.3.4.4.17 RSTATUS Command

4.3.4.4.17 RSTATUS Command

 Use the RSTATUS command to synchronize the Operational Status
 and Tracking control tables with the CA MICS unit database
 checkpoint file and to produce the CA MICS Run Status Report.
 
 Normal unit database update, backup, and restore processing
 will keep Operational Status and Tracking synchronized with
 the checkpoint file.  However, run status processing may not
 execute if Database update processing is canceled by the
 console operator, fails with a JCL error, or is terminated by
 an MVS system crash.  Under these conditions, Operational
 Status and Tracking will not be synchronized with the unit
 database checkpoint file and RSTATUS will be required before
 Operational Status and Tracking can restart the Database
 update.
 
 RSTATUS submits the prefix.MICS.CNTL(RSTATUS) batch job to
 update Operational Status and Tracking entries from the unit
 database checkpoint file.  RSTATUS also saves a copy of the
 generated run status job in the prefix.MICS.RESTART.CNTL data
 set for the unit database.
 
 If the RSTATUS job finds the database in a non-updatable
 condition, the RSTATUS job will terminate with a U999 abend.
 When the RSTATUS job terminates with a U999 abend, use the
 Operational Status and Tracking STATUS command or review the
 printed Run Status Report to analyze the database problem.