MSMTC fails at startup with MSM0008E - System startup failed - please see error output for further information. Fatal error has stopped the startup was: SafError - Error during DSI java open. RC=13 . Path to 'dsi.conf': /msmserv41/msmruntime/dsi/

book

Article ID: 49521

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:

This safError Error during DSI java open, RC=13 is addressed by TEC535343 which points out the host and port parameters in dsi.conf file must match the dsiHost and dsiPort values on the MSM Datacom database. The database is updated with these values from SAMPLIB(DBINIT).

In addition the DSI port may already be in use by another application and not available to MSM and MSM maybe pointing to the wrong location for the dsi.conf file. To verify if the location is correct refer to the dsiConf parm in SAMPLIN(DBINIT).

If all of the above checks out okay and the safError RC=13 still occurs it maybe related to the dsiport being reserved in the TCPI/IP profile. If it is a port reversation issue you should see in the .../scroot/tmp/dsi_client.log file errors like these:

13:37:33.197345|23D19B0000000000? daemon_open_listener:bind(4,127.0.0.1:22130) failed: errno=111
13:37:33.198990|23D19B0000000000? daemon_open_listener: EDC5111I Permission dened.

This specific example shows the loopback address and port 22130 but this would vary depending on what values you are using.

Solution:

If the dsi port is reserved in the TCP/IP profile verify that it is reserved to the jobname for the MSMTC startup proc. If it is meant for another application use another dsi port for MSM or change it to be reserved for the MSMTC startup proc jobname. If the jobname is less than 8 characters you could reserve it with an asterisk. For example if the jobname is MSMTC you may use MSMTC* other use 8 characters for the jobname.

Environment

Release:
Component: MSM