OPS1423E error when accessing OPSLOG via Opslog Browse
search cancel

OPS1423E error when accessing OPSLOG via Opslog Browse

book

Article ID: 453401

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

A user encountered the error OPS1423E while attempting to access the OPSLOG via the OPS/MVS OB (OPSVIEW Browser). 

Cause

 The OPS1423E message is written when the OPS/MVS security exit denies the current user access to the OPSLOG.

Resolution

The OPS1423E error is triggered when the OPS/MVS security exit determines that the current user ID does not have the required access to the OPSLOG at that moment. Security implementation depends on your system configuration, which can be verified via the EXTSECURITY parameter:

  • External Security (ESM): If the EXTSECURITY parameter is set to ON, OPS/MVS delegates security checks to your External Security Manager (e.g., RACF, ACF2, or Top Secret).

    • Action: Ensure the user ID has the appropriate resource profiles defined in your ESM for OPSLOG access. Review your ESM security logs for the time of the error to identify the specific resource access violation.
  • Internal AOF Security Rules: If the EXTSECURITY parameter is set to OFF, security is managed via OPS/MVS Automation Object Facility (AOF) security rules.

    • Action: Review your AOF members specifically written to intercept and authorize OPSLOG requests. Ensure these rules are correctly configured to permit the user access.

Additional Troubleshooting If the issue is intermittent and resolves after re-logging in, verify if there was a temporary issue with the user's security session or context at the time of the failure. If the error persists, monitor OPSLOG and Security Audit events to track denied access attempts in real time.