OPS0087W: Subsystem SVC 95 microhook not receiving control

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

This article explains the OPS0087W warning message, which indicates that the OPS/MVS subsystem has not received control via the SVC 95 microhook for a specified period (typically one hour). It provides guidance on determining if this message is informational or indicates an underlying issue.

The message OPS0087W Subsystem <subsystem_name> SVC 95 microhook not receiving control is issued when OPS/MVS has not detected any JOB, STC, or TSU completion events for one hour.

In many environments, this message is informational and can be erroneous, particularly on systems with low activity where no relevant events have occurred within the monitoring window.

Environment

• Product: CA OPS/MVS Event Management and Automation
• Release: All supported releases (14.0 and later)

Resolution

Resolution / Troubleshooting Steps

1. Verify Maintenance: Ensure that PTF LU12763 (or the latest cumulative maintenance) is applied to your system. This PTF was specifically released to address and correct erroneous OPS0087W reporting.

2. Verify the SVC 95 Hook: If the warning persists, verify that the SVC 95 hook is correctly installed. You can do this by taking a dump of the SVC 95 entry point and checking for the valid eye-catcher (e.g., OPSC95HK followed by the version level). If the hook is correctly in place, the subsystem is functioning as intended.

   • Run the SVCTABLE job that can be found in the OPSMVS.**.CCLXSAMP library 
   • Look for the address associated with SVC 95 (EP=xxxxxxxxx)
   • Use a system utility to dump and view the address space 
   • Inspect the dump output for a valid eye-catcher. The eye-catcher should begin with OPSC95HK.
   • Verify that the version string present in the eye-catcher aligns with your current OPS/MVS installation level.
   • If the eye-catcher is found and reflects the expected release version, the hook is correctly installed, and the subsystem is functioning as intended.
   • Note - SYSVIEW can be used to view the storage via the DUMP xxxxxxxx command, where xxxxxxxx is the address found in the SVCTABLE.  

3. Evaluate System Activity: Assess whether the message correlates with periods of low system activity. If the warning consistently appears when no jobs or tasks are completing and disappears during periods of normal activity, it is operating as designed.

4. Further Investigation: If you suspect the message is suppressing critical alerts or if you are experiencing other related functional issues, perform the following:

   • Review the OPSLOG for additional error messages occurring during the same timeframe.
   • If the issue cannot be resolved through the steps above, please open a support case with Broadcom and provide a tersed copy of the archivedOPSLOG for further analysis.