Control program keypoints

Control program keypoint records are used to initialize the system during restart and the file copy is updated whenever the core image counterparts are modified by the control program or by a command program.

Table 1. Control program keypoints
Keypoint Macro name Function Processor SS Initialized by Residency Demand keypointable Size
Record A (CTKA) CK1KE Contains information required for system loading and for the initializer program. Unique Unique SIP File No >4 KB
Record B (CTKB) CK9KC Miscellaneous initialization and restart values, for example, clock status, VFA status, and DASD error thresholds. Unique Unique SIP Main storage Yes 4 KB
Record C (CTKC) CK8KE Status of Computer Room Agent Set (CRAS) attached terminals, initial Routing Control Application Table (RCAT) and Terminal Address Table (WGTA) control information. Shared Shared SIP Main storage No 4 KB
Record D (CTKD) CK7KE This keypoint is available for customer use. Shared Unique Customer File Yes (see note 6) >4 KB
Record E (CTKE) CK6KE Describes the non-SNA communications network. Unique Shared SIP File No 4 KB
Record I (CTKI) IC0CK Describes the status of all processors in a loosely coupled complex of the HPO feature. Shared Shared SIP File No 4 KB
Record M (CTKM) MK0CK Describes the status of each subsystem and each subsystem user. Shared Shared SIP Main storage No 4 KB
Record V (CTKV) IDSCKV Contains volume serial number ranges for the online modules, the copy module, and the loader general file. Shared Unique SIP File No 4 KB
Record 0 (CTK0) CK0KE Contains legal disk hardware addresses. Shared Shared SIP File No >4 KB
Record 1 (CTK1) CK2KC Contains the Tape Status Table (TSTB). Unique Shared N/A Main storage Yes 4 KB
Record 2 (CTK2) CK2SN Contains all the information in the system about the SNA configuration and the TCP/IP device parameters. Unique Shared Source and the SIP-generated symbolic device address table (SDAT). Main storage Yes >4 KB
Record 3 (CTK3) None This keypoint is available for customer use. Unique Shared Customer File Yes (see note 6) >4 KB
Record 4 (CTK4) VK4CK This keypoint is available for customer use. Shared Unique Customer File Yes (see note 6) 4 KB
Record 5 (CTK5) None This keypoint is reserved for IBM® use. Shared Shared N/A File No 4 KB
Record 6 (CTK6) CJ6KP Contains the DASD module status indicators. Shared Unique SIP File and main storage (see note 1) No >4 KB
Record 9 (CTK9) CY1KR Contains the status of the DASD pools. Shared Unique Source, contains no SIP provided inputs Main storage No 4 KB
Notes:
  1. The entire keypoint is file-resident; the first section of the keypoint is also main-storage-resident.
  2. Processor shared means that there is one copy of the keypoint for all processors in a loosely coupled environment.
  3. Processor unique means that there is one copy of the keypoint per processor in a loosely coupled environment. These processor-unique records are required before you enter the ZIMAG KEYPT command on a new processor with the MOVE parameter specified.
  4. Subsystem (SS) shared means that there is one copy of the keypoint residing in the BSS in an MDBF environment.
  5. Subsystem (SS) unique means that there is one copy of the keypoint per subsystem in an MDBF environment.
  6. You must update the image pointer record so that the z/TPF system recognizes this keypoint as demand keypointable. To do this, update SIP macro SKCTKX:
    • Turn on the DSCRCD bit, which is located in the CX0DSC byte.
    • Turn off the INDFIL bit in the CX0IN1 byte, if it is not already off.