You can dynamically change the following switched major
node operands by editing the VTAMLST and then issuing the VARY ACT,UPDATE=ALL
command. You can specify the new operand value on a higher-level definition
statement for sifting, if applicable.
ADDR
ANS
ASDP
ASLENT
ASLTAB
BATCH
CALL
CAPACITY
CONNTYPE
COSTBYTE
COSTTIME
CPCP
DATMODE
DIALNO
DISCNT
DLCADDR
DLOGMOD
DLURNAME
DYNADJCP
DYNLU
EEVERIFY
ENCR
ENCRTYPE
FASTPASS
FEATUR2
GID
GRPNM
HOSTNAME
HPREEARB
HPRPSDLY
IDBLK
IDNUM
IPADDR
IRETRY
ISTATUS
LIMRES
LINENM
LOCADDR
LOGAPPL
LOGTAB
|
LUGROUP
LUSEED
MAXDATA
MAXOUT
MAXSESS
MDLENT
MDLTAB
MODETAB
MTU
NN
PACING
PASSLIM
PDELAY
PID
PUTYPE
REDDELAY
REDIAL
REGISTER
SAPADDR
SECURITY
SECNET
SHM
SHMTIM
SSCPFM
TERM
TGP
TOPO
UPARM1
UPARM2
UPARM3
USE
USSTAB
VERALSID
VERID
VERIFY
VPACING
|
In addition to the above VTAM® operands,
you can also dynamically change the following NCP operands, which
are passed to the NCP during switched PU connection. For information
on these operands, see the
NCP, SSP, and EP Resource Definition Reference.
- COMRATE
- DLCI
- DYNWIND
- HPRQLIM
- INTFACE
- IPQLIM
- LADDR
- SNETMASK
- T1TIMER
- T2TIMER
To dynamically change an operand on the PU or LU statement,
the resource to which it applies must be inactive. For instance, an
operand on an LU definition statement that receives its value from
a PU definition statement can be dynamically changed only when the
LU is inactive; the PU can remain active.
You can dynamically change the operands associated with
a PATH statement or tables (ASLTAB, LOGTAB, MDLTAB, MODETAB, and USSTAB)
when the PU is active, connectable, or inactive. You cannot change
the PATH operands when the PU is in pending state.
Note: For a switched major node, you cannot add APPN capability
or SDDLU support to a PU with the dynamic change function. If a PU
has not been coded as APPN-capable, you cannot add the APPN operands
to it. Likewise, if you have not coded LUGROUP (which allows SDDLU
support) on a PU definition statement, you cannot add it with dynamic
change.