gtpa1m0dACF/SNA Network Generation

Considerations for Defining Records for SNA Structures

The following information describes some SNAKEY-related considerations for defining the records for the SNA structures.

#NCBRI and #SPARI Records

#NCBRI and #SPARI records are used only by resources that are defined using the OSTG program. Therefore, the number of #NCBRI and #SPARI records allocated during SIP must be equal to or greater than the number of resources that you plan to define using the OSTG program.

You can also use the ZNDYN ADD command and dynamic LU support to define resources to the TPF system. Resources defined using the ZNDYN ADD command or dynamic LU support do not use #NCBRI and #SPARI records.

See the following for more information:

#CCBRU Records

Enough #CCBRU records must be allocated during system initialization program (SIP) processing to hold all the conversational control block (CCB) entries defined by the MAXCCB parameter. The minimum number of records can be determined by the following formula:

   Number of CCB entries × Length of CCB entry
   ------------------------------------------------
                       4079

Where:

 Number of CCB entries 
is the value specified for the MAXCCB parameter.

 Length of CCB entry 
is defined in data macro ICCB.

 4079 
is calculated as follows: 4 KB - header size.

The #CCBRU fixed file records are used to keypoint (update) the CCB main storage control blocks.

#RV1RU and #RV2RU Records

Enough #RV1RU and #RV2RU records must be allocated during SIP processing to hold all the resource vector table (RVT) entries defined by the MAXRVT parameter. The minimum number of records can be determined by the following formula:

   Number of RVT entries × Length of RVT entry
   ------------------------------------------------
                    4079

Where:

 Number of RVT entries 
is the value specified for the MAXRVT parameter.

 Length of RVT entry 
is defined in data macros RV1VT and RV2VT.

 4079 
is calculated as follows: 4 KB - header size.

#SRTRU Records

Enough #SRTRU records must be allocated during SIP processing to hold all the system recovery table (SRT) entries defined by the MAXSRT parameter. The minimum number of records can be determined by the following formula:

   Number of SRT entries × Length of SRT entry
   ------------------------------------------------
                       4079

Where:

 Number of SRT entries 
is the value specified for the MAXSRT parameter.

 Length of RVT entry 
is defined in data macro SR0RT.

 4079 
is calculated as follows: 4 KB - header size.

#SC1RU and #SC2RU Records

Enough #SC1RU and #SC2RU records must be allocated during SIP processing to hold all the session control block (SCB) entries defined by the MAXSCB parameter. The minimum number of #SC1RU records can be determined by the following formula:

   Number of SCB entries × Length of SCB1 entry
   -------------------------------------------------
                    4079

Where:

 Number of SCB entries 
is the value specified for MAXSCB + 1 for the SCB anchor.

 Length of SCB1 entry 
is defined in data macro ISCB.

 4079 
is calculated as follows: 4 KB - header size.

The minimum number of #SC2RU records can be determined by the following formula:

   Number of SCB entries × Length of SCB2 entry
   -------------------------------------------------
                    4079

Where:

 Number of SCB entries 
is the value specified for the MAXSCB parameter.

 Length of SCB2 entry 
is defined in data macro ISCB.

 4079 
is calculated as follows: 4 KB - header size.

The #SC1RU and #SC2RU fixed file records are used to keypoint the SCB main storage control blocks.

#RT1RI and #RT2RI Records

Enough #RT1RI and #RT2RI records must be allocated during SIP to hold all the rapid transport protocol control block (RTPCB) entries defined by the MAXRTPCB parameter. See TPF ACF/SNA Data Communications Reference for information about how many of these records to define.