Changing the JAVA path in CA Mainframe Software Manager

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:

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.

Solution:

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 libjvm.so was not found.

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

Environment

Release:
Component: MSM