Command Propagation Facility › About CPF › CPF Architecture › Defining CPF nodes

Defining CPF nodes

CPF nodes are defined as CPFNODE elements on the NDT system record in the CA‑Top Secret security file. CPF nodes are grouped on the NDT record by system id, to allow multiple CA‑Top Secret systems use separate CPF node definitions. For downward compatibility, this release of CA‑Top Secret, will also support defining CPF nodes using the CPFNODES control option. Once a CPF node is defined to the NDT record, a control option definition for the same node name is ignored.

CPF node definitions in the NDT record can be created or modified at any time after CA‑Top Secret starts up. The START & REFRESH commands described later in this chapter are used to activate newly defined CPF nodes, or to apply new processing options to existing active CPF nodes. When refreshing an individual node, CPF processing for other nodes is not interrupted.

The following example shows how to set up the NDT CPFNODE definitions for system SYS1, to allow sending and receiving CPF commands and passwords to remote system SYS2:

TSS ADD(NDT) CPFSYSID(SYS1) RECVCMDS(YES) CPFTARGET(LOCAL)

TSS ADD(NDT) CPFSYSID(SYS1) CPFNODE(SYS2) JOURNAL(YES) RECEIVE(ALL)  SEND(ALL)

Note: If all CPF related control options are migrated from the control options parameter file to the NDT, control option CPF(ON) or CPF(OFF) is required in the parameters file for CPF to initialize using the NDT based definition. If neither is specified, CPF will not initialize and cannot be activated unless CA‑Top Secret is recycled. CPF(ON) activates CPF as soon as CA‑Top Secret is started up. CPF(OFF) will start CA‑Top Secret with CPF inactive, however, CPF may be later activated via a TSS MODIFY(CPF(ON)) command.

Note: Adding a new CPF node to an active CA‑Top Secret system, also requires adding a NODE definition to CAICCI.