Subtask control commands allow you to manually control the status of a subtask. Ironstream subtasks start automatically when the job is started, and the subtasks restart automatically if brought down by some anomaly.
INIT
Activates a defined subtask that is in a DOWN state. This command can also be used when a subtask is in the DOWNR state to skip the rest of the timed delay and force the re-initialization to continue immediately. The INIT command can only activate tasks that are listed in the SHOW TASK table.
Parameters:
subtaskname
Example:
MODIFY VP390,INIT TCP-0
EVO595 Command entered: INIT TCP-0
EVO002 TCP subtask initialized for 6106,6107
KILL
Forces the termination of a defined subtask. When a subtask is terminated with this command, it does not attempt any automatic restarts. The command resets the count of number of automatic restarts that are attempted. The command can also be used to stop a subtask in the DOWNR state from attempting any more restarts.
Parameters:
Subtaskname
Example:
MODIFY VP390,KILL SPO-1
EVO595 Command entered: KILL SPO-1
EVO902 SPO-1 subtask terminated, RC = 0
Term
Stops all subtask and then stops the main task, terminating the VP390 job. This command is equivalent to the z/OS STOP command.
Parameters
None
Example
MODIFY VP390,TERM
EVO595 Command entered: TERM
EVO690 VP390 STOP Command accepted
EVO901 Stopping subtask #1: TCP-0
EVO901 Stopping subtask #2: OSI
EVO901 Stopping subtask #3: CMD-0
EVO695 VP390 STOP command processed
EVO902 OSI subtask terminated, RC = 0
EVO902 CMD-0 subtask terminated, RC = 0
EVO902 TCP-0 subtask terminated, RC = 0
EVO904 All VP390 subtasks complete
IEF404I VP390 - ENDED - TIME=17.30.08
$HASP395 VP390 ENDED