START command

Starting VTAM in an MVS environment:

Note:

The start options are listed in this information alphabetically; however, you can code them in any order.
Precede the option list with three commas and enclose the group of options in parentheses.
Start options that are entered on the START command must be separated by commas. Do not leave any blanks between options.

Options

Notes:

¹ APPNCOS is meaningful only if the NODETYPE start option is also used.
² BN is meaningful only if the NODETYPE=NN start option is also used.
³ BNDYN is meaningful only if the BN=YES start option is also used.
⁴ BNORD is meaningful only if the BN=YES start option is also used.
⁵ CDSERVR is meaningful only if the NODETYPE=NN start option is also used.
⁶ CDSREFER is meaningful only if the NODETYPE=NN and CDSERVR=NO start options are also used.
⁷ The CMPMIPS start option is meaningful only if the value for CMPVTAM is greater than 1.
⁸ CONNTYPE is meaningful only if the NODETYPE start option is also used.
⁹ CPCP is meaningful only if the NODETYPE start option is also used.
¹⁰ Specify the CSDUMP start option twice to set both message and sense code triggers.
¹¹ DIRSIZE is meaningful only if the NODETYPE=NN start option is also used.
¹² DIRTIME is meaningful only if the NODETYPE=NN start option is also used.
¹³ DLURSAW is meaningful only if the NODETYPE=NN start option is also used.
¹⁴ Because of the volume of messages that can be generated, it is not recommended that this option be enabled during normal operation. Instead, it is recommended that this option be enabled (using the MODIFY VTAMOPTS command) on all necessary hosts only when trying to diagnose specific problems. After the problem has been diagnosed or documentation has been collected, this option should be disabled once again (using the MODIFY VTAMOPTS command).
¹⁵ If the DSPLYMAX start option value is less than 100, that value is the default for DSPLYDEF.
¹⁶ Use the CFSIZER tool to determine the appropriate number of lists for your EZBDVIPA structure, as well as, the suggested INITSIZE and SIZE values for the structure. Before you modify the DVLSTCNT option to increase the number of lists requested for the EZBDVIPA structure, update your CFRM policy with the recommended INITSIZE and SIZE values. Increasing the number of lists requires more storage for the EZBDVIPA structure. Make sure the same DVLSTCNT value is configured in all VTAMs in the sysplex. To enable the modified DVLSTCNT value, issue the following SETXCF MVS™ command to rebuild the EZBDVIPA structure: SETXCF START,REBUILD,STRNAME=EZBDVIPA. See SETXCF command in z/OS MVS System Commands for more information.
¹⁷ DYNADJCP is meaningful only if the NODETYPE start option is also used.
¹⁸ Two character prefix.
¹⁹ EEHPRANR is meaningful only when the NODETYPE=NN start option is also used.
²⁰ The EEVERIFY start option is meaningful only if VTAM® provides RTP-level HPR support. The NODETYPE start option must be coded and the RTP value must be specified on the HPR start option.
²¹ ENCRYPTN=CCA needs to be coded when Triple Des Encryption is required.
²² The ENSEMBLE setting is used to either permit or deny connectivity to the intraensemble data network and the intranode management network. It does this by either allowing or denying activation of OSX and OSM interfaces.
²³ HOSTNAME is meaningful only if the NODETYPE start option is also used. If neither HOSTNAME nor IPADDR is specified on any of the GROUP definition statements within the Enterprise Extender XCA major node, then either the HOSTNAME, TCPNAME, or IPADDR start options must be specified in order to activate an Enterprise Extender link. The HOSTNAME start option specifies the default hostname to be used for name-to-address resolution as part of activating an Enterprise Extender connection, and must resolve at this node to a static VIPA address associated with a TCP/IP stack at this node. If IPADDR is specified along with HOSTNAME on the START command, the IPADDR value is ignored.
²⁴ HOSTSA specifies the subarea number of this VTAM. If HOSTSA is not coded, then a default subarea number of 1 is used.
²⁵ HPR is meaningful only if NODETYPE is also used.
²⁶ HPRCLKRT=ADAPTIVE is meaningful only in Enterprise Extender configurations that have a defined capacity of 1 Gb (gigabit) or higher access speeds.
²⁷ This option is meaningful only if VTAM provides RTP-level HPR support.
²⁸ HPRSESLM=DISABLED is meaningful only on interchange nodes.
²⁹ INITDB is meaningful only if the NODETYPE=NN start option is also used.
³⁰ When specifying an InOpCode for the second parameter, always specify three digits by including any leading zeros.
³¹ If an InOpCode is specified for the second parameter, the first parameter cannot be ALL.
³² INOPCODE has no effect unless INOPDUMP is active for the resource when an inoperative condition is detected. See the MODIFY INOPCODE command for more details.
³³ Multiple INOPCODE parameters can be specified by the START command, and will be processed left to right as they are entered. This is different from specifying the INOPCODE parameter on either the MODIFY INOPCODE command or the MODIFY VTAMOPTS command, where only one INOPCODE parameter is allowed for each entry of these commands.
³⁴ INOPDUMP status is propagated to resources that are defined within a TRLE when the entry is activated.
³⁵ IPADDR is meaningful only if the NODETYPE start option is also used. If neither IPADDR nor HOSTNAME is specified on any of the GROUP definition statements within the Enterprise Extender XCA major node, then either the HOSTNAME, TCPNAME, or IPADDR start option must be specified in order to activate an Enterprise Extender link. The IPADDR start option specifies the default IPv4 or IPv6 static VIPA address to be used when activating an Enterprise Extender connection. If HOSTNAME is specified along with IPADDR on the START command, the IPADDR value is ignored.

Notes:

¹ The IQDCHPID option controls which IQD CHPID (and related subchannel devices) VTAM selects to dynamically build the iQDIO (IUTIQDIO) MPC group. The IUTIQDIO MPC group is used for TCP/IP dynamic XCF communications within System z®. Although this option can be modified (and the modification will immediately be displayed) while the IUTIQDIO MPC group is currently active, any modifications have the effects shown in the section called IQD CHPID modifications.
² This option affects only iQDIO devices that use a MFS of 64k. The smaller frame sizes will always use 126 SBALs. You can override this option on a per-device basis using the READSTORAGE parameter on the LINK or INTERFACE statement in the TCP/IP profile. See z/OS Communications Server: IP Configuration Reference for more details.
³ LIST can be entered by a VTAM operator only. If LIST is coded in an ATCSTRxx file, it is considered to be an error and is ignored.
⁴ Because of the volume of messages that can be generated, it is not recommended that this option be enabled during normal operation. Instead, it is recommended that this option be enabled (using the MODIFY VTAMOPTS command) on all necessary hosts only when trying to diagnose specific problems. After the problem has been diagnosed or documentation has been collected, this option should be disabled once again (using the MODIFY VTAMOPTS command).
⁵ LISTBKUP can be coded only in a start option file. If you enter it on the START command or at an operator prompt, VTAM will ignore it.
⁶ MAXLOCAT is meaningful only if NODETYPE is specified.
⁷ MULTPATH is meaningful only if the NODETYPE start option is also specified.
⁸ NNSPREF can be specified only if NODETYPE=EN is specified during VTAM START processing.
⁹ NODETYPE enables APPN function. The combination of HOSTSA, NODETYPE, and SACONNS determines the configuration (subarea node, interchange node, migration data host, network node, or end node).
¹⁰ NUMTREES is meaningful only if the NODETYPE=NN start option is also used.
¹¹ PMTUD is meaningful only if the NODETYPE start option is also specified.
¹² A VTAM operator cannot enter the PROMPT or NOPROMPT start option; it can be coded only in ATCSTR00. The value coded in ATCSTR00 is ignored if start options are entered on the START command or if VTAM finds an error in a start list. Upon finding an error in a start list, VTAM prompts the operator so that the operator can specify the option correctly.
¹³ QDIOSTG defaults to MAX. To understand the meaning of the various keywords on QDIOSTG, see QDIOSTG start option in z/OS Communications Server: SNA Resource Definition Reference. To see the amount of read storage being used for a specific QDIO datapath device, use the DISPLAY TRLE command. You can override the QDIOSTG value on a per-device basis using the READSTORAGE parameter on the LINK or INTERFACE statement in the TCP/IP profile. See z/OS Communications Server: IP Configuration Reference for more details.
¹⁴ RESUSAGE is meaningful only if the NODETYPE=NN start option is also used.
¹⁵ ROUTERES is meaningful only if the NODETYPE=NN start option is also used.
¹⁶ The SECLVLCP start option is meaningful only if the NODETYPE and VERIFYCP start options are also used.
¹⁷ SNVC is meaningful only if the BN=YES start option is also used.
¹⁸ SORDER is meaningful only in an interchange node or a migration data host.
¹⁹ SRCOUNT is meaningful only if the SRCHRED=ON start option is also used.
²⁰ SRTIMER is meaningful only if the SRCHRED=ON start option is also used.
²¹ The SSCPDYN start option applies only for interconnected networks (that is, GWSSCP=YES is used).
²² SSEARCH is meaningful only if the NODETYPE=NN start option is also used.
²³ TCPNAME is meaningful only if the NODETYPE start option is also used. If neither IPADDR nor HOSTNAME is specified on any of the GROUP definition statements within the Enterprise Extender XCA major node, then either the HOSTNAME, TCPNAME, or IPADDR start options must be specified in order to activate an Enterprise Extender link.
²⁴ TDUDIAG is meaningful only if the NODETYPE=NN start option is also available.
²⁵ TOPOTIME is meaningful only if the NODETYPE start option is also used.
²⁶ Do not use NOTRACE when starting VTAM, except to override a TRACE start option coded in a predefined list.
²⁷ You can code TRACE and its qualifiers through position 71, even if you are in the middle of the start option. Continue the remainder of the item in the next record. Code the TYPE qualifier immediately after you code the TRACE start option.

Buffer Pool Values

BUF Trace Operands

CSDUMP message trigger

CSDUMP sense code trigger

IO Trace Operands

LINE Trace Operands

MODULE Trace Operands

QDIOSYNC trace operands

SIT Trace Operands

STATE Trace Operands

Operands used with ID

OPTION Operand

Notes:

¹ NOTRACE,TYPE=VTAM is accepted but ignored. Tracing is started with the default trace table size and the default options. The NOTRACE,TYPE=VTAM start option processing is affected by the level of VIT control being used (as specified by the VITCTRL start option). See z/OS Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT for details.
² You can code TRACE and its qualifiers through position 71, even if you are in the middle of the start option. Continue the remainder of the item in the next record. Code the TYPE qualifier immediately after you code the TRACE start option.
³ UNRCHTIM is meaningful only if the NODETYPE start option is also used.
⁴ UPDDELAY is meaningful only if the OSIMGMT=YES start option is also used.
⁵ The VERIFYCP start option is meaningful only if the NODETYPE start option is also used.
⁶ VFYREDTI is meaningful only if the NODETYPE=NN start option is also used.
⁷ VITCTRL start option will only affect the TRACE or NOTRACE start option if it is specified prior to the TRACE or NOTRACE TYPE=VTAM (MODE=INT) start option.
⁸ VRTG is meaningful only if the NODETYPE and HOSTSA start options are also used.
⁹ VRTGCPCP is meaningful only if the NODETYPE and HOSTSA start options are also used.
¹⁰ XCFINIT=YES is the default if VTAM is started as an APPN node (that is, the NODETYPE start option has been specified). XCFINIT=YES is not valid for pure subarea nodes. XCFINIT=DEFINE is the default if VTAM is started as a pure subarea node (the NODETYPE start option has not been specified).
¹¹ When the same parameter is entered multiple times on a CSDUMP message trigger, only the last occurrence is accepted.
¹² MSGVALUE is valid only when the MESSAGE operand is used and specifies either message IST2391I, IST2406I or IST2419I.
¹³ When an error message is received on any parameter of the CSDUMP start option, the remaining parameters for this CSDUMP start option are ignored. Enter the complete CSDUMP start option again when you are prompted.
¹⁴ When the same parameter is entered multiple times on a CSDUMP sense trigger, only the last occurrence is accepted.
¹⁵ COUNT applies only to the IBM® 3720 and 3745 Communication Controllers.

VIT Operands

Notes:

¹ The default options apply only to MODE=INT.
² PSS is a default VIT option, but PSS can be turned off.
³ When you specify SUBTRACE=ARBP and you code a single OPTION value, the OPTION value must be HPR, ALL, or one of the group options (hprgrpopt) that include HPR as an individual option equivalent. The applicable group options are DLUROPTS, EEOPTS, HPDTOPTS, HPROPTS, QDIOOPTS, and XCFOPTS.
⁴ When SUBTRACE=ARBP is coded and you code multiple trace options in parentheses, you must code either HPR or one of the group options (hprgrpopt) that include HPR as an individual option equivalent inside the parentheses.
⁵ When you specify SUBTRACE=DIO and you code a single OPTION value, the OPTION value must be CIA, ALL, or one of the group options (ciagrpopt) that include CIA as an individual option equivalent. The applicable group options are EEOPTS, HPDTOPTS, HPROPTS, QDIOOPTS, TCPOPTS and XCFOPTS.
⁶ When SUBTRACE=DIO is coded and you code multiple trace options in parentheses, you must code either CIA or one of the group options (ciagrpopt) that include CIA as an individual option equivalent inside the parentheses.
⁷ When you code SUBTRACE=TGVC or SUBTRACE=TREE and you code a single OPTION value, the OPTION value must be either SSCP, ALL, or one of the group options (groupopt), all of which include SSCP as an individual option equivalent. The group options are APIOPTS, APPCOPTS, CPCPOPTS, CSMOPTS, DLUROPTS, EEOPTS, HPDTOPTS, HPROPTS, LCSOPTS, QDIOOPTS, STDOPTS, TCPOPTS, and XCFOPTS.
⁸ When you code SUBTRACE=TGVC or SUBTRACE=TREE and you code multiple trace options in parentheses, you must code either SSCP or one of the group options (groupopt) inside the parentheses.

IQD CHPID modifications

While the IUTIQDIO MPC group is currently active, any modifications to the IQDCHPID option have the following effects:

Modified from ANY (or CHPID) to NONE - no effect on current usage but blocks subsequent activations
Modified from NONE to ANY (or CHPID) - no effect on current usage but allows subsequent activations
Modified from CHPID_X to CHPID_Y - no effect on current usage
Note: VTAM uses the CHPID value only when building the IUTIQDIO MPC group. To change CHPIDs for an active MPC group, the following must be done:
1. All TCP/IP iQDIO (HiperSocket) devices must be stopped.
2. Make any necessary HCD/IOCDS changes.
3. Verify that new subchannel devices are varied online.
4. Verify that the MPC group has deactivated (with no usage, it times out after approximately two minutes).
5. Modify IQDCHPID=CHPID (to new CHPID).
6. Restart the TCP/IP iQDIO device or devices.

Note: In order to use iQDIO communications, the processor must have the necessary hardware support. If the processor does not support iQDIO communications, then modifications to this start option will not be accepted and the IQDCHPID option will not be displayed (displayed as ***NA***).

Abbreviations

Operand	Abbreviation
START	S
AMOUNT=FULL	AMT=F
AMOUNT=PARTIAL	AMT=P
DATEFORM	DATEFRM
EVERY	E
MSGLEVEL	MSGLVL
OPTION	OPT
OPTION=COMMAND	OPT=CMD
OPTION=CONNECTION	OPT=CON
OPTION=DEFINITION	OPT=DEF
OPTION=INTERFACES	OPT=INT
OPTION=MANAGEMENT	OPT=MGMT
OPTION=SESSION	OPT=SES
PLUALMSG=NOSUPP	PLUALMSG=NOSUP
PLUALMSG=SUPPRESS	PLUALMSG=SUPP
SECLVLCP=LEVEL1	SECLVLCP=LVL1
SECLVLCP=LEVEL2	SECLVLCP=LVL2
SLUALMSG=NOSUPP	SLUALMSG=NOSUP
SLUALMSG=SUPPRESS	SLUALMSG=SUPP
TRANSLAT=COSNAME	TRANSLAT=3
TRANSLAT=DLUALIAS	TRANSLAT=7
TRANSLAT=DLUREAL	TRANSLAT=1
TRANSLAT=DLUSSCP	TRANSLAT=2
TRANSLAT=LOGMODES	TRANSLAT=4
TRANSLAT=LUANAME	TRANSLAT=5
TRANSLAT=OLUALIAS	TRANSLAT=0
TRANSLAT=USERVAR	TRANSLAT=6

When using an abbreviation in place of an operand, code the abbreviation exactly as shown in the table. For example, when coding the abbreviation for PLUALMSG=SUPPRESS, code only PLUALMSG=SUPP.

Purpose

VTAM is started with the START command.

You can enter the START command only at the master or a secondary system console.

Operands

procname

Procedure name for the command.

procname can be specified as either startname.ident or startname, where startname is the name of the JCL procedure used to start VTAM and ident is an optional identifier.

procname used for this command determines the procname used for all MODIFY commands as follows:

If procname in the START command was specified as startname.ident, where startname is the VTAM start procedure and ident is the optional identifier, then either startname.ident or ident can be specified for procname.
If procname in the START command was startname, then startname must be specified for procname.

Therefore, if you use NET as the optional identifier on this command, you can consistently use NET as procname for all VTAM commands.

options

VTAM start options supplied by the system programmer. The VTAM operator can enter one or more options. For a description of the start options, see z/OS Communications Server: SNA Resource Definition Reference.

If more than one line is necessary for the start options, enter a comma and a closing parenthesis after the last option.

The values established by the start options go into effect when VTAM is started and remain in effect until VTAM is halted. Many of the options, however, can be modified with the MODIFY VTAMOPTS command while VTAM is running. You can use the DISPLAY VTAMOPTS command to display the values of the start options.

Examples

s net,,,(list=01)s net,,,(list=01) 
...
IST020I VTAM INITIALIZATION COMPLETE FOR level 
IST1349I COMPONENT ID IS dddd-ddddd-ddd 
IST1348I VTAM STARTED AS nodetype

For further information about these messages, see z/OS Communications Server: SNA Messages.