Abnormal system termination (SETS) is initiated by MSCF in four defined situations. The cases indicated by messages MCS1300 and MCS1301 are, however, "normal" terminations, i.e. system terminations permitted by the defined operating parameters. Only message MCS1302 indicates an error that must be diagnosed.
MCS1300 SYSTEM TERMINATION TO PREVENT ERRONEOUS CRASH DETECTION BY PARTNERSIf the processor is no longer able to send vital-sign messages to a partner due to the loss of the MSCF connection and the simultaneous occurrence of a write error on the watchdog files of all shared pubsets, and if there is a danger (due to time conditions and the RECOVERY-START settings) that a fail reconfiguration will be initiated by a partner, a SETS is initiated with MCS1300 in order to prevent data inconsistency on the global resources. See also “Controlling allowed system aborts” (Global control parameters).MCS1301 SYSTEM TERMINATION TO ALLOW THE RECONFIGURATION AT THE MSCF PARTNERSIf MSCF terminates on a processor and the network functionality used by the processor cannot be released due to an error in configuration management or in the registered functions, it is not possible for the remaining processors to reestablish the XCS network. When operating with the general RECOVERY-START=*AUTOMATIC setting, a SETS is therefore initiated with MCS1301 to enable the reconfiguration of the XCS network on the partner processors.MCS1302 SYSTEM TERMINATION BECAUSE OF IRRECOVERABLE ERROR IN CONFIGURATION MANAGEMENT(failed error recovery)
If the MXCM task terminates abnormally, a task error recovery is initiated in which MSCF is terminated on the processor. If a program error occurs again, a SETS is initiated with MCS1302 because the consistency of the network can no longer be guaranteed.MCS1304 SYSTEM TERMINATION BECAUSE OF EXPIRATION OF ABORT-LIMIT TIMEIf a network-participation abort for a shared pubset network or XCS network cannot be completed within the interval specified by ABORT-LIMIT, a SETS is initiated with MCS1304.