SNAX/APC Configuration and Management Manual

SCF Commands for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
8-35
ALTER TPN Command
started, the DEFAULTMAXINRUSIZE and DEFAULTMAXOUTRUSIZE are not
validated against the underlying SNAX access method. However if the values of
these attributes exceeds the transfer count upper limit of the underlying SNAX
access method, the CurrentMaxInRUSize and CurrentMaxOutRUSize counters (as
shown in the INFO PTNR-MODE detailed display) are set to the upper limit after
the PTNR-MODE is started. If the values of the DEFAULTMAXINRUSIZE and
DEFAULTMAXOUTRUSIZE attributes do not exceed the upper limit, the
CurrentMaxInRUSize and CurrentMaxOutRUSize counters are set to the values
specified in the DEFAULTMAXINRUSIZE and DEFAULTMAXOUTRUSIZE
attributes when the PTNR-MODE object is started.
Examples
-> ASSUME PTNR-LU $APC1.LU01.CICSLU62
-> ALTER PTNR-MODE LU62BIND, MAXAUTOACT 5, RCVWINDOW 7, &
SENDWINDOW 7
-> ASSUME PTNR-LU $APC1.LU01.CICSLU62
-> ALTER PTNR-MODE LU62BIND, MAXSESSION 100, MINCONWINNER 25, &
MINCONLOSER 25, RESPONSIBLE SOURCE
-> ASSUME PROCESS $APC1
-> ALTER PTNR-MODE LU01.CICS001.CICSLU62, &
DEFAULTMAXINRUSIZE 256, DEFAULTMAXOUTRUSIZE 256
ALTER TPN Command
The ALTER TPN command changes the attribute settings of the target TPN object.
ALTER TPN Attributes
LIKE tpn2
identifies an existing TPN object whose attribute values serve as the model for the
new values of the attributes of the TPN being altered.
CHARMAPPING { YES | NO }
alters whether SNAX/APC performs character translation for all mapped
conversations subordinate to the target TPN.
ALTER [ TPN tpn1 ] [ , LIKE tpn2 ] [ , attribute-spec ]
where attribute-spec is:
[ , CHARMAPPING { YES | NO } ]
[ , CHARMAPNAME [ mapname ] ]
[ , GENERALTPREADY { YES | NO } ]
[ , REMOTEATTACH { QUEUE | REJECT } ]
[ , REMOTEATTACHTIMER number ]
[ , REPLYDELAYEDONERROR { YES | NO } ]
[ , SECURITYREQUIRED { NONE | USER } ]
[ , SESSIONCONTROL { YES | NO } ]