Professional Documents
Culture Documents
Installation Getting Started
Installation Getting Started
Version 6 Release 3
IBM
GI11-9443-08
Note
Before using this information and the product it supports, read the information in “Notices” on page
163.
This edition applies to version 6, release 3 of IBM Z NetView (product number 5697-NV6 ) and to all subsequent
versions, releases, and modifications until otherwise indicated in new editions.
This edition replaces GI11-9443-06.
© Copyright International Business Machines Corporation 2001, 2019.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
Contents
Figures................................................................................................................ vii
About this publication...........................................................................................ix
Intended audience...................................................................................................................................... ix
Publications................................................................................................................................................. ix
IBM Z NetView library............................................................................................................................ ix
Related publications .............................................................................................................................. x
Terminology in this Library.................................................................................................................... xi
Using IBM Z NetView online help.......................................................................................................... xi
Accessing publications online............................................................................................................... xi
Ordering publications ...........................................................................................................................xii
Accessibility ............................................................................................................................................... xii
Tivoli user groups....................................................................................................................................... xii
Support information................................................................................................................................... xii
Conventions used in this publication......................................................................................................... xii
Typeface conventions ......................................................................................................................... xiii
Operating system-dependent variables and paths.............................................................................xiii
Syntax diagrams...................................................................................................................................xiii
iii
Allocating Data Sets Using the CNMSJ002 Job........................................................................................ 21
Changing Sample Installation Jobs Using the CNMSJ000 Job................................................................ 23
Loading Members of Partitioned Data Sets Using the CNMSJ003 Job.................................................... 24
Reviewing Canzlog Archiving Allocation Parameters............................................................................... 25
Allocating Data Sets for Canzlog Print.......................................................................................................26
Allocating VSAM Clusters Using the CNMSJ004 Job................................................................................26
Initializing the Saved Packet Trace Database Using the CNMSJ033 Job................................................ 28
iv
Configuring Allocation Parameters for Canzlog Archive Data Sets.....................................................54
Setting up Security............................................................................................................................... 55
Assigning Unique EMCS Console Names.............................................................................................55
Disabling XCF Group Participation.......................................................................................................56
Specifying Commands to Run Automatically When the NetView Program Is Started....................... 56
Starting the NetView Subsystem Interface......................................................................................... 57
Specifying the Subsystem Command Designator............................................................................... 57
Including Japanese Support................................................................................................................ 57
CNMSTYLE Processing......................................................................................................................... 58
Using the Report Generator................................................................................................................. 60
Starting the NetView Program Before Starting JES.................................................................................. 66
Starting the NetView Program Without Restarting the MVS System........................................................67
v
Appendix C. NetView Samples Reference........................................................... 119
Notices..............................................................................................................163
Programming Interfaces..........................................................................................................................164
Trademarks..............................................................................................................................................164
Privacy policy considerations.................................................................................................................. 164
Index................................................................................................................ 167
vi
Figures
6. auxInitCmd Statements.............................................................................................................................. 64
vii
24. PING command output............................................................................................................................. 82
viii
About this publication
The IBM Z® NetView® product provides advanced capabilities that you can use to maintain the highest
degree of availability of your complex, multi-platform, multi-vendor networks and systems from a single
point of control. This publication, IBM Z NetView Installation: Getting Started, provides information about
installing the NetView program after creating the target libraries using SMP/E.
Intended audience
This publication is for system programmers who install the NetView program.
Publications
This section lists publications in the IBM Z NetView library and related documents. It also describes how
to access NetView publications online and how to order NetView publications.
Related publications
You can find additional product information on the IBM Z NetView web site at https://www.ibm.com/us-
en/marketplace/ibm-tivoli-netview-for-zos.
For information about the NetView Bridge function, see Tivoli NetView for OS/390® Bridge Implementation,
SC31-8238-03 (available only in the V1R4 library).
Accessibility
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to
use software products successfully. Standard shortcut and accelerator keys are used by the product and
are documented by the operating system. Refer to the documentation provided by your operating system
for more information.
For additional information, see the Accessibility appendix in the User's Guide: NetView.
Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following
ways for you to obtain the support you need:
Online
Please follow the instructions located in the support guide entry: https://www.ibm.com/support/
home/pages/support-guide/?product=4429363.
Troubleshooting information
For more information about resolving problems with the IBM Z NetView product, see the IBM Z
NetView Troubleshooting Guide. You can also discuss technical issues about the IBM Z NetView
product through the NetView user group located at https://groups.io/g/NetView. This user group is for
IBM Z NetView customers only, and registration is required. This forum is also monitored by
interested parties within IBM who answer questions and provide guidance about the NetView
product. When a problem with the code is found, you are asked to open an official case to obtain
resolution.
Syntax diagrams
The following syntax elements are shown in syntax diagrams. Read syntax diagrams from left-to-right,
top-to-bottom, following the horizontal line (the main path).
• “Symbols” on page xiii
• “Parameters” on page xiv
• “Punctuation and parentheses” on page xiv
• “Abbreviations” on page xv
For examples of syntax, see “Syntax examples” on page xv.
Symbols
The following symbols are used in syntax diagrams:
Parameters
The following types of parameters are used in syntax diagrams:
Required
Required parameters are shown on the main path.
Optional
Optional parameters are shown below the main path.
Default
Default parameters are shown above the main path. In parameter descriptions, default parameters
are underlined.
Syntax diagrams do not rely on highlighting, brackets, or braces. In syntax diagrams, the position of the
elements relative to the main syntax line indicates whether an element is required, optional, or the
default value.
When you issue a command, spaces are required between the parameters unless a different separator,
such as a comma, is specified in the syntax.
Parameters are classified as keywords or variables. Keywords are shown in uppercase letters. Variables,
which represent names or values that you supply, are shown in lowercase letters and are either italicized
or, in NetView help, displayed in a differentiating color.
In the following example, the USER command is a keyword, the user_id parameter is a required variable,
and the password parameter is an optional variable.
USER user_id
password
COMMAND_NAME opt_variable_1,,opt_variable_3
You do not need to specify the trailing positional commas. Trailing positional and non-positional commas
either are ignored or cause a command to be rejected. Restrictions for each command state whether
trailing commas cause the command to be rejected.
Syntax examples
The following examples show the different uses of syntax elements:
• “Required syntax elements” on page xv
• “Optional syntax elements” on page xv
• “Default keywords and values” on page xv
• “Multiple operands or values” on page xvi
• “Syntax that is longer than one line” on page xvi
• “Syntax fragments” on page xvi
A required choice (two or more items) is shown in a vertical stack on the main path. The items are shown
in alphanumeric order.
REQUIRED_OPERAND_OR_VALUE_1
REQUIRED_OPERAND_OR_VALUE_2
OPTIONAL_OPERAND
A required choice (two or more items) is shown in a vertical stack below the main path. The items are
shown in alphanumeric order.
OPTIONAL_OPERAND_OR_VALUE_1
OPTIONAL_OPERAND_OR_VALUE_2
KEYWORD2 VALUE1
KEYWORD3 VALUE2
REPEATABLE_OPERAND_OR_VALUE_1
REPEATABLE_OPERAND_OR_VALUE_2
REPEATABLE_OPERAND_OR_VALUE_3
value_n )
OPERAND7 OPERAND8
Syntax fragments
Some syntax diagrams contain syntax fragments, which are used for lengthy, complex, or repeated
sections of syntax. Syntax fragments follow the main diagram. Each syntax fragment name is mixed case
and is shown in the main diagram and in the heading of the fragment. The following syntax example
shows a syntax diagram with two fragments that are identified as Fragment1 and Fragment2.
COMMAND_NAME Fragment1
Fragment2
Fragment1
KEYWORD_A= valueA KEYWORD_B KEYWORD_C
Fragment2
KEYWORD_D KEYWORD_E= valueE KEYWORD_F
Before starting the installation and configuration procedures described in this book, perform the SMP/E
installation of the NetView product that is listed in the NetView program directory.
This document is designed to guide you through the installation, configuration, and verification of the
NetView program in a minimum amount of time. The assumption for this document is that this is the first
time that the NetView program is being installed on this system. Initially, make only essential changes to
the sample definitions provided with the NetView program. Your first objective is a fast and error-free
installation.
This chapter describes:
• The organization of the NetView program
• Installation of the NetView program
Migrating Users: Refer to the IBM Z NetView Installation: Migration Guide for information on new and
deleted functions from prior releases of the NetView product, as well as migration considerations for base
functions.
Naming Conventions
The NetView program uses the following types of data sets:
• System data sets
• NetView user partitioned data sets
• NetView VSAM data sets
• NetView sequential data sets
• UNIX system services (USS) file system data sets
./usr/lpp/netview/v6r3/bin
./usr/lpp/netview/v6r3/mibs
./usr/lpp/netview/v6r3/lib
./usr/lpp/netview/v6r3/samples
./usr/lpp/netview/v6r3/samples/at-tls
./usr/lpp/netview/v6r3/samples/properties
./usr/lpp/netview/v6r3/www
./usr/lpp/netview/v6r3/www/img
Installation Package
If you are installing the NetView program for the first time, you will find familiar IBM fulfillment methods
(such as Shop zSeries), installation tools (such as SMP/E or InstallShield), and installation documentation,
including a program directory.
Product media (or their electronic representation) are in the standard IBM relfile format that IBM
software manufacturing uses to create the images for installation systems such as ServerPac and CBPDO.
If you receive your product through the CBPDO system, maintenance is included on the media for you to
install. If you receive your product as part of a ServerPac or SystemPac system, maintenance is
preinstalled.
For detailed information about the installation package contents, see the NetView program directory.
Workstation-based NetView code is shipped in two formats:
• DVD
http://www.ibm.com/software/tivoli/products/netview-zos/
For service updates to workstation-based NetView code, see the Tivoli website.
The NetView program directory lists APARs from the previous release that have been created for z/OS
products to work with this NetView release.
The program directory also lists APARs from the previous NetView releases that are incorporated into the
release. Check with the IBM Support Portal to obtain the latest available service.
Refer to the IBM Z NetView Tuning Guide and the NetView program directory for information about
estimating the hardware and software resources required to install NetView. If you cannot determine how
to estimate the resource types, call IBM Software Support at 1-800-237-5511 or contact your IBM
Software Support account representative.
Installation Results
When you complete the procedures described in this book, the following functions are operational:
• Base NetView components including the command facility, hardware monitor, and session monitor
• Automation table to respond automatically to messages and MSUs, including alerts
• Canzlog log that stores NetView and system messages
• NetView log that stores messages and commands
• Save / Restore VSAM facility to save critical information across NetView restarts
• NetView to NetView remote command processing (RMTCMD)
• TCP/IP connection management
• Discovery manager
• XCF services
When the NetView program is installed and functioning correctly, many NetView functions are not yet
active.
Follow these steps to prepare your MVS system if you are installing the NetView program:
• Use SMP/E to load the NetView V6.3 libraries.
• Update the number of Language Processor (REXX) environments.
• Update SYS1.PARMLIB members.
• Modify the IEFUSI exit.
• Review the attributes assigned to extended multiple console support (EMCS) consoles.
The NetView program consists of the following address spaces:
• The base NetView program including the following components:
– Command facility
– Session monitor
– Status monitor
– Hardware monitor
– Automated Operations Network (AON)
• NetView subsystem address space, which may include the program-to-program interface (PPI)
• Event/Automation Service
• Graphic Monitor Facility host subsystem (GMFHS)
• Resource Object Data Manager (RODM)
• Z NetView Enterprise Management Agent
– The Z NetView Enterprise Management Agent is a separately orderable feature.
This book guides you through the installation and configuration of base NetView and the NetView
subsystem address application.
LPALSTxx
The LPALST member contains the names of program libraries you want the system to concatenate to
SYS1.LPALIB. This concatenation is called the LPALST concatenation, which the system uses to build the
pageable link pack area (PLPA).
Add the SCNMLPA1 NetView library to the LPALST member.
Data sets to be concatenated to the SYS1.LPALIB data set must be cataloged in the system master
catalog or in a user catalog identified in the LPALST member. If the SCNMLPA1 target data set is not
cataloged in the system master catalog but is cataloged in a user catalog, specify (in parenthesis
immediately following the data set name) the 1- to 6-character VOLSER of the pack on which the
SCNMLPA1 data set resides, for example:
NETVIEW.V6R3M0.SCNMLPA1(NVPTFM)
In this case, the system verifies that the NETVIEW.V6R3M0.SCNMLPA1 data set has a user catalog entry
pointing to the NVPTFM volume.
LNKLST concatenation
If you are using LNKLST instead of a STEPLIB DD statement in any of your NetView JCL members (for
example, your startup procedure), update your PROGxx member in the SYS1.PARMLIB data set to include
the following program libraries as extensions to the SYS1.LINKLIB data set:
• NETVIEW.V6R3M0.SCNMMJPN (if the Japanese NetView program is being installed)
• NETVIEW.V6R3M0.SAQNLINK
• NETVIEW.V6R3M0.CNMLINK
• NETVIEW.V6R3M0.SCNMLNKN
Usage notes:
1. If you installed the IBM Z NetView for Continuous Availability product, make sure that the modules in
SAQNLINK library are loaded prior to those in the CNMLINK library.
2. The SCNMLNKN data set is used for RODM trace, MVS command exit, and DSIPHONE (which is used
by CMDSERV and by the UNIX, TSO command, and REST servers). The SCNMLNKN data set is not
referenced in the NetView program samples; JCL for those samples must specify the SCNMLNKN data
set on the STEPLIB DD statement if it is not included in the PROGxx member.
APF authorization
The following libraries must be authorized with the APF facility. To be authorized, a library name and
volume ID must be in the list of authorized libraries in the PROGxx member of SYS1.PARMLIB.
1. If these are not already authorized, authorize all the libraries from the //STEPLIB, //VTAMLIB,
and //NCPLOAD concatenations in your VTAM start procedure. The VTAM start procedure, CNMSJ008
(CNMNET), in NETVIEW.V6R3M0.CNMSAMP is the default member shipped with the NetView program.
2. Authorize all the libraries from the //STEPLIB concatenation in the following procedures:
• NetView start procedure, CNMSJ009 (CNMPROC)
• NetView procedure to start the subsystem interface (SSI) address space, CNMSJ010 (CNMPSSI)
• RODM start procedure, EKGXRODM
• GMFHS start procedure, CNMSJH10 (CNMGMFHS)
• Event/Automation Service (E/AS) start procedure, IHSAEVNT
These procedures are located in the NETVIEW.V6R3M0.CNMSAMP samples library.
3. Authorize the following NetView libraries:
• NETVIEW.V6R3M0.SAQNLINK
• NETVIEW.V6R3M0.SCNMLNK1
• NETVIEW.V6R3M0.SCNMLPA1
• NETVIEW.V6R3M0.CNMLINK
• NETVIEW.V6R3M0.SCNMLNKN
4. If you are installing the NetView Japanese program, authorize the SCNMMJPN data set. This data set
is listed in the //STEPLIB concatenation of CNMPROC.
Exit routines
Update the PROGxx member if you use the following exit routines:
1. The MVS IEFACTRT SMF installation exit receives control from the system when a job or job step ends,
either normally or abnormally. The NetView program provides an IEFACTRT sample exit (CNMSMF3E)
that passes data across the PPI to a receiver which issues a message that can be automated using the
NetView automation facilities. If you plan to use the CNMSMF3E sample as an IEFACTRT exit routine,
associate the CNMSMF3E sample to the IEFACTRT exit by adding the following statement to your
PROGxx member:
More than one exit routine can be defined for the IEFACTRT exit, so there might be more than one
EXIT statement for the SYS.IEFACTRT exit in your PROGxx member.
2. You can use the Canzlog log to view the system log messages that were issued before the NetView
subsystem was initialized. To enable these preinitialization messages to be written to the Canzlog log,
add this statement to the PROGxx member:
Additional information
If you want information about... Refer to...
APF authorization z/OS library
CNMSMF3E sample IBM Z NetView Installation: Configuring Additional
Components
NetView agent IBM Z NetView Installation: Configuring the NetView
Enterprise Management Agent
IEFSSNxx
The IEFSSNxx member in the SYS1.PARMLIB data set contains parameters that define the secondary
subsystems during MVS system initialization. Each SUBSYS statement in the IEFSSNxx member contains
parameters that define a single subsystem.
Usage notes:
1. The name of the subsystem for the NetView program is 4 characters and must be the first 4 characters
of the procedure names that you use to start the following address spaces:
• NetView subsystem (sample CNMSJ010)
• NetView application (sample CNMSJ009)
For example, if both procedure names begin with CNMP, you can code the following entry in the
IEFSSNxx member:
Create one entry for each instance of the NetView program that you plan to start on this system. Make
sure that you specify the INITRTN value (DSI4LSIT) for each entry.
2. Any subsystem name that you define for the NetView program can be used only for the NetView
program. If you choose a subsystem name that was previously used, restart MVS before using the
subsystem name. If the NetView program is started as a job rather than as a task, the job name must
have the same first four characters as the subsystem interface and startup procedure.
3. Consider the following conditions before deciding where to place the NetView subsystem name in the
IEFSSNxx member:
• If you place the NetView subsystem name after other subsystem names in the IEFSSNxx member,
all MVS messages and commands received by the NetView subsystem are affected by the changes
made by the other subsystems that are listed before the NetView subsystem.
• If you are defining more than one NetView subsystem (SSI) in the IEFSSNxx member, the first
NetView subsystem must come before the BEGINPARALLEL keyword. Any remaining NetView
subsystems can be defined following the BEGINPARALLEL keyword. If you are defining only one
NetView subsystem, the NetView subsystem can be placed before or after the BEGINPARALLEL
keyword in the IEFSSNxx member.
• By default, the NetView program does not send unsolicited foreign messages (those originating at
another MVS LPAR in the same sysplex that are not specifically destined for an EMCS console owned
by a NetView operator) to Canzlog. To have foreign messages eligible to be logged in Canzlog,
specify the following parameter on the first SUBSYS statement that contains INITRTN(DSI4LSIT):
INITPARM('LOGFORN')
Note that the NetView subsystem initialization routine ignores any value specified on INITPARM on a
SUBSYS statement containing INITRTN(DSI4LSIT) that is not the first such statement read by MVS.
4. The DSI4LSIT initialization routine allocates the CNMCANZ0 data space where MVS and NetView
messages are stored. The data space wraps when it reaches its current usable size. CNMCANZ0 is the
main Canzlog data space, and by default is allocated with a static data space size of 2 GB. If the data
space is specified as dynamic, it will allocate 128 MB of storage and grow by 8 MB as necessary
accommodate message processing until it reaches its maximum size.
To explicitly define the data space size to be a maximum of 2GB, specify the following value on the
INITPARM parameter on the first SUBSYS statement that contains INITRTN(DSI4LSIT):
INITPARM('FULLDS')
INITPARM('TINYDS')
To explicitly define the data space size to be static, which means the entire data space storage will be
used before wrapping occurs, specify the following value on the INITPARM parameter on the first
SUBSYS statement that contains INITRTN(DSI4LSIT):
INITPARM('STATIC')
To explicitly define the data space size to be dynamic, which means only 128 MB of data space storage
will be used before wrapping occurs, unless more space is needed to accommodate situations where
logging of messages is much faster than automation of messages, specify the following value on the
INITPARM parameter on the first SUBSYS statement that contains INITRTN(DSI4LSIT):
INITPARM('DYNAMIC')
Note that when DYNAMIC is used and Canzlog data is not being archived, the amount of messages that
can be browsed is less than when the Canzlog data space is defined as STATIC.
The NetView subsystem initialization routine ignores any value specified on the INITPARM parameter
on a SUBSYS statement that contains INITRTN(DSI4LSIT) that is not the first such statement read
by MVS.
Multiple values can be specified on the INITPARM parameter. For example, if the TINYDS, DYNAMIC,
and LOGFORN values are required, specify these values on the same INITPARM parameter:
INITPARM('TINYDS,DYNAMIC,LOGFORN')
Warning: Proper planning for real and auxiliary storage must be performed before enabling the
Canzlog data space, as system slowdown and hangs can occur with insufficient storage.
5. If you do not add the NetView subsystem to the subsystem name table, you can dynamically add it
before starting the NetView subsystem. For information on dynamically adding the subsystem name to
the table, see “Starting the NetView Program Without Restarting the MVS System” on page 67.
IEASYSxx
The IEASYSxx member in the SYS1.PARMLIB data set contains system parameters.
If you are using the status monitor, system automation, or Automatic Restart Manager (ARM) support,
update the MAXUSER and RSVNONR values using the following steps:
• For the status monitor, determine the number of times you expect to stop and restart the NetView
program over the life of the MVS IPL.
• For system automation, determine the number of times you expect to stop and restart the NetView
subsystem interface (SSI) address space over the life of the MVS IPL.
• If both the preceding sets of conditions apply, add the values together that you computed.
Increase the number of address spaces available to MVS by this value by changing the MAXUSER or
RSVNONR value, or both:
IEASYMxx
Add a SYSDEF statement in member IEASYMxx to identify user-defined system symbolic variables for the
NetView program, including the TCP/IP application name, RODM name, and network ID.
Setting these symbolic variables can alleviate modification of many of the NetView initialization members
unless some default parameter such as a TCP/IP port needs to be changed.
For example, you can define the following symbolic variables (these are the default names used in the
NetView program):
SYSDEF SYMDEF(&CNMTCPN='tcpip_name')
SYSDEF SYMDEF(&CNMRODM='rodm_name')
SYSDEF SYMDEF(&CNMNETID='network_id')
Usage note:
If you need to produce an actual ampersand (&) in the text of members that support symbolic
substitution, one easy method is to define the ampersand as follows in your system substitution tables.
SYSDEF SYMDEF(&.='&')
You can use the symbol &. to specify an ampersand in this statement anywhere without risking an
inadvertant symbol substitution.
The initialization members that use the symbolic variables are shown in this table.
Note: After you run job CNMSJBUP (see “Creating the Installation JCL Samples Library Using Job
CNMSJBUP” on page 21), you can use sample CNMSJM12 in data set NETVIEW.V6R3USER.INSTALL as
IKJTSOxx
The IKJTSOxx member contains TSO/E settings, including command and program authorization
information.
If you plan to use the NetView agent, add the KPDDSCO command in the authorized program (AUTHPGM)
section:
AUTHPGM NAMES(KPDDSCO,pgm2,...)
IBM Tivoli Monitoring components require the KPDDSCO command to be authorized in the IKJTSOxx
member for persistent data store processing.
COUPLExx
The COUPLExx member contains cross-system coupling facility (XCF) parameters.
Add the following DATA statement to identify the automatic restart manager (ARM) couple data to XCF:
Initialize the primary and alternate ARM couple data sets after you create them.
SMFPRMxx
To write the following records to the System Management Facility (SMF) log, ensure that member
SMFPRMxx in the SYS1.PARMLIB data set is set up to collect type 37, type38, and type 39 SMF records
accordingly:
• SMF record type 37: hardware monitor records
• SMF record type 38: authorization, task resource utilization, and command resource utilization records
• SMF record type 38: session monitor records
The SMF 38 subtype 4 record is written on an interval. Set the SMF interval value, and if desired, the SMF
synchronization value.
If you plan to use the CNMSMF3E sample as an IEFACTRT exit routine, verify that type 30 SMF records
are set up to be collected and that the EXITS operand of the SYS specification includes the IEFACTRT exit.
For example, the following statement causes SMF record types 0 through 255 to be collected and the
IEFACTRT exit to be called:
SYS(TYPE(0:255),EXITS(IEFU83,IEFU84,IEFU85,IEFACTRT,IEFUJV,IEFUSI,
IEFUJP,IEFUSO,IEFUJI,IEFUTL,IEFU29,IEFUAV),NOINTERVAL,NODETAIL)
NetView • The NetView program creates an internal trace data space at initialization that is
managed through the TRSIZE parameter in the CNMPROC startup procedure.
• The Canzlog archiving function creates data spaces CNMCANZ1, CNMCANZ2, …,
CNMCANZ9, CNMCANZA that are used for browsing archived Canzlog data. The
number of data spaces that are created is limited by the specification on the
ARCHIVE.BROWSE.DATASPACES or ARCHIVE.BROWSE.MAXDSPSIZE statement
in the CNMSTYLE member. The data space(s) will be created as necessary to
accommodate usage requirements, and their sizes can increase up to the defined
limit.
• TCP/IP connection management (TCPCONN) creates a data space for each TCP/IP
stack on your system.
• The IP packet trace (PKTS) function creates a data space for each TCP/IP stack on
your system.
• The OSA packet trace (OPKT) function creates a data space for each TCP/IP stack
on your system.
• If the DISCOVERY tower is enabled in the CNMSTYLE member, the real-time SMF
data network management interface (SYSTCPSM) creates a data space for each
TCP/IP stack on your system.
• As of V6R3, if LOGSMF is enabled in the Command Statistics function, a data
space is created to store Command Statistics data before being written into SMF.
The size of the data space is specified by the CMDMON.INIT.SMFDSSIZE
CNMSTYLE statement.
RODM RODM creates and utilizes three data spaces. Note that RODM allocates a 2
gigabyte data space at initialization.
NetView agent • The NetView agent creates a data space for each NetView program with which it
communicates.
• A second data space is created if the value of the NACMD.PERSIST statement in
the CNMSTYLE member is greater than zero.
The IEFUSI exit is passed the address of the program name on input.
This chapter describes the steps that help you prepare the NetView program. Each step gives you explicit
directions for installing an operational NetView system. Unless otherwise stated, each step is required for
a NetView system to be functional.
The sequential data sets that are allocated by the CNMSJ002 job are listed in Table 5 on page 23.
The data sets allocated by the CNMSJ002 job are used to hold user data. Initially, they are empty data
sets. In some cases, you might need to make modifications to the data set members provided with the
NetView program. To do this, copy the members that you need to modify from the NETVIEW.V6R3M0
data set to the NETVIEW.V6R3USER.domain data set and then make modifications to the copied
members in the user data set. This preserves the original member and protects your modifications when
maintenance is applied. For example, to make changes to the CNMSTUSR member, copy the CNMSTUSR
member from the NETVIEW.V6R3M0.DSIPARM data set to the NETVIEW.V6R3USER.CNM01.DSIPARM
data set, and then make your modifications to the CNMSTUSR member in the user DSIPARM data set.
Although data set NETVIEW.V6R3USER.CNM01.DSIPRF is not used for operator profiles if an SAF
security product is used exclusively for operator definitions, it is required to be present when the NetView
address space is started. Because this data set is used for other members besides operator profiles, such
as DSITCPRF.
Allocate the data sets in the following way:
1. Review the variables and associated comments in the CNMSJ002 job. Change the &UNIT and &SER
variables to match your installation, if needed.
2. Change the &DOMAIN variable to match the NetView domain name you are installing.
3. Run CNMSJ002.
4. Verify your return codes before continuing with the next step.
Usage notes:
a. These samples are used as input for job CNMSJ004. For more information, see “Allocating VSAM
Clusters Using the CNMSJ004 Job” on page 26.
b. If you specify NOVOLSER, the volume specification is removed in the VSAM allocation member.
This allows the VSAM cluster to be allocated to any available volume.
3. Run CNMSJ000.
4. Verify your return codes before continuing with the next step.
The remaining steps assume that you are installing the NetView program in subarea 01 and domain
CNM01. If you are installing the NetView program in a subarea other than 01 and domain CNM01, make
the appropriate substitutions throughout this installation.
To copy members:
1. If necessary, edit the CNMSJ003 job to match your system naming conventions. You can change the
specification for the Q2 variable on the PDS2 step to use a different high-level qualifier for PROCLIB.
2. Step PDS2 is initially commented out to prevent the overlaying of existing members in the target
PROCLIB data set. Before running this step, ensure that the members that are copied do not exist in
the PROCLIB data set, so they do not get replaced (see Table 7 on page 25).
3. Run the CNMSJ003 job.
4. Verify your return codes before continuing with the next step.
BNH803I VALUE *NONE* FOR KEYWORD ARCHIVE.HLQ CONFLICTS WITH VALUE YES FOR KEYWORD ARCHIVE.WRITE
The Canzlog archiving function is disabled and Canzlog data is not archived. By not setting up the archive
data sets, you can lose message data when the Canzlog log wraps and writes over previously stored
message data.
NetView provides functionality for printing Canzlog messages to a sequential data set or a member of a
partitioned or partitioned extended data set by using the PRINT command. The data sets need to be
allocated before you use PRINT. The following example shows attributes for defining a sequential data
set:
Organization . . : PS
Record format . . : FB
Record length . . : 134
Block size . . . . : 27872
1st extent cyls . .: 15
Secondary cyls . . : 2
The next example shows sample attributes for a partitioned or partitioned extended data set:
Organization . . . . . : PO
Record format . . . . : FB
Record length . . . . : 134
Block size . . . . . : 27872
1st extent cylinders..: 15
Secondary cylinders ..: 2
A default data set for use with the PRINT command can be defined in CNMSTYLE. For information about
configuring CNMSTYLE to support Canzlog printing, see Configuring parameters for Canzlog Print in
Installation: Configuring Additional Components.
Note: All members referenced by the CNMSJ004 job for deleting or allocating VSAM data sets are
found in the NETVIEW.V6R3USER.INSTALL data set.
2. If you want to define a security password for the VSAM data sets, add the password to the CNMSTPWD
member in the DSIPARM data set. Also add this password to the VSAM allocate members (for example
CNMSI101). Specify a password on the catalog that contains the entry for the data set before the
system verifies the password for that data set.
To run the CNMSJ004 job to allocate or reallocate VSAM clusters, follow these steps:
1. If you are reallocating VSAM clusters, edit member CNMSID01 to uncomment the DELETE statements
for the VSAM clusters to be reallocated.
2. Run the CNMSJ004 job.
3. Verify that all steps ran correctly. If you are reallocating VSAM clusters and uncommented only some
of the names in member CNMSID01, the DEFINE statements for the remaining VSAM clusters might
fail. This is acceptable because those VSAM clusters were not being reallocated.
If you are operating in an environment such as an SMS environment and receive an open error such as the
DSI556I message with a return code of X'08' and an ACB error field value of X'A8', you can delete and
redefine the database, moving it to a different volume. To accomplish these tasks:
1. Free the database.
2. Delete the database.
Initializing the Saved Packet Trace Database Using the CNMSJ033 Job
The CNMSJ033 job loads an initialization record into the Saved Packet Trace database that was allocated
using the CNMSJ004 job.
To initialize the Saved Packet Trace database:
1. In the REPRO step, review and update as necessary the OUTDATASET high-level qualifier for your local
NetView VSAM catalog. You defined the catalog using the CNMSJ001 job.
2. Run the CNMSJ033 job.
3. Verify your return codes.
If you need to rerun the CNMSJ033 job for any reason, first update and rerun the job you ran in
“Allocating VSAM Clusters Using the CNMSJ004 Job” on page 26 to delete and reallocate the Saved
Packet Trace database.
to
Usage notes:
1. You cannot change the corresponding task ID on the TASK definition in the CNMSTASK member in
DSIPARM.
2. All APPL statements with the CNM01 name prefix must follow the existing DOMAINID constraints.
3. An APPL name prefixed with CNM01 cannot have its suffix changed. For example, CNM01LUC must
retain the LUC suffix.
4. Verify the original APPL name with the TASK statement in the CNMSTASK member. The MEM operand
specifies the startup initialization member in DSIPARM.
5. Command help panels reference the original APPL names.
6. You cannot change BNJHWMON because of its downward compatibility with the BNJDSERV task.
7. You cannot change ALIASAPL because it is necessary for the VTAM Alias Name Translation function to
work.
8. The ACBNAME keyword for CNM01VPD in A01APPLS must match the name in DSIVPARM.
to:
Note:
1. If you code the optional ACBNAME operand on the APPL statement, it must match the APPL name in
column 1. Therefore, if you change the DOMAIN name, you must also change ACBNAME.
to:
VTAM does not open more than one access method control block with AUTH=PPO specified. If you are
migrating and running a previous release of the NetView program concurrently with the NetView program
for verification or testing, change this statement from AUTH=(NVPACE,SPO) back to
AUTH=(NVPACE,PPO).
MODETAB=AMODETAB,DLOGMOD=DSILGMOD
Check the DLOGMOD operands for your applications and ensure that they are pointing to the proper
entries for your installation.
* STATOPT='NETVIEW 000'
If you want to redefine the name of this resource, or any other resource, change the STATOPT statement.
You must specify an APPL statement for each concurrent NetView operator. Each APPL statement name
contains a 3-character suffix which is a hexadecimal number in the range of 000–FFF. If you are starting
autotasks before VTAM, you must have enough consecutively numbered APPL statements to allow each
autotask to obtain one. The numbers after those reserved for the autotasks do not need consecutive
suffixes.
To enable takeover or reconnect, include PASS value in your AUTH= definition. If PASS is not specified
and a takeover or reconnect is attempted, the authorized receiver receives message DSI133I, and the
operator attempting to log on receives the following message:
If you are not using the status monitor preprocessor, define one APPL statement using wildcard
characters (??) for multiple concurrent NetView operators. See the following example:
The maximum number of concurrent users of NetView application LUs is 4096. Users of the NetView
application LUs include the following operators and tasks:
• Started hardcopy tasks (for LUs defined on HARDCOPY statements)
• Started autotasks
• Operators logged on through real or simulated terminals, the web browser, or the NetView management
console client
Factors such as local system queue area (LSQA) storage and the number of tasks can affect the maximum
limit for the number of concurrent users of NetView application LUs to be less than 4096.
If you have more than five concurrent TAF users of operator control sessions, you need to add APPL
statements.
Note: If the status monitor preprocessor is not used, you can define one APPL statement using the
wildcard character (?). For example:
If you have more than 20 concurrent TAF users of full-screen sessions, you need to add APPL statements.
Note: If the status monitor preprocessor is not used, you can define one APPL statement using the
wildcard character (?). For example:
This statement points to DSIALTAB, which contains examples of alias translation statements.
To add an alias data set member that defines one of your networks, add the member name to the
statement in DSIALATD in the following way:
Create a data set member of the same name following the format of DSIALTAB to define your alias
translations. You can add more than one member name to the same ALIASMEM statement. Ensure that
you either modify DSIALTAB with valid aliases or comment out the example statements provided.
Note: Do not use alias names to translate NetView APPL names, including the domain ID, and any names
that are constructed from it; for example, A01M, A01M001, A02M, and A02M002.
DSIALTAB provides examples of the following statements. Modify these statements for your own
environment.
ORIGNET Statement
For each member name you code on an ALIASMEM statement, code at least one ORIGNET definition
statement for each network that requires alias name translations. The ORIGNET statement has the
following format:
ORIGNET netid
Where:
netid
Is the network name as coded on the NETWORK statement for the CDRM major node, or on the VTAM
NETID start option. This name always represents the network that knows the resource by its alias
name.
The following example shows this statement:
ORIGNET NETA
LU Statement
If you have LUs with the same name in more than one network, code the LU name translation statement.
With this name translation, the LU can be known in its owning network by its real name and in other
networks by the assigned alias name. The LU statement has the following format:
LABEL LU realname,ownernet,
aliasname[,ownersscp]
Where:
realname
Is the LU name as it is defined in the domain where the LU resides.
ownernet
Is the 1–8 character network name of the network where the LU is known by its realname.
ORIGNET NETA
LABEL LU TERM1,NETB,TERM1B
Where:
adjacnme
Is the COS name defined in the adjacent or destination network that provides the class-of-service
equivalent to the COS entry specified in the local-name class of service.
adjacnet
Is the 1–8 character NETID of the adjacent network where the equivalent class of service is defined.
localnme
Is the name of the class of service defined in the network specified on the ORIGNET definition
statement.
The following example shows this statement:
ORIGNET NETA
LABEL COS QUICK,NETB,FAST
You can use the same local name (or alias) within one network for different adjacent networks. Also, each
adjacent name can be given any number of aliases or local names.
MODE Statement
In interconnected networks, the set of logon mode entry names used in one network can be different
from the names used in another network. However, two logon mode entries with different names can
result in the session parameters being the same. With the name translation facility, you can make a logon
mode entry name used in one network equivalent to a name in another network. In this way, you can
access the information in a logon mode table from another network without changing the logon
procedures used in either network.
The MODE statement has the following format:
Where:
destname
Is the name of the logon mode entry defined in the destination network.
ORIGNET NETA
LABEL MODE LOG1B,NETB,LOG1A
ORIGNET NETB
LABEL MODE LOG1A,NETA,LOG1B
The logon mode entry name defined to NETA as LOG1A is known in NETB as LOG1B. The logon mode
entry name defined to NETB as LOG1B is known in NETA as LOG1A.
For more information about rules for name translation, refer to the z/OS Communications Server library.
Reviewing VTAM and NCP Definitions for Mode Table and USS Table
Changes
The sample definitions include the A01SNA (CNMS0073) statement for SNA locally attached terminals,
the A01LOCAL (CNMS0016) statement for non-SNA locally attached terminals, and your VTAM and NCP
definitions for any mode table changes. Update your USS table for the NetView program and reflect that
change in your definitions. The USS table is AUSSTAB (CNMS0011) in the samples.
Note: If you modify AUSSTAB, run CNMSJ006 to reassemble and link edit the table and carry out the
changes.
MODIFY NET,TABLE,NEWTAB=AMODETAB,OPTION=LOAD
// DD DISP=SHR,DSN=NETVIEW.V6R3USER.CNM01.VTAMLST
The VTAMLST data set that is shipped with the NetView program contains data set members that you
might have already customized. Protect any members that you customized. Otherwise, the VTAM
program does not perform as expected.
2. Add the following data sets to the VTAMLIB DD statement:
• Add the USER.VTAM data set before the SYS1.VTAMLIB data set
• If you plan to use the NetView Application Management Instrumentation, (AMI) or status monitor
functions, add the SCNMLNK1 data set after the SYS1.VTAMLIB data set
// DD DISP=SHR,DSN=NETVIEW.V6R3M0.SCNMLNK1
//VTAMLIB DD DISP=SHR,DSN=NETVIEW.V6R3USER.VTAMLIB
// DD DISP=SHR,DSN=SYS1.VTAMLIB
// DD DISP=SHR,DSN=NETVIEW.V6R3M0.SCNMLNK1
Usage notes:
1. Sample CNMSJ002 allocates the VTAMLST and VTAMLIB data sets. For more information, see
“Allocating Data Sets Using the CNMSJ002 Job” on page 21.
2. If you added the SCNMLNK1 data set to the VTAMLIB DD statement, make sure that it is APF-
authorized. For information about authorizing this data set, see “PROGxx” on page 11.
3. If you added the VTAMLIB data set to the VTAMLIB DD statement, make sure that it is APF-authorized.
For information about authorizing this data set, see “PROGxx” on page 11.
4. The modifications you made to your VTAM start procedure go into effect when you restart the VTAM
program.
Before starting the NetView program, review the following START procedures:
• CNMPROC (CNMSJ009) for the NetView program
• CNMPSSI (CNMSJ010) for the NetView subsystem
The CNMSTYLE member in the DSIPARM data set is used during NetView initialization. Review the
CNMSTYLE member and make any changes necessary for your installation.
//* PEND
//*CNMPSSI EXEC PROC=CNMPSSI
Make sure that the PROC name you specify in this statement agrees with the one you specify in CNMPROC
(CNMSJ009). Both of these procedure names must match the NetView subsystem name that you
specified in your SYS1.PARMLIB data set member IEFSSNxx.
TRSIZE=[pages|0]
If 0 is specified, no trace table is allocated, and the NetView internal trace does not start early during
initialization. The CNMSTYLE trace options take effect regardless of whether the NetView internal trace
starts early. Leave early tracing on unless it significantly degrades NetView performance.
// DPRTY=(13,13)
Set the DPRTY parameter to the highest dispatching priority possible below the priority set for VTAM to
get the best performance and to help prevent records from being overlaid.
The default region size provided with the NetView program might not be adequate for all environments. If
you enable additional components in the NetView program, for example the SA tower in the CNMSTYLE
member, or the size of your network is large, consider increasing the region size. For more information on
calculating the region size, refer to the IBM Z NetView Tuning Guide.
The buffer size parameter specifies the amount of storage allocated to the global buffer, the local buffer,
and the router buffer. Each buffer is allocated the amount of storage specified by this parameter. The
acceptable values are 8, 12, 16, 20, and 24 KB.
The slot size parameter refers to a fixed portion of a buffer that is used to contain incoming error records.
As these error records increase in number, you can increase the size of the buffer. Acceptable values are
200, 250, or 300 bytes. If the slot size is too low, the SVC76 mapper truncates error records of greater
length than the slot size. If the slot size is too great, the number of slots available is reduced and records
can be lost unless you also define a larger buffer size.
// DD DSN=&REXX..SEAGLPA,DISP=SHR
• To use the REXX alternate library, ensure that the following statement is uncommented:
// DD DSN=&REXX..SEAGALT,DISP=SHR
For more information about which REXX library to use, refer to the comments in the CNMPROC start
procedure.
//DSICLD DD DSN=&Q1..&DOMAIN..CNMCLST,DISP=SHR
// DD DSN=&SQ1..SAQNCLST,DISP=SHR
If you write additional command lists, add them to the following data set:
NETVIEW.V6R3USER.&domain.CNMCLST
Each command list is a separate member of the command list data set. The name of the command list is
the data set member name.
You can have several data sets for different types of command lists. Add the names of any data sets that
you have defined for your command lists before those of the NetView command lists, for example:
//DSICLD DD DSN=DATASETNAME1,DISP=SHR
// DD DSN=DATASETNAME2,DISP=SHR
// DD DSN=&Q1..&DOMAIN..CNMCLST,DISP=SHR
If you allocate your command list library with secondary space, you might have to recycle the NetView
program to update the library.
//DSIPARM DD DSN=&Q1..&DOMAIN..DSIPARM,DISP=SHR
// DD DSN=&SQ1..SAQNPARM,DISP=SHR
// DD DSN=&SQ1..DSIPARM,DISP=SHR
If you have other definition and sense code libraries, concatenate them after this statement.
//STEPLIB DD DSN=&SQ1..SCNMMJPN,DISP=SHR
// DD DSN=&SQ1..SAQNLINK,DISP=SHR
// DD DSN=&SQ1..CNMLINK,DISP=SHR
• The following statements define the data sets that contain VTAM definitions:
//DSIVTAM DD DSN=&Q1..&DOMAIN..VTAMLST,DISP=SHR
//* DD DSN=SYS1.VTAMLST,DISP=SHR
• The following statements define the data sets that contain your NetView operator profiles:
//DSIPRF DD DSN=&Q1..&DOMAIN..DSIPRF,DISP=SHR
// DD DSN=&SQ1..DSIPRF,DISP=SHR
//CNMPNL1 DD DSN=&Q1..&DOMAIN..CNMPNL1,DISP=SHR
// DD DSN=&SQ1..CNMPNL1,DISP=SHR
• The following statement defines the English online help panels for the hardware monitor:
//BNJPNL1 DD DSN=&SQ1..BNJPNL1,DISP=SHR
For online help panels in the Japanese language, replace the BNJPLN1 statement with the following
statement:
//BNJPNL1 DD DSN=&SQ1..SBNJPNL3,DISP=SHR
//BNJPNL2 DD DSN=&SQ1..BNJPNL2,DISP=SHR
//* DD DSN=&SQ1..SCNMPNL2,DISP=SHR
• The following statement defines the data set used for user-defined message members and translation
members:
//DSIMSG DD DSN=&SQ1..SDSIMSG1,DISP=SHR
//DSIOPEN DD DSN=&Q1..&DOMAIN..SDSIOPEN,DISP=SHR
// DD DSN=&SQ1..SDSIOPEN,DISP=SHR
• The following statement defines the data set used for storing NetView reports, listings, and other
output:
//DSILIST DD DSN=&Q1..&DOMAIN..DSILIST,DISP=SHR
• The following statement defines the data set containing members to be used for testing the automation
table:
//DSIASRC DD DSN=&Q1..&DOMAIN..DSIASRC,DISP=SHR
• The following statement defines the data set used for storing the report produced from running tests of
the automation table:
//DSIARPT DD DSN=&Q1..&DOMAIN..DSIARPT,DISP=SHR
For more information, see IBM Z NetView Installation: Configuring Additional Components.
//* PEND
//*CNMPROC EXEC PROC=CNMAPROC
Make sure the PROC name that you specify in this statement agrees with the one you specify in CNMPSSI
(CNMSJ010). Both of these procedure names must match the NetView subsystem name that you
specified in your SYS1.PARMLIB data set member IEFSSNxx.
The &DOMAIN NetView symbol stores the NetView domain name. The &NV2I NetView symbol is set in
the CNMPROC (CNMSJ009) procedure and has a default value of NM if it is not specified.
If you specify the NetView domain ID and password in the CNMPROC (CNMSJ009) procedure, the
DOMAIN statement in the CNMSTYLE member and the ACBpassword statement in the CNMSTPWD
member are not used. They are ignored unless the parameters that are passed by the CNMPROC
procedure are null. If the domain password is not specified in the CNMPROC (CNMSJ009) procedure or in
the CNMSTYLE member, the domain name becomes the password.
Usage notes:
1. A tower is enabled if it is not preceded by an asterisk. To enable a tower, remove the asterisk (*)
before the tower name.
2. To disable a tower, add a MODIFY.TOWER statement with a minus sign. For example:
MODIFY.TOWER.sortkey = -NLDM
3. If multiple TOWER statements exist, the last TOWER statement encountered is processed. It is
important to remember that modified TOWER statements are not recognized until the NetView
program is restarted.
Note that the "sortkey" values indicate the order of processing and must all be different. A plus sign
indicates an item is being enabled and a minus sign indicates an item is being disabled. For any attempt to
enable or disable a subtower to be effective, the tower must have previously been enabled.
Review the subtower statements that are associated with the towers that are supplied with the NetView
product that you enable. To enable a subtower, create a MODIFY.TOWER statement in the CNMSTUSR or
CxxSTGEN member. To enable or disable any tower or subtower, you must recycle the NetView program,
so review these statements carefully. If you plan on implementing any of the tower and subtower
components, consider enabling the functions during this step in the installation process.
Table 10 on page 50 lists the towers and subtowers that are provided with the NetView program:
Note: In this and other examples, the names PROBMGMT, PROBTASK, and HighPriProbs are used as
examples; you can use any 1-16 character name for a tower statement.
In the example that follows, the name of an autotask is defined for a user-written problem management
application and the name of an additional autotask is defined for a user-written application. The user
written application is used to analyze high priority problems that are handled by the problem
management application:
(PROBMGMT)function.autotask.probMGR = PROBTASK
(PROBMGMT.HighPriProbs)function.autotask.PriMGR = HPRITASK
The PROBTASK autotask is only defined when the PROBMGMT tower is enabled. The HPRITASK autotask is
only defined when the HighPriProbs subtower is enabled in the TOWER.PROBMGMT statement.
Additional information about the function.autotask statement can be found in IBM Z NetView
Administration Reference.
You can add Data REXX logic to the CNMSTUSR or CxxSTGEN member to conditionally process definition
statements based on whether a particular tower is enabled. This is an example:
If you use Data REXX logic, ensure that the %> characters begin in column one. Lines beginning with a
blank are considered continuation statements from the previous line. Also, Data REXX files must begin
with either a /* %DATA */ or /* %LOGIC */ statement.
Defining Variables
Use STYLEVAR to define variables that can be used anywhere within the CNMSTYLE member (except for
the command phase, described in “Command Phase” on page 59). You can use these variables to
simplify the process of entering repetitious data. The STYLEVAR phase is described in “STYLEVAR Phase”
on page 59.
Usage notes:
1. System variable names are not valid names for STYLEVAR variable names.
2. STYLEVAR variable values cannot contain another STYLEVAR variable.
3. If you are using a STYLEVAR variable in the CNMSTYLE member, the construction &&varname is not
supported, where varname is the STYLEVAR variable.
ARCHIVE.HLQ = NETVIEW
If you are not using the default NetView data set naming convention or want to use a different high-level
qualifier for the Canzlog archive data sets, replace the value NETVIEW with the high-level qualifier that
you want to use.
The Canzlog archiving function allocates several different types of sequential data sets:
• Message data sets are allocated to store archived message data from the Canzlog log.
• Index data sets are allocated to reference the message data sets as they are created.
• A primary index data set is allocated to reference the index data sets as they are created.
The allocation parameters for the message data sets are specified by the ARCHIVE.MESSAGE CNMSTYLE
statements. The allocation parameters for the index data sets and the primary index data set are
specified by the ARCHIVE.INDEX CNMSTYLE statements.
Default allocation parameters are provided by the NetView program for allocating non-storage
management subsystem (non-SMS) sequential data sets that are written to a 3390 DASD device.
Depending on your environment, you might want to customize the allocation specifications. See Table 11
on page 54 for a list of statements that contain allocation parameters for the archive Canzlog data sets.
Because most production systems generate large amounts of message data, you might want to use
dedicated DASD storage for managing your Canzlog log archive data sets. Your data management set-up
Setting up Security
You can use the SECOPTS statement to specify levels of security:
• Operator security
• Command authority
• Span of control authority
XCF.RANK=-1
XCF group participation can be enabled after NetView initialization by changing the XCF.RANK value and
issuing the RESTYLE XCF command.
Usage note: If you are running the GDPS Continuous Availability solution, do not disable XCF group
participation. For information on setting the XCF rank for the solution, see IBM Z NetView for Continuous
Availability Configuring and Using the GDPS Continuous Availability Solution.
In this case, the MSG SYSOP command (A) runs before the LISTVAR command (AC).
Note: These AuxInitCmd commands run before any commands at any autotask. All commands for
autotasks, including both task initial command lists and commands sent by EXCMD, are queued and held
up. They run only after all AuxInitCmds have completed. Messages are also queued; they are not
submitted to automation nor logged until all AuxInitCmds have completed.
SSI.ProcString = CNMPSSI.SS,SUB=MSTR,ARM='*ARM'
Specify the procedure name (for example, CNMPSSI). The NetView program provides a value for the
PPIOPT parameter. You can also specify additional start parameters (such as SUB=MSTR) that are
required for your installation.
Note: Do not specify the PPIOPT parameter on the SSI.ProcString statement because the NetView
program adds this parameter during processing. To update this value, use the SSI.PPI statement.
If you specify *NONE* for SSI.ProcString statement, the CNMCSSIR task does not start the SSI procedure.
This is the default.
transTbl = DSIKANJI
To include Japanese translations of messages, copy the following statement from CNMSTYLE to
CNMSTUSR or CxxSTGEN, and remove the asterisk from the beginning of the statement:
transMember = CNMTRMSG
The CNMTRMSG member contains the Japanese message translations. It is located in the
NETVIEW.V6R3M0.SDSIMSG1 data set in the DSIMSG DD concatenation in the NetView procedure
(CNMPROC). Edit the CNMTRMSG member and uncomment the %INCLUDE for CNMMSJPN. To preserve
the SMP/E-installed copy of the CNMTRMSG member, allocate a user SDSIMSG1 data set, copy the
CNMTRMSG member into this user data set, and then edit the CNMTRMSG member in the user data set.
To make sure that user data set changes are in effect, concatenate the user data set ahead of the
NETVIEW.V6R3M0.SDSIMSG1 data set.
The system variables can then be used throughout the NetView program.
Command Phase
During the command phase, the CNMCMD command definitions are evaluated. The values of tower,
domain, type, and other variables set in the early initialization phase control how these members are
read.
Member DSISCHED is read and other initialization members not associated with a CNMSTYLE statement
or optional task are also read.
If you coded a command definition of CNMSTRLY in DISPARM member CNMCMD, the defined REXX
procedure is called. Do not call any long running commands from this procedure, except PIPE. Do not call
the following commands:
• AUTOTASK
• AUTOTBL
• REFRESH
• START
You can use MVS commands. Do not use POI VTAM commands. If a problem occurs with this procedure,
the NetView program might not initialize. Also, if you preset variables designed to be set by CNMSTYLE
processing, the NetView program might not initialize properly.
STYLEVAR Phase
During the STYLEVAR phase, the CNMSTYLE member specifications are reevaluated. All &xxx. stylevar
variables that are used in CNMSTYLE statements are replaced with the value specified in the
corresponding stylevar.xxx entry.
Common Phase
During the common phase, the CNMSTYLE member specifications are re-evaluated. Because of possible
changes in the value of tower, domain, type, and other variables, different statements might be included
by Data REXX or %INCLUDE processing.
Note: Data REXX can be used only in the members that are included in the CNMSTYLE member using the
%INCLUDE statement. Do not use Data REXX in the main CNMSTYLE member (CxxSTYLE).
Because tower statements have already been evaluated, they are used when reading the CNMSTYLE
member for this phase. If a CNMSTYLE statement is preceded by a tower name in parentheses, it is
included during initialization, if the tower is active. Otherwise, the statement is ignored. Do not use
variables or other substitutions within these parentheses.
The CNMSTYLE statements identified by the values in variable earlyCommon (in procedure CNMESTYL)
are processed. For more information about the variable earlyCommon and on which CNMSTYLE
statements are processed, refer to the earlyCommon in procedure CNMESTYL.
Common global variables are set. This includes interpretation of function.autotask.xxx statements.
%INCLUDE C&DOMAIN(2:2).STGEN
Usage notes:
1. Precede the symbolic_name with an ampersand (&).
2. The symbolic_name can optionally include a trailing period (.).
3. Use single quotation marks (‘ ’) if value has leading or trailing blanks.
4. Do not specify a value that contains a symbolic variable, such as
&AAAAA='C&NV2I.01'
&AAAAA='C&DOMAIN(2:2).01'
The following example shows keyword parameters for CNMECRG within CNMSJCRG:
CNMECRG
TASKS=NO
&DOMAIN=CNM01
&NV2I=NM
&CNMTCPN=TCPIP
&CNMRODM=RODMNAME
&CNMNETID=NETA
&MYSYMBL=' A B C '
/*
CNMSTYLE REPORT
&NV21 value: NM
CNMSTYLE
CNMSTPWD
CNMSTASK
CNMSTIDS
CNMSTTWR
CNMSTWBM
CNMSTUSR
MYINCLUD
CNMSTGEN
The format of the CNMSTYLE statements presented in the generated report includes the following fields:
Member
Member name containing the statement
Line#
Line number within the member where the CNMSTYLE statement is located. If a statement is a
continuation statement, only the line number where the statement begins is listed.
Indicators
Lists information about the statement. This information is formatted in the following way:
R CCCCCC
where R represents the Resolve indicator and CCCCCC represents the Condition indicator:
Resolve
Indicates whether the given CNMSTYLE statement was modified by the report generator. A
specification of Y indicates that the statement was modified. For example, a symbolic variable
was substituted or an autotask statement that uses the question mark (?) feature was resolved.
The third section of the report lists the auxInitCmd statements as shown in Figure 6 on page 64. The
auxInitCmd statements are listed in the order they are encountered in the CNMSTYLE member.
The fourth section of the report lists CNMSTYLE statements that are not recognized by the CNMSTYLE
report generator as belonging to a specific NetView function or to the general NetView information in the
first section of the report. A statement might be listed under User-Defined/Unrecognized CNMSTYLE
Statements for the following reasons:
• A statement might be owned by another product such as IBM Z System Automation.
• A statement might require an additional CNMSTYLE statement to become active.
For example, the AUTOTASK.?APSERV.Console CNMSTYLE statement requires the
function.autotask.APSERV statement before it can become active.
• A statement was moved from IBM Z NetView to another product.
For example, the ACTACT.MASTER.DELAY statement was part of the IBM Z NetView product but was
moved to the IBM Z NetView for Continuous Availability product. If the ACTACT.MASTER.DELAY
statement was modified and placed in the CNMSTUSR member and the IBM Z NetView product but was
moved to the IBM Z NetView for Continuous Availability product is not installed, the
ACTACT.MASTER.DELAY statement is not recognized by the Report Generator until the IBM Z NetView
product but was moved to the IBM Z NetView for Continuous Availability product is installed.
• A statement is created by a user.
For example, you define the OPAAA01 autotask as follows:
This section identifies statements in your CNMSTYLE member that were either
created by the user, require additional CNMSTYLE statements to become active,
were moved from Z NetView to another product, or are owned by another
product.
The fifth section of the report lists Data REXX and %INCLUDE statements, as shown in Figure 8 on page
65. During report processing, Data REXX statements are ignored. Data REXX statements are listed in the
report in the order that they are encountered in the CNMSTYLE member. Only the first 63 characters of
each Data REXX statement are placed in the report. CNMSTYLE statements within a %DATA portion of a
Data REXX block that are affected by an IF-THEN statement are also listed to help you understand which
CNMSTYLE statements are impacted by your Data REXX statements.
. . .
. . .
. . .
CNMSTGEN 13 %> IF domain() = 'CNM01' THEN /* Never true! Data Rexx runs...
CNMSTGEN 14 %> /* earlier than resolution of system-sym
CNMSTGEN 15 %> 'STYLEMSG = Illustration only. You will never see this.'
Note: Only the first 63 characters of each Data REXX statement are displayed.
Return codes
The following return codes are set by CNMECRG:
0
Successful completion; a file was created in DSIWRIT
4
Minor errors encountered; a file was created in DSIWRIT
8
Major error encountered; a file was not created in DSIWRIT
For non-zero return codes, error messages can be found in the CNMSJCRG job log.
UPON(CMDVERB='$PJES2')
SELECT
WHEN(W2 = 'ABEND') NETVONLY=rexx_proc
WHEN(W2 = 'TERM') NETVONLY=rexx_proc
OTHERWISE
END
where rexx_proc is the name of the REXX procedure that you created in step “2” on page 66.
4. Activate the command revision table from step “3” on page 66 using the REVISE command.
Procedure
1. Dynamically add the following MVS system symbols:
&CNMTCPN=tcpip_name
&CNMRODM=rodm_name
&CNMNETID=network_id
If you are running z/OS 2.2, use the SETLOAD command to dynamically update your system symbols:
SETLOAD xx,IEASYM,DSN=data_set_name
where xx specifies the LOADxx member in the specified data set (data_set_name). The LOADxx
member specifies the IEASYMyy member where your system symbols are defined.
2. Dynamically add the required NetView modules to the link pack area (LPA):
• BNJLINTB
• BNJMTERM
• BNJSVC76
• (CNMCNETV,CNMNETV)
• CNMCSRVP
• CNMCSSEI
• CNMCSSPI
• DSICSENF
• DSIELSVC
• DSIRVCEX
• DSISPNOT
• DSI4LCUI
• DSI4LSIT
Use the SETPROG LPA ADD command to add each module:
SETPROG LPA,ADD,MODNAME=module,DSNAME=NETVIEW.V6R3M0.SCNMLPA1
where module is the module name or names and NETVIEW.V6R3M0.SCNMLPA1 is the NetView library
where the module was installed. Note that CNMCNETV and its alias, CNMNETV, must be specified
together, separated by commas, and within parentheses, in the SETPROG command.
3. Add the required NetView modules to the list of APF-authorized libraries.
SETPROG APF,FORMAT=DYNAMIC
Issue the following MVS commands to add APF authorizations for the required NetView libraries:
SETPROG APF,ADD,DSNAME=NETVIEW.V6R3M0.CNMLINK,VOLUME=vol-ser
SETPROG APF,ADD,DSNAME=NETVIEW.V6R3M0.SAQNLINK,VOLUME=vol-ser
SETPROG APF,ADD,DSNAME=NETVIEW.V6R3M0.SCNMLNKN,VOLUME=vol-ser
SETPROG APF,ADD,DSNAME=NETVIEW.V6R3M0.SCNMLNK1,VOLUME=vol-ser
SETPROG APF,ADD,DSNAME=NETVIEW.V6R3M0.SCNMLPA1,VOLUME=vol-ser
where vol-ser is the name of the volume where the NetView V6R3 libraries were allocated.
4. Verify that the subsystem (SSI) procedure and the main NetView procedure both include a STEPLIB
DD statement that specifies the data set names for the NetView libraries.
If you plan to start RODM, the RODM Loader, GMFHS, or the Event/Automation Service (E/AS), verify
that these procedures also include STEPLIB DD statements that specify the data set names for the
NetView libraries.
5. Optional: If you plan to run multiple instances of the NetView program within the same LPAR, decide
which is the first instance.
Typically, if only one instance manages system messages, that instance is first; however, you can
choose the instance that you prefer. For more information about running multiple NetView programs in
the same LPAR refer to IBM Z NetView Installation: Configuring Additional Components.
6. Dynamically add the subsystem for the first NetView instance by issuing the SETSSI ADD command:
SETSSI ADD,SUBNAME=ssiname,INITRTN=DSI4LSIT,INITPARM=parms
where ssiname is the subsystem name of the first NetView instance, and parms is the initialization
parameters you want to specify (omit this keyword to use the default initialization parameters). The
subsystem name is the four-character name specified either by the IEFSSNxx member or by the
SETSSI ADD command.
Tip: By convention, the subsystem name for an instance of the NetView program consists of the first
four characters of the job name associated with its main address space and the matching SSI
procedure. The subsystem name you use for an instance of NetView must not be the same as any
other subsystem name in use; multiple NetView address spaces cannot use the same subsystem
name.
Including the INITPARM parameter with any value on the SETSSI command causes all settings that
are specified on previous INITPARM parameters for NetView subsystems to be erased and the active
Canzlog data space to be deleted and reallocated, resulting in loss of all messages from the active
data space. This means that those messages that are issued during the current IPL will only be
available from an archive.
For example, additionally specifying INITPARM='TINYDS,STATIC' on the SETSSI command causes
the Canzlog data space to be deleted and reallocated with a size of 512 MB and not expandable, and
foreign messages are not to be logged in the Canzlog log.
Omitting the INITPARM parameter causes the Canzlog data space with the existing options to be
preserved.
Message CNM617 is displayed when the SETSSI ADD command completes.
Usage note: The SETSSI ACTIVATE command is not supported by the NetView subsystem.
7. Optional: Repeat the SETSSI ADD command for any additional instances of the NetView program in
the LPAR.
Make sure the CNM617 message is displayed for each instance before you proceed to the next.
8. Start the subsystem (SSI) procedure for each NetView instance as documented in “Starting the
NetView Subsystem Address Space Using Job CNMPSSI” on page 71.
Make sure the CNM541 message is displayed for each procedure before you proceed to the next.
S CNMNET,,,(LIST=xx)
Where xx specifies the VTAM start options list (ATCSTRxx) to use when you start the VTAM procedure.
For example, specify LIST=01 when you start the VTAM procedure for NetView domain CNM01 in
subarea 01 in network NETA.
S CNMPSSI
S CNMPROC
Usage notes:
1. Notice the DSI530I messages for the following tasks:
• DSIDCBMT
• DSIHLLMT
• DSILOGMT
• DSIMONIT
• DSISTMMT
• DSITIMMT
These tasks are part of the main task of the NetView program. They are automatically started when the
NetView program is started and are not defined by TASK statements externally. They cannot be
started or stopped by the STARTCNM and STOPCNM commands. They have no user exits, and cannot
be stopped with the STOP TASK command either. Although these tasks can be forced to ABEND with
the STOP FORCE command, after the ABEND, NetView automatically restarts the task. Therefore, do
not try to stop these tasks during NetView initialization.
2. If you did not configure the allocation parameters for the Canzlog archive data sets for your
environment, you might receive the following BNH803I message:
BNH803I VALUE *NONE* FOR KEYWORD ARCHIVE.HLQ CONFLICTS WITH VALUE YES
FOR KEYWORD ARCHIVE.WRITE
To configure the Canzlog archiving function for this NetView program, review the ARCHIVE statements
in the CNMSTYLE member. For information about modifying the ARCHIVE statements, see
“Configuring Allocation Parameters for Canzlog Archive Data Sets” on page 54.
3. VSAM might return IEC161I messages. Do not be concerned with these messages if all the tasks start
properly.
4. Do not respond to the DSI802A message at this time.
This section leads you through a series of commands to test the NetView program that you just started.
Run the commands in exactly the order presented. If you make errors, or issue the commands out of
sequence, the contents of the network logs and the results of the operator tests are different from the
examples you see in this chapter.
To verify the NetView installation, issue instructions that test the installation. If you cannot start the tests,
ensure that you correctly performed all the installation procedures in the NetView program directory and
all the installation procedures in this book.
Usage notes:
1. Your data can differ from the panels in the examples because the display format depends on the type
of terminal that you are using.
2. If you customized your system to suppress messages, remember to check the system and Canzlog
logs for critical information that might be suppressed during the verification of your NetView
installation.
3. For a list of tasks and automated tasks that are initialized by default, see Table 14 on page 95 and
Table 15 on page 97.
LOGON APPLID(CNM01)
NN NN VV VV
NNN NN EEEEEE TTTTTTTT VV VV II EEEEEE WW WW TM
NNNN NN EE TT VV VV II EE WW W WW
NN NN NN EEEE TT VV VV II EEEE WW WWW WW
NN NNNN EE TT VV VV II EE WWWW WWWW
NN NNN EEEEEE TT VVV II EEEEEE WW WW
NN NN V
If the value of the SECOPTS.OPERSEC statement in the CNMSTYLE member is SAFDEF, or if the OPERSEC
operand was specified as SAFDEF on the REFRESH command, no PROFILE field is shown on the Logon
panel and the HARDCOPY LOG field does not have a default value.
In the PROFILE field, system symbolic substitution is performed on records read from the DSIOPF
member in the DSIPARM data set and the specified profile member in the DSIPRF data set. The
&DOMAIN symbolic variable that is supplied with the NetView product is also included in the substitution
Logging on
To log on, enter the following text in both the OPERATOR ID field and in the PASSWORD field:
NETOP1
| CNM01
News for 30 Nov 2019
The information that is displayed on this panel is contained in member CNMNEWS in the
NETVIEW.V6R3M0.SDSIOPEN data set. The date and time at the top of your panel will differ from the
examples.
Usage Note: When verifying your installation, be sure to clear the console between each step. In Figure
10 on page 74, the 3 asterisks at the bottom of a panel indicate a held screen.
HELP NETVIEW
HELP
Select option 4 to display the command facility commands. A panel similar to Figure 14 on page 76 is
displayed.
Figure 14. Using NetView Command and Command List Help Panel
AUTOTBL STATUS
If the default NetView automation table (DSITBL01) was loaded during NetView initialization, a panel
similar to Figure 15 on page 76 is displayed.
-------------------------------------------------------------------------------
???
WHO
Press the ENTER key to release any messages being held by the command facility. The three asterisks
(***) at the bottom of the screen indicate that there are more messages to display.
Enter the CLEAR command to refresh the command facility screen.
DISPFK
The PF key settings are displayed for the component from which you entered the command. A panel
similar to Figure 17 on page 78 is displayed.
BROWSE DSIOPF
NETVIEW.BRWS ------ BROWSE DSIOPF (DSIPARM ) --- LINE 00000 TO 00017 OF 0117
SCROLL ==> CSR
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----
******************************** TOP OF DATA ********************* DATASET: 4
***********************************************************************
* LICENSED MATERIALS - PROPERTY OF IBM *
* 5697-NV6 © Copyright IBM Corp. 1986, 2019 *
* ALL RIGHTS RESERVED. *
* US GOVERNMENT USERS RESTRICTED RIGHTS *
* - USE, DUPLICATION OR DISCLOSURE RESTRICTED BY *
* GSA ADP SCHEDULE CONTRACT WITH IBM CORPORATION. *
***********************************************************************
* NAME(DSIOPF) SAMPLE(DSIOPF) RELATED-TO( ) *
* DESCRIPTION: SAMPLE DSIPARM - OPERATOR DEFINITIONS/PASSWORDS *
* *
*---------------------------------------------------------------------*
* Include customer operator definitions. *
*---------------------------------------------------------------------*
***************** START OF MEMBER DSIOPFU FROM DSIOPF DATASET: 2
***********************************************************************
* 5697-NV6 © Copyright IBM Corp. 1986, 2019 *
CMD==>
TO SEE YOUR KEY SETTINGS, ENTER 'DISPFK'
BFSESS CNM01
OPER4
OPER4
| CNM01
News for 30 Nov 2019
To go to the NetView main menu, press the Enter key and continue to press the Enter key until the
NetView main menu is displayed.
Press the F3 key to go to the command facility.
Enter the CLEAR command to refresh the screen.
To view the operator identifiers and passwords, enter the following command:
BR DSIOPF
???
Usage notes:
1. OPER4 does not have the authority to display the DSIOPF member.
2. Command authorization is being performed by using the NetView command authorization table
(CNMSCAT2). If a SAF product (such as RACF) is being used for security, the information in Figure 20
on page 80 will be different.
To end your OPER4 operator session, enter:
LOGOFF
at the cursor.
You return to a panel similar to Figure 21 on page 80 (the command facility for the NETOP1 operator).
BROWSE CANZLOG
15:57:07 CNM337I VIEW : CODE 12 - YOU ARE NOT AUTHORIZED TO BROWSE 'DSIOPF'. TH
15:57:28 LOGOFF
15:57:28 CNM493I CNMSDCA : #0000023 : CNME8251
15:57:28 DSI081I OPERATOR OPER4, LOGOFF PROCEEDING: TERMINAL = TF01#000
15:57:30 DSI496I FLSCN SESSION BETWEEN APPLID = CNM01 AND SRCLU = TF01#000 E
15:58:38 CLEAR
15:59:00 QRYGLOBL COMMON VARS=CNMSTYLE.NV*
15:59:00 BNH031I NETVIEW GLOBAL VARIABLE INFORMATION
BNH103I COMMAND ISSUED AT: 06/22/19 15:59:00
BNH061I
BNH032I COMMON GLOBAL VARIABLES
BNH036I GLOBAL VARIABLE NAME: GLOBAL VARIABLE VALUE:
BNH061I --------------------- ----------------------
BNH039I CNMSTYLE.NVROLE NETWORK
BNH039I CNMSTYLE.NV2I NM
BNH035I NUMBER OF VARIABLES FOUND: 2
BNH061I
BNH037I NETVIEW GLOBAL VARIABLE INFORMATION COMPLETE
15:59:20 BROWSE CANZLOG
TO SEE YOUR KEY SETTINGS, ENTER 'DISPFK'
CMD==>
Usage notes:
1. You can use the BR LOG command to display messages that match a filter set by the DEFAULTS or
OVERRIDE commands for CANZLOG.
2. You can use the BR filtername command to display messages that match the specified filter name.
You can display a list of defined filters by using the LIST CZFILTER command.
Press the F3 key to return to the command facility. Enter the CLEAR command to refresh the command
facility screen.
PING 1.2.3.4
NETVIP
Type the number or move the cursor to a function and press Enter
Command ===>
F1=Help F3=Return F6=Roll
F12=Cancel
Usage note: To select a function, you can enter the number associated with the function and press Enter,
or move the cursor to the function description and press Enter.
To display a list of the NetView sysplex discovery commands, move the curser to option 7 and press
Enter. A panel similar to Figure 26 on page 83 is displayed.
Type the number or move the cursor to a function and press Enter
Command ===>
F1=Help F3=Return F6=Roll
F12=Cancel
You can view configuration and status information about the NetView domains known to this NetView
program. To do this, move the cursor to option 3 and press enter. A panel similar to Figure 27 on page
83 is displayed.
Usage note: Not all IP management functions are enabled by default. To fully enable IP management,
see IBM Z NetView Installation: Configuring Additional Components.
Press the F3 key until you return to the command facility panel.
Enter the CLEAR command to refresh the command facility screen.
???
NPDA
SEL# PRODUCES:
( 1) ALERTS-DYNAMIC DISPLAY
( 2) TOTAL EVENTS DISPLAY
( 3) TOTAL STATISTICAL DATA DISPLAY
( 4) HELP MENU DISPLAY
ENTER SEL#
???
CMD==>
Note: If the sample job CNMSJ005 is used to initialize a newly allocated hardware monitor (NPDA)
database cluster, the database initialization dates shown on the hardware monitor main menu NPDA-01A
will be 05/30/96.
Examine the dates in the AL, EV, and ST fields. The dates cannot be asterisks. Your dates might not match
the dates in Figure 29 on page 84.
Use the ALERTSH (ALH) command to display the alerts recorded in the hardware monitor database. To
see a panel similar to Figure 30 on page 84, enter:
ALH
ENTER SEL# (ACTION),OR SEL# PLUS M (MOST RECENT), P (PROBLEM), DEL (DELETE)
???
CMD==>
NLDM
NLDM.MENU PAGE 1
NETVIEW
DOMAIN CNM01
SEL# DESCRIPTION
Note: If the sample job CNMSJ005 is used to initialize a newly allocated session monitor (NLDM)
database cluster, the database initialization date shown on the session monitor main menu NLDM.MENU
will be 07/17/87.
To display a list of all inactive NetView sessions enter:
SESS * * INACT
NLDM.SESS PAGE 1
SESSION LIST
NAME: * DOMAIN: CNM01
------------------------------------------------------------------------------
***** PRIMARY ***** **** SECONDARY ****
SEL# NAME TYPE DOM NAME TYPE DOM START TIME END TIME
( 1) CNM0100F LU CNM01 TF01#000 LU CNM01 08/22 15:56:13 08/22 15:57:29
( 2) NT68MVS SSCP CNM01 CNM0100F LU CNM01 08/22 15:56:13 08/22 15:57:29
( 3) CNM01 LU CNM01 TF01#000 LU CNM01 08/22 15:56:13 08/22 15:56:13
( 4) NT68MVS SSCP CNM01 TF01#000 LU CNM01 08/22 15:56:13 08/22 15:57:29
( 5) CNM01 LU CNM01 NT68L703 LU CNM01 08/22 15:52:07 08/22 15:52:07
END OF DATA
ENTER SEL# (CONFIG), SEL# AND CT (CONN. TEST), SEL# AND STR (TERM REASON
CMD==>
Logging Off
To log off from the NetView program, enter:
logoff
Installation, configuration, and setup for NetView IBM Z NetView Installation: Configuring Additional
REST Server Components
Installing the NetView program on the same LPAR Running Multiple NetView Programs in the Same
as an existing NetView program LPAR in IBM Z NetView Installation: Configuring
Additional Components
Using the NetView program for IP management IBM Z NetView Installation: Configuring Additional
Components
IBM Z NetView IP Management
Using the NetView program for sysplex IBM Z NetView IP Management
management
Implementing graphics support IBM Z NetView Installation: Configuring Graphical
Components
Extending automation IBM Z NetView Automation Guide
Make sure that your automation tables are updated
and correctly specified using AUTOCMD
statements in the CNMSTYLE member. The
DSITBL01 automation table is required for the
NetView program and provides basic automation
statements to respond to messages and
management services units (MSUs).
Use %INCLUDE members to define changes for
your environment and add these changes before
any automation statements that are provided with
the NetView program. Code any local
customization with CONTINUE(YES).
NetView Functions
The following table contains some of the NetView functions with information on how they benefit you and
where more information can be found.
Automated Provides automation for TCP/IP, VTAM, and IBM Z NetView User's Guide: Automated
operation for SNA using NetView AON automation policy Operations Network
networks (AON)
Browse facility 1 View logs, data sets, and files on either a IBM Z NetView User's Guide: NetView
local or remote NetView
Canzlog log Provides consolidated access to all IBM Z • IBM Z NetView Installation: Configuring
NetView system messages (including the Additional Components
netlog and syslog). The Canzlog log
• IBM Z NetView User's Guide: NetView
includes expanded access to message
attributes and robust filtering to retrieve
specific log records. By using the Canzlog
function, you can significantly reduce
problem determination time. You can
archive the Canzlog log for later recall, as
needed for audit or further problem
analysis.
CNMSTYLE Converts previous releases of CNME1034 IBM Z NetView Installation: Migration Guide
migration tool command list and DSIPARM initialization
members to the CNMSTYLE member
format. This tool also converts your
DSICMD definitions to the CNMCMD
member format.
CNMSTYLE report Creates a report that provides information “Using the Report Generator” on page 60
generator on the CNMSTYLE member. The report
includes the following information:
• Listing of the %INCLUDE structure of the
CNMSTYLE member
• Grouping of statements by NetView
function
• Grouping of multiple occurrences of
statements for quick analysis
• Listing of enabled towers
Command facility 1 Provides basic command support for the IBM Z NetView User's Guide: NetView
NetView product; lets you issue VTAM,
MVS, and NetView commands from the
NetView command line.
Command Statistics Provides usage statistics for each IBM Z NetView Installation: Configuring
invocation of a command that runs in the Additional Components
NetView address space.
Discovery manager Collects sysplex, z/OS image, TCP/IP stack, IBM Z NetView Installation: Configuring
IP interface, OSA, HiperSockets, NetView Additional Components
program, and Telnet server data for display
in the NetView management console and
the NetView agent. Provides real-time
3270 TCP/IP stack, IP interface, Telnet
server, OSA, HiperSockets, and NetView
application commands.
Help facility 1 Provides online help for messages and IBM Z NetView User's Guide: NetView
commands
Help desk facility 1 Provides online help for diagnosing IBM Z NetView User's Guide: NetView
problems
Intrusion detection Defines automated responses to the IBM Z NetView Installation: Configuring
services following items: Additional Components
• Scans
• Attacks
• Traffic regulation for TCP connections
and UDP receive queues
Using notification and inform policies, you
can send an e-mail to a security
administrator, issue a message, generate
an alert or Event Integration Facility (EIF)
event, issue commands, or generate a
report in response to an intrusion.
NetView automation Perform repetitive or routine tasks without IBM Z NetView Automation Guide
operator action
NetView Displays topology and status information IBM Z NetView Installation: Configuring
management about network and system resources in a Graphical Components
console graphical format, from any platform
enabled by Java™
NetView MVS The NetView MVS command revision table IBM Z NetView Automation Guide
command revision (CRT) enables you to intercept MVS
table commands before they are processed.
Command sources include the MVS
console and the NetView MVS command.
NetView Resource Used to graphically monitor and manage IBM Z NetView Installation: Configuring
Manager NetView task resource utilization and Graphical Components
status using the NetView management
console. You can monitor all NetView
programs in your enterprise using one
NetView management console.
REST Server Externalize NetView functions through • IBM Z NetView Application Programmer's
Restful APIs. Provides users the Guide
capabilities to access NetView from
• IBM Z NetView Installation: Configuring
anywhere that can make REST request.
Additional Components
This helps facilitates the creation of web
applications. • IBM Z NetView User's Guide: NetView
• IBM Z NetView Security Reference
Save and restore Saves timers, global variables, and focal IBM Z NetView Installation: Configuring
function point information to VSAM and then Additional Components
restores this data when the NetView
program is restarted
Session monitor Collects and stores data about SNA IBM Z NetView Installation: Configuring
resources in subarea, Advanced Peer-to- Additional Components
Peer Networking, and mixed networks.
SNA topology Obtains the status and topology IBM Z NetView SNA Topology Manager
manager information for SNA subarea and SNA Implementation Guide
Advanced Peer-to-Peer Networking
resources dynamically, for graphical
display using the NetView management
console
Status monitor Collects status information about SNA IBM Z NetView Installation: Configuring
resources in the network Additional Components
XCF services In sysplex management, z/OS XCF services IBM Z NetView Installation: Configuring
are used to help initiate resource discovery Additional Components
and facilitate forwarding of management
data in the sysplex, and to implement a
master NetView program. The master
NetView program has the complete view of
the sysplex.
zERT data collection Collects TCP/IP connection security data to IBM Z NetView Installation: Configuring
be displayed in NetView workspaces in the Additional Components
Tivoli Enterprise Portal, or on the 3270
console.
Notes:
1. For AON autotasks associated with the AON tower, see the EZLOPF member that is included in the DSIOPF
member.
2. For AON autotasks associated with the AON.SNA subtower, see the FKVOPF member that is included in the
DSIOPF member.
3. For AON autotasks associated with the AON.TCP subtower, see the FKXOPF member that is included in the
DSIOPF member.
4. For autotasks associated with the IPMGT tower, see the FKXOPFIP member that is included in the DSIOPF
member.
5. For MSM autotasks associated with the MSM tower, see the FLCSOPF member that is included in the
DSIOPF member.
Changing an operator ID
If you change an operator ID, you might also have to change the corresponding operator ID in other
DSIPARM members. For example, the following DSIPARM members might require modifications:
NetView style sheet
CNMSTYLE and its included members
NetView automation table
DSITBL01 and its included members
NetView command authorization table
CNMSCAT2 or CNMSCATU member, if the following statement is specified:
SECOPTS.CMDAUTH=TABLE
Security product definitions for operators
CNMSAF2 member (CONNECT statements), if the following statement is specified:
SECOPTS.CMDAUTH=SAF.option
Important: Do not change the following automated task IDs that are defined in DSIOPF and CNMSAF2 or
their included members:
AUTOAMI
All of the sample definitions listed in this book (and some not listed) are contained on the NetView
distribution media. These definitions are distributed as members of the following data sets:
• NETVIEW.V6R3M0.CNMSAMP
• NETVIEW.V6R3M0.DSIPARM
• NETVIEW.V6R3M0.DSIPRF
• NETVIEW.V6R3M0.SAQNPARM
• NETVIEW.V6R3M0.SAQNSAMP
• NETVIEW.V6R3M0.SDSIMSG1
• NETVIEW.V6R3M0.SDSIOPEN
Each samples name begins with AAU, BNJ, CNMB, CNMCM, CNMS, DSI, DUIF, EKG, EZL, FKV, FKX, or FLC,
and can have a maximum length of 8 characters. The last four or five characters of all samples vary. Table
17 on page 101 summarizes the samples distributed with the NetView program.
Appendix C, “NetView Samples Reference,” on page 119 lists all the samples on the distribution media
and a brief description of each sample. Use CNMSJ003 to copy sample members into the correct libraries
where they can be used by the NetView and VTAM programs. Sometimes, you must rename the samples
to meet NetView or VTAM program requirements. For example, VTAM start options are distributed on the
samples media in CNMS0010. However, the VTAM program requires that you name this member
ATCSTR00. CNMSJ003 copies CNMS0010 into the VTAM library as ATCSTR00.
The sample network uses a standard naming convention for the NCP and VTAM definitions.
Table 18. Summary of Sample VTAM Major Nodes at A01MPU in Network NETA
Name Distributed As Description
ATCCON01 CNMS0003 Defines configuration start list
ATCSTR00 ATCSTR01 CNMS0010 CNMS0007 Defines VTAM start options
A01ADJ CNMS0012 Defines adjacent SSCPs for VTAM to query
Table 19 on page 103 lists the names of the VTAM major nodes in the sample network (NETB). The actual
samples are not shown in this book, however, their NETA equivalents are listed in the table for easy
reference.
Table 19. Summary of Sample VTAM Major Nodes at B01MPU in Network NETB
Name Distributed As Description NETA Equivalent
ATCCONB1 CNMS0102 Defines configuration start list ATCCON01
ATCSTRB1 CNMS0101 Defines VTAM start options ATCSTR01
B01ADJ CNMS0104 Defines adjacent SSCPs for VTAM to A01ADJ
query
B01APPLS CNMS0113 Defines the NetView program A01APPLS
application major node
B01CDRM CNMS0106 Defines cross-domain resource A01CDRM
managers in NETA
B01CDRSC CNMS0107 Defines cross-domain resource A01CDRSC
managers in NETB
B01LOCAL CNMS0108 Defines local non-SNA terminals A01LOCAL
B01MVS CNMS0111 Defines MVS applications A01MVS
B01PATH CNMS0105 Defines path table for host B01MPU A01PATH
B30NTRI CNMS0110 Defines dial deck coded for NTRI lines A04NTRI
VTAM Definitions
You can modify the sample network definitions to fit your network. This process includes modifying VTAM
definition statements and VTAM tables.
v net,act,id=a01local
Conversely, the operator can deactivate these terminals by entering the following VARY INACT command:
v net,inact,id=a01local
Configuration Lists
The major nodes you have defined are not processed by the VTAM program until you activate them. Use
one of the following two ways to activate these nodes:
1. Have the VTAM operator enter a VARY ACT command for each major node.
2. Include the major node names in a configuration list. When you start the VTAM program, it
automatically activates every node that you have listed if CONFIG=xx is coded in your start list, where
xx is the last two characters of your configuration list name (ATCCONxx).
s cnmnet.net,,,(list=01)
If the same option is coded in both ATCSTR00 and ATCSTR01, the option coded in ATCSTR01 takes
precedence.
The VTAM start options for B01MPU in NETB are coded in ATCSTRB1. To start the VTAM program in host
B01MPU, enter:
s cnmnet.net,,,(list=B1)
ATCSTR00, the default start option file, is on the distribution media. If you want to use these definitions in
your network:
1. Check the PPOLOG start option. This option is used to specify whether messages are sent to the
network log. The sample network uses the default value of PPOLOG=NO. If you are running a release
of the VTAM program before V3R3, change this value to PPOLOG=YES to keep the status monitor
panels in the NetView program accurate.
2. Review the default values for each start option. Default values are coded for all start options except
TRACE and IOBUF.
3. Check the TRACE start option. This option indicates which functions are traced when the VTAM
program is started. OPT=ALL was coded here, meaning all functions are traced when the VTAM
program is started. To conserve storage, delete the OPT=ALL operand or specify a specific function
that you want to trace.
4. Check the IOBUF start option. This option is the message pool in fixed storage and is used for input/
output data. For the sample network, this option is set to 256 bytes. This represents the value of the
UNITSZ operand on the NETA definition statements in A04A54C (CNMS0065) and A31A54C
(CNMS0066). The value of the UNITSZ operand on the NETB definition statement in B30A54C
(CNMS0109) is set to 384 bytes.
Application Programs
Each VTAM application program must be defined with an APPL definition statement. The statement is
coded in an application major node defined with a VBUILD statement (TYPE=APPL).
In the sample network, the following major nodes are available for host A01MPU:
A01APPLS
Defines application programs common to all operating systems. APPL statements for the NetView
program are in this major node.
A01MVS
Defines MVS-based application programs, such as TSO and NetView Performance Monitor (NPM).
A01NVAS
Defines NetView access services application major node.
A01USER
Defines additional application programs, such as IMS and CICS
A detailed description of each application major node follows.
A01MVS is an APPL major node coded for host A01MPU. The APPL major node coded for NETB is B01MVS
(CNMS0111). If you want to use these definitions in your network, complete the following steps:
1. If you plan to have more than 10 concurrent TSO users, add additional TSOA01nn APPL statements.
2. This major node contains APPL definitions for NPM. The sample network does not contain NPM. This
definition is included only as an example. If you do not plan to run NPM in your network, you can
remove the NPM APPL definition.
3. Add APPL statements for any other VTAM applications you plan to run.
Cross-Domain Resources
The logical units (LUs) in other domains that the VTAM program accesses are called cross-domain
resources (CDRSCs). Some cross-domain resources are applications that reside in other hosts, such as
CICS and TSO. A terminal in another domain can also be a CDRSC.
CDRSC definitions are not required. CDRSCs can dynamically define the owner of a CDRSC by polling
other hosts in the network.
You can define CDRSCs in one or more CDRSC major nodes. The major node consists of a VBUILD
statement (TYPE=CDRSC), followed by a CDRSC statement for each cross-domain resource.
The following sections define the cross-domain resources for A01MPU. The NETB equivalent cross-
domain resource major node is B01CDRSC (CNMS0107).
In this example, only the NetView programs at subareas 2 (CNM02) and 99 (CNM99) are defined as
CDRSCs. In this example, the owning CDRM for the NetView program is not defined. The VTAM program
uses an adjacent SSCP table to locate the owning CDRM. See “Adjacent SSCP Table” on page 110 for
additional information.
cnm99
When the VTAM program searches its list of cross-domain resources, it tries to locate an entry for CNM99.
Because there is no indication where this resource resides, the VTAM program checks an adjacent SSCP
table to see if adjacent SSCPs are defined. The VTAM program then uses the table to try to locate CNM99.
The first SSCP in the list is A02M. The VTAM program sends a session initiation request (CDINIT) to A02M,
seeking to establish a session with CNM99. A01M has already established an SSCP-to-SSCP session with
A02M. Therefore, the VTAM program knows which route to use.
A02M reacts to the initiation request by searching its resources for CNM99. A02M does not find CNM99
and returns a negative response. After receiving the negative response, the VTAM program tries the next
SSCP in the list, which is A99M. Here, A99M owns CNM99 and accepts the initiation request.
Channel-to-Channel Attachment
As the illustration of the network in Figure 35 on page 112 shows, A01MPU has a channel-to-channel
attachment to A02MPU. This attachment must be defined to the VTAM program in a channel attachment
major node. The channel attachment major node consists of a VBUILD statement (TYPE=CA) followed by
GROUP, LINE, and PU statements.
The major nodes named CTCA0102 (CNMS0038) and CTCA0201 (CNMS0039) define the channel
attachment between A01MPU and A02MPU. If you want to use these definitions in your network,
complete the following steps:
1. Check the DELAY and REPLYTO operands. Default values are coded for each. The value specified in the
DELAY operand is the time in seconds that the VTAM program in A01MPU must wait before sending
Channel-to-NCP Attachment
As the illustration of the sample network shows (see Figure 35 on page 112), A01MPU has a channel-to-
NCP attachment to A04A54C as coded in CTNA0104 (CNMS0081). To use these definitions in your
network, change the ADDRESS operand on the LINE statement to match the correct value for your
network.
The NCP channel attachment between A02MPU and A04A54C in NETA is coded in CTNA0204
(CNMS0082) and the NCP channel attachment between A99MPU and A31A54C in NETA is coded in
CTNA9931 (CNMS0083). The channel-to-NCP definition coded for B01MPU in NETB is CTNB0130
(CNMS0115)
Paths
When you know the physical structure of your network, remember to define the paths between the
different nodes with PATH definition statements.
Figure 36 on page 113 illustrates the meaning of the PATH statement.
Code a PATH statement for each subarea (host or NCP) with which the VTAM program needs to
communicate. Code a PATH statement for every subarea except your own.
The statement first defines the destination subarea. You can use the same statement for more than one
subarea. Next, the statement must define the explicit routes and virtual routes (ERs and VRs) that make
up that path.
An ER defines the physical elements that connect two subareas. A VR is the logical connection between
two subareas. A VR uses the physical route defined by an ER. Associate each ER with a VR. ERs have the
additional characteristic of a transmission priority.
The VTAM program needs both ERs and VRs to set up a session. The VTAM program begins with a VR and
then uses the PATH table to determine which ER to which the VR maps. A class-of-service table tells the
VTAM program which VR to use. In Figure 36 on page 113, if the class of service says that VR1 is to be
used, then the VTAM program uses the PATH statement and map that statement into ER0.
Routes
Figure 38 on page 115 shows how the logon mode and the class-of-service (COS) table, along with the
VTAM definitions, are used to select the route for a session.
In this example, a user of a terminal at address 701 in the domain of A01MPU wants to establish a cross-
domain session with the NetView program at A02MPU.
The user at A01MPU requests the session by entering the following command:
cnm02
logon applid(cnm02)
CNM02 is a USS command defined in the USS table of A01MPU (AUSSTAB (CNMS0011)). The formatted
logon specifies an application name of CNM02, which is the name given to the NetView program at
subarea 2. CNM02 is also defined to the VTAM program at A02MPU as an APPL and to the VTAM program
at A01MPU as a CDRSC.
The VTAM program at A01MPU carries out these steps when selecting the route:
1. A01MPU uses the USS table (not shown in Figure 38 on page 115) to format the logon.
VTAM Tables
Besides VTAM major nodes, you need to code the CNM routing table. You have the option of also coding
the following tables:
• Unformatted system services (USS)
• Logon mode
• Class of service (COS)
The VTAM and NetView programs provide default values or samples for each table. You can use the tables
as they exist or customize them to fit the requirements of your network.
If you plan to modify one or more of these tables, copy the IBM sample and change it to meet your
requirements. Then assemble and link edit the table.
The following sections provide an overview of each table and include a description of how to assemble
and link edit a VTAM table.
USS Table
You can use the USS table to define user (and operator) commands and messages. As an MVS user at
subarea 01, remember to remove the VM and the VM01 commands. If hosts A02MPU and A99MPU are
MVS hosts, remove the VM02 and VM99 commands. AUSSTAB (CNMS0011) is the USS table that is used
for the sample network.
A default USS table is also shipped with the VTAM program.
Class-of-Service Table
Use a class-of-service (COS) table to define the routes that the VTAM program uses in establishing cross-
domain sessions. High-priority sessions might be assigned a class of service that uses high-speed routes.
Conversely, low-priority sessions might be assigned a class of service that uses slower routes.
You define a class of service by creating an entry for it in a class-of-service table. You then specify the
name of the entry in the logon mode table entry to create the routes used for the session.
The VTAM program does not require a class-of-service table. However, if you do not code one, the only
classes of service you can use are the unnamed class of service and ISTVTCOS, which is the name the
VTAM program uses to set up its own sessions.
For the sample network, the COS table has five classes of service:
• Unnamed class of service
• ISTVTCOS
• NETOPER
• INTERACT
• BATCH
All the classes of service have the same selection order but different transmission priorities. ISTVTCOS is
always the class of service with the highest transmission priority. The following list shows the selection
order for the unnamed class of service:
1. Virtual Route 0, Transmission Priority 0
2. Virtual Route 1, Transmission Priority 0
3. Virtual Route 2, Transmission Priority 0
4. Virtual Route 3, Transmission Priority 0
5. Virtual Route 4, Transmission Priority 0
6. Virtual Route 5, Transmission Priority 0
7. Virtual Route 6, Transmission Priority 0
8. Virtual Route 7, Transmission Priority 0
Table 20 on page 119 lists the samples that can be found in the following libraries:
• NETVIEW.V6R3M0.CNMSAMP
• NETVIEW.V6R3M0.DSIPARM
• NETVIEW.V6R3M0.DSIPRF
• NETVIEW.V6R3M0.SDSIMSG1
• NETVIEW.V6R3M0.SDSIOPEN
The table includes a brief description of each sample and the data set name where each member resides
when installation is complete.
Usage notes:
1. Samples that reside in VTAMLST and PROCLIB data sets are initially distributed in
NETVIEW.V6R3M0.CNMSAMP.
2. The National Language Support feature contains CNMMSJPN, the NetView sample for the Kanji feature
program definition file for the sample network.
3. Although the samples were tested and are supported by the NetView program, you are responsible for
making the proper modifications to the samples for your operating system.
4. For information about RODM, GMFHS, SNA Topology Manager, and MultiSystem Manager samples,
refer to IBM Z NetView Installation: Configuring Graphical Components.
DSIPROFF same Defines automated operator profile for the NetView DSIPRF
Bridge REMOTEBR command
This is a sample profile for an automated operator
(that is, an operator started with the AUTOTASK
command to run as an unattended operator). This
profile is used by the REMOPER automated
operator.
This appendix lists some of the ddnames in the NetView start procedure CNMPROC and some of the data
set members that the NetView program uses. The NetView program looks in the data sets specified on
the DD statement for the given ddname for the members listed in Table 21 on page 143.
If you start the NetView program before VTAM or TCP/IP network services, you receive error messages
from enabled towers and other functions that rely on these network services. Note that these error
messages might mask other error messages that are unrelated to the unavailability of the network
services.
This appendix provides information for configuring the NetView program to minimize errors related to
VTAM and TCP/IP network services during initialization. This information is followed by instructions for
starting NetView components and related functions when the VTAM network services or the TCP/IP
network services are available, so that the enabled towers and related functions are fully operational in
your configuration.
The instructions for starting NetView program features are divided into two sets. The first set focuses on
features of the NetView program that depend on other features, providing a list that begins with more
atomic or independent features and progresses through other features that depend on them. Steps in the
instructions about features that are not used can be skipped.
The second set shows how to start other NetView program features that depend on VTAM or TCP/IP
network services. These features are not used by other features of the NetView program, so this list of
instructions does not need to be followed sequentially. Again, steps in the instructions related to features
that are not used can be skipped.
If you have other products or have created your own features that depend on NetView program features
and VTAM or TCP/IP network services, you might consider adding instructions for those features to the
instructions provided in this section so that error message traffic is minimized and, when VTAM or TCP/IP
network services become available, these products and features can be made fully operational.
The information for configuring the NetView program and, on availability of VTAM or TCP/IP network
services, starting features that rely on those network services is organized according to the following
tasks.
• Enable towers that you want to use, but prevent initialization of their related functions until the required
network services are available.
It is necessary to enable towers, in particular, before starting the NetView program, because towers
cannot be dynamically enabled after the NetView program is started. For a number of features, tower
selections determine definitions that are read during NetView program initialization.
• For each enabled tower or related function, configure the NetView program so that the related function
of the enabled tower can be started when VTAM or TCP/IP network services are available.
Depending on how you detect and react to the availability of VTAM or TCP/IP network services,
additional NetView program configuration might be required:
– NetView command security to accommodate any changes in tasks that execute commands that start
NetView program features
Many commands that the NetView program normally runs to start towers and related functions have
one of the following characteristics:
- Run on the primary program operator interface task (PPT)
- Scheduled by PPT to run on an autotask that is associated with the tower or related function, in
addition to or instead of an initial command defined in a profile for such an autotask
- Run as an initial command on an autotask that is associated with the tower or related function, for
example, the value of the IC keyword on a PROFILE statement in an operator profile used by the
autotask
TASK.CNMCALRT.INIT=N
TASK.CNMTAMEL.INIT=N
TASK.DSIHPDST.INIT=N
TASK.DSITCONT.INIT=N
TASK.DSIUDST.INIT=N
TASK.DSIXCFMT.INIT=N
TASK.DSI6DST.INIT=N
TASK.DUIDGHB.INIT=N
%>IF TOWER('GRAPHICS') THEN
TASK.DUIFSSCO.INIT=N
%>IF TOWER('AON') THEN DO;
TASK.EZLTSTS.INIT=N
TASK.EZLTLOG.INIT=N
* EZLTDDF is already INIT=N, since AON will eventually start the task itself
%> END
Precede these statements in your CxxSTGEN with this statement to enable data REXX.
An example is provided in the CNMSTGEN sample that is included with the NetView program. DSTs and
OPTs that require VTAM or TCP/IP network services and that are not shown above are already defined
with INIT=N in the CNMSTYLE member and its included members.
Although the DSIACBMT task is defined with INIT=Y and attempts to open the NetView main ACB (the
application LU that matches the domain name), no message is issued, so you do not need to change the
definition.
Add these statements to your CxxSTGEN member of the DSIPARM data set. These statements either
prevent autotasks that are associated with towers and other NetView program features from being
started by specifying LOGOFF for the initial command, or ensure that the NetView program starts the
autotask and runs a command that does essentially nothing by specifying NODATA for the initial
command. For each statement that specifies a tower or subtower in parentheses, you can omit that
statement if you do not enable the tower or subtower.
AUTOTASK.?AUTOIP.INITCMD = NODATA
AUTOTASK.?Policy.INITCMD = NODATA
*
(AMI)AUTOTASK.?AMI.INITCMD = LOGOFF
*
(AON)AUTOTASK.?AON.INITCMD = NODATA
(AON.TCP.IDS)AUTOTASK.?IDS.INITCMD = LOGOFF
(AON.TCP.IDS)AUTOTASK.?IDS2.INITCMD = LOGOFF
*
(DISCOVERY)AUTOTASK.?COLTSK7.INITCMD = LOGOFF
(DISCOVERY.INTERFACES)AUTOTASK.?COLTSK5.INITCMD = LOGOFF
(DISCOVERY.TELNET)AUTOTASK.?COLTSK6.INITCMD = LOGOFF
*
(DVIPA)AUTOTASK.?DVIPSTAT.INITCMD = LOGOFF
(DVIPA)AUTOTASK.?DVIPAUTM.INITCMD = LOGOFF
(DVIPA)AUTOTASK.?COLTSK1.INITCMD = LOGOFF
(DVIPA.DVTAD)AUTOTASK.?COLTSK2.INITCMD = LOGOFF
(DVIPA.DVCONN)AUTOTASK.?COLTSK3.INITCMD = LOGOFF
(DVIPA.DVROUT)AUTOTASK.?COLTSK4.INITCMD = LOGOFF
*
(GRAPHICS)AUTOTASK.?NMCPOLICY.INITCMD = LOGOFF
(GRAPHICS)AUTOTASK.?EVENTMGR.INITCMD = LOGOFF
(GRAPHICS)AUTOTASK.?COSGATEWAY.INITCMD = LOGOFF
*
(IPMGT)AUTOTASK.?IPMGT.INITCMD = LOGOFF
(IPMGT.IDS)AUTOTASK.?IDS.INITCMD = LOGOFF
(IPMGT.IDS)AUTOTASK.?IDS2.INITCMD = LOGOFF
*
(MSM)AUTOTASK.?MSMALERTS.INITCMD = LOGOFF
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 147
(MSM)AUTOTASK.?VBVWORKER.INITCMD = LOGOFF
(MSM.OPN)AUTOTASK.?MSMOPENALERTS.INITCMD = LOGOFF
*
(NVSOA)AUTOTASK.?NVSOAPTSK.INITCMD = LOGOFF
*
(TEMA)AUTOTASK.?NALCLOP.INITCMD = LOGOFF
(TEMA)AUTOTASK.?EMAAUTOM.INITCMD = LOGOFF
(TEMA.HEALTH)AUTOTASK.?NAPOLTSK1.INITCMD = LOGOFF
(TEMA.CONNACT)AUTOTASK.?NAPOLTSK2.INITCMD = LOGOFF
(TEMA.CONINACT)AUTOTASK.?NAPOLTSK3.INITCMD = LOGOFF
(TEMA.SESSACT)AUTOTASK.?NAPOLTSK4.INITCMD = LOGOFF
*
If an autotask that is part of a tower or NetView program feature requiring VTAM or TCP/IP network
services was not included, it is because the sample profile for the autotask either has no initial command
or has an initial command that does not require the network services.
Add this statement to your CxxSTGEN member to ensure that Z NetView Enterprise Management Agent is
not started.
(TEMA)INIT.EMAAUTO = NO
Other NetView program features have their INIT statements assigned the value No in the CNMSTYLE
member.
(TCPIPCOLLECT.TCPCONN)INIT.TCPCONN = No
(TCPIPCOLLECT.PKTS)INIT.PKTS = No
(TCPIPCOLLECT.PKTS)INIT.OPKT = No
INIT.NRM = No
(DVIPA)Init.DVIPASTATS = No
The CNMSTYLE member and its included members contain examples of auxiliary commands, some of
which start functions for enabled towers. To prevent these functions from being started, override the
sample auxInitCmd statements by adding these statements to your CxxSTGEN member:
(NLDM)auxInitCmd.SNLDM = NODATA
(NPDA)auxInitCmd.SNPDA = NODATA
auxInitCmd.POLICY = NODATA
(DISCOVERY)auxInitCmd.ZDISC = NODATA
For each statement that specifies a tower in parentheses, you can omit that statement if you did not
enable the tower.
If you have enabled the GRAPHICS tower, NetView program initialization schedules a STARTCNM
GRAPHICS command to start tasks needed by that feature. The STARTCNM command, a synonym for
CNME1015, whose source code is provided with the NetView program, does not check the availability of
network services to ensure that they are available before starting the tasks associated with the
GRAPHICS tower, so errors might result when the network services are unavailable.
One way to prevent the errors would be to replace the code in the DO group that follows this statement:
For example, if you set a TCPIP_UP common global variable to Y when you determine that the TCP/IP
program of the z/OS Communications Server completed initialization, you can choose to let the
STARTCNM GRAPHICS command start its tasks only when both TCP/IP and VTAM are available. Do this
by replacing the code in the DO group with coding similar to this example:
slist3.0 = 0
TCPIP_UP = ''
'GLOBALV GETC TCPIP_UP'
if ((TCPIP_UP = 'Y') &,
(VTAM() <> '')) then /* TCP/IP and VTAM are up */
do
slist3.1 = 'START CNMTAMEL' /* Might need VTAM, TCP/IP, or both*/
slist3.2 = 'START DUIDGHB' /* Needs TCP/IP */
slist3.3 = 'START DUIFSSCO' /* Needs neither VTAM nor TCP/IP directly */
slist3.4 = 'AUTOTASK DUIFCSGW' /* Might need VTAM */
slist3.0 = 4
if (TOWER('GRAPHICS.SNATM')) then /* SNA Topology Manager subtower enabled */
If you have enabled the AMI tower, NetView program initialization will insert automation definitions from
the DSIAMIAT member of the DSIPARM data set, as well as its included members, after automation table
definitions in the DSITBL01 member and its included members are loaded. Because some of the
automation associated with the AMI tower attempts to schedule commands on the autotask defined for
the AMI function and because an earlier AUTOTASK definition ensured that autotask was not started, an
error message like this message might be displayed:
One way to prevent the error message is to remove or comment out the following statements in the
CNMSTASK member of the DSIPARM data set.
AUTOCMD.DSIAMIAT.list = *NONE*
AUTOCMD.DSIAMIAT.marker = AMI
AUTOCMD.DSIAMIAT.order = B
If the AMI tower is not enabled, it is not necessary to alter the AUTOCMD statements as they are not
processed during NetView program initialization.
Several of the operators use the same sample profile, so an initial command can check the operator on
which it is running and then choose the applicable command from the table.
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 149
If you coded SECOPTS.OPERSEC = SAFDEF in the CNMSTYLE member instead of updating the
applicable members of the DSIPRF data set, update the IC keyword in the NETVIEW segment for each
user profile in the System Authorization Facility (SAF) product you are using. You might have to update
your command security configuration to accommodate the changes in the ways these commands are
run.
• Comment out or remove the POLICY statement for each tower that you have not enabled. The
CNMSTYLE member has a POLICY statement for each of the AON and GRAPHICS towers.
POLICY.AON = EZLCFG01
POLICY.GRAPHICS = DUIPOLCY
For each POLICY statement whose corresponding tower is not enabled, the NetView program issues the
EZL601I POLICY FILE xxxx NOT LOADED, yyy TOWER NOT ENABLED message, where xxxx is
the name of the policy member and yyy is the applicable tower.
• For the auxInitCmd definitions that were overridden by following the instructions in the previous
section, provide some mechanism for executing the original commands when the required VTAM or
TCP/IP services are available.
As an example, when VTAM issues the IST020I message to indicate that initialization is complete, a
REXX procedure driven by NetView automation could run the following commands:
'STARTCNM NLDM'
'STARTCNM NPDA'
One method is to add these commands to a section of code in CNMEVTAM, whose source code is
included with the NetView program. An automation table statement in the DSITBL01 sample causes the
NetView program to schedule the CNMEVTAM MSG command when the IST020I message is received.
The CNME1015 (STARTCNM) CLIST that is included with the NetView program ensures that the NLDM
and NPDA towers are enabled before attempting to start the tasks associated with these towers.
• If you enabled the AMI tower, prepare the NetView automation for that tower.
The CNMSTYLE member and its included members provide for sample automation table DSITBL01 and
its included members to be loaded as the first automation table. If the AMI tower is enabled, then
DSIAMIAT and its included members are inserted after that.
The AUTOTBL MEMBER=DSIAMIAT INSERT AFTER=1 command can be used to insert DSIAMIAT and
its included members after DSITBL01 and its included members. If you want to insert your own
automation tables before DSIAMIAT and its included members, you can change the applicable
AUTOTBL keywords to suit your installation.
The AUTOTBL command can be added to the CNMEVTAM CLIST or a command procedure that you
create and schedule to be driven when VTAM and TCP/IP network services become available.
• If CNME1015 was changed to prevent the STARTCNM GRAPHICS command from starting tasks while
the TCP/IP program was inactive, then some mechanisms should allow the STARTCNM GRAPHICS
command to start tasks again when TCP/IP completes initialization.
The previous section described the addition of code to the CNME1015 sample to prevent the starting of
tasks that implement the functions of the GRAPHICS tower unless a TCPIP_UP common global variable
had the value Y and the VTAM() function returned a non-null value, indicating that the NetView program
detected that VTAM initialization was complete. You must also create a command procedure to assign the
value Y to the TCPIP_UP common global variable when TCP/IP initialization completes, as indicated by
the EZAIN11I message for z/OS Communications Server TCP/IP.
DSIGDS, Network Product Support DST (including Common Operations Services, RUNCMD)
Network Service
VTAM
Used by these NetView program features:
MSM tower (communication with service points via SNA LU6.2)
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 151
GRAPHICS tower (communication with network management gateways using common operations
services)
Other product or user applications using common operations services (RUNCMD) also require
DSIGDS.
Command to execute:
START TASK=DSIGDS
NetView bridge
Network Service:
VTAM
Commands to execute:
• For NetView bridge
AUTOTASK OPID=BRIGOPER
AUTOTASK OPID=REMOPER
Note: NetView bridge also requires a NetView subsystem address space to be started with PPI
function.
AUTOTASK OPID=AUTOCSEC
CONNSEC DEFINE OPID=AUTOCSEC,TCPNAME=TCPIP
CONNSEC START,TCPNAME=TCPIP
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 153
For the TCPCONN subtower:
AUTOTASK OPID=AUTOTCPC
TCPCONN DEFINE OPID=AUTOTCPC TCPNAME=TCPIP
TCPCONN START TCPNAME=TCPIP
AUTOTASK OPID=AUTOPKTS
PKTS DEFINE OPID=AUTOPKTS,TCPNAME=TCPIP
PKTS START TCPNAME=TCPIP
AUTOTASK OPID=AUTOOPKT
PKTS DEFINE OPID=AUTOOPKT,
TCPNAME=TCPIP,
PSOURCE=OSA
PKTS START PSOURCE=OSA
TCPNAME=TCPIP
AUTOTASK OPID=DUIFPOLI
If the GRAPHICS tower is enabled, ensure that RODM is started and that the GMFHS data model is
loaded.
If RODM is started at this point in the process, the TEMA and DISCOVERY towers are enabled, and if
the Z NetView Enterprise Management Agent is not running, you might receive error messages such
as the following messages:
The types of data for which you receive these messages depend on which subtowers are enabled for
the DISCOVERY and TEMA towers.
These instructions defer the start of the Z NetView Enterprise Management Agent to prevent requests
for data that the NetView program has not yet collected.
Regardless of whether the GRAPHICS tower is enabled, run a command to initialize NetView policy on
the autotask named in the value of the function.autotask.Policy statement in the CNMSTYLE
member. This autotask was started in an earlier step. The following command can be used to initialize
NetView policy:
EXCMD AUTOAON,EZLEANTL
If other products or user applications load their own policies, you might reconsider the position of
policy initialization in this list of start instructions. If the AON tower is enabled, the EZLEANTL
command also initializes AON.
AUTOTASK OPID=AUTIPMGT
If you did not define the FKXEIPMI command as an initial command in the operator profile, then
schedule it to run. One method to start the command is as follows:
EXCMD AUTIPMGT,FKXEIPMI
GRAPHICS tower
Network Service:
VTAM or TCP/IP
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 155
Used by these NetView program features:
DISCOVERY tower
MSM tower
NetView Resource Manager
AMI tower
Commands to execute:
To begin, the autotask assigned as the value of the function.autotask.NMCpolicy statement,
DUIFPOLI in the CNMSTYLE member, was started in an earlier step in this list of instructions.
Start the autotask assigned as the value of the function.autotask.eventMGR statement,
DUIFEAUT in the CNMSTYLE member, using a command like the following command:
AUTOTASK OPID=DUIFEAUT
Start the autotask assigned as the value of the function.autotask.COS gateway statement,
DUIFCSGW in the CNMSTYLE member, using a command such as the following command:
AUTOTASK OPID=DUIFCSGW
To start the other components of the GRAPHICS tower, run the following command:
STARTCNM GRAPHICS
AUTOTASK OPID=AUTOMSMD
AUTOTASK OPID=AUTOMSM
If you are using the OPN subtower of MSM, then start the autotask assigned as the value of the
function.autotask.MSMopenAlerts statement, AUTOOPNA, in the CNMSTYLE member:
AUTOTASK OPID=AUTOOPNA
(MSM)function.autotask.MSMdefault = AUTOMSMD
(MSM)AUTOTASK.?MSMdefault.InitCmd = INITTOPT
S IHSAEVNT
(using the name of the sample E/AS start procedure that is provided with the NetView program)
The IHSAINIT sample that is provided with the NetView program is configured for E/AS to
automatically start the alert adapter task (ALERTA), the message adapter task (MESSAGEA), and the
event receiver task (EVENTRCV). If you must start them, you can use z/OS MODIFY (F) commands like
these:
F IHSAEVNT,START TASK=ALERTA
F IHSAEVNT,START TASK=MESSAGEA
F IHSAEVNT,START TASK=EVENTRCV
To start the trap-to-alert conversion task (TRAPALRT), which might receive SNMP traps that can
indicate changes to IP resources, use the z/OS MODIFY (F) command, as follows:
F IHSAEVNT,START TASK=TRAPALRT
If you are using the alert-to-trap conversion task (ALRTTRAP) to convert alerts to SNMP traps and
pass them to the z/OS Communications Server SNMP agent for forwarding to SNMP managers, use the
z/OS MODIFY (F) command to start the task as follows:
F IHSAEVNT,START TASK=ALRTTRAP
If you are using the confirmed alert adapter task (ALERTC) or confirmed message adapter task
(MESSAGEC) to send EIF events confirmed at the application level, you can use z/OS MODIFY (F)
commands to start the tasks as follows:
F IHSAEVNT,START TASK=ALERTC
F IHSAEVNT,START TASK=MESSAGEC
AUTOTASK OPID=AUTOAMI
AUTOTBL MEMBER=DSIAMIAT INSERT AFTER=1
INITAMI
If you are using the ACB monitoring feature, then run the following command:
INITAMON
If you are using the ACB monitoring feature, ensure that a NetView subsystem address space with PPI
function is active. If you enabled the ACB monitoring feature that saves data to a DB2 database,
ensure that the DSIDB2MT task is active.
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 157
Used by these NetView program features:
TEMA tower
Commands to execute:
Start the autotask that is defined on the function.autotask.COLTSK7 CNMSTYLE statement. For
example, for the function.autotask.COLTSK7=AUTOCT7 statement, you can use the following
command:
AUTOTASK OPID=AUTOCT7
If you are using the DISCOVERY INTERFACES subtower, start the autotask that is defined on the
function.autotask.COLTSK5 CNMSTYLE statement. For example, for the
function.autotask.COLTSK5=AUTOCT5 statement, you can use the following command:
AUTOTASK OPID=AUTOCT5
If you are using the DISCOVERY TELNET subtower, start the autotask that is defined on the
function.autotask.COLTSK6 CNMSTYLE statement. For example, for the
function.autotask.COLTSK6=AUTOCT6 statement, you can use the following command:
AUTOTASK OPID=AUTOCT6
EXCMD AUTOAON,CNMEERSC
Note: If you enabled a TEMA subtower that corresponds to an enabled DISCOVERY subtower and the
Z NetView Enterprise Management Agent did not start or did not complete initialization, you might
receive BNH638I and DWO050E messages similar to those described in “Policy and AON tower” on
page 154.
DVIPA tower
Network Service:
TCP/IP
Used by these NetView program features:
TEMA tower
Commands to execute:
Start the autotask defined as the value of the function.autotask.DVIPAUTM statement,
DVIPAUTO in the CNMSTYLE member, using a command such as the following command:
AUTOTASK OPID=DVIPAUTO
If you are going to log distributed DVIPA statistics, then start the autotask defined as the value of the
function.autotask.DVIPSTAT statement, DVIPSTAT in the CNMSTYLE member, using a
command such as the following command:
AUTOTASK OPID=DVIPSTAT
To initialize the distributed DVIPA statistics logging function, execute a command like the following
command:
DVIPALOG START
Start the collection autotask defined as the value of the function.autotask.COLTSK1 statement,
AUTOCT1 in the CNMSTYLE member, using a command such as the following command:
AUTOTASK OPID=AUTOCT1
AUTOTASK OPID=AUTOCT2
If you are using the DVCONN subtower of DVIPA, start the collection autotask defined as the value of
the function.autotask.COLTSK3 statement, AUTOCT3 in the CNMSTYLE member, using a
command such as the following command:
AUTOTASK OPID=AUTOCT3
If you are using the DVROUT subtower of DVIPA, start the collection autotask defined as the value of
the function.autotask.COLTSK4 statement, AUTOCT4 in the CNMSTYLE member, using a
command such as the following command:
AUTOTASK OPID=AUTOCT4
Note: If you have enabled a TEMA subtower that corresponds to an enabled DVIPA subtower and the
Z NetView Enterprise Management Agent has not been started or has not completed initialization, you
might receive BNH638I and DWO050E messages similar to those described in “Policy and AON
tower” on page 154.
AUTOTASK OPID=AUTONALC
If you are using Tivoli Enterprise Monitoring Server on the same instance of z/OS on which the
NetView program is running, start the Tivoli Enterprise Monitoring Server.
If you have defined Z NetView Enterprise Management Agent start parameters using the
EMAAUTO.TEMA.procStr statement in the CNMSTYLE member, the NetView program attempts to
use that to start the Z NetView Enterprise Management Agent. If you have not provided the
EMAAUTO.TEMA.procStr statement or gave it the value *NONE*, then you must start the Z NetView
Enterprise Management Agent.
Start the rest of the features of the tower by running a command on the autotask assigned as the
value of the function.autotask.NALCLOP statement, AUTONALC in the CNMSTYLE member, as in the
following example:
EXCMD AUTONALC,NACMD
NACMD starts the polling tasks for the following TEMA subtowers, if they are enabled:
• CONINACT
• CONNACT
• HEALTH
• SESSACT
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 159
NetView Discovery Library Adapter (DLA)
Network Service:
TCP/IP
Command to execute:
The autotask defined as the value of the function.autotask.DLAAUTO statement, AUTO2 in the
CNMSTYLE member, was allowed to start.
An example of a command to schedule the DLA is the following command:
The DLA expects to be able to start or use a NetView TSO server that can use TCP/IP services.
START TASK=CNMTRAPD,MOD=DSIZDST,MEM=CNMTRAPI,PRI=5
Status monitor (xxxxxVMT optional task, in which xxxxx is the NetView domain ID)
Network service:
VTAM
Command to execute:
START TASK=xxxxxVMT (where xxxxx is the NetView domain ID)
AUTOTASK OPID=AUTONVSP
IP Port Monitoring
Network service:
TCP/IP
Appendix E. Starting the NetView Program before VTAM or TCP/IP Network Services 161
Commands to execute:
Start the autotask defined as the value of the function.autotask.IPPORTMON statement, AUTOPORT
in the CNMSTYLE member. An example of a command for starting the autotask follows:
AUTOTASK OPID=AUTOPORT
EXCMD AUTOPORT,CNMETSTL
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Such information may be available, subject to appropriate terms and conditions, including in some cases
payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
Programming Interfaces
This publication documents information that is NOT intended to be used as Programming Interfaces of
IBM Z NetView.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml .
Adobe and Acrobat and all Adobe-based trademarks are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and service names might be trademarks of IBM or other companies.
Notices 165
166 IBM Z NetView: Installation: Getting Started
Index
Index 167
AUTOTASK CNMCLST 22, 43
profile 144 CNMCMD 121, 143
autotasks 97 CNMCMD command definitions 59
AUTOTCPC autotask 98 CNMCMDO 121
AUTOTCPS autotask 98 CNMCMDU 121
AUTOTMSI autotask 98 CNMCMENT 121
AUTOVTAC autotask 98 CNMCMSYS 121
AUTOVTDB autotask 98 CNMCRGC1 121
AUTOXCF autotask 98 CNMCRGR1 121
AUTOXDSC autotask 98 CNMCSSIR
AUTTRAn autotask 98 task 95
auxInitCmd statement 56 CNMDVIPP 23
CNMDVIPS 23
CNMESTYL 59
B CNMETSO 121
BFSESS command 79 CNMEVTAM command list 37
BNH845I message 135 CNMGMFHS 25
BNH846I message 132 CNMGNETV 121
BNH848I and BNH850I messages 135 CNMGSPCR 121
BNH848I message 135 CNMGTIVL 121
BNH849I message 134 CNMHELPF 121
BNH850I message 135 CNMI 143
BNJDSERV task 37, 95 CNMIPMGT 121
BNJLGPR cluster 27 CNMJSCL 121
BNJMBDST 119 CNMJSHW 121
BNJMNPDA task 95 CNMKEYS 121, 143
BNJPNL1 143 CNMKEYS2 121
BNJPNL2 143 CNMLINK data set 11
books CNMMIGKA 122
see publications ix CNMMIGKV 122
BRIGOPER autotask 98 CNMMSENU 122
buffer size, modifying 42 CNMMSJPN 122
CNMNDEF 25
CNMNET
C starting 71
CNMNEWS 74, 122
Canzlog
CNMPNL1 22, 143
archiving 54
CNMPOLCY 122
browsing 81
CNMPROC
filters 81
start procedures 39
Canzlog log 81
starting 72
catalog, defining user 21
CNMPRT 25
CDRM
CNMPSSI
identifying 109
start procedures 39
major node, network name for 33
starting the subsystem address space 71
CDRSC 34, 109
CNMS0001
central site control facility (CSCF)
logmode table 31
VSAM cluster 27
sample 122
changing
CNMS0003 29, 122
domain 23
CNMS0010 36, 122
subarea numbers 23
CNMS0013
VOLSER 23
modifying major nodes 29
channel-attached
STATOPT statements 31
terminals 35
CNMS002 16
checkpoint data sets, RODM 27
CNMS0031 16
class of service (COS) names, aliases for 34
CNMS0055 (DSICTMOD) 123
class-of-service table 117
CNMS0073 (A01SNA) 36, 123
CNM router task 143
CNMS0113 16
CNM routing table 116
CNMS8050 130
CNM01BRW 37
CNMS8051 130
CNM01LUC 37
CNMS8052 130
CNM01VMT 37
CNMS8053 130
CNMCALRT task 95
CNMS8054 130
CNMCAU00 121
CNMSAF2 130
Index 169
CNMSTYLE (continued) defining (continued)
overview 46 ALIAS translations 33
primary task phase 59 VSAM clusters 26
processing 58 definition data set members in DSIPARM 43
report 60 directory names, notation xiii
RODM name 48 DISCOVERY
security 55 INTERFACES subtower
statements, evaluating 60 HIPERSOCKETS subtower 50
STYLEVAR phase 59 OSA subtower 50
tower statement 49 discovery manager 56
CNMSUNXS 136 dispatch priority, setting 42
CNMSVPRT 136 DISPFK command 77
CNMSVTET 136 distributed targets
CNMSVTFT 136 AUTOCT2 autotask 97
CNMSXCFA 136 distribution media 5
CNMTAMEL task 95 DLOGMOD operand 31
CNMTRAPI 136 domain
CNMTRMSG 136 changing 23
CNMTRUSR 136 DOMAINID, changing 29
CNMTRXMP 136 DPRTY parameter 42
COLLCTL command 131 DSI6DST task 96
color maps 143 DSI6INIT 136
command DSI6SCF 137
security 55 DSIACBMT task 95, 100
command definitions 101 DSIALATD 137, 143
command designator, subsystem 57 DSIALTAB 33, 137, 143
command facility DSIAMIAT 137
list of commands 76 DSIAMIE 137
PF keys 77 DSIAMII 137
samples 102 DSIAMIN 137
testing 73 DSIAMIR 137
command list DSIAMIT 137
automatically run 56 DSIAMLTD 137, 143
defining 42 DSIAMLUT task 37, 95
definitions 143 DSIAPMI 137
command lists DSIAPML 137
user-modified 22 DSIAPMR 137
command processor 85 DSIARPT 22, 143
command revision table 4 DSIASRC 22, 143
connection routing information 131 DSIATOPT task 95
CONSNAME command 55 DSIAUTB 137
console 55 DSIAUTBU 137
conventions DSIBKMEM 137
typeface xiii DSICCDEF 137
COS (class of service) statement 34 DSICCSYS 138
COUPLExx member 16 DSICLD 42, 143
CP-MSU 134 DSICNM 138, 143
CPDLB2 volume 26 DSICORSV task 95
CSCFIML 130 DSICPINT 138, 143
CUADDR parameter 36 DSICRTR task 37, 95
customization 85, 86 DSICRTTD 138, 143
DSIDB2DF 138
DSIDB2MT task 95
D DSIDCBMT task 100
data cache DSIDMN 138
load procedure 25 DSIELMEM 138, 143
data collection DSIELTSK task 96
automation 131 DSIEX21 138
Data REXX 53 DSIGDS
data set naming conventions 5 starting VTAM ACBs and NetView tasks 37
data spaces 17 task 37, 96
DBAUTO1 autotask 98 DSIGEMTR 138
DBAUTO2 autotask 98 DSIGKPMT task 96, 100
defining DSIHINIT 138
Index 171
EKGXRODM 25 hardware monitor (continued)
EMCS console VSAM cluster 27
assigning names 55 help facility
enterprise master NetView program testing 75
AUTOERDT task 97 HIPERSOC command 132
environment variables, notation xiii HLL samples 101
estimates, decisions before calculating
full-screen automation 6
RODM checkpoint data sets 6
I
session awareness record filtering 6 IBMDS started task 12
event processing IBMNA started task 12
DVIPAUTO autotask 99 ICF catalog 21
extended multiple console support 55 IDS
extended multiple console support consoles 18 CNMSTIDS %INCLUDE 47
external log IEASYMxx member 15
initialization (no SMF) 143 IEASYSxx member 14
EZLCMENT 141 IEFACTRT exit 12
EZLSI101 27 IEFACTRT exit routine
EZLSI300 25, 141 AUTOSMF3 autotask 98
EZLSI301 25, 141 AUTOTCPS autotask 98
EZLTCFG task 96 IEFACTRT SMF exit 134
EZLTDDF task 97 IEFSSNxx member 12
EZLTLOG task 97 IEFUSI exit 17
EZLTSTS task 97 IFSTAT command 132
IHSAEVNT 25, 141
F IKJTSOxx member 16
index, naming conventions 5
FKVCMENT 141 Information/Management 44
FKXCMENT 141 initial command
FKXIPMTB 141 automatically run 56
FKXOPFIP 141 installation
FKXSI101 27, 141 results 7
FKXSI201 141 task definition 6
FLBEXV 16 verification 28
FLBOSIDS 16 installation exits 85
FLBSRT 16 installing
FLBSYSD 16 NetView 21
FLBTOPO task 99 internal trace
focal point autodial specifying allocation 41
DSILCOPR autotask 98 Intrusion Detection Services 47
full-screen sessions 32 IP interfaces 132
IP management
testing 81
G ISTMGC00 table 35
GETCONID command 55 ISTMGC01 table 35
GETTOPO command ISTSDCOS class of service table 35
AUTOMSMD autotask 97
GMFHS J
DUIFEAUT autotask 99
DUIFPOLI autotask 99 JCL symbolics in naming conventions 5
installation samples 101 JES 66
samples 102
start procedure 25
K
H KEEP, global 96
KPDDSCO program 16
hardware monitor
color maps 143
Information/Management 44
L
panel definitions 143 Link Pack Area (LPA)
samples 101 building pageable 10
SMF log records 17 creating 10
testing 83 LIST command 77
Index 173
NETWORK statement 33 PPO value on AUTH operand 30
NEVIEW.CNM01 PPOLOG statement 36
CNMDVIPS 23 preinstallation tasks
NLDM command 84 applying required PTFs and APARs 6
NMI automation 131 estimating resources 6
notation getting the PSP Bucket 6
environment variables xiii program directory 6
path names xiii preventive service planning 6
typeface xiii primary POI task 30
NPDA command 83 primary task phase 59
NPS initialization 143 print log
NTRI 112 automatically 44
NV2I, local system variable 41 priority, setting dispatch 42
NVSTAT command 134 program directory 6
program-to-program interface (PPI) 4
PROGxx member 11
O PSP 6
online publications PTF 6
accessing xi publications
operator accessing online xi
automated tasks 97 IBM Z NetView ix
changing IDs 97 ordering xii
control sessions 32
multiple concurrent 31 R
security 55
operator definitions 144 REG (region size) operand 40
operator profile region size
CONSNAME attribute 55 specifying 42
sample 144 RELATE value to define user catalog 21
operator profiles REMOPER autotask 99
user-modified 22 resource
optional tasks 95 defining 31
organization, NetView and network 1 name, defining to status monitor 31
ORIGNET statement 33 names, using alias names to resolve duplicate 32
OSA channels and ports resource estimates 6
AUTOCT5 autotask 97 REXX alternate library 12
OSAPORT command 134 REXX Execs
user-modified 22
REXX library, defining 42
P REXX samples 102
P256BUF operand 40 REXX/370 library 12
P4000BUF operand 40 RKANMOD data set 12
packet trace RKANMODL data set 12
AUTTRAn autotask 98 RKANMODU data set 12
Packet trace RODM
log, saved 27 checkpoint data set, allocating 27
panel data set load data cache procedure 25
user-modified 22 log, allocating 27
panels samples 102
source 143 start procedure 25
partitioned data sets symbolic substitution 16
allocating 21 root name 29
loading ROUTECDE operand 40
new installation 24
password S
VSAM 27
path names, notation xiii SAA DM members 101
PATH statement 113 sample network 1
PDS members 143 samples
PF key settings 77 domain 23
POI task, defining VTAM 30 network 1
PPI (program-to-program interface) 4 subarea 23
PPIOPT operand 40 SAQNLINK data set 11
Index 175
tasks (continued) VSAM
DSIAMLUT 37 allocating 26
DSICRTR 37 data sets, naming conventions 5
DSIGDS 37 password, defining 27
optional 95 passwords 27
restarting VTAM, considerations 37 sample databases 28
starting and stopping 97 VSAM DB automation
statements 47 DBAUTO1 autotask 98
supplied by the NetView product 97 DBAUTO2 autotask 98
VPDTASK 37 VSAM, changing VOLSER 23
TCP/IP VTAM
configuration data 45 ACBs, and corresponding NetView tasks 37
defining 45 APPL major node 23
TCP/IP profile application programs 106
VIPADYNAMIC 131 assembling tables 35
TCP/IP socket application 45 CDRSC definition statement 34
TCP/IP stack channel-to-channel attachment 112
DVIPA configuration changes 98 channel-to-NCP attachment 113
Telnet servers class-of-serve table 117
AUTOCT6 autotask 97 CNM routing table 116
TELNSTAT command 135 configuration list 29
TESTPORT function configuration lists 104
AUTOPORT autotask 98 cross-domain resource managers 109
Tivoli cross-domain resources 109
user groups xii defining NetView to 29
Tivoli Enterprise Monitoring Services definitions
AUTOTMSI autotask 98 reviewing for mode and table changes 35
Tivoli Software Information Center xi load modules for sample network 22
TNPTSTAT command 136 local non-SNA terminals 107
TOWER statement 47, 49 local SNA devices 108
tower statements 52 logon mode table 117
trace NETID start option 33
specifying allocation 41 NetView management console updates 30
transMember statement 57 NTRI 112
transTbl statement 57 PATH definition 113
TSO/E settings 16 SNA topology manager 30
typeface conventions xiii span of control 144
SSCP table 110
start options 36, 104
U start procedure 11, 25, 36, 117
unattended operator profile 144 starting 71
unique identifier, assigning NetView 48 USS table 116
user catalog, defining 21 VTAM ACB monitor
user group, NetView xii AUTOVTAC autotask 98
user groups AUTOVTDB autotask 98
NetView xii VTAM definitions 101
Tivoli xii VTAMLIB data set 22
USS table 116 VTAMLST data sets 22
USS table changes, reviewing 35
W
V Web browser
variables, DSIJSTYL 58 access 55
variables, notation for xiii Web server interface
verifying DSIWEB task 98
installation 73 Web Services Gateway
of NetView 73 AUTONVSP autotask 98
VIPA routes Web Services Gateway function 12, 93
AUTOCT4 autotask 97 Web Services server 12
VIPADYNAMIC TCP/IP profile 131 WHO command 77
VIPAROUT command 136
VOLSER, changing 23
VPDTASK task 37, 97
Z
Z NetView Enterprise Management Agent
AUTONALC autotask 98
AUTONDCn autotask 97
z/OS exit routine 17
ZAIGET 130
ZAIPROC 130
ZAITIMER 130
Index 177
178 IBM Z NetView: Installation: Getting Started
IBM®
GI11-9443-08