The CA MSM MUF fails at startup with DB01900I - MUF MF20B,99,YES LOGICAL NAME OF THIS MUF,#EXTRA RUNUNITS followed by DB01909E - * - ASTERISK POINTS NEAR ERROR then DB01911E - PARAMETER HAS INVALID VALUE.

book

Article ID: 50682

calendar_today

Updated On:

Products

Compress Data Compression for MVS Compress Data Compression for Fujitsu Datacom DATACOM - AD Mainframe Software Manager (Chorus Software Manager) MICS Resource Management 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:

The asterisk in the DB01909E points to the name of the MUF in the DB01900I message. The Datacom DBSIDPR module is assembled with the name of the MUF coded on the MUFname= parm in MSMSetupOptionsFile.properties file in .SAMPLIB(MSMINS02).

Solution:

The name of the MUF in DBSIDPR must match the MUF name in .CAIMAC(DBDATIN2) on the MUF statement in this member. For example:

MUF        MF20B,99,YES      LOGICAL NAME OF THIS MUF,#EXTRA RUNUNITS.

The default name of the MUF is MF20B. Whatever name is coded in the MSMSetupOptionsFile.properties file should also be coded in .CAIMAC(DBDATIN2) on the MUF statement.

Environment

Release:
Component: MSM