gtpa1m0hACF/SNA Network Generation

OSTG Data Sets

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.

OSTG EXEC PARM Field

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:

CPUID
Required. Specify the processor for which the table generation is being performed. When generating a loosely coupled complex, this must be the ID of the first processor specified in the loosely coupled complex. The processor ID that is specified must be the same as the processor ID specified in the ANTDEF statement. The processor ID is a 1-character alphanumeric value from A-Z or 0-9.

DESC
Optional. Specify a description (as many as 25 bytes) for the OSTG input data sets. This description is included in the information that is displayed when you enter the ZNOPL STATUS command. See TPF Operations for more information about the ZNOPL STATUS command and an example of the information that is displayed.

SDPSID
Required for a loosely coupled system. This parameter specifies the IDs of all the TPF processors in a loosely coupled complex. The processor ID is a 1-character alphanumeric value from A-Z or 0-9. The value is specified as a list of processor IDs separated by commas, as a range of processor IDs with the first and last processor ID separated by a dash, or as a combination of the two. The following code examples are equivalent:
SDPSID=(A,C,D,E,F,H,J)
SDPSID=(A,C-F,H,J)

Notes:

  1. The value coded for the SDPSID parameter in the OSTG EXEC statement PARM field must contain the same processor IDs in the same order as coded in the SDPSID parameter in the ANTDEF statement.

  2. OSTG will consider SDPSID=(A,C-F)coded in the OSTG EXEC PARM field to be the same as SDPSID=(A,C,D,E,F) coded in the ANTDEF statement. Because of a JCL restriction of 100 characters for the PARM field, OSTG allows the use of the dash (-) to indicate a range.

PILOTID
Required. Specify the 1-character pilot tape or GDS identification code.

GENTYPE
Optional. Specify VAL to perform a validation-only run, which reads and processes all of the input statements. Only an output report is created during a validation-only run. Specify GEN to request a full OSTG run, which creates the output files only if no S-level or E-level errors are found. The default value is GEN.

SUBAREA
Required for PU 5 support; otherwise optional. Specify the subarea of the generating processor; that is, the processor specified for the CPUID parameter. This value can be from 1-255.

Notes:

  1. The optional SUBAREA parameter is used to determine if the TPF system will support PU 5. If this parameter is omitted, the TPF system will only support connections to the SNA network as a PU 2.1 link station.

  2. For PU 5 support, the correlation between subarea and processor ID for the generating processor is determined from this information in the EXEC PARM field. The correlation between subarea and processor ID for other TPF processors is determined from the CDRM statements that must be provided to the OSTG program in the RSC deck. See CDRM Statement for more information.

See Figure 16 for an example of the PARM field.

Input Data Sets

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:

  1. ANT deck
  2. RSC deck
  3. ALS deck.

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:

Output Data Sets

The output of the OSTG program consists of the SNA configuration data on either a pilot tape or a GDS, and various reports.

SNA Configuration Data

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.

OSTG Reports

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.

Input List Report

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:

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.

Update List Report

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.

LEID List Report

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.

Duplicate Node Name List Report

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:

Subarea Report

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.

PSV Report

This report lists all of the PSV routines that are defined in the TPF system.

Intermediate Work Data Sets

The intermediate work data sets consist of the intermediate RRT work files and the SORT work files.

Intermediate RRT 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.

SORT Work Files

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.