gtps4m3m | System Generation |
The following summarizes the various types of output that result from stage
II. See Appendix C, SIP Stage II Job Summary for the order and complete description of the stage II job
stream.
- Source code for keypoints, table label records, macros, and others created
by SIP will exist in ACP.SYSRCE.RELvv and
ACP.SYMACRO.RELvv data sets, respectively.
- Because stage II uses a multiple assembler/compiler (see TPF System Installation Support Reference for more
information about the multiple assembly/compilation program), the assembly and
compilation listings for all error-free programs will be on a tape when the
LISTAPE parameter of the GENSIP macro is used. You can then request a
specific listing as provided in TPF System Installation
Support Reference.
- The ANTDEF input statements generated by SIP for the OSTG program will be
put into the data set named by the ANTPDS parameter on the GENSIP
macro. (See TPF ACF/SNA Network
Generation.)
- Applicable object and load modules for all segments contained in SPPGML
will exist in respective object and load module libraries. On a WTC
system this will include the real-time program segments listed in SPIPML and
the offline components listed in SPWTC.
- A list for this release named PARSvv and located in data set
ACP.SYSRCE.RELvv is generated. This list is then
referenced in the load deck described previously. It will include all
segments listed in SPPGML as real-time segments, except for those segments
that need be loaded only once. For WTC systems, a second list will be
generated containing all the IPARS real-time program segments as defined by
SIP internal macro SPIPML. IBMPAL macros and any user allocator
decks.
- An allocator table will exist in data set
ACP.SALTBL.RELvv.
- A load deck is generated and listed during stage II as member LOADDECK of
data set ACP.SYSRCE.RELvv. This deck is run against ALDR
to create the loader general file (LGF).
- Loader general file DASD will be ready for executing the load deck.