STATOPT
Purpose
Use the STATOPT operand values to control the functions of the status monitor. Code these operands following the applicable VTAM® node definition statements. Code this statement in the member that defines a resource. To implement changes to rerun the status monitor preprocessor, stop and restart the task specified by TSKID xxxxxVMT. If changing the member results in additional extents being used, stop and restart the NetView® program. After the preprocessor is finished, but before restarting the task, reaccess the minidisk containing DSINDEF.
- Code a specific description for the node in place of the default node description.
- Exclude the node from automatic reactivation by the NetView program.
- Exclude the node from status monitor activity displays.
- Omit the node, plus all the dependent lower nodes that follow, from the status monitor's view of the network definition.
- A statement following an initial major node macroinstruction statement (LBUILD, VBUILD, or BUILD macroinstruction) that defines a descriptive name for the major node when you do not want to use the default.
- A statement following a VTAM or NCP macroinstruction definition statement for a minor node.
If the VTAMLST definitions specified for status monitor processing contain resources of the same name and type, only the first of these resource definitions processed by the status monitor is updated. For example, if an NCP major node, NCP001, contains a definition for LU1, and a backup major node, NCP002, also contains a definition for LU1, the status is monitored for the first LU1 found (in DSINDEF). The status monitor is unaware of the second LU1.
If NCP001 is activated first, then deactivated, and then NCP002 is activated, the status monitor might not display the correct status for either of the LU1 resources. If NCP002 is then deactivated and NCP001 is activated again, the status monitor displays the correct status for the LU1 under NCP001.
It is not necessary to code a STATOPT statement for every VTAM node definition. The defaults for a node that is not coded are given in the operand descriptions that follow.
Syntax
- *
- Causes VTAM to treat the STATOPT statement as a comment statement. The asterisk must be in position 1.
- STATOPT=
- Is used to control major or minor node monitoring functions for
the status monitor. Use the following rules for adding the STATOPT statement:
- Insert the statements directly after the related VTAM macroinstruction definition. You cannot insert them between statements for the same VTAM macroinstruction (between continuation statements).
- Code each statement on a single record.
- If you use the network definition facility (NDF), specify your comment keywords on the GROUP macro after you have run NDF. If you do not, NDF generates PU and LINE statements for the GROUP macro and associates the comment keyword with only the last PU generated.
- STATOPT must start in position 16.
- All operands must follow directly after the equal sign (=). Do not leave a blank after the equal sign.
- The VTAM VBUILD statement must be present in application major node definitions or the STATOPT statements are not recognized by the preprocessor.
- If nodedesc is coded with one or more of the other operands, it must be the first operand. You can code the other operands in any order. Enclose nodedesc in single quotation marks.
- OMIT
- Excludes the node, plus all the dependent lower nodes, from the status monitor's view of the network definition. If you do not code this operand, the node is included in the status monitor's view of the network. When you specify OMIT after a VTAM definition for a cluster, the cluster and the terminals defined on the cluster are omitted from status monitor's view of the network definition.
- nodedesc
- Indicates the 14-character description of any major or minor node.
The description is displayed on the DESCRIPT form of the Status Detail
panels. The description must not include any single quotation marks. If you do not code a description, the STATOPT default descriptions for the node types in Table 1 are used.
Table 1. STATOPT Default Descriptions Node Group Default Description Application major nodeApplication minor nodeAPPL MAJ NODEAPPLICATIONCDRM major nodeCDRM minor nodeCDRM MAJ NODECDRMCDRSC major nodeCDRSC minor nodeCDRSC MAJ NODECDRSCLocal non-SNA terminal major nodeLocal non-SNA terminal minor nodeLOCAL 3270 MAJLOCAL dev-addrLocal SNA PU/LU major nodeLocal SNA PU minor nodeLocal SNA LU minor nodeLCL SNA MAJORLOCAL SNA PULOCAL SNA LUNCP major nodeLine minor nodeRemote PU minor nodeRemote LU minor nodeRemote cluster minor nodeRemote terminal minor nodeNCP MAJOR NODELINEPULUCLUSTERTERMINALChannel-channel major nodeLine minor nodePU minor nodeLU minor nodeCLUSTER minor nodeTERMINAL minor nodeCA MAJOR NODELINEPULUCLUSTERTERMINALSwitched major nodeSwitched PU minor nodeSwitched LU minor nodeSWITCHED MAJORSWITCHED PUSWITCHED LULAN major nodeLine minor nodePU minor nodeLAN major nodeLINEPUPACKET major nodeLINE minor nodePU minor nodeLU minor nodePACKET major nodeLinePULU - NOMONIT
- Excludes the node from automatic reactivation. Code the NOMONIT operand on a STATOPT statement to prevent automatic reactivation. If this operand is not present, the node is included for automatic reactivation when monitoring is on. Do not code this option for major nodes or applications. See O MONIT to determine how to enable monitoring.
- NOACTY
- Excludes the application node from activity recording. Code the NOACTY operand on a STATOPT statement to prevent activity displays. The default condition includes the node in the activity displays if the node is an application node.
Usage notes
If you code the STATOPT statement under the PCCU macro in the NCP major node, move the STATOPT statement after the BUILD macro.
Related statements
O MONIT