OPS0010U Load Module OPSENQ release code error - IBM SA Library SINGLOAD

book

Article ID: 210924

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

Upgrading to z/OS 2.4, that includes an update to System Automation 4.02, when OPSMAIN is started on the newly converted system, the  below message is got:

OPS0010U Load module OPSENQ release code error - contact systems

Why this message and how to bypass it ?

 

Environment

Release : 

Component : OPS/MVS

Resolution

Upgrading to z/OS 2.4, it will automatically include an update to System Automation 4.02. This update renames loadlib SINGMOD1 to SINGLOAD and adds a new IBM module alias OPSENQ.  This same module name is also present in the OPSMVS product CCLXLOAD loadlib.

If the CCLXLOAD library is located AFTER the SINGLOAD in Link List, starting OPSMAIN on the newly converted system, the message

OPS0010U Load module OPSENQ release code error - contact systems

is immediately issued because of modules mismatch and the easiest temporary work around is to use the //STEPLIB to the CCLXLOAD library in the OPSMAIN PROC.

In general CA OPS/MVS does not require that its load library is in the LNKLST and it is usually recommended to include STEPLIB in all OPS procs such OPSOSF, OPSUSS, OPSECF and others like the OPSLOG archival task. The JCL procedure of the TSO users that access the OPSVIEW panels will also have to include the STEPLIB for the CCLXLOAD library as some functions require APF authorization. Other than the above, it is OK to use STEPLIB instead of LNKLST, but also the LNKLST can be used.

That's why for this specific situation IBM has provided the APAR fix:

OA60121: SA V4.2 CREATED TWO ALIASES BY MISTAKE.

Error description
IBM Z SA v4.2 shipped incorrect ALIASes.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: All IBM Z System Automation V4R2             *
*                 customers.                                   *
****************************************************************
* PROBLEM DESCRIPTION: SA created incorrect ALIASes.           *
****************************************************************
SA should not introduce an ALIAS which can interfere with third
party products.
Problem conclusion
Changes have been made to delete the incorrect ALIASes

closed by the PTF UJ03885

This IBM PTF should be applied to solve the problem.