Parameters

CMDS:
  • ABEND — abnormally end a command that is currently executing.

    This parameter requires subparameters CMD= and ID=.

    The system terminates, with ABEND code 422, reason code 00010301, the command that CMD=cccccccc and ID=nnnn identifies.

    Use the ABEND option with extreme caution, being careful to avoid leaving the system in an inconsistent state.

    The system issues message IEE064I in response to this command. It does not send any response message to the console that issued the abended command.

    Attention: The ABEND request will be rejected with message CNZ6002I if the command is in a non-abendable state.
  • DISPLAY | D — display the numbers and brief information about the commands that are currently executing and those that are waiting for execution.

    The system issues message IEE062I in response to this command.

  • DUMP — schedule a dump for the master and console address space.
  • FORCE — abnormally end a command that is currently executing.

    This parameter requires subparameters CMD= and ID=.

    The system terminates, with ABEND code 422, reason code 00010302, the command that CMD=cccccccc and ID=nnnn identifies.

    Use the FORCE option with extreme caution because you are terminating a command that may be updating critical system data. Use this parameter only as a last resort, such as when a re-IPL is needed if the command is not terminated.

    The system issues message IEE064I in response to this command. It does not send any response message to the console that issued the abended command.

    Attention: If the command is considered non-abendable, FORCE will still terminate the command and message CNZ6002I will be issued indicating that FORCE overrode the abendable setting.
  • REMOVE | R — remove commands that are waiting for execution, as specified by the subparameters. You cannot use this option to cancel any commands that are executing.

    The REMOVE parameter requires you specify at least one of the keyword subparameters CLASS=, CMD=, ID=, or JOB=.

    The system issues message IEE064I in response to this command, and sends message IEE065I to the console that issued the removed command.

  • SHOW | S — display full information about the specific command(s) specified by the subparameters.

    The system issues message IEE063I in response to this command.

The CMDS command uses the following keyword subparameters to limit the number of commands to show or remove:
  • CLASS= classname

    The command class in which the commands belong.

    If you do not specify this parameter, commands in all classes will be displayed or removed.

    The classes are:
    1. Class M1 commands may be essential to clearing a backlog of Class M2 commands.
    2. Class M2 commands are ordinary attached commands that run in the MASTER address space.
    3. Class M3 is only for SEND commands executed in the MASTER address space.
    4. Class C1 commands might be needed to clear a backlog of Class C2 commands.
    5. Class C2 commands are ordinary attached commands that run in the CONSOLE address space.
    6. Class C3 is only for the ROUTE command executed in the CONSOLE address space.
    For a list of the commands by class, see Command flooding.
  • CMD= command verb
    The name of the command, as displayed by the SHOW option. For example,
     CMDS  REMOVE,CMD=CONFIG
    will delete all CONFIG commands that are waiting for execution.

    You can use command abbreviations instead of full command names.

  • ID= number
    • The command's sequence number, which appears in the output from a CMDS DISPLAY or CMDS SHOW command (messages IEE062I or IEE063I).
  • JOB= jobname of the command issuer, as displayed by the SHOW option. For example,
    CMDS  REMOVE,JOB=JOB1111
    will remove all commands issued by JOB1111.
    If you specify more than one of the keyword parameters, the command must meet all specified criteria. For example,
    CMDS  REMOVE,CMD=VARY,JOB=JOB1111
    will remove waiting VARY commands that job JOB1111 issued.
Note: Some commands remain active indefinitely, so the system will display them whenever CMDS is issued. For example, if any SLIP commands have been issued and SLIP traps are in effect, one SLIP command will be "executing" until all traps are deleted. This is also true for many SET commands, such as SET SLIP and SET MPF.