Using Java 7 with CA MSM Version 5.0 and Previous Versions

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

1.0 Introduction

2.0 Using Java 7 with CA MSM Version 5.0 and Previous Versions
2.1 You have an older CA MSM version than V5.0 and a previous Java version
2.2 You have CA MSM V5.0 and a previous Java version
2.3 You have an older CA MSM version than V5.0 and have already upgraded to Java 7
2.4 You have CA MSM V5.0 and have already upgraded to Java 7

3.0 Appendix
3.1 Apply the PTF
3.2 Reassign the Java Home Directory

1.0 Introduction

Product: CA Mainframe Software Manager™ (CA MSM)

Version: 5.0

OS: z/OS

The following scenarios are for customers who want to runCA MSM V5.0 on Java 7. CA MSM V5.0 still supports Java 6and upgrading to Java 7 is not mandatory. Previous versionsof CA MSM do not support Java 7 and require you to upgradeto CA MSM V5.0 to use Java 7.

Support for Java 7 is delivered in PTF #RO52356 (containingCA MSM V5.0 Build 58) and every PTF going forward. You canuse CA MSM 5.0 to apply the PTF on Java 7. However, otherfunctionality is not supported on Java 7 on builds prior toCA MSM 5.0 build 58.

2.0 Using Java 7 with CA MSM Version 5.0 and Previous Versions

The steps you need to perform may vary based on yoursituation. Find the following scenario that best fits yoursituation.

• You have an older CA MSM version than 5.0 and a previousJava version.
  
  
• You have CA MSM V5.0 and a previous Java version.
  
  
• You have an older CA MSM version than V5.0 and have alreadyupgraded to Java 7.
  
  
• You have CA MSM V5.0 and have already upgraded to Java 7.

2.1 You have an older CA MSM version than V5.0 and a previous Java version

Follow these steps:

1. Upgrade to CA MSM V5.0.
   
   
2. Apply the PTF.
   
   
3. Upgrade to Java 7.
   
   
4. Reassign the Java home directory.

Note: Use the correct JVM load module version in thestartup job:

• JVMLDM70 for 31-bit Java 7.0
  
  
• JVMLDM76 for 64-bit Java 7.0

You can now use CA MSM on Java 7.

2.2 You have CA MSM V5.0 and a previous Java version

Follow these steps:

1. Apply the PTF.
   
   
2. Upgrade to Java 7.
   
   
3. Reassign the Java home directory.

Note: Use the correct JVM load module version in thestartup job:

• JVMLDM70 for 31-bit Java 7.0
  
  
• JVMLDM76 for 64-bit Java 7.0

You can now use CA MSM on Java 7.

2.3 You have an older CA MSM version than V5.0 and have already upgraded to Java 7

Follow these steps:

1. Upgrade to CA MSM V5.0.
   
   Note: When running the installer application, use yourexisting Java 7 environment.
   
   Use the correct JVM load module version in the startup job:
   
   
   • JVMLDM70 for 31-bit Java 7.0
     
     
   • JVMLDM76 for 64-bit Java 7.0
     
     
2. Apply the PTF.

You can now use CA MSM on Java 7.

2.4 You have CA MSM V5.0 and have already upgraded to Java 7

Follow these steps:

1. Reassign the Java home directory.
   
   
2. Apply the PTF.

Note: Use the correct JVM load module version in thestartup job:

• JVMLDM70 for 31-bit Java 7.0
  
  
• JVMLDM76 for 64-bit Java 7.0

You can now use CA MSM on Java 7.

3.0 Appendix

3.1 Apply the PTF

Follow these steps:

1. Apply the cumulative PTF.
   
   
2. Stop CA MSM.
   
   
3. Run the MSMDEPLY job to deploy the maintenance package tothe CA MSM run-time libraries and USS paths.
   
   
4. Start CA MSM.

Note: For more information about applying a maintenancepackage to CA MSM, see Apply Maintenance to CA MSM in theAdministration Guide.

3.2 Reassign the Java Home Directory

You may want to reassign the Java home directory, forexample, when you install a new minor version of Java intoa different directory to preserve the old version. When youchange the Java directory, you must correct the Java pathin the following places:

• Change the value of the JAVA_HOME variable In theSAMPLIB(MSMLIB) member.
  
  Example: In the following sample SAMPLIB(MSMLIB) member,replace original_path with the new path.

      export JAVA_HOME=original_path

• Change the SMPJHOME DDDEF value in the CA CSM CSI thatpoints to the Java home directory. The CA CSM CSI islocated in CSIHLQ.SMPCSI.CSI. Change the SMPJHOME DDDEFvalue in the global (GLOBAL), target (CAIT) anddistribution (CAID) zones. Use the UCLIN statement tochange the SMPJHOME DDDEF value.
  
  Example: Use this UCLIN statement to change the SMPJHOMEDDDEF value for all CA CSM CSI zones by replacing the zonevariable with each zone name: CAID, CAIT and GLOBAL.

      SET    BOUNDARY(zone).    UCLIN.    REP  DDDEF(SMPJHOME)         PATH('new_path').    ENDUC.

Note: Once you start the MSMTC job, the JAVA_HOME path inthe job log message has to match the path in the SMPJHOMEDDDEF in the CA CSM CSI:

JVMJZBL1006I JAVA_HOME = new_path

• Change the JAVAPATH option in theMSMSetupOptionsFile.properties option file located in theMSMPATH/CEGPHFS directory.

  Example: In the following MSMSetupOptionsFile.propertiesoption file sample, replace original_path with the new path.

      JAVAPATH=original_path

Environment

Release:
Component: MSM