Removing Tasks from Execution
Use the FLUSH TASK command to remove a task from execution. Identify the task by its task number. You cannot flush system or IUI tasks.
The FLUSH TASK command has the following format and associated parameters. Required parameters are in bold print.
|(optional)||FLush TASK||WHERE (|
|TASK = (tasknumber | (list),|
|SERVER = server name|
The required FLUSH TASK parameter is:
|WHERE (TASK = (tasknumber | (list), SERVER=server name)||(tasknumber | (list) specifies the tasks to flush
either by task number or a list of task numbers.
This parameter is required. SERVER=server name specifies the name of the IBM® Connect:Direct® server where the FLUSH TASK is performed. The server name parameter is the 1–8 character name assigned to a IBM Connect:Direct/Server by the CDPLEX.SERVER initialization parameter. This parameter is only valid in a IBM Connect:Direct/Plex environment. If you omit this parameter in a IBM Connect:Direct/Plex environment, the FLUSH TASK is performed on a IBM Connect:Direct/Manager.
The optional FLUSH TASK parameter is:
|FORCE||Specifies that flush task is forced. Do not use
the FORCE parameter when the task is executing on a LU6.2 session.
The session terminates immediately and statistics are not exchanged
between the two nodes.
If you do not specify the FORCE option for the FLUSH TASK command, then an indicator notifies the program executing on behalf of the task that a FLUSH TASK command was issued for that task. If that program is not in control (for example, if it is waiting on a request outside of IBM Connect:Direct to complete), then it does not recognize the FLUSH TASK indicator, and the task is not flushed; otherwise, the program recognizes for the FLUSH TASK indicator and takes the appropriate action.
When you specify the FORCE option, then the action taken depends on the STATE and SUBSTATE of the task for which you issued the FORCE FLUSH. See Connect:Direct Process Language for the actions taken for the specific STATE and SUBSTATE.
Note: Use the SELECT TASK command to determine the STATE and SUBSTATE of the task.
The following example shows the FLUSH TASK command force flushing three tasks:
The following example shows the FLUSH TASK command flushing a task running on a IBM Connect:Direct/Server named OSGOOD: