How to monitor remote LPARs using CA OPS/MVS Event Management and Automation.
Article ID: 8980
Updated On:
Products
Issue/Introduction
We need to issue alerts when OPS is shutdown or the system is unresponsive on a LPAR. What messages can we monitor on remote LPARS that may serve as indication that a LPAR is not active?
Environment
CA OPS/MVS
Cause
Replies from the pings are not possible due to a problem with the following: Network, VTAM or a major system error.
Resolution
Some messages can be monitored:
- OPS3440O MSF SYSTEM XXXX HAS NOT RESPONDED TO A PING
- OPS3504O SYSTEM ID XXXX IS NOW INACTIVE
- OPS3541O APPC SEND FUNCTION FAILED FOR XXXX
- OPS3486O MSF/CCI system xxxxx IS NOW INACTIVE - N/A
Additional Information
Here are some other possible solutions:
> You can register OPS with Automatic Restart Management (ARM) to have it restart automatically after a failure.
> If you have the CA Automation Point software, you can use it to monitor failure message from OPS and restart the product.
> We have also seen customers run a second, scaled down version, of CA OPS that only manages the production copy and restarts it after a failure.
> One thing that could be done is add a OPSYSPLX call (if this system is in the sysplex) to your logic to assure the system didn't stop.
systems = OPSYSPLX(i,s)
and it will give you the in WORD number 11 the status - and word number 5 is the last status date. If the status isn't ACTIVE, you may have a problem, but you would need to further evaluate based upon its actual value..
You can even add the name to the OPSYSPLX('i','s',SYSA) to look only at the system you are interested in. Again this must be within a sysplex to use.
If the system froze, the same thing would occur on any release of CA OPS/MVS, since no error is detected and VTAM does not do anything (it is frozen)... If all systems, other than the monitoring system are in a SYSPLEX, they could have TOD rules to check the status within their sysplexs, and if something appears wrong, notify the monitoring system.
Feedback
