Changing the JAVA path in CA Mainframe Software Manager


Article ID: 52578


Updated On:


CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom CA DATACOM - AD 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



When there are changes in your JAVA path on your USS partition because of new releases, or other naming conventions, it is needed to make this known to CA Mainframe Software Manager and his tasks too.

This document describes how this can de done.


You will need to change the properties file with the new path, but also the path specified in the MSMTC (CA Mainframe Software Manager Tomcat Server) task in the STDENV DD statement. In the STDENV DD statement is a PARMLIB/SAMPLIB member specified, by default called MSMLIB. Also this member needs to be changed regarding the JAVA path.

After the change the MSMTC STC needs to be recycled and the new values will be taken into consideration.

If you don't change the STDENV DD statement specified member you will experience the below error message at MSMTC startup:
CEE3501S The module was not found.

From entry point JzosVM::initializeVMArgs() at compile unit offset
+0000008E at entry offset +0000008E at address 18403AD6.


Component: MSM