gtpp1m0k | Program Development Support Reference |
The following section provides the required format for the input the STC utility uses to create your tape output. The information regarding what options are selected for any given input is described in the appropriate function's chapter. For example, the information to code on the RUNID that pertains to dump processing (keylock condition) is described in Diagnostic Output Formatter (DOF) Online and Offline Utility. RUNID information, which pertains to system tests, is described in Program Test Vehicle (PTV) Online Utility.
Disk allocation records define the set of disk tracks that are formatted with 381 or 1055-byte records on the STC work disk. A maximum of 40 disk allocation cards may be used in a single STC run; 20 for large records and 20 for small records. See TPF Operations for more information about the required format.
Disk type records identify the type of disk pack available to the STC utility for use as a work disk. See TPF Operations for more information about the required format for the system test compiler (STC) utility.
The RUNID record identifies the test unit or pilot system that the STC utility will generate. It must be the first record in the input message stream. The required content of the RUNID depends on the type of run:
For example, the only information required on the RUNID record for a system
test is RUNID in positions 2-6. For package tests, the statements
following each RUNID define the data to generate and any options for the
particular test unit. Subsequent RUNID records mark the beginning of
other test units. The last test unit to be recorded on the TUT must
have an END STC statement as the last record.
Table 2. RUNID Format for Package Tests
Position | Content | Description |
---|---|---|
1 | Blank | Not Applicable |
2-6 | RUNID | Record identification. |
7 | Blank | Not Applicable |
8-12 | XXXXX | Test unit identifier or pilot system identifier. |
13 | X | Database restore indicator. |
14 | X | Pilot system ID number. If you specify an ID of N, the TPF system can be in any state when you use the ZSLDR command to load the pilot tape. If the ID of the pilot tape is not N, the TPF system must be in 1052 state when the pilot tape is loaded. |
15 | X | Subsystem pilot tape use. |
16 | X | Global storage load mode. |
17 | X | Diagnostic output formatter (DOF) screen reset indicator. |
18 - 24 | Blank | |
25 | X | Message input mode. |
26 | X | Number of messages. |
27 | X | Online terminal use. |
28 | X | Running state. |
29 | Blank | Not Applicable |
35-80 | User comments. |
When loading a pilot tape, see Pilot Tape Generation for more information about the RUNID record fields.
Table 3. Terminal Simulation Record Format
Position | Content | Description |
---|---|---|
1 | Blank | Not Applicable |
2-7 | X....X | Device type. |
8-15 | Blank | Not Applicable |
16-80 | X....X | Device addresses. |
Table 4. Dump Option Record Format
Position | Content | Description |
---|---|---|
1 | Blank | Not Applicable |
2-5 | XXXX | Dump option code. |
6-9 | Blank | Not Applicable |
10-14 | XXXXX | Macro or macro group identifier. |
15 | Blank | Not Applicable |
16-72 |
XXXX | Program segment name field. |