How to run MSM on a different LPAR?


Article ID: 49438


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



Do you need to move CA MSM to a different LPAR? The following instructions will help you accomplish the task.


  1. This is only for moving CSM between LPARs that are sharing the same file systems.
  2. The CSM base USS file systems are mounted on the system where CSM will be moved
  3. Ensure that Settings -> System Settings -> Mountpoint Management -> Unmount at Shutdown is enabled
  4. Update hostname and dsi port in SAMPLIB(DBINIT) for the target LPAR.
  5. Update hostname and dsi port in /.../msmruntime/dsi/dsi.conf for the target LPAR. Note that the new path for /.../msmruntime/dsi/dsi.conf on the target LPAR should be assigned to dsiConf= in item 4 above.
  6. Modify the following xml files located at .../msmruntime/tomcat/conf: (These are ASCII files so Edit ASCII option will have to be used)
  7. For CSM 6.0 and 6.1 update the TCPIP_HOST= parm in CUSMAC(SRVLIB) with the new IP address. CUSMAC(SRVLIB) is referenced on the MSMDBSVS startup JCL on the SYSIN DD.

    1. Context.xml
      1. SystemID=????????
      2. HostName=???????   
    2. Server.xml (only if port numbers will need to change)
      1. Server port="?????"
      2. Connector connectionTimeout="20000" port="?????" .... redirectPort="?????"
      3. Connector port="?????"


The best way to edit is to use ISPF Edit change command rather than direct edit.

Also, you can pre-define these files for each LPAR where MSM will run and simply rename them to original name (context.xml and server.xml) when you move MSM.

For example, let's say you have two MSM eligible LPARS, SYSA and SYSB:

context.xml.SYSA and server.xml.SYSA
context.xml.SYSB and server.xml.SYSB
context.xml and server.xml - created during initial MSM installation

You would copy the LPAR specific files to original names before starting MSM on the respective LPAR.


Release: MSMNGR00200-5.1-Chorus Software Manager