MSMTC Fails with RC=100

Troubleshooting › MSMTC Fails with RC=100

MSMTC Fails with RC=100

Symptom:

The MSMTC job fails with RC=100 (MAXCC=100) after the job is started.

For example:

04.30.18 JOB00480 $HASP165 MSMTC    ENDED AT SYSSERV1  MAXCC=100 CN(INTERNAL)

The STDMSG output contains the following message:

JVMJZBL2007E Stack trace follows:
java.lang.NoClassDefFoundError: org.apache.catalina.startup.Bootstrap
Caused by: java.lang.ClassNotFoundException: org.apache.catalina.startup.Bootstrap

Note: The STDMSG output may not be a part of MSMTC JOBLOG. The following statement in RunTimeMVSHLQPrefix.JCL(MSMTCSRV) manages it:

//   ARGS=’start 1>stdout 2>stdERR',   <-- Args to Java class

If ARGS=’’, STDMSG is created.

Reason:

The first step of the MSMTC job is to start the CA CSM application server that is located in RunTimeUSSPath/tomcat.

When RunTimeUSSPath is empty, this step fails with RC=100. A possible reason for RunTimeUSSPath being empty is that the file system belonging to this folder is not mounted.

Solution:

Mount the file system to RunTimeUSSPath and verify that other file systems are properly mounted.
Contact CA Support.

Note: For more information about USS path setup, see the appendix CA CSM Implementation and Status in the Administration Guide.