gtpa1m0h | ACF/SNA Network Generation |
OSTG data sets consist of the input data set, several output data sets, and several work data sets, each of which is described in the following sections.
As a general rule, the logical record length (LRECL) for all of the data control blocks (DCBs) are defined in the OSTG program. The block size (BLKSIZE) and record format (RECFM), however, are usually not defined on the program DCB, which allows you to specify this information on the JCL DD statements for the data sets.
The OSTG program uses the PARM field of the JCL EXEC statement to provide important information that is used to control the OSTG processing. The PARM field contains the following parameters:
SDPSID=(A,C,D,E,F,H,J) SDPSID=(A,C-F,H,J)
Notes:
Notes:
See Figure 16 for an example of the PARM field.
The OSTG input data set (DDNAME=STGINP) contains all of the input definition statements. This data set is read sequentially by the OSTG program and broken logically into 3 decks, which must be processed in the following order:
The input definition statements can reside in separate data sets, either as members of partitioned data sets (PDS members) or as one or more sequential data sets. In any case, these input definition statements must be provided to the OSTG program as a sequential file. See Figure 16 for an example of how to concatenate the various data sets together as one sequential data set.
See the following for more information:
The output of the OSTG program consists of the SNA configuration data on either a pilot tape or a GDS, and various reports.
The data records created by the OSTG program are written to a system pilot tape or GDS. The 1-character name (such as PILOT S) associated with these records is assigned by you using the PILOTID parameter in the PARM field of the JCL EXEC statement. This character is used to load the SNA data records to the online TPF system using the ZNOPL LOAD command. For more information about the ZNOPL LOAD command, see TPF Operations. The offline program CNVNNR1 is a service routine that
uses these files for the conversion process.
The OSTG program produces the following reports, which are all written to the same data set (DDNAME=SYSOUT):
See Sample OSTG Reports for examples of the OSTG reports.
This report lists all the input definition statements and any information or error messages that occurred.
Error messages are listed following the input definition statement where they occurred. Each error message contains a severity code, which can be one of the following:
An S-level error causes the OSTG program to be canceled. Any additional processing normally performed by the OSTG program will not occur. You must correct all of the S-level errors and then rerun the OSTG program.
An E-level error indicates that an error was detected that invalidates any attempt to produce output. The OSTG program attempts to continue processing; however, no output is produced. You must correct all of the E-level errors and then rerun the OSTG program.
A W-level error indicates that the OSTG program detected a condition that may not give the results you intended. The OSTG program continues to process and attempts to produce output. Review all W-level errors to ensure proper results.
I-level messages are strictly informational. They advise you of actions or processes that occurred. Review I-level messages to ensure that the OSTG program produced the correct results.
Severity S and E errors are offset from severity W and I messages to help you isolate these messages. See Messages (System Error and Offline) and Messages (Online) for a complete list of all OSTG error messages.
This report shows all of the resources that were defined using the OSTG program and the value of the relevant parameters for each resource. The resources are ordered on the update list report in the sequence that they will be loaded online. This report may also list additional errors found in the input definition.
This report is produced if the LEID parameter was specified on any RSC statement. All resources defined with an LEID are listed in LEID sequence and any duplicate LEIDs are flagged.
This report is produced if any duplicate node names were found. It lists all of the duplicate node names that were found by the OSTG program. A node name is considered a duplicate node name if one or more of the following conditions exist:
This report is produced only if PU 5 support was included in the TPF system. It lists the SAT tables in order to provide you with enough data to get a full perspective of the TPF network.
This report lists all of the PSV routines that are defined in the TPF system.
The intermediate work data sets consist of the intermediate RRT work files and the SORT work files.
SORTIN and SORTOUT are the data sets used to hold the intermediate resource resolution table (RRT) records. These files are used by each of the various OSTG CSECTs to pass information, as well as by the SORT package.
These files must be large enough to handle one RRT entry for each resource defined using the OSTG program. The space allocation depends on the blocking factor used, the number of resources defined, and the type of device used. The logical record length is specified in the DCB macro that defines the data set. (The size of an RRT record is 4 KB.)
See Figure 16 for sample definitions of the SORTIN and SORTOUT data sets.
The SYSUT1, SYSUT2, and SYSUT3 data sets are work files required by the SORT program. See the appropriate SORT manual for estimating the required size of these data sets.
See Figure 15 for sample definitions of the SYSUT1, SYSUT2, and SYSUT3 data sets.