gtps4m3qSystem Generation

Non-SNA Communications

The system communication keypoint (SCK) and processor keypoint status table (PKST) record generation, hereafter called SCK gen, should be run for all communication lines connected to TPF via an EP or PEP communications controller and for 3270 locals. In addition to building the two types of records described below, it also, automatically, builds two System Communication Keypoint Records (SCK) for the prime and RO (receive only) CRAS (Computer Room Agent Set) terminals. Therefore, in the case of a system whose network consists solely of communication lines connected to TPF via a communication controller in NCP mode, with no 3270 locals, this generation need not be run. However, in that case, those two SCK records for the prime and RO CRAS will not be built automatically and should be created by hand, via the System Test Compiler (STC) and pilot tape load.

The SCK gen Phase I input consists of a set of user macros that describe the non-SNA communication network. The output of Phase I is a sequential file containing the network information in STC input format. The SCK gen Phase II consists of running STC with that sequential file as input. The output of Phase II is a non-SNA Communication pilot tape that contains the two record types described below. This pilot tape must be loaded later to the online system via the TPF Data Loader.

The two record types that are produced by the SCK gen are:

SCK
System Communication Keypoints (one record/line)

These contain the status of each communication line attached to the system. They are used at restart time to build core resident communication tables:

Line Status Table (LSTB)

TI Status Table (TITB)

Symbolic Line Status Table (SLST)

PKST
Communication Control Unit Keypoints

These contain the status of each control unit on the system.