CAICCI r12 changes the way host name is assigned for a given MVS system.


Article ID: 50216


Updated On:


CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom CA DATACOM - AD 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



Along with the assignment of a unique SYSID, the CCI component also uses the TCP/IP hostname to identify the host on which it resides. On hosts having multiple IP interfaces configured with multiple host names, CCI requires one of these host names be flagged as its primary identifying hostname. In CCS r12 the CCI component assigns its primary TCP/IP hostname for a system from the nodename defined in the VMCF subsystem. The VMCF nodename can be defined either via SYS1.PARMLIB member IEFSSNxx, or through program EZAZSSI, specifying the P=hostname parameter. You should use the MVS system name for the VMCF node name specification.

Because of this change it is important to ensure that the VMCF nodename on each system is correct. An incorrect definition can result in unpredictable results with CA-Solutions attempting CCI function requests.


In the event it is found that this value is incorrect, a temporary solution would be to use the new HOSTNAME(hostname) statement in your CCI PARM member to assign a primary hostname to CCI. This statement would be placed immediately after the SYSID(sysid) statement and would require a restart of the ENF address space to implement.


Component: CCIMVS