IBM Z NetView

Version 6.Release 3

Installation: Configuring Graphical

Components

IBM

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

This edition applies to version 6, release 3 of IBM Z NetView (product number 5697-NV6 ) and to all subsequent
versions, releases, and modifications until otherwise indicated in new editions.
This edition replaces GC27-2852-01.
© Copyright International Business Machines Corporation 2001, 2019.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
Contents

Figures................................................................................................................ vii
About this publication...........................................................................................ix
Intended audience...................................................................................................................................... ix
Publications................................................................................................................................................. ix
IBM Z NetView library............................................................................................................................ ix
Related publications .............................................................................................................................. x
Terminology in this Library.................................................................................................................... xi
Using IBM Z NetView online help.......................................................................................................... xi
Accessing publications online............................................................................................................... xi
Ordering publications ...........................................................................................................................xii
Accessibility ............................................................................................................................................... xii
Tivoli user groups....................................................................................................................................... xii
Support information................................................................................................................................... xii
Conventions used in this publication......................................................................................................... xii
Typeface conventions .......................................................................................................................... xii
Operating system-dependent variables and paths.............................................................................xiii
Syntax diagrams...................................................................................................................................xiii

Chapter 1. Introduction......................................................................................... 1
Managing SNA Resources with the SNA Topology Manager....................................................................... 1
Managing Non-SNA Resources with MultiSystem Manager....................................................................... 2
Managing NetView Resources with the NetView Resource Manager.........................................................3
Managing Sysplex Resources with the NetView Discovery Manager......................................................... 3
Planning the Installation Process................................................................................................................4

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

Enabling RODM.............................................................................................................................................5
Enabling GMFHS...........................................................................................................................................6
Enabling SNA Topology Manager.................................................................................................................6
Enabling MultiSystem Manager................................................................................................................... 6
Enabling NetView Resource Manager..........................................................................................................7
Enabling the Discovery Manager................................................................................................................. 7

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

Preparing RODM........................................................................................................................................... 9
Defining RODM as an MVS Subsystem................................................................................................... 9
Allocating VSAM Clusters for RODM...................................................................................................... 9
Bypassing or Defining Security............................................................................................................ 11
Updating the RODM Start Procedure................................................................................................... 15
Defining RODM Using the EKGCUST Member......................................................................................15
Defining Initialization Values for RODM DSIQTSK Task...................................................................... 17
Preparing GMFHS.......................................................................................................................................18
Updating the GMFHS Start Procedure................................................................................................. 18
Defining Initialization Values for the GMFHS Main Task..................................................................... 18
Defining the COS Gateway Autotask....................................................................................................19
Defining the Event Manager Autotask................................................................................................. 19
Defining the Scope Checker OPT......................................................................................................... 19
Defining the NMCSTATUS Policy Autotask...........................................................................................20
Starting RODM Using Job EKGXRODM...................................................................................................... 20
Verifying the RODM Installation................................................................................................................ 23

iii
 Loading the Data Models........................................................................................................................... 24
Starting GMFHS Using Job CNMGMFHS....................................................................................................25
Verifying the GMFHS Installation.............................................................................................................. 27

Chapter 4. Installing and Configuring the NetView Management Console for

Graphics..........................................................................................................29
NetView Setup for the NetView Management Console............................................................................ 29
Defining the Status Focal Point............................................................................................................ 30
Security Considerations....................................................................................................................... 31
Workstation Setup for the NetView Management Console...................................................................... 32
Installing and Configuring the NetView Management Console Topology Server............................... 33
Installing the NetView Management Console Topology Console....................................................... 37
Verifying the NetView Management Console Installation........................................................................ 37
Starting the Topology Server................................................................................................................37
Begin Communication with the NetView Management Console Topology Server............................. 37
Starting the Topology Console............................................................................................................. 37
Signing On to the NetView Management Console Topology Console................................................. 38
Customizing the NetView Management Console................................................................................ 38

Chapter 5. Installing and Configuring SNA Topology Manager Agents.................... 39

VTAM Setup................................................................................................................................................39
Planning for Implementation of Topology Monitoring in Your Network...................................................39

Chapter 6. Preparing and Activating the SNA Topology Manager............................41

VTAM Setup................................................................................................................................................41
Security Considerations.............................................................................................................................41
Automation Options...................................................................................................................................41
Initialization File........................................................................................................................................ 41
Starting the SNA Topology Manager..........................................................................................................42
Verifying the SNA Topology Manager Installation.................................................................................... 42

Chapter 7. Installing and Configuring MultiSystem Manager Agents...................... 45

Role of the Topology Agent........................................................................................................................45
Installing Topology Agents........................................................................................................................ 45
Modifying Your Open Environment............................................................................................................46

Chapter 8. Preparing and Activating the MultiSystem Manager..............................47

How MultiSystem Manager Communicates with Your Networks............................................................. 47
Modifying Your MVS Environment............................................................................................................. 49
Modifying the NetView SNMP Trap Receiver Task.................................................................................... 49
Modifying Your NetView Start Procedure..................................................................................................50
Security Considerations.............................................................................................................................50
RODM Access....................................................................................................................................... 50
Command Authorization...................................................................................................................... 50
Implementing Span of Control.............................................................................................................51
Automation Options...................................................................................................................................51
Automation Table Automation............................................................................................................. 52
AON Automation...................................................................................................................................52
RODM Automation................................................................................................................................52
Assigning Operator Profiles to Autotasks..................................................................................................52
Initialization Files.......................................................................................................................................52
Setting Up Your NetView Cross-Domain Environment............................................................................. 54
RUNCMD Considerations........................................................................................................................... 55
Setting the RUNCMD Timeout Value....................................................................................................55
Allocating Additional NetView DSRBs................................................................................................. 55
Modifying the NetView RATE and AUTORATE Statements....................................................................... 56

iv
 Tuning the REXX Environment...................................................................................................................56
Starting MultiSystem Manager ................................................................................................................. 56
Initializing Network Topology and Status............................................................................................56
Processing Topology Requests............................................................................................................ 58
Verifying the MultiSystem Manager Installation....................................................................................... 59
Creating Applications to Manage New Topologies....................................................................................59
Creating Workstation Topology Agents................................................................................................59
Creating MVS Topology Managers........................................................................................................60
Documentation and Tools.................................................................................................................... 60

Chapter 9. Preparing and Activating the NetView Resource Manager.....................61

Defining the NetView Resource Manager Autotask.................................................................................. 61
Security Considerations.............................................................................................................................61
RODM Access....................................................................................................................................... 61
Command Authorization...................................................................................................................... 62
Initialization Considerations......................................................................................................................63
Sampling............................................................................................................................................... 63
Display Status Defaults........................................................................................................................ 63
Monitoring Remote NetView Systems................................................................................................. 63
Starting the NetView Resource Manager.................................................................................................. 64
Verifying the NetView Resource Manager Installation............................................................................. 64

Chapter 10. Preparing and Activating the Discovery Manager................................67

Security Considerations.............................................................................................................................67
RODM Access....................................................................................................................................... 67
Command Authorization...................................................................................................................... 67
Initialization and Operational Considerations.......................................................................................... 68

Chapter 11. Managing Views................................................................................ 69

Types of Views........................................................................................................................................... 69
Restricting Access to Views.......................................................................................................................70
Applying Policy to Views............................................................................................................................ 71
Correlating Views....................................................................................................................................... 71
Enabling SNA Topology Manager Object Correlation.......................................................................... 71
Enabling Object Correlation for Additional SNA Topology Manager and GMFHS Resources.............72
Tools for Managing Views.......................................................................................................................... 72
RODMVIEW...........................................................................................................................................72
RODM Unloader.................................................................................................................................... 72
FLCARODM............................................................................................................................................72
RODM Collection Manager................................................................................................................... 73
BLDVIEWS............................................................................................................................................ 73
DELVIEWS.............................................................................................................................................74

Appendix A. SNA Definitions for the NetView Management Console Topology

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

Appendix B. NetView Graphics Samples...............................................................83

GMFHS Samples........................................................................................................................................ 83
MultiSystem Manager and Agent Samples............................................................................................... 84
MultiSystem Manager Samples............................................................................................................84
IBM Tivoli Network Manager Topology Samples.................................................................................87
Open Topology Samples.......................................................................................................................87

v
 NetView Management Console Samples.................................................................................................. 88
NetView Resource Manager Samples....................................................................................................... 89
RODM Samples.......................................................................................................................................... 90
FLCARODM Samples............................................................................................................................ 99
SNA Topology Manager Samples............................................................................................................ 100

Appendix C. Customizing the MultiSystem Manager Initialization Statements..... 105

Sample Files.............................................................................................................................................105
Defining RODM to MultiSystem Manager................................................................................................ 105
Defining the RUNCMD Retry Count......................................................................................................... 106
Defining the Default Autotask................................................................................................................. 106
Defining Exception Views........................................................................................................................ 106
Defining Service Points............................................................................................................................ 106
Specifying the SP Parameter for the TCP/IP Protocol.......................................................................107
Specifying the SP Parameter for the SNA Protocol........................................................................... 107
Additional GETTOPO Parameters............................................................................................................108
HEARTBEAT Parameter......................................................................................................................108
Additional Parameters for IBM Tivoli Network Manager.................................................................. 108
Additional Parameters for the Open Topology Interface.................................................................. 109
Defining NetView Management Console Views and Objects..................................................................109
Network Views................................................................................................................................... 109
Network Objects.................................................................................................................................112
Network Configurations and Views......................................................................................................... 114
Working with Networks...................................................................................................................... 114
A Network Aggregate......................................................................................................................... 115
Displaying a New View and a Network Aggregate.............................................................................116
Displaying an Individual Network......................................................................................................117
Naming an Individual Network.......................................................................................................... 118

Appendix D. Global Variables for MultiSystem Manager...................................... 121

Notices..............................................................................................................125
Programming Interfaces..........................................................................................................................126
Trademarks.............................................................................................................................................. 126
Privacy policy considerations.................................................................................................................. 126

Index................................................................................................................ 129

vi
Figures

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

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

3. GMFHS Status Command Results...............................................................................................................27

4. NetView Management Console Overview...................................................................................................29

5. TOPOSNA QUERYDEF Command Results...................................................................................................43

6. Communication between MultiSystem Manager and Topology Agents.................................................... 48

7. MultiSystem Manager Environment with IP Connection............................................................................49

8. Collapsed View Tree.................................................................................................................................... 70

9. Expanded View Tree....................................................................................................................................70

10. Coding the SP and REMOTE Parameters................................................................................................107

11. NetView Management Console Details.................................................................................................. 110

12. NetView Management Console Default Network View (MultiSysView) Example................................. 110

13. NetView Management Console Details Example 2................................................................................111

14. NetView Management Console Details Example 3................................................................................111

15. NetView Management Console Default Network Object Examples...................................................... 112

16. NetView Management Console Details Window.................................................................................... 114

17. NetView Management Console Window................................................................................................ 115

18. NetView Management Console Network View Window........................................................................ 116

19. NetView Management Console Window with Test_View Added........................................................... 117

20. NetView Management Console Network Views Window.......................................................................118

21. NetView Management Console Network Views Window.......................................................................119

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, 2019 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.
• Using Tivoli System Automation for GDPS/PPRC HyperSwap Manager with NetView, GI11-4704, provides
information about the Tivoli® System Automation for GDPS®/PPRC HyperSwap® Manager with NetView
feature, which supports the GDPS and Peer-to-Peer Remote Copy (PPRC) HyperSwap Manager services
offering.
• 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), SNA topology manager, 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.
• SNA Topology Manager Implementation Guide, SC27-2864, describes planning for and implementing
the NetView SNA topology manager, which can be used to manage subarea, Advanced Peer-to-Peer
Networking, and TN3270 resources.
• 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/
us-en/marketplace/ibm-tivoli-netview-for-zos.
For information about the NetView Bridge function, see Tivoli NetView for OS/390® Bridge Implementation,
SC31-8238-03 (available only in the V1R4 library).

x IBM Z NetView: Installation: Configuring Graphical Components

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
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 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/support/knowledgecenter. 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.

About this publication xi

Ordering publications
You can order many Tivoli 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
In other countries, contact your software account representative to order Tivoli 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.

Tivoli user groups

Tivoli user groups are independent, user-run membership organizations that provide Tivoli users with
information to assist them in the implementation of Tivoli Software solutions. Through these groups,
members can share information and learn from the knowledge and experience of other Tivoli users.

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:

xii IBM Z NetView: Installation: Configuring Graphical Components

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

Symbols
The following symbols are used in syntax diagrams:

Marks the beginning of the command syntax.

About this publication xiii

 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.
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 xvi.
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.

xiv IBM Z NetView: Installation: Configuring Graphical Components

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 xv
• “Optional syntax elements” on page xv
• “Default keywords and values” on page xv
• “Multiple operands or values” on page xvi
• “Syntax that is longer than one line” on page xvi
• “Syntax fragments” on page xvi

Required syntax elements

Required keywords and variables are shown on the main syntax line. You must code required keywords
and variables.
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.

About this publication xv

 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.
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 SNA topology manager component and the NetView
management console to manage SNA resources. GMFHS works with the MultiSystem Manager component
and the NetView management console to manage non-SNA resources. 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 9

Managing SNA Resources with the SNA Topology Manager

The SNA topology manager functions for managing SNA and Advanced Peer-to-Peer Networking (APPN)
network environments include collection of subarea and APPN network, local, and LU status and topology.
These functions provide:
• Collection and storage of topology data, including real-time updates, in the RODM data cache
• Dynamic graphical display of topology and status
VTAM includes an agent that gathers topology information about APPN network nodes, APPN end nodes,
and the subarea network. The SNA topology manager uses CMIP services to communicate with the VTAM

© Copyright IBM Corp. 2001, 2019 1

 topology agent when collecting this topology information. Communication between the manager and
agent applications is over LU 6.2 sessions that are using:
• OSI common management information protocols (CMIP)
• SNA multiple-domain support (MDS)
The manager applications can retrieve information from multiple agent applications. In addition, the
agent applications can forward data to multiple managers (for example, if there is another NetView
system in the network with the SNA topology manager installed).

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

Installing SNA topology manager Chapter 6, “Preparing and Activating the SNA
Topology Manager,” on page 41
Installing SNA topology manager agents Chapter 5, “Installing and Configuring SNA
Topology Manager Agents,” on page 39

Managing Non-SNA Resources with MultiSystem Manager

MultiSystem Manager is a NetView application that provides dynamic topology and status data in RODM
for management of non-SNA domains. Agents are supported for the following network environments:
• Internet protocol (IP) networks managed by IBM Tivoli Network Manager
• Other types of networks that use Open topology agents
MultiSystem Manager topology manager uses the GETTOPO command to request topology information
and resource status from its agents. This topology and status information is stored in RODM. As topology
and status changes occur, these agents notify the MultiSystem Manager topology manager, which updates
RODM.
MultiSystem Manager simplifies the task of network management by using the power of the Z NetView
program to centrally manage your network resources.
Use the MultiSystem Manager features to manage the following types of networks:
• IP networks managed by IBM Tivoli Network Manager
• Any network supported by MultiSystem Manager Open topology agents
MultiSystem Manager provides an integrated and centralized network management facility so that you
can manage your networks from a NetView management console workstation. MultiSystem Manager
provides the following benefits:
• Dynamic topology and status discovery of your networks
• Instant access to graphical views of the topology and status of your networks, all from a single NetView
management console workstation
• Quick notification of changes in network topology and status:
– A node is down
– A node joined the network
– A monitored adapter is not responding
– A bridge is off line
• The ability to send commands to network resources simply by selecting the resource in a NetView
management console view and then selecting the command from a pull-down menu
• The ability to integrate the management of various types of networks
• The ability provided with the Open feature for you or a vendor to create a topology agent that manages
and monitors your resources

2 IBM Z NetView: Installation: Configuring Graphical Components

 If you want information about... Refer to...
Installing MultiSystem Manager “Initialization Files” on page 52
Installing MultiSystem Manager agents Chapter 7, “Installing and Configuring MultiSystem
Manager Agents,” on page 45

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.
• 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.

Chapter 1. Introduction 3
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
• Updating the RODM load utility job to include the MultiSystem Manager data model
• Updating the RODM load utility job to include the SNA topology manager 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:
• 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
• Installing the appropriate MultiSystem Manager topology agents
• Preparing the security system for the MultiSystem Manager
• Preparing REXX for MultiSystem Manager
• Preparing the MultiSystem Manager initialization file statements
5. Optional: Prepare for managing SNA resources, which includes:
• Updating the CNMSTYLE member
• Preparing VTAM for the SNA topology manager
• Preparing the security system for the SNA topology manager
• Preparing the SNA topology manager initialization file FLBSYSD
6. 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
7. Optional: Prepare for managing discovery manager resources, which includes:
• Updating the CNMSTYLE member

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:

TOWER Description
MSM Enables the MultiSystem Manager
Graphics Enables graphics

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. For the MultiSystem
Manager and the SNA topology manager, you must also enable the subtowers.

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

CNMSTYLE statements IBM Z NetView Administration Reference and IBM Z
NetView Installation: Getting Started
MultiSystem Manager “Enabling MultiSystem Manager” on page 6
SNA topology manager “Enabling SNA Topology Manager” on page 6

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:

© Copyright IBM Corp. 2001, 2019 5

 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.

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 SNA Topology Manager

When the TOWER statement is enabled for Graphics, the SNA topology manager is automatically enabled
and instructions are issued to start communication with the local VTAM agent.
SNATM is a subtower to the Graphics tower. If you are not using the SNA topology manager, type an
asterisk (*) before SNATM to disable this function:

TOWER.Graphics = *SNATM

Enabling MultiSystem Manager

To enable the MultiSystem Manager agents, copy the following CNMSTYLE statement to the CNMSTUSR or
CxxSTGEN member:

TOWER.MSM = ITNM OPN

Agent names preceded by an asterisk (*) are disabled. Remove or add asterisks as necessary to enable
the agents that you will use:
ITNM
IBM Tivoli Network Manager agent
OPN
Open agent
For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
Note: When the TOWER.MSM CNMSTYLE statement is enabled, the %INCLUDE statement for FLCSOPF
(used for operator profiles) is also enabled.

6 IBM Z NetView: Installation: Configuring Graphical Components

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.

Chapter 2. Enabling Graphics Support 7

8 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 9 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.V6R3USER.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 V6R3 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, 2019 9

 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

10 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 11

 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 11 or “Defining RODM Security to a
User-Defined Class” on page 11, 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.

12 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 12 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 13 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 13 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 13

 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)
• SNA topology manager
The SNA topology manager requires a minimum of RODM security level 5. The user ID to authorize is
APPNTM.
• 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)
– SNA topology manager
– 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.

14 IBM Z NetView: Installation: Configuring Graphical Components

 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.

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 16 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 16 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 15

 /********************************************************************/
/* 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:

16 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 17

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:

18 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 19

 – 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.

20 IBM Z NetView: Installation: Configuring Graphical Components

START
START EKGXRODM
. identifier

, TYPE = W , NAME = proc_name

, TYPE = W , NAME = rodmname

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 21

 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.

22 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 20. To verify the
RODM installation using job EKGSVER:
1. Edit the PARM statement in job EKGSVER in the NETVIEW.V6R3USER.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 23

 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:

24 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)
FLBTRDMx
SNA topology manager data model
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 83.
• 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 24.
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.

Chapter 3. Preparing and Activating RODM and GMFHS 25

 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

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.

26 IBM Z NetView: Installation: Configuring Graphical Components

 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.
• 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 27.

| 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 DUI4043I TYPE = MANAGER STATUS = ACTIVE SESSION =
SNA_Topology_Manager
E NTV6C DUI4037I END

Figure 3. GMFHS Status Command Results

Chapter 3. Preparing and Activating RODM and GMFHS 27

28 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 29.

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.

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.

© Copyright IBM Corp. 2001, 2019 29

 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 75 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:
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

30 IBM Z NetView: Installation: Configuring Graphical Components

 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/v6r3/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
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.

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 31
 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.
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.

32 IBM Z NetView: Installation: Configuring Graphical Components

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 33.
Otherwise see Appendix A, “SNA Definitions for the NetView Management Console Topology Servers,”
on page 75.
• See “Storing Topology Server Databases” on page 34.
• For Windows server users, see “Setting Security for Your Operating System” on page 35 and
“Configuring the Topology Server to Run as a Windows Service” on page 36.
• For AIX and Linux for zSeries server users, see “Configuring the Topology Server to Run as a UNIX
Daemon” on page 36.

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 77). 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
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:

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 33
 • 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:
• 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)

34 IBM Z NetView: Installation: Configuring Graphical Components

 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.

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:

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 35
 • 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 36 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:

$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.

36 IBM Z NetView: Installation: Configuring Graphical Components

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).

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.

Chapter 4. Installing and Configuring the NetView Management Console for Graphics 37
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

38 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 5. Installing and Configuring SNA Topology
Manager Agents

The key to SNA topology management is the SNA topology manager communication with Common
Management Information Protocol (CMIP) topology agents. Manager-to-agent communication is through
LU 6.2 sessions using the CMIP services component of VTAM and SNA MDS (Multiple Domain Support).
The VTAM topology agent is a standard component of VTAM. The agent collects topology and status data
for subarea and APPN resources.

VTAM Setup
Ensure that the VTAM procedure includes DD statements for ISTCMIP, ACYGDMO, and ISTASN1. In
addition, the VTAM CMIP agent must be started prior to the manager applications. At a minimum, this
requires the OSIMGMT start option in VTAM to be specified as YES. The NetView program issues the
appropriate MODIFY command to VTAM to enable the OSIMGMT option if the SNATM subtower is enabled
in the CNMSTYLE member.
VTAM agent local topology can report many switched logical lines and PUs. This can increase the network
traffic and the manager-to-agent work load. CMIP filtering provides improved control. CMIP filtering
allows an entire major node and all its subordinate lines and PUs to be suppressed (not reported in
local topology). To enable filtering, VTAM definitions for XCA, NCP, and SWNET nodes must include the
VTAMTOPO keyword.
Note: If an NCP major node is reported, its physical lines cannot be suppressed, but its switched logical
lines can be suppressed.
If you specify the VTAM start option MSGMOD, turn it off while running NetView command lists and
NetView automation.

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

VTAM requirements FLBSYSD initialization file (comments) or IBM Z
NetView SNA Topology Manager Implementation
Guide
VTAM CMIP services z/OS Communications Server library
ISTCMIP, ACYGDMO, and ISTASN1 statements z/OS Communications Server library

Planning for Implementation of Topology Monitoring in Your

Network
To plan for the implementation of topology monitoring in your network, perform the following steps:
1. Activate the SNA topology manager at focal points where RODM is installed.
2. Activate the VTAM topology agent on each VTAM node to manage SNA.

© Copyright IBM Corp. 2001, 2019 39

40 IBM Z NetView: Installation: Configuring Graphical Components
Chapter 6. Preparing and Activating the SNA
Topology Manager

This section describes the necessary steps to enable the SNA topology manager:
• “VTAM Setup” on page 41
• “Security Considerations” on page 41
• “Automation Options” on page 41
• “Initialization File” on page 41
It also describes how to start and verify the SNA topology manager.

VTAM Setup
VTAM needs APPL definitions for the SNA topology manager application. Sample definitions are included
in member A01APPLS (CNMS0013). The APPL name for the SNA topology manager must match the
APPLNAME specified in the VTAM section of the FLBSYSD initialization file used by the manager
application.

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

VTAM requirements FLBSYSD initialization file (comments) or IBM Z
NetView SNA Topology Manager Implementation
Guide

Security Considerations
The SNA topology manager requires that a user ID of APPNTM be defined to an SAF product, such as
RACF, and authorized to use RODM. This requires the use of the RACF ADDUSER and PERMIT commands.

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

RACF requirements IBM Z NetView Security Reference

Automation Options
The manager applications start automatically under standard NetView installation procedures. The VTAM
CMIP agent starts upon NetView initialization. The default automation table, DSITBL01, also starts
automation for the managers (FLBAUT).

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

Automation options IBM Z NetView SNA Topology Manager
Implementation Guide

Initialization File
The SNA topology manager is shipped with an initialization file (FLBSYSD) that you can use to tailor it
to your installation. This file contains the names of your RODM, the VTAM application names for the
managers, values for controlling automatic topology gathering, message suppression options, and other
customization information. In addition, three other files (FLBOSIDS, FLBSRT, and FLBEXV) can be used to
further customize SNA topology manager views.
The FLBSYSD initialization file is not refreshed until the topology manager is stopped and started again.

© Copyright IBM Corp. 2001, 2019 41

 The FLBOSIDS, FLBSRT, and FLBEXV customization files can be refreshed using the TOPOSNA REFRESH
command.
If symbolic substitution is enabled on your system, you can use symbols in the initialization and
customization files. Ensure that the symbols are defined in member IEASYMxx of SYS1.PARMLIB.
Note: Data REXX is not supported in the initialization and customization files.

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

Customizing the initialization files IBM Z NetView SNA Topology Manager
Implementation Guide

Starting the SNA Topology Manager

If you updated the CNMSTYLE member as described in Chapter 1, “Introduction,” on page 1, the SNA
topology manager automatically starts when the NetView program is started. To verify this, use the
following procedures:
• The VTAM CMIP services must be active.
To see if the agent is active, type the following command:

D NET,VTAMOPTS

and search for:

OSIMGMT=YES

• The FLBTOPO autotask must be active.

To see if it is active, type the following command:

LIST FLBTOPO

If it is not active, enter the following command:

AUTOTASK OPID=FLBTOPO

Note: You can also issue the STARTCNM SNATM, STARTCNM GRAPHICS, or the STARTCNM ALL
command to start the SNA topology manager.

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

Enabling the SNA topology manager IBM Z NetView SNA Topology Manager
Implementation Guide
STARTCNM command HELP STARTCNM (online help)

Verifying the SNA Topology Manager Installation

The procedures in this section help you verify that the SNA topology manager functions are installed
correctly. Certain commands can be issued even if the agents are not started; these commands verify that
the manager code is properly installed.
When the topology manager is active, you can use the following commands to control the collection of
SNA subarea information.

Command Use
TOPOSNA CRITICAL Monitor critical LU or CDRSC
TOPOSNA LISTPOOL Display internal storage pool statistics

42 IBM Z NetView: Installation: Configuring Graphical Components

Command Use
TOPOSNA LISTREQS Display status of pending requests
TOPOSNA LISTRODM Display RODM activity and object counts
TOPOSNA LISTSTOR Display storage usage counts
TOPOSNA MONITOR Start monitoring topology
TOPOSNA PURGE Delete expired unreachable resources from RODM
TOPOSNA QUERYDEF Display current default settings
TOPOSNA REFRESH Change the defaults that are provided with the NetView program
TOPOSNA SETDEFS Modify defaults
TOPOSNA STOP Stop monitoring topology
TOPOSNA STOPMGR Stop the topology manager
TOPOSNA TRACE Control tracing

To begin verifying the topology manager host installation, issue the TOPOSNA QUERYDEF command. You
will receive a response similar to that shown in Figure 5 on page 43.

NCCF NetView NTVE9 NETOP1 2/1/01 08:17:32

* NTVE9 TOPOSNA QUERYDEF
- NTVE9 FLB494I SNA TOPOLOGY MANAGER DEFAULT SETTINGS FOLLOW:
- NTVE9 FLB495I MONITOR SNA LOCAL TOPOLOGY FOR NEW NETWORK NODES : NO
- NTVE9 FLB496I MONITOR SNA LOCAL TOPOLOGY FOR NEW END NODES : NO
- NTVE9 FLB650I MONITOR SNA NETWORK TOPOLOGY FOR NEW T5 NODES : NO
- NTVE9 FLB651I MONITOR SNA LOCAL TOPOLOGY FOR NEW T5 NODES : NO
- NTVE9 FLB497I SNA NETWORK TOPOLOGY IMMEDIATE RETRY INTERVAL : 60
- NTVE9 FLB498I SNA NETWORK TOPOLOGY IMMEDIATE RETRY LIMIT : 5
- NTVE9 FLB499I SNA NETWORK TOPOLOGY LONG-TERM RETRY INTERVAL : 1800
- NTVE9 FLB500I SNA NETWORK TOPOLOGY LONG-TERM RETRY LIMIT : 48
- NTVE9 FLB501I SNA LOCAL TOPOLOGY IMMEDIATE RETRY INTERVAL : 60
- NTVE9 FLB502I SNA LOCAL TOPOLOGY IMMEDIATE RETRY LIMIT : 5
- NTVE9 FLB503I SNA LOCAL TOPOLOGY LONG-TERM RETRY INTERVAL : 1800
- NTVE9 FLB504I SNA LOCAL TOPOLOGY LONG-TERM RETRY LIMIT : 48
- NTVE9 FLB546I SNA LU COLLECTION IMMEDIATE RETRY INTERVAL : 60
- NTVE9 FLB547I SNA LU COLLECTION IMMEDIATE RETRY LIMIT : 5
- NTVE9 FLB548I SNA LU COLLECTION LONG-TERM RETRY INTERVAL : 1800
- NTVE9 FLB549I SNA LU COLLECTION LONG-TERM RETRY LIMIT : 48
- NTVE9 FLB411I TOPOSNA QUERYDEF COMMAND COMPLETED SUCCESSFULLY

Figure 5. TOPOSNA QUERYDEF Command Results

If an agent is running in the network, issue the TOPOSNA MONITOR command to start monitoring at
the agent node. This command verifies that communication between the manager and agent is working
properly. Issue the TOPOSNA STOP command to stop monitoring at the agent node.
For detailed user scenarios for the topology function, refer to the IBM Z NetView SNA Topology Manager
Implementation Guide.
Access the first SNA topology manager view (from the NetView management console) to verify that RODM
has been loaded correctly.
From the NetView management console tree view, select SuperclusterView. This opens a view of the NN
domain network cluster object and verifies that the topology data model files is loaded correctly.
At this point, no further navigation is possible because RODM does not yet contain SNA resource objects
for monitoring (unless you issued the TOPOSNA MONITOR command to start monitoring). You have two
options for creating resources in RODM:
• Load the APPN sample network.

Chapter 6. Preparing and Activating the SNA Topology Manager 43

 This option provides you and your operators an opportunity to gain experience with the topology
manager in a test environment. The sample network is designed so you can simulate dynamic addition
of resources in the network and gain familiarity with APPN views. Command actions against resources
(such as activating or recycling) are not available because it is a sample network.
For scenarios describing how to load and use this sample network, refer to the IBM Z NetView SNA
Topology Manager Implementation Guide.
• Start monitoring the SNA topology from agents in your network.
This option loads RODM with the actual resources from your network. See the NetView online help for
information about using the TOPOSNA MONITOR command to start monitoring agents in your network.

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

TOPOSNA command HELP TOPOSNA (online help)

44 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 7. Installing and Configuring MultiSystem
Manager Agents

Topology agents are supported for the following network environments:

• IP networks managed by IBM Tivoli Network Manager
• Other types of networks that use Open topology agents
If you are using MultiSystem Manager to manage workstations in your network, you need to install the
topology agent on a service point workstation. A service point workstation can be any workstation in your
distributed network that is running the topology agent and associated applications required for managing
the distributed network.

Role of the Topology Agent

The run time and installation characteristics of the topology agents are dependent upon the operating
system on which they run.
Each of the MultiSystem Manager features require that you install the topology agent on the service point.
The role of the topology agent residing on the service point is to monitor the network in which it resides
and to dynamically communicate information about changes in network topology or resource status to the
topology manager.
When the topology manager issues a command to gather topology and status, the topology agent collects
the information and sends it back as part of the command's response.
The topology agent sends an alert or resolution to the topology manager to indicate changes in topology
and status.
The topology manager updates the status of the resource in RODM and reflects this status change in your
NetView management console views. Alerts and resolutions are then stored in the event viewer for the
resource and can be displayed on your NetView management console workstation.
The Z NetView program provides the capability to manage these types of networks:
• IP networks managed by IBM Tivoli Network Manager. These are described in more detail in IBM Z
NetView IP Management.
• Other types of networks that use the Open topology agent. This is described in more detail in IBM Z
NetView User's Guide: NetView Management Console.

Installing Topology Agents

Topology agents for MultiSystem Manager are available in a variety of formats:
DVD
This format enables installation using the following platform-specific methods:
Windows
InstallShield to install and uninstall
AIX
Installp format (SMIT) to install and uninstall
Linux
Package format (rpm) to install and uninstall
The readme documentation is located in the README\language subdirectory, where language
specifies the language. For example, US-English is ENU.

© Copyright IBM Corp. 2001, 2019 45

 IBM Web site
Contains the same data formats as the DVD. This contains the latest version of the workstation-based
code for downloading.
The following table identifies readme file names and installation methods associated with the
workstation-based components.

Table 3. Readme Files and Installation Methods for Workstation Components

IBM
Component Name DVD Web Readme File
MultiSystem Manager IBM Tivoli Network x x msm_nm_ip_readme_en.html
Manager agent
MultiSystem Manager Open agent x x Included with the vendor-supplied
topology agent

Install the topology agent on the service point workstation. Refer to the readme files for specific
installation instructions.
Open agents can be written by customers or provided by vendors.
Documentation and tools for building a MultiSystem Manager Open Topology Interface agent application
can be downloaded from the NetView support Web page. For more information about downloads for the
NetView program, see Downloads.

Modifying Your Open Environment

The modifications needed for a particular network of distributed resources depends on the requirements
of the vendor-supplied topology agent managing that network. For information about topology agent
requirements, see the documentation that is provided with your topology agent.

46 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 8. Preparing and Activating the MultiSystem
Manager

The following actions are necessary to enable MultiSystem Manager:

• “Modifying Your MVS Environment” on page 49
• “Modifying Your NetView Start Procedure” on page 50
• “Security Considerations” on page 50
• “Automation Options” on page 51
• “Assigning Operator Profiles to Autotasks” on page 52
• “Initialization Files” on page 52
• “Setting Up Your NetView Cross-Domain Environment” on page 54
• “RUNCMD Considerations” on page 55
• “Modifying the NetView RATE and AUTORATE Statements” on page 56
• “Starting MultiSystem Manager ” on page 56
• “Verifying the MultiSystem Manager Installation” on page 59

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

Using MultiSystem Manager IBM Z NetView User's Guide: NetView Management
Console and IBM Z NetView IP Management

How MultiSystem Manager Communicates with Your Networks

MultiSystem Manager uses a topology manager-topology agent relationship to manage your network
resources. MultiSystem Manager provides a topology manager, which runs on the NetView program. The
topology agent resides in the managed environment and is responsible for forwarding topology and status
for all managed network resources to the topology manager.
To monitor and manage your networks, the topology manager performs the following functions:
• Dynamically discovers the topology and status and stores it in RODM
• Processes the topology and status updates from the topology agents
• Integrates with Automated Operations Network (AON) to automate recovery of failing resources
• Provides an easy-to-use command interface based on Distributed Manager Command Support (DMCS)
The topology manager begins the process of network management by dynamically discovering the initial
topology and status of the resources in your network and storing this information in RODM. After the
information is in RODM, you can view your network resources from your NetView management console
workstation.
After MultiSystem Manager is initialized and the initial topology and status of the network is stored
in RODM, the topology manager keeps topology and status up-to-date by receiving updates from the
topology agents. The status changes are reflected in your views, and alerts are stored in the NetView
management console event viewer.
MultiSystem Manager provides an easy-to-use command interface, distributed manager command
support (DMCS), that can be used to send commands to the topology agents. DMCS automatically
retrieves RODM information that is required to send the command. DMCS can be used in an
automation routine, from the NetView operator command line, or from the NetView management console
workstation.

© Copyright IBM Corp. 2001, 2019 47

 The topology manager sends queries and commands to the topology agents. Topology agents use alerts
and command responses to communicate with the topology manager. Alerts and resolutions are received
by the NetView automation table and processed by the topology manager. Figure 6 on page 48 shows
topology manager and agent communications.

Figure 6. Communication between MultiSystem Manager and Topology Agents

The topology manager can use SNA LU 6.2, SNA SSCP-PU, or IP sessions to communicate with a topology
agent, depending on the agent. If using SNA sessions, the topology manager uses NetView RUNCMD and
RMTCMD commands over SNA sessions to communicate with the topology agents. If using IP sessions,
the topology manager uses commands over IP sessions.
For SNA communications, the service point is the LU or PU of the workstation that communicates with the
topology manager. For IP communications, the service point is the IP host name of the workstation that
communicates with the topology manager.
Note: In this book, the term service point includes the topology agents that are communicating with
topology managers using TCP/IP.
Figure 7 on page 49 shows the MultiSystem Manager feature that uses an IP communication protocol.

48 IBM Z NetView: Installation: Configuring Graphical Components

 Figure 7. MultiSystem Manager Environment with IP Connection

Modifying Your MVS Environment

All data sets in the NetView STEPLIB DD concatenation must be authorized for NetView initialization.
Use the Authorized Program Facility (APF) to authorize the REXX data set (SEAGLPA for the REXX/370
runtime library or SEAGALT for the REXX alternate library). To be authorized, a library's name must appear
in the list of authorized libraries for the APF member (IEAAPFxx) of SYS1.PARMLIB. Refer to the MVS
library for more information about APF authorization.
If you previously ran MultiSystem Manager on this system, the REXX data set might already be authorized.
Changes to the APF member do not take effect until you restart MVS or dynamically update the APF
member by using the MVS SETPROG command.
1. To authorize the REXX data set (SEAGLPA or SEAGALT), edit your APF member in SYS1.PARMLIB and
add the REXX data set (SEAGLPA or SEAGALT).
2. Restart MVS, if necessary.
If your system is set up to use dynamic APF services, you can avoid restarting MVS by using the
SETPROG command to dynamically update the APF list.

Modifying the NetView SNMP Trap Receiver Task

If you are using the MultiSystem Manager IBM Tivoli Network Manager agent, the NetView SNMP trap
receiver task is used to receive status update traps that are sent from IBM Tivoli Network Manager
through Netcool/OMNIbus Gateway for SNMP.
Traps can be sent from the SNMP Gateway with either the UDP or TCP protocol. In either case, the port
number of the port on which the NetView SNMP trap receiver task is listening for that protocol must be
specified. The protocol and port that are used must match between the NetView SNMP trap receiver task
and the SNMP Gateway.

Chapter 8. Preparing and Activating the MultiSystem Manager 49

 To create a NetView trap receiver task, see the comments in the CNMSTYLE member. The protocol and
port are specified with the TCPPORT and the UDPPORT parameters.
If you are using the default MultiSystem Manager configuration files for the SNMP Gateway, the
transport protocol and port are configured in the MSM_snmp.conf file. The protocol is defined by the
Gate.SNMP.protocol parameter, and the port is specified on the Gate.SNMP.Gateway parameter.
You can further configure the communications that are used to send traps from Netcool/OMNIbus
Gateway for SNMP to the Z NetView program, for example, the version of SNMP can be set to V3, and
security can be configured.

Modifying Your NetView Start Procedure

If you are using TCP/IP to communicate between the Z NetView program and MultiSystem Manager agent,
refer to IBM Z NetView Installation: Getting Started.
The REXX programs for several NetView components, including the MultiSystem Manager, have been
compiled with the ALTERNATE option.
If you access the REXX runtime library from the NetView program, MultiSystem Manager REXX programs
run in compiled mode. Otherwise, the REXX alternate library is used and MultiSystem Manager REXX
programs run in interpreted mode.
If the REXX runtime library or REXX alternate library is not accessible from the pageable link pack area
(PLPA), modify the NetView start procedure to access one of these libraries. For more information about
REXX library usage, refer to IBM Z NetView Installation: Getting Started.

Security Considerations
Consider the following aspects of security for MultiSystem Manager:
• “RODM Access” on page 50
• “Command Authorization” on page 50

RODM Access
You can add to your network security by authorizing access to RODM. By defining the application ID to an
SAF product, such as RACF, you can verify security levels for API calls into RODM. With a security level of
3, you can connect, disconnect, query, create objects, delete objects, change fields, and so on. You cannot
use it to create classes, create fields, delete classes, delete fields, and so on.
Add the RODM user application ID to RACF or another security system with a security level of 3. The
RODM user application ID is specified by the common.FLC_RODMAPPL statement in the CNMSTYLE
member. The default value for MultiSystem Manager is your NetView domain ID concatenated with the
letters MSM, for example, CNM01MSM.

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

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

Command Authorization
The command definition statements in CNMCMENT define the MultiSystem Manager command
procedures.
Note: If you modify the CNMCMD member or any of the members included by CNMCMD, restart the
NetView program so that the changes take effect.
To implement command authorization checking:
1. To restrict the use of MultiSystem Manager commands to specific operators, modify the command
authorization as described in IBM Z NetView Administration Reference.

50 IBM Z NetView: Installation: Configuring Graphical Components

 The CMDDEF 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. Ensure that the following commands can be issued by the same operators who can issue GETTOPO
commands:
EXCMD
RUNCMD or RMTCMD, depending on your system
3. You can have command authorization performed on the keywords and values of the FLCARODM
command.
If you are using the CMDAUTH table or the System Authorization Facility (SAF), use the NetView
SECMIGR command to migrate these definitions. Refer to the IBM Z NetView Administration Reference
for more information.

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

Command authorization IBM Z NetView Security Reference

Implementing Span of Control

Span of control provides a means to control access to particular resources and views. Use the NetView
span table to implement span of control. MultiSystem Manager fills in the UserSpanName field in RODM
whenever a viewable object is created. The UserSpanName is composed, when available, of the following
parts (in order):
• service point
• application
• element (if any)
• object specific data
To modify the operator profiles, edit member FLCSPRFB, which is shipped in the DSIPRF data set. Specify
CTL=SPECIFIC or CTL=GENERAL on the AUTH statement.
The following example shows how operator profile FLCSPRFB can be modified for span of control:

FLCSPRFB PROFILE
AUTH MSGRECVR=NO,CTL=GENERAL
ISPAN SPAN1,SPAN2
END

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

Operator profiles IBM Z NetView Security Reference
Span of control IBM Z NetView Security Reference
Examples of UserSpanName IBM Z NetView Data Model Reference

Automation Options
MultiSystem Manager provides automation statements for each of its features. These statements
allow for automation of alerts and resolutions sent to the NetView program by the topology agent.
MultiSystem Manager automation statements are included before any GMFHS automation statements and
are controlled by the MSM tower and MSM subtower statements specified in the CNMSTYLE member.
The following automation statement is controlled by the GRAPHICS tower specification in the CNMSTYLE
member:

IF (MSUSEG(0000) ¬= '' | MSUSEG(0002) ¬= '') & HIER ¬= ''

THEN EXEC(CMD('DUIFECMV') ROUTE(ONE DUIFEAUT)) CONTINUE(Y);

Chapter 8. Preparing and Activating the MultiSystem Manager 51

 During GMFHS initialization, the topology agent can send alerts to the NetView program before GMFHS
has completed initialization. If these alerts arrive before GMFHS is initialized, they are not processed by
GMFHS. As a result, the status of MultiSystem Manager objects is not automatically updated during this
period. The automation statements provided in DSITBL01 generate a message when GMFHS is initialized.
You can use MultiSystem Manager to automate many network management procedures. In general, there
are three types of automation: automation table, AON, and RODM.

Automation Table Automation

This type of automation is based on user-written applications that react to information received by
the NetView program from the topology agents. MultiSystem Manager adds statements to the NetView
automation table to capture alerts and resolutions, and messages to react to them. The NetView
automation table provides this information for user-written programs. You can also add statements to
the NetView automation table, enabling you to receive updates from the topology agents.

AON Automation
MultiSystem Manager has been integrated with Automated Operations Network using AON policy to
recover failing resources. For more information, refer to the IBM Z NetView User's Guide: Automated
Operations Network.

RODM Automation
This type of automation is based on applications that access information stored in RODM. RODM
automation applications can process within RODM, using RODM methods, or externally using MultiSystem
Manager Access or the RODM API. You can write automation applications that react to status changes
made by MultiSystem Manager alert processing. You can also write applications that correlate resources
reported upon by different topology managers. These applications can react to problems affecting
multiple resources, which might have been reported in multiple alerts.
Note: An example of a topology manager, other than MultiSystem Manager, is the SNA topology manager.
MultiSystem Manager uses RODM-based automation and the topology correlation function to dynamically
correlate different managed resources to the same aggregate objects.

Assigning Operator Profiles to Autotasks

Autotasks are driven by the NetView automation table when processing alerts and resolutions from the
topology agents.
Autotasks must be created for each of the MultiSystem Manager agents to distribute the SNA and TCP/IP
work load across different tasks in the NetView program. These autotasks can be specified on the
AUTOTASK parameter on GETTOPO commands or on the GETTOPO statements in the initialization file.
If you modify the operator profile or member DSIOPF, restart the NetView program or issue the REFRESH
OPERS command from the NetView command line to activate the changes.
1. Add autotasks to FLCSOPF as needed to distribute the workload across tasks.
Note: FLCSPRFB in DSIPRF is the sample operator profile used by the autotasks that are added for
each MultiSystem Manager agent.
2. Change the passwords shipped in the sample file.

Initialization Files
There are two categories of MultiSystem Manager initialization file statements:
• General
• Agent-specific

52 IBM Z NetView: Installation: Configuring Graphical Components

General statements define various aspects of your system and network environment to MultiSystem
Manager. They define system defaults, information about the RODM used, and information about your
networking environment. General statements are specified in the CNMSTYLE member.
GETTOPO RES and ONLY statements are agent-specific. They are used to define service points to
MultiSystem Manager during initialization. GETTOPO statements are specified in the MultiSystem
Manager initialization file. GETTOPO statements are thoroughly documented in the online help and in
the IBM Z NetView Command Reference Volume 2 (O-Z). GETTOPO statements can be specified in the
MultiSystem Manager initialization file if you want to retrieve topology and status of your managed
network during MultiSystem Manager initialization.
The following initialization statements are required and are specified in the CNMSTYLE member:
• (MSM)function.autotask.MSMdefault
• COMMON.FLC_RODMNAME
• COMMON.FLC_RODMAPPL
If you do not include other general statements, default values are used.
If you do not include GETTOPO statements in the initialization file, MultiSystem Manager is enabled, but
topology and status information is not initially stored in RODM when you issue an INITTOPO command.
Topology and status information is retrieved only when GETTOPO commands are later issued or when
alerts are received.
If you include GETTOPO statements in the initialization file, MultiSystem Manager is enabled and
topology and status information is retrieved from the specified service points and added to RODM during
MultiSystem Manager initialization.
MultiSystem Manager provides a sample initialization file that resides in the DSIPARM data set. This file,
which is named FLCAINP, contains %INCLUDE statements for each of the MultiSystem Manager agents,
shown in Table 4 on page 53.

Table 4. MultiSystem Manager Agent Sample Initialization Files

MultiSystem Manager Agent Sample Initialization File
IBM Tivoli Network Manager FLCSITNM
Open Topology Interface FLCSIOPN

Use the DISPTOPO command to display some of the general information that is defined by the statements
in the CNMSTYLE member. If you change a CNMSTYLE statement, issue the RESTYLE COMMON
command, followed by the INITTOPO command, to inform MultiSystem Manager of the changes.
See “Issuing the INITTOPO Command” on page 57 for instructions and examples about coding the
initialization statements. See the IBM Z NetView Resource Object Data Manager and GMFHS Programmer's
Guide for details on RODM.
GETTOPO RES or GETTOPO ONLY statements describe specific information about a MultiSystem Manager
feature that is managing a portion of your enterprise. Code one GETTOPO RES or GETTOPO ONLY
statement for each MultiSystem Manager feature that has an associated service point. GETTOPO
statements are specified in the MultiSystem Manager initialization file. For examples using GETTOPO RES
and ONLY, see “Network Configurations and Views” on page 114. For more information about GETTOPO
statements, see the online help or the IBM Z NetView Command Reference Volume 2 (O-Z). Table 5 on
page 53 lists the MultiSystem Manager features along with the GETTOPO RES and ONLY statements for
each.

Table 5. MultiSystem Manager Agent and GETTOPO Statements

MultiSystem Manager Feature GETTOPO RES and ONLY Statement
IBM Tivoli Network Manager GETTOPO ITNMRES, GETTOPO ITNMONLY
Open Topology Interface GETTOPO OPENRES

Chapter 8. Preparing and Activating the MultiSystem Manager 53

 GETTOPO statements consist of keyword parameters (KEYWORD=variable). Use the following syntax
rules for coding these statements:
• Start each statement on a separate line of the file.
• Separate keyword parameters by blanks or commas.
• Statements containing more than one keyword parameter can span multiple lines. If a statement spans
more than one line:
– Do not split entries in the middle of a keyword parameter.
– End each continued line with a comma.
– Do not end the last line with a comma.
• You can code the %INCLUDE statement. See the IBM Z NetView Administration Reference for
information about the %INCLUDE statement.
• Start comment lines with an asterisk (*) in column 1.

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

Initialization file statements Appendix C, “Customizing the MultiSystem
Manager Initialization Statements,” on page 105
GETTOPO command NetView online help or the IBM Z NetView
Command Reference Volume 2 (O-Z)

Setting Up Your NetView Cross-Domain Environment

Note: This step is for MultiSystem Manager agents that use SNA to communicate with the topology agent.
Perform this step only if you have service points that are not in the same domain as the NetView program
running MultiSystem Manager. Your cross-domain environment affects:
• Alerts and resolutions
• RMTCMD commands
• RUNCMD commands
Setting up your cross-domain environment enables MultiSystem Manager to send RUNCMD commands to,
and receive alerts and resolutions from, service points in other SNA domains.
1. If alerts from a service point are sent to a NetView program in a different domain, forward these alerts
to the NetView program running MultiSystem Manager.
You can forward all alerts and resolutions from one NetView program to another by issuing the
following command from the NetView program running MultiSystem Manager:

FOCALPT CHANGE FPCAT=ALERT TARGET=remote_domain

TARGNET=remote_netid

Specify the same values for remote_domain and remote_netid as specified for the REMOTE keyword
in the GETTOPO command. If remote_netid is not specified on the REMOTE keyword in the GETTOPO
command, then the TARGNET keyword can be omitted.
2. To ensure that RMTCMD commands work between the NetView program running MultiSystem
Manager and remote NetView programs, define dedicated autotasks at your remote NetView programs
specifically for this purpose.
The RMTCMD commands that are issued from MultiSystem Manager specify OPERID=*. Refer to IBM Z
NetView Command Reference Volume 1 (A-N) for more information about the RMTCMD command.
3. If the REMOTE parameter is used on the GETTOPO command for a service point, allocate additional
NetView DSRBs at the remote NetView domain.
4. If the REMOTE parameter is used on the GETTOPO command for a service point (meaning a RMTCMD
command is used to forward the RUNCMD command to another NetView domain), ensure that

54 IBM Z NetView: Installation: Configuring Graphical Components

 RMTCMD commands work from the NetView domain running MultiSystem Manager to the destination
NetView domain as specified in the REMOTE parameter of the GETTOPO command.
5. You might need to define the topology agent LU in a VTAM cross-domain resource (CDRSC) definition
in the domain running MultiSystem Manager. If you are using cross-network sessions, the CDRSC
definition might be needed in both networks.

RUNCMD Considerations
Note: This section is for MultiSystem Manager agents that use SNA to communicate with the topology
agent.
MultiSystem Manager uses RUNCMD commands to gather initial topology and status from topology agents
that use SNA to communicate with the NetView program.

Setting the RUNCMD Timeout Value

The RUNCMD timeout value specifies the amount of time to wait before a RUNCMD command is canceled.
To prevent RUNCMD commands from prematurely timing out, increase the timeout value.
The default value for RUNCMD timeout is stored in DSICTMOD. This value is assigned each time that the
NetView program is initialized. If you modify member DSICTMOD, restart the NetView program for the
changes to take effect.
Note: The RUNCMD timeout value is defined by the timeout value for Service Point Control Interface
commands in DSICTMOD.
If you previously installed a MultiSystem Manager topology agent on this system, the RUNCMD timeout
value might already be set to an appropriate value for your site.
1. Edit DSICTMOD and set the RUNCMD timeout value.
2. Assemble and link-edit DSICTMOD using job CNMS0055.
3. Restart the NetView program for these changes to take effect.
If you do not want to restart the NetView program at this time, specify the RUNCMD timeout value by
using the COSTIME keyword of the DEFAULTS command.

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

DEFAULTS command IBM Z NetView Command Reference Volume 1 (A-N)
Modifying the RUNCMD timeout value in IBM Z NetView Installation: Configuring Additional
DSICTMOD Components

Allocating Additional NetView DSRBs

Note: This step is for MultiSystem Manager agents that use SNA to communicate with the NetView
program.
DSRBs are used to store information about each RUNCMD request, and RUNCMD processing is managed
by the NetView DSIGDS task. If a RUNCMD request is made and there are no DSRBs available to task
DSIGDS, the RUNCMD request is queued.
Allocate additional DSRBs to minimize the queuing of these requests.
If your connection between the MultiSystem Manager topology manager and its topology agents is over an
SSCP-PU session, you might need to modify the NetView DSRB count for task DSIGDS:
1. Determine the DSRB allocation for task DSIGDS.
2. Edit the DSTINIT statement in NetView initialization member DSICPINT and modify the current DSRBO
value with the value that is appropriate for your site.
3. Stop and restart task DSIGDS.

Chapter 8. Preparing and Activating the MultiSystem Manager 55

 Notes:
1. Allocating additional DSRBs is not necessary if all of your sessions are LU 6.2 sessions.
2. If you have previously installed a MultiSystem Manager topology agent on this system, the DSRB count
for task DSIGDS might already be modified.

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

DSTINIT statements and DSICPINT IBM Z NetView Administration Reference
Determining the DSRB allocation for task DSIGDS IBM Z NetView Tuning Guide

Modifying the NetView RATE and AUTORATE Statements

It is possible for several MultiSystem Manager topology agents to send numerous alerts to the NetView
program that can overload the NetView hardware monitor database. Update the NetView RATE and
AUTORATE statements with an appropriate value to prevent overloading the NetView hardware monitor
database.
The RATE statement can be used to set the maximum rate at which alerts and resolutions can be logged
into the NetView hardware monitor database. If an alert is blocked by a recording filter set by the
RATE statement, it is not sent to automation unless you code an AUTORATE statement. The AUTORATE
statement can be used to send a blocked alert to automation.

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

RATE and AUTORATE statements IBM Z NetView Administration Reference

Tuning the REXX Environment

One of the most powerful features of the NetView program is the ability to run REXX code in the NetView
environment. Several of the NetView components, as well as base NetView functions, exercise code that
has been written in REXX.
MultiSystem Manager uses REXX command lists to acquire topology and status and to update objects in
RODM. Tuning the number and size of REXX environments can improve performance.

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

REXX Environment IBM Z NetView Installation: Configuring Additional
Components

Starting MultiSystem Manager

To start MultiSystem Manager, issue the INITTOPO command. By default, this command uses an
initialization file named FLCAINP. If your initialization file has a different name, specify this name
immediately following the INITTOPO command. If your initialization member includes GETTOPO
commands, they will be processed after the general statements specified in the CNMSTYLE member
have been verified.

Initializing Network Topology and Status

Network topology and status information must be stored in RODM before MultiSystem Manager can
manage your networks. This is done during MultiSystem Manager initialization, which is initiated by
issuing the INITTOPO command.

Initialization Steps
When the INITTOPO command is issued, MultiSystem Manager reads your initialization file, which
contains the names and SNA network addresses or IP host names of the topology agents. MultiSystem

56 IBM Z NetView: Installation: Configuring Graphical Components

Manager sends topology requests to each topology agent defined in the initialization file. Topology and
status are returned to MultiSystem Manager and stored in RODM. When the initialization process is
complete, you can view the networks from your NetView management console workstations. Topology
and status are dynamically updated for the managed resources in your network.
The initialization process proceeds in three steps:
1. Verifies the Multisystem Manager statements that are coded in the CNMSTYLE member.
2. Creates a topology manager object in RODM for each MultiSystem Manager feature. These objects
represent the MultiSystem Manager topology features and are displayed on the NetView management
console Details window.
After the CNMSTYLE statements have been verified and the topology manager class objects have been
created successfully, you receive the following message:

FLC059I MULTISYSTEM MANAGER INITIALIZATION FILE filename

HAS BEEN READ SUCCESSFULLY. THE MULTISYSTEM MANAGER IS NOW ENABLED.

The status of MultiSystem Manager is set to ENABLED, meaning that subsequent GETTOPO commands
can now be processed.
3. Runs the GETTOPO statements in the initialization file. When MultiSystem Manager starts processing
these statements, you receive the following message:

FLC048I GETTOPO COMMANDS FROM MULTISYSTEM MANAGER INITIALIZATION

FILE filename ARE NOW BEING PROCESSED.

After MultiSystem Manager has finished processing all of the GETTOPO statements, you receive the
following message:

FLC126I GETTOPO COMMANDS FROM MULTISYSTEM MANAGER INITIALIZATION

FILE file_name HAVE NOW BEEN PROCESSED.

Issuing the Focal Point Commands

To enable MultiSystem Manager to communicate with any Open topology agents, you must issue focal
point change commands to each of the service points on which Open topology agents are running. Open
topology agents are typically written by partners or customers to manage resources not managed by
MultiSystem Manager agents. Issue the following commands to each of the service points:

FOCALPT CHANGE TARGET=luname FPCAT=SPCS

FOCALPT CHANGE TARGET=luname FPCAT=ALERT

Issuing the INITTOPO Command

The INITTOPO command can be issued from a NetView command line or command procedure at any
time. This initializes topology and status processing. Topology agents notify MultiSystem Manager of
subsequent topology and status changes by means of alerts and resolutions. MultiSystem Manager
processes these alerts and resolutions using the NetView automation table.
To initialize MultiSystem Manager from your host NetView operator station task (OST), enter the
INITTOPO command on the operator command line:

INITTOPO filename

The filename parameter is optional. If you do not specify a file name, MultiSystem Manager uses the
default initialization file, FLCAINP.
You can also use the following statements that are included in the CNMSTYLE member:
• (MSM)AUTOTASK.?MSMdefault.Console = *NONE*
• (MSM)AUTOTASK.?MSMdefault.InitCmd = INITTOPO

Chapter 8. Preparing and Activating the MultiSystem Manager 57

 The first statement starts the autotask defined in the MSMdefault statement. The second statement runs
the INITTOPO command on that autotask. If you do not want to run the INITTOPO command during
NetView initialization, copy these statements to the CNMSTUSR or CxxSTGEN member, and comment out
these statements (precede the statement with an asterisk (*)). For information about changing CNMSTYLE
statements, see IBM Z NetView Installation: Getting Started.
Refer to the INITTOPO command in the IBM Z NetView Command Reference Volume 1 (A-N) or online
help for information about specifying an initialization file on the INITTOPO command. See Appendix
C, “Customizing the MultiSystem Manager Initialization Statements,” on page 105 for more information
about initialization file statements.
If you have just installed a MultiSystem Manager feature, issue the INITTOPO command to ensure that
the global variables have been set correctly. This also ensures that the correct topology manager objects
are created in RODM. See Appendix D, “Global Variables for MultiSystem Manager,” on page 121 for more
information about global variables.

Processing Topology Requests

One of the major functions of MultiSystem Manager is to process requests for topology and status of
resources in your network. These requests are made by issuing GETTOPO commands for particular
resources being managed by a topology agent. GETTOPO commands can be coded in the MultiSystem
Manager initialization file or issued from a NetView command line or command procedure. GETTOPO
commands can be processed by MultiSystem Manager only if MultiSystem Manager is enabled.
MultiSystem Manager receives the GETTOPO request, parses it, and builds and runs a series of RUNCMD
commands depending on the topology request. These RUNCMD commands are run from the specified
autotask and resource topology and status is returned to MultiSystem Manager in the form of RUNCMD
responses. These responses are then parsed and the topology and status information is stored in RODM.
In large, complex computing environments, you sometimes stop and restart multiple programs and
processes to apply maintenance, backup data, upgrade, and so on. During such times, you might want to
suspend the processing of topology requests, knowing that these requests fail until a particular process or
program is restarted. MultiSystem Manager provides commands that you can use to suspend and resume
MultiSystem Manager processing of topology requests.

Suspending Processing of Topology Requests

The SUSPTOPO command suspends MultiSystem Manager processing. The status of MultiSystem
Manager must be enabled to suspend processing. After successful completion of this command, the
status of MultiSystem Manager is set to SUSPENDED. This also causes the topology manager objects
displayed on the NetView management console Details window to change to a status of Not available.
GETTOPO commands cannot be processed while MultiSystem Manager is suspended.
GETTOPO commands issued before MultiSystem Manager processing was suspended, continue to
process until complete. GETTOPO commands issued after MultiSystem Manager processing is suspended
are ignored, and message FLC045E (processing is suspended) is issued.
Many of the alerts sent from the topology agents report new resources coming online. These alerts
drive statements in the NetView automation table, which in turn, drive command procedures that issue
topology and status requests for the newly discovered resources. If MultiSystem Manager processing
is suspended when these topology and status requests are issued, these requests are ignored.
Consequently, topology and status information for new resources is lost while MultiSystem Manager
processing is suspended.

Resuming Processing of Topology Requests

If the status of MultiSystem Manager is suspended, issue the RESTOPO command to resume processing
topology and status requests. After the RESTOPO command successfully completes, MultiSystem
Manager status is set to ENABLED. This also causes the topology manager objects displayed on the
NetView management console Details window to change to a status of AVAILABLE. All GETTOPO
commands issued while MultiSystem Manager processing is enabled are processed.

58 IBM Z NetView: Installation: Configuring Graphical Components

 Depending on how long MultiSystem Manager processing has been suspended and depending on the size
of your network and the amount of activity in your network, you might need to issue GETTOPO commands
for specific networks to bring topology and status information up to date. If you want to update the
topology and status information for all your networks, issue the INITTOPO command again.

Displaying Topology Processing Information

The DISPTOPO command displays the status and initialization parameters and other information for
MultiSystem Manager. See the DISPTOPO command in the IBM Z NetView Command Reference Volume 1
(A-N) or the online help for a description of the displayed fields.

Verifying the MultiSystem Manager Installation

When the MultiSystem Manager is active, you can use the following commands to control the collection of
topology information:

Command Use
GETTOPO ITNMxxxx Get topology and initial status for IP resources managed by IBM
Tivoli Network Manager.
GETTOPO OPENRES Get topology and initial status for OPEN resources

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

Using MultiSystem Manager IBM Z NetView User's Guide: NetView Management
Console
GETTOPO command NetView online help

Creating Applications to Manage New Topologies

You can write applications to monitor and manage resources that are not supported by other MultiSystem
Manager features. These applications can be either workstation-based topology agents or MVS-based
topology managers.
Workstation-based topology agents are agents that reside on SNA service points. These agents use
the MultiSystem Manager Open topology manager to create and manage objects in RODM. MVS-based
topology managers reside on the NetView host. MVS-based topology managers either perform the
function of a topology agent at the host or communicate with a remote topology agent that is not at
an SNA service point. MVS-based topology managers use the MultiSystem Manager Access facility to
create and manage objects in RODM, rather than using the Open API and the Open topology manager.
The documentation and tools you need depend on the type of topology application you want to create.

Creating Workstation Topology Agents

The following documentation and tools help you create workstation-based topology agents:
• IBM Z NetView Data Model Reference
• IBM Z NetView Resource Object Data Manager and GMFHS Programmer's Guide
• MultiSystem Manager: Topology Agent Developer's Guide
• MultiSystem Manager Topology Agent Developer's Toolkit
• MultiSystem Manager Sample Topology Agent
For a description of these items and how you can obtain them, see “Documentation and Tools” on page
60.

Chapter 8. Preparing and Activating the MultiSystem Manager 59

Creating MVS Topology Managers
The following documentation and tools help you create MVS-based topology managers:
• IBM Z NetView Data Model Reference
• IBM Z NetView Resource Object Data Manager and GMFHS Programmer's Guide
• MultiSystem Manager Access
• MultiSystem Manager Sample MVS Data Model Application
For a description of these items and how you can obtain them, see “Documentation and Tools” on page
60.

Documentation and Tools

Documentation and tools for building a MultiSystem Manager Open Topology Interface agent application
can be downloaded from the MSMTOOLK package, which is available from the NetView support Web
page.
Tools and selected patches include:
• MultiSystem Manager: Topology Agent Developer's Guide describes how to write an Open topology agent
application program. This document is available from the MSMTOOLK package.
• MultiSystem Manager Sample Topology Agent contains the C language source code for a topology agent.
This sample application demonstrates use of the Topology Agent Developer's Toolkit. This sample
application is available from the MSMTOOLK package.
• IBM Z NetView Data Model Reference describes the NetView data models.
• IBM Z NetView Resource Object Data Manager and GMFHS Programmer's Guide describes writing RODM
applications and methods, and creating objects in RODM that use the GMFHS data model.
• MultiSystem Manager Topology Agent Developer's Toolkit contains a set of C language functions that
create data streams used to build NetView management console views. This toolkit is available from the
MSMTOOLK package.
• MultiSystem Manager Sample MVS Data Model Application contains REXX samples that you can use
to create and update objects in RODM from an MVS application using the Open data model. The
sample application is provided on the MultiSystem Manager product media in the CNMSAMP data set as
FLCSOX01.
• MultiSystem Manager Access provides a fast and efficient REXX interface to RODM. This document also
describes how to create a topology manager application on MVS if you do not want to use the Open API
to support a remote topology agent. Refer to IBM Z NetView Resource Object Data Manager and GMFHS
Programmer's Guide for more information about RODM tools.

60 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 9. Preparing and Activating the NetView
Resource Manager

This chapter addresses the following technical considerations:

• “Defining the NetView Resource Manager Autotask” on page 61
• “Security Considerations” on page 61
• “Initialization Considerations” on page 63
• “Starting the NetView Resource Manager” on page 64
• “Verifying the NetView Resource Manager Installation” on page 64

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 61
• “Command Authorization” on page 62

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, 2019 61

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

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.

62 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 9. Preparing and Activating the NetView Resource Manager 63

 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.

64 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 9. Preparing and Activating the NetView Resource Manager 65

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

This chapter addresses the following technical considerations:

• “Security Considerations” on page 67
• “Initialization and Operational Considerations” on page 68

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

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 12

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, 2019 67

 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.

68 IBM Z NetView: Installation: Configuring Graphical Components

Chapter 11. Managing Views

As SNA topology manager and MultiSystem Manager agents gather 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.

© Copyright IBM Corp. 2001, 2019 69

 • Advantages of RODM collection manager views with similar characteristics:
– 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 8. Collapsed View Tree

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

Figure 9. 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

70 IBM Z NetView: Installation: Configuring Graphical Components

 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

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 MultiSystem Manager topology
agents, the SNA topology 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.V6R3M0.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 and SNA topology 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 SNA Topology Manager Object Correlation

SNA correlation occurs on PU resources for which SNA topology manager discovers a LAN MAC address.
PU resources are excluded from TOPOSNA commands that do not include the LOCAL parameter. Use
the LOCAL parameter on any TOPOSNA command issued to resources you want included in correlation.
Correlation also occurs for LU resources which support a telnet 3270 (tn3270) server or requester.

Chapter 11. Managing Views 71

Enabling Object Correlation for Additional SNA Topology Manager and
GMFHS Resources
If you have SNA topology manager or 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.

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 72
• “RODM Unloader” on page 72
• “FLCARODM” on page 72
• “RODM Collection Manager” on page 73
• “BLDVIEWS” on page 73
• “DELVIEWS” on page 74

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

72 IBM Z NetView: Installation: Configuring Graphical Components

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

Chapter 11. Managing Views 73

 • GMFHS_Managed_Real_Objects_Class
You cannot use BLDVIEWS to delete objects, classes, or fields, but you can modify certain fields of
objects.
For the SNA topology manager and MultiSystem Manager data models, objects cannot be created or
deleted using BLDVIEWS. However, views can be created to include objects of these classes. BLDVIEWS
supports real and aggregate objects created in RODM by the MultiSystem Manager and SNA topology
manager.
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.
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.

74 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, 2019 75

 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.

76 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 77
 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 6 on page 78 shows an example of the topology server workstation configuration for the data link
control profile for LAN.

Table 6. 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.

78 IBM Z NetView: Installation: Configuring Graphical Components

Table 6. 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 7 on page 79 shows an example of a topology server workstation configuration for the local node
characteristics. Modify this profile for a LAN configuration.

Table 7. 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 8 on page 79 shows an example of the topology server workstation configuration for the logical
unit profile you have specified.

Table 8. 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 79
 Table 8. 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 9 on page 80 is an example of the topology server workstation configuration for the transmission
service mode profile.

Table 9. 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 10 on page 80 shows an example of the topology server workstation configuration for the
transaction program profile.

Table 10. Transaction Program Definitions

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

80 IBM Z NetView: Installation: Configuring Graphical Components

Table 10. 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 11. 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 81
82 IBM Z NetView: Installation: Configuring Graphical Components
Appendix B. NetView Graphics Samples

This appendix contains the following topics:

• “GMFHS Samples” on page 83
• “MultiSystem Manager and Agent Samples” on page 84
• “NetView Management Console Samples” on page 88
• “NetView Resource Manager Samples” on page 89
• “RODM Samples” on page 90
• “SNA Topology Manager Samples” on page 100
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 12 on page 83 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 12. 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.

© Copyright IBM Corp. 2001, 2019 83

 Table 12. List of GMFHS Samples (continued)
Distributed As Name Description Data Set Name
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.

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

MultiSystem Manager and Agent Samples

The following samples are provided for MultiSystem Manager:
• “MultiSystem Manager Samples” on page 84
• “IBM Tivoli Network Manager Topology Samples” on page 87
• “Open Topology Samples” on page 87

MultiSystem Manager Samples

Table 13 on page 84 lists the samples and includes a brief description of each MultiSystem Manager
sample and the data set name where each member resides when installation is complete.

Table 13. List of MultiSystem Manager Samples

Distributed As Name Description Data Set Name
CNMCMENT same NetView command definition statements including DSIPARM
those for MultiSystem Manager.
CNMSTYLE same Defines some of the NetView initialization DSIPARM
parameters. Refer to the CNMSTYLE member for
more information.

84 IBM Z NetView: Installation: Configuring Graphical Components

Table 13. List of MultiSystem Manager Samples (continued)
Distributed As Name Description Data Set Name
FLCAINP same Sample initialization file DSIPARM
This file can be used as a template when creating
the MultiSystem Manager initialization file (or files)
for your site.
If you rename this file, specify that file name when
issuing the INITTOPO command.
FLCAINP contains an example of how to use the
%INCLUDE statement to include other MultiSystem
Manager initialization files.

FLCSCCHK same Authorization checking for MultiSystem Manager CNMSAMP

commands sent using the TCP/IP transport
The FLCACCHK REXX command list is called when
processing a MultiSystem Manager command that
uses TCP/IP to communicate between the NetView
program and the MultiSystem Manager agent. As
shipped, FLCACCHK does not do any authorization
checking and all commands are processed.
The FLCSCCHK sample contains the REXX source
code from the FLCACCHK command list. The
FLCSCCHK sample resides in the CNMSAMP
data set and is provided in sample format so
that you can add authorization checking for
MultiSystem Manager commands sent using the
TCP/IP transport. Refer to the sample's prolog
for instructions on replacing the existing REXX
command list with your modified sample.

FLCSDM1 same MultiSystem Manager data model — part 1 CNMSAMP

This file contains the class and field definitions
of the MultiSystem Manager data model that
are SystemView-compliant. This file contains the
SystemView classes used to create view objects.

FLCSDM2 same MultiSystem Manager data model — part 2 CNMSAMP

This file contains the class and field definitions
of the MultiSystem Manager data model that are
private extensions to the data model. This file
contains the private classes used to create view
objects.

FLCSDM3 same MultiSystem Manager data model — part 3 CNMSAMP

This file sets default status aggregation on both
real and aggregate objects. This file also sets some
default values for fields previously created. This file
can be rerun with changed defaults.

FLCSDM4 same MultiSystem Manager data model — part 4 CNMSAMP

This file creates objects and sets fields used to
graphically display objects.

Appendix B. NetView Graphics Samples 85

 Table 13. List of MultiSystem Manager Samples (continued)
Distributed As Name Description Data Set Name
FLCSDM5 same MultiSystem Manager data model — part 5 CNMSAMP
This file contains the default values for view change
notification. This file can be customized.

FLCSDM6 same MultiSystem Manager data model — part 6 CNMSAMP

This file creates the default exception view
definitions. The Exception view classes that are
created by this sample are the same as those
referenced in sample FLCSEXV.

FLCSDM8 same MultiSystem Manager data model — part 8 CNMSAMP

This file enables the use of RODM methods for
dynamic topology correlation. The file loads the
FLCMCON and FLCMCOR methods into RODM.

FLCSDM9 same MultiSystem Manager data model — part 9 CNMSAMP

This file enables the use of RODM methods for
linking TN3270 resources to IP resources.

FLCSEXV same Exception view file DSIPARM

This file contains sample statements for
MultiSystem Manager Exception view processing.
It contains exception view statements for the
real RODM classes that are supported by the
MultiSystem Manager data model. Remove the
comments from those statements you want to use.
The prolog of this file describes the usage and
syntax of the Exception view statements.

FLCSOPF same Operator definitions for MultiSystem Manager DSIPARM

autotasks
This file contains the operator definition
statements for the MultiSystem Manager autotasks.
You can add additional autotasks for processing
topology requests.

FLCSPRFB same Operator profile for MultiSystem Manager DSIPRF

autotasks
This file contains a sample profile for MultiSystem
Manager autotasks.

86 IBM Z NetView: Installation: Configuring Graphical Components

 Table 13. List of MultiSystem Manager Samples (continued)
Distributed As Name Description Data Set Name
FLCSSMT same MultiSystem Manager status mapping table CNMSAMP
required for exception view processing
This file contains sample statements for
MultiSystem Manager exception view processing.
The statements in this sample MUST be
included in your existing NetView Status Mapping
Table (DUIFSMT) if you want to implement
exception view processing for MultiSystem
Manager resources in RODM. The prolog of this
file describes the usage and syntax of the NetView
Status Mapping Table statements.

FLCVBLDS same Sample BLDVIEWS control statements CNMSAMP

IBM Tivoli Network Manager Topology Samples

The following samples are specific to the MultiSystem Manager IBM Tivoli Network Manager topology
feature.

Table 14. List of MultiSystem Manager IBM Tivoli Network Manager Topology Samples
Distributed As Name Description Data Set Name
FLCSPAUT same Sample REXX alert processor CNMSAMP
The FLCAPAUT REXX command list is called from
the NetView automation table to process alerts
generated by IBM Tivoli Network Manager.
The FLCSPAUT sample contains the REXX source
code from the FLCAPAUT command list. The
FLCSPAUT sample resides in the CNMSAMP data
set and is provided in sample format so that you
can modify the automated alert processing. See
the sample prolog for instructions on replacing the
existing REXX command list with your modified
sample.

FLCSITNM same Sample GETTOPO initialization statement for IBM DSIPARM

Tivoli Network Manager
The FLCSITNM sample is included by the FLCAINP
MultiSystem Manager initialization file sample. The
FLCSITNM sample contains a sample GETTOPO
statement for IBM Tivoli Network Manager. Each
of the keywords on the GETTOPO command are
described briefly.

Open Topology Samples

The following samples are specific to the MultiSystem Manager Open topology feature.

Appendix B. NetView Graphics Samples 87

 Table 15. List of MultiSystem Manager Open Topology Samples
Distributed As Name Description Data Set Name
FLCSDM6O same Sample file for Open topology CNMSAMP
Exception_View_Classes
This data model sample loads sample instances of
Exception_View_Class for the Open topology agent.
The exception view classes that are created by this
sample are the same as those referenced in sample
FLCSEXV. Both FLCSDM6O and FLCSEXV can be
customized.

FLCSIOPN same Sample GETTOPO initialization statement for Open DSIPARM

Sample FLCSIOPN is included by MultiSystem
Manager initialization file sample FLCAINP.
FLCSIOPN contains a sample GETTOPO statement
for the Open topology interface. Each of
the keywords on the GETTOPO command are
described briefly.

FLCSOALH same Sample REXX alert processor CNMSAMP

REXX command list FLCSOALH is called from
the NetView automation table to process alerts
generated by Open topology agents.
Sample FLCSOALH contains the REXX source code
from FLCAOALH. FLCSOALH is provided in sample
format so that you can modify the automated
alert processing. Refer to the sample's prolog
for instructions on replacing the existing REXX
command list with your modified sample.

FLCSOAUT same Sample REXX alert processor CNMSAMP

REXX command list FLCSOAUT is called from
the NetView automation table to process alerts
generated by Open topology agents.
Sample FLCSOAUT contains the REXX source code
from FLCAOAUT. FLCSOAUT is provided in sample
format so that you can modify the automated
alert processing. Refer to the sample's prolog
for instructions on replacing the existing REXX
command list with your modified sample.

FLCSOX01 same Sample REXX creation of RODM views, CNMSAMP

using MultiSystem Manager Access (FLCARODM
command) and the open data model
This file also demonstrates topology correlation
between different resources.

NetView Management Console Samples

Table 16 on page 89 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.

88 IBM Z NetView: Installation: Configuring Graphical Components

 Table 16. 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.

Table 17. 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.

Appendix B. NetView Graphics Samples 89

RODM Samples
Table 18 on page 90 lists the RODM samples found in the NETVIEW.V6R3M0.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.V6R3M0.CNMSAMP library under the
distributed sample name.

Table 18. 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)
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

90 IBM Z NetView: Installation: Configuring Graphical Components

Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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

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

Appendix B. NetView Graphics Samples 91

 Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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

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

92 IBM Z NetView: Installation: Configuring Graphical Components

Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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

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

Appendix B. NetView Graphics Samples 93

 Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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

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

94 IBM Z NetView: Installation: Configuring Graphical Components

Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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

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

Appendix B. NetView Graphics Samples 95

 Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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

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

96 IBM Z NetView: Installation: Configuring Graphical Components

Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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

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

Appendix B. NetView Graphics Samples 97

 Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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
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

98 IBM Z NetView: Installation: Configuring Graphical Components

 Table 18. List of RODM Samples (continued)
Distributed As Name Description Data Set Name
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 19. 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
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

Appendix B. NetView Graphics Samples 99

 Table 19. List of FLCARODM Samples (continued)
Distributed As Name Description Data Set Name
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
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

SNA Topology Manager Samples

Table 20 on page 101 lists the samples and includes a brief description of each SNA Topology Manager
sample and the data set name where each member resides when installation is complete.

100 IBM Z NetView: Installation: Configuring Graphical Components

Table 20. List of SNA Topology Manager Samples
Distributed As Name Description Data Set Name
CNMCMENT same NetView command definition statements for the DSIPARM
SNA topology manager.
CNMSTYLE same This sample defines many of the NetView DSIPARM
initialization parameters. Refer to the CNMSTYLE
member for more information.
CNMSXENT same Sample used to show that the SNA topology CNMSAMP
manager is installed
FLBAUT same Automation Table Entries for SNA topology DSIPARM
manager
FLBEXV same SNA topology manager Exception View Table DSIPARM
FLBEXVU same SNA topology manager Exception View Table user DSIPARM
entry. This is a sample INCLUDE file that is
included from SNA topology manager initialization
file FLBEXV.
FLBOSIDS same SNA topology manager OSI/Display Status Table. DSIPARM
Maps the OSI status values to DisplayStatus
values.
FLBOSIDU same SNA topology manager OSI/Display Status Table DSIPARM
user entry. This is a sample INCLUDE file that is
included from SNA topology manager initialization
file FLBOSIDS.
FLBS8001 same Sample REXX exec named REFRESHC. This CNMSAMP
executable runs a TOPOSNA CRITICAL command
against a list of resources specified in a member of
the DSIOPEN data set.
FLBS8002 same Sample used by the FLBS8001 sample to provide a CNMSAMP
table of LUs for the REFRESHC command.
FLBSRT same SNA topology manager Status Resolution Table. DSIPARM
This table contains the hierarchy of OSI status
entries used to resolve the status of a multiply-
owned resource.
FLBSRTU same SNA topology manager Status Resolution Table DSIPARM
user entry. This is a sample INCLUDE file that is
included from SNA topology manager initialization
file FLBSRT.
FLBSYSD same SNA topology manager initialization file DSIPARM
FLBTPROF same Sample operator profile statements for NetView DSIPRF
SNA topology manager function
FLBTRDM1 same SNA Topology Data Model loader file that creates CNMSAMP
the generic managed object classes
FLBTRDM2 same SNA Topology Data Model loader file that creates CNMSAMP
the APPN and Subarea managed object classes

Appendix B. NetView Graphics Samples 101

 Table 20. List of SNA Topology Manager Samples (continued)
Distributed As Name Description Data Set Name
FLBTRDM3 same SNA Topology Data Model loader file that creates CNMSAMP
a SNA topology manager specific class for
operational defaults
FLBTRDM4 same SNA Topology Data Model loader file that creates CNMSAMP
RODM method objects
FLBTRDM5 same SNA Topology Data Model loader file that sets CNMSAMP
default values for the generic managed object
classes
FLBTRDM6 same SNA Topology Data Model loader file that sets CNMSAMP
default values for the APPN and Subarea object
classes
FLBTRDM7 same SNA Topology Data Model loader file that sets CNMSAMP
GMFHS-navigation values
FLBTRDM8 same SNA Topology Data Model loader file that creates CNMSAMP
View_Information_Reference_Class objects
FLBTRDM9 same SNA Topology Data Model loader file that is CNMSAMP
reserved for Tivoli use
FLBTRDMA same SNA Topology Data Model loader file for Predefined CNMSAMP
Network_View_Class view object
FLBTRDMB same SNA Topology Data Model loader file for View CNMSAMP
Information Object Class Instances
FLBTRDMC same SNA Topology Data Model loader that sets links CNMSAMP
between VIROs and DRTs
FLBTRDMD same SNA Topology Data Model loader file that creates CNMSAMP
Exception Views
FLBTRDME same View Notification Granularity loader file that installs CNMSAMP
notification methods
FLBTRDMG same SNA Topology Data Model loader file that takes the CNMSAMP
netid from DisplayResourceName
FLBTRDMH same SNA Topology Data Model loader file that creates a CNMSAMP
SNA_Backbone_View
FLBTRDMI same SNA Topology Data Model loader file that produces CNMSAMP
a grid layout for More Detail views
FLBTRDMJ same SNA Topology Data Model loader file that creates CNMSAMP
port aggregate objects and suppresses logical links
FLBTRDMZ same SNA Topology Data Model loader file that creates CNMSAMP
the Topology_Manager class
FLBTREU same A method that is a sample exception view CNMSAMP
customization method that can be invoked from
the SNA topology manager method exception view
table is refreshed.
FLBTRSC1 same SNATM APPN Sample Network JCL for the initial CNMSAMP
scene

102 IBM Z NetView: Installation: Configuring Graphical Components

Table 20. List of SNA Topology Manager Samples (continued)
Distributed As Name Description Data Set Name
FLBTRSC2 same SNATM APPN Sample Network JCL for scene 2 CNMSAMP
FLBTRSC3 same SNATM APPN Sample Network JCL for scene 3 CNMSAMP
FLBTRSC4 same SNATM APPN Sample Network JCL for scene 4 CNMSAMP
FLBTRSC5 same SNATM APPN Sample Network JCL for scene 5 CNMSAMP
FLBTRSC6 same SNATM APPN Sample Network JCL for scene 6 CNMSAMP
FLBTRSN1 same SNATM APPN Sample Network loader file for the CNMSAMP
initial scene
FLBTRSN2 same SNATM APPN Sample Network loader file for scene CNMSAMP
2
FLBTRSN3 same SNATM APPN Sample Network loader file for scene CNMSAMP
3
FLBTRSN4 same SNATM APPN Sample Network loader file for scene CNMSAMP
4
FLBTRSN5 same SNATM APPN Sample Network loader file for scene CNMSAMP
5
FLBTRSN6 same SNATM APPN Sample Network loader file for scene CNMSAMP
6
FLBTRUM same A method that is a sample status customization CNMSAMP
method that can be invoked from the SNA topology
manager method FLBTRST when the manager is
processing a status update for an object in RODM

Appendix B. NetView Graphics Samples 103

104 IBM Z NetView: Installation: Configuring Graphical Components
Appendix C. Customizing the MultiSystem Manager
Initialization Statements

The initialization statements in the CNMSTYLE member define how MultiSystem Manager is to manage
your network. You can customize the initialization statements to do the following actions:
• Define the Resource Object Data Manager (RODM).
• Set the number of times a failed RUNCMD command is retried.
• Specify the name of the NetView autotask that is used for default processing.
• Design network views.
Many of the initialization statements have default values. You can customize the initialization statements
to specify values that meet the needs of your enterprise.
In addition to the initialization statements specified in the CNMSTYLE member, you can code GETTOPO
statements in a MultiSystem Manager initialization file. These statements can retrieve topology and status
for your managed networks when you initialize MultiSystem Manager.
If you have multiple topology features, you can include multiple initialization files in a single file by using
the %INCLUDE statement.

Sample Files
MultiSystem manager provides several samples files that can assist in your preparation.
MultiSystem Manager provides a sample initialization file named FLCAINP. This file resides in the
DSIPARM data set.
MultiSystem Manager also provides sample initialization files that contain examples of GETTOPO
statements for each feature. These files are included by the sample file FLCAINP. Table 4 on page 53
shows the sample initialization file for each MultiSystem Manager feature. Your initialization files must
reside in a DSIPARM data set.

Defining RODM to MultiSystem Manager

The following CNMSTYLE initialization statements are used to define RODM to MultiSystem Manager:
COMMON.FLC_RODMNAME
The name of the RODM you specify must be the same name you used to define this RODM to GMFHS.
This statement is required.
(MSM)COMMON.FLC_RODMINT
The amount of time (in seconds) between retries of a RODM request that failed because RODM
is checkpointing. When RODM is checkpointing a disk, it cannot process certain transactions, so
MultiSystem Manager must wait until the checkpoint process is finished. If MultiSystem Manager tries
but cannot access the information because RODM is checkpointing, it waits and tries again.
This statement is optional. If you do not code a value for this statement, MultiSystem Manager waits
five seconds between each retry.
(MSM)COMMON.FLC_RODMRETRY
The number of times MultiSystem Manager retries a RODM request that failed because RODM is
checkpointing. When RODM is checkpointing a disk, it cannot process certain transactions, so that
MultiSystem Manager must wait until the checkpoint process is finished. If MultiSystem Manager
cannot access the information because RODM is checkpointing, it waits and tries again.
This statement is optional. If you do not code a value for this statement, MultiSystem Manager retries
three times.

© Copyright IBM Corp. 2001, 2019 105

 To update these statements, copy them from the CNMSTYLE member to the CNMSTUSR or CxxSTGEN
member, and if necessary uncomment the statement (remove the asterisk from the beginning of the
statement). Make any statement modifications in CNMSTUSR or CxxSTGEN. For information about
changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.

Defining the RUNCMD Retry Count

The (MSM)COMMON.FLC_RUNCMDRETRY statement in the CNMSTYLE member specifies the number of
times you want the MultiSystem Manager to retry a RUNCMD that cannot be sent because the SNA
session was busy (sense code 0851). This statement is optional. If you do not code a value for this
statement, the MultiSystem Manager retries three times.
To update the (MSM)COMMON.FLC_RUNCMDRETRY statement, copy it from the CNMSTYLE member to the
CNMSTUSR or CxxSTGEN member, remove the asterisk (*), and change the retry count. For information
about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.

Defining the Default Autotask

Use the (MSM)function.autotask.MSMdefault statement to specify the name of the default
autotask that MultiSystem Manager is to use during GETTOPO processing. When the autotask keyword is
not specified on the GETTOPO command and the service point object for the GETTOPO command is not
stored in RODM, then the default autotask is used.
This statement is required. If you do not code a value for this statement, MultiSystem Manager fails
to initialize. MultiSystem Manager supplies a sample autotask, AUTOMSMD, in sample FLCSOPF. Assign
AUTOMSMD to be the default autotask.

Defining Exception Views

The following optional CNMSTYLE statement specifies the file that contains information about processing
exception views for MultiSystem Manager resources:

*(MSM)COMMON.FLC_EXCEPTION_VIEW_FILE=xxxxxxxx

Note: Exception views are not available for the MultiSystem Manager IBM Tivoli Network Manager agent.
To update the (MSM)COMMON.FLC_EXCEPTION_VIEW_FILE statement, copy it from the CNMSTYLE
member to the CNMSTUSR or CxxSTGEN member, remove the asterisk (*), and specify the exception
view file. For information about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting
Started.

Defining Service Points

Service points can be defined to MultiSystem Manager by specifying a GETTOPO statement in the
initialization file.
The workstation where the topology agent is installed is called the service point. The service point
communicates with the topology manager. As used in this book, the term service point extends past the
traditional SNA definition to include TCP/IP. The service point name is specified in the SP parameter on
the GETTOPO command. This parameter is required on the GETTOPO statement.
The topology manager can communicate with topology agents through SNA or TCP/IP protocol.
The communication protocol is dependent upon the MultiSystem Manager feature that you are
implementing. Table 21 on page 107 lists each MultiSystem Manager topology feature and the associated
communication protocols that each feature supports.

106 IBM Z NetView: Installation: Configuring Graphical Components

 Table 21. MultiSystem Manager Topology Feature and Communication Protocols
MultiSystem Manager Feature Communication Protocol
IBM Tivoli Network Manager IP
Open Topology Interface SNA LU 6.2

In some cases, it is necessary to code additional parameters, such as REMOTE and APPL, that are closely
related to the SP parameter. These related parameters are discussed in the following sections, where
applicable.

Specifying the SP Parameter for the TCP/IP Protocol

For topology agents that communicate with the topology manager using an IP connection, the SP
parameter is the TCP/IP host name of the service point. This can be either the simple TCP/IP host name
or the fully qualified host name. Even if you specify a fully qualified host name, the host name must be
unique. You cannot specify two host names that are the same, even if they reside in different subnets.

Specifying the SP Parameter for the SNA Protocol

For topology agents that communicate with the topology manager using an SNA connection, the SP
parameter is the LU or PU name of the service point. The LU name is specified when an LU6.2 connection
is used to communicate with the topology manager. The PU name is used when an SSCP-PU session is
used.
If the service point does not reside in the same SNA domain or network as MultiSystem Manager, and
the connection to the service point is LU6.2, specify the fully qualified SNA name when coding the SP
parameter. The format of a fully qualified SNA name is sp_netid.sp_domain.sp_name, where sp_netid and
sp_domain are the names of the remote SNA network and domain where the service point resides.
If the service point does not reside in the same SNA domain or network as MultiSystem Manager and the
connection to the service point is SSCP-PU, you must also code the REMOTE parameter.
See Figure 10 on page 107 for guidelines on coding the SP and REMOTE parameters.

Figure 10. Coding the SP and REMOTE Parameters

Appendix C. Customizing the MultiSystem Manager Initialization Statements 107

 If you use the Open feature, the APPL parameter is also required. The APPL parameter is used to define
the name of the application on the service point system that communicates with the topology manager.

Additional GETTOPO Parameters

You can use additional GETTOPO parameters within the initialization file to define your topology agents.
Some of these parameters are optional. Specify, in your GETTOPO statement, the parameters needed to
best manage the resources in your network.

HEARTBEAT Parameter
The HEARTBEAT parameter provides a means of notification if you lose communication with a service
point. MultiSystem Manager polls the agent at a specified interval. If the agent fails to respond,
MultiSystem Manager sets the status of the agent to unsatisfactory and sets the status of all the objects
owned by that agent to unknown.

Additional Parameters for IBM Tivoli Network Manager

This section describes the additional GETTOPO parameters for IBM Tivoli Network Manager.

ITNMRES and ITNMONLY Parameters

When you define the service point for a network managed by the MultiSystem Manager IBM Tivoli
Network Manager agent, you can specify that MultiSystem Manager is to gather topology and status for
the topology agent and all of its managed IP resources or for only the topology agent.
MultiSystem Manager uses initialization statements, which are in the form of GETTOPO ITNMRES and
GETTOPO ITNMONLY topology commands, to gather the initial network topology and status. If you code
the ITNMRES parameter, MultiSystem Manager gathers topology and status for the topology agent and all
its managed IP resources such as subnetworks, routers, bridges, hubs, hosts, and interfaces.
If you specify the ITNMONLY parameter, MultiSystem Manager gathers topology and status only for the
topology agent. Although you can specify either of the parameters in the initialization file, specify the
ITNMRES parameter on each statement to gather the most complete initial information.

HOSTS Parameter
When you define your topology agents, you can use the initialization file to choose the types of resources
you want to manage. You can choose whether you want to include the hosts and host adapters of the
network. To include hosts and host adapters in your managed IP resources, specify HOSTS=YES (the
default) on your GETTOPO initialization file statements.
If you specify HOSTS=NO, MultiSystem Manager gathers topology and status for and manages only
subnetworks, routers, bridges, and hubs. Hosts and host interfaces are not managed.
If you specify HOSTS=NO, but later need information about your hosts to do problem determination, you
can issue a GETTOPO ITNMRES or ITNMDETAIL command with HOSTS=YES to gather topology and status
for the hosts and host interfaces.
If you want to decrease the network traffic flow and the amount of NetView and RODM storage that
MultiSystem Manager uses during initialization, specify HOSTS=NO on the GETTOPO ITNMRES statement.

UNMANAGED Parameter
As part of managing your IP environment using IBM Tivoli Network Manager, you can choose to
display unmanaged resources. The UNMANAGED parameter on your GETTOPO ITNMRES initialization
file statements determines if unmanaged network resources are displayed.
If you specify UNMANAGED=YES, which is the default, MultiSystem Manager gathers topology and status
about the unmanaged resources, stores this information in RODM, and creates these objects in your
views.

108 IBM Z NetView: Installation: Configuring Graphical Components

 If you specify UNMANAGED=NO, MultiSystem Manager does not collect information about unmanaged
resources or display them.
If you want to decrease the amount of processing done by the IBM Tivoli Network Manager agent during
initialization, specify UNMANAGED=NO on the GETTOPO ITNMRES statement.

Additional Parameters for the Open Topology Interface

This section describes the additional GETTOPO parameters for Open.

OPENRES Parameter
MultiSystem Manager uses initialization file statements, which are in the form of GETTOPO OPENRES
topology commands, to gather the initial network topology and status.

HOSTONLY Parameter
MultiSystem Manager also uses GETTOPO HOSTONLY commands to retrieve status and information for
Open topology agents and update them in RODM.

ELEMENT Parameter
If your topology agent (defined by the APPL parameter) supports multiple sub-applications, you can use
the ELEMENT parameter to send the GETTOPO commands to that element manager.
For example, if your Open topology agent, APPLA, is composed of several sub-applications that
perform different functions, and if you designed a sub-application to handle GETTOPO command
processing, called sub-application GTAPPL, you can code APPL=APPLA and ELEMENT=GTAPPL. When
the initialization file is processed, MultiSystem Manager sends the GETTOPO command to APPLA, but
indicates that this command is routed to sub-application GTAPPL.

Defining NetView Management Console Views and Objects

With MultiSystem Manager, you can create graphical views showing your networks at various levels of
detail. These views are based on the information specified in the initialization file. You can create and
name network views and objects that are to be displayed in these network views.
This section describes how to customize network views and network objects by using the
NETWORK_VIEW, NETWORK_AG_OBJECT, and NETWORK_NAME keywords. If you customize network
views or network objects, specify these keywords on the first GETTOPO command that you issue to each
service point. In most cases, the first GETTOPO command to each service point must be specified in the
initialization file.
If the customized information is stored in RODM, it is not necessary to specify the customized values
again in subsequent GETTOPO commands to each service point. This simplifies the task of writing
additional automation routines for these managed resources.

Network Views
The NetView management console Details window lists the highest level MultiSystem Manager network
views. The Details window, as shown in Figure 11 on page 110, contains the default network view,
MultiSysView.
Each MultiSystem Manager feature is added to the NetView management console component list during
initialization. The feature does not display in the details window until it is defined in the initialization file.
Figure 11 on page 110 shows the NetView management console component list.
Note: The NetView management console, by default, displays icons in views. To display geometric shapes
instead of icons, click View > Show Icons.

Appendix C. Customizing the MultiSystem Manager Initialization Statements 109

 Figure 11. NetView Management Console Details

Using the Default Network Views

A single network view named MultiSysView is created by default. All defined networks are displayed in
this view. Figure 12 on page 110 shows the MultiSysView view. These views show the default high level
networks object for all of the MultiSystem Manager features. To simplify the customization examples, the
remaining portion of this chapter refers to a subset of MultiSystem Manager features.

Figure 12. NetView Management Console Default Network View (MultiSysView) Example

Creating Views
MultiSystem Manager dynamically builds views that meet the majority of your network management
needs, but you might also want to create unique views.
You can monitor your network from a single NetView management console view, or you can create
multiple views, with each view reflecting a different grouping of your resources.
You can also integrate your MultiSystem Manager networks with other network views. For example, if you
have an SNA network view, you can add your MultiSystem Manager networks to that view.
The NetView program provides several options that you can use to build customized views.

110 IBM Z NetView: Installation: Configuring Graphical Components

• You can use the RODM Collection Manager to create dynamic custom views and aggregate objects. For
more information, see the IBM Z NetView User's Guide: NetView Management Console.
• You can use BLDVIEWS to create static customized views; for more information, see the BLDVIEWS
information in the IBM Z NetView Resource Object Data Manager and GMFHS Programmer's Guide.
• You can use GETTOPO commands to create unique views; for more information, see the online help.

Customizing Network Views

You can customize network views by changing the name of the default network view (MultiSysView) or by
creating additional network views to manage network operations more efficiently.

Changing the Name of the Default View

The MultiSystem Manager default is a single network view named MultiSysView. To change the name of
the default network view, copy the (MSM)COMMON.FLC_DEF_NETW_VIEW statement to CNMSTUSR or
CxxSTGEN, remove the asterisk (*), and modify the statement. For information about changing CNMSTYLE
statements, see IBM Z NetView Installation: Getting Started.
1st_Shift_View can be created for each MultiSystem Manager feature. When you initialize MultiSystem
Manager using this initialization statement, an entry called 1st_Shift_View is displayed in the list of
views on your NetView management console. Open this view to see the networks monitored by the first
shift. Figure 13 on page 111 shows how your Details window might look.

Figure 13. NetView Management Console Details Example 2

Creating Additional Network Views

You can also create additional network views. For example, if you want to view a smaller subset of
networks during your off-shift operations, create another view called Off_Shift_View.
When you initialize MultiSystem Manager using the NETWORK_VIEW parameter, the name of the new
off-shift view is added to the list as shown in Figure 14 on page 111.

Figure 14. NetView Management Console Details Example 3

For additional examples of customizing views, see “Network Configurations and Views” on page 114.

Appendix C. Customizing the MultiSystem Manager Initialization Statements 111

Network Objects
You can use the default network objects, customize certain aggregate objects that are provided with each
feature, or create network objects.

Using the Default Network Objects

MultiSystem Manager groups all networks by type, for example, all IBM Tivoli Network Manager networks
are grouped under one network aggregate object called ITNM_IP_Networks, by default, shown in Figure
12 on page 110.
By default, MultiSystem Manager creates a network object named spname_MSMfeature_Network for
each network. The spname string is either the LU portion of the SNA network address or the TCP/IP host
name that is coded on the SP parameter of the GETTOPO statement for the network. The MSMfeature
string names the MultiSystem Manager feature to which this network belongs (such as IP). Figure 15
on page 112 shows an example of the default network objects that can be displayed in your NetView
management console views.

Figure 15. NetView Management Console Default Network Object Examples

If you do not want to use the default network object created by MultiSystem Manager, define
the NETWORK_NAME or the NETWORK_AG_OBJECT parameters in the GETTOPO statements in the
initialization file.

IBM Tivoli Network Manager Network Objects

MultiSystem Manager creates the following aggregate objects that can be customized:
Networks aggregate object
Represents a group of IP networks and has a resource type of IP networks.
Network object
Represents a single IP network and has a resource type of IP network aggregate.
MultiSystem Manager, by default, groups all IP networks that are extracted from the IBM Tivoli
Network Manager topology database together under a single network aggregate object named
ITNM_IP_Network, as shown in Figure 12 on page 110.
By default, MultiSystem Manager creates a network object, spname_IP_Network, for each IP network.
The spname string represents the value coded on the SP parameter on the GETTOPO statement for that
network.
If you do not want to use the default objects created by MultiSystem Manager, define the
NETWORK_NAME or the NETWORK_AG_OBJECT parameters in the GETTOPO statements in the
initialization file. See Figure 15 on page 112 for an example of the default network object.

Open Topology Interface Network Objects

MultiSystem Manager creates the following aggregate objects that can be customized:
Networks aggregate object
Represents a group of Open networks and has a resource-type of Group.
Network object
Represents a single Open network (an Open topology agent and all its managed resources) and has a
resource-type of Network aggregate.

112 IBM Z NetView: Installation: Configuring Graphical Components

MultiSystem Manager creates a networks aggregate object, applname_Networks, for each topology
agent. The applname string is the value of the APPL parameter on the associated GETTOPO statement.
MultiSystem Manager groups all of the resources in this network under this object.
By default, MultiSystem Manager creates a network object, spname_applname_Network, for each Open
network. The spname string is either the PU or LU portion of SNA network address specified on the SP
parameter on the associated GETTOPO statement. The name applname can be either the name that
is specified on the APPL parameter or, if the ELEMENT parameter is specified, the name that is the
concatenated values of the APPL and ELEMENT parameters (appl.element). See Figure 15 on page 112 for
an example of the default network object.
If you do not want to use the default objects that are created by MultiSystem Manager, define
the NETWORK_NAME or the NETWORK_AG_OBJECT parameters in the GETTOPO statements in the
initialization file.

Creating Network Objects

You can create network objects as described in the following sections:
• “Changing the Name of the Networks Aggregate” on page 113
• “Changing the Name of a Network Aggregate” on page 113
• “Displaying Individual Feature Networks” on page 113

Changing the Name of the Networks Aggregate

By default, MultiSystem Manager names the networks object using the feature name as a prefix, as shown
in Figure 12 on page 110.
To change the name of the default networks aggregate object, use the NETWORK_AG_OBJECT parameter.
For example, to define all first-shift networks under an aggregate object that is displayed only in your
first-shift view, and similarly your off-shift networks to be displayed only in your off-shift view, define your
first-shift aggregate object with a different name than that of your off-shift aggregate object.
To manage networks on both shifts that are displayed in your first-shift and off-shift views, define them
under the same network aggregate object, and define that network aggregate object to be displayed in
each view. To do this, define at least one of the networks under the network aggregate object to be
displayed in each view.
If you define a network setting NETWORK_AG_OBJECT to NONE (NETWORK_AG_OBJECT=NONE), the
network is displayed in only one view, the view that is defined by the GETTOPO initialization file statement
for that network.
Note that all networks that are displayed under the same NETWORK_AG_OBJECT object must be the same
type of network such as Open and IBM Tivoli Network Manager. For example, if you issue the following
GETTOPO commands from your initialization file, you create two different MAINSITE objects:

GETTOPO OPENRES,NETWORK_AG_OBJECT=MAINSITE,......
GETTOPO ITNMRES,NETWORK_AG_OBJECT=MAINSITE,......

Only Open objects can be placed under the MAINSITE object that is created by the GETTOPO OPENERES
command, and only IBM Tivoli Network Manager objects can be placed under the MAINSITE object that is
created by the GETTOPO ITNMRES command.

Changing the Name of a Network Aggregate

By default, MultiSystem Manager names your network aggregate spname._Feature_Network, The
Feature string represents the type of network. To change the name of a network aggregate, use the
NETWORK_NAME parameter.

Displaying Individual Feature Networks

By default, MultiSystem Manager groups all of your networks in a single aggregate object,
Feature_Networks. The Feature string represents the type of network. To display a single network

Appendix C. Customizing the MultiSystem Manager Initialization Statements 113

 on a network view, do not aggregate it with other networks. Use the NETWORK_AG_OBJECT parameter
and specify NONE.
See “Network Configurations and Views” on page 114 for additional examples of how network objects can
be displayed.

Network Configurations and Views

This section describes a series of network configurations and shows sample initialization file statements,
NetView management console windows, MultiSystem Manager network views, and network objects that
are displayed in those views.

Working with Networks

Suppose that your enterprise consists of an IBM Tivoli Network Manager network in New York and an
open network in Boston, and that your initialization file contains the following statements:

GETTOPO ITNMRES SP=NewYork,...

GETTOPO OPENRES SP=Boston,APPL=OPEN,...

In the initialization file, specify topology and status for both networks and their managed resources
(ITNMRES and OPENRES). Also, specify the default network view and the default network objects to be
created.
Figure 16 on page 114 shows the resulting NetView management console window.

Figure 16. NetView Management Console Details Window

When you select MultiSysView from the NetView management console window, you see two cluster
objects, ITNM_IP_Networks for the New York network and OPEN_Networks for the Boston network,
which are shown in Figure 17 on page 115.

114 IBM Z NetView: Installation: Configuring Graphical Components

 Figure 17. NetView Management Console Window

If you select ITNM_IP_Networks and click More Detail, the objects that represent the IBM Tivoli Network
Manager network in New York are displayed. If you select OPEN_Networks and click More Detail, the
objects that represent the open network in Boston are displayed.

A Network Aggregate
Your enterprise consists of the same two networks (New York and Boston), but you want your open
network in Boston to be grouped under a network aggregate named Backup_Network.
In your initialization file, code the IBM Tivoli Network Manager network in New York as you did before,
but, for the open network in Boston, code NETWORK_AG_OBJECT=Backup_Network as follows:

GETTOPO ITNMRES SP=NewYork,...

GETTOPO OPENRES sp=Boston,APPL=OPEN,NETWORK_AG_OBJECT=Backup_Network,...

The resulting NetView management console window has the same network views as shown in Figure 16
on page 114 because a new network view was not created.
When you select MultiSysView from the NetView management console window, you see two cluster
objects, ITNM_IP_Networks and BACKUP_NETWORK, which are shown in Figure 18 on page 116.

Appendix C. Customizing the MultiSystem Manager Initialization Statements 115

 Figure 18. NetView Management Console Network View Window

If you select ITNM_IP_Networks and click More Detail, you see only objects representing the IBM Tivoli
Network Manager network in New York. If you select Backup_Network and click More Detail, you see
only objects representing the open network in Boston.

Displaying a New View and a Network Aggregate

Your enterprise now consists of an IBM Tivoli Network Manager network in New York and an open
network in Boston. Suppose you want your IBM Tivoli Network Manager network in Chicago to display in
its own view called Test_View and to be grouped under an aggregate object named Test_Networks.
To do this, in your initialization file, code the IBM Tivoli Network Manager network in New York and the
open network in Boston as before, and, for the IBM Tivoli Network Manager network in Chicago, code
NETWORK_AG_OBJECT=Test_Networks and NETWORK_VIEW=TEST_VIEW/TEST ITNM NETWORKS, as
follows:

GETTOPO ITNMRES SP=NewYork,...

GETTOPO OPENRES SP=Boston,APPL=OPEN,NETWORK_AG_OBJECT=Backup_Network,...
GETTOPO ITNMRES SP=Chicago,NETWORK_AG_OBJECT=TEST_NETWORKS,
NETWORK_VIEW=TEST_VIEW/TEST ITNM Networks,...

The NetView management console window displays a new network view named TEST_VIEW. If you select
TEST_VIEW, one cluster object named TEST_NETWORKS, which is shown in Figure 19 on page 117, is
displayed.

116 IBM Z NetView: Installation: Configuring Graphical Components

 Figure 19. NetView Management Console Window with Test_View Added

If you select TEST_NETWORKS and click More Detail, only objects representing the Chicago IBM Tivoli
Network Manager network are displayed.

Displaying an Individual Network

Your enterprise now consists of IBM Tivoli Network Manager networks in New York and Chicago and
an open network in Boston. Suppose that you want to display your open network in Raleigh in the
MultiSysView view as an individual network and not under an aggregate object. This way of displaying the
network results in one less level of hierarchy in navigating the NetView management console views.
In your initialization file, define the New York, Boston, and Chicago networks the same, but, for the
Raleigh network, define NETWORK_AG_OBJECT=NONE, as follows:

GETTOPO ITNMRES SP=NewYork,...

GETTOPO OPENRES SP=Boston,APPL=OPEN,NETWORK_AG_OBJECT=Backup_Network,...
GETTOPO ITNMRES SP=Chicago,NETWORK_AG_OBJECT=TEST_NETWORKS,
NETWORK_VIEW=TEST_VIEW/TEST ITNM Networks,...
GETTOPO OPENRES SP=Raleigh,APPL=APPLA NETWORK_AG_OBJECT=NONE,...

The resulting NetView management console window has the same network views as shown in Figure 19
on page 117 because no new network views were created. However, you added the Raleigh network to
the default view (MultiSysView).
When you select MultiSysView from the NetView management console window, you see four objects, two
of which are connected, as shown in Figure 20 on page 118. The ITNM_IP_Networks (New York) and
BACKUP_NETWORK (Boston) networks are displayed as before, but the Raleigh network is also displayed
in the view. The Raleigh open network consists of a real object named RALEIGH_APPLA_Mgr, which
represents the Open topology agent, and an aggregate object named RALEIGH_APPLA_Network, which
represents the Open network.

Appendix C. Customizing the MultiSystem Manager Initialization Statements 117

 Figure 20. NetView Management Console Network Views Window

RALEIGH_APPLA_Network is the default name that is created by adding the LU name of the open
network in Raleigh (RALEIGH) followed by the string _Network to the name of the managing application
for that network.

Naming an Individual Network

Your enterprise now consists of IBM Tivoli Network Manager networks in New York and Chicago and open
networks in Boston and Raleigh. Suppose that you want to display your IBM Tivoli Network Manager
network in Miami in the same view as the Chicago network, the Test_View view, but as an individual
network that is not under an aggregate object. Also, suppose that you want to name the Miami network
TESTNET.
To do this, define the other networks as before in the initialization file, but for the IBM Tivoli Network
Manager network in Miami, define the NETWORK_VIEW keyword as TEST_VIEW/TEST IP NETWORKS and
the NETWORK_NAME keyword as TESTNET, as follows:

GETTOPO ITNMRES SP=NewYork,...

GETTOPO OPENRES SP=Boston,APPL=OPEN,NETWORK_AG_OBJECT=Backup_Network,...
GETTOPO ITNMRES SP=Chicago,NETWORK_AG_OBJECT=TEST_NETWORKS,
NETWORK_VIEW=TEST_VIEW/TEST ITNM Networks,...
GETTOPO OPENRES SP=Raleigh,APPL=APPLA NETWORK_AG_OBJECT=NONE,...
GETTOPO ITNMRES SP=Miami NETWORK_VIEW=TEST_VIEW/TEST IP Networks,
NETWORK_AG_OBJECT=NONE,NETWORK_NAME=TESTNET,...

The resulting NetView management console window has the same network views as shown in Figure 19
on page 117 because no new network views were created. However, you added the Miami network to the
Test_View view.
Clicking Test_View from the NetView management console window displays the view with the Miami
network added, as shown in Figure 21 on page 119. The Miami network is similar to the Raleigh network,
except that the aggregate object that represents the Miami network is named TESTNET instead of the
default name.

118 IBM Z NetView: Installation: Configuring Graphical Components

Figure 21. NetView Management Console Network Views Window

Appendix C. Customizing the MultiSystem Manager Initialization Statements 119

120 IBM Z NetView: Installation: Configuring Graphical Components
Appendix D. Global Variables for MultiSystem
Manager

Table 22 on page 121 lists the global variables used by the MultiSystem Manager topology manager
to store information about MultiSystem Manager. See IBM Z NetView Administration Reference for an
explanation of the referenced initialization statements.

Table 22. MultiSystem Manager Global Variables

Variable Name Description
FLC_DEF_AUTOTASK Default Autotask Name
The name of the default autotask that MultiSystem
Manager is using to process topology and
status requests. This name is specified on the
(MSM)function.autotask.MSMdefault statement in
the CNMSTYLE member.

FLC_DEF_NETWORK_VIEW_DESC Default Network View Description

The description for the default network view. This
description is specified on the network_view_annotation
portion of the (MSM)COMMON.FLC_DEF_NETW_VIEW
statement in the CNMSTYLE member.

FLC_DEF_NETWORK_VIEW_NAME Default Network View Name

The name of the MultiSystem Manager default
network-level view. This name is specified
on the network_view_name portion of the
(MSM)COMMON.FLC_DEF_NETW_VIEW statement in the
CNMSTYLE member.

FLC_EXCEPTION_VIEW_FILE Exception View File Name

The name of the exception view file that MultiSystem
Manager is using for exception view processing.
The name of this file is specified on the
(MSM)COMMON.FLC_EXCEPTION_VIEW_FILE statement
in the CNMSTYLE member.

FLC_INFILE_NAME Initialization Member Name

The name of the current MultiSystem Manager
initialization file. This is the name of the initialization
member specified on the INITTOPO command. If the
initialization member was not specified on the INITTOPO
command, the default initialization member FLCAINP
was used. See the online help or the IBM Z NetView
Command Reference Volume 2 (O-Z) for information about
the INITTOPO command.

© Copyright IBM Corp. 2001, 2019 121

 Table 22. MultiSystem Manager Global Variables (continued)
Variable Name Description
FLC_RODMAPPL RODM Application ID
The user application ID used by MultiSystem Manager
to access RODM. This ID is specified on the
COMMON.FLC_RODMAPPL statement in the CNMSTYLE
member.

FLC_RODMINT RODM Interval

The amount of time, in seconds, between retries of
a RODM request that has failed because RODM is
checkpointing. When RODM is checkpointing to disk,
it cannot process certain transactions, so MultiSystem
Manager must wait until the checkpoint process is
finished. If MultiSystem Manager tries but cannot
access the information because RODM is checkpointing,
it waits and tries again. This value is specified on
the (MSM)COMMON.FLC_RODMINT statement in the
CNMSTYLE member.

FLC_RODMNAME RODM Name

The name of the RODM that MultiSystem Manager is
using to store topology and status information. This
name is specified on the (MSM)COMMON.FLC_RODMNAME
statement in the CNMSTYLE member.

FLC_RODMRETRY RODM Retry Count

The number of times MultiSystem Manager retries
a RODM request that has failed because RODM is
checkpointing. When RODM is checkpointing to disk,
it cannot process certain transactions, so MultiSystem
Manager must wait until the checkpoint process is
finished. If MultiSystem Manager tries but cannot access
the information because RODM is checkpointing, it
waits and tries again. This number is specified on
the (MSM)COMMON.FLC_RODMRETRY statement in the
CNMSTYLE member.

FLC_RUNCMDRETRY RUNCMD Retry Count

The number of times a RUNCMD is retried after
an initial failure that has a sense code of 0851
(session busy). This value is specified on the
(MSM)COMMON.FLC_RUNCMDRETRY statement in the
CNMSTYLE member.

122 IBM Z NetView: Installation: Configuring Graphical Components

Table 22. MultiSystem Manager Global Variables (continued)
Variable Name Description
FLC_TOPOMGR_STATUS Current® Status
The current status of MultiSystem Manager. See “Issuing
the INITTOPO Command” on page 57 for information
about initializing MultiSystem Manager.
ENABLED
MultiSystem Manager can process GETTOPO
commands.
INITIALIZATION_FAILED
MultiSystem Manager cannot process GETTOPO
commands. An INITTOPO command was issued,
but initialization failed. The failure was because
of a syntax error or incorrect information in the
initialization file.
INITIALIZING
An INITTOPO command was issued and MultiSystem
Manager is processing the initialization file. After the
initialization file is processed, the status is changed to
INITIALIZATION_FAILED or ENABLED.
NEVER_INITIALIZED
MultiSystem Manager has not been initialized and
cannot process GETTOPO commands.
SUSPENDED
A SUSPTOPO command was issued and the
processing of GETTOPO commands is suspended.

Appendix D. Global Variables for MultiSystem Manager 123

124 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, 2019 125

 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”

126 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 127
128 IBM Z NetView: Installation: Configuring Graphical Components
Index

Special Characters autotasks (continued)

FLBTOPO 42
(MSM)COMMON.FLC_EXCEPTION_VIEW_FILE 106
(MSM)COMMON.FLC_RODMINT 105
(MSM)COMMON.FLC_RODMRETRY 105
B
(MSM)COMMON.FLC_RUNCMDRETRY 106 benefits, MultiSystem Manager 2
(MSM)function.autotask.MSMdefault 106 BLDVIEWS
RODM 73
A books
see publications ix
A01APPLS 41
accessibility xii
activating
C
NetView Resource Manager characteristics
AUTONRM 61 local node
initialization 63 LAN 79
initialization, display status defaults 63 checkpoint data sets
initialization, monitoring remote systems 63 RODM 9
initialization, sampling 63 CMIP
security 61 agent 39
security, command authorization 62 filtering 39
agent services, starting 42
installing 39 CNMCMENT
placement 39 command definitions 90
SNA topology manager 39 CNME2101, GMFHS command list 6
SNATM 39 CNMGMFHS 18, 25
VTAM topology 39 CNMHELPR
agents helpmap 90
installing CNMS0013 41
IBM Tivoli Network Manager agent 46 CNMS4290 90
open agent 46 CNMSID01
open topology interface 46 delete VSAM databases 90
MultiSystem Manager 45 CNMSJ004
alert history file 45 allocate logs and databases 90
allocating job
VSAM clusters allocating VSAM clusters for RODM 9
for RODM 9 CNMSJH10 18, 25
allocating VSAM clusters for RODM CNMSJH12
CNMSID01 9 load RODM data cache 90
APPN networks CNMSJH13 83
managing 1 CNMSJI10
APPNTM user ID 41 EIBCOPY 90
AUTH statement CNMSNIFF 83
NGMFADMN keyword usage 32 CNMSTYLE
NGMFCMDS keyword usage 32 event manager autotask 19
automation GMFHS global variables 6
AON-based 52 initialization statements 105
NetView 52 MultiSystem Manager, enabling 6
RODM-based 52 RODM global variables 5
AUTOMSMD 106 status focal point 30
AUTOMSMD autotask 52 TCP/IP 30
AUTONRM CNMSTYLE initialization statements
NetView Resource Manager 61 COMMON.FLC_DEFAULT_ITNM_OBJECT_STATUS 69
AUTORATE statement 56 customizing 105
autotasks CNMSXENT 101
AUTOMSMD 52 CNMTAMEL
event manager 19 task definitions 89

Index 129
CNMTAMEL task 30 data models
collection manager loading GMFHS 25
RODM 73 loading MultiSystem Manager 25
command authorization loading SNA topology manager 25
discovery manager security 67 default autotask
NetView Resource Manager security 62 (MSM)function.autotask.MSMdefault 106
command definition statements default network object example
GMFHS 83 NetView management console 112
COMMON.FLC_DEFAULT_ITNM_OBJECT_STATUS statement default network objects, using
69 IP 112
COMMON.FLC_RODMNAME 105 default objects, using
communication protocol 47, 107 IP 112
Communications Server Open Topology Interface 113
configuring for SNA, NetView management console 77 default status color 69
local LU profile 79 default views, changing names
local modes profile 80 NetView management console 111
transaction program definitions 80 defining
Communications Server, using NetView Resource Manager
to configure for SNA LU 6.2 Autotask 61
workstation network 78 VSAM clusters
configuration diagrams for RODM 9
individual network 117 defining IP socket port numbers 33
naming individual networks 118 defining resources
network aggregate 115 RACF 12
new view, network aggregate 116 defining the LU name 77
configuring DELVIEWS
communications server RODM 74
configuring for SNA LU 6.2 77 directory names, notation xiii
for user rights for Windows systems 36 discovery manager
topology server 33 activating 67
workstation network, NetView management console command authorization 67
configuring for SNA 77 enabling 68
configuring for SNA LU 6.2 managing resources 68
workstation network, NetView management console preparing 67
using Communications Server 78 RODM access 67
connecting to RODM 14 security considerations 67
connections displaying individual feature networks 113
for LAN 81 DISPTOPO command 59
control profile, data link documentation and tools, external 60
for LAN 78 DSIGDS task 55
conventions DSIQTSK task 17
typeface xii DSIQTSKI 17, 90
correlating DUIDGHB task 30
views 71 DUIFCSGW
correlating objects command processor 19
enabling DUIFCUX2 83
SNA topology manager 71 DUIFCUXM, exception views 84
COS gateway autotask 19 DUIFDEXV 84
CPDLB2 volume 10 DUIFEDEF 84
creating additional network views DUIFEMDY 84
NetView management console 111 DUIFEUSR 84
creating views 110 DUIFHNAM global variable 6
creating your own network views 111 DUIFHPRC global variable 6
cross-domain environment DUIFPMEM 89
MultiSystem Manager 54 DUIFSMT 89
customization DUIFSNET
RODM 15 non-SNA network
customizing initialization statements in CNMSTYLE 105 24
DUIFSSCO 19
DUIFSTRC
D GMFHS data model 25
data link DUIGINIT 84
control profile DUIGPWLU 19, 84
for LAN 78 DUIIGHB 31, 84

130 IBM Z NetView: Installation: Configuring Graphical Components

DUIISFP 17, 31, 89 FLBOSIDS
DUILOGON command 31 view customization 41
DUIPOLCY 89 FLBOSIDU 101
dump utility, RODM 11 FLBS8001 101
FLBS8002 101
FLBSRT
E view customization 41
EDGXRODM FLBSRTU 101
start procedure 15 FLBSYSD
EGVREAD1.ME 37 initialization 41
EGVREAD2.ME 33 FLBTPROF 101
EKGCUST FLBTRDM*
sample customization member 15 SNA topology manager data models 25
EKGHNAM global variable 5 FLBTRDM1 101
EKGHPRC global variable 5 FLBTRDM2 101
EKGKUJCL 98 FLBTRDM3 102
EKGMIMV FLBTRDM4 102
named method 98 FLBTRDM5 102
EKGNEQL FLBTRDM6 102
notification method 98 FLBTRDM7 102
EKGNLST FLBTRDM8 102
notification method 98 FLBTRDM9 102
EKGNOTF FLBTRDMA 102
notification method 98 FLBTRDMB 102
EKGNTHD FLBTRDMC 102
notification method 98 FLBTRDMD 102
EKGOPPI FLBTRDME 102
object independent method 98 FLBTRDMG 102
EKGPTENU 98 FLBTRDMH 102
EKGRDUMP 98 FLBTRDMI 102
EKGRLOG FLBTRDMJ 102
log formatter JCL 10 FLBTRDMZ 102
EKGSI101 FLBTREU 102
RODM checkpoint data set 9 FLBTRSC1 102
RODM logs 9 FLBTRSC2 103
EKGSI202 98 FLBTRSC3 103
EKGSNIFF 83 FLBTRSC4 103
EKGSVER FLBTRSC5 103
verification member 23 FLBTRSC6 103
EKGXRODM FLBTRSN1 103
sample start job 20 FLBTRSN2 103
ELEMENT parameter 109 FLBTRSN3 103
enabling FLBTRSN4 103
NetView Resource Manager 7 FLBTRSN5 103
object correlation FLBTRSN6 103
for additional SNA topology manager 72 FLBTRUM 103
SNA topology tanager 71 FLC_DEF_AUTOTASK 121
environment variables, notation xiii FLC_DEF_NETWORK_VIEW_DESC 121
Ethernet LAN-attached workstation, defining 75 FLC_DEF_NETWORK_VIEW_NAME 121
event manager 19 FLC_EXCEPTION_VIEW_FILE 121
event viewer 45 FLC_INFILE_NAME 121
exception views FLC_RODMAPPL 122
defining in CNMSTYLE 106 FLC_RODMINT 122
implementing 71 FLC_RODMNAME 122
FLC_RODMRETRY 122
FLC_RUNCMDRETRY 122
F FLC_TOPOMGR_STATUS 123
FLCAINP 105
FLBAUT automation table entries 101
FLCAINP initialization file 52
FLBAUT, automation manager 41
FLCAINP initialization sample 85
FLBEXV
FLCARODM
view customization 41
samples 99
FLBEXV exception view table 101
FLCCCHK 85
FLBEXVU exception view table, user entry 101
FLCSDM*

Index 131
FLCSDM* (continued) global variables (continued)
MultiSystem Manager data models 25 FLC_RUNCMDRETRY 122
FLCSDM1 FLC_TOPOMGR_STATUS 123
data model definition 85 GMFHS 6
FLCSDM2 RODM 5
data model definition 85 GMFHS
FLCSDM3 automation example 83
data model definition 85 CNME2101 6
FLCSDM4 command definition statements 83
data model definition 85 COS gateway autotask 19
FLCSDM5 data model, loading 25
data model definition 86 defining event manager autotask 19
FLCSDM6 description 1
data model definition 86 global variables 6
FLCSDM6O 88 initialization 83
FLCSDM8 initialization parameters
data model definition 86 CNMSTYLE 84
FLCSDM9 DUIGINIT 84
data model definition 86 initialization values 18
FLCSEXV exception view file 86 installing 18
FLCSIOPN 53, 88 main task 18
FLCSITNM 53, 87 message routing 19
FLCSOALH 88 restricting server access 19
FLCSOAUT 88 samples 83
FLCSOPF scope checker OPT 19
operator definitions 86 start procedure 18, 83
FLCSOX01 88 starting 25
FLCSPAUT 87 verifying installation 27
FLCSPRFB GMFHS resources, additional
operator profiles 86 enabling object correlation 72
FLCSPRFB operator profile 50 GMFHS STATUS 27
focal point commands, issuing 57
FTP site 60
H
G hardware monitor data base
alerts, overloading 56
GETTOPO command HEARTBEAT parameter 108
additional parameters host name 107
IBM Tivoli Network Manager 108 HOSTONLY parameter 109
Open Topology Interface 109 HOSTS parameter 108
APPL parameter 106 HP OpenView servers, topology agent 45
HEARTBEAT parameter 108
HOSTONLY parameter 109
HOSTS parameter 108
I
ITNMONLY 108 IBM Tivoli Network Manager
ITNMRES 108 additional GETTOPO parameters 108
OPENRES parameter 109 ITNMONLY 108
REMOTE parameterr 106 ITNMRES 108
SP parameter 106 managing hosts 108
UNMANAGED parameter 108 viewing unmanaged resources 108
GETTOPO commands 59 IBM Tivoli Network Manager hosts, managing 108
GHB.TCPANAME keyword 31 initialization
global variables for NetView Resource Manager
DUIFHNAM 6 display status defaults 63
DUIFHPRC 6 monitoring remote systems 63
FLC_DEF_AUTOTASK 121 sampling 63
FLC_DEF_NETWORK_VIEW_DESC 121 initialization file
FLC_DEF_NETWORK_VIEW_NAME 121 MultiSystem Manager 52
FLC_EXCEPTION_VIEW_FILE 121 sample 105
FLC_INFILE_NAME 121 initialization file, sample
FLC_RODMAPPL 122 FLCSIOPN 53
FLC_RODMINT 122 FLCSITNM 53
FLC_RODMNAME 122 initialization statements
FLC_RODMRETRY 122

132 IBM Z NetView: Installation: Configuring Graphical Components

initialization statements (continued) msm_nm_ip_readme_en.html 46
customizing 105 MSMTOOLK 60
purpose 105 MSMTOOLK package 46
initialization steps 56 MultiSystem Manager
INITTOPO command 56 agents 2
INITTOPO command, issuing 57 alerts, repetitive 56
installation CNMSTYLE updates 6
verifying for NetView Resource Manager 64 command authorization 50
installing command definition statements
GMFHS 18 CNMCMENT 84
MultiSystem Manager 47 FLCSCHK 85
NetView management console 29 correlating views 71
RODM 9 cross-domain environment 54
SNA topology manager 41 data model definition
Internet protocol (IP) networks 45 FLCSDM1 85
IP FLCSDM2 85
network object 112 FLCSDM3 85
networks aggregate object 112 FLCSDM4 85
using default network objects 112 FLCSDM5 86
using the default objects 112 FLCSDM6 86
ITNMONLY 108 FLCSDM8 86
ITNMRES 108 FLCSDM9 86
data model, loading 25
exception view file 86
L GETTOPO commands 59
LAN initialization 84
connections 81 initialization file
data link control profile 78 sample FLCAINP 85
local node characteristics 79 installation verification 59
LAN-attached workstation definitions 75, 76 installing 47
Linux for zSeries 45 MSMTOOLK package 46
local LU profile 79 operator definitions 86
local modes profile 80 operator profiles 52, 86
local node characteristics overview 2
LAN 79 RMTCMD commands 54
log formatter RUNCMD commands 54
RODM 10 RUNCMD, DSRBs 55
LU 6.2 connectivity 75 RUNCMD, timeout value 55
LU 6.2 sessions samples 84
configuring Communications Server security considerations 50
workstation network, NetView management span of control 51
console 77 starting 56
configuring workstation network topology agents 45
using Communications Server 78 topology, controlling collection 59
LU name 107 MultiSysView
LU, local NetView management console 109
profile 79 MVS subsystem
LU6.2 107 RODM 9

M N
management applications, creating 59 NCP
manuals definitions
see publications ix NetView management console 75
MAXLNTH statement 13 NCP node 39
method, notification 98 NETCMD command 20
modes, local NetView management console
profile 80 1st_Shift_View 111
monitoring changing the name of the default view 111
remote NetView systems configuring the server 33
NetView Resource Manager 63 creating additional network views 111
RMTCMD considerations 64 default network object example 112
monitoring resources 45 defining objects 109
defining views 109

Index 133
NetView management console (continued) node characteristics, local (continued)
installation verification 37 LAN 79
installing 29 notation
LAN definitions 75, 76 environment variables xiii
MultiSysView 109 path names xiii
network views 109 typeface xiii
NMCSTATUS autotask 20 notification method 98
Off_Shift_View 111
resource time schedules 71
samples 89
O
security 31 object class definitions
topology console, installing 37 RODM 24
topology server object correlation
communication, starting 37 enabling
configuring 33 for additional SNA topology manager 72
installing 33 SNA topology manager 71
restricting access to GMFHS 19 enabling for additional SNA topology manager 72
topology workstation Off_Shift_View
signing on 38 NetView management console 111
using default network objects online publications
IP 112 accessing xi
using the default network views 110 OPEN topology agents 45
NetView Resource Manager Open Topology Interface
activating additional GETTOPO parameters 109
AUTONRM 61 ELEMENT parameter 109
initialization 63 HOSTONLY parameter 109
initialization, display status defaults 63 network object 112
initialization, monitoring remote systems 63 network objects 112
initialization, sampling 63 networks aggregate object 112
security 61 OPENRES parameter 109
security, command authorization 62 samples 88
enabling 7 using default objects 113
preparing OPENRES parameter 109
AUTONRM 61 OSI
initialization 63 status entries 101
initialization, display status defaults 63 OSIMGMT 39
initialization, monitoring remote systems 63
initialization, sampling 63
security 61 P
security, command authorization 62
path names, notation xiii
starting 64
port numbers, reassigning 33
verifying installation 64
preparing
network aggregate, changing names 113
NetView Resource Manager
network object
AUTONRM 61
Internet Protocol 112
initialization 63
IP 112
initialization, display status defaults 63
network objects
initialization, monitoring remote systems 63
Open Topology Interface 112
initialization, sampling 63
network objects, creating 113
security 61
network topology, initializing 56
security, command authorization 62
network views
profile
NetView management console 109
local LU 79
networks
local modes 80
creating 111
profile, control
using 114
data link for LAN 78
networks aggregate object
PU name 107
IP 112
publications
Open Topology Interface 112
accessing online xi
networks aggregate, changing names 113
IBM Z NetView ix
NGMFADMN keyword, AUTH statement 32
ordering xii
NGMFCMDS keyword, AUTH statement 32
NMCSTATUS autotask 20
NMCSTATUS policy definitions 71
node characteristics, local

134 IBM Z NetView: Installation: Configuring Graphical Components

R RODM (continued)
log 98
RACF log formatter 98
RODM security 11 MVS subsystem, defining 9
SNA topology manager 41 object load 97
RACF security RODM Unloader 72
defining resources 12 RODMVIEW 72
RATE statement 56 samples 90
readme files SEC_CLASS field 11
EGVREAD1.ME 37 SEC_RNAME field 12
EGVREAD2.ME 33 security 11
msm_nm_ip_readme_en.html 46 start procedure 15
reassigning port numbers 33 start with EKGXRODM 99
REMOTE parameter, coding 107 starting 20
Resource Manager, NetView structure load 97
enabling 7 tasks 90
resource object data manager tools
using RODM dump utility 11 BLDVIEWS 73
resources DELVIEWS 74
access, controlling 51 RODM collection manager 73
RESTOPO command 58 RODM Unloader 72
REXX environment RODMVIEW 72
tuning 56 using dump utility 11
RMTCMD considerations verifying using EKGSVER 23
monitoring remote NetView systems 64 views
RODM customizing 73
allocate log using CNMSJ004 90 deleting 74
allocating VSAM clusters 9 RODM collection manager 73
allocating VSAM clusters for RODM connection 14
CNMSID01 9 RODM tools 72
BLDVIEWS 73 RODM Unloader 72
checkpoint data set 98 RODMINT
checkpointing 105 (MSM)COMMON.FLC_RODMINT 105
command definitions 90 RODMNAME
customization file, sample 97 COMMON.FLC_RODMNAME 105
customization parameters 15 RODMRETRY
data model, sample 84 (MSM)COMMON.FLC_RODMRETRY 105
defining 105 RODMVIEW
defining security RODM 72
to RODMMGR class 11 RUNCMD
to user-defined class 12 DSRBs 55
defining the checkpoint data sets 9 timeout value 55
defining, GMFHS 105 RUNCMD retry count
definition statement (MSM)COMMON.FLC_RUNCMDRETRY 106
MAXLNTH 13 RUNCMDRETRY
delete VSAM databases, using CNMSID01 90 (MSM)COMMON.FLC_RUNCMDRETRY 106
DELVIEWS 74
description 1
DSIQTSK 17
S
dump utility 98 samples
ending 23 A01APPLS 41
exception views 84 CNMGMFHS 18, 25
global variables 5 CNMHELPW 89
helpmap 90 CNMS0013 41
initialization method CNMSAF 89
sample 98 CNMSCAT2 89
initialization values 17 CNMSJ004 9
installation verification CNMSJH10 25
EKGSVER 99 CNMSJH12 24
installing 9 DUIFSNET 24
load file, sample 84 DUIGINIT 19
load RODM data cache EKGCUST 15
CNMSJH12 90 EKGSI101 9
loading the data cache 24 FLCAINP 52

Index 135
samples (continued) starting (continued)
FLCSPRFB 50 NetView Resource Manager 64
GMFHS 83 RODM 20
MultiSystem Manager 84 status defaults
open topology feature 88 displaying for NetView Resource Manager 63
RODM 90 storing topology server databases 34
SNA topology manager 101 SUSPTOPO command 58
sampling SWNET node 39
NetView Resource Manager 63 system authorization facility product
scope checker OPT 19 RODMMGR class 11
SEC_CLASS
field in RODM 11
SEC_RNAME field in RODM 12
T
security TAMEL.CONV keyword 30
for NetView Resource Manager TAMEL.PORT keyword 30
command authorization 62 TAMEL.SOCKETS keyword 30
for the discovery manager 67 TAMEL.TCPANAME keyword 30
service points TAMEL.TTLS keyword 30
cross-domain 54 tasks
receiving commands 19 CNMTAMEL 25
service points, defining 106 DSIGDS 55
SNA LU 6.2 sessions DSIQTSK 17
configuring Communications Server TCP/IP 30
workstation network, NetView management TCP/IP host name 107
console 77 Tivoli
configuring workstation network user groups xii
using Communications Server 78 Tivoli Software Information Center xi
SNA networks token-ring
managing 1 LAN-attached workstation
SNA topology manager defining 76
agent 2, 39 topology
agent placement 39 correlation 71
automation table entries 101 topology agents
automation, FLBAUT 41 creating workstation-based 59
command definitions 101 role 45
commands 42 topology console, installing 37
controlling topology gathering 41 topology manager, SNA
correlating objects correlating objects
enabling 71 enabling 71
customizing views 41 topology managers
data model, loading 25 creating MVS-based 60
description 1 topology processing information, displaying 59
exception view table 101 topology requests
initialization file 41, 101 processing 58
installation verification 42 resuming processing 58
loader file 102 suspending processing 58
message suppression options 41 topology server
operator profile statements 101 configuring 33
OSI display status table 101 configuring as a UNIX daemon 36
samples 101 configuring as a Windows service 36
security requirements 41 defining IP socket port numbers 33
starting 42 defining the LU name 77
status resolution table 101 NetView management console, installing 33
VTAM requirement 41 reassigning port numbers 33
SP parameter setting security 35
coding 107 storing databases 34
specifying, IP protocol 107 updating the TSERVER_DB variable 35
specifying, SNA protocol 107 topology server running as a UNIX daemon 36
span of control topology server running as a Windows service 36
resources 70 topology servers
views 70 defining to
SSCP-PU 107 token-ring LAN-attached 76
starting TOPOSNA commands 42
GMFHS 25 transaction program definitions 80

136 IBM Z NetView: Installation: Configuring Graphical Components

tserver dbtransfer command 35 workstation network, NetView management console (continued)
TSERVER_DB variable 35 configuring for SNA 77
tuning
REXX environment 56
typeface conventions xii
X
XCA node 39
U
Unloader
RODM 72
UNMANAGED parameter 108
updating the TSERVER_DB variable 35
user group, NetView xii
user groups
NetView xii
Tivoli xii
using default network views
NetView management console 110

V
variables, notation for xiii
verifying
CNMSXENT 101
installation
NetView Resource Manager 64
RODM installation 23
SNA topology manager 101
viewing unmanaged resources, IBM Tivoli Network Manager
108
views
access, controlling 51
correlating 71
customizing 73
deleting 74
managing 69, 72
resource time schedules 71
restricting access 70
VSAM
allocating
for RODM 9
VSAM clusters for RODM, allocating
CNMSID01 9
VTAM
APPL names, SNA topology manager 39, 41
CMIP agent 39
CMIP filtering 41
definitions
NetView management console 75
VTAM agent 39
VTAM CMIP agent 41

W
workstation
defining
Ethernet LAN-attached 75
token-ring LAN-attached 76
workstation configuration
configuring for SNA, NetView management console 77
workstation network, NetView management console
configuring Communications Server
for SNA LU 6.2 77

Index 137
138 IBM Z NetView: Installation: Configuring Graphical Components
IBM®

GC27-2852-03