How to apply changes to CCI parms
Article ID: 129912
Updated On:
Products
CIS
COMMON SERVICES FOR Z/OS
90S SERVICES
DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
COMMON PRODUCT SERVICES COMPONENT
Common Services
Datacom/AD
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
Compress Data Compression for MVS
Compress Data Compression for Fujitsu
Issue/Introduction
In the process of adding additional NODE statements to an existing CCI parameter file (CCIPARMS).
What is the recommended process to apply these changes? Is just recycling ENF(considering other products rely on ENF) enough, or is an IPL of the system suggested?
A fully operational CCI environment already exists where a number of systems are currently connected. New systems are being added and corresponding NODE and CONNECT statements have been defined to the CCI parameter file.
What is the recommended process to apply these changes? Is just recycling ENF(considering other products rely on ENF) enough, or is an IPL of the system suggested?
A fully operational CCI environment already exists where a number of systems are currently connected. New systems are being added and corresponding NODE and CONNECT statements have been defined to the CCI parameter file.
Environment
- Mainframe z/OS systems
- Any supported release of CA Common Services
Resolution
An IPL is certainly not necessary for this activity. It is also not necessary to recycle ENF to add additional CCI NODES.
New CCI NODES can be added dynamically by issuing the NODE statement at the console.
For example, the command CCI NODE(protocol,netparm,retry,sysid,maxru,start/stop,netparm2) can be issued as a console command. Therefore, whatever new NODE statements you added (or plan to add) to the CCI parameter file, just issue the CCI console command to have it dynamically defined. This can also be done with the CONNECT statement....CCI CONNECT(sysid)
To make changes permanent, remember to define any new statements to the CCI parms so that they are picked up next time ENF is recycled.
Examples: As a console command
CCI NODE(LU0,A73CVC01,01,A73SYSID,4000,START/SHUT)
CCI NODE(TCPSSLGW,USILCA11:1721;SECURE=D,1,ALLSENF)
CCI CONNECT(A73SYSID)
CCI CONNECT(ALLSENF)
Examples: As defined in CCIPARM member (ENFPARMS DD stmt)
NODE(LU0,A73CVC01,01,A73SYSID,4000,START/SHUT)
NODE(TCPSSLGW,USILCA11:1721;SECURE=D,1,ALLSENF)
CONNECT(A73SYSID)
CONNECT(ALLSENF)
New CCI NODES can be added dynamically by issuing the NODE statement at the console.
For example, the command CCI NODE(protocol,netparm,retry,sysid,maxru,start/stop,netparm2) can be issued as a console command. Therefore, whatever new NODE statements you added (or plan to add) to the CCI parameter file, just issue the CCI console command to have it dynamically defined. This can also be done with the CONNECT statement....CCI CONNECT(sysid)
To make changes permanent, remember to define any new statements to the CCI parms so that they are picked up next time ENF is recycled.
Examples: As a console command
CCI NODE(LU0,A73CVC01,01,A73SYSID,4000,START/SHUT)
CCI NODE(TCPSSLGW,USILCA11:1721;SECURE=D,1,ALLSENF)
CCI CONNECT(A73SYSID)
CCI CONNECT(ALLSENF)
Examples: As defined in CCIPARM member (ENFPARMS DD stmt)
NODE(LU0,A73CVC01,01,A73SYSID,4000,START/SHUT)
NODE(TCPSSLGW,USILCA11:1721;SECURE=D,1,ALLSENF)
CONNECT(A73SYSID)
CONNECT(ALLSENF)
Additional Information
Reference the CA Common Services documentation for further details.
For details specific to the CCI NODE control option, click here
For details specific to the CCI NODE control option, click here
Feedback
Yes
No
Powered by
