JAVA Version Change Impact to MSM

book

Article ID: 50038

calendar_today

Updated On:

Products

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

Issue/Introduction

Description:

When the JAVA version is changed several members need to be updated to reflect the new JAVA version and path.

Solution:

The PGM= statement in the MSMTC procedure needs to be changed to reflect the new program name for the new release of the JAVA Loader program. The JAVA_HOME= statement needs to be changed in the MSMHLQ.SAMPLIB(MSMLIB) to reflect the new path name.

Environment

Release:
Component: MSM