OPS3146S EMERGENCY PRODUCT SHUTDOWN STARTED - MAXIMUM COMMAND RATE EXCEEDED
Article ID: 13197
Updated On:
Products
Issue/Introduction
OPS3146S EMERGENCY PRODUCT SHUTDOWN STARTED - MAXIMUM COMMAND RATE EXCEEDED
was shown and SYSTEM was shutdown.
How do we avoid the shut down?
Environment
Component:
Resolution
It is effective to change the COMMANDMAX parameter regarding Parameter guide, Chapter 2.
For example ;
At OPSSPAxx
T = OPSPRM('SET' , 'COMMANDMAX' , '2000')
As TSO command
TSO OP SET(COMMANDMAX) VALUE(2000)
It should be noted that depending on what is issuing the messageID that the command is running off of, this may be a temporary fix to just raise the COMMANDMAX value. It is recommended to use the OPS/MVS provided REXX function OPSTHRSH to eliminate or reduce the number of duplicate actions that get triggered by the same event.
Additional Information
For release 14,0 more information, refer to https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/reference-information/parameter-reference/parameters-in-ca-ops-mvs/command-related-parameters.html
COMMANDMAX Parameter
This parameter dictates the maximum number of commands CA OPS/MVS can issue per second.
When this number equals the value of the COMMANDCURRENT counter, CA OPS/MVS terminates and issues message OPS3146S.
Setting the COMMANDMAX parameter to its maximum possible value prevents CA OPS/MVS from ever shutting down due to an excessive command rate.
- Default value
200 - Other possible values
Any number between 100 and 10000 - Set or modify this parameter...
Anytime
Example: COMMANDMAX
This function limits CA OPS/MVS to issuing 2000 commands.
OPSPRM('SET','COMMANDMAX','2000')
Please also refer to the below link for more information on the OPSTHRSH REXX function:
https://docops.ca.com/ca-opsmvs/13-0/en/reference-information/command-and-function-reference/ops-rexx-built-in-functions/opsthrsh-function
Feedback
