Setting up CCI for MSM deployment

book

Article ID: 49574

calendar_today

Updated On:

Products

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

In the CA MSM Administrator Guide is only defined that MSM needs a SYSID and CAS9DCM3 in ENF. (Appendix A, CA Common Services Component Requirements).

However for MSM Deployment and Configuration functions there is needed more.

Solution:

To get the MSM local lpar connected to the remote lpars to do the deploy and configuration, you will need to setup a CCI connection under ENF (CA Common Services component).

This needs to be done with a PROTOCOL, NODE and CONNECT statement.

For samples setup and instructions you need to check the CA Common Services Best Practice Guide.

At CCS v14.0 it's 'Chapter 6: CAIRIM Configuration' who holds the samples.

For a detailed description of the statements, check the CCS Reference Guide (CCS v14.0 Chapter 4: CAICCI Control Options).

Environment

Release:
Component: MSM