IBM Z NetView

6.4

Installation: Configuring Graphical

Components

IBM

GC27-2852-04
 Note
Before using this information and the product it supports, read the information in “Notices” on page
73.

This edition applies to version 6, release 4 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 GC27-2852-03.
© Copyright International Business Machines Corporation 2001, 2022.
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..................................................................................................................... x
Using IBM Z NetView online help.......................................................................................................... xi
Accessing publications online............................................................................................................... xi
Ordering publications ............................................................................................................................xi
Accessibility ............................................................................................................................................... xii
Support information................................................................................................................................... xii
Conventions used in this publication......................................................................................................... xii
Typeface conventions .......................................................................................................................... xii
Operating system-dependent variables and paths.............................................................................xiii
Syntax diagrams...................................................................................................................................xiii

Chapter 1. Introduction......................................................................................... 1
Managing NetView Resources with the NetView Resource Manager.........................................................1
Managing Sysplex Resources with the NetView Discovery Manager......................................................... 2
Planning the Installation Process................................................................................................................2

Chapter 2. Enabling Graphics Support.................................................................... 5

Enabling RODM.............................................................................................................................................5
Enabling GMFHS...........................................................................................................................................6
Enabling NetView Resource Manager..........................................................................................................6
Enabling the Discovery Manager................................................................................................................. 6

Chapter 3. Preparing and Activating RODM and GMFHS.......................................... 7

Preparing RODM........................................................................................................................................... 7
Defining RODM as an MVS Subsystem................................................................................................... 7
Allocating VSAM Clusters for RODM...................................................................................................... 7
Bypassing or Defining Security...............................................................................................................9
Updating the RODM Start Procedure................................................................................................... 13
Defining RODM Using the EKGCUST Member......................................................................................13
Defining Initialization Values for RODM DSIQTSK Task...................................................................... 15
Preparing GMFHS.......................................................................................................................................16
Updating the GMFHS Start Procedure................................................................................................. 16
Defining Initialization Values for the GMFHS Main Task..................................................................... 16
Defining the COS Gateway Autotask....................................................................................................17
Defining the Event Manager Autotask................................................................................................. 17
Defining the Scope Checker OPT......................................................................................................... 17
Defining the NMCSTATUS Policy Autotask...........................................................................................18
Starting RODM Using Job EKGXRODM...................................................................................................... 18
Verifying the RODM Installation................................................................................................................ 21
Loading the Data Models........................................................................................................................... 22
Starting GMFHS Using Job CNMGMFHS....................................................................................................23
Verifying the GMFHS Installation.............................................................................................................. 25

iii
 Chapter 4. Installing and Configuring the NetView Management Console for
Graphics..........................................................................................................27
NetView Setup for the NetView Management Console............................................................................ 28
Defining the Status Focal Point............................................................................................................ 28
Security Considerations....................................................................................................................... 29
Workstation Setup for the NetView Management Console...................................................................... 30
Installing and Configuring the NetView Management Console Topology Server............................... 31
Installing the NetView Management Console Topology Console....................................................... 35
Verifying the NetView Management Console Installation........................................................................ 35
Starting the Topology Server................................................................................................................35
Begin Communication with the NetView Management Console Topology Server............................. 35
Starting the Topology Console............................................................................................................. 36
Signing On to the NetView Management Console Topology Console................................................. 36
Customizing the NetView Management Console................................................................................ 36

Chapter 5. Preparing and Activating the NetView Resource Manager.....................37

Defining the NetView Resource Manager Autotask.................................................................................. 37
Security Considerations.............................................................................................................................37
RODM Access....................................................................................................................................... 37
Command Authorization...................................................................................................................... 38
Initialization Considerations......................................................................................................................39
Sampling............................................................................................................................................... 39
Display Status Defaults........................................................................................................................ 39
Monitoring Remote NetView Systems................................................................................................. 39
Starting the NetView Resource Manager.................................................................................................. 40
Verifying the NetView Resource Manager Installation............................................................................. 40

Chapter 6. Preparing and Activating the Discovery Manager..................................43

Security Considerations.............................................................................................................................43
RODM Access....................................................................................................................................... 43
Command Authorization...................................................................................................................... 43
Initialization and Operational Considerations.......................................................................................... 44

Chapter 7. Managing Views.................................................................................. 45

Types of Views........................................................................................................................................... 45
Restricting Access to Views.......................................................................................................................46
Applying Policy to Views............................................................................................................................ 47
Correlating Views....................................................................................................................................... 47
Enabling Object Correlation for GMFHS Resources............................................................................ 47
Tools for Managing Views.......................................................................................................................... 48
RODMVIEW...........................................................................................................................................48
RODM Unloader.................................................................................................................................... 48
FLCARODM............................................................................................................................................48
RODM Collection Manager................................................................................................................... 48
BLDVIEWS............................................................................................................................................ 49
DELVIEWS.............................................................................................................................................50

Appendix A. SNA Definitions for the NetView Management Console Topology

Servers............................................................................................................51
Ethernet LAN-Attached NetView Management Console Servers.............................................................51
Token-Ring LAN-Attached NetView Management Console Servers........................................................ 52
Defining the Logical Unit (LU) Name..........................................................................................................53
Configuring Your Workstation for SNA................................................................................................. 53

Appendix B. NetView Graphics Samples...............................................................59

iv
 GMFHS Samples........................................................................................................................................ 59
NetView Management Console Samples.................................................................................................. 60
NetView Resource Manager Samples....................................................................................................... 60
RODM Samples.......................................................................................................................................... 61
FLCARODM Samples............................................................................................................................ 70

Notices................................................................................................................73
Programming Interfaces............................................................................................................................74
Trademarks................................................................................................................................................ 74
Privacy policy considerations.................................................................................................................... 74

Index.................................................................................................................. 77

v
vi
Figures

1. Graphical Components..................................................................................................................................1

2. Example of the EKGCUST Customization Input Member Syntax...............................................................14

3. GMFHS Status Command Results...............................................................................................................25

4. NetView Management Console Overview...................................................................................................27

5. Collapsed View Tree.................................................................................................................................... 46

6. Expanded View Tree....................................................................................................................................46

vii
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, the IBM Z NetView Installation: Configuring Graphical Components,
provides information about installing NetView graphics.

Intended audience
This publication is for system programmers who install NetView graphics.

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.

IBM Z NetView library

The following documents are available in the IBM Z NetView library:
• Administration Reference, SC27-2869, describes the NetView program definition statements required
for system administration.
• Application Programmer's Guide, SC27-2870, describes the NetView program-to-program interface
(PPI) and how to use the NetView application programming interfaces (APIs).
• Automation Guide, SC27-2846, describes how to use automated operations to improve system and
network efficiency and operator productivity.
• Command Reference Volume 1 (A-N), SC27-2847, and Command Reference Volume 2 (O-Z), SC27-2848,
describe the NetView commands, which can be used for network and system operation and in
command lists and command procedures.
• Installation: Configuring Additional Components, GC27-2851, describes how to configure NetView
functions beyond the base functions.
• Installation: Configuring the NetView Enterprise Management Agent, GC27-2853, describes how to
install and configure the IBM Z NetView Enterprise Management Agent.
• Installation: Getting Started, GI11-9443, describes how to install and configure the base NetView
program.
• Installation: Migration Guide, GC27-2854, describes the new functions that are provided by the current
release of the NetView product and the migration of the base functions from a previous release.
• IP Management, SC27-2855, describes how to use the NetView product to manage IP networks.
• Messages and Codes Volume 1 (AAU-DSI), GC27-2856, and Messages and Codes Volume 2 (DUI-IHS),
GC27-2857, describe the messages for the NetView product, the NetView abend codes, the sense
codes that are included in NetView messages, and generic alert code points.
• Programming: Pipes, SC27-2859, describes how to use the NetView pipelines to customize a NetView
installation.
• Programming: REXX and the NetView Command List Language, SC27-2861, describes how to write
command lists for the NetView product using the Restructured Extended Executor language (REXX) or
the NetView command list language.
• Security Reference, SC27-2863, describes how to implement authorization checking for the NetView
environment.
• Troubleshooting Guide, GC27-2865, provides information about documenting, diagnosing, and solving
problems that occur in the NetView product.

© Copyright IBM Corp. 2001, 2022 ix

 • Tuning Guide, SC27-2874, provides tuning information to help achieve certain performance goals for the
NetView product and the network environment.
• User's Guide: Automated Operations Network, SC27-2866, describes how to use the NetView
Automated Operations Network (AON) component, which provides event-driven network automation,
to improve system and network efficiency. It also describes how to tailor and extend the automated
operations capabilities of the AON component.
• User's Guide: NetView, SC27-2867, describes how to use the NetView product to manage complex,
multivendor networks and systems from a single point.
• User's Guide: NetView Enterprise Management Agent, SC27-2876, describes how to use the NetView
Enterprise Management Agent.
• Licensed Program Specifications, GC31-8848, provides the license information for the NetView product.
• Program Directory for IBM Z NetView US English, GI11-9444, contains information about the material
and procedures that are associated with installing the NetView product.
• Program Directory for IBM Z NetView Japanese, GI11-9445, contains information about the material and
procedures that are associated with installing the NetView product.
• Program Directory for IBM Z NetView Enterprise Management Agent, GI11-9446, contains information
about the material and procedures that are associated with installing the IBM Z NetView Enterprise
Management Agent.
The following books are archived:
• Customization Guide, SC27-2849, describes how to customize the NetView product and points to
sources of related information.
• Data Model Reference, SC27-2850, provides information about the Graphic Monitor Facility host
subsystem (GMFHS) and MultiSystem Manager data models.
• Installation: Configuring Graphical Components, GC27-2852, describes how to install and configure the
NetView graphics components.
• Programming: Assembler, SC27-2858, describes how to write exit routines, command processors, and
subtasks for the NetView product using assembler language.
• Programming: PL/I and C, SC27-2860, describes how to write command processors and installation exit
routines for the NetView product using PL/I or C.
• Resource Object Data Manager and GMFHS Programmer's Guide, SC27-2862, describes the NetView
Resource Object Data Manager (RODM), including how to define your non-SNA network to RODM and
use RODM for network automation and for application programming.
• User's Guide: NetView Management Console, SC27-2868, provides information about the NetView
management console interface of the NetView product.

Related publications
You can find additional product information on the IBM Z NetView web site at https://www.ibm.com/
products/z-netview.
For information about the NetView Bridge function, see Tivoli NetView for OS/390® Bridge Implementation,
SC31-8238-03 (available only in the V1R4 library).

Terminology in this Library

The following terms are used in this library:
CNMCMD
For the CNMCMD member and the members that are included in it using the %INCLUDE statement
CNMSTYLE
For the CNMSTYLE member and the members that are included in it using the %INCLUDE statement
DSIOPF
For the DSIOPF member and the members that are included in it using the %INCLUDE statement

x IBM Z NetView: Installation: Configuring Graphical Components

 IBM® Tivoli® Netcool®/OMNIbus
For either of these products:
• IBM Tivoli Netcool/OMNIbus
• IBM Tivoli OMNIbus and Network Manager
MVS™
For z/OS® operating systems
MVS element
For the base control program (BCP) element of the z/OS operating system
NetView
For the following products:
• IBM Z NetView version 6 release 4
• IBM Z NetView version 6 release 3
• IBM Tivoli NetView for z/OS version 6 release 2 modification 1
• NetView releases that are no longer supported
PARMLIB
For SYS1.PARMLIB and other data sets in the concatenation sequence
VTAM®
For Communications Server - SNA Services
Unless otherwise indicated, topics to programs indicate the latest version and release of the programs. If
only a version is indicated, the topic is to all releases within that version.
When a topic is made about using a personal computer or workstation, any programmable workstation
can be used.

Using IBM Z NetView online help

The following types of IBM Z NetView mainframe online help are available, depending on your installation
and configuration:
• General help and component information
• Command help
• Message help
• Sense code information
• Recommended actions

Accessing publications online

IBM posts publications for this and all other products, as they become available and whenever they
are updated, to the IBM Documentation at https://www.ibm.com/docs/en. You can find IBM Z NetView
documentation on IBM Z NetView Documentation.
Note: If you print PDF documents on other than letter-sized paper, set the option in the Print window that
enables Adobe Reader to print letter-sized pages on your local paper.

Ordering publications
You can order many IBM publications online at http://www.ibm.com/e-business/linkweb/publications/
servlet/pbi.wss
You can also order by telephone by calling one of these numbers:
• In the United States: 800-426-4968
• In Canada: 800-879-2755

About this publication xi

 In other countries, contact your software account representative to order IBM publications. To locate the
telephone number of your local representative, perform the following steps:
1. Go to http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss.
2. Select your country from the list and click the grey arrow button beside the list.
3. Click About this site to see an information page that includes the telephone number of your local
representative.

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.

Conventions used in this publication

This section describes the conventions that are used in this publication.

Typeface conventions
This publication uses the following typeface conventions:
Bold
• Lowercase commands and mixed case commands that are otherwise difficult to distinguish from
surrounding text
• Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons,
list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs,
property sheets), labels (such as Tip:, and Operating system considerations:)
• Keywords and parameters in text
Italic
• Citations (examples: titles of publications, diskettes, and CDs
• Words defined in text (example: a nonswitched line is called a point-to-point line)
• Emphasis of words and letters (words as words example: "Use the word that to introduce a
restrictive clause."; letters as letters example: "The LUN address must start with the letter L.")
• New terms in text (except in a definition list): a view is a frame in a workspace that contains data.
• Variables and values you must provide: ... where myname represents...

xii IBM Z NetView: Installation: Configuring Graphical Components

 Monospace
• Examples and code examples
• File names, programming keywords, and other elements that are difficult to distinguish from
surrounding text
• Message text and prompts addressed to the user
• Text that the user must type
• Values for arguments or command options

Operating system-dependent variables and paths

For workstation components, this publication uses the UNIX convention for specifying environment
variables and for directory notation.
When using the Windows command line, replace $variable with %variable% for environment variables
and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment
variables are not always the same in the Windows and UNIX environments. For example, %TEMP% in
Windows environments is equivalent to $TMPDIR in UNIX environments.
Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions.

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 xiii
• “Punctuation and parentheses” on page xiv
• “Abbreviations” on page xiv
For examples of syntax, see “Syntax examples” on page xiv.

Symbols
The following symbols are used in syntax diagrams:

Marks the beginning of the command syntax.

Marks the end of the command syntax.

Indicates that the command syntax is continued on the next line.

Indicates that a statement is continued from the previous line.

|
Marks the beginning and end of a fragment or part of the command syntax.

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.

About this publication xiii

 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

Punctuation and parentheses

You must include all punctuation that is shown in the syntax diagram, such as colons, semicolons,
commas, minus signs, and both single and double quotation marks.
When an operand can have more than one value, the values are typically enclosed in parentheses and
separated by commas. For a single value, the parentheses typically can be omitted. For more information,
see “Multiple operands or values” on page xv.
If a command requires positional commas to separate keywords and variables, the commas are shown
before the keywords or variables.
When examples of commands are shown, commas are also used to indicate the absence of a positional
operand. For example, the second comma indicates that an optional operand is not being used:

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.

Abbreviations
Command and keyword abbreviations are listed in synonym tables after each command description.

Syntax examples
The following examples show the different uses of syntax elements:
• “Required syntax elements” on page xiv
• “Optional syntax elements” on page xv
• “Default keywords and values” on page xv
• “Multiple operands or values” on page xv
• “Syntax that is longer than one line” on page xvi
• “Syntax fragments” on page xvi

Required syntax elements

Required keywords and variables are shown on the main syntax line. You must code required keywords
and variables.

xiv IBM Z NetView: Installation: Configuring Graphical Components

 REQUIRED_KEYWORD required_variable

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 syntax elements

Optional keywords and variables are shown below the main syntax line. You can choose not to code
optional keywords and variables.

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

Default keywords and values

Default keywords and values are shown above the main syntax line in one of the following ways:
• A default keyword is shown only above the main syntax line. You can specify this keyword or allow it
to default. The following syntax example shows the default keyword KEYWORD1 above the main syntax
line and the rest of the optional keywords below the main syntax line.
• If an operand has a default value, the operand is shown both above and below the main syntax line. A
value below the main syntax line indicates that if you specify the operand, you must also specify either
the default value or another value shown. If you do not specify the operand, the default value above the
main syntax line is used. The following syntax example shows the default values for operand OPTION=*
above and below the main syntax line.

KEYWORD1 OPTION=*
COMMAND_NAME
KEYWORD1 OPTION= *
KEYWORD2 VALUE1

KEYWORD3 VALUE2

Multiple operands or values

An arrow returning to the left above a group of operands or values indicates that more than one can be
selected or that a single one can be repeated.

About this publication xv

 KEYWORD= (
,

REPEATABLE_OPERAND_OR_VALUE_1

REPEATABLE_OPERAND_OR_VALUE_2

REPEATABLE_OPERAND_OR_VALUE_3

value_n )

Syntax that is longer than one line

If a diagram is longer than one line, each line that is to be continued ends with a single arrowhead and the
following line begins with a single arrowhead.
OPERAND1 OPERAND2 OPERAND3 OPERAND4 OPERAND5 OPERAND6

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

xvi IBM Z NetView: Installation: Configuring Graphical Components

Chapter 1. Introduction

After you install and set up NetView graphics, you can monitor your system and network resources with
a dynamic, color-coded graphical display. NetView graphical displays are based on the Resource Object
Data Manager (RODM), which is an object-oriented data cache. Objects in RODM represent resources in
your network. The data cache is located in the memory of the host processor. Many applications can
interact with a single RODM, and more than one RODM can run on a host processor.
The Graphic Monitor Facility host subsystem (GMFHS) is the host program that works with RODM and
the NetView management console to manage resources. The NetView management console graphically
displays the resources that represent a network, a portion of the network, or a group of networks at
various levels of detail. GMFHS supports resources that can send status updates to the NetView program
in a standard format. GMFHS works with the NetView Resource Manager component and the NetView
management console to manage NetView tasks. GMFHS works with the discovery manager and the
NetView management console to view and manage sysplex TCP/IP stack information.
Figure 1 on page 1 shows the relationships of the graphical components.

Figure 1. Graphical Components

This document describes the steps required to install and enable the NetView graphical functions. Also
included are workstation-based components that support graphical or other access.

If you want information about... Refer to...

Installing RODM and GMFHS Chapter 3, “Preparing and Activating RODM and
GMFHS,” on page 7

Managing NetView Resources with the NetView Resource Manager

You can use the NetView Resource Manager to manage all NetView hosts in an enterprise from the
NetView management console. NetView hosts are monitored at the task level using the resource
utilization function of the NetView product.
NetView Resource Manager consists of NetView hosts that are either managers or agents. Those that
are managers require RODM and the NetView management console to use the full function of NetView
Resource Manager. NetView hosts that are agents forward their local host information to a manager or
managers.
The following information applies to NetView Resource Manager:
• Both managers and agents can forward their local host information to one or more managers.
• The ability to forward local host information is an agent function.

© Copyright IBM Corp. 2001, 2022 1

 • You can use SNA or TCP/IP as your communication vehicle between managers and agents.

Managing Sysplex Resources with the NetView Discovery Manager

The discovery manager provides a comprehensive set of monitoring tools for your sysplex, and a view of
your physical configuration. The discovery manager provides information that you can use to manage and
monitor your sysplex from the master NetView program. Additionally, information that is discovered by
the discovery manager can be viewed at the enterprise master NetView program.
The following kinds of resources can be monitored by the discovery manager:
• Central processor complex (CPC)
• Channel subsystem identifier
• Logical partition (LPAR)
• Sysplex
• Coupling facility
• z/OS image
• TCP/IP stack
• TCP/IP subplex
• IP interfaces
• Open Systems Adapter (OSA) channels and ports
• HiperSockets adapter
Note: Resource Object Data Manager (RODM) is required to display OSA and HiperSockets information in
any NetView user interface.
Discovery manager resources can be viewed in the NetView management console. If you are using the
NetView management console to view sysplex TCP/IP stack information, RODM is required.
For more information about managing and viewing sysplex resources that are discovered by the discovery
manager, see IBM Z NetView IP Management.

Planning the Installation Process

The following set of tasks is an overview of the installation process. This overview lists steps that are
required and those that are optional, depending upon the types of resources to be managed graphically.
1. Required: Prepare RODM, which includes:
• Updating the CNMSTYLE member
• Preparing MVS for RODM
• Allocating the RODM data sets
• Preparing the security system for RODM
• Updating the RODM procedure
• Customizing RODM startup values in EKGCUST
• Customizing the automated operations RODM task
• Updating the RODM load utility job to include the GMFHS data model
2. Required: Prepare GMFHS, which includes:
• Updating the CNMSTYLE member
• Updating the GMFHS start procedure
• Customizing GMFHS startup values in DUIGINIT
• Defining GMFHS-related tasks
3. Required: Prepare the NetView management console, which includes:

2 IBM Z NetView: Installation: Configuring Graphical Components

 • Updating the CNMSTYLE member
• Establishing a SNA LU 6.2 or TCP/IP session for the NETCONV command
• Installing the NetView management console topology server
• Installing NetView management console topology consoles
4. Optional: Prepare for managing non-SNA resources (for example IP resources), which includes:
• Updating the CNMSTYLE member
5. Optional: Prepare for managing NetView resources, which includes:
• Updating the CNMSTYLE member
• Defining AUTONRM to DSIOPF
• Preparing the security system for the NetView Resource Manager
6. Optional: Prepare for managing discovery manager resources, which includes:
• Updating the CNMSTYLE member

Chapter 1. Introduction 3
4 IBM Z NetView: Installation: Configuring Graphical Components
Chapter 2. Enabling Graphics Support

The NetView base definitions that enable the graphics functions are contained in the CNMSTYLE member.
Make all changes to CNMSTYLE definitions in the CNMSTUSR or CxxSTGEN member. For information
about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
CNMSTYLE statements are read during NetView initialization. Some changes to CNMSTYLE statements
require a restart of the NetView program before they take effect. For this reason, make all CNMSTYLE
updates at the same time for the graphics functions that you plan to use as part of this installation. The
following sections provide details on the CNMSTYLE definitions for the various graphics functions.
Note: The member name for the CNMSTYLE member is controlled by the value of NV2I in the NetView
start procedure.
The graphics components are activated with TOWER statements in the CNMSTYLE member. Copy the
TOWER statement to the CNMSTUSR or CxxSTGEN member and uncomment the components that you will
be using:
When the TOWER is enabled, various associated functions are also enabled during initialization. The
NetView program must be recycled for the TOWER statements to take effect.

If you want information about... Refer to...

CNMSTYLE statements IBM Z NetView Administration Reference and IBM Z
NetView Installation: Getting Started

Enabling RODM
Many NetView processes require the Resource Object Data Manager (RODM) name to be specified.
The RODMname statement in the CNMSTYLE member sets the CNMSTYLE.RODMNAME common global
variable.
You can set the RODM name using the system symbolic variable &CNMRODM in SYS1.PARMLIB. If you
do not set the &CNMRODM system symbolic variable, copy the following CNMSTYLE statement to the
CNMSTUSR or CxxSTGEN member and substitute the correct RODM name for &CNMRODM:

RODMname = &CNMRODM

For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
The CNMSTYLE member also contains the following global variables, which are used by the RODM
command list (CNME1098):

COMMON.EKGHNAM = RODM
COMMON.EKGHPRC = EKGXRODM

If necessary, copy these statements to the CNMSTUSR or CxxSTGEN member, and update the variables as
needed:
EKGHPRC
Change the EKGHPRC global variable to the name of your RODM procedure (if it is not the same as the
default value supplied with the NetView product).
EKGHNAM
If you started the RODM procedure using an identifier, change the EKGHNAM global variable to this
identifier (if it is not the same as the default value supplied with the NetView product). If you are not
using an identifier, the EKGHNAM global variable is not required.

© Copyright IBM Corp. 2001, 2022 5

Enabling GMFHS
The CNMSTYLE member contains the following global variables, which are used by the Graphic Monitor
Facility host subsystem (GMFHS) command list (CNME2101):

COMMON.DUIFHNAM = GMFHS
COMMON.DUIFHPRC = CNMGMFHS

If necessary, copy these statements to the CNMSTUSR or CxxSTGEN member, and update the variables as
needed:
DUIFHPRC
Specify your system PROC name for starting GMFHS. DUIFHPRC must be defined to the same name as
the GMFHS procedure.
DUIFHNAM
Specify the identifier you use when starting GMFHS. If you do not use an identifier when starting the
GMFHS procedure, do not specify the global variable DUIFHNAM.
For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.

Enabling NetView Resource Manager

To enable NetView Resource Manager, perform the following steps:
1. Copy the following CNMSTYLE statement to the CNMSTUSR or CxxSTGEN member:

INIT.NRM = No

2. Change No to Yes.
This starts NetView Resource Manager at NetView initialization.
If you do not change CNMSTYLE statements, NetView Resource Manager defaults to type MGR
(manager). No host destinations are defaulted.
3. If you want the NetView Resource Manager type to be an agent, copy the following CNMSTYLE
statements to the CNMSTUSR or CxxSTGEN member, and modify as needed for your system:
• NRM.TYPE
Change this statement to NRM.TYPE = Agent.
• NRM.HOSTDEST.x
Code as many NRM.HOSTDEST.x statements as are applicable.
Code CMODE and PORT statements as necessary (based on your HOSTDEST statements).
For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.

Enabling the Discovery Manager

The discovery manager is enabled by default with the DISCOVERY tower in the CNMSTYLE member.
To enable the discovery of Telnet servers and ports, IP interfaces, Open Systems Adapter (OSA), and
HiperSockets adapters, add the following statements to the CNMSTUSR or CxxSTGEN member with your
modifications. For information about changing CNMSTYLE statements, see IBM Z NetView Installation:
Getting Started.
• TOWER.DISCOVERY
• TOWER.DISCOVERY,INTERFACES
For more information, see IBM Z NetView Installation: Configuring Additional Components.

6 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 3. Preparing and Activating RODM and
GMFHS

NetView graphics are based on Resource Object Data Manager (RODM) and Graphic Monitor Facility host
subsystem (GMFHS). Before you can define graphics, you must install and define parameters for RODM
and GMFHS.
RODM and GMFHS require the Language Environment® for z/OS run time library. See the Program
Directory for IBM Z NetView for more information.

Preparing RODM
Use the steps in this section to prepare RODM.

Defining RODM as an MVS Subsystem

Before RODM can be used, it must be defined as an MVS subsystem in SYS1.PARMLIB member IEFSSNxx.
For more information, see IBM Z NetView Installation: Getting Started.

Allocating VSAM Clusters for RODM

Job CNMSJ004 defines the VSAM clusters for RODM. Table 1 on page 7 lists the data set
names that are associated with RODM, as well as the names of members containing VSAM cluster
information for these data sets. Any sample members needed to run CNMSJ004 are located in the
NETVIEW.V6R4USER.INSTALL data set that was created when you ran job CNMSJBUP.
Note: CNMSJ004 is a sample job that is run during basic NetView installation and might already have
been used to create the RODM VSAM clusters.
Before allocating VSAM clusters:
1. Review EKGSI101 and CNMSID01.
EKGSI101 provides the name, volume, catalog, and password specifications for the VSAM clusters that
are allocated. CNMSID01 specifies the name of the VSAM clusters that are to be deleted.
Ensure that the values specified in these input members are correct for your system.

Table 1. VSAM Clusters for the V6R4 Facilities

Facility Data Sets
RODM log NETVIEW.CNM01.EKGLOGP
NETVIEW.CNM01.EKGLOGS
RODM checkpoint NETVIEW.CNM01.EKGMAST
NETVIEW.CNM01.EKGTRAN
NETVIEW.CNM01.EKGCK001
NETVIEW.CNM01.EKGCK002

The EKGSI101 sample specifies VSAM SHAREOPTIONS(2) for performance reasons. However, with
SHAREOPTIONS(2), the RODM logging function makes no provision for secondary allocations. The
results of RODM logging with SHAREOPTIONS(2) using secondary allocations are unpredictable.
Note: Use the MVS MODIFY command to specify RODM logging options.
2. Make sure that the VSAM cluster names match the names in your RODM startup procedure,
EKGXRODM.

© Copyright IBM Corp. 2001, 2022 7

 3. With the checkpoint facility, you can save a copy of the data cache to DASD.
The data can then be read from DASD at RODM restart (warm start). Programs cannot access RODM
data during checkpointing.
The following VSAM clusters are used by the RODM checkpoint facility:
• NETVIEW.CNM01.EKGMAST is the RODM master window checkpoint data set.
This data set contains system information for RODM.
• NETVIEW.CNM01.EKGTRAN is the RODM translation window checkpoint data set.
This data set contains the translation address information that allows for correct data mapping and
addressing in the RODM data cache.
• NETVIEW.CNM01.EKGCK001 and NETVIEW.CNM01.EKGCK002 are RODM data window checkpoint
data sets.
These data sets contain the actual data in the RODM data cache.
You can create additional data window checkpoint data sets. Define a new checkpoint data set to
RODM by adding a DD card to the RODM start procedure using a file name format of EKGCKxxx,
where xxx is the next available 3-digit decimal number in the increasing sequence.
The size of the RODM checkpointing facility VSAM clusters that were defined to the RODM startup
procedure, EKGXRODM, determines the number of objects and classes that you can add to RODM. See
IBM Z NetView Tuning Guide for information about estimating the size of these data sets.
If you do not use the checkpoint facility, update the RODM procedure to remove the DD statements for
the checkpoint data sets and code the following statement in EKGCUST:

CHECKPOINT_FUNCTION ( NONE )

During initialization RODM looks for the checkpoint data sets. When it does not find them, you see one
or more of the following messages:

EKG1123I EKGXRODM : THE CHECKPOINT FUNCTION IS NOW DISABLED

To allocate VSAM clusters:

1. The default volume specified in EKGSI101 is VOL(CPDLB2). If your volume is not CPDLB2, change
CPDLB2 in these members to a valid volume.
Note: If you are deleting any of your existing VSAM clusters, review CNMSID01 to make sure you
delete the correct VSAM cluster names.
2. Run CNMSJ004.
3. Verify your return codes before continuing with the next step.
Note: If you need to allocate VSAM clusters for a second instance of RODM, you can run job EKGSLOG
to allocate the RODM log data sets as defined in EKGSI201 and job EKGSCKPT to allocate the RODM
checkpoint data sets as defined in EKGSI202.

If you want information about... Refer to...

RODM logging options IBM Z NetView Troubleshooting Guide

Using the RODM Log Formatter

The RODM log formatter (EKGRLOG) provides formatted output of the contents of the RODM log.

If you want information about... Refer to...

RODM log formatter IBM Z NetView Troubleshooting Guide

8 IBM Z NetView: Installation: Configuring Graphical Components

 Using the RODM Dump Utility
The RODM dump utility is a service program that makes it possible to print data residing in the RODM data
cache. The dump utility provides multiple formats for printing this information.
You can generate five types of reports to print the contents and structure of the RODM classes and
objects. These reports include:
• Class listing
• Class index
• Object listing
• Object index
• Statistical report

If you want information about... Refer to...

The output for each of the RODM dump utility IBM Z NetView Troubleshooting Guide
reports

Bypassing or Defining Security

The commands you issue to define RODM and the operators to the security class can vary, depending on
whether you use RACF® or another SAF product.
If you are using an SAF product, such as RACF, on your system, you can use one of the following methods
to define RODM security:
• Bypass system security with *TSTRODM.
• Define the RODM task and authority level to the RODMMGR class of your SAF product, if it is available.
• Define the RODM task and resources that represent authority levels to a user-defined class in your SAF
product.

If you want information about... Refer to...

RODM security IBM Z NetView Security Reference

Bypassing RODM Security

To bypass RODM security, initialize RODM with *TSTRODM in the SEC_CLASS field in EKGCUST when:
• Your system uses an SAF product, such as RACF, but you do not want to define RODM and operator
tasks to the SAF product for security.
• Your system does not use an SAF product.
• The SAF product is not active on your system.

Note: You can now recycle the target system with the create link pack area (CLPA) option.

Defining RODM Security to the RODMMGR Class

If you are using an SAF product which provides a RODMMGR class, define security resource names to that
product and authorize users to the correct SAF resources.

Defining RODM Security to a User-Defined Class

If you are using an SAF product for RODM security and if the SAF product does not provide the SAF
RODMMGR class, these steps must be completed before RODM can initialize:
• Define a security class in the SAF product for RODM.

Chapter 3. Preparing and Activating RODM and GMFHS 9

 For RACF, create a RACF router table for this security class, as described in the IBM Z NetView Security
Reference.
• Define security resource names for the class you define. For more information, see the IBM Z NetView
Administration Reference.

Defining the Resource Class to the RACF Class Descriptor Table

If you defined RODM security, use the SEC_CLASS operand in EKGCUST in CNMSAMP to specify the
security class definition for your installed security system.
If you do not define the class name in the EKGCUST customization file, or if you do not include the
EKGCUST DD statement in the JCL, the default security name is RODMMGR.
To use another class name as the default RACF security name, define the class_name to the RACF
class descriptor table and the RACF router table. Locate the RFTABLE in the RACINSTL member in
SYS1.SAMPLIB. RACINSTL contains sample RACF installation jobs.

If you want information about... Refer to...

RFTABLE job IBM Z NetView Security Reference

Using RACF for RODM Security

If you use “Defining RODM Security to the RODMMGR Class” on page 9 or “Defining RODM Security to a
User-Defined Class” on page 9, you must also perform the following operations:
• Define six RACF resource names under RODMMGR or your user-defined security class for the six user
authority levels.
• Define user IDs for users who are connecting to RODM.
• Authorize user IDs to the appropriate RACF resource names.
Note: RODM only verifies security levels for API calls into RODM, and not on the MODIFY command
interface. To implement security for the MODIFY command interface, refer to the SecureWay Security
Server for z/OS library.

Defining RACF Resource Names

To define the RACF resource names under RODMMGR for the six user authority levels, complete the
following steps from your RACF-authorized TSO ID.
1. To define the RODM resource names, if SEC_RNAME is RODM, enter:

RDEFINE RODMMGR RODM1 UACC(NONE)

RDEFINE RODMMGR RODM2 UACC(NONE)
RDEFINE RODMMGR RODM3 UACC(NONE)
RDEFINE RODMMGR RODM4 UACC(NONE)
RDEFINE RODMMGR RODM5 UACC(NONE)
RDEFINE RODMMGR RODM6 UACC(NONE)

If you have your own user-defined class_name, replace RODMMGR with the security class name on the
RDEFINE commands. The resource names used are an example.
The RODM resource names consists of a prefix and a suffix. The suffix must have values of 1 through
6 for the different levels of security. The default resource name prefix is the RODM name specified in
the RODM startup JCL. For example, the RODM name is ZZRODM using either of the following start
commands:

S EKGXRODM,NAME=ZZRODM
S EKGXRODM.ZZRODM

Your resources must use the name of your RODM.

If you specify your own RODM resource names, the resource name prefix must be specified in
EKGCUST on the SEC_RNAME statement if the resource name prefix is not the name of your RODM.

10 IBM Z NetView: Installation: Configuring Graphical Components

 RODM restricts the length of resource names by requiring that the resource name be one less than the
number you specify for MAXLNTH. For RODMMGR, MAXLNTH is 44, so the resource name must contain
43 characters or less. If you define your own security class, MAXLNTH is specified when you define the
RACF class descriptor table. See “Defining the Resource Class to the RACF Class Descriptor Table” on
page 10 for information about defining a security class.
2. To set the system-wide RACF options, enter:

SETROPTS CLASSACT(RODMMGR)

If you have your own user-defined class_name, replace RODMMGR with the security class name on the
SETROPTS command. The resource class name used is an example.

Defining User IDs for Users Who Are Connecting to RODM

Typically, user IDs are already defined. If the user ID is already defined to RACF (for example, for normal
logon), no additional registration is required. To define a user ID, locate the RFTABLE job in the RACINSTL
member in SYS1.SAMPLIB. RACINSTL contains sample RACF installation jobs.

If you want information about... Refer to...

RFTABLE job IBM Z NetView Security Reference

Authorizing User IDs to RACF Resource Names

To access RODM, enter the following command from your authorized TSO ID for each userid that
requires access:

PERMIT resourcename CLASS(RODMMGR) ID(userid)

Where:
resourcename
Specifies the name of the RODM resource (such as RODM1 through RODM6) that has the appropriate
security level for the function that the userid needs to be able to perform. Indicate the highest level
RODM resource name the userid needs to access. If you indicate a user is authorized for RODM3, that
user also has authorization for security level 1 (RODM1) and security level 2 (RODM2) capabilities.
For example:

PERMIT RODM3 CLASS(RODMMGR) ID(USER1)

Indicates that USER1 is authorized to perform the capabilities of RODM security levels 1, 2, and 3.
Table 2 on page 11 describes the RODM security levels.
userid
Specifies the RACF user ID. You can list individual user IDs. You can also use the PERMIT command to
authorize a group to the authority level resources, which can be used to connect or remove user IDs
from the group as their need for RODM capabilities changes.
There are three special user IDs for AON, MultiSystem Manager, and the NetView Resource Manager.
These user IDs consist of the domain ID concatenated with the characters AON, MSM, and NRM
respectively.
Note: If you have a user-defined class_name, replace RODMMGR with the security class name on the
PERMIT commands.
Table 2 on page 11 shows how each level of access security includes those preceding it.

Table 2. RODM Access Security Levels

Resource Name Security Level Capabilities
rodm1 1 Connect and disconnect to RODM

Chapter 3. Preparing and Activating RODM and GMFHS 11

 Table 2. RODM Access Security Levels (continued)
Resource Name Security Level Capabilities
rodm2 2 Query and list of functions (queries only)
rodm3 3 Action and list of functions (queries or actions) including
triggering methods and change methods
rodm4 4 Checkpointing
rodm5 5 Administrative functions (adding or deleting from the RODM
data cache) and adding managerial objects
rodm6 6 Stopping RODM

NetView operators require RODM security level 2 or higher to use the QRS command to query whether
they have span of control over resources. Authorize the following items:
• RODM load function
The RODM load function requires a minimum of RODM security level 3. If your RODM loader job is run
as a started procedure, you can define it to the STARTED class in the SAF product to enable it to run
as a trusted user. You can define the task in the started procedure table, ICHRIN03; however, using the
STARTED class is preferred.
• GMFHS procedure
The GMFHS procedure requires a minimum of RODM security level 5.
• NetView procedure (if NetView user code accesses RODM)
• DSIQTSK task
The DSIQTSK task requires RODM security level 6. Define user ID DSIQTSK or the value of the ID
keyword of the REP statement in the DSIQTSKI initialization member.
• Any user who submits or starts one of the following items:
– RODM load function
– NetView procedure (if NetView user code accesses RODM)
– DSIQTSK task
• Any user who manipulates RODM from the NetView program by using either RODMVIEW panels or the
RODMVIEW command processors.
A minimum of RODM security level 2 for the NetView domain name, if span of control is being applied to
NetView management console views and resources.

Connecting to RODM
When connecting to RODM, a user ID and password or password phrase are part of the API request. A
password or password phrase is required, except when the program making the request is running in an
APF-authorized library. The user ID can be specified on the connection request, or RODM can extract it
from the SAF product.
You can connect to RODM with a blank user ID if the system on which RODM is installed has active
RODM security. In this case, RODM extracts the user ID from the SAF product. Connecting to RODM is not
allowed if you bypassed RODM security.
If you have RODM security active, the user ID that is associated with the connection request must be
defined to your SAF security product.
For started procedures, you can define the started procedure name to the STARTED class of the SAF
product. In RACF, this can also be accomplished by defining the task in the started procedure table,
ICHRIN03; however, using the STARTED class is preferred.

12 IBM Z NetView: Installation: Configuring Graphical Components

Updating the RODM Start Procedure
The NetView program supplies a sample RODM start procedure EKGXRODM in CNMSAMP. You can modify
the RODM start procedure to match your environment. Consider the following items:
• TYPE of startup (C for cold, W for warm, or COLDFORC for cold force)
• NAME assigned to this RODM (default is the RODM procedure name)
This name can be specified as a system symbolic.
• INIT to specify a method to run during RODM initialization (default is no initialization method)
• CUST to specify the customization member containing startup parameters
EKGCUST is supplied as a sample.
• Correct data set names for STEPLIB, EKGLOGP, EKGLOGS, and EKGCUST data sets, as well as the
checkpoint data sets if checkpointing is to be used
• Modification of the exit to accommodate the region size needed for RODM
If you have the IEFUSI exit on your system, modify the exit to accommodate the region size needed for
RODM. The IEFUSI exit can be used to limit:
– The region size and region limit
– The size of data spaces and hiperspaces for jobs started on an MVS system
Because RODM allocates a 2-gigabyte data space at initialization, modify your IEFUSI exit to enable
RODM to start. Note that IEFUSI is passed the address of the program name on input.

Defining RODM Using the EKGCUST Member

With the EKGCUST member, you can define values and tailor RODM to your installation's needs. If you
choose not to customize your RODM, the default values apply.
RODM looks for an optional EKGCUST DD statement in the job stream. EKGCUST names the input
customization member. If you defined a customization member, RODM reads it in. If not, RODM provides
defaults.
You can use symbols to represent operands, values, and comments in EKGCUST if symbolic substitution is
enabled on your system. Ensure that the symbols are defined in the IEASYMxx member of SYS1.PARMLIB.
See “RODM Customization Member Guidelines” on page 14 for more information.
Note: You can specify each operand once.
After initialization is complete, you are prompted for instructions to continue with the default values or to
stop the process of bringing up the RODM.

RODM Customization Member Format and Defaults

Figure 2 on page 14 is an example of the format and defaults for the RODM operands that you can
specify in the customization member. Except for the CELL_POOLS statement, the values in EKGCUST
are the default values that are assumed if a statement is not present in the member or if the EKGCUST
member is not available.

Chapter 3. Preparing and Activating RODM and GMFHS 13

 /********************************************************************/
/* Number of asynchronous tasks. The asynchronous tasks run */
/* some of the methods that are triggered within RODM. */
/********************************************************************/
ASYNC_TASKS ( 5 )

/********************************************************************/
/* Cell pool and cell size definition. You can specify up to 200 */
/* cell sizes and cell pools. */
/********************************************************************/
CELL_POOLS ( 8, 12, 16, 20 )
CELL_POOLS ( 24, 28, 32, 36:2 )
CELL_POOLS ( 40:2, 48:2, 52:2, 56:2 )
CELL_POOLS ( 60:2, 64:2, 68:3, 72:3 )
CELL_POOLS ( 80:3, 88:3, 100:3, 104:3 )
CELL_POOLS ( 112:3, 120:3, 128:3, 136:4 )
CELL_POOLS ( 144:4, 152:4, 160:4, 168:4 )
CELL_POOLS ( 176:4, 184:4, 192:4, 200:4 )
CELL_POOLS ( 208:4, 216:4, 224:4, 232:4 )
CELL_POOLS ( 240:4, 248:4, 256:4, 384:6 )
CELL_POOLS ( 484:9, 512:8, 768:9, 1024:8 )
CELL_POOLS ( 1536:12, 2048:16, 3072:24, 4096:32 )
CELL_POOLS ( 6144:48, 8192:64, 12288:96, 16384:128 )
CELL_POOLS ( 24576:192, 32768:256 )

Figure 2. Example of the EKGCUST Customization Input Member Syntax

RODM Customization Member Guidelines

You can code multiple operands in a single record (or line), separated by at least one blank, or you can
code them individually in separate records. Blanks between the operands and the left parenthesis as well
as blanks within the parentheses are ignored. For example,

CELL_POOLS (8,12,16,20)

reads the same as

CELL_POOLS ( 8, 12, 16, 20 )

You can specify operands in any order, and all operands are optional. You can use symbols to represent
operands and values in EKGCUST if symbolic substitution is enabled on your system. Ensure that the
symbols are defined in member IEASYMxx of SYS1.PARMLIB.
Besides the operands specified above, you can code comments in the customization member. The
beginning and closing comment delimiters, /* and */, need not appear in the same record or line.
Comments are ignored by RODM and can appear any place a blank space is allowed.
You can also use symbols to represent comments if symbolic substitution is enabled on your system.
Ensure that the symbols are defined in member IEASYMxx of SYS1.PARMLIB. Code a symbol for the
beginning comment delimiter and a symbol for the closing comment delimiter.
Note: Note that the symbols for the beginning and closing comment delimiters must be coded on the
same line in EKGCUST.
If you do not supply customization values, RODM provides the defaults for all operands. Consider these
default values as guides.

If you want information about... Refer to...

Customizing the RODM EKGCUST operands IBM Z NetView Administration Reference

RODM Customization Member Performance Considerations

Performance considerations differ depending upon your system environment and the other applications
you have installed. You can make performance enhancements by modifying the following parameters in
EKGCUST:
1. Set the following parameters to reduce the time spent acquiring and freeing storage:

14 IBM Z NetView: Installation: Configuring Graphical Components

 • PLI_ISA to 40K
• PRIMARY_HEAP_SIZE to 64K
• EXTEND_HEAP_SIZE to 32K
2. Set the CONCURRENT_USERS parameter to the maximum number of RODM user tasks you might have
at the same time.
If the number is too small, you cannot start all the RODM user applications you need. If the number is
too large, you will have unused storage. Start with a value of 20 and increase or decrease as required.
3. Set the ASYNC_TASKS parameter to the number of concurrently running asynchronous tasks. This
parameter controls the multiprogramming level of RODM and controls the asynchronous method API
tasks.
The default value of 5 asynchronous tasks is sufficient for most environments.

If you want information about... Refer to...

Customizing the RODM EKGCUST operands IBM Z NetView Tuning Guide

Defining Initialization Values for RODM DSIQTSK Task

DSIQTSKI contains the RODM initialization values for the DSIQTSK task.
The DSIQTSK task allocates storage, reads the DSIQTSKI initialization file, and carries out RODM
connections, disconnections, and checkpoint requests. This task is defined to the NetView program in
the CNMSTYLE member.
To automatically start the DSIQTSK task during NetView initialization, copy the following CNMSTYLE
statement to CNMSTUSR or CxxSTGEN, and change INIT=N to INIT=Y:

TASK.DSIQTSK.INIT=Y

For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
For each RODM you specify in DSIQTSKI you can define an initialization command processor to be
invoked when the DSIQTSK task successfully connects to RODM. Specify the name of this command
processor in each RODM definition statement.
The following example shows the DSIQTSKI initialization file:

CMDRCVR ID=DSIQTSK
*
REP &CNMRODM,CONN=N,AO=Y,T=30
⋮
TASK TASK001
TASK TASK002
⋮

Notice that you can specify the RODM name with a system symbolic (&CNMRODM).
You can define up to 64 RODMs and 64 NetView tasks in DSIQTSKI to be used for command routing.
The repository definition statements (REP) specify the object repository name, as well as:
• Whether DSIQTSK connects to the repository during initialization (CONN)
• Whether the repository is the current run time RODM (AO)
• The number of seconds that DSIQTSK waits to access the repository while it is being checkpointed (T)

If you want information about... Refer to...

The RODM automation task definition statements IBM Z NetView Administration Reference
Using the DSIQTSK task to manage your RODMs. IBM Z NetView Automation Guide
An example that illustrates using RODM to
automate the recovery of a failed resource.

Chapter 3. Preparing and Activating RODM and GMFHS 15

Preparing GMFHS
Use the steps in this section to define GMFHS.

Updating the GMFHS Start Procedure

The NetView program supplies a sample GMFHS start procedure CNMGMFHS (distributed as CNMSJH10)
in CNMSAMP. You can modify the GMFHS start procedure to match your environment.
To update the CNMGMFHS procedure for starting GMFHS, perform the following steps:
1. Change the domain name to match your NetView domain or invoke CNMGMFHS with
DOMAIN=domain_name.
2. For an aggregation warm start, code the AGGRST=YES parameter.
An object-independent method (DUIFFAWS) is invoked to start methods associated with the fields
related to status aggregation in the real and aggregate objects in the RODM data cache.
The default is that DUIFFAWS is not invoked and GMFHS starts normally.
3. For a resource status warm start, code the RESWS=YES parameter.
This causes GMFHS to bypass the normal clearing and soliciting of the initial status for all domain
resources and, instead, to use the existing status within RODM.
The default is that a resource status warm start is not invoked and GMFHS starts normally.
4. Set the ARM parameter.
The ARM parameter controls GMFHS registration with the MVS Automatic Restart Manager (ARM).
*ARM
Register with ARM using the default name, which is NETVIEW@@ concatenated with the domain
ID.
name
Register with ARM using a user-specified name. A valid name has the following characteristics:
• Consists of 1–16 characters.
• The first character cannot be numeric.
• The remaining characters can be alphanumeric, or the following special characters: @, #, or $.
• Alphabetic characters must be in uppercase.
*NOARM
Do not register with ARM. This is the default.
You can also use the MVS Automatic Restart Manager to group applications together by element type.
The GMFHS element type is SYSNETV4. The element type cannot be changed.
5. The SUBSYM parameter enables symbolic substitution for the data set members that are read by
GMFHS: DUIGINIT and DUIGPWLU.
*SUBSYM
Enable symbolic substitution. This is the default.
*NOSUBSYM
Disable symbolic substitution.

If you want information about... Refer to...

Aggregation and resource status warm starts IBM Z NetView Resource Object Data Manager and
(AGGRST=YES and RESWS=YES) GMFHS Programmer's Guide

Defining Initialization Values for the GMFHS Main Task

Use the GMFHS main task to perform the following tasks:

16 IBM Z NetView: Installation: Configuring Graphical Components

 • Start the GMFHS host environment.
• Start and control the GMFHS host subcomponents.
• Provide an interface to the MVS operator.
• Provide reinitialization services on completion of a CONFIG NETWORK command.
• End the GMFHS host session.
The GMFHS main task initialization keywords are contained in DSIPARM member DUIGINIT. Ensure that
your RODM name and user ID are correct. DUIGINIT contains the system symbolic &CNMRODM that can
be used to set the RODM name. See sample DUIGINIT for parameters that can be changed for your
environment.
The NetView management console topology servers that are restricted from accessing GMFHS are listed
in DSIPARM member DUIGPWLU. If no names are specified, all NetView management console topology
servers can access GMFHS.

If you want information about... Refer to...

The GMFHS host main task initialization keywords IBM Z NetView Administration Reference

Defining the COS Gateway Autotask

The common operations services (COS) gateway autotask uses the DUIFCSGW command processor to
receive commands for service points from the GMFHS scope checker OPT. The command processor
routes these commands to the appropriate COS gateway service point autotask. The command processor
also receives the command responses from the service point autotasks, correlates these to the
appropriate commands, and returns the correlated commands to the network command manager in the
GMFHS host.
The COS gateway autotask supports the GMFHS command support. COS gateway uses the RUNCMD
command to run commands on a service point.
If you specified TOWER=Graphics in the CNMSTYLE member, the COS gateway autotask (DUIFCSGW)
is started at NetView initialization. Statements are coded in the CNMSTYLE and CNMSTASK members to
facilitate the starting of the task. Do not change these statements.
The STARTCNM Graphics command also starts the COS gateway autotask.

Defining the Event Manager Autotask

The event manager autotask DUIFEAUT receives and interprets alerts for GMFHS. The event manager
posts resource status provided by alerts to the appropriate objects in the RODM data cache.
If you specified TOWER=Graphics in the CNMSTYLE member, the event manager autotask is started at
NetView initialization. Statements are coded in the CNMSTYLE and CNMSTASK members to facilitate the
starting of the task. Do not change these statements.

Defining the Scope Checker OPT

The GMFHS scope checker OPT (task DUIFSSCO) receives all workstation commands from the
interprocess communications (IPC) task using the program-to-program interface (PPI).
The IPC component of GMFHS provides message routing both within the GMFHS address space
and between the GMFHS address space (and other components). IPC does not perform application
processing; but it is the originator of, and destination for, messages related to session establishment and
release.
Some of the commands received by the scope checker OPT are:
• Activate, Deactivate, and Recycle commands
• Commands with NetView command definition statements that might require command authorization
For example:

Chapter 3. Preparing and Activating RODM and GMFHS 17

 – Resource specific commands
– Native commands
– Generic commands
The scope checker OPT carries out NetView command authorization on these commands. Commands
without proper authorization are sent with a command authorization failure reason code to the network
command manager (NETCMD) in the GMFHS host.
The scope checker OPT receives NetView OST gateway and COS gateway command messages from the
GMFHS NETCMD.
If you specified TOWER=Graphics in the CNMSTYLE member, the scope checker OPT is started at
NetView initialization. Statements are coded in CNMSTYLE and CNMSTASK members to facilitate the
starting of the task. Do not change these statements.

If you want information about... Refer to...

Protecting commands using scope of command IBM Z NetView Security Reference
authorization, the NetView command authorization
table, or an SAF security product

Defining the NMCSTATUS Policy Autotask

DUIFPOLI is the autotask used to process NMCSTATUS policy definitions.
You can automatically start the NMCSTATUS policy autotask and processing of the NMCSTATUS policy
definitions at NetView initialization. To do this, verify that you made the following updates in CNMSTUSR
or CxxSTGEN member (see Chapter 2, “Enabling Graphics Support,” on page 5):
• Graphics is uncommented on the TOWER statement.
• RODM identifier is specified on the RODMname statement.
You can change the name of the DUIFPOLI autotask to another autotask name. To do this, copy the
following CNMSTYLE statement to CNMSTUSR or CxxSTGEN:

(GRAPHICS)function.autotask.NMCpolicy = DUIFPOLI

Replace DUIFPOLI with your autotask name. The autotask name can be 1 - 8 characters long. When you
do this, a common global variable CNMSTYLE.AUTO.NMCPOLICY is created with the new autotask name.
For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
Note: Do not change the global variable CNMSTYLE.AUTO.NMCPOLICY in the CNMSTASK or DSITBL01
member.

If you want information about... Refer to...

Creating and loading a policy file containing IBM Z NetView Administration Reference
NMCSTATUS policy definitions

Starting RODM Using Job EKGXRODM

To start RODM, enter the following command at the system console:

S EKGXRODM,TYPE=C,NAME=rodmname

or

S EKGXRODM.RODM,TYPE=C,NAME=rodmname

The syntax for the START EKGXRODM command follows.

18 IBM Z NetView: Installation: Configuring Graphical Components

START
START EKGXRODM
. identifier

, TYPE = W , NAME = proc_name

, TYPE = W , NAME = rodmname

C

COLDFORC

, CLRSSB = NO

, INIT = methodname , CLRSSB = NO

YES

, CUST = EKGCUST , ARM = *NOARM

, CUST = member , ARM = *ARM

name

*NOARM

, SUBSYM = *SUBSYM

, SUBSYM = *SUBSYM

*NOSUBSYM

, ROUTECDE = 1

, ROUTECDE = route_code

EKGXRODM has the following parameters:

TYPE
Specifies whether to cold start or warm start RODM.
W
Specifies warm start. This is the default if you do not specify a type.
Note: Because of the changes to DUIFSTRC, the first time you start RODM for the NetView
program (after upgrading), specify C to perform a cold start of RODM.
C
Specifies cold start.
COLDFORC
Specifies cold start without issuing message EKG1918D, which requires operator intervention.
NAME
Specifies the rodmname of the RODM program to be started. If you do not enter a value for
rodmname, the NetView program defaults to the procedure name that you defined. For the samples
that are supplied with the NetView program, use RODMNAME as the example RODM name.
INIT
Specifies the name of the initialization method to run. If you leave this parameter blank, no
initialization method is run. See the IBM Z NetView Resource Object Data Manager and GMFHS
Programmer's Guide for additional information about writing initialization methods.

Chapter 3. Preparing and Activating RODM and GMFHS 19

 CLRSSB
Specifies to clear MVS storage traces left by a RODM that has ended abnormally or has been forced off
the system by the operator. Use this parameter only after a RODM has been forced off the system in
this manner, and then only after an attempt to restart RODM without the CLRSSB parameter has been
unsuccessful.
NO
Specifies not to force a restart of a RODM with the same name. This is the default.
YES
Specifies to force a restart of a RODM with the same name.
Note: When using this parameter, specify YES only if, when you start RODM, you receive message
EKG1912 EKGXRODM: THE RODM rodmname IS ALREADY ACTIVE, and are certain no RODM
with the same name is active.
The CLRSSB keyword has no effect on the number of SSBs that are stored in the CSA area.
CUST
Specifies the member name in EKGCUST DD PDS to be used as the customization file.
ARM
Controls RODM registration with the MVS Automatic Restart Manager (ARM).
*ARM
Register with ARM using a RODM-generated name, which is NETVIEW# concatenated with the
RODM name.
name
Register with ARM using a user-specified name. A valid name has the following characteristics:
• Consists of 1 - 16 characters.
• The first character cannot be numeric.
• The remaining characters can be alphanumeric, or the following special characters: @, #, or $.
• Alphabetic characters must be in uppercase.
*NOARM
Do not register with ARM. This is the default.
You can also use the MVS Automatic Restart Manager to group applications together by element type.
The RODM element type is SYSNETV3. The element type cannot be changed.
SUBSYM
The SUBSYM parameter enables symbolic substitution for the RODM customization member.
*SUBSYM
Enable symbolic substitution. This is the default.
*NOSUBSYM
Disable symbolic substitution.
ROUTECDE
Specifies the route code to be used for all WTO commands issued by RODM. The default value is 1.
When you receive the following message:

EKG1918D EKGXRODM: RODM rodmname WILL COLD START.

ENTER '1' TO CONTINUE OR '2' TO TERMINATE.

Type 1 to continue.
You then receive the following two messages:

IEC161I 227-229,EKGXRODM,EKGXRODM,EKGD003
EKG5011I EKGXRODM : THE NUMBER OF CHECKPOINT FILES USED
BY RODM IS 2.

20 IBM Z NetView: Installation: Configuring Graphical Components

 The last parameter in the first message (EKGD003) changes, depending on the number of checkpoint
files. It is always one more than the number of checkpoint files that you have specified in EKGXRODM.
EKGXRODM is shipped with two checkpoint files defined.
If you are running RODM without checkpoint data sets, you receive the following message:

EKG1123I EKGXRODM : THE CHECKPOINT FUNCTION IS NOW DISABLED

To start a second RODM:

• Allocate VSAM clusters by running job EKGLOG to allocate the RODM log data sets as defined in
EKGDLOG and job EKGWIND to allocate the RODM checkpoint data sets as defined in EKGDWIND.
• Specify a second rodmname. You cannot use the same rodmname (for example, RODMNAME) for the
second RODM.
• Create a second RODM start procedure and modify it to use the data set names you allocated with
EKGLOG and EKGWIND.
• Keep the checkpoint data sets of a RODM with the translation data sets (EKGTRAN) and the master
window data sets (EKGMAST) for each RODM. After you have performed a warm start on RODM, mixing
the checkpoint data sets from one RODM with the translation and master window data sets of another
RODM can corrupt the RODM data cache.
After RODM is initialized, you receive the following message:

EKG1900I EKGXRODM: RODM rodm INITIALIZATION IS COMPLETE WITH LE/370

Note: You cannot stop RODM by ending the current NetView program. To end RODM when started using
only its PROC name, enter the following command at the system console:

F procname,TERM

If you started RODM using an identifier, enter the following command at the system console:

F identifier,TERM

If you are running GMFHS and need to end or recycle RODM, end the GMFHS application before ending
RODM.
Note: GMFHS is dependent on the GMFHS data model being present in RODM and it is present only when
RODM is active. If you start GMFHS before RODM is active, or if you end RODM while GMFHS is still
active, GMFHS periodically checks to see if RODM has become active. If you then start RODM, and GMFHS
reconnects to RODM before the GMFHS data model becomes active, then GMFHS ends.

Verifying the RODM Installation

Start RODM using the instructions in “Starting RODM Using Job EKGXRODM” on page 18. To verify the
RODM installation using job EKGSVER:
1. Edit the PARM statement in job EKGSVER in the NETVIEW.V6R4USER.INSTALL data set to reflect the
rodmname and userid for your system.
Note: The rodmname and userid are required parameters. The password or password phrase is not
required with userid. You can specify a password or password phrase to your TSO user ID, but the
JES output log displays this password or password phrase. If you do specify a password or password
phrase, you might want to keep this verification job in a RACF authorized data set to prevent access to
the user ID passwords or password phrases.
2. Run job EKGSVER.
3. Ensure that the return code is 0.

Chapter 3. Preparing and Activating RODM and GMFHS 21

 If you specified the same user ID in DUIGINIT, you receive a return code of 8. Change the user ID in
EKGSVER to fix this problem.
The following example shows the output that you receive after running EKGSVER:

RODM name from JCL --> <RODM name>

User_id from JCL --> <user id>
**No Password Specified**
====================
Function ID --- > 1101
Return code --- > 0
Reason code --- > 0
User ID --- > <user id>
Trans ID --- > 6205
====================
Function ID --- > 1501
Return code --- > 0
Reason code --- > 0
Trans ID --- > 6206
Query EKG_Name field from EKG_System class
Response --- > <RODM name>
====================
Function ID --- > 1501
Return code --- > 0
Reason code --- > 0
Trans ID --- > 6207
Query EKG_Name field from EKG_System object
Response --- > <RODM name>
====================
====================
Function ID --- > 1501
Return code --- > 0
Reason code --- > 0
Trans ID --- > 6208
Query EKG_ExternalLogState
Response --- > 1
*** Log Enabled ***
====================
Function ID --- > 1102
Return code --- > 0
Reason code --- > 0
Trans ID --- > 6209
====================
Highest Return code --> 0
====================

If you want information about... Refer to...

The parameters (FUNCTION ID, RETURN CODE, for IBM Z NetView Resource Object Data Manager and
example) listed in this output file GMFHS Programmer's Guide

Loading the Data Models

The CNMSJH12 sample job, which is provided with the NetView program, loads the GMFHS data model.
It also loads RODM with the SNA topology data model class and object definitions that are required for
the dynamic definition of SNA objects, as well as the MultiSystem Manager data model class and object
definitions that are required for dynamic definition of the non-SNA objects. Each class contains a set of
fields describing the characteristics of an object. Classes also contain presentation fields from the GMFHS
data model that determine how an object is displayed in views on the NetView management console.
Job CNMSJH12 calls JCL procedure EKGLOADP to load the RODM data cache with a set of RODM class
definitions and methods and sample object definitions. To load the class and object definitions using job
CNMSJH12:
1. Verify that RODM is active.
2. Verify that your TSO ID is authorized if you are using a security facility, such as RACF.
3. Ensure that job CNMSJ003 has been run to copy EKGLOADP into one of your system PROCLIB data
sets, and that EGKLOADP has been modified to run on your system.
4. Edit job CNMSJH12:

22 IBM Z NetView: Installation: Configuring Graphical Components

 • In the PARM field of the EXEC statement, replace rodmname with the name by which RODM is known
to the applications to which it connects.
• Ensure that the EKGIN1 DD statements include the data model members for the components you
are using:
DUIFSTRC
GMFHS data model (required)
DUIFNRMx
NetView Resource Manager sample (uncomment to run)
FLCSDMx
MultiSystem Manager data model (uncomment to run)
DUIFSNET
Sample network member which can be loaded for test purposes (uncomment to run)
For more information about the data model samples, see Appendix B, “NetView Graphics Samples,”
on page 59.
• To install topology correlation, remove the comment before the load statement for FLCSDM8 in the
EKGIN1 data set concatenation.
5. Run CNMSJH12:
• As a batch job, your TSO user ID or USER on the job statement must be RACF-authorized if you are
using RACF to protect RODM.
• As a started procedure, you must update the RACF started procedure table, which assigns a RACF-
authorized user ID for the RODM load utility procedure if you are using RACF.
6. Ensure that the return code is 0 before proceeding.
If you need to run this job more than once to receive a return code of 0, you need to delete the classes
that were allocated during the previous running. You can delete these classes by stopping and then cold
starting RODM.
Note: When you cold start RODM, you delete all information in RODM.

If you want information about... Refer to...

Defining your network resources to RODM IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide
Authorizing user IDs for RACF IBM Z NetView Security Reference.

Starting GMFHS Using Job CNMGMFHS

CNMGMFHS (CNMSJH10) is copied to PROCLIB when you load partitioned data sets during installation.
The symbolics in CNMGMFHS must match the naming conventions for your system.
Complete the following steps before starting GMFHS:
1. Verify that RODM is active and the RODM data cache has been loaded with data models from
CNMSJH12, as explained in “Loading the Data Models” on page 22.
2. Your host is designated as the focal point host on the CNMTAMEL statement in CNMSTASK. The
member name is set to MEM=DUIISFP.
Notes:
a. Make sure the Graphics tower is enabled on the TOWER statement in the CNMSTYLE member.
b. If you updated the CNMTAMEL task statement before you started CNMPROC, you can make the
change by stopping and starting CNMTAMEL. Enter the following from the NetView command
facility:

STOP TASK=CNMTAMEL
START TASK=CNMTAMEL,MEM=DUIISFP

Chapter 3. Preparing and Activating RODM and GMFHS 23

 To start GMFHS, enter the following command at the system console:

S CNMGMFHS.GMFHS

You receive messages similar to the following messages:

DUI4027I GMFHS MAIN TASK INITIALIZATION IS COMPLETE FOR DOMAIN = domainid

DUI4003I GMFHS NETWORK CONFIGURATION INITIALIZED SUCCESSFULLY

The syntax for the START CNMGMFHS command follows:

START
START CNMGMFHS
. identifier

, CLRSSB = NO

, DOMAIN = domain_name , CLRSSB = NO

YES

, CUST = EKGCUST , ARM = *NOARM

, CUST = member , ARM = *ARM

name

*NOARM

, AGGRST = N , RESWS = N

, AGGRST = Y , RESWS = Y

N N

, SUBSYM = *SUBSYM

, SUBSYM = *SUBSYM

*NOSUBSYM

, ROUTECDE = 1

, ROUTECDE = route_code

where:
DOMAIN=domain_name
Specifies the name of your NetView domain.
AGGRST=Y|N
Specifies whether to run AGG calculation. The default is no (N).
ARM=*NOARM|*ARM|name
Specifies whether to register with the Automatic Restart Manager (ARM). The default is *NOARM.
If the value is ARM, the name generated is NETVIEW@@ concatenated with the domain_name and
the element type (SYSNETV4). This name cannot be changed.
You can register with ARM using a user-specified name. A valid name has the following
characteristics:
• Consists of 1–16 characters.

24 IBM Z NetView: Installation: Configuring Graphical Components

 • The first character cannot be numeric.
• The remaining characters can be alphanumeric, or the following special characters: @, #, or $.
• Alphabetic characters must be in uppercase.
RESWS=Y|N
Specifies whether to warm start the resource status. The default is no (N).
SUBSYM=*SUBSYM|*NOSUBSYM
Specifies whether to substitute system symbolics before they are displayed. The &DOMAIN symbolic
that is supplied with the NetView program is also included in the substitution process. Substitution
is always performed on the &DOMAIN symbolic unless substitution is disabled when the NetView
program is started. For MVS and user-defined system symbolics, substitution is not performed if
substitution is disabled when the NetView program is started or you do not define an MVS system
symbolic on your MVS system. *SUBSYM is the default.
ROUTECDE
Specifies the route code to be used for all WTO commands issued by RODM. The default value is 1.

Verifying the GMFHS Installation

To verify that the GMFHS functions are installed correctly, issue the GMFHS STATUS command at the
NetView operator console. This verifies that the GMFHS is installed correctly at the host.
You receive a response similar to the example shown in Figure 3 on page 25.

| NTV6C MVS F C,STATUS

E NTV6C DUI4040I STATUS DISPLAY
E NTV6C DUI4041I RODM CONFIGURATION STATUS = COMPLETE
E NTV6C DUI4042I TYPE = CNMTAMEL STATUS = ACTIVE SESSION = NTV6CHTM
PPIST = OK
E NTV6C DUI4042I TYPE = SCOPT STATUS = ACTIVE SESSION = NTV6CSCO
PPIST = OK
E NTV6C DUI4043I TYPE = RODM STATUS = ACTIVE SESSION = RODMNAME
E NTV6C DUI4037I END

Figure 3. GMFHS Status Command Results

Chapter 3. Preparing and Activating RODM and GMFHS 25

26 IBM Z NetView: Installation: Configuring Graphical Components
Chapter 4. Installing and Configuring the NetView
Management Console for Graphics

The NetView management console consists of topology servers and topology consoles that communicate
with each other, as shown in Figure 4 on page 27.

Figure 4. NetView Management Console Overview

The NetView management console topology server provides information to NetView management console
topology consoles for displaying network topology and status. This information is retrieved from RODM.
The NetView management console server also provides the NetView management console topology
console with a set of tasks applicable to each resource type. It communicates with the NetView program
using either an SNA LU 6.2 (AIX® and Windows only) or TCP/IP session that has been established using
the NetView NETCONV command.
The NetView management console topology console graphically displays network topology and status.
This includes system and network views, using color to show the status of resources. It receives this
configuration and status from the NetView management console topology server and provides command
facilities for managing monitored resources.
Installing and configuring the NetView management console for graphics requires definitions in the
NetView program and the workstation environment.

© Copyright IBM Corp. 2001, 2022 27

NetView Setup for the NetView Management Console
The NetView program communicates with NetView management console servers using either TCP/IP or
SNA LU 6.2.
For TCP/IP communication with the NetView program, TCP/IP must be enabled in the DUIFPMEM
member. The server workstation must be able to ping the NetView host.
For SNA LU 6.2 communication with the NetView program, the workstation PU and independent LUs must
be defined to VTAM in a switched major node. The NetView management console LU 6.2 application must
be defined to VTAM in a cross-domain resource major node. Refer to Appendix A, “SNA Definitions for the
NetView Management Console Topology Servers,” on page 51 for information about the VTAM definitions
required.
Note: SNA LU 6.2 is supported only on the AIX and Windows platform of the topology server.

Defining the Status Focal Point

This section describes how to set up connectivity between the status focal point and the NetView
management console topology server.

CNMSJ009
Ensure that the NetView start procedure CNMSJ009 includes a DD statement for SYSTCPD that specifies
the TCP/IP configuration information data set. This might already have been included when the NetView
program was installed and configured.

CNMSTYLE
If GRAPHICS is specified on the TOWER statement in the CNMSTYLE member, NetView ensures that the
CNMTAMEL task is active. The CNMTAMEL task receives status changes for resources and forwards them
to the NetView management console. You can change the values of the following keywords to meet the
requirements of your network:
TAMEL.CONV.ip_sysdef = ipid
Specifies the IP server with which a NETCONV session is to be started during NetView initialization.
You can specify a port number by appending /portnum to the IP name or address. This is not
necessary if the port number is the same value as that specified by the TAMEL.PORT statement.
TAMEL.CONV.lu_sysdef = SNA
Specifies the SNA server with which a NETCONV session is to be started during NetView initialization.
TAMEL.PORT
Specifies the port used by the status focal point host for TCP/IP communication. This is not a required
keyword. The default is 4020.
Note: The value assigned to the PORT keyword on the NETCONV command overrides the value
assigned to this keyword in the DUIFPMEM member.
TAMEL.SOCKETS
Specifies the maximum number of sockets that the CNMTAMEL task can open simultaneously,
including those sockets used for connections that are started for TCP/IP-based NETCONV commands.
This is not a required keyword. The default is 50.
TAMEL.TCPANAME
Specifies the TCP/IP application procedure name that the status focal point host uses. This is a
required keyword for the TCP/IP function.
TAMEL.TTLS = NONE|ANY|REQUIRE
Specifies if the z/OS Communications Server Application Transparent Transport Layer Security (AT-
TLS) function is used to secure NETCONV TCP/IP sessions. The value specified also indicates if all
NETCONV sessions are required to be secure. The following values can be used:

28 IBM Z NetView: Installation: Configuring Graphical Components

 NONE
Specifies that the z/OS Communications Server AT-TLS function is not to be used to secure any
connections. This is the default value.
ANY
This indicates that the z/OS Communications Server AT-TLS function is to be used to determine if
connections are secure or not. If a secure connection is needed, then a corresponding policy must
be defined in the z/OS Communications Server Policy Agent. The AT-TLS function must be enabled
and the z/OS Communications Server Policy Agent must be configured and active. Connections
that do not have a corresponding policy are not secured.
REQUIRE
This indicates that the z/OS Communications Server AT-TLS function is to be used to secure all
connections. The AT-TLS function must be enabled and the z/OS Communications Server Policy
Agent must be configured and active. Connections that do not have a corresponding policy that
secures the connection are rejected and fail.
Note: If you specify TAMEL.TTLS=ANY or TAMEL.TTLS=REQUIRE, ensure that the AT-TLS function
is enabled on your system. As part of enabling AT-TLS, it is necessary to configure the z/OS
Communications Server Policy Agent (the started task name is PAGENT). A sample configuration for
the z/OS Communications Server Policy Agent is provided in the following path:

/usr/lpp/netview/v6r4/samples

See the znetview_at-tls_readme.txt for instructions on using this sample.

The DUIDGHB task is used to resolve TCP/IP addresses and names including:
• Host names and addresses for establishing IP NETCONV sessions
• Host names for issuing IP RMTCMD commands
• Host names and addresses of host destinations for the NetView Resource Manager
You can change the value of the following keyword to meet the requirements of your network:
GHB.TCPANAME
Specifies the TCP/IP application procedure name that the status focal point host uses. This is a
required keyword for the TCP/IP function.
Note: You can also set the TCP/IP name in the following way:
• As a system symbolic (&CNMTCPN) in SYS1.PARMLIB
• Copy the TCPname statement from the CNMSTYLE member to the CNMSTUSR or CxxSTGEN member,
and update it as necessary. For information about changing CNMSTYLE statements, see IBM Z NetView
Installation: Getting Started.

If you want information about... Refer to...

Keywords IBM Z NetView Administration Reference

DUIISFP
This member defines the initialization values for the CNMTAMEL task. It contains the default values for
each operand.

DUIIGHB
DUIIGHB is the initialization member for the DUIDGHB task.

Security Considerations
Signing on to the NetView management console requires a valid NetView operator ID and password or
password phrase. The NetView program validates the password when the DSIOPF member is used. The

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 29
 SAF program validates the password or password phrase when OPERSEC is set to SAFDEF, SAFPW, or
SAFCHECK.
You can prevent unauthorized users from logging on to the NetView management console by restricting
access to the DUILOGON command used to connect to the NetView management console server. You
can restrict access using either an SAF product or the NetView command authorization table. For more
information, refer to IBM Z NetView Security Reference.

Using NGMFADMN
The NGMFADMN attribute can be used in NetView operator profiles and in the NETVIEW segment of
the SAF product. It specifies whether operators are allowed to perform administrative functions for the
NetView management console. Some examples of functions controlled by this keyword include:
• Using the command profile editor
• Adjusting aggregation for individual resources
• Customizing views
• Customizing settings and applying them to all topology consoles
• Creating custom views and aggregates using the RODM Collection Manager Wizard
NO
The operator does not have administrative authority for the NetView management console. This is the
default.
YES
The operator has administrative authority for the NetView management console.

Using NGMFCMDS
The NGMFCMDS attribute can be used in a NetView operator profile only. It cannot be specified using the
NETVIEW segment of the SAF product. It specifies whether operators are allowed to issue commands
from the popup menus of the NetView management console. NGMFCMDS does not prevent operators
from typing commands in a NetView command line window.
YES
The operator is allowed to issue commands from the popup menus on the NetView management
console. This is the default.
NO
The operator is not allowed to issue commands from the popup menus on the NetView management
console.

Using Spans to Protect Resources and Views

You can use span of control to protect access to particular resources and views. Operators access
resources by:
• Issuing commands
• Opening a NetView management console view
• Selecting a resource in a NetView management console view and performing an action against that
resource
When a resource is accessed, the NetView program verifies the operator's authority to access the span
that contains the resource. This resource protection is in addition to the normal command security
checking. For more information, refer to IBM Z NetView Security Reference.

Workstation Setup for the NetView Management Console

The NetView program can communicate with NetView management console servers using either TCP/IP
or SNA LU 6.2.

30 IBM Z NetView: Installation: Configuring Graphical Components

 Note: SNA LU 6.2 is supported only on the AIX and Windows platform of the NetView management
console server.
After installing the workstation code, it must be configured to enable communication with the host
components of the NetView management console.

Installing and Configuring the NetView Management Console Topology

Server
The NetView management console topology server can be installed on a Windows, AIX, or Linux® for
zSeries system.
To install the NetView management console topology server, refer to the EGVREAD2.ME file on the
product CD or on the Tivoli web site.
After the server is installed, take the following actions:
• If you are using TCP/IP sessions, see “Defining IP Socket Port Numbers for TCP⁄IP” on page 31.
Otherwise see Appendix A, “SNA Definitions for the NetView Management Console Topology Servers,”
on page 51.
• See “Storing Topology Server Databases” on page 32.
• For Windows server users, see “Setting Security for Your Operating System” on page 34 and
“Configuring the Topology Server to Run as a Windows Service” on page 34.
• For AIX and Linux for zSeries server users, see “Configuring the Topology Server to Run as a UNIX
Daemon” on page 34.

Enabling the Topology Display Subsystem View to Show NetView

Components
NetView instrumentation must be enabled to monitor the status of the components that provide NetView
management console views.
The Topology Display Subsystem view shows the status of the components that provide NetView
management console views. To open this view from the Business tree, follow these steps:
1. Click the plus sign next to Business Systems.
2. Double-click Systems Management Business System.
The resulting view shows the topology consoles, topology servers, NETCONV connections, Graphic
Monitor Facility host subsystem (GMFHS), RODM, and the RODM managers. Without NetView
instrumentation, this view shows only one topology server, and the topology consoles signed onto that
server.

If you want information about... Refer to...

Enabling NetView instrumentation (INITAMI, IBM Z NetView Customization Guide
DSIAMII, and DSIAMIAT).

Defining IP Socket Port Numbers for TCP⁄IP

Communication with the NetView environment is achieved through either TCP/IP or LU 6.2 for AIX and
Windows systems (as described in “Defining the Logical Unit (LU) Name” on page 53). The topology
server communicates through TCP/IP with the topology console. The topology server default uses the
following IP socket ports:
• Port 4000 for NetView management console communications
• Port 4020 for NetView communications for the topology server
• Port 4021 for NetView communications for the TBSM server
• Port 48415 for NetView communications using secure sockets layer

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 31
 No action is required if these port numbers do not conflict with your current application settings. However,
if there is a conflict, change the port number or numbers using these instructions:
1. On the topology server workstation, open a command window.
2. Change to one of the following directories:
• For Windows systems: %windir%\system32\drivers\etc
You can display the value of %windir% by entering set windir from a command prompt.
• For UNIX: ⁄etc
3. Add the appropriate entry to the services file. Substitute your port number for the following default
port numbers. These services must each have a unique port number; the same port number cannot be
used for more than one of these services.

tserver_console 4000⁄tcp #Port that NMC server listens for consoles

tserver_390 4020⁄tcp #Port that NMC server listens for NETCONV
tserver_tbsm 4021⁄tcp #Port that TBSM server listens for NETCONV
tserver_390_ssl 48415/tcp #Port used for SSL

Notes:
1. If you reassign the topology server console port, specify the port number on the topology console
Sign On window each time you sign on. However, the topology console retains the server:port setting
from the last signon (either ipv4address:port or [ipv6address]:port) and uses it to complete the Host
Machine field of the topology console Sign On window.
2. If you reassign the topology server 390 port, also customize the CNMSTYLE PORT statement in
the CNMSTUSR or CxxSTGEN member. See the IBM Z NetView Administration Reference for more
information about the PORT statement.
3. You do not need to reboot the workstation to activate the new PORT value.

Storing Topology Server Databases

Depending on your operating system, the topology server uses one of the following directories to store its
databases:
• For Windows: %BINDIR%\TDS\server\db
• For UNIX: $BINDIR⁄TDS⁄server⁄db
Notes:
1. If you are running the NetView management console in the Japanese AIX environment, the default
locale is shift JIS with a locale value of Ja_JP.
The EUC locale (ja_JP) is also supported. If you have configured your system on either locale and
decide to change locales, you must convert the databases to the new locale. The JA_JP locale is not
supported. Several database samples are provided to assist you if you want to change locales. The
following shell scripts are provided:
• convert_ja_JP_databases.sh converts the databases from the Ja_JP to the ja_JP locale and
preserves your databases.
• convert_Ja_JP_databases.sh converts the databases from the ja_JP to the Ja_JP locale and
preserves your databases.
• setup_ja_JP_databases.sh creates databases with the ja_JP locale and deletes any existing
databases.
• setup_Ja_JP_databases.sh creates databases with the Ja_JP locale and deletes any existing
databases.
2. If your NetView management console topology server and NetView management console topology
console do not have identical locales, then some text on the topology console can seem corrupted.
Also, the log file created by the Save Log to Server function can seem corrupted.
The following locales are supported by the NetView management console topology server:

32 IBM Z NetView: Installation: Configuring Graphical Components

 • For Windows systems: Shift-JIS (code page 932)
• For AIX systems: Shift-JIS (Ja_JP) and EUC (ja_JP)
• For Linux for zSeries systems: Shift-JIS (ja_jp.sjis) and EUC (ja_jp.eucjp)
The following locales are supported by the NetView management console topology console:
• For Windows systems: Shift-JIS (code page 932)
• For Linux for zSeries systems: Shift-JIS (ja_jp.sjis) and EUC (ja_jp.eucjp)
To avoid problems with corrupted text, use servers and consoles that run with the same locale
settings.
No action is required if these directory locations are satisfactory. However, to use a different directory or
disk for your databases, perform the following steps to change the directory structure:
1. Update the TSERVER_DB environment variable.
• Windows systems: Set the TSERVER_DB environment variable at the user ID level using the
following steps:
a. Log on to the ID where the topology server is running.
b. Right-click the My Computer icon.
c. Select Properties from the resulting pull-down window.
d. Select the Advanced tab on the System Properties panel.
e. Click the Environment Variables... button on the System Properties panel.
The Environment Variables panel displays.
f. Click New... in the User Variables for Administrators section of the Environment Variables panel.
The New User Variable panel displays.
g. Type TSERVER_DB in the Variable Name text field.
h. In the Variable Value field, type the name of the new directory where you want the topology
server databases to reside.
i. Click OK.
j. Click OK.
k. Click OK.
• UNIX systems: Update the TSERVER_DB environment variable in the appropriate profile.
2. Under your new directory, create the same directory structure as the one that is presently under one of
the following:
• For Windows systems: %BINDIR%\TDS\server\db
• For UNIX systems: $BINDIR⁄TDS⁄server⁄db
3. Ensure that the topology server is stopped.
4. Run the tserver dbtransfer command. This copies the contents of the databases from the
default installation subdirectories to the subdirectories set by the TSERVER_DB variable. The tserver
dbtransfer command prompts you for a confirmation before overwriting files in each subdirectory.
Notes:
a. When the server is started for the first time and it detects the TSERVER_DB environment variable,
but the command tserver dbtransfer was not run, the server shuts down and you receive a
message to run tserver dbtransfer.
b. The tserver dbtransfer command does not erase or overwrite the files in the default
installation database subdirectories.

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 33
 Setting Security for Your Operating System
If you are using a Windows system, additional security configuration steps are required. No additional
security configuration is required for UNIX platforms.
For a Windows system, add the following user rights to the user ID under which the topology server runs
so that it performs in the following ways:
• Acts as part of the operating system.
• Logs on as a service.
This is optional and needs to be set only if the topology server is run as a service. See “Configuring the
Topology Server to Run as a Windows Service” on page 34 for instructions.
Follow these instructions to set user rights for Windows systems:
1. Log on to an ID with administrator authority.
2. Click Start > Settings > Control Panel > Administrative Tools > Local Security Policy > Local
Policies > User Rights Assignment.
3. Click Act as part of the operating system
4. Click Action > Properties > Add User or Group.
5. Select the target user ID under which the topology server is to run by typing the name in the Enter the
object names to select field. Then click OK.
If you do not know the exact target user ID, click Advanced > Find Now to see a list of user IDs in the
name (RDN) panel.
Note: To filter or add other object types, click Object Types, select the applicable check boxes, and
click OK. Then, click Advanced.
6. Click OK on each window that you opened to close and save your selection.
7. Log off and log back on to the target ID for the user rights to take effect.

Configuring the Topology Server to Run as a Windows Service

To run the topology server as a Windows service, perform the following steps:
1. On the topology server workstation, open a workstation command window.
2. Change to the following directory: %BINDIR%\TDS\server\bin.
3. Enter the following command to install the topology server as a Windows service:

tserver service account_name password

Where:
account_name
An account name in the form DomainName\UserName. If the account belongs to the local domain,
you can specify .\UserName.
password
The corresponding password or password phrase for the specified account name.
The topology server installs as two services: the topology server and the topology communications
server, and the startup option will be manual.
4. To change the startup to automatic, use the Windows Services control applet.
5. To delete the services, enter the ihsxsrv delete command from the same directory.

Configuring the Topology Server to Run as a UNIX Daemon

For UNIX, to start the topology server processes at system startup and have them run as daemons, issue
the following command:

34 IBM Z NetView: Installation: Configuring Graphical Components

 $BINDIR⁄TDS⁄server⁄bin⁄tsersver⁄config -d

The processes start the next time the system is booted.

Note: You must be the root user to issue this command.

Installing the NetView Management Console Topology Console

The NetView management console topology console requires TCP/IP communication capability. Do not
run the NetView management console topology server and topology console code on the same system in
a production environment.
For information about installing the NetView management console topology console, refer to the
EGVREAD1.ME file on the product CD.

Verifying the NetView Management Console Installation

To verify the NetView management console installation, start the NetView management console topology
server and then start a NetView management console topology console as described in the following
sections.

Starting the Topology Server

You can start the topology server in the following ways:
• Manually
• As a daemon when using a UNIX system
• As a Windows service when using a Windows system
Note: This task is usually completed by a system administrator for all topology console operators. For
specific information, refer to the IBM Z NetView User's Guide: NetView Management Console.

Begin Communication with the NetView Management Console Topology

Server
If communication between the NetView management console topology server and the NetView program
is not active, you can issue the NETCONV command to start the communication. Normally this
communication is defined to start automatically during NetView initialization. To start communication
using TCP/IP, that was defined to start automatically but is not currently active, enter:

NETCONV STARTCON=ip_sysdef

To start communication using SNA, that was defined to start automatically but is not currently active,
enter

NETCONV STARTCON=lu_sysdef

These NETCONV commands cause the connection to be established under the autotask defined by the
function.autotask.NetConv statement in the CNMSTYLE member.
If you have not defined communication to start automatically, you can use the NETCONV command
with the ACTION=START keyword or with the STARTCON=ip_sysdef / lu_sysdef keyword to start
communication under the task issuing the NETCONV command.
Note: If the task under which communication is established ends for any reason, the connection is
broken. This is true for both the autotask specified in the CNMSTYLE member or the task under which the
NETCONV command (with ACTION=START or STARTCON=ip_sysdef / lu_sysdef ) was issued.
For more information about the NETCONV command, refer to the IBM Z NetView Command Reference
Volume 1 (A-N).

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 35
Starting the Topology Console
You can start the topology console from a desktop icon in Windows or by issuing the command in line
mode. For specific information, refer to the IBM Z NetView User's Guide: NetView Management Console.

Signing On to the NetView Management Console Topology Console

Sign on to the NetView management console topology console and do the following:
• Connect to the topology server
• Display views

If you want information about... Refer to...

Signing on and using the NetView management IBM Z NetView User's Guide: NetView Management
console topology workstation Console
Online help NetView management console topology console
help index

Customizing the NetView Management Console

You can customize the NetView management console for your environment. You can add or change the
following:
• Topology console icons
• Topology console views
This can include creating views and aggregate resources (RODM Collection Manager), changing the
background image, and moving resources and text labels.
• Topology console help
• Server.properties configuration file for the topology server
• Time and date format
You can also use plug-ins and Java™ applications for additional customization.

If you want information about... Refer to...

Customizing the NetView management console IBM Z NetView User's Guide: NetView Management
Console
Java applications and plug-ins IBM Z NetView User's Guide: NetView Management
Console

36 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 5. Preparing and Activating the NetView
Resource Manager

This chapter addresses the following technical considerations:

• “Defining the NetView Resource Manager Autotask” on page 37
• “Security Considerations” on page 37
• “Initialization Considerations” on page 39
• “Starting the NetView Resource Manager” on page 40
• “Verifying the NetView Resource Manager Installation” on page 40

Defining the NetView Resource Manager Autotask

AUTONRM is the autotask used by the NetView Resource Manager for processing. This is defined, in the
following way, in DSIOPF:

AUTONRM OPERATOR PASSWORD=AUTONRM

PROFILEN DSIPROFC

If you modify the DSIOPF member, either restart the NetView program or issue the REFRESH OPERS
command from the NetView command line to activate the changes.
You can specify a different autotask to use for NetView Resource Manager processing by copying the
following CNMSTYLE statement to the CNMSTUSR or CxxSTGEN member and updating the statement:

function.autotask.NRM=AUTONRM

This autotask must be defined in the DSIOPF member. For information about changing CNMSTYLE
statements, see IBM Z NetView Installation: Getting Started.
Note: The autotask that is used for NetView Resource Manger must have as little other activity as
possible; otherwise, NetView Resource Manager processing can be impacted.

Security Considerations
Consider the following aspects of security for NetView Resource Manager:
• “RODM Access” on page 37
• “Command Authorization” on page 38

RODM Access
You can add to your network security by authorizing access to RODM.
By defining the RODM user application ID to an SAF product, such as RACF, you can verify security levels
for API calls into RODM. For example, with a security level of 3, you can connect, disconnect, query,
create objects, delete objects, change fields, and so on. It prevents you from activities that include (but
are not limited to): creating classes and fields, deleting classes and fields.
Add the RODM user application ID (for NetView Resource Manager) to RACF or other security system
with a security level of 3. The RODM user application ID for NetView Resource Manager is your NetView
domain ID concatenated with the letters NetView Resource Manager (for example, CNM01NRM).
Note: Authorizing access to RODM is necessary only for manager hosts.

© Copyright IBM Corp. 2001, 2022 37

 If you want information about... Refer to...
Using RACF for RODM security “Using RACF for RODM Security” on page 10

Command Authorization
The command definitions in CNMCMD (%INCLUDE member CNMCMENT) define the NetView Resource
Manager command procedures.

CMDDEF.CNME8600.MOD=DSICCP
CMDDEF.CNME8600.TYPE=R
CMDDEF.CNME8600.RES=Y
CMDDEF.CNME8600.ECHO=N
CMDDEF.CNME8601.MOD=DSICCP
CMDDEF.CNME8601.TYPE=R
CMDDEF.CNME8601.RES=Y
CMDDEF.CNME8601.CMDSYN=INITNRM
CMDDEF.CNME8602.MOD=DSICCP
CMDDEF.CNME8602.TYPE=R
CMDDEF.CNME8602.RES=Y
CMDDEF.CNME8602.CMDSYN=SUSPNRM
CMDDEF.CNME8604.MOD=DSICCP
CMDDEF.CNME8604.TYPE=R
CMDDEF.CNME8604.RES=Y
CMDDEF.CNME8604.ECHO=N
CMDDEF.NRMCTL.MOD=DSINRCTL
CMDDEF.NRMCTL.TYPE=R

If you modify the member CNMCMD or any of the members included by CNMCMD, use the ADDCMD
command to dynamically add the command without restarting the NetView program. The command
definition remains in effect until you restart the NetView program.
To implement command authorization checking:
1. Restrict the use of NetView Resource Manager commands to specific operators by modifying the
command authorizations of NetView Resource Manager commands as described in theIBM Z NetView
Security Reference.
The command definition statements that specify MOD=DSICCP represent REXX command lists.
NetView command authorization checking for REXX command lists does not apply to keyword and
keyword values.
Note: The CNME8600 sample runs on the NetView Resource Manager autotask, as specified by the
function.autotask.NRM statement in the CNMSTYLE member.
2. Ensure that the SOCKET command can be issued by the same operators who can issue INITNRM and
SUSPNRM commands.
3. Ensure that the SOCKET command can be issued by the NetView Resource Manager autotask.
4. You can have command authorization performed on the keywords and values of the NRMCTL
command.
5. NetView Resource Manager uses FLCARODM. You can have command authorization performed on the
keywords and values of the FLCARODM command.
6. Commands are available on the NetView management console for all NetView Resource Manager
objects. Some of these commands are protected by the default security (CNMSCAT2 or CNMSAF2)
of the NetView program. Refer to the IBM Z NetView Resource Object Data Manager and GMFHS
Programmer's Guide for more information about the commands that are available for NetView
Resource Manager objects. This book also identifies which of these commands are protected.
If you want to enable the protected commands to be issued for the local domain, authorize
the NetView operators to log on to the NetView management console client for the appropriate
commands. If you want to enable the protected commands to be issued for a remote domain,
then authorize the NetView Resource Manager autotask, on the remote domain, for the appropriate
commands.

38 IBM Z NetView: Installation: Configuring Graphical Components

 All other commands for NetView Resource Manager objects are not protected by the default security of
the NetView program. You can protect or authorize those commands with your installation.

If you want information about... Refer to...

Command authorization IBM Z NetView Security Reference

Initialization Considerations
You can start the NetView Resource Manager at NetView initialization by copying the INIT.NRM statement
from the CNMSTYLE member to the CNMSTUSR or CxxSTGEN member, and specifying INIT.NRM = Yes.
For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
You can also start the NetView Resource Manager at a later time by issuing the INITNRM command.
Note: Before starting the NetView Resource Manager, review the initialization parameters in the
CNMSTYLE member, and customize them as necessary in the CNMSTUSR or CxxSTGEN member.
You can override all parameters except the DISPLAY STATUS values on the INITNRM command.
After customizing CNMSTYLE statements, use the RESTYLE NRM command to stop the NetView Resource
Manager and restart it.

Sampling
NetView Resource Manager detects RODM failures when an NetView Resource Manager request fails.
NetView Resource Manager continues trying to connect to RODM until either a connection is established
or the NetView Resource Manager is shut down.
When the connection is reestablished, it requests status from all the agents NetView Resource Manager
was monitoring at the time of the failure.
You might want to specify a value for sampling in order for the NetView Resource Manager to detect
RODM failures, especially if the status of your NetView Resource Manager objects does not change very
often.
If you want sampling to occur, either modify the NRM.SAMPLERATE statement in the CNMSTUSR or
CxxSTGEN, or specify the SAMPLE keyword on the INITNRM command. For information about changing
CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.

Display Status Defaults

NetView Resource Manager uses the following DisplayStatus values for its real objects:

Active Satisfactory
Inactive Unknown
Unknown Unknown
Threshold 1 met or exceeded Intermediate
Threshold 2 met or exceeded Medium Unsatisfactory
Threshold 3 met or exceeded Unsatisfactory
RESET Unknown

Monitoring Remote NetView Systems

To monitor a remote NetView system, perform the following steps:
1. Code a HOSTDEST parameter at the remote system.
Note: For the following reasons, do not code multiple HOSTDEST parameters for the same destination
host (For example, an SNA HOSTDEST for CNM01, and an IP HOSTDEST for CNM01).
• Coding multiple HOSTDEST parameters for the same target host causes unpredictable behavior.
• NetView Resource Manager does not support backup host destinations.

Chapter 5. Preparing and Activating the NetView Resource Manager 39

 2. If you code HOSTDEST statements, you must also code the CMODE and PORT parameters, if
applicable. Examples are provided in the CNMSTYLE member.
The DUIDGHB task is required for any IP HOSTDEST that uses a host name instead of an IP address.
3. Activate other NetView functions that are required to monitor remote NetView programs:
• The manager that is receiving remote host data uses the following functions:
– RMTCMD
– Hardware Monitor
– LU 6.2 transport
– TCP/IP Alert Receiver (if your communication method is TCP/IP)
• The agent sending its data to a manager uses the following functions:
– LU 6.2 transport (if your communication method is SNA)
– TCP/IP (if your communication method is IP)
– RMTCMD
Note: The agent can be a NetView host with NRM.TYPE=MGR. It is the agent function that uses the
previously listed items.

RMTCMD Considerations
NetView Resource Manager uses the RMTCMD command to communicate between NetView hosts.
Ensure that RMTCMD capability exists for each mode of communication (SNA, IP, or IPV6) to be used for
transporting data between managers and agents. For example, if an agent is reporting to a manager using
IP or IPV6, TCP/IP-based remote operations must be enabled at the agent and manager hosts.

IPv6 Networking Considerations

An agent reports its IP address to a manager. When the IP (IPv4) communication mode is used, the IP
address is obtained using the z/OS Communications Server EZASMI macro with TYPE=GETHOSTID. There
is not an exact equivalent method for obtaining an IPv6 address when the IPV6 communication mode is
used.
The NRM.IPV6SRC CNMSTYLE statement or the IPV6SRC keyword of the INITNRM command can be used
to provide either an IPv6 address or a host name that the NetView Resource Manager can resolve to an
IPv6 address to be reported to the manager. If IPV6SRC information is not provided, the agent attempts
to obtain a host name that is defined for the TCP/IP stack with which affinity was obtained, and if present,
attempts to resolve it to an IPv6 address to be reported to the manager. If an IPv6 address cannot be
determined and associated with the NetView Resource Manager agent, the agent does not contact the
managers for which the IPV6 communication mode is being used.

Starting the NetView Resource Manager

To start the NetView Resource Manager, specify INIT.NRM = Yes in the CNMSTUSR or CxxSTGEN member,
or issue the INITNRM command. For information about changing CNMSTYLE statements, see IBM Z
NetView Installation: Getting Started.
If you issue the INITNRM command with no parameters, the parameter values in the CNMSTYLE member
are used to initialize the Resource Manager.

Verifying the NetView Resource Manager Installation

After the NetView Resource Manager is active, you can issue NRMCTL LISTPARM to verify your
initialization parameters.
You can verify domains that are being monitored from a manager host with the NRMCTL LISTMON
command.

40 IBM Z NetView: Installation: Configuring Graphical Components

Access the NetView Resource Manager view (from the NetView management console) to verify that RODM
has been populated correctly. From the NetView management console tree view, select NetViewTasks.
This opens a view of the NetView Resource Manager domain aggregate objects and verifies that NetView
Resource Manager data has been stored in RODM. You can right-click this object and select commands to
run.
You can then navigate from the NetView Resource Manager domain aggregate object to the NetView
Resource Manager task aggregate objects.
From the NetView Resource Manager task aggregate objects, you can navigate to the NetView Resource
Manager real statistical objects.
Commands are available at both of these levels.

If you want information about... Refer to...

INITNRM command NetView online help
NRMCTL command NetView online help
RESTYLE command NetView online help

Chapter 5. Preparing and Activating the NetView Resource Manager 41

42 IBM Z NetView: Installation: Configuring Graphical Components
Chapter 6. Preparing and Activating the Discovery
Manager

This chapter addresses the following technical considerations:

• “Security Considerations” on page 43
• “Initialization and Operational Considerations” on page 44

Security Considerations
Consider the following aspects of security for the discovery manager:
• “RODM Access” on page 43
• “Command Authorization” on page 43

RODM Access
You can add to your network security by authorizing access to RODM.
By defining the RODM user application ID to an SAF product, such as RACF, you can verify security levels
for API calls into RODM. For example, with a security level of 3, you can connect, disconnect, query,
create objects, delete objects, change fields, and so on. It prevents you from actions that include (but are
not limited to) creating and deleting classes and fields.
Add the RODM user application ID (for the discovery manager) to RACF or other security system with a
security level of 3. The RODM user application ID for the discovery manager is your NetView domain ID
concatenated with the letters MSM (for example, CNM01MSM).
Note: Authorizing access to RODM is necessary only for manager hosts.

If you want information about... Refer to...

Using RACF for RODM security “Using RACF for RODM Security” on page 10

Command Authorization
The command definitions in CNMCMD (%INCLUDE member CNMCMENT) define discovery manager
command procedures.

CMDDEF.CNMEERSC.MOD=DSICCP

If you modify the CNMCMD member or any of the members included by CNMCMD, use the ADDCMD
command to dynamically add the command without restarting the NetView program. The command
definition remains in effect until you restart the NetView program.
To implement command authorization checking:
1. Restrict the use of the discovery manager command to specific operators by modifying the command
authorizations of the discovery manager command as described in theIBM Z NetView Security
Reference.
The command definition statements that specify MOD=DSICCP represent REXX command lists.
NetView command authorization checking for REXX command lists does not apply to keyword and
keyword values.
2. The discovery manager uses the FLCARODM command. You can have command authorization
performed on the keywords and values of the FLCARODM command.

© Copyright IBM Corp. 2001, 2022 43

 3. Commands are available on the NetView management console for some discovery manager objects.
Some of these commands are protected by the default security (the CNMSCAT2 or CNMSAF2 sample)
of the NetView program. Refer to the IBM Z NetView Resource Object Data Manager and GMFHS
Programmer's Guide for more information about the commands that are available for discovery
manager objects. This book also identifies which of these commands are protected.
If you want to enable the protected commands to be issued for the local domain, authorize
the NetView operators to log on to the NetView management console client for the appropriate
commands.
All other commands for discovery manager objects are not protected by the default security of the
NetView program. You can protect or authorize those commands with your installation.

If you want information about... Refer to...

Command authorization IBM Z NetView Security Reference

Initialization and Operational Considerations

For information about enabling the discovery manager, see IBM Z NetView Installation: Configuring
Additional Components.
For information about managing resources that are discovered by discovery manager, see IBM Z NetView
IP Management.

44 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 7. Managing Views

As discovery manager gathers network topology information, they store that information in RODM.
By default, this information is presented by the NetView management console in a top-down, hierarchical
perspective. You can change these default views in the NetView management console to accomplish the
following goals:
• Meet the needs of your organization
• Customize the graphical representation of your network
Access to the list of views, including access to individual objects within those views, can be granted on a
per-operator basis.

Types of Views
A NetView management console operator can view the following types of views:
• Network views
• Exception views
Network views are created by gathering topology and status from topology agents or by using tools,
such as the RODM collection manager (from the NetView management console) or BLDVIEWS. Network
views are capable of displaying objects as they relate to other objects, by showing relationships or links
between them.
The current state of each device within the view is represented by a color scheme. The default colors are
green for satisfactory status and red for unsatisfactory status.
Note: You can change the default status (which affects the color) for real objects that are created by
the MultiSystem Manager IBM Tivoli NetView Manager agent and that do not have any outstanding
events. You can do that by using the COMMON.FLC_DEFAULT_ITNM_OBJECT_STATUS statement; for
more information about this statement, see the IBM Z NetView Administration Reference.
Exception views are special types of views which show objects that are in an exception state and that
might require operator attention.
For example, as a network device becomes inoperable, its state might change from satisfactory to
unsatisfactory. If an exception view is defined to display this type of device, an object representing that
device appears within this exception view, alerting an operator about the unsatisfactory state. When the
device becomes operable again, it disappears from the exception view.
Because the RODM collection manager is capable of creating views that actively track changes in RODM,
you can use the RODM collection manager to create a network view with characteristics that are similar
to an exception view. For example, you can create a RODM collection that specifies all IP Routers that are
not in satisfactory state; this becomes a network view that resembles the functionality of an exception
view.
Exception views and RODM collection manager views with similar characteristics have a few differences
that might make one a more appropriate choice than the other in a given situation.
• Advantages of exception views:
– Exception views use less CPU resource on the host system.
They are only created and maintained when a NetView management console user has an exception
view open.
– Exception views can be opened at the NetView management console by default in Details mode while
network views are still opened by default in Topology mode.
• Advantages of RODM collection manager views with similar characteristics:

© Copyright IBM Corp. 2001, 2022 45

 – RODM collection manager views are easier to define and maintain than exception views.
– The status that constitutes an exception can easily be defined on an object-by-object basis.
– RODM collection manager views provide more flexible options. For example, more criteria (than just
status) can be applied.
– When two objects in a RODM collection manager view are connected, that connection is displayed.
These two view types appear as expandable branches of the view tree in the NetView management
console:

Figure 5. Collapsed View Tree

When the operator clicks the plus sign, the tree is expanded to show the available views:

Figure 6. Expanded View Tree

The operator can then double-click a selection to open the view.

Restricting Access to Views

If necessary, operator access can be restricted to the following items:
• Views
• Individual resources within views
This is done using span of control.
To implement span of control, use the following items:
• NGMFVSPN attribute to specify if operators are to be subject to span checking
• NetView span table to define views and resources within views to spans
• CTL attribute to specify that span checking is to be done for an operator

If you want information about... Refer to...

Using spans to protect resources and views IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide and IBM Z NetView
Security Reference

46 IBM Z NetView: Installation: Configuring Graphical Components

Applying Policy to Views
Using NMCSTATUS policy definitions, you can define time schedules for resources in NetView
management console views. With these schedules, policy can be applied to views to specify when:
• The status for one or more resources in a view is disabled at the NetView management console
• One or more resources in a view is suspended from aggregation

If you want information about... Refer to...

Creating and loading a policy file containing IBM Z NetView Administration Reference
NMCSTATUS policy definitions

Correlating Views
The NetView program uses topology correlation to automatically tie together resources managed by
different types of topology agents. Topology correlation is provided for all discovery manager and
customer or vendor applications that use the GMFHS data model.
Most managed resources participate in more than one network or system. For example, an IP stack that is
managed through sysplex management can have a presence in the IP environment and in a z/OS system.
Most management agents recognize only one type of network or system, as opposed to every resource
running in the system. For example, the IBM Tivoli Network Manager agent recognizes resources with IP
addresses. Therefore, an IP view of the example IP stack contains information related to IP, but not the
z/OS system.
Topology correlation overcomes the agent-specific perspective of management agents and enables a
graphic monitor view to contain all components of a network device. This single view includes the current
status of all components.
Object correlation is enabled by loading the FLCSDM8 input file into RODM. To load FLCSDM8, uncomment
the following line in the CNMSJH12 job:

//* DD DSN=NETVIEW.V6R4M0.CNMSAMP(FLCSDM8),DISP=SHR <-CORRELATE SAMPL

Correlation occurs when an application sets a valid value in a field of a RODM object that is enabled for
correlation. Objects are enabled for correlation by loading the FLCSDM8 file.
MultiSystem Manager automatically set the value of these fields, which results in correlation.
Views are displayed on a NetView management console.

If you want information about... Refer to...

Correlating views IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide

Enabling Object Correlation for GMFHS Resources

If you have GMFHS resources that do not correlate to any IP resources, this indicates that the
management agent did not discover a MAC address or IP address that can be used for correlation.
If you know that some of these resources do participate in IP networks and if you have the MAC
addresses and IP addresses for those resources, you can include them in correlation. You do this by
setting those address values in the managed objects in RODM.
To set these values, you can write a NetView CLIST that uses MultiSystem Manager access through
RODMVIEW.

Chapter 7. Managing Views 47

 If you want information about... Refer to...
Correlation IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide

Tools for Managing Views

This section describes the following tools that you can use to manage RODM views:
• “RODMVIEW” on page 48
• “RODM Unloader” on page 48
• “FLCARODM” on page 48
• “RODM Collection Manager” on page 48
• “BLDVIEWS” on page 49
• “DELVIEWS” on page 50

RODMVIEW
RODMVIEW is a menu-driven tool that you can use to display and manipulate RODM objects from the
NetView command facility. It requires knowledge of GMFHS and other data models. It does not require a
separate workstation installation.

If you want information about... Refer to...

RODMVIEW IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide

RODM Unloader
As data is dynamically added to RODM, you might want to periodically use the RODM Unloader to create
text files that represent the current contents of RODM. This is a slightly different archival method than
checkpointing. A checkpoint data set is a binary representation of the current contents of RODM, which
can be used to restart RODM. The RODM Unloader utility takes the contents of RODM and creates RODM
Loader language statements that can be reloaded later.

If you want information about... Refer to...

RODM unloader utility IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide

FLCARODM
FLCARODM (RODM Access Facility) provides a fast and efficient REXX interface to RODM. (FLCARODM was
formerly known as the RODM Access Facility or MultiSystem Manager Access.) With FLCARODM, you can
create, update, and delete objects using a NetView CLIST written in REXX. FLCARODM provides a simple
interface to RODM and you can use it to exploit the processing advantages of issuing batched requests to
RODM.IBM Z NetView Resource Object Data Manager and GMFHS Programmer's Guide

If you want information about... Refer to...

FLCARODM IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide

RODM Collection Manager

The RODM collection manager actively manages the contents of views based on criteria set by the user.
These criteria can be a naming convention, a set of statuses, or both. A view managed by the RODM
collection manager can have characteristics of both network and exception views. NetView management

48 IBM Z NetView: Installation: Configuring Graphical Components

 console administrators have access to the RODM collection manager on their desktops. You can also
manage views with complex criteria beyond names and statuses.

If you want information about... Refer to...

RODM collection manager NetView management console online help or to the
IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide.

BLDVIEWS
BLDVIEWS can gather a set of objects based on a naming convention. You can use BLDVIEWS to:
• Create either a network or an exception view out of that set of objects.
• Manipulate a field on that set of objects.
BLDVIEWS is controlled by an input file.
Network views created by BLDVIEWS are snapshots in time. As network topology changes occur, it might
be necessary to recreate the views by rerunning BLDVIEWS. For this reason, it is advisable to migrate
BLDVIEWS-based views to RODM collection manager views. The FLCV2RCM command can be used to do
this.
For more information about FLCV2RCM, see NetView online help.
BLDVIEWS can also be used to:
• Create aggregate objects
• Link and unlink objects to and from views and aggregates
Views or aggregates can be grouped by:
• Networks
• Regions
• Locations
• Sites
• Plants
• Buildings
• Floors
• Individual operator responsibilities
You can set or change fields such as DisplayResourceOtherData.
Using the GMFHS data model, you can create objects in these classes:
• Various view object classes
• GMFHS_Aggregate_Objects_Class
• GMFHS_Managed_Real_Objects_Class
You cannot use BLDVIEWS to delete objects, classes, or fields, but you can modify certain fields of
objects.
Views and aggregates created by BLDVIEWS are static. Only the objects that are in RODM at the time you
run BLDVIEWS are processed. If new objects are added to RODM, you must rerun BLDVIEWS. BLDVIEWS
changes to the RODM data cache are not part of any RODM loader file and are lost if RODM is cold-started.
Views that are created with BLDVIEWS might need to be recreated because they can become out-of-date
as system and network resources change.
You can use BLDVIEWS to enable generic command support (for example activate and deactivate)
from the NetView management console on MultiSystem Manager-discovered network resource objects.

Chapter 7. Managing Views 49

 BLDVIEWS provides a way to map a default set of commands to these generic commands for key
MultiSystem Manager resources.

If you want information about... Refer to...

BLDVIEWS IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide

DELVIEWS
You can use DELVIEWS to delete the following customized views from RODM:
• Network views
• Configuration peer views
• Configuration backbone views
• Exception views
For example, to delete a specific exception view (NET_EX_VIEW), type:

DELVIEWS NETA_EX_VIEW TYPE=EXCP

You can also use an asterisk (*) as a wild card at the end of a view name. For example, to delete all
network views with names starting with LAN, enter:

DELVIEWS LAN*

An optional parameter is RODM=rodmname. This is not necessary if MultiSystem Manager is initialized

and connected to RODM.

50 IBM Z NetView: Installation: Configuring Graphical Components

Appendix A. SNA Definitions for the NetView
Management Console Topology Servers

To establish LU 6.2 connectivity between your host and the NetView management console topology
servers, define the workstation-to-host connections in your VTAM and NCP definitions. You can define
your workstation connections to the host using any type of connection that allows parallel LU 6.2
conversion.
Note: LU 6.2 connectivity is available only on the AIX and Windows platform of the NetView management
console topology server.

Ethernet LAN-Attached NetView Management Console Servers

To define NetView management console topology servers to an Ethernet LAN, add definitions for NCP
and VTAM. In the NCP generation, where the Ethernet is attached, define a GROUP set that defines the
physical Ethernet adapter.
For the details of the parameters in the following example, see NCP, SSP, and EP Resource Definition Guide
and the NCP, SSP, and EP Resource Definition Reference:

A03ETH GROUP ETHERNET=PHYSICAL, X

DIAL=NO, X
ISTATUS=ACTIVE, X
LNCTL=SDLC, X
VIRTUAL=NO
A03E170 LINE ADDRESS=(1070,FULL), X
ANS=CONT, X
FRAMECNT=(100000,5000), X
INTFACE=ETH2, X
LANTYPE=DYNAMIC
A03P170 PU ANS=CONT, X
ARPTAB=(2000,20), X
INNPORT=YES, X
PUTYPE=1
IPLOCAL LADDR=96.0.0.99, X
INTFACE=ETH2, X
METRIC=1, X
PROTOCOL=RIP

Because LAN-attached workstations appear as switched nodes to VTAM, they must be defined in a
switched major node. In the following example, the LOCADDR=00 LU is the independent LU that the
NetView management console topology server uses. The four other LUs are the dependent LUs that are
used as the 3270 emulation screens.
Note: The LU names that you specify here must also be specified when you define the NetView
management console topology server profile configurations.
For information about the following example, see the z/OS Communications Server library:

A03LETH VBUILD TYPE=SWNET,MAXGRP=25,MAXNO=25

A03L021 PU ADDR=01,IDBLK=05D,IDNUM=00001,MAXPATH=0,IRETRY=NO, X
MAXDATA=256,PUTYPE=2,DISCNT=NO,ISTATUS=ACTIVE, X
MAXOUT=7,PASSLIM=7
A03L0210 LU LOCADDR=00,DLOGMOD=DSIL6MOD,MODETAB=AMODETAB
A03L0212 LU LOCADDR=02,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB
A03L0213 LU LOCADDR=03,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB
A03L0214 LU LOCADDR=04,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB
A03L0215 LU LOCADDR=05,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB

Because the server workstation uses LU 6.2 parallel session support, you must update the ADDSESS,
MAXSESS, and AUXADDR keywords specified on the build macro to support this configuration.
To update these keywords, perform the following tasks:
1. Verify that you specified the correct keywords and values on the LUDRPOOL macro.

© Copyright IBM Corp. 2001, 2022 51

 2. If you already modified these keywords, verify that you defined them correctly for the configuration
you are defining.
3. Perform the changes to these keywords on every NCP that has a server workstation.
.

Token-Ring LAN-Attached NetView Management Console Servers

To define NetView management console topology servers to a token-ring local area network (LAN), add
definitions for NCP and VTAM. In the NCP generation, where the token ring is attached, define two GROUP
sets. The first GROUP set defines the physical NTRI connection. The second GROUP defines the logical
switched lines that are mapped onto the ring. The AUTOGEN parameter defines the number of lines
created. There must be at least one line for each workstation.
For the details of the parameters in the following example, see NCP, SSP, and EP Resource Definition Guide
and the NCP, SSP, and EP Resource Definition Reference:

N3PGRP1 GROUP ECLTYPE=(PHYSICAL,PER), X

USSTAB=AUSSTAB, X
ANS=CONTINUE, X
ISTATUS=ACTIVE, X
XID=NO
N3N1088 LINE ADDRESS=(1088,FULL), X
PORTADD=1, X
LOCADD=400000311088
N3P8821 PU MAXOUT=7
N3881D0 LU ISTATUS=INACTIVE
*
*
*
N3BNNG1 GROUP ECLTYPE=LOGICAL, X
AUTOGEN=32, X
CALL=INOUT, X
MODETAB=AMODETAB, X
USSTAB=AUSSTAB, X
ANS=CONTINUE, X
PHYPORT=1, X
ISTATUS=ACTIVE, X
XMITDLY=NONE

Because LAN-attached workstations appear as switched nodes to VTAM, they must be defined in a
switched major node. In the following example, the LOCADDR=00 LU is the independent LU that the
NetView management console topology server uses. The four other LUs are the dependent LUs that are
used as the 3270 emulation screens.
Note: The LU names that you specify here must also be specified when you define the NetView
management console topology server profile configurations.
For information about the following example, see the z/OS Communications Server library:

N3LNTRI VBUILD TYPE=SWNET,MAXGRP=25,MAXNO=25

N3L021 PU ADDR=01,IDBLK=05D,IDNUM=00001,MAXPATH=0,IRETRY=NO, X
MAXDATA=256,PUTYPE=2,DISCNT=NO,ISTATUS=ACTIVE, X
MAXOUT=7,PASSLIM=7
N3L0210 LU LOCADDR=00,DLOGMOD=DSIL6MOD,MODETAB=AMODETAB
N3L0212 LU LOCADDR=02,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB
N3L0213 LU LOCADDR=03,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB
N3L0214 LU LOCADDR=04,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB
N3L0215 LU LOCADDR=05,DLOGMOD=M2SDLCQ,MODETAB=AMODETAB

Because the server workstation uses LU 6.2 parallel session support, you must update the ADDSESS,
MAXSESS, and AUXADDR keywords specified on the build macro to support this configuration. Verify that
you have specified the correct keywords and values on the LUDRPOOL macro. If you already modified
these keywords, ensure that you defined them correctly for the configuration you are defining. Perform
the changes to these keywords on every NCP that has a server workstation.

52 IBM Z NetView: Installation: Configuring Graphical Components

Defining the Logical Unit (LU) Name
The topology server can communicate with the NetView environment through an LU 6.2 conversation. To
communicate with the NetView environment through an LU 6.2 conversation, define the LU name for the
topology server that will be used.
To define the LU name of the topology server on the topology server workstation, use the sample ts.acg
configuration file in one of the following directories:
• For Windows systems: %BINDIR%\TDS\server\sample
• For UNIX systems: $BINDIR⁄TDS⁄server⁄sample
This file is shipped with the NetView management console and represents a sample communications
server configuration file for the topology server LU 6.2 communications. Use the configuration file as
a guide to tailor the configuration to fit your environment. See the appropriate communications server
documentation for more information about LU 6.2 connections.

Configuring Your Workstation for SNA

Before using the NetView management console to monitor your network, define your workstation network
configuration. This section outlines how to configure SNA on your topology server workstation.

Configuring Communications Server

To configure SNA LU 6.2 support for your workstation network, use the information in this section.
NCP can be channel-attached to the host, with token-ring connections between the NCP and server.
The topology communications server provides communications between the server workstation and the
host. In a multi-workstation configuration, the topology server also handles communications between the
server workstation and the client workstations.
The topology server uses a topology communications server to establish and communicate through LU
6.2 sessions. The topology communication server supports LU 6.2 sessions through any medium that
supports LU 6.2 communication. The server workstation is directly connected to a status focal point host
through an LU 6.2 session.
This type of workstation serves the client workstation by storing views and status and by distributing this
data to the client workstations. The client workstation acts as a graphic operator console that retrieves
data from the server workstation. An example of this is a topology server workstation communicating with
topology console workstations over a LAN.
SNA requires an IBM SNA communications product to be properly configured. Although there are
numerous products that support the NetView management console requirements for communications
over SNA, they share certain parameters that must be configured. Before you configure your workstation
for SNA, define the following:
Data Link Control (DLC)
Defines the underlying communications hardware to use. This includes token-ring modems.
Local Node Definition
Defines the workstation control point name and ID to the hardware.
Connections
Specifies the link between the workstation and the host.
Local LU
Specifies the logical name that the topology communications server uses for communications.
Transaction Program
Specifies the attributes for the topology communications server.
Modes
Specifies the attributes of the communication session between the topology communications server
and the host.

Appendix A. SNA Definitions for the NetView Management Console Topology Servers 53
 Note: Workstations can have additional local LU profiles and partner LU profiles that define LUs that are
used by other applications. These profiles must not specify the same LU names that are used by the
topology server.
To define the LU name of the topology server on the topology server workstation, use the sample ts.acg
configuration file in one of the following directories:
• For Windows systems: %BINDIR%\TDS\server\sample
• For UNIX systems: $BINDIR⁄TDS⁄server
This file is shipped with the NetView management console and represents a sample communications
server configuration file for the topology server LU 6.2 communications. Use the configuration file as
a guide to tailor the configuration to fit your environment. See the appropriate communications server
documentation for more information about LU 6.2 connections.

Using Communications Server to Configure your Workstation Network

The tables in this section provide examples of how to define the LU 6.2 sessions between the host and the
server workstation.
The fields provided in the tables are fields that, typically, are in the configuration panel for each area.
Because each SNA communications program is slightly different, the fields in the tables might not be
available in all products or they might be labeled slightly differently.

Data Link Control Profile for LAN

Table 3 on page 54 shows an example of the topology server workstation configuration for the data link
control profile for LAN.

Table 3. APPC APIs over Token Ring

Communications Example Field Value Explanation
Server Field Name
Adapter 0 The LAN adapter used for this communication.
Free Unused Link No No indicates that the host connection must not
be dropped when the last application is logged
off.
Local Node Name A19SRVCP The 8-character name of the local control point.
The name must match the CP name parameter
in the host definition for this workstation.
Maximum I-field Size 2048 Specifies the maximum I-field size that the
station can receive. This number must be
greater than, or equal to, the maximum I-field
size in the transmission service mode profile.
For the host connection only, this number must
coordinate with the MAXDATA value on the PU
definition statement.
Maximum Number of 16 One link is used to allocate sessions to
Link Stations another workstation. This parameter sets the
maximum number of link stations that LU 6.2
communication uses.
Network ID NETA The 8-character name for the network
containing this PU.
Receive Window 1 The receive window count specifies the number
Count of frames that the station can receive before
sending an acknowledgment.

54 IBM Z NetView: Installation: Configuring Graphical Components

Table 3. APPC APIs over Token Ring (continued)
Communications Example Field Value Explanation
Server Field Name
Send Window Count 7 The send window count specifies the number
of frames that the station can send before
receiving an acknowledgment. For the host
connection, this number must match the
MAXOUT parameter on the PU definition
statement.

Local Node Characteristics for LAN

Table 4 on page 55 shows an example of a topology server workstation configuration for the local node
characteristics. Modify this profile for a LAN configuration.

Table 4. Local Node Characteristics for LAN (Communications Server)

Communications Example Field Value Explanation
Server Field Name
Network ID NETA The 8-character name of the network containing
this PU.
Local Node Name (CP A19SRVCP The 8-character name of the local control point.
name) The name must match the CP name parameter
in the host definition for this workstation.
Local Node Type Network node The topology server can work with any node
type. This example, however, assumes that the
node type of the server is network node.
Local Node ID (in (05D) 00001 Used to determine which link station is primary
hexadecimal) for negotiable link stations. The node with the
higher value becomes the primary link station.
For a LAN connection, the first 3 hexadecimal
digits are typically '05D'; the last 5 hexadecimal
digits must match the IDNUM parameter in the
switched major node PU definition.

Local LU Profile
Table 5 on page 55 shows an example of the topology server workstation configuration for the logical
unit profile you have specified.

Table 5. Local LU Profile (Communications Server)

Communications Example Field Value Explanation
Server Field Name
LU Name A19SRVLO Specifies the name of the LU as it is known
externally to the SNA network. The value must
match the host definition for this workstation.
This value is unique for each workstation.
LU Alias EGVPC The name of the local LU profile. Create a local
LU profile with the name EGVPC. The topology
server requires the value EGVPC. The topology
server also requires the LU alias to be specified
in uppercase.

Appendix A. SNA Definitions for the NetView Management Console Topology Servers 55
 Table 5. Local LU Profile (Communications Server) (continued)
Communications Example Field Value Explanation
Server Field Name
NAU Address Independent LU The topology server requires that an
independent LU be selected.

Modes Profile
Table 6 on page 56 is an example of the topology server workstation configuration for the transmission
service mode profile.

Table 6. Modes Profile (Communications Server)

Communications Example Field Value Explanation
Server Field Name
Mode Name DSIL6MOD Specifies the mode name profile. Create a mode
name profile with the name DSIL6MOD. The
topology server requires this value.
Class of Service #CONNECT Specifies the class of service name. Use the
system default for this value.
Mode Session Limit 3 Specifies the mode session limit. The topology
server requires a minimum of 3. The sum of the
mode session limits for a partner LU must be
equal to or less than the partner LU session limit
in the partner LU profile.
Minimum Contention 1 The topology server requires 1 contention
Winners winner source session.
Receive Pacing 1 Must be coordinated with the PACING
Window parameter in the NCP definition for this LU
and the SSNDPAC and ARCVPAC parameter in
the VTAM logmode entry table for DSIL6MOD.
Pacing prevents a session from flooding a node
with data and using all the available buffers.
RU Size Default RU Enables Communications Server to select
the most appropriate maximum RU size. If
Maximum RU size is selected, the maximum
RU size must be smaller than or equal to
the maximum RU size in the appropriate DLC
profile.

Transaction Program Definitions

Table 7 on page 56 shows an example of the topology server workstation configuration for the
transaction program profile.

Table 7. Transaction Program Definitions

Communications Example Field Value Explanation
Server Field Name
Service TP No The topology server transaction program is not
a service TP.

56 IBM Z NetView: Installation: Configuring Graphical Components

Table 7. Transaction Program Definitions (continued)
Communications Example Field Value Explanation
Server Field Name
Transaction Program 30F0F4F4 The required name of the topology server
(TP) Name transaction program. This value is case-
sensitive and the topology server requires the
TP name to be specified in upper case.
Transaction Program ihsctp.exe The TP executable file which enables the host
(TP) File Name and server to communicate.
Conversation Security No The topology server does not support
conversation security.
Program Parameter The topology server does not require this field.
String

Connections for LAN

If you have a LAN connection, configure a connection to the host.
Note: Define the connection to the host if you do not have a 3270 emulator session to that host.
Then configure a connection by performing the following steps:
1. Select the adapter type.
2. Verify that the appropriate adapter number is in the entry field.
3. Click Continue.

Table 8. Connections for LAN

Communications Example Field Value Explanation
Server Field Name
Link name LINK0001 Specifies the user default.
Adjacent Node ID Blank Specifies the XID used by the partner node.
Leave this value blank for the topology server.
Partner Network ID NETID Use the NETID in the VTAM ATCSTRxx member.
Partner Node Name SSCPNAME Use SSCPNAME in the VTAMATCSTRxx member.
This field and the Partner Network ID can be left
blank.
LAN Destination The 12-character, hexadecimal LAN address of
Address (LAN only) the computer to which you are defining the
connection.
Address Format Token-ring This value must match the type of LAN
connection you are using: token-ring or
Ethernet.
Remote SAP 04 Defines the address of the service access
point (SAP) of the host with which you are
communicating.

Appendix A. SNA Definitions for the NetView Management Console Topology Servers 57
58 IBM Z NetView: Installation: Configuring Graphical Components
Appendix B. NetView Graphics Samples

This appendix contains the following topics:

• “GMFHS Samples” on page 59
• “NetView Management Console Samples” on page 60
• “NetView Resource Manager Samples” on page 60
• “RODM Samples” on page 61
Other NetView samples are described in IBM Z NetView Installation: Getting Started.
Note: Although the samples have been tested and are supported by IBM, you are responsible for making
the proper modifications to the samples for your operating environment.

GMFHS Samples
Table 9 on page 59 lists the samples and includes a brief description of each GMFHS sample and the
data set name where each member resides when installation is complete.

Table 9. List of GMFHS Samples

Distributed As Name Description Data Set Name
CNMCMENT same NetView command definition statements including DSIPARM
those for GMFHS
CNMS4402 CNMSNIFF GMFHS automation example CNMSAMP
CNMS4403 EKGSNIFF GMFHS automation example CNMSAMP
CNMSJH10 CNMGMFHS GMFHS start procedure CNMSAMP
CNMSJH13 same Relink - edits the assembler table, DUIFSMT CNMSAMP
CNMSTYLE same Sample that defines many of the NetView DSIPARM
initialization parameters. Refer to the CNMSTYLE
member for more information.
DUIFCUX2 same Sample RODM method (for exception views) that CNMSAMP
is driven as an installation exit by GMFHS if the
USRXMETH keyword is set in the DisplayStatus
mapping table
For more information about DUIFCUX2,
DUIFCUXM, USRXMETH, and the DisplayStatus
mapping table, refer to the IBM Z NetView Resource
Object Data Manager and GMFHS Programmer's
Guide.

DUIFCUXM same Sample RODM method (for exception views) that CNMSAMP
is driven as an installation exit by GMFHS if the
USRXMETH keyword is set in the DisplayStatus
mapping table
For more information about DUIFCUXM, refer to the
IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide for information about
DUIFCUXM, USRXMETH, and the DisplayStatus
mapping table.

© Copyright IBM Corp. 2001, 2022 59

 Table 9. List of GMFHS Samples (continued)
Distributed As Name Description Data Set Name
DUIFDEXV same Sample exception views object and exception CNMSAMP
views candidate definitions
DUIFEDEF same Non-SNA resource alert processor CNMSAMP
DUIFEMDY same NETCENTER migration sample CNMSAMP
DUIFEUSR same Provides alert translation constants for GMFHS CNMSAMP
event management
DUIFSNET same Sample load file CNMSAMP
DUIFSTRC same GMFHS data model CNMSAMP
DUIGINIT same GMFHS initialization parameters DSIPARM
DUIGPWLU same Graphic data server LU names to GMFHS that are DSIPARM
not to be allowed to acquire a session
DUIIGHB same Initialization values for the DUIDGHB task DSIPARM

NetView Management Console Samples

Table 10 on page 60 lists the samples and includes a brief description of each NetView management
console sample and the data set name where each member resides after installation is complete.

Table 10. List of NetView Management Console Samples

Distributed As Name Description Data Set Name
CNMSAF2 same Sample RACF definition statements for restricting DSIPARM
access to the NetView management console
CNMSCAT2 same Sample command authorization table statements DSIPARM
for restricting access to the NetView management
console
CNMSTYLE same NetView initialization parameters DSIPARM
Refer to the CNMSTYLE member for more
information.

DUIFPMEM same CNMTAMEL task definition statements DSIPARM

DUIFSMT same Default DisplayStatus mapping table CNMSAMP
DUIISFP same Defines initialization values for the CNMTAMEL task DSIPARM
DUIPOLCY same Define NMCSTATUS policy definitions DSIPARM

NetView Resource Manager Samples

bkm:(split='yes' hdframe='rules') lists the samples and includes a brief description of each NetView
Resource Manager sample and the data set name where each member resides after installation.

60 IBM Z NetView: Installation: Configuring Graphical Components

 Table 11. List of NetView Resource Manager Samples
Distributed As Name Description Data Set Name
CNMSTYLE same NetView initialization parameters. DSIPARM
All of the NetView Resource
Manager initialization parameters
are in the CNMSTYLE member.
Refer to the CNMSTYLE member
for more information.

DUIFNRM1 same Group of RODM Collection CNMSAMP

Manager collections
The contents of the collections
are various NetView Resource
Manager objects from ALL
monitored NetView programs.

DUIFNRM2 same Group of RODM Collection CNMSAMP

Manager collections
The contents of the collections
are various NetView Resource
Manager objects from a single
NetView program.

RODM Samples
Table 12 on page 61 lists the RODM samples found in the NETVIEW.V6R4M0.CNMSAMP library. The
table includes a brief description of each sample and the data set name into which each member is
copied.
All required JCL and definitions can be found in the NETVIEW.V6R4M0.CNMSAMP library under the
distributed sample name.

Table 12. List of RODM Samples

Distributed As Name Description Data Set Name
CNMCMENT same NetView command definition statements for RODM DSIPARM
CNMS4290 ARODMCON Activates the assembler DSINOR that connects to CNMSAMP
RODM
CNMSJ004 same Deletes and defines the NetView program, RODM, CNMSAMP
and AON VSAM databases.
CNMSJH12 same Loads the RODM data cache for GMFHS CNMSAMP
CNMSJI10 same IEBCOPY RODM procedure to PROCLIB CNMSAMP
CNMSTYLE same NetView initialization parameter definitions DSIPARM
Refer to the CNMSTYLE member for more
information.

DSIQTSKI same Defines RODM tasks to the RODM access and DSIPARM
control subtask (DSIQTSK)

Appendix B. NetView Graphics Samples 61

 Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG51100 same PL/I Sample - Function (connect with password CNMSAMP
phrase)

EKG_ConnectLong

EKG51101 same PL/I Sample - Function (connect with password) CNMSAMP

EKG_Connect

EKG51102 same PL/I Sample - Function CNMSAMP

EKG_Disconnect

EKG51201 same PL/I Sample - Function CNMSAMP

EKG_Checkpoint

EKG51202 same PL/I Sample - Function CNMSAMP

EKG_Stop

EKG51302 same PL/I Sample - Function CNMSAMP

EKG_CreateClass

EKG51303 same PL/I Sample - Function CNMSAMP

EKG_DeleteClass

EKG51304 same PL/I Sample - Function CNMSAMP

EKG_CreateField

EKG51305 same PL/I Sample - Function CNMSAMP

EKG_DeleteField

EKG51306 same PL/I Sample - Function CNMSAMP

EKG_CreateSubfield

EKG51307 same PL/I Sample - Function CNMSAMP

EKG_DeleteSubfield

EKG51401 same PL/I Sample - Function CNMSAMP

EKG_ChangeField

EKG51402 same PL/I Sample - Function CNMSAMP

EKG_SwapField

EKG51403 same PL/I Sample - Function CNMSAMP

EKG_ChangeSubfield

62 IBM Z NetView: Installation: Configuring Graphical Components

Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG51404 same PL/I Sample - Function CNMSAMP

EKG_SwapSubfield

EKG51405 same PL/I Sample - Function CNMSAMP

EKG_LinkTrigger

EKG51406 same PL/I Sample - Function CNMSAMP

EKG_LinkNoTrigger

EKG51407 same PL/I Sample - Function CNMSAMP

EKG_UnLinkTrigger

EKG51408 same PL/I Sample - Function CNMSAMP

EKG_UnLinkNoTrigger

EKG51409 same PL/I Sample - Function CNMSAMP

EKG_CreateObject

EKG51410 same PL/I Sample - Function CNMSAMP

EKG_DeleteObject

EKG51411 same PL/I Sample - Function CNMSAMP

EKG_RevertToInherited

EKG51412 same PL/I Sample - Function CNMSAMP

EKG_AddNotifySubscription

EKG51413 same PL/I Sample - Function CNMSAMP

EKG_DeleteNotifySubscription

EKG51415 same PL/I Sample - Function CNMSAMP

EKG_TriggerNamedMethod

EKG51416 same PL/I Sample - Function CNMSAMP

EKG_TriggerOIMethod

EKG51417 same PL/I Sample - Function CNMSAMP

EKG_AddObjDelNotifySubs

EKG51418 same PL/I Sample - Function CNMSAMP

EKG_DelObjDelNotifySubs

Appendix B. NetView Graphics Samples 63

 Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG51419 same PL/I Sample - Function CNMSAMP

EKG_ChangeMultipleFields

EKG51501 same PL/I Sample - Function CNMSAMP

EKG_QueryField

EKG51502 same PL/I Sample - Function CNMSAMP

EKG_QuerySubfield

EKG51503 same PL/I Sample - Function CNMSAMP

EKG_QueryEntityStructure

EKG51504 same PL/I Sample - Function CNMSAMP

EKG_QueryFieldStructure

EKG51505 same PL/I Sample - Function CNMSAMP

EKG_QueryFieldID

EKG51506 same PL/I Sample - Function CNMSAMP

EKG_QueryFieldName

EKG51507 same PL/I Sample - Function CNMSAMP

EKG_QueryNotifyQueue

EKG51508 same PL/I Sample - Function CNMSAMP

EKG_QueryMultipleSubfields

EKG51509 same PL/I Sample - Function CNMSAMP

EKG_Locate

EKG51510 same PL/I Sample - Function CNMSAMP

EKG_QueryResponseBlockOverflow

EKG51600 same PL/I Sample - Function CNMSAMP

EKG_ExecuteFunctionList

EKG52001 same PL/I Sample - Function CNMSAMP

EKG_QueryFunctionBlockContents

EKG52002 same PL/I Sample - Function CNMSAMP

EKG_LockObjectList

64 IBM Z NetView: Installation: Configuring Graphical Components

Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG52003 same PL/I Sample - Function CNMSAMP

EKG_UnlockAll

EKG52004 same PL/I Sample - Function CNMSAMP

EKG_ResponseBlock

EKG52005 same PL/I Sample - Function CNMSAMP

EKG_SendNotification

EKG52006 same PL/I Sample - Function CNMSAMP

EKG_SetReturnCode

EKG52007 same PL/I Sample - Function CNMSAMP

EKG_WhereAmI

EKG52008 same PL/I Sample - Function CNMSAMP

EKG_OutputToLog

EKG52009 same PL/I Sample - Function CNMSAMP

EKG_MessageTriggeredAction

EKG52011 same PL/I Sample - Function CNMSAMP

EKG_QueryObjectName

EKG5VDCL same PL/I sample that declares RODM data types CNMSAMP
EKG5WAIT same PL/I sample to invoke RODM EKGWAIT CNMSAMP
EKG61100 same C Sample - Function (connect with password CNMSAMP
phrase)
EKG_ConnectLong

EKG61101 same C Sample - Function (connect with password) CNMSAMP

EKG_Connect

EKG61102 same C Sample - Function CNMSAMP

EKG_Disconnect

EKG61201 same C Sample - Function CNMSAMP

EKG_Checkpoint

EKG61202 same C Sample - Function CNMSAMP

EKG_Stop

Appendix B. NetView Graphics Samples 65

 Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG61302 same C Sample - Function CNMSAMP

EKG_CreateClass

EKG61303 same C Sample - Function CNMSAMP

EKG_DeleteClass

EKG61304 same C Sample - Function CNMSAMP

EKG_CreateField

EKG61305 same C Sample - Function CNMSAMP

EKG_DeleteField

EKG61306 same C Sample - Function CNMSAMP

EKG_CreateSubfield

EKG61307 same C Sample - Function CNMSAMP

EKG_DeleteSubfield

EKG61401 same C Sample - Function CNMSAMP

EKG_ChangeField

EKG61402 same C Sample - Function CNMSAMP

EKG_SwapField

EKG61403 same C Sample - Function CNMSAMP

EKG_ChangeSubfield

EKG61404 same C Sample - Function CNMSAMP

EKG_SwapSubfield

EKG61405 same C Sample - Function CNMSAMP

EKG_LinkTrigger

EKG61406 same C Sample - Function CNMSAMP

EKG_LinkNoTrigger

EKG61407 same C Sample - Function CNMSAMP

EKG_UnLinkTrigger

EKG61408 same C Sample - Function CNMSAMP

EKG_UnLinkNoTrigger

66 IBM Z NetView: Installation: Configuring Graphical Components

Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG61409 same C Sample - Function CNMSAMP

EKG_CreateObject

EKG61410 same C Sample - Function CNMSAMP

EKG_DeleteObject

EKG61411 same C Sample - Function CNMSAMP

EKG_RevertToInherited

EKG61412 same C Sample - Function CNMSAMP

EKG_AddNotifySubscription

EKG61413 same C Sample - Function CNMSAMP

EKG_DeleteNotifySubscription

EKG61415 same C Sample - Function CNMSAMP

EKG_TriggerNamedMethod

EKG61416 same C Sample - Function CNMSAMP

EKG_TriggerOIMethod

EKG61417 same C Sample - Function CNMSAMP

EKG_AddObjDelNotifySubs

EKG61418 same C Sample - Function CNMSAMP

EKG_DelObjDelNotifySubs

EKG61419 same C Sample - Function CNMSAMP

EKG_ChangeMultipleFields

EKG61501 same C Sample - Function CNMSAMP

EKG_QueryField

EKG61502 same C Sample - Function CNMSAMP

EKG_QuerySubfield

EKG61503 same C Sample - Function CNMSAMP

EKG_QueryEntityStructure

EKG61504 same C Sample - Function CNMSAMP

EKG_QueryFieldStructure

Appendix B. NetView Graphics Samples 67

 Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG61505 same C Sample - Function CNMSAMP

EKG_QueryFieldID

EKG61506 same C Sample - Function CNMSAMP

EKG_QueryFieldName

EKG61507 same C Sample - Function CNMSAMP

EKG_QueryNotifyQueue

EKG61508 same C Sample - Function CNMSAMP

EKG_QueryMultipleSubfields

EKG61509 same C Sample - Function CNMSAMP

EKG_Locate

EKG61510 same C Sample - Function CNMSAMP

EKG_QueryResponseBlockOverflow

EKG61600 same C Sample - Function CNMSAMP

EKG_ExecuteFunctionList

EKG62001 same C Sample - Function CNMSAMP

EKG_QueryFunctionBlockContents

EKG62002 same C Sample - Function CNMSAMP

EKG_LockObjectList

EKG62003 same C Sample - Function CNMSAMP

EKG_UnlockAll

EKG62004 same C Sample - Function CNMSAMP

EKG_ResponseBlock

EKG62005 same C Sample - Function CNMSAMP

EKG_SendNotification

EKG62006 same C Sample - Function CNMSAMP

EKG_SetReturnCode

EKG62007 same C Sample - Function CNMSAMP

EKG_WhereAmI

68 IBM Z NetView: Installation: Configuring Graphical Components

Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKG62008 same C Sample - Function CNMSAMP

EKG_OutputToLog

EKG62009 same C Sample - Function CNMSAMP

EKG_MessageTriggeredAction

EKG62011 same C Sample - Function CNMSAMP

EKG_QueryObjectName

EKG6VDCL same C sample that declares RODM data types CNMSAMP

EKG6WAIT same C sample to invoke RODM EKGWAIT CNMSAMP
EKGCMIMV same C sample that increments the value of a specified CNMSAMP
field
EKGCPPI same Sample change method to invoke EKGSPPI CNMSAMP
EKGCTABL same Sample loader control file CNMSAMP
EKGCTIM same Sample change method source CNMSAMP
EKGCUST same Sample RODM customization file CNMSAMP
EKGCVER same C sample verification routine source CNMSAMP
EKGIN1 same Sample RODM structure load input CNMSAMP
EKGIN3 same Sample RODM object load input CNMSAMP
EKGINIT same Sample initialization method CNMSAMP
EKGINMTB same Sample loader install method table CNMSAMP
EKGIVER same PL/I sample verification routine source CNMSAMP
EKGKUCDS same Sample that allocates output data sets used by CNMSAMP
RODMUNLD to store RODM loader statements
EKGKUJCL same Sample that invokes the RODM unload function CNMSAMP
EKGLG000 same Sample log formatter procedure CNMSAMP
EKGLLINK same Sample JCL to link edit user modules that load CNMSAMP
structure and object definitions to RODM
EKGLLOAD same Sample RODM JCL procedure to load RODM data CNMSAMP
cache
EKGLOADP same Sample RODM JCL procedure to load RODM data PROCLIB
cache
EKGLUSER same Sample JCL for structure or object load of RODM CNMSAMP
through a user module
EKGMIMV same Sample named method source CNMSAMP
EKGNEQL same Sample notification method 4 CNMSAMP
EKGNLST same Sample notification method 3 CNMSAMP

Appendix B. NetView Graphics Samples 69

 Table 12. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
EKGNOTF same Sample notification method 1 CNMSAMP
EKGNTHD same Sample notification method 2 CNMSAMP
EKGOPPI same Sample object independent method to invoke CNMSAMP
EKGSPPI
EKGPTENU same Sample load parameter mapping table CNMSAMP
EKGRDUMP same Sample JCL to run the RODM dump utility CNMSAMP
EKGRLOG same Sample JCL to submit log formatter procedure CNMSAMP
EKGSCKPT same Sample JCL to allocate VSAM checkpoint data sets CNMSAMP
for a second instance of RODM
EKGSI101 same Allocates the RODM VSAM databases CNMSAMP
EKGSI201 same Allocates the RODM log VSAM databases for a CNMSAMP
second instance of RODM
EKGSI202 same Allocates the RODM master, transaction, and check CNMSAMP
point VSAM databases for a second instance of
RODM
EKGSID01 same Deletes the RODM log VSAM databases for a CNMSAMP
second instance of RODM
EKGSID02 same Deletes the RODM master, transaction, and check CNMSAMP
point VSAM databases for a second instance of
RODM
EKGSLOG same Sample JCL to allocate VSAM data sets used for CNMSAMP
logging for a second instance of RODM
EKGSVER same Sample JCL to run the installation verification CNMSAMP
routine
EKGXRODM same Sample JCL to start RODM PROCLIB

FLCARODM Samples
The following samples are specific to FLCARODM which provides an external REXX interface for the
manipulation of RODM objects.

Table 13. List of FLCARODM Samples

Distributed As Name Description Data Set Name
FLCSBX1 same Sample REXX example for FLCARODM CNMSAMP
FLCSBX2 same Sample REXX example for FLCARODM CNMSAMP
FLCSBX3 same Sample REXX example for FLCARODM CNMSAMP
FLCSBX4 same Sample REXX example for FLCARODM CNMSAMP
FLCSBX5 same Sample REXX example for FLCARODM CNMSAMP
FLCSBX6 same Sample REXX example for FLCARODM CNMSAMP
FLCSBX7 same Sample REXX example for FLCARODM CNMSAMP

70 IBM Z NetView: Installation: Configuring Graphical Components

Table 13. List of FLCARODM Samples (continued)
Distributed As Name Description Data Set Name
FLCSBX8 same Sample REXX example for FLCARODM CNMSAMP
FLCSDX1 same Sample REXX example for FLCARODM CNMSAMP
FLCSDX2 same Sample REXX example for FLCARODM CNMSAMP
FLCSDX3 same Sample REXX example for FLCARODM CNMSAMP
FLCSPX1 same Sample REXX example for FLCARODM CNMSAMP
FLCSPX2 same Sample REXX example for FLCARODM CNMSAMP
FLCSQX1 same Sample REXX example for FLCARODM CNMSAMP
FLCSQX2 same Sample REXX example for FLCARODM CNMSAMP
FLCSQX3 same Sample REXX example for FLCARODM CNMSAMP
FLCSQX4 same Sample REXX example for FLCARODM CNMSAMP
FLCSQX5 same Sample REXX example for FLCARODM CNMSAMP
FLCSSTEM same Sample REXX example for FLCARODM CNMSAMP
FLCSX10 same Sample REXX example for FLCARODM CNMSAMP
FLCSX11 same Sample REXX example for FLCARODM CNMSAMP
FLCSX12 same Sample REXX example for FLCARODM CNMSAMP
FLCSX13 same Sample REXX example for FLCARODM CNMSAMP
FLCSX14 same Sample REXX example for FLCARODM CNMSAMP
FLCSX15 same Sample REXX example for FLCARODM CNMSAMP
FLCSX16 same Sample REXX example for FLCARODM CNMSAMP
FLCSX17 same Sample REXX example for FLCARODM CNMSAMP
FLCSX18 same Sample REXX example for FLCARODM CNMSAMP
FLCSX19 same Sample REXX example for FLCARODM CNMSAMP
FLCSX1 same Sample REXX example for FLCARODM CNMSAMP
FLCSX20 same Sample REXX example for FLCARODM CNMSAMP
FLCSX21 same Sample REXX example for FLCARODM CNMSAMP
FLCSX22 same Sample REXX example for FLCARODM CNMSAMP
FLCSX2 same Sample REXX example for FLCARODM CNMSAMP
FLCSX3 same Sample REXX example for FLCARODM CNMSAMP
FLCSX4 same Sample REXX example for FLCARODM CNMSAMP
FLCSX5 same Sample REXX example for FLCARODM CNMSAMP
FLCSX6 same Sample REXX example for FLCARODM CNMSAMP
FLCSX7 same Sample REXX example for FLCARODM CNMSAMP
FLCSX8 same Sample REXX example for FLCARODM CNMSAMP
FLCSX9 same Sample REXX example for FLCARODM CNMSAMP

Appendix B. NetView Graphics Samples 71

 Table 13. List of FLCARODM Samples (continued)
Distributed As Name Description Data Set Name
FLCSXF1 same Sample REXX example for FLCARODM CNMSAMP
FLCSXL01 same Sample REXX example for FLCARODM CNMSAMP
FLCSXL02 same Sample REXX example for FLCARODM CNMSAMP
FLCSXQ1 same Sample REXX example for FLCARODM CNMSAMP
FLCSXQ2 same Sample REXX example for FLCARODM CNMSAMP
FLCSXQ3 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS01 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS02 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS03 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS04 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS05 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS06 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS07 same Sample REXX example for FLCARODM CNMSAMP
FLCSXS08 same Sample REXX example for FLCARODM CNMSAMP

72 IBM Z NetView: Installation: Configuring Graphical Components

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not give you any license to these patents. You can
send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

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

© Copyright IBM Corp. 2001, 2022 73

 Austin, TX 78758
U.S.A.

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 is a trademark of Adobe Systems Incorporated in the United States, and/or other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are 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.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software Offerings”) may use cookies
or other technologies to collect product usage information, to help improve the end user experience,
to tailor interactions with the end user or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings can help enable you
to collect personally identifiable information. If this Software Offering uses cookies to collect personally
identifiable information, specific information about this offering’s use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect personally identifiable
information.
If the configurations deployed for this Software Offering provide you as customer the ability to collect
personally identifiable information from end users via cookies and other technologies, you should seek
your own legal advice about any laws applicable to such data collection, including any requirements for
notice and consent.
For more information about the use of various technologies, including cookies, for these purposes,
See IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at http://
www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and Other Technologies”

74 IBM Z NetView: Installation: Configuring Graphical Components

and the “IBM Software Products and Software-as-a-Service Privacy Statement” at http://www.ibm.com/
software/info/product-privacy.

Notices 75
76 IBM Z NetView: Installation: Configuring Graphical Components
Index

A CNMSJI10 (continued)
EIBCOPY 61
accessibility xii CNMSNIFF 59
activating CNMSTYLE
NetView Resource Manager event manager autotask 17
AUTONRM 37 GMFHS global variables 6
initialization 39 RODM global variables 5
initialization, display status defaults 39 status focal point 28
initialization, monitoring remote systems 39 TCP/IP 28
initialization, sampling 39 CNMSTYLE initialization statements
security 37 COMMON.FLC_DEFAULT_ITNM_OBJECT_STATUS 45
security, command authorization 38 CNMTAMEL
allocating task definitions 60
VSAM clusters CNMTAMEL task 28
for RODM 7 collection manager
allocating VSAM clusters for RODM RODM 48
CNMSID01 7 command authorization
AUTH statement discovery manager security 43
NGMFADMN keyword usage 30 NetView Resource Manager security 38
NGMFCMDS keyword usage 30 command definition statements
AUTONRM GMFHS 59
NetView Resource Manager 37 COMMON.FLC_DEFAULT_ITNM_OBJECT_STATUS statement
autotasks 45
event manager 17 Communications Server
configuring for SNA, NetView management console 53
local LU profile 55
B local modes profile 56
BLDVIEWS transaction program definitions 56
RODM 49 Communications Server, using
books to configure for SNA LU 6.2
see publications ix workstation network 54
configuring
communications server
C configuring for SNA LU 6.2 53
for user rights for Windows systems 34
characteristics
topology server 31
local node
workstation network, NetView management console
LAN 55
configuring for SNA 53
checkpoint data sets
configuring for SNA LU 6.2
RODM 7
workstation network, NetView management console
CNMCMENT
using Communications Server 54
command definitions 61
connecting to RODM 12
CNME2101, GMFHS command list 6
connections
CNMGMFHS 16, 23
for LAN 57
CNMHELPR
control profile, data link
helpmap 61
for LAN 54
CNMS4290 61
conventions
CNMSID01
typeface xii
delete VSAM databases 61
correlating
CNMSJ004
views 47
allocate logs and databases 61
COS gateway autotask 17
job
CPDLB2 volume 8
allocating VSAM clusters for RODM 7
customization
CNMSJH10 16, 23
RODM 13
CNMSJH12
load RODM data cache 61
CNMSJH13 59
CNMSJI10

Index 77
D EGVREAD2.ME 31
EKGCUST
data link sample customization member 13
control profile EKGHNAM global variable 5
for LAN 54 EKGHPRC global variable 5
data models EKGKUJCL 69
loading GMFHS 23 EKGMIMV
loading MultiSystem Manager 23 named method 69
loading SNA topology manager 23 EKGNEQL
default status color 45 notification method 69
defining EKGNLST
NetView Resource Manager notification method 69
Autotask 37 EKGNOTF
VSAM clusters notification method 70
for RODM 7 EKGNTHD
defining IP socket port numbers 31 notification method 70
defining resources EKGOPPI
RACF 10 object independent method 70
defining the LU name 53 EKGPTENU 70
DELVIEWS EKGRDUMP 70
RODM 50 EKGRLOG
directory names, notation xiii log formatter JCL 8
discovery manager EKGSI101
activating 43 RODM checkpoint data set 7
command authorization 43 RODM logs 7
enabling 44 EKGSI202 70
managing resources 44 EKGSNIFF 59
preparing 43 EKGSVER
RODM access 43 verification member 21
security considerations 43 EKGXRODM
DSIQTSK task 15 sample start job 18
DSIQTSKI 15, 61 enabling
DUIDGHB task 28 NetView Resource Manager 6
DUIFCSGW object correlation
command processor 17 for additional SNA topology manager 47
DUIFCUX2 59 environment variables, notation xiii
DUIFCUXM, exception views 59 Ethernet LAN-attached workstation, defining 51
DUIFDEXV 60 event manager 17
DUIFEDEF 60 exception views
DUIFEMDY 60 implementing 47
DUIFEUSR 60
DUIFHNAM global variable 6
DUIFHPRC global variable 6
F
DUIFPMEM 60 FLBTRDM*
DUIFSMT 60 SNA topology manager data models 23
DUIFSNET FLCARODM
non-SNA network samples 70
22 FLCSDM*
DUIFSSCO 17 MultiSystem Manager data models 23
DUIFSTRC FLCSDM8 47
GMFHS data model 23
DUIGINIT 60
DUIGPWLU 17, 60 G
DUIIGHB 29, 60
GHB.TCPANAME keyword 29
DUIISFP 15, 29, 60
global variables
DUILOGON command 29
DUIFHNAM 6
DUIPOLCY 60
DUIFHPRC 6
dump utility, RODM 9
GMFHS 6
RODM 5
E GMFHS
automation example 59
EDGXRODM CNME2101 6
start procedure 13 command definition statements 59
EGVREAD1.ME 35

78 IBM Z NetView: Installation: Configuring Graphical Components

GMFHS (continued) M
COS gateway autotask 17
data model, loading 23 manuals
defining event manager autotask 17 see publications ix
description 1 MAXLNTH statement 11
global variables 6 method, notification 69
initialization 59 modes, local
initialization parameters profile 56
CNMSTYLE 60 monitoring
DUIGINIT 60 remote NetView systems
initialization values 16 NetView Resource Manager 39
installing 16 RMTCMD considerations 40
main task 16 MultiSystem Manager
message routing 17 correlating views 47
restricting server access 17 data model, loading 23
samples 59 MVS subsystem
scope checker OPT 17 RODM 7
start procedure 16, 59
starting 23
verifying installation 25
N
GMFHS resources, additional NCP
enabling object correlation 47 definitions
GMFHS STATUS 25 NetView management console 51
NETCMD command 18
I NetView management console
configuring the server 31
initialization installation verification 35
for NetView Resource Manager installing 27
display status defaults 39 LAN definitions 51, 52
monitoring remote systems 39 NMCSTATUS autotask 18
sampling 39 resource time schedules 47
installation samples 60
verifying for NetView Resource Manager 40 security 29
installing topology console, installing 35
GMFHS 16 topology server
NetView management console 27 communication, starting 35
RODM 7 configuring 31
installing 31
restricting access to GMFHS 17
L topology workstation
LAN signing on 36
connections 57 NetView Resource Manager
data link control profile 54 activating
local node characteristics 55 AUTONRM 37
LAN-attached workstation definitions 51, 52 initialization 39
local LU profile 55 initialization, display status defaults 39
local modes profile 56 initialization, monitoring remote systems 39
local node characteristics initialization, sampling 39
LAN 55 security 37
log formatter security, command authorization 38
RODM 8 enabling 6
LU 6.2 connectivity 51 preparing
LU 6.2 sessions AUTONRM 37
configuring Communications Server initialization 39
workstation network, NetView management initialization, display status defaults 39
console 53 initialization, monitoring remote systems 39
configuring workstation network initialization, sampling 39
using Communications Server 54 security 37
LU, local security, command authorization 38
profile 55 starting 40
verifying installation 40
NGMFADMN keyword, AUTH statement 30
NGMFCMDS keyword, AUTH statement 30
NMCSTATUS autotask 18

Index 79
NMCSTATUS policy definitions 47 RODM (continued)
node characteristics, local allocating VSAM clusters for (continued)
LAN 55 CNMSID01 7
notation BLDVIEWS 49
environment variables xiii checkpoint data set 70
path names xiii command definitions 61
typeface xiii customization file, sample 69
notification method 69 customization parameters 13
data model, sample 60
defining security
O to RODMMGR class 9
object class definitions to user-defined class 10
RODM 22 defining the checkpoint data sets 7
object correlation definition statement
enabling MAXLNTH 11
for additional SNA topology manager 47 delete VSAM databases, using CNMSID01 61
enabling for additional SNA topology manager 47 DELVIEWS 50
online publications description 1
accessing xi DSIQTSK 15
dump utility 70
ending 21
P exception views 59
global variables 5
path names, notation xiii
helpmap 61
port numbers, reassigning 31
initialization method
preparing
sample 69
NetView Resource Manager
initialization values 15
AUTONRM 37
installation verification
initialization 39
EKGSVER 70
initialization, display status defaults 39
installing 7
initialization, monitoring remote systems 39
load file, sample 60
initialization, sampling 39
load RODM data cache
security 37
CNMSJH12 61
security, command authorization 38
loading the data cache 22
profile
log 70
local LU 55
log formatter 69
local modes 56
MVS subsystem, defining 7
profile, control
object load 69
data link for LAN 54
RODM Unloader 48
publications
RODMVIEW 48
accessing online xi
samples 61
IBM Z NetView ix
SEC_CLASS field 9
ordering xi
SEC_RNAME field 10
security 9
R start procedure 13
start with EKGXRODM 70
RACF starting 18
RODM security 9 structure load 69
RACF security tasks 61
defining resources 10 tools
readme files BLDVIEWS 49
EGVREAD1.ME 35 DELVIEWS 50
EGVREAD2.ME 31 RODM collection manager 48
reassigning port numbers 31 RODM Unloader 48
Resource Manager, NetView RODMVIEW 48
enabling 6 using dump utility 9
resource object data manager verifying using EKGSVER 21
using RODM dump utility 9 views
RMTCMD considerations customizing 49
monitoring remote NetView systems 40 deleting 50
RODM RODM collection manager 48
allocate log using CNMSJ004 61 RODM connection 12
allocating VSAM clusters 7 RODM tools 48
allocating VSAM clusters for RODM Unloader 48

80 IBM Z NetView: Installation: Configuring Graphical Components

RODMVIEW Tivoli Software Information Center xi
RODM 48 token-ring
LAN-attached workstation
defining 52
S topology
samples correlation 47
CNMGMFHS 16, 23 topology console, installing 35
CNMHELPW 60 topology server
CNMSAF 60 configuring 31
CNMSCAT2 60 configuring as a UNIX daemon 34
CNMSJ004 7 configuring as a Windows service 34
CNMSJH10 23 defining IP socket port numbers 31
CNMSJH12 22 defining the LU name 53
DUIFSNET 22 NetView management console, installing 31
DUIGINIT 17 reassigning port numbers 31
EKGCUST 13 setting security 34
EKGSI101 7 storing databases 32
GMFHS 59 updating the TSERVER_DB variable 33
RODM 61 topology server running as a UNIX daemon 34
sampling topology server running as a Windows service 34
NetView Resource Manager 39 topology servers
scope checker OPT 17 defining to
SEC_CLASS token-ring LAN-attached 52
field in RODM 9 transaction program definitions 56
SEC_RNAME field in RODM 10 tserver dbtransfer command 33
security TSERVER_DB variable 33
for NetView Resource Manager typeface conventions xii
command authorization 38
for the discovery manager 43 U
service points
receiving commands 17 Unloader
SNA LU 6.2 sessions RODM 48
configuring Communications Server updating the TSERVER_DB variable 33
workstation network, NetView management user group, NetView xii
console 53 user groups
configuring workstation network NetView xii
using Communications Server 54
SNA topology manager
data model, loading 23
V
span of control variables, notation for xiii
resources 46 verifying
views 46 installation
starting NetView Resource Manager 40
GMFHS 23 RODM installation 21
NetView Resource Manager 40 views
RODM 18 correlating 47
status defaults customizing 49
displaying for NetView Resource Manager 39 deleting 50
storing topology server databases 32 managing 45, 48
system authorization facility product resource time schedules 47
RODMMGR class 9 restricting access 46
VSAM
T allocating
for RODM 7
TAMEL.CONV keyword 28 VSAM clusters for RODM, allocating
TAMEL.PORT keyword 28 CNMSID01 7
TAMEL.SOCKETS keyword 28 VTAM
TAMEL.TCPANAME keyword 28 definitions
TAMEL.TTLS keyword 28 NetView management console 51
tasks
CNMTAMEL 23
DSIQTSK 15
W
TCP/IP 28 workstation

Index 81
workstation (continued)
defining
Ethernet LAN-attached 51
token-ring LAN-attached 52
workstation configuration
configuring for SNA, NetView management console 53
workstation network, NetView management console
configuring Communications Server
for SNA LU 6.2 53
configuring for SNA 53

82 IBM Z NetView: Installation: Configuring Graphical Components

IBM®

GC27-2852-04