How to apply changes to CCI parms
Article ID: 129912
Updated On:
Products
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 Datacom/AD
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 Compress Data Compression for MVS
CA 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
Powered by
