Restarting a Manager Fault Tolerant UCMD Manager on z/OS
In Using Manager Fault Tolerance from zOS, the example demonstrates how to remotely execute work using the Manager Fault Tolerant (MFT) feature.
The following example demonstrates how to restart a UCMD Manager that premature ended when using MFT.
If a UCMD Manager executing with MFT ends prematurely, the UCMD Server and the remote work will continue executing until the remote work has completed. All standard I/O files are saved on the UCMD Server system, along with the exit conditions of the work. They will remain on the UCMD Server system until a UCMD Manager is restarted using the same command ID that identifies the work.
A restart can be performed after the remote work has complete or while the remote work is still in executing.
Continuing from Using Manager Fault Tolerance from zOS, the following example illustrates a UCMD Manager restart for the work identified by command ID example-2010-07-02.
//jobname JOB CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID //* // JCLLIB ORDER=SBI.UNV.SUNVSAMP //* //STEP1 EXEC UCMDPRC //SYSIN DD * -cmd command -host hostname -userid username -pwd password -managerft yes -cmdid example-2010-07-02 -restart yes /*
SYSIN Options
Option | Description |
|---|---|
Command to execute on the remote system. | |
Host name or IP address of the remote system on which to execute the script. | |
Remote user ID with which to execute the command. | |
Password for the user ID. | |
Specification for whether or not the Manager Fault Tolerance (MFT) feature is used. A value of yes specifies that MFT should be used. | |
Unique command ID associated with the remote unit of work. | |
Specification for whether or not the manager is requesting restart. A value of yes indicates the Manager is being restarted. |
Components
Universal Command Manager for z/OS