gtpa1m0j | ACF/SNA Network Generation |
Remember the following when using the OSTG program to define resources to the TPF system.
Only resources defined using the OSTG program can have a scratch pad area (SPA). Resources defined using the ZNDYN ADD command and dynamic LU support do not have a scratch pad area.
You can, however, assign spare SPA ordinals to the dynamic LUs using the dynamic LU user exit. For a dynamic LU, the ordinal saved at RV1ORDN only means the SPA ordinal and cannot be used as an NCB ordinal. You can use the CSNB segment to access the SPA record. However, the SPA fixed file record must be initialized before calling the CSNB segment. Without doing so, the CSNB segment sets an error return code and returns to the calling segment.
See TPF Operations for more information about the ZNDYN ADD command. See TPF ACF/SNA Data Communications Reference for more information about dynamic LU support and defining resources to the TPF system.
Enough #RRTRI records must be allocated during SIP to hold the following records and allow for future expansion:
The minimum number of #RRTRI records required can be determined by using the following formula:
2(# of resources (highest RID from OSTG) + 2(first entry and last entry)) 1 (extra entry + ------------------------------------------------------------------------- for PSVNT) RR0ENT(size of each # of RRT entries per record from RR0RT DSECT)
When preparing input for the OSTG program, consider the resource definitions that exist in other components of the network, specifically, in the NCP and VTAM system generations. Resource definitions must be compatible across all network components.
The ZNDLU command can be used to display information about resources that have a common string of characters in their resource name. Therefore, when using the RSC statement to define resources, consider assigning resource names in such a way that resources with similar characteristics share names with a common string of characters.
For example, if you prefix all of the names for New York City Ticket Counter resources with NYC, you can enter ZNDLU ID-NYC* to display information about all of these resources.
See TPF Operations for more information about the ZNDLU command.
This section is significant only when the TPF system is running in LEN mode. If the TPF system is running in APPN mode, ALS and CTC qualifiers are not used and do not need to be defined. ALS qualifiers are not used for non-37x5 connections.
The QN and ALSQN parameters on the ALS input definition statement of the OSTG program define alias names to the VTAM Logon Manager for TPF applications. If a TPF system will connect to multiple 37x5 devices as an ALS, the TPF applications must appear unique to each ALS. This is done by defining the TPF applications in the NCP generation in the following format:
aaaacqq
where:
The QN parameter on the CTC statement serves the same purpose. TPF applications must appear unique across each CTC connection. This is done by defining the TPF applications to VTAM as CDRSCs under the TPF CTC CDRM in the following format:
aaaacqq
where:
The LUTYPE=ANY option on the RSC statement allows you to define the cross-domain resources of the SNA network with little or no knowledge of the real attributes or topology of the network configuration. It also allows you to easily predefine resource names that do not yet exist in the network configuration. This can significantly reduce the number of times that you must rerun the OSTG program and reload the SNA configuration data to the TPF system to reflect changes in the network.
Specifying LUTYPE=ANY for a resource simply defines a resource name to the TPF system. The characteristics or attributes of the resource are determined when the resource requests a session with a TPF application. The RVT entry of the resource that is defined as LUTYPE=ANY is updated using the information in the suggested BIND image, which is part of the CDCINIT (PU 5 support) or SESINIT (PU 2.1 support) request.
When the session of a resource defined as LUTYPE=ANY ends, the updated information in the RVT entry is removed. This allows subsequent sessions for this resource to be started with a different suggested BIND image, which allows the resource to appear as different device types at different times.
The system defaults for the various RSC parameter values depend on the values specified for the LUTYPE and CCTYPE parameters. You can use the RSCSET statement to override these system defaults.
Any valid parameter value specified on the RSCSET statement is applied to all subsequent RSC statements until either another RSCSET statement with the same parameter is found in the input data set or until the RSCEND statement is found. Coding the RSCSET statement with a valid parameter value is treated as if the parameter value was explicitly coded on each of the subsequent RSC statements.
In certain cases, the OSTG program imposes values for certain parameters. This occurs whether the parameter value is explicitly coded on the RSC statement or implicitly included by the effects of an RSCSET statement. When a parameter value is imposed, an informational message is included in the input list report.
Table 2 and Table 3 shows the valid combinations for the LUTYPE and CCTYPE parameters. The following list is of incompatible combinations, which are flagged as an error.
SCSBUF=4K is valid only if LUTYPE=3287 or LUTYPE=3289 is specified. SCSBUF is ignored unless LUTYPE=3287 or LUTYPE=3289 is specified.
The MODE parameter is ignored if the value specified for the CCTYPE or LUTYPE parameter is not valid.
Table 2. SNAKEY Macro - Minimum, Maximum, and Default Values
PARAMETERS | CCTYPE | ||||||
---|---|---|---|---|---|---|---|
3274 3276 |
3274 3276 | 3271 | 3271 |
3601 3602 |
3601 3602 |
3601 3602 | |
LUTYPE | |||||||
3277 3278 |
3284 3286 3287 3288 3289 |
3277 3278 |
3284 3286 3287 3288 3289 | 3614 | 360x | BATCH | |
RECVRY | YES | N/A | YES | N/A | N3 | Y1 | N3 |
LUMOD | YES | YES | YES | YES | N/A | N/A | N/A |
SCSBUF | N/A | N4 | N/A | N/A | N/A | N/A | N/A |
THREAD | N1 | N1 | N1 | N1 | N2 | Y1 | N1 |
IATA | YES | YES | YES | YES | N/A | N/A | N/A |
UMODE | YES | YES | YES | YES | YES | YES | YES |
MODE | N/A | N5 | N/A | N/A | N/A | N/A | N/A |
PSV | YES | YES | N/A | N/A | YES | YES | N/A |
AWARE | YES | YES | YES | YES | YES | YES | YES |
CHAIN | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
LEID | YES | YES | YES | YES | YES | YES | YES |
PRSHR | N/A | YES | N/A | YES | N/A | N/A | N/A |
Table 3. SNAKEY Macro - Minimum, Maximum, and Default Values (Continued)
PARAMETERS | CCTYPE | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | |
LUTYPE | ||||||||||||||
APPL PLU | APPL SLU | NEF | ANY | L6PLU | L6SLU | APPC | FMMR | MCHLU | VCLU | AX001 | AX002 | XALCI | FTPI | |
RECVRY | YES | YES | N/A | N/A | N3 | N3 | N3 | N/A | N3 | N3 | N3 | N3 | N/A | N/A |
LUMOD | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
SCSBUF | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
THREAD | N1 | N1 | N/A | N/A | N1 | N1 | N1 | N/A | N2 | N2 | N2 | N2 | N/A | N/A |
IATA | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
UMODE | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES | N/A | N/A |
MODE | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
PSV | N/A | N/A | YES | YES | N/A | N/A | N/A | N/A | YES | YES | YES | YES | YES | YES |
AWARE | YES | YES | YES | YES | N/A | N/A | N/A | YES | YES | YES | YES | YES | YES | YES |
CHAIN | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | YES | N/A | N/A | N/A | N/A |
LEID | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES | N/A | N/A |
PRSHR | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |