Chorus Software Manager fails to initialize. Does not abend
search cancel

Chorus Software Manager fails to initialize. Does not abend

book

Article ID: 41274

calendar_today

Updated On:

Products

Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

 

Issue: 

A Systems Programmer started the Chorus Tomcat Server ( CSMTC is the default name ) and it never completes initialization. The following message is never issued:

MSM0013I CA CSM STARTUP INITIATED

 

Furthermore the task would not respond to an operator command for a STOP or CANCEL producing error:

IEE342I STOP / MODIFY COMMAND REJECTED TASK BUSY


As a result the task had to be forced off the system.

 

Environment:  

z/OS any release, Chorus Software Manager any release, JAVA any release.

 

Cause: 

The cause was due to the fact that the Systems Programmer had edited the member (eg. MSMLIB) pointed to in the CSMTC PROC by the STDENV DDNAME .
They had added a JAVA variable but had left off the trailing double quote.

In this case the variable was:

IJO="$IJO -DCSM_SIS.SYSPRINT.DEFAULT.CYLINDERS=number_of_cylinders

 

But be aware it could have been any JAVA variable being defined and having the closing double quote character missing. Carefully review any modifications to ensure the syntax matches other statements of similar type.

 

Resolution/Workaround:

Add the closing quote and recycle the MSMTC task. You may have to force the task off the system.

 

Additional Information:

For more information on the IEE342I message please see:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieam700/m011389.htm

For more information on the Chorus Software Manager JAVA variable mentioned please see:
https://support.ca.com/cadocs/0/CA%20Chorus%20Software%20Manager%206%200-ENU/Bookshelf_Files/HTML/CSM_V60_TroubleshootingGuide_ENU/index.htm?toc.htm?2366117.html

Environment

Release: MSMNGR00200-5.1-Chorus Software Manager
Component: