CA OPS/MVS has various mechanisms that can detect conditions when the product is impacting the entire system. When such a condition is detected, the product shuts down and attempts to issue a message OPx3146S. This is known as an Emergency Product Shutdown.
Under some conditions (for example, there was insufficient storage in the address space when the condition occurred), the OPx3146S message cannot be issued, and you may not know the reason for the emergency shutdown. In this situation, you can determine the reason for the Emergency Product Shutdown by executing the program OPEMSHCK.
OPEMSHCK is a pre-compiled OPS/REXX program distributed in the compiled OPS/REXX library on the distribution media. You can execute the program before the system restarts after an Emergency Product Shutdown, or at any time.
Under normal conditions, OPEMSHCK issues the following message:
No CA OPS/MVS subsystems have terminated due to emergency product shutdown
Following an Emergency Product Shutdown, OPEMSHCK issues a message similar to the following:
CA OPS/MVS subsystem OPSS terminated due to an emergency product shutdown The reason being: MAXIMUM ABEND RATE EXCEEDED The shutdown may be related to JOBNAME: EVILJOB - ASID: 03B5 The shutdown occurred at: 2005/05/12 12:49:31
The 'JOBNAME' in the message is the job in which the shutdown condition was detected. It is not necessarily the job that caused the problem.
When the product is restarted following an Emergency Product Shutdown, message OPx0042I is issued. This message provides similar information to that provided by the OPEMSHCK program.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|