NET/MASTER Management Services (MS) Command Reference Manual

FLUSH
NonStop NET/MASTER MS Commands
2–106 115412 Tandem Computers Incorporated
FLUSH The FLUSH command terminates an NCL process and any NCL processes executing
in its dependent processing environment. This command terminates execution
immediately and unconditionally. You can use this command to terminate an
executing, paused, queued, or delayed NCL process. The command is useful when
you are developing NCL procedures and debugging NCL processes; you can use it to
terminate an old version of an NCL process before you execute the new version.
FLUSH [ ID= ncl-id ]
ID= ncl-id
identifies the NCL process to terminate. You must specify this operand if more
than one NCL process (excluding MSGPROC) is executing in your primary
processing environment.
If you enter this command without specifying an NCL process identifier, NonStop
NET/MASTER MS assumes that only one NCL process (excluding MSGPROC) is
executing in the current execution environment and assumes the command
applies to that NCL process. NonStop NET/MASTER MS attempts to terminate
this NCL process. If more than one NCL process (excluding MSGPROC) is
executing in the current execution environment and you enter the command with
no operands, NCL displays an error message.
Considerations
The default authority level of this command is 0. The ID operand has a default
authority level of 2.
You can enter this command from any NCL procedure, including the INIT NCL
procedure, by using either the CMD core statement or the INTCMD verb.
By default, the target NCL process must be owned by your user ID. If your
command authority level is equal to or higher than the authority level of the ID
operand and SYSPARMS NCLXUSER=YES, then you can use this command to
terminate any NCL process in any region (belonging to any user).
You can target an NCL process in either OCS window excluding MSGPROC. You
must use the PROFILE MSGPROC=FLUSH command to flush MSGPROC.
When you are developing NCL procedures and debugging NCL processes, you
should set test mode on using PROFILE NCLTEST=YES to ensure that you execute
the latest version of an NCL procedure.
If you do not have an error handler to trap the FLUSH command in the NCL
process (either the ERROR or FLUSH_ERROR error handler), when the NCL
process is flushed it raises a run-time error and terminates.