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

CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA Mainframe Software Manager (Chorus Software Manager) CA MICS Resource Management CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

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