Recovery actions for command flooding indications

Command flooding occurs when too many MVS™ commands are issued at one time, possibly because a program has issued too many MGCRE macros. The first indication of command flooding is message IEE822E COMMANDS ARE AT 80% OF LIMIT IN COMMAND CLASS cc, followed by message IEE806A COMMANDS EXCEED LIMIT IN COMMAND CLASS cc. The CMDS command can be used to correct this situation.

Determine why the command flooding occurred.
Issue the CMDS SHOW command. This displays all of the executing commands as well as the commands that are waiting for execution with the time that the command started execution and the job that issued the commands.
If most of the commands in the CMDS SHOW output appear to be from the same job or automation program, the job may be in a loop issuing commands, or the job may have legitimately issued a large number of commands. For example, a program may have issued a large number of VARY commands for many devices. If the commands were issued legitimately, and it appears that the commands are being processed, the commands may be allowed to complete execution.
If the commands appear to have been issued in error, take one of the following actions:
- Use the CANCEL command to cancel the job that is issuing the commands.
- Use the CMDS REMOVE command to remove the commands that are waiting for execution. CMDS REMOVE cannot remove commands that are already executing.
If it appears that an executing command has been running for a long time, it may be hung due to a resource deadlock or other required action. Issue CMDS DUMP to obtain diagnostic data about why the command is hung. The CMDS ABEND command can be used to ABEND the command that is hung. CMDS ABEND should be used with extreme caution and should be used only as a last resort, as the system could be left in an inconsistent state.