gtpa1m0b | ACF/SNA Network Generation |
The SNAKEY macro defines the TPF SNA configuration. It also contains
parameters for defining Transmission Control Protocol/Internet Protocol
(TCP/IP) support.
This macro contains the information that is initializer dependent as well
as the status and definition of the network. This allows the removal of
the network configuration dependencies assembled in CTIN and provides an
effective procedure for implementing configuration changes.
In a loosely coupled environment, one version of the SNA keypoint is loaded
to each TPF processor. The keypoint actually becomes processor unique
only after it is updated by the TPF processor.
All SNAKEY parameters are optional.
Table 1 shows the minimum, maximum, and default values that are valid
for the keypoint parameters.
Figure 2 shows a sample SNAKEY definition.
Table 1. SNAKEY Macro - Minimum, Maximum, and Default Values
Parameter
| Default
| -----RANGE-----
|
Minimum
| Maximum
|
---|
Table Allocation
|
MAXALS
| 0
| 0
| 255 (See note 1.)
|
MAXCCB
| 0
| 3
| 16777215 (See note 2.)
|
MAXCDRSC
| 0
| 0
| 8388607
|
MAXCTC
| 0
| 0
| 255 (See note 1.)
|
MAXHCT
| 0
| 0
| 65535
|
MAXPCID
| 127
| 127
| 32767
|
MAXPRIM
| MAXRVT/10
| 0
| MAXRVT (See note 8.)
|
MAXRVT
| 0
| 0
| 8388607
|
MAXSCB
| 0
| 0
| 8388607
|
MAXSDD
| 0
| 0
| 80
|
MAXSID
| 0
| 0
| 65022
|
MAXSNF
| 1024
| 1024
| 16384
|
MAXSRT
| 0
| 0
| 32767
|
MAXTPI
| 0
| 0
| 8388607
|
MQITRC
| 1
| 1
| 255
|
NUMALS
| 255
| 0
| MAXRVT (See note 9.)
|
SNSESZ
| 0
| 0
| 255
|
TRACSZ
| 1
| 1
| 255
|
Network Parameters
|
CTCANS
| 30
| 2
| 32767
|
CTCRBFR
| 1
| 1
| 16 (See note 3.)
|
CTCTGANY
| YES
| Yes
|
|
CTCWBFRS
| 1
| 1
| 4080 (See note 4.)
|
DYNTO
| 60
| 0
| 65535
|
FMHDR
| 03,80,00
| 2-16 hex characters
|
|
HARDREC
| NO
| Yes or No
|
|
HPFMMR
| NO
| Yes or No
| (See note 6.)
|
HPRALIVE
| 30
| 1
| 65535
|
HPRMTSIZ
| 0
| 0
| 65535
|
HPRPST
| 60
| 1
| 65535
|
ILWPC
| 0
| 0
| 99
|
ILWPE
| 0
| 0
| 99
|
ILWPF
| 0
| 0
| 99
|
ILWPI
| 0
| 0
| 99
|
ILWPS
| 0
| 0
| 99
|
INREC
| NO
| Yes or No
|
|
LENNETID
| blanks
| 0-8 alphanumeric characters
|
|
LMSCTI
| 60
| 1
| 32767
|
LUBLKT
| 1
| 1
| 100
|
MAXBFRU
| 16
| 1
| 32 (See note 5.)
|
MAXHPRSA
| 0
| 0
| 16777215
|
MAXRTPCB
| 0
| 0
| 2500000
|
MAXSMTB
| 0
| 0
| 5
|
NBLKLU
| 0
| 0
| 65535
|
NETID
| blanks
| 0-8 alphanumeric characters
|
|
OLDAPPL
| NO
| Yes or No
|
|
PARACOS
|
|
| (See note 7.)
|
PIUTAPEQ
| 20
| 20
| 255
|
RECIT
| 2,30
| 1,1
| 255255
|
RECOP
| 900
| 1
| 32767
|
RECOT
| 60
| 1
| 32767
|
RSPTO
| 30
| 1
| 32767
|
RTPRSYNC
| YES
| Yes or No
|
|
RVTCTRL
| 20000
| 0
| 8388607
|
SINGMODE
| TPFLU62
| 0-8 alphanumeric characters
|
|
SLOWTIME
| 100
| 0
| 32767
|
SNAPOLL
| 5
| 1
| 5
|
SNDWN
| 11
| 11
| 32766
|
SNKEY
| 60
| 1
| 32767
|
SNQDPT
| 8
| 8
| 50
|
SNRST
| 12
| 12
| 32767
|
SNSETO
| 0
| 0
| 360
|
TPALLOC
| 180
| 1
| 32767
|
TPRECV
| 180
| 1
| 32767
|
TPWAIT
| 180
| 1
| 32767
|
TRANA
| NO
| Yes or No
|
|
UNITSZ
| 256
| 104
| 4096 (See note 5.)
|
VRRTO
| 10
| 0
| 120
|
TCP/IP Support Parameters
|
MAXASCU
| 0
| 0
| 16777215
|
MAXMATIP
| 0
| 0
| 16777215
|
SOCKSWP
| 0
| 0
| 60 (See note 10.)
|
TCP/IP Offload Support Parameters
|
CLAWADP
| 0
| 0
| 84
|
CLAWFD
| 0
| 0
| 1680000
|
CLAWIP
| 0
| 0
| 6804
|
TCP/IP Native Stack Support Parameters
|
IPMTSIZE
| 0
| 0
| 65535 (See note 11.)
|
IPRBUFFS
| 16
| 8
| 32
|
IPRBUFSZ
| 1024
| 1024
| 4096 (See note 12.)
|
IPTOS
| 0
| 0
| 255 (See note 15.)
|
IPTRCNUM
| 0
| 0
| 10 (See notes 15 and 16.)
|
IPTRCSIZ
| 0
| 0
| 100 (See notes 15 and 16.)
|
MAXIPCCW
| 0
| 0
| 200 (See note 11.)
|
MAXOSA
| 0
| 0
| 30 (See notes 14 and 15.)
|
MAXRTE
| 0
| 0
| 2048 (See note 13.)
|
MAXSOCK
| 0
| 0
| 1048576 (See note 11.)
|
OSABUFF
| 16
| 16
| 64 (See note 19.)
|
Shared SSL Session Support Parameters
|
SSLPROC
| 0
| 0
| 16 (See note 17.)
|
SSLTHRD
| 0
| 0
| 32 (See note 18.)
|
- The sum of MAXALS and MAXCTC must be less than 256. If
MAXRVT=0, MAXALS and MAXCTC will also be set to 0.
- If you specify a value for the MAXCCB parameter, the minimum
value required is 3. The MAXCCB value includes a header and a trailer
conversation control block (CCB) entry. Therefore, the actual number of
CCB entries available is equal to the MAXCCB value minus 2. If you do
not specify a value, the default is 0. This indicates that TPF/APPC
support is not being used.
- The number of 4-KB buffers allocated for channel-to-channel
(CTC) input is sent as part of the exchange ID (XID) values when the CTC link
station is activated. CTCRBFR specifies the number of input buffers per
CTC link.
- The number of 4-KB buffers allocated for CTC output is
determined from the value of CTCWBFRS. The number of 4-KB buffers
actually used for output to a CTC link is determined from the remote node as
part of the XID activation sequence. If the number of output buffers
requested in the XID is greater than the number available, the TPF system
rejects the request for link activation. CTCWBFRS specifies the number
of total output buffers for all CTC links.
- The input area size used by the TPF system to read data from
the 37x5 is determined from the UNITSZ and MAXBFRU parameters.
This size is calculated by multiplying the UNITSZ value by the value of
MAXBFRU. The minimum input area size is 1037 bytes, which is comprised
of the following:
- 4 bytes for a link header
- 6 bytes for a transmission header
- 3 bytes for a request header
- 1024 bytes for the request unit.
Therefore, if the value of MAXBFRU × UNITSZ is less than 1037 bytes,
UNITSZ is set to 1037 / MAXBFRU and rounded up to the next integer.
- The high-performance functional management message router
(HPFMMR) affects a base-only system. HPO systems only use
high-performance FMMR.
- The class of service name used by TPF/APPC parallel sessions
defaults to blank. When the TPF system acts as a PU 5 node and receives
a CDINIT request, a class of service name is returned in the CDINIT response
if it is a TPF/APPC parallel session. A class of service name can be
specified with a string of as many as 8 characters (alphabetic, numeric, #, $,
or @), starting with a nonnumeric character.
- If the value specified for the MAXPRIM parameter is not a
prime number, the value is rounded down to the largest prime number that is
less than the value specified. The same is true when calculating the
default value. If MAXRVT/10 is not a prime number, the default
value is rounded down to the largest prime number that is less than
MAXRVT/10.
- The value of the NUMALS parameter cannot be greater than the
value of the MAXRVT parameter. The default value for the NUMALS
parameter is 255, unless 255 is less than MAXRVT/2. In this case,
the default value is MAXRVT/2.
- If the value specified for the SOCKSWP parameter is zero, the
TCP/IP socket sweeper is disabled. See TPF
Transmission Control Protocol/Internet Protocol for more information
about the socket sweeper.
- The values for IPMTSIZE, MAXIPCCW, and MAXSOCK must all be 0,
or the values must all be greater than 0.
- Valid values for the IPRBUFSZ parameter are 1024, 2048, or
4096.
- If the value for IPMTSIZE, MAXIPCCW, or MAXSOCK is 0, MAXRTE
will also be set to 0.
- If the value specified for the MAXOSA parameter is zero, Open
Systems Adapter (OSA)-Express support is disabled in the TPF system.
See TPF Transmission Control Protocol/Internet
Protocol for more information about OSA-Express support.
- If the value specified for the MAXSOCK parameter is 0, the
IPTOS, IPTRCNUM, IPTRCSIZ, and MAXOSA parameters will also be set to 0.
- If the value specified for IPTRCNUM or IPTRCSIZ is 0, both
parameters will be assigned a value of 0.
- If the value for SSLPROC is 0, SSLTHRD must also be set to
0.
- If the value for SSLTHRD is 0, SSLPROC must also be set to
0.
- Valid values for the OSABUFF parameter are 16, 32, or
64.
- MAXHCT
- Specifies the maximum number of hotcon table (HCT) entries between
relational databases and the TPF Application Requester (TPFAR) feature that
the TPF system maintains. The HCT contains TPFAR communication
parameters that are saved as an entry in the HCT for later use by another
transaction.
Hotcons are described as follows depending on the communication
protocol used:
- A hotcon for LU 6.2 is a TPF/APPC conversation that remains
allocated and active past the completion of the transaction; that is,
active until the SNA session is deactivated or the conversation is deallocated
by the remote transaction program. The TPF/APPC conversation parameters
between TPFAR and the DB2 system are saved in an entry in the HCT. When
another ECB requests a conversation with the same remote application server,
TPFAR reuses the active conversation.
- A hotcon for TCP/IP is a TCP/IP connection that remains active past the
completion of the transaction. The socket descriptors are saved in an
entry in the HCT. When another ECB requests a connection with the same
remote application server, TPFAR reuses the active connection.
The value specified for the MAXHCT parameter must be less than or equal to
the value specified for the MAXCCB parameter -2 plus the value specified
for the MAXSOCK parameter. In addition, the value specified for MAXHCT
should be equal to or greater than the sum of the values specified for the
MAXHC parameter of the ZSQLD command. For more information about the
maximum number of hotcons, see TPF Operations and
the TPF Application Requester User's
Guide.
- MAXSDD
- Specifies the maximum number of structured query language (SQL) database
management systems (DBMS) that are defined to the TPF system by the ZSQLD
command. For more information about the ZSQLD command, see TPF Operations.
- HPRMTSIZ
- Specifies the number of 4-KB frames in the high-performance routing
message table (HPRMT). You can specify a nonzero value for this
parameter only if you also specify a nonzero value for the MAXRTPCB and
MAXHPRSA parameters.
See TPF ACF/SNA Data Communications Reference for
more information about the HPRMT.
- MAXALS
- Specifies the maximum number of channel-attached 37x5 and 3174
controllers that can be physically attached to the TPF system and running at
the same time. This number is used to allocate buffers (CCW areas) and
the session index table (SIT) for each NCP or 3174 Advanced Peer-to-Peer
Networking (APPN) controller. See the description of the MAXSID
parameter for information about determining the size of the SIT.
- MAXCCB
- Specifies the number of conversation control block (CCB) entries that can
be active in a TPF system. The default value of zero indicates that
TPF/APPC is not being used. Values 1 and 2 are not valid.
- MAXCDRSC
- Specifies the maximum number of cross-domain resources by
processor. This parameter is required when the TPF system can connect
to the network as a PU 5 node. The number specified must be equal to or
greater than the sum of the following:
- Number of TPF local applications
- Maximum number of cross-domain sessions you plan to have active at one
time
- Number of cross-domain resource managers that can communicate with the TPF
system as a PU 5 node.
This is the value used to allocate main storage for the network address
table (NAT).
- MAXCTC
- Specifies the maximum number of channel-attached channel-to-channel (CTC)
link stations that can simultaneously be physically attached to the SNA CTC
connection and running.
- MAXHPRSA
- Specifies the number of entries in the high-performance routing session
address table (HPRSAT). This is the maximum number of high-performance
routing (HPR) LU-LU sessions per TPF processor. You can specify a
nonzero value for this parameter only if you also specify a nonzero value for
the MAXRTPCB parameter.
- Note:
- Entries in the HPRSAT are located using a hashing algorithm. To
optimize the distribution of entries in the HPRSAT, specify a prime number for
this parameter.
See TPF ACF/SNA Data Communications Reference for
more information about the HPRSAT.
- MAXPCID
- Specifies the number of procedure correlation identification (PCID) table
entries. Entries in the PCID table are used for APPN LU-LU sessions
that are being activated. Once the LU-LU session becomes active, the
PCID table entry can be reused. This table is maintained only on the
TPF processor that has the CP-CP sessions; however, the table contains an
entry for each APPN LU-LU session that is being activated with any TPF
processor in the loosely coupled complex.
- MAXPRIM
- Specifies the number of resource name hash prime table (RNHPT)
entries. For more information about RNHPT entries, see TPF ACF/SNA Data Communications Reference.
See note 8 in Notes on Minimum, Maximum, and Default SNAKEY Values for more information about the MAXPRIM
parameter.
- MAXRTPCB
- Specifies the number of entries in the rapid transport protocol control
block (RTPCB) table. This is the maximum number of rapid transport
protocol (RTP) connections per TPF processor. You can specify a nonzero
value for this parameter only if you also specify a nonzero value for the
MAXHPRSA parameter.
See TPF ACF/SNA Data Communications Reference for
more information about the RTPCB table.
- MAXRVT
- Specifies the number of entries to create in the RVT. This value
corresponds to the maximum number of resources that can be defined to the TPF
system at any one time.
An RVT entry is defined as a spare RVT entry until a resource
definition is created for that RVT entry. A resource definition is
created by using the OSTG program, the ZNDYN ADD command, or dynamic LU
support.
See TPF Operations for more information about the
ZNDYN ADD command. See TPF ACF/SNA Data
Communications Reference for more information about spare RVT entries
and dynamic LU support.
Resource definitions are created for the following resources:
- Each TPF system services control point (SSCP)
- TPF control point (CP)
- Each TPF application
- Each TPF SLU appearance of a TPF application
- Each TPF functional management message router (FMMR)
- Each TPF processor NEF LU
- Each 37x5/3174 channel attached to the TPF system as a PU
2.1 link station
- Each control LU (CLU) associated with a PU 2.1 link station
- Each Logon Manager that can communicate with the TPF processor
- Each 37x5 channel attached to the TPF system as a PU 4 node
- Each remote LU
- Each remote SSCP.
Notes:
- If MAXALS and MAXRVT are equal to zero, main storage is not allocated for
37x5 I/O areas and a single end of table RVT entry is
created. These I/O areas (CCW areas) are also allocated for 3174 APPN
connections. Any further references to 37x5 I/O areas or CCW
areas should be considered to include 3174 APPN controllers.
- If you decrease the value of this parameter, enter the ZNOPL BUILD command
before you perform an initial program load (IPL) to load the new
version of the SNA keypoint (CTK2). This will force the TPF system to
perform a fresh load during the IPL. Otherwise, an error will
occur.
If you increase the value of this parameter, you do not need to perform a
fresh load.
- MAXSCB
- Specifies the number of session control block (SCB) entries that can be
active in the TPF system. The default value of zero indicates that
TPF/APPC is not being used.
- Note:
- There is an interdependency between CCBs and SCBs. If you want to use
TPF/APPC support, you must code both MAXCCB and MAXSCB greater than 0.
- MAXSID
- The session index table (SIT) is used by the TPF system to correlate
session identifiers (SIDs) to session control blocks (or RVTs). SIDs
are assigned by the BIND sender, the TPF system, or the NCP. The value
specified must be equal to or greater than the maximum number of PU 2.1
sessions that will flow through any channel-attached 37x5 or 3174
controller. This value is used to allocate an SIT as a CCW extension
for every 37x5 or 3174 controller.
A value of 0 indicates that the TPF system cannot attach to the network as
a PU 2.1 node. Because CTC links between PU 2.1 nodes are
not supported, the SIT is not used for CTC links. Storage is allocated
for MAXALS SITs.
- Note:
- For 3174 connections, SIDs X'0101'-X'01FF' are
reserved by the 3174. To compensate for this, you must add an
additional 255 SIDs when specifying the MAXSID parameter.
- MAXSNF
- Specifies the number of slots in the sequential number field table.
This table is used to correlate responses to TPF requests sent over a
CDRM-CDRM session from one LU to another LU. The table contains the RID
of the LU, which is found by using the session sequence number sent in the
original request and returned in the corresponding response PIU.
- MAXSRT
- Specifies the number of system recovery table (SRT) entries generated in a
processor. The default value of zero indicates that the TPF message
recovery facility will not be invoked.
- MAXTPI
- Specifies the number of transaction program instance control block (TPICB)
entries that can be active in the TPF system. For the TPF Application
Requester (TPFAR) feature, one TPICB block is needed for each conversation
that is active with the remote application server (AS). These active
conversations also include those already saved as hotcons in the
hotcon table (HCT). See the TPF Application
Requester User's Guide for more information.
- MQITRC
- Specifies the size of the MQI trace table in increments of 4-KB page
units.
- NUMALS
- Specifies the number of entries to allocate in the non-LU section of the
RVT. The non-LU section of the RVT contains the resource definitions
for ALS, CDRM, CTC, and NCP resources. If an entry in the non-LU
section of the RVT is not being used, it is referred to as a spare RVT
entry.
- Note:
- If you change this parameter to a value that requires the TPF system to
reassign the RIDs, a fresh load is automatically performed when you load the
new SNA keypoint (CTK2). If it is not necessary to reassign the RIDs, a
nonfresh load is performed.
See note 9 in Notes on Minimum, Maximum, and Default SNAKEY Values for more information about the NUMALS
parameter.
- SNSESZ
- Specifies the number of sense table (SNS) entries that will be defined in
the TPF system. The default value of zero indicates that the TPF sense
table facility will not be called.
- TRACSZ
- Specifies the size of the main storage PIU trace table in increments of
4-KB page units.
- CTCANS
- Specifies the number of seconds that the TPF system waits before declaring
the other side inoperative. This is equivalent to the NCP Automatic
Network Shutdown (ANS) or VTAM Missing Interrupt Handler (MIH)
functions.
- CTCRBFR
- Specifies the number of 4-KB input buffers per CTC link that the TPF
system allocates for receiving from a CTC link station.
- CTCTGANY
- Specifies that the TPF system supports any transmission group (TG) for CTC
links. Always specify CTCTGANY=YES. (If you specify CTCTGANY=NO,
the value is changed to CTCTGANY=YES.)
- CTCWBFRS
- Species the number of 4-KB output buffers that the TPF system allocates as
a pool for sending data to SNA CTC link stations. This value is the
total number of output buffers for all CTC links. This buffer pool is
shared by all active CTC link stations.
- DYNTO
- Specifies the minimum time, in seconds, that an RVT entry must remain on
the RVT termination list before it can be reused by a new logical unit that is
logging on to the TPF system.
- FMHDR
- Specifies the FM header data to prefix system-generated messages to 3600
LUs. This header data allows 3600 programs to distinguish between TPF
system-generated messages and application replies. The FM header
description is placed in the SNA keypoint and SNA parameter list.
All entries must be 2 hexadecimal characters. The first entry is the
total length of the header, including this length byte. It must be from
2-16. After the first length byte, the remainder contains as
many as 15 additional bytes of FM header data.
- HARDREC
- Allows the TPF system to resynchronize the virtual route (VR) sequence
number for each NCP using FID4 following a soft or a hard initial program load
(IPL). When HARDREC=NO is specified, a DISCONTACT request is issued to
each NCP using FID4 if the RVT entry indicates that the NCP is active and
bound.
- HPFMMR
- Specifies if the high-performance functional management message router
(HPFMMR) transmit process is used. HPFMMR uses an ENQC|DEQC method of
serializing activity on the FMMR-FMMR session instead of using the NCB.
HPFMMR allows multiple processors in a loosely coupled complex to transmit to
the same destination simultaneously. See note 6 in Notes on Minimum, Maximum, and Default SNAKEY Values.
- HPRALIVE
- Specifies the value, in seconds, of the alive timer. The
alive timer is used by the TPF system to detect failures for idle rapid
transport protocol (RTP) connections in a high-performance routing (HPR)
network. See TPF ACF/SNA Data Communications
Reference for more information about the alive timer.
- HPRPST
- Specifies the number of seconds the TPF system will suggest the remote
rapid transport protocol (RTP) endpoint use for its path switch
timer. The path switch timer is used to detect path switch
failures in a high-performance routing (HPR) network. See TPF ACF/SNA Data Communications Reference for more
information about the path switch timer.
- ILWPC
- Specifies the percentage of common blocks that must be available in the
TPF system. If the percentage falls below this value, the TPF system
will not perform certain functions that require common blocks, such as sending
virtual route (VR) pacing responses, until the minimum percentage is available
again. This helps the TPF system avoid running out of critical
resources.
This parameter is also used by adaptive rate-based (ARB) pacing to regulate
the rate at which traffic is sent across high-performance routing (HPR) rapid
transport protocol (RTP) connections. See TPF
ACF/SNA Data Communications Reference for more information about ARB
pacing and RTP connections.
If you specify a value of 0 for this parameter, the TPF system will not
check the percentage of common blocks available and will use a default value
of 20 to calculate ARB pacing.
- ILWPE
- Specifies the percentage of entry control blocks (ECBs) that must be
available in the TPF system. If the percentage falls below this value,
the TPF system will not perform certain functions that require ECBs, such as
sending virtual route (VR) pacing responses, until the minimum percentage is
available again. This helps the TPF system avoid running out of
critical resources.
This parameter is also used by adaptive rate-based (ARB) pacing to regulate
the rate at which traffic is sent across high-performance routing (HPR) rapid
transport protocol (RTP) connections. See TPF
ACF/SNA Data Communications Reference for more information about ARB
pacing and RTP connections.
If you specify a value of 0 for this parameter, the TPF system will not
check the percentage of ECBs available and will use a default value to
calculate ARB pacing.
- ILWPF
- Specifies the percentage of frame blocks that must be available in the TPF
system. If the percentage falls below this value, the TPF system will
not perform certain functions that require frame blocks, such as sending
virtual route (VR) pacing responses, until the minimum percentage is available
again. This helps the TPF system avoid running out of critical
resources.
This parameter is also used by adaptive rate-based (ARB) pacing to regulate
the rate at which traffic is sent across high-performance routing (HPR) rapid
transport protocol (RTP) connections. See TPF
ACF/SNA Data Communications Reference for more information about ARB
pacing and RTP connections.
If you specify a value of 0 for this parameter, the TPF system will not
check the percentage of frames available and will use a default value to
calculate ARB pacing.
- ILWPI
- Specifies the percentage of input/output blocks (IOBs) that must be
available in the TPF system. If the percentage falls below this value,
the TPF system will not perform certain functions that require IOBs, such as
sending virtual route (VR) pacing responses, until the minimum percentage is
available again. This helps the TPF system avoid running out of
critical resources.
This parameter is also used by adaptive rate-based (ARB) pacing to regulate
the rate at which traffic is sent across high-performance routing (HPR) rapid
transport protocol (RTP) connections. See TPF
ACF/SNA Data Communications Reference for more information about ARB
pacing and RTP connections.
If you specify a value of 0 for this parameter, the TPF system will not
check the percentage of IOBs available and will use a default value to
calculate ARB pacing.
- ILWPS
- Specifies the percentage of system work blocks (SWBs) that must be
available in the TPF system. If the percentage falls below this value,
the TPF system will not perform certain functions that require SWBs, such as
sending virtual route (VR) pacing responses, until the minimum percentage is
available again. This helps the TPF system avoid running out of
critical resources.
This parameter is also used by adaptive rate-based (ARB) pacing to regulate
the rate at which traffic is sent across high-performance routing (HPR) rapid
transport protocol (RTP) connections. See TPF
ACF/SNA Data Communications Reference for more information about ARB
pacing and RTP connections.
If you specify a value of 0 for this parameter, the TPF system will not
check the percentage of SWBs available and will use a default value to
calculate ARB pacing.
- INREC
- Specifies whether to create a safe store file copy of recoverable input
messages. This parameter is ignored if MAXSRT=0 is coded.
- LENNETID
- Specifies the network identifier (NETID) of the TPF system when it is
connected to the network as a PU 2.1 node. This network ID is
used for both 37x5/VTAM and non-37x5 connections. If
you do not specify a value for the LENNETID parameter, the value stored in the
SNA keypoint defaults to 8 blanks. The LENNETID parameter can be as
many as 8 characters long.
- LMSCTI
- Specifies the time interval, in seconds, used to notify the Logon Manager
(LM) of the number of active sessions on an ALS.
- LUBLKT
- Specifies the time interval before the LU blocking package transmits
queued output data. For compatibility with NPSI, the time interval is
specified in 100-ms increments. The default value is 1.
- MAXBFRU
- Specifies the number of input buffers the TPF system allocates for
receiving data from channel attached 37x5s. This value is
passed to the NCP at channel contact time as the number of read channel
commands the TPF system will execute per channel program. (See note 5 in Notes on Minimum, Maximum, and Default SNAKEY Values for more information about the MAXBFRU
parameter.)
- MAXSMTB
- Specifies the number of 4-KB storage areas used per I-stream to hold the
structured query language (SQL) trace information. If 0 is specified,
no trace information is collected.
- NBLKLU
- Specifies the number of control blocks for the blocking of output messages
destined for General Access to X.25 Transport Extensions (GATE)/ Fast
Transaction Processing Interface (FTPI) resources. For detailed
information about GATE and FTPI, see TPF ACF/SNA Data
Communications Reference.
- NETID
- Specifies the network ID of the TPF system when it is attached as a PU 5
node. For example, if VTAM defines a network ID of TPFNET to the TPF
system, specify TPFNET for this parameter. If you do not specify a
value for this parameter, a default value of 8 blanks is stored in the SNA
keypoint. There is an 8-character limitation for the NETID
parameter.
- OLDAPPL
- Allows the TPF system to support old applications and SNA 3270
terminals, and to bypass the restriction for the multiple chained output
message segments. When OLDAPPL=NO is specified, current 3270 message
flow is not affected.
- PARACOS
- Specifies the class of service name that the TPF system uses when building
a CDINIT response for a TPF/APPC parallel session.
- PIUTAPEQ
- Specifies the RTL tape queue threshold for writing to the PIU trace
tape. If the RTL tape queue threshold is exceeded, an attention message
is issued to the operator and PIU trace blocks are not written to tape until
the queue count falls below the threshold.
- RECIT
- Specifies the activation frequency of the SNA input recovery timeout
program. The default timeout value is the product of the
following:
- Multiplier used to calculate the recovery timeout.
- Resolution factor, in seconds, use to calculate the recovery
timeout.
This parameter is ignored if MAXSRT=0 (no message recovery) is
specified.
- RECOP
- Specifies the number of seconds that the TPF system waits for a response
to an output data message to a 3270 printer before taking recovery
action.
- RECOT
- Specifies the number of seconds that the TPF system waits for a response
to an output data message before taking recovery action.
- RSPTO
- Specifies the number of seconds that the TPF system waits for a response
to a SNA command before the response is considered lost. This value
should be greater than the maximum time that the NCP can attempt to send a
command. This maximum NCP time is a function of the NCP system
generation parameters REPLYTO=(a) and RETRIES=(m,t,n). For more
information, see NCP/SSP/EP Resource Definition Reference.
A close approximation of this NCP time can be calculated using the
following formula:
Time = (n × t) + (m × n × a)
This, of course, does not include text transmission or internal NCP
processing time. Failure to make this value large enough can cause
retransmission of a command and result in incorrect processing in the NCP or
cluster controller. Specifying too large a value will result in error
conditions not being reported to the operator within an appropriate amount of
time.
- RTPRSYNC
- Enables or disables the rapid transport protocol (RTP) resynchronization
process. When enabled, the RTP resynchronization process attempts to
keep RTP connections active after a hard initial program load (IPL) is
performed.
See TPF ACF/SNA Data Communications Reference for
more information about the RTP resynchronization process.
- RVTCTRL
- Specifies the number of entries that are processed when keypointing or
validating the RVT or when searching the RVT for timed-out commands before
control of the processor is given up.
- SINGMODE
- Specifies the mode name used for TPF/APPC single sessions started by the
TPF system.
- SLOWTIME
- Specifies the number of SNA polling intervals that an ALS can be in
slowdown mode before the TPF system deactivates the link. The SNA
polling interval value is defined by the SNAPOLL parameter. The
SLOWTIME parameter also defines the amount of time, in 10-ms intervals, that
an Internet Protocol (IP) router is allowed to be in slowdown mode before the
TPF system deactivates the link.
- SNAPOLL
- Specifies the SNA polling interval. The value can range from
1-5, where 1 represents 10 milliseconds (ms), 2 represents 20 ms, and
so on, up to a maximum of 50 ms.
- SNDWN
- Specifies the SNA shutdown level. If the number of available system
work blocks (SWBs) falls below the number specified for this parameter, RVT
scan will not issue any command. This value must be less than the
number specified for the SNRST parameter.
- SNKEY
- Specifies the time interval, in seconds, at which the SNA keypointable
control blocks (for example, RVTs) will be written to file.
- SNQDPT
- Specifies the SOUTC queue depth for SNA output command handler,
RVTSCAN. Specifying a higher value for this parameter can increase SNA
outbound traffic flow under certain conditions.
- SNRST
- Specifies the SNA restart level. After the shutdown level is
reached, this number specifies the number of system work blocks (SWBs) that
must be available before RVT scan can issue any commands. This value
must be greater than the number specified for the SNDWN parameter.
- SNSETO
- Specifies the number of seconds that the TPF system will collect the
negative responses before issuing a message to indicate the total number
received during this time period.
- TPALLOC
- Specifies the number of seconds that the TPF system waits for a remote LU
to respond to a TPF/APPC ALLOCATE verb before timing out.
- TPRECV
- Specifies the number of seconds that the TPF system waits for data after a
TPF/APPC RECEIVE verb or any verb that implies CONFIRM before timing
out.
- TPWAIT
- Specifies the number of seconds that the TPF system waits for a remote LU
to respond to a TPF/APPC WAIT verb before timing out.
- TRANA
- Specifies if the user-written transaction analysis exit must be called for
each input message. This parameter is ignored if the message recovery
facility was excluded from the TPF system by coding MAXSRT=0.
- UNITSZ
- Specifies the TPF input buffer size used for data transfer from a
37x5. This value is passed to the NCP at channel contact to
specify the number of bytes allocated by the TPF system per NCP read
command. See note 5 in Notes on Minimum, Maximum, and Default SNAKEY Values for special coding considerations
for the UNITSZ parameter. The recommended value for this parameter is a
multiple of 8.
- VRRTO
- Specifies the number of seconds that virtual route (VR) resync waits
before declaring a timeout. The default value is 10 seconds.
- MAXASCU
- Specifies the maximum number of Mapping of Airline Traffic over Internet
Protocol (MATIP) agent set control units (ASCUs) that can be connected to the
TPF system at one time.
- MAXMATIP
- Specifies the maximum number of MATIP sessions that can exist on the TPF
system at one time.
- SOCKSWP
- Specifies, in minutes, the CRET timeout interval for the TCP/IP socket
sweeper and the Secure Sockets Layer (SSL) sweeper.
See TPF Transmission Control Protocol/Internet
Protocol for information about the values to specify for these
parameters.
- CLAWADP
- Specifies the number of Common Link Access to Workstation (CLAW)
adapters.
- CLAWFD
- Specifies the number of file descriptors.
- CLAWIP
- Specifies the number of local Internet Protocol (IP) addresses.
See TPF Transmission Control Protocol/Internet
Protocol for information about the values to specify for these
parameters.
- IPMTSIZE
- Specifies the size of the IP message table (IPMT) in 4-KB blocks.
- IPRBUFFS
- Specifies the number of read buffers assigned per read channel program to
each IP router using channel data link control (CDLC) support.
- IPRBUFSZ
- Specifies the size of each read buffer for IP routers using CDLC
support.
- IPTOS
- Specifies the type of service (TOS) value to use for the network priority
of outbound TPF IP packets.
- IPTRCNUM
- Specifies the maximum number of individual IP traces that can be
defined.
- IPTRCSIZ
- Specifies the size of each individual IP trace table, defined in 4-KB
blocks.
- MAXIPCCW
- Specifies the maximum number of IP routers that can be active on the TPF
system.
- MAXOSA
- Specifies the maximum number of Open Systems Adapter (OSA)-Express
connection that can be active on the TPF system.
- MAXRTE
- Specifies the maximum number of IP routing table entries.
- MAXSOCK
- Specifies the maximum number of sockets using TCP/IP native stack support
that can be active on the TPF system.
- OSABUFF
- Specifies the number of 64-KB read buffers assigned to each OSA-Express
connection.
See TPF Transmission Control Protocol/Internet
Protocol for information about the values to specify for these
parameters.
- SSLPROC
- Specifies the number of Secure Sockets Layer (SSL) daemon
processes. The SSLPROC and SSLTHRD parameters must both be 0 or a value
other than 0. If you want to use shared SSL session support, you must
set the SSLPROC and SSLTHRD parameters to values other than 0.
- SSLTHRD
- Specifies the number of thread ECBs per SSL daemon process. The
SSLTHRD and SSLPROC parameters must both be 0 or a value other than 0.
If you want to use shared SSL session support, you must set the SSLTHRD and
SSLPROC parameters to values other than 0.
You should understand the relationship among the MAXCTC, CTCRBFR, and
CTCWBFRS parameters:
- The value specified for the CTCRBFR (read buffers) and CTCWBFRS (write
buffers) parameters must be proportional to the value specified for the MAXCTC
parameter. This proportion represents the total number of frames
available in the read and write buffers.
- The required number of write buffers (CTCWBFRS) depends on the number of
read buffers (CTCRBFR) in the other side of the network.
The following examples provide some guidelines for you to use when
determining the values for the CTCRBFR and CTCWBFRS parameters:
- Two TPF systems, TPFA and TPFB, are connected with 2 CTC links, CTC1 and
CTC2. Both systems have the MAXCTC parameter set to 2. The TPFA
system has the CTCRBFR parameter set to 10; the TPFB system has the
CTCRBFR parameter set to 16. The number of frames automatically carved
out on TPFA is:
2 (MAXCTC) × 2 read buffers per link × 10 (CTCRBFR) = 40 frames
The number of frames automatically carved out on TPFB is:
2 (MAXCTC) × 2 read buffers per link × 16 (CTCRBFR) = 64 frames
When the first link is activated (CTC1), the number of frames needed on the
TPFA system is:
2 read buffers × 10 (from CTCRBFR) frames per buffer = 20
1 write buffer with 16 frames = 16
(found out at link activation time from the
value of CTCRBFR on TPFB
-------
Total frames needed on TPFA 36
Because the second CTC link, CTC2, is between the same 2 systems, the same
number of frames (36) is used. Therefore, in order to activate both
links, there must be a minimum of 72 frames allocated.
Because 40 frames were initially allocated, the value of the CTCWBFRS
parameter must be set to a minimum of 32 frames (72 - 40 = 32).
However, if you knew that you would never have both CTC links activated at the
same time, you could set CTCWBRFS to 0, because enough frames are already
allocated (40) to bring up one link (36).