gtps4m3r | System Generation |
Before generating the non-SNA communications pilot, the user must have completed designing his communications network. TPF Concepts and Structures offers an overview of network design considerations, as does Data Communications Support. Information entered in SIP macros is passed to the SCK macros via the SYGLBK and SYSETK members in the SYMACRO data set created during SIP execution. This ensures basic integrity between the two generations (e.g., binary synchronous station names and polling/selection sequences are the same in both SIP and SCK generation). SIP stage II must be successfully completed prior to SCK generation.
There are three SCK generation user macros:
The macros must be used together according to the following rules:
SKLNG
SENDG
During Phase I the user coded SCK/PKST macro statements are analyzed for errors. Some errors will prevent SCK/PKST record generation from continuing but in most cases errors will be flagged and processing will continue, using default values wherever possible, to produce an assembly listing and STC input for Phase II. If errors occur in Phase I, they must be resolved according to the instructions for each error as described in Messages (System Error and Offline) before proceeding to Phase II.
Phase II is a straight forward STC run. Before executing STC, the unit test disk, DISK01, should*** be loaded with SDMF and a DRIL file containing at least the following macros:
Output from Phase I can then be used as input (*CARDIN) to STC to produce a non-SNA communications pilot tape (**TAPE1). This tape is later input to the data loader, via a command, to initialize the communications keypoint records on file.