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

Products

• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• Common Services

Issue/Introduction

 

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.

 

Environment

Release:
Component: CCIMVS

Resolution

 

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.