gtpo1mhu | Operations |
Input to the system test compiler (or the SDMU) can be loaded to disk. If a tape or a disk is used to load the input, the input is always in card image format.
The SDMF resides permanently on tape. After the SDMF is loaded to a unit test disk, the disk can be set aside and used as SDMF input for subsequent runs.
The DRIL normally resides on tape. After the DRIL is loaded to a work disk, the tape can be set aside and used for subsequent runs.
If the input to the system test compiler (or the SDMU) is on a tape rather than on control cards, CARDIN must be assigned to the input tape. The input tape contains all the system test compiler (or the SDMU) control cards and all the control cards required to generate the test unit in card-image format. Make sure that you include the END card.
The SDMF/DRIL work disk contains the SDMF and the DRIL. Areas on this disk that are available for the system test compiler are specified on the LOAD ADDRESS cards. This disk can be any supported direct access storage device. (See TPF Migration Guide: Program Update Tapes for a list of supported devices.) The SDMU stores any new records that it creates on this disk.
The object library data set contains the system test compiler programs that will be loaded into core. It also contains the application programs that are called by the RUNID test units.
The system allocator table (SALTBL) contains the information required by the TPF linkage editor to resolve virtual address constants (VCONs). See TPF System Installation Support Reference for more information about the SALTBL.