ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Setting up CCI for MSM deployment

book

Article ID: 49574

calendar_today

Updated On:

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 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