WHY DO I HAVE AMDUSR31 MODULE IN TWO DIFFERENT LIBRAIRIES?

Products

• CA 1 Flexible Storage
• CA 1 Tape Management - Copycat Utility
• CA 1 Tape Management - Add-On Options
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Description:

You have installed CA Common Services r14.1

You found the same load module in 2 different libraries: AMDUSR31 is the load module name.

It exists in the CAW0LINK library and is an alias of CASRVTRF.
It is created by the CEI0E10 function (CA-MASTER).

It exists also in the CAW0PLD library and is an alias of MSMCJTRF.
It is created by the CETN500 function (MSM Common Services).

The duplicate AMDUSR31 alias entry needs to be removed from the CAW0LINK library. While having these duplicate alias entries existing in two different libraries is not currently a concern, we do not want mulitple alias entries around because at some future point this can present a problem. The only current impact is for customers that may decide to merge the CAW0LINK and CAW0PLD libraries.

 

Environment

Release:
Component: CCS390

Resolution

Solution:

A temporary circumvention would be to delete the alias from the CAW0LINK so that the ADMUSR31 entry from CAW0PLD is used or simply be sure to define CAW0PLD ahead of CAW0LINK in the LINKLIST.

The permanent solution is to download and install PTF RO49032. While this PTF will delete the associated module, you will still be required to manually delete the AMDUSR31 alias entry from CAW0LINK dataset.