Automation using tivoli net view os 390 v1r3 and system automation os-390 v1r3 sg245515

SG24-5515-00

International Technical Support Organization

www.redbooks.ibm.com

Automation Using Tivoli NetView OS/390 V1R3and System Automation OS/390 V1R3

Holger Stamme, Ling Xiao Gao, Marcio Guimaraes, Clive Kennedy, Jason Wyer

http://www.redbooks.ibm.com/

Automation Using Tivoli NetView OS/390 V1R3and System Automation OS/390 V1R3

March 2000

SG24-5515-00

International Technical Support Organization

© Copyright International Business Machines Corporation 2000. All rights reserved.Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure issubject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

First Edition (March 2000)

This edition applies to Tivoli NetView for OS/390 V1R3 and System Automation for OS/390 V1R3 foruse with the OS/390.

This document created or updated on March 14, 2000.

Comments may be addressed to:IBM Corporation, International Technical Support OrganizationDept. OSJB Building 003 Internal Zip 283411400 Burnet RoadAustin, Texas 78758-3493

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute theinformation in any way it believes appropriate without incurring any obligation to you.

Before using this information and the product it supports, be sure to read the general information inAppendix D, “Special notices” on page 245.

Take Note!

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Introduction to Tivoli NetView for OS/390 V1R3 . . . . . . . . . . 11.1 At a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.3.1 IP management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.3.2 Graphical console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.3 Automation features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.4 Other customer satisfaction enhancements . . . . . . . . . . . . . . . . . 71.3.5 Product positioning in the market . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2. Benefits of using System Automation for OS/390 . . . . . . . 112.1 Why automate? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Proactive management of OS/390 subsystem tasks . . . . . . . . . . . . . . 122.3 Monitoring and recovery capabilities of OS/390 subsystems . . . . . . . 122.4 Automation features of System Automation for OS/390 V1R3 . . . . . . 13

2.4.1 New Interface - Single system image support . . . . . . . . . . . . . . . 132.4.2 Better managing your applications . . . . . . . . . . . . . . . . . . . . . . . 132.4.3 Simultaneously updating policy databases for applications . . . . . 142.4.4 Notifying the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . 142.4.5 Other enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3. The ITSO automation project environment . . . . . . . . . . . . . 173.1 Types of communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1.1 Communication using a LU 6.2 session . . . . . . . . . . . . . . . . . . . 193.1.2 Communication using a LUC session . . . . . . . . . . . . . . . . . . . . . 203.1.3 Communication using an OST-NNT session . . . . . . . . . . . . . . . . 20

3.2 Resource Object Data Manager (RODM) . . . . . . . . . . . . . . . . . . . . . . 203.2.1 RODM object oriented structure . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.3 Graphic Monitor Facility Host Subsystem (GMFHS) . . . . . . . . . . . . . . 213.4 Status Display Facility (SDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4. Customization of Tivoli NetView OS/390. . . . . . . . . . . . . . . 254.1 Planning the Tivoli NetView for OS/390 environment . . . . . . . . . . . . . 264.2 Defining the Tivoli NetView for OS/390 environment . . . . . . . . . . . . . 27

4.2.1 Recommended library structure in multi-system environment . . . 274.2.2 OS/390 subsystem extensions . . . . . . . . . . . . . . . . . . . . . . . . . . 314.2.3 Usage of OS/390 system symbolics . . . . . . . . . . . . . . . . . . . . . . 32

© Copyright IBM Corp. 2000 iii

4.3 Network management environment . . . . . . . . . . . . . . . . . . . . . . . . . . 334.3.1 Creation of common networking NetView libraries . . . . . . . . . . . 344.3.2 Setting up the base components NetView for OS/390. . . . . . . . . 364.3.3 Setting up the Resource Object Data Manager . . . . . . . . . . . . . . 364.3.4 Setting up the Graphic Monitor Facility Host Subsystem. . . . . . . 374.3.5 Setting up the Automated Operation Network feature . . . . . . . . . 374.3.6 Creation of local (domain specific) NetView libraries . . . . . . . . . 37

4.4 Automation environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.4.1 Creation of common automation NetView libraries . . . . . . . . . . . 404.4.2 Setting up the base NetView for OS/390. . . . . . . . . . . . . . . . . . . 474.4.3 Setting up the Resource Object Data Manager . . . . . . . . . . . . . . 474.4.4 Customizing RODM load jobs in the automation environment . . . 494.4.5 Setting up the Graphic Monitor Facility Host Subsystem. . . . . . . 494.4.6 Creation of local (domain specific) NetView libraries . . . . . . . . . 50

Chapter 5. Customization of System Automation for OS/390 . . . . . . . 535.1 Base System Automation customization . . . . . . . . . . . . . . . . . . . . . . . 53

5.1.1 Preparation and set up jobs for System Automation . . . . . . . . . . 535.1.2 Preparing the OS/390 system environment and library . . . . . . . . 555.1.3 Creating System Automation policy database dialog panels . . . . 56

5.2 Usage of system symbolics and System Automation synonyms . . . . . 595.3 Defining all systems and objects to System Automation . . . . . . . . . . . 60

5.3.1 Starting the System Automation policy database dialog . . . . . . . 615.3.2 Creating a new System Automation policy database. . . . . . . . . . 625.3.3 Entering all systems and objects . . . . . . . . . . . . . . . . . . . . . . . . 645.3.4 Building SA Automation Control File (ACF) . . . . . . . . . . . . . . . . . . . . 985.3.5 Build RODM loader input file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

5.4 Defining dependencies and start-up behavior . . . . . . . . . . . . . . . . . . 1035.4.1 Define dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.2 Define start-up behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

5.5 Customizing the Status Display Facility (SDF) . . . . . . . . . . . . . . . . . 1085.5.1 Customizing the panel member AOFPNLS . . . . . . . . . . . . . . . . 1085.5.2 Customizing the status member AOFTREE . . . . . . . . . . . . . . . 1105.5.3 Defining SDF gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115.5.4 Starting the SDF monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 6. Installation of the NetView Management Console . . . . . . 1156.1 Prerequisites for NetView Management Console Version 1.3 . . . . . . 1176.2 Setting up the NMC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

6.2.1 Installing NMC Server to run as a Windows NT service . . . . . . 1176.2.2 Setting up NMC Topology Server for Systems Automation . . . . 1236.2.3 Starting the NMC Topology Server using TCP/IP . . . . . . . . . . . 1276.2.4 Uninstalling the NMC Topology Server . . . . . . . . . . . . . . . . . . . 128

iv Automation Using Tivoli NetView OS/390 V1R3 and System Automation OS/390 V1R3

6.2.5 Hints and tips for the NMC Topology Server . . . . . . . . . . . . . . . 1296.3 Setting up the NMC client workstation . . . . . . . . . . . . . . . . . . . . . . . 131

6.3.1 Installing the NMC Topology Console . . . . . . . . . . . . . . . . . . . . 1316.3.2 Starting the NMC Console using a TCP/IP connection . . . . . . . 1336.3.3 Uninstalling the Tivoli NMC Topology Console . . . . . . . . . . . . . 1346.3.4 Hints and tips for the NMC Topology Console . . . . . . . . . . . . . 1356.3.5 Issuing SA OS/390 commands using the NMC . . . . . . . . . . . . . 135

6.4 Setting up the Web interface to Tivoli NetView OS/390 . . . . . . . . . . 1406.5 Setting up the NetView 3270 Management Console . . . . . . . . . . . . . 142

6.5.1 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426.5.2 Selecting the correct files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1436.5.3 Available documentation and technical information. . . . . . . . . . 1446.5.4 Setting up the host (mainframe) environment . . . . . . . . . . . . . . 1446.5.5 Installing NetView 3270 Console on Windows 95, 98, and NT . 1466.5.6 Uninstalling the NetView 3270 Console . . . . . . . . . . . . . . . . . . 1506.5.7 Replicating the NetView 3270 Console . . . . . . . . . . . . . . . . . . . 1516.5.8 Operating notes, hints, and tips . . . . . . . . . . . . . . . . . . . . . . . . 152

Chapter 7. Maintenance of Tivoli NetView and System Automation . 1557.1 Automation table maintenance using AUTOMAN . . . . . . . . . . . . . . . 155

7.1.1 Enabling the AUTOMAN function for the Automation NetView . 1557.1.2 Using AUTOMAN command . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

7.2 Netview and automation table optimization for performance . . . . . . . 1667.2.1 NetView automation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1667.2.2 Additional hints and tuning considerations . . . . . . . . . . . . . . . . 168

7.3 Maintenance of the System Automation policy data base . . . . . . . . . 1707.3.1 Design a hierarchical structure . . . . . . . . . . . . . . . . . . . . . . . . . 1707.3.2 Using ADD/REMOVE commands . . . . . . . . . . . . . . . . . . . . . . . 1717.3.3 RACF considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717.3.4 System Automation migration . . . . . . . . . . . . . . . . . . . . . . . . . . 1727.3.5 Building for ACF and RODM . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727.3.6 Policy report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737.3.7 ACFPLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Chapter 8. Base automation features . . . . . . . . . . . . . . . . . . . . . . . . . 1758.1 New automation table features of NetView for OS/390 V1R3 . . . . . . 175

8.1.1 Multi-line message support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758.1.2 IF-THEN condition item substrings . . . . . . . . . . . . . . . . . . . . . . 1768.1.3 Greater-than and less-than operator support . . . . . . . . . . . . . . 1778.1.4 Numeric comparison and current time support . . . . . . . . . . . . . 1778.1.5 Variable value function support. . . . . . . . . . . . . . . . . . . . . . . . . 1778.1.6 Message reformatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1788.1.7 Automation table tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

v

8.1.8 The AUTOMATED function. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1808.2 System Automation framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

8.2.1 Automating subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1818.2.2 Automating messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

8.3 System Automation and NetView base automation rules . . . . . . . . . 197

Chapter 9. Automation example scenarios . . . . . . . . . . . . . . . . . . . . . 1999.1 NetView SMTP mail gateway support . . . . . . . . . . . . . . . . . . . . . . . . 199

9.1.1 NetView provided samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1999.1.2 Required customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2009.1.3 Sending SMTP e-mail with EZLEMAIL . . . . . . . . . . . . . . . . . . . 2019.1.4 Sending SMTP e-mail from AON Inform policies. . . . . . . . . . . . 2029.1.5 Sending SMTP e-mail from user-written clists. . . . . . . . . . . . . . 203

9.2 System Automation in a multi-system focal point environment . . . . . 2049.2.1 Defining Automation Network process . . . . . . . . . . . . . . . . . . . 205

9.3 Using NetView AON inform policies by System Automation . . . . . . . 2149.3.1 Installation of AON inform policy in the Automation NetView. . . 2149.3.2 Inform policy customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2159.3.3 Calling the Inform policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2179.3.4 Calling AON Inform policy from System Automation . . . . . . . . . 218

9.4 Brief comparison of NMC and SDF Consoles . . . . . . . . . . . . . . . . . . 2249.5 Example NMC screens of the ITSO project scenario . . . . . . . . . . . . 225

Appendix A. NetView 1.3 toleration for System Automation 1.3 . . . . 231

Appendix B. System Automation V1R3 members and jobs . . . . . . . . 233B.1 Other System Automation jobs and definitions . . . . . . . . . . . . . . . . . . . . 234

B.1.1 Automation NetView start-up procedure . . . . . . . . . . . . . . . . . . . . . 235B.1.2 System Automation RODM procedure . . . . . . . . . . . . . . . . . . . . . . 237B.1.3 Automation GMFHS start-up procedure . . . . . . . . . . . . . . . . . . . . . 238B.1.4 SA RODM data model load job. . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Appendix C. One RODM/GMFHS focal point configuration. . . . . . . . . 241

Appendix D. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Appendix E. Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249E.1 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249E.2 IBM Redbooks collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249E.3 Other resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249E.4 Referenced Web sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

How to get ITSO redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251IBM Redbook fax order form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

vi Automation Using Tivoli NetView OS/390 V1R3 and System Automation OS/390 V1R3

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

IBM Redbooks review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

vii

viii Automation Using Tivoli NetView OS/390 V1R3 and System Automation OS/390 V1R3

Preface

The objective of this redbook is to provide an easy to use and understandautomation guide for large organizations. The major focus of this redbook ison how to efficiently set up and customize Tivoli NetView for OS/390 andSystems Automation for OS/390 in a multi-systems enterprise environment.

In addition to this, this redbook provides best practices and tips formaintenance issues of the Tivoli NetView and System Automationenvironment. This will include the AUTOMAN feature for maintenance ofmultiple automation tables, basic tuning considerations to improve generalNetView and automation table performance, as well as an optimized structureof the System Automation policy database.

To help system administrators and operators establish and leverage theirautomation environment, this redbook provides further information on basicautomation features, such as the System Automation framework, and someautomation scenarios using the new NetView AON inform policy feature.Examples include an automation scenario of the ITSO project environment,as well as integration aspects of System Automation using the new NetViewAON inform policy features, such as notifications via pager support orescalations by sending e-mails using the SMTP gateway support.

The steps outlined in this redbook are based on, and supported by, examplesderived from the actual installation, set up, and customization of TivoliNetView for OS/390 and System Automation for OS/390 at the ITSO.

The team that wrote this redbook

This redbook was produced by a team of specialists from around the worldworking at the International Technical Support Organization, Austin Center.

Holger Stamme is a Certified IT Architect at the ITSO, Austin Center, whohas more than 10 years of working experience in consulting, designing, andimplementing Systems Management solutions within IBM. Before joining theITSO in 1999, he was leading the architectural and design phases of largecustomer projects in the finance and insurance industry in Germany.

Ling Xiao Gao is a Advisory IT Specialist in China. He has seven years ofexperience in MVS and OS/390 fields. His areas of expertise include NetViewfor OS/390 and System Automation.

© Copyright IBM Corp. 2000 ix

Marcio Guimaraes is an Advisory IT Specialist in Brazil. He has eight yearsof experience in the IT field, of which the last five years have been indeveloping, designing, and supporting the System Management area. Hisareas of expertise include Tivoli NetView for OS/390 and System Automationfor OS/390.

Clive Kennedy is a Network Automation Specialist with AT&T GlobalNetworks in the UK. He has over 20 years experience in Systems andNetwork Management in large MVS installations and over 12 yearsexperience using NetView OS/390 for Systems and Network Automation.

Jason Wyer is an IT Consultant working for PricewaterhouseCoopers in theUSA. He has three years of experience in the Systems Administration field.He holds a BS from the University of Connecticut along with being an A+Certified Technician and Microsoft Certified Professional. His areas ofexpertise include Microsoft Windows environments.

Thanks to the following people for their invaluable contributions to this project:

Adam BarryTivoli Systems Raleigh, Network Management Applications Development

Denny BearyIBM Gaithersburg, S/390 Systems Management Technology Support

Budi DarmawanInternational Technical Support Organization, Austin Center

Gary ForghettiTivoli Systems Raleigh, Tivoli Product Introduction

Roland HaiblIBM Boeblingen, System Automation for OS/390 Information Development

Robert HaimowitzInternational Technical Support Organization, Raleigh Center

Stephan HartigIBM Boeblingen, System Automation for OS/390 Information Development

Joseph MaceraIBM Los Angeles, Tivoli Migration Team

Wade MillerTivoli Systems Raleigh, NetView Performance Group

x Automation Using Tivoli NetView OS/390 V1R3 and System Automation OS/390 V1R3

Paul QuigleyTivoli Systems Raleigh, Network Management Applications Development

Phil RiedelTivoli Systems Raleigh, Network Management Applications Development

Joachim SchmalzriedIBM Boeblingen, System Automation for OS/390 Information Development

Aimee TattersallTivoli Systems Raleigh, NetView for OS/390 Technical Evangelist

Comments welcome

Your comments are important to us!

We want our redbooks to be as helpful as possible. Please send us yourcomments about this or other redbooks in one of the following ways:

• Fax the evaluation form found in “IBM Redbooks review” on page 265 tothe fax number shown on the form.

• Use the online evaluation form found at http://www.redbooks.ibm.com/

• Send your comments in an Internet note to [email protected]

xi

http://www.redbooks.ibm.com/contacts.html


xii Automation Using Tivoli NetView OS/390 V1R3 and System Automation OS/390 V1R3

Chapter 1. Introduction to Tivoli NetView for OS/390 V1R3

This chapter provides a brief overview of the functions in Tivoli NetView forOS/390 V1R3, which is extracted from the Request for Announcement (RFA).In addition, some information about the configuration used during theresidency will be provided.

A complete list of all the hardware and software requirements for each TivoliNetView for OS/390 V1R3 function is provided in the announcement letterand also in the Tivoli NetView for OS/390 V1R3 Planning Guide, GC31-8226.

1.1 At a glance

Tivoli NetView for OS/390 V1R3 targets enterprise control of the e-businesscomplexity. Building on the already rich functionality of Tivoli NetView forOS/390, V1R3 provides enhancements in the following areas:

• It is possible to issue any TCP/IP, SNMP, or UNIX command from TivoliNetView for OS/390 either through a user-friendly panel interface or inClists that are written to extend the functions NetView provides.

• SNMP services include a MIB compiler/loader and a MIB browserlaunched from the NMC. There is also a robust 3270 interface for issuingSNMP requests, such as GET/SET/etc. MIB polling and thresholds alsoaid in monitoring and automation.

• Graphical Network Management now includes IP agents available for:

- Tivoli NetView on Sun Solaris or Windows NT

- HP OpenView on Sun Solaris or HP-UX

- Tivoli NetView on AIX

• Tivoli NetView for OS/390 now provides the ability to convert SNMP trapsto SNA alerts and SNA alerts to SNMP traps.

• Web interfaces for third-party Web applications can be launched.

• The timer and automation capabilities are further enhanced.

1.2 Overview

Tivoli NetView for OS/390 addresses the challenges of network and systemsmanagement by focusing on operator productivity through the use ofgraphical displays and embedded automation capability. Tivoli NetView for

© Copyright IBM Corp. 2000 1

OS/390 continues its leadership in SNA management and strongly addressesthe management of mixed network architecture environments.

Tivoli NetView for OS/390 V1R3 focuses on management of IP networks andSNMP-based devices, management of IP clients accessing mainframeapplications, and integration with third-party network and elementmanagement vendors.

TCP/IP management can be accomplished through the use of native OS/390TCP/IP management or in cooperation with management applications ondistributed platforms. This includes IP agents available for Tivoli NetView onAIX, Sun Solaris, or Windows NT, and HP OpenView on Sun Solaris orHP-UX.

An SNMP stack and MIB services (MIB compiler/loader, MIB browser)improve the management of TCP/IP resources and sessions. In addition,NetView can receive and process any SNMP V1 trap.

Full function SNMP command support from the NMC, 3270 panels, orcommand procedures, support for logical groupings of MIB variables, remotePing support, MIB polling, and thresholds aid in resource monitoring andautomation. Not all functions are available from both the NMC and 3270interfaces.

Any socket can now be monitored for availability. If the socket is down, thenautomation can attempt to restart its associated application, job, or task.

TN3270 session management now includes support for the remote TN3270server feature on both Cisco and IBM routers plus support for connectionswith any TCP socket.

Tivoli NetView for OS/390 provides the ability to launch a Web interface forany vendor application from the NetView Management Console (NMC).

NMC improvements include view cycling, view and resource security, andother ease-of-use enhancements. In addition, there are enhancements thatintegrate the NMC and NetView 3270 Management Console into a singleconsole.

Tivoli NetView's robust timer and automation table capabilities are expandedto assist in automation table management, and a new CHRON command withcalendering support.

Tivoli NetView for OS/390 now adapts dynamically to daylight savings timeand other system time changes without requiring a recycle.

2 Automation Using Tivoli NetView OS/390 V1R3 and System Automation OS/390 V1R3

1.3 Description

Building on the already rich functionality of Tivoli NetView for OS/390, theV1R3 provides the additional enhancements, which are discussed in thefollowing sections.

1.3.1 IP managementTivoli NetView for OS/390 V1R3 provides the operator with the ability tomonitor and control the enterprise-wide, multi-protocol network from a singleconsole. This includes the ability to view and manage the protocol-basednetwork topologies, network devices, and the interrelationships betweenthem.

• Graphical Network Management now includes IP agents available onTivoli NetView for Sun Solaris, Tivoli NetView for Windows NT, HPOpenView for Sun Solaris, and HP OpenView for HP-UX. The agentsenable collection of IP topology and status discovered by the distributedSNMP-based network managers and forwarded to Tivoli NetView forOS/390 on a TCP/IP session. This enables management of IP networksfrom one central location. There is also a TCP/IP connection between theagent on Tivoli NetView for AIX and Tivoli NetView for OS/390 as well asan LU6.2 connection.

• For topology updates and status changes, Tivoli NetView for OS/390 nowhas the ability to receive SNMP traps about IP resources and convert themto SNA alerts and status updates.

• Conversion of SNA alerts into SNMP traps allows OS/390 captured alertsto be forwarded to distributed SNMP management applications.

• A sample IP Layer 3 discovery engine that runs natively on OS/390minimizes the need to define resources to be managed.

• Topology correlation has been enhanced to generate enterprise specificviews more easily. Critical resources can now be automatically linked to ahierarchy of topology resources, such as "Room 12, Warehouse 2, HongKong, Manufacturing." If business views are not found, they will becreated. Topology correlation is now easier to invoke through integrationwith BuildViews and Visual BuildViews.

• Continuing to build on end-to-end network management, NetView forOS/390 provides the ability to launch a Web interface for any vendorapplication from the NetView Management Console. Use of this functionincludes CiscoWorks Blue and IBM Nways Manager Element Manager.This allows operators to manage the enterprise from one control console

Chapter 1. Introduction to Tivoli NetView for OS/390 V1R3 3

and seamlessly work with other management tools without changingmanagement consoles.

• From the NMC, you can retrieve inventory data for IBM and Cisco networkinterconnect devices from the Tivoli Inventory database. The TivoliInventory database is populated by Tivoli Manager for CiscoWorks 2000and Tivoli Manager for IBM NWAYS.

• An NMC-based MIB Browser functions as a client of MIB services andSNMP services on OS/390. The MIB services provide a MIBcompiler/loader function, which allows Tivoli NetView for OS/390 tosupport any vendor specific MIB described using the standard ASN.1format. SNMP services provide an SNMP stack facility. Full SNMP commandsupport is provided from NMC command pull-downs.

• The Tivoli Management Region (TMR) agent is enhanced to collecttopology and monitors for critical Tivoli Management Agents (TMAs).

• The ATM topology agent supports new alerts for status updates.

• Operators can now issue SNMP GET, GETNEXT, SET, and WALK commands fromTivoli NetView for OS/390 in addition to PING, TRACERTE, IPSTAT, and NETSTAT.In general, it is possible to issue any IP, SNMP, or UNIX command. Thesecommands can also be used in REXX clists and other automationroutines.

• It is possible to define which MIB variables to check at specified intervalsand take action if a threshold is exceeded. User exits are available for MIBpolling and MIB thresholding to provide the capability to do more extensiveanalysis or automation.

• Extending previous support for managing TN3270 and FTP sessions, anysocket connection can now be monitored for availability. Operators candisplay session status for any socket connection, including TN3270sockets, FTP, SMTP, telnet, and Web browser. If the socket is down,automation can attempt to restart its associated application, job, or task.

• If you are running OS/390 V2R6, or later, and have it properly configuredto support multiple TN3270 sockets, then Session Management can alsobe configured to support multiple sockets for TN3270 connections.

• Sessions being displayed by Session Management can be filtered. Forexample, operators can set filters to see only TN3270 sessions fromsubnet 146.48.*.* to applications starting with CICS.

• IP session management has been extended to include sessions betweenIP clients and SNA mainframe applications connected through TN3270servers. Servers supported include IBM 2210 and 2216 and Cisco'sChannel Interface Processors (CIP) and Channel Port Adapters (CPAs).


• Tivoli NetView for OS/390 has predefined MIB group definitions to collectSNMP data that is most meaningful to the operators. Additionally, it ispossible to define your own groups to present MIB data best suited for thespecific SNMP environment.

1.3.2 Graphical consoleThe NetView Management Console (NMC) now has equivalent functionalityto NGMF plus several additional customer-requested capabilities. In addition,there are enhancements that integrate the NMC and NetView 3270Management Console (formerly known as the 3270 Java (TM) Client) into asingle console. These enhancements include:

• View cycling

• Resource session data from session monitor (including configuration data)

• Launching Web interface for vendor applications, such as CiscoWorksBlue and IBM Nways Manager Element Manager

• Sending messages to a specific console or broadcast to all consoles

• View and resource security

• Non-SNA command line (now called Service Point Command Line)

• Visual NETCONV status (to more clearly see when NETCONV is down)

• Single sign on for NMC and NetView 3270 Management Console

• The ability to create a note associated with a flag (user status)

• Operator ID and timestamp stored whenever a flag is changed

• Console log freeze and thaw to prevent scrolling while you are trying toread a message

• Additional hot key support, such as ctrl-H for help, ctrl-L for locateresource, and ctrl-F for find

• New menu item to quickly suspend/unsuspend resources fromaggregation

• Closing a view and/all descendent views

• Selection of multiple resources (including selecting objects in a specifiedregion of the view)

• Customized dynamic views displayed on a business tree structure

• Finding objects in a view


• The ability to write a client application to send a command to TivoliNetView for OS/390 and receive a correlated response back forsubsequent processing

• Built-in Java runtime environment eliminating the need for a separateinstallation and configuration of the Java Development Kit

• Productivity kit

- The ability to write console-based Java applications

- The ability to extend console operation using plug-ins

- Advanced customization guide

- Self-standing demonstration mode of the NMC (server not required)

1.3.3 Automation featuresThe automation enhancements include additional functions and usability inthe automation table, timers, and TCP/IP. These enhancements include:

• Support of greater-than and less-than in the automation table

• Triggering of information in multiple lines of MLWTOs in the automationtable

• The ability to use PIPE EDIT functionality in automation table conditionsand actions

• A tool for managing multiple automation tables (AUTOMAN)

• Support allowing operators to send e-mail directly from Tivoli NetView forOS/390 via a panel interface using SMTP

• Greatly enhanced timer support through a new CHRON command whichprovides capabilities such as:

- The ability to define enterprise-unique dates of importance, such asholidays, vacations, and payroll days, using a customizable calendarthat can be dynamically reloaded.

- Very flexible specification of dates and times for timer executionincluding days of the week or days of the month; for example, you canspecify that a certain command is to be executed at 10:00 everyMonday that is not a holiday.

- The ability to specify repeated timers that automatically compensate fordaylight savings time or other system time changes.

• An enhanced panel interface (TIMER) for viewing and creatingtimer-driven commands, including support for the CHRON command


1.3.4 Other customer satisfaction enhancementsFurther customer satisfaction enhancements include:

• Dynamic timer adjustment to allow Tivoli NetView for OS/390 to remain upand running through daylight savings time changes or other system timechanges.

• The ability to dynamically define Tivoli NetView for OS/390 commands,removing one of the final reasons to recycle Tivoli NetView for OS/390.This enhancement provides truly 24x7 operation of Tivoli NetView forOS/390 since planned outages are no longer necessary except forapplication of maintenance between releases.

• The use of system symbolics for all components of Tivoli NetView forOS/390 allows easier configuration of multiple instances of Tivoli NetViewfor OS/390 throughout your enterprise and reduces maintenance efforts ina multi-system OS/390 environment.

• Visual BLDVIEWS support to provide an easy-to-use graphical interface tocreate views and modify resource information.

• A new NetView SOCKET command to facilitate communication with otherTCP/IP applications and devices from automation procedures or theNetView command line.

• The ability for an operator to log on with an active autotask of the samename or take over a task logged on elsewhere. In addition, the RMTCMD

command can take over tasks already logged on or make use of tasksbeing used for other purposes.

• Conversion of initial clist to use REXX and pipes.

• Support for personal operator data sets to allow for operatorcustomizations, including the ability to save and restore personalized PFkey settings.

• The ability to use up to eight characters for the command prefix used toissue Tivoli NetView for OS/390 commands from an MVS console.

• Support for Tivoli Software Distribution file packs to distribute and installworkstation components where Tivoli Software Distribution is deployed,thus, making software install easier on distributed platforms connecting toTivoli NetView for OS/390.

• The ability to view session monitor configuration data from the NMC orfrom a Web browser.

• Customizable Title Line on the Command Facility screen.

• Many improvements to the NetView Pipe command.


• Upgrading of MEMSTORE and IDLEOFF from samples to supported TivoliNetView for OS/390 commands.

• BROWSE NETLOG support for the HDRMTYPE field.

• Enhanced ability to locate network node (NN) servers in APPNenvironments and run commands remotely at these network nodes.

• Security enhancements include:

- Enhanced security for DB2 access.

- Disk read security for %INCLUDE members.

- Security for VTAM commands prefixed with 'MVS'.

- Checking an operator's READSEC or WRITESEC authorization beforereading from or writing to a data set member when EXECIO is done ina NetView command list.

- More granularity in submitting jobs via NetView's SUBMIT command.

• Resource monitor enhancements to help determine which task is queuingtoo many messages and to provide more flexibility in logging usagestatistics in SMF.

• Several customer requested enhancements to the NetView 3270Management Console (previously known as the 3270 Java client), such asremappable colors and keyboard, an editable session list, and an option tohide the PF keys palette.

• Access to Tivoli NetView for OS/390 using a standard Web browserincludes these enhancements:

- An operator sending a LOGOFF command to NetView from a Webbrowser can be prompted for their operator ID and password the nexttime they send a command to NetView from the browser. Previously,the operator had to close the browser.

- Set an idle time limit for Web-connected operator tasks, after which theoperator will be prompted again for an ID and password.

- The ability to specify which operators are authorized to access NetViewfrom a Web browser.

- The ability to differentiate commands entered through Web accessfrom commands entered through traditional NetView tasks.

- Support for frames and support for JavaScript (.js) as a valid file type.


1.3.5 Product positioning in the marketTivoli NetView for OS/390 Version 1 Release 3 is an integral part of the Tivolienvironment that provides a comprehensive set of tools for maintainingcomplex, multi-vendor, multi-platform networks and systems from a singlepoint of control.

With its open application programming interfaces (APIs), Tivoli NetView forOS/390 can be an integration point for other S/390 vendors to the Tivolidistributed environment.

Tivoli NetView for OS/390 is a program for managing networks and systemsthrough a strong set of automation features and graphical console displays. Itreduces manual resource definition and complex automation set-up throughproduction-ready automation and extends centralized management intomultiple, non-SNA network environments. Tivoli NetView for OS/390 can beused in a large enterprise organization as a centralized manager, a mid-levelmanager, or just as a S/390 management endpoint.

Tivoli NetView for OS/390 Version 1 Release 3 is the last release that willsupport the OS/2-based NetView Graphical Monitor Facility (NGMF).Subsequent to Release 3, only the NetView Management Console (NMC)will be supported for graphical topology and status display.

This information is being provided for customer awareness and is based onIBM best technical judgement at this time. IBM makes no guarantee thatthis information will not change based on future business decisions.

Note



Chapter 2. Benefits of using System Automation for OS/390

This chapter describes why it is essential to use System Automation forOS/390. An effective and proactive management of OS/390 subsystemcomponents or applications includes functions, such as monitoring, recoverycapabilities, and ease of use.

2.1 Why automate?

The need to simplify operations increases as you add hardware and softwareproducts to your data center, data centers to your network, and personnel toyour data-processing staff. By simplifying your operations, SystemAutomation can help you meet required service levels, contain costs, makeefficient use of your operation staff, and remove repetitive tasks from beingreliant on human frailties.

System Automation offers system-wide benefits by simplifying your operatingenvironment. You can reduce the amount of manual intervention required tomanage operating systems, subsystems, application programs, and manyother products.

This is particularly important in a multiple system, especially for a ParallelSysplex environment. However, the job of managing these multiple images orsystems is not a simple task.

There are opportunities during the operation in multiple system or ParallelSysplex environments where, despite the best efforts of software developersand testers, human intervention is required. The phrase “to err is human” hasnever been more true than in computer operations.

Given that the enterprise wide environment is complex, and that humanerrors can occur, the use of an automation tool that responds in a consistentway to a particular event can help in delivering on the promise of continuousoperations.

One of the questions surrounding automation is: “Just what do I automate?”In this book, we look at some of the issues surrounding set up, customization,and automation examples in a multiple system environment.

A similar, but more specific to the Parallel Sysplex environment focusing, isthe ITSO redbook, Parallel Sysplex Automation: Using System Automation forOS/390, SG24-5442, published in September of 1999.


2.2 Proactive management of OS/390 subsystem tasks

The purpose of the proactive management features of System Automation isaddressing the automation of repetitive tasks that operators currentlyperform. Today, the operators usually respond in a particular way to amessage, or perform a task in accordance to the standard operatingprocedures. Coding automation routines to replace these tasks is relativelystraight forward since the triggers for the actions, and the actions themselves,are well known.

Another approach is to collect a number of days of SYSLOG data and to usea program, such as the MVS SYSLOG Message Analysis Program, which canbe downloaded from URL http://www.s390.ibm.com/sa, to see whatmessage triggers are being issued and base your automation (and messagesuppression) on the output of the tool.

In this book, you will find information, hints, and tips to start up and control amultiple system OS/390 environment and how to build a hierarchy of yourconnected OS/390 systems and subsystem components.

2.3 Monitoring and recovery capabilities of OS/390 subsystems

Next to the proactive management are the monitoring and recoverycapabilities of System Automation for OS/390. It addresses the automation ofevents based on what is currently happening in your OS/390 systems.

Typically, automation routines address both of these areas. But of the two, themonitoring and recovery capabilities of unsolicited events are by far morecomplex to resolve. This is due to the fact that it is not precisely known whatto automate without having experienced relevant problems.

When developing automation routines to handle error conditions, the triggersare not always as obvious. One way around this is to experience the problemfirst, then, based on what happened, code routines to automate the handlingof that condition. This works as long as you are happy to experience everyproblem or error condition at least once. One other approach is to dive into allthe message manuals and try and look for likely messages to automate.

This book will provide some information, hints, and tips on unsolicited eventsin a multiple system OS/390 environment and how to monitor and recoverfrom these critical situations.

In addition, it will be shown how to notify or escalate in situations wheresuccessful recovery is not possible.


2.4 Automation features of System Automation for OS/390 V1R3

This section provides a brief overview of the new System Automation V1R3features.

The following major enhancements are new to SA OS/390 V1R3:

• New interface - Single system image

• Managing your applications with triggers, events, and service periods

• Simultaneously updating policy databases for applications

2.4.1 New Interface - Single system image supportSystem Automation for OS/390 V1R3 comprises full sysplex and singlesystem image support. Now, systems in the sysplex need not be automatedseparately, but one system in the sysplex acts as a single point of controlwhere the operator can specify the resources and their automation of theentire sysplex environment. Using the System Display Feature (SDF) on theSystem Automation focal point and System Automation instances on each ofthe systems in the sysplex environment, it is possible to display the statusand workloads of resources as well as control and manage them. The supportof single system image helps to optimize operating tasks and improvesproductivity.

2.4.2 Better managing your applicationsOptimizing the availability of applications when they are needed is animportant issue in data processing. System Automation enables the user todefine the availability of resources to meet a company's specific needs withthe following set of functions:

• Service periods are user specified time intervals, during which anapplication should be active.

• Events are part of a trigger condition. If the event of a trigger conditionhas occurred, the startup or shutdown of an application is performed. Ifthere is a service period also connected to the trigger, then it will checkthe service window to determine whether a shutdown or start-up should beperformed.

• Triggers, in combination with events, and optionally with service periods,allows control over the startup and shutdown of resources. For example,the shutdown of application A automatically triggers the start-up ofapplication B.

Chapter 2. Benefits of using System Automation for OS/390 13

2.4.3 Simultaneously updating policy databases for applicationsThe customization dialogs are enhanced to allow for multi-user access to thepolicy database for applications. To improve the ease-of-use for updates ofthe policy database for applications, changes can now be done in parallel byvarious automation administrators.

2.4.4 Notifying the Tivoli Enterprise ConsoleSystem Automation for OS/390 V1R3 now includes integration with the TivoliManagement Environment. Events reported by System Automation, as wellas events reported in a distributed environment, are received at, and handledfrom, a single point of control. Therefore, System Automation notifies theTivoli Enterprise Console (TEC) in situations when System Automation issuesmessages and alerts indicating critical situations. These messages and alertsare forwarded to the TEC event server by the Event Automation Server(EAS).

2.4.5 Other enhancementsThe following enhancements were further introduced by System Automationfor OS/390 V1R3:

• Workload Manager (WLM) resource name support

By introducing this ability, the interface to the operating system OS/390has been improved. SA OS/390 now passes status information about theresources to the operating system's Workload Manager.

• AOCQRES command

With this command you can examine where, in a sysplex environment, aresource is located and return information about this resource. Optionally,it also supplies up-to-date status information about resources.

• Partial ACF load

The new ACFPLOAD command allows small changes in the automationconfiguration without having to reload the entire ACF file and withoutinterrupting automation.

• Line mode output

A number of commands have been enhanced with a new parameter(OUTMODE=LINE) to allow for specifying output mode. All NetView basedcommands are now able to be piped for further processing. The operatordialog NetView panels have been enhanced to support displays of up to43 lines per panel.

• SHUTSYS command


The default of the SHUTSYS command is now set to VERIFY=NO forunattended processing.

• Overall performance

The overall performance has been improved by restructuring tasks, whichaccelerates the start-up and the shutdown of subsystems.

In the System Automation customization dialog it is now possible to definea set of auto operators to handle subsystem automation.

Chapter 2. Benefits of using System Automation for OS/390 15


Chapter 3. The ITSO automation project environment

The following sections will provide a brief description of some basic conceptsthat are commonly used when working with focal points and graphicalenterprise features. Further detailed information about these topics areprovided within the Tivoli Netview for OS/390 and System Automation forOS/390 technical documentations.

System Automation for OS/390 allows control of the customization,monitoring, and management functions of multiple systems or images in theenterprise (each running System Automation instances), using a single,centrally located OS/390 system. This controlling OS/390 system is called thefocal point system. The managed systems in the environment are calledtarget systems. All connected systems communicate between each otherthrough Tivoli NetView for OS/390 using specific Netview data transportmechanisms.

Figure 1 on page 18 shows a high-level diagram of the environment usedduring the project at the ITSO. The environment consisted of three systems,each of them running OS/390 V2R7, Tivoli NetView for OS/390 V1R3, andSystem Automation for OS/390 V1R3.

The system SC66 is the designated focal point system, while the other twosystems, SC42 and SC69, are target systems.

Within this ITSO project, it was decided to set up the environmentconsisting of the three systems, SC66, SC42, and SC69, without anysystem resource (storage/workload) limitations. Assuming the networkingand automation objects within the enterprise should be managed by theirown RODM, it was decided to run separate RODM/GMFHS applications forthe networking and the automation environment on the focal point system.

For a limited system resource (storage/workload) approach on the focalpoint system, when managing a reasonable number of networking andSystem Automation objects, a configuration with only one RODM/GMFHSon the focal point system for both environments can be chosen. Refer toAppendix C, “One RODM/GMFHS focal point configuration” on page 241,for a customization checklist.

Note


Figure 1. ITSO project environment


3.1 Types of communication

Since its earliest releases, Tivoli Netview for OS/390 provides three differentdata transport mechanisms that support the centralized operations from afocal point system. The transport mechanisms are:

• Communication using a LU 6.2 session

• Communication using a LUC session

• Communication using an OST-NNT session

• Communication using TCP/IP

These communications are used to transfer data between Tivoli NetViewprograms that reside in different domains or systems. The LU 6.2communication is also used to transfer data between Tivoli NetView andnon-NetView products, such as the AS/400 and its applications. Whencentralizing operations between different Tivoli NetView domains, one ormore of these communication types are used.

In addition, new to Tivoli NetView for OS/390 V1R3 is the support to convertSNMP traps to SNA NVMT alerts and vice versa, which uses the TCP/IPcommunication.

3.1.1 Communication using a LU 6.2 sessionTivoli NetView supports two LU 6.2 session types, which use differentversions of the SNA LU 6.2 protocol:

1. The Management Services (MS) transport is for low-volume transmissionsthat require high reliability, such as sending alerts.

2. The high-performance option of the MS transport is for large-volumetransmissions that require optimized network performance.

Tivoli NetView’s LU 6.2 session communications are based on theMULTIPLE_DOMAIN_SUPPORT function set described in the SNAManagement Services Reference, SC30-3346. This LU 6.2 sessiontransports are used by Management Services (MS) applications to send andreceive data.

The NetView DSI6DST task must be active to use the LU 6.2 sessiontransports.

Note

Chapter 3. The ITSO automation project environment 19

3.1.2 Communication using a LUC sessionUnlike the communication using a LU 6.2 session, the LUC session transportsupports communication only between NetView programs. The LUC tasks inthe Tivoli NetView domain must be active to use this transport mechanism. Inaddition to using the NV-UNIQ/LUC alert forwarding, the DSICRTR task mustbe active.

3.1.3 Communication using an OST-NNT sessionLike the communication using the LUC session, the OST-NNT sessiontransport supports communication only between NetView programs. Toestablish an OST-NNT session between Tivoli NetView domains, the NetViewcommand START DOMAIN is used. In this way, a central NetView domain cancommunicate with a target NetView domain.

3.2 Resource Object Data Manager (RODM)

The Tivoli NetView for OS/390 uses RODM to store topology and statusinformation for resources that are to be managed by automation programs(for example, System Automation for OS/390) or to be displayed by theNetView Management Console (NMC). The interface between RODM and thedistributed NetView Management Console server component is the NetViewGraphic Monitor Facility Host Subsystem (GMFHS), which is furtherexplained in the next section.

RODM provides a high-speed data cache, an application program interface(API), and services that enable the management of system and networkresources. It stores topology data, status information, execution information,and other details about resources or classes of resources in an objectoriented data structure. Objects in RODM represent resources in the systemor in the network environment. The data cache is located entirely in thememory of the host processor and is designed for applications that need toaccess, interpret, and alter large amounts of rapidly changing data in a shortperiod of time. RODM provides an open interface to enable managementapplications to use the data for automation as well as allow multipleapplications to access the data simultaneously.

It is a single source for all topology and status information that TivoliNetView’s automation facilities support. The contained information in RODMis updated dynamically, which is most important to all automation facilities ofTivoli NetView for OS/390.


Based on any change in your system or network configuration as reportedthrough a NetView alert, for example, if a subsystem goes off-line, RODMdynamically updates the object information and triggers as requiredautomation procedures.

To ensure fast response time, RODM operates in memory. It supportssophisticated systems and network process control applications that need toaccess, interpret, and respond to rapidly changing configuration and statusdata.

3.2.1 RODM object oriented structureIn order to operate RODM, it is necessary to load one or more physical datamodel structures of the managed environments into RODMs memory storage.These data model structures consists of the following elements:

• Object: Any resource or link that is required to be managed would berepresented in the data model as an object. Link objects represent theconnection between two resource objects.

• Class: The class defines the characteristics that are common to allobjects that belong to that class. Its purpose is to define a particular typeof object.

• Field: The attributes or fields of an object contain the specific informationabout a resource that you want to manage.

• Methods: The actions that can be performed against that object would bedefined as methods to that class of objects.

3.3 Graphic Monitor Facility Host Subsystem (GMFHS)

GMFHS manages the configuration, topology, and status updates fromRODM to the distributed NetView Management Console (NMC) application. Itresides in its own address space at the host and communicates to NetViewthrough the Program-to-Program Interface (PPI). The PPI serves as atransport facility for commands, views, and status information passingbetween GMFHS and the NetView program at the focal point host. Theinformation is routed over TCP/IP or LU 6.2 communication sessions betweenthe NetView program at the host and the NetView Management Console(NMC) Topology Server at the distributed side, which is, in return,communicating to connected NMC Topology clients via TCP/IP protocol.


3.4 Status Display Facility (SDF)

The Status Display Facility (SDF) is a System Automation system resourcemonitoring feature that does, unlike the NetView Management Console, notrequire RODM or GMFHS to display the status of various resources of theautomation focal point and target OS/390 systems. SDF is a non-graphical,3270 session based, control panel that uses different colored and highlightedtext strings to inform the subsystem resource states. The resource typesdisplayed by SDF include:

• Applications and subsystems

• WTORs

• Gateways

SDF is also able to show spool problems and assist requests from OS/390subcomponents. SDF consists of a hierarchy of dynamically updated panelsshowing color-coded status conditions. SDF is set up during thecustomization of System Automation for OS/390. The screen shown in Figure2 on page 23 is an actual sample of the ITSO focal point system SC66.

GMFHS is required only in the system defined as the Focal Point System orBackup Focal Point System. It is not required to be active in target systems

Note

A Gateway is a group of one NetView-NetView task session and its twoautomated operator tasks, which allows communication of messages,commands, and responses between the two NetView systems.

Note


Figure 2. SDF sample screen of focal point system SC66



Chapter 4. Customization of Tivoli NetView OS/390

This chapter details the customization process of Tivoli NetView for OS/390V1R3. The main emphasis will be a generic and fast setup approach usingsystem symbolics in the NetView common libraries. No changes should everbe made to the NetView install libraries, ensuring modifications are notdeleted when applying NetView for OS/390 PTFs. The customizations willenable system programmers to roll out several NetViews on multiple systemswith minimal additional customization efforts.

At the highest level, the installation of NetView in a multiple systemenvironment breaks down into five large steps, which are shown in Table 1.

Table 1. High-level NetView installation process in a multi-system environment

# Step Description

1 Plan the environment Obtain details of the environment and whatfeatures are to be installed:- Number of enterprise Focal Point NetViews- Number of procedural NetViews- What NetView features will be running- Where these NetView will features be running

Document the findings.

2 Define the environment Decide on naming conventions for the plannedenvironment. Clarify existing system symbolicsbeing used and consider any new symbolicsthat may be required or useful.

3 Full featured test install ofTivoli NetView for OS/390

Install a full featured copy of NetView on a testsystem. This will validate findings previouslyobtained and will help with the creation of thecommon/local library structure.

4 Creation of commonlibraries

Create and populate the common libraries(which is in effect an install in itself) and createa task list for the local (domain specific)installations.See Section 4.3.6.1, “Local install process forthe networking NetView domains” on page 38,for an example of a local install task list.

5 Creation of local (domainspecific) libraries

Follow the task list for each local (domainspecific) NetView installation and create andpopulate the domain specific libraries.


4.1 Planning the Tivoli NetView for OS/390 environment

The details of the project environment are outlined in Chapter 3, “The ITSOautomation project environment” on page 17. It is planned to have one focalpoint system and two target systems.

In terms of NetView, this means on the Focal Point system, one Focal PointNetView for each of the automation and the network environments. For eachof the target systems, it also requires one NetView for each of the twoenvironments. The total number of NetViews for the planned environment ofthree systems is six.

The two Focal Point NetViews are planned to run as full featured enterpriseNetViews, whereas all other NetViews on the target systems are planned torun only as procedural NetViews.

In this ITSO environment, all of the six NetViews will be connected to theirindividual Resource Object Data Manager (RODM) to store and manage theindividual network and system resources.

Refer to Tivoli NetView for OS/390 Installation and Administration Guide,SC31-8236, for full details of the NetView installation process.

Note

Refer to Tivoli NetView for OS/390 Installation and Administration Guide,SC31-8236, for full details of the NetView installation process.

Within this ITSO project it was decided to setup the environment withoutany system resource (storage/workload) limitation. Assuming thenetworking and automation objects within the enterprise should bemanaged by their own RODM, it was chosen to run separateRODM/GMFHS applications for the networking and the automationenvironment on the focal point system SC66.

For a limited system resource (storage/workload) approach on the focalpoint system, when managing not too many networking and SystemAutomation objects, a configuration with only one RODM/GMFHS on thefocal point system for both environment could be chosen. For acustomization checklist, refer to Appendix C, “One RODM/GMFHS focalpoint configuration” on page 241.

Note


For the target systems, it is noted that it is not always required to implementRODM instances (see Note box).

Only the Focal Point NetViews will have the graphical interface to the NetViewManagement Console topology servers, which will be provided by twoinstances of the Graphical Monitor Facility Host Subsystem (GMFHS).

Therefore, in addition to six NetViews to be installed and customized, therewill be also six RODM and two GMFHS installations in the ITSO environment.

4.2 Defining the Tivoli NetView for OS/390 environment

To reduce the effort and time required to roll out an implementation of TivoliNetView for OS/390 across multiple systems, a common library structure isstrongly recommended. Within the common libraries are those NetViewmembers that require no local customization for any particular system ordomain.

The use of common libraries exploits the concept of the OS/390 system anduser defined symbolics, as explained further in Section 4.2.3, “Usage ofOS/390 system symbolics” on page 32.

4.2.1 Recommended library structure in multi-system environmentFigure 3 on page 28 will explain the recommended concept and librarystructure for Tivoli NetView for OS/390 in a multi system environment.

A RODM instance on the networking target environment is only required ifnetwork resources are to be managed on that particular target system.

A RODM instance on the automation target environment is only required ifusing the System Automation enterprise monitoring functions.

Note

Chapter 4. Customization of Tivoli NetView OS/390 27

Figure 3. Recommended NetView library structure in a multi-systems environment

Given the recommendation for the NetView library structure, the followingtables will specify the explicit naming conventions for the NetView installlibraries, common network and automation libraries, and all domain specificlibraries.

Table 2. Tier 1: Tivoli NetView install libraries

Install library dataset names Content

NETVIEW.V1R3M0.DSIPARM Supplied DSIPARM members


It is strongly recommended to never modify the level of product installlibraries. If modifications are necessary to effect all instances of NetView,then copy the required shipped members to next library level (NetViewcommon libraries) and modify them on this library level.

If the modifications are effective only for some NetView domains, the requiredmembers need to be copied to, and afterwards modified in, the NetViewdomain specific libraries.

Table 3. Tier 2: Tivoli NetView common libraries for the Network environment

Modifications to this library level effect all instances of NetViews in theNetwork environment.

Table 4. Tier 2: Tivoli NetView common libraries for the Automation environment

NETVIEW.V1R3M0.CNMCLST Supplied CLIST members

NETVIEW.V1R3M0.CNMPNL1 Supplied PANEL members

... ...

Common library dataset names Content

NETVUSER.NETWORK.DSIPARM Modified DSIPARM members

NETVUSER.NETWORK.DSIPARM.ENTERP Modified DSIPARM members,specifically for Network Focal Points

NETVUSER.NETWORK.DSIPARM.AON Modified DSIPARM members,specifically for AON

NETVUSER.NETWORK.CNMCLST Modified CLIST members

NETVUSER.NETWORK.CNMCLST.ENTERP Modified CLIST members, specificallyfor Network Focal Points

NETVUSER.NETWORK.CNMPNL1 Modified PANEL members


NETVUSER.SYSTEM.DSIPARM Modified DSIPARM members

NETVUSER.SYSTEM.DSIPARM.ENTERP Modified DSIPARM members,specifically for Automation Focal Points

NETVUSER.SYSTEM.DSIPARM.ACF Modified DSIPARM members,specifically for System Automation

Install library dataset names Content


Modifications to this library level effect all instances of NetViews in theAutomation environment.

If modifications are necessary to effect only some NetView domains, thencopy the required members from the NetView common libraries (or NetViewinstall libraries) to the next library level (NetView domain specific libraries)and modify them on this library level.

Table 5. Tier 3: Tivoli NetView domain specific libraries

As a common rule, it is recommended to specify a numeric system identifier,as well as an indicator of the specific environment, into the NetView domainname. In this project, the following naming convention for the NetView domainnames were chosen:

• Character 1, 2 - System string ‘SC’

• Character 3, 4 - Numeric system identifier, for example, 66 or 42

• Character 5 - Environment identifier, for example, ‘N’ or ‘A’

The library structure of datasets within any single implementation of TivoliNetView for OS/390 will then be:

a. NetView install libraries

b. NetView common (global) libraries

c. NetView domain specific (local) libraries

However, the concatenation order of these library dataset names in theNetView for OS/390 start-up procedure is reverse because existent members

NETVUSER.SYSTEM.CNMCLST Modified CLIST members

NETVUSER.SYSTEM.CNMCLST.ENTERP Modified CLIST members, specificallyfor Automation Focal Points

NETVUSER.SYSTEM.CNMPNL1 Modified PANEL members


NETVUSER.<domain name>.DSIPARM Modified DSIPARM members

NETVUSER.<domain name>.CNMCLST Modified CLIST members

NETVUSER.<domain name>.CNMPNL1 Modified PANEL members

where <domain name> Denotes the specific NetView domainname, for example, SC66N or SC66A



of the domain specific libraries should be loaded first instead of members ofcommon or install libraries. The concatenation order is thus:

a. NetView domain specific (local) libraries

b. NetView common (global) libraries

c. NetView install libraries

The following example shows the DSIPARM concatenation in a proceduralNetwork NetView for OS/390:

//DSIPARM DD DSN=&Q1..&DOMAIN..DSIPARM,DISP=SHR// DD DSN=&Q1..NETWORK.DSIPARM.AON,DISP=SHR// DD DSN=&Q1..NETWORK.DSIPARM,DISP=SHR// DD DSN=&SQ1..DSIPARM,DISP=SHR

And, in addition, the example of the DSIPARM concatenation of an enterpriseNetwork NetView for OS/390:

//DSIPARM DD DSN=&Q1..&DOMAIN..DSIPARM,DISP=SHR// DD DSN=&Q1..NETWORK.DSIPARM.AON,DISP=SHR// DD DSN=&Q1..NETWORK.DSIPARM.ENTERP,DISP=SHR// DD DSN=&Q1..NETWORK.DSIPARM,DISP=SHR// DD DSN=&SQ1..DSIPARM,DISP=SHR

4.2.2 OS/390 subsystem extensionsSince the ITSO project addresses two different environments, the networkingand the automation NetView environment, it was decided to not onlydifferentiate the library structures, but to extend, in addition, the OS/390subsystem definitions for NetView and RODM (GMFHS is not a subsystem).This can, for example, be achieved by editing the OS/390 system definitionmember IEFSSNxx (SYS1.PARMLIB) and adding the following statements:

SUBSYS SUBNAME(NETC)SUBSYS SUBNAME(NETV)SUBSYS SUBNAME(EKGN)SUBSYS SUBNAME(EKGA)

These subsystem extensions created in this ITSO project lead to the followingsubsystem and start-up procedure naming conventions for NetView andRODM (for GMFHS, just start-up procedure names):

• Networking environment:

- Subsystem names:

• RODM: EKGN

• NetView: NETC


- Start-up procedure names:

• RODM: EKGNss

• NetView: NETCssN

• GMFHS: GMFHSssN

where <ss> reflects the system identifier.

• Automation environment:

- Subsystem names:

• RODM: EKGA

• NetView: NETV

- Start-up procedure names:

• RODM: EKGAss

• NetView: NETVssA

• GMFHS: GMFHSssA

where <ss> reflects the system identifier.

4.2.3 Usage of OS/390 system symbolicsTivoli NetView for OS/390 has supported the use of MVS system and userdefined symbolics since V1R1, and each release has extended thisfunctionality.

The use of these symbolics can simplify the installation and maintenanceeffort required in a sysplex-wide implementation of Tivoli NetView for OS/390.

The symbolics used in this project are listed in Table 6.

Table 6. System symbolics used in this project

SYMBOLIC COMMENTS

&SYSNAME. Name of the system - On the systems in this project, this was “SC”followed by the clone ID (see below).

&SYSCLONE. On the project systems, a two-character numeric field used toidentify the clone ID.

MVS V5R2M0 or higher is required for system and user defined symbolicsupport.

Note


For example, on system SC66, the values coded in the IEASYMxx member ofPARMLIB would be :

SYSNAME(SC66)SYSCLONE(&SYSNAME(3:2))

To determine current symbols on one system, issue the following MVScommand from the TSO system log (SDSF) or from the NetView NCCFinterface (with prefixed command string ‘MVS‘):

D SYMBOLS

An example of the use of this technique is in the NetView start-up procedure,where the symbolic &SYSNAME. was used to generate the NetView domainname :

// DOMAIN=&SYSNAME.N, ** NETVIEW DOMAIN NAME

This enabled the usage of common JCL across systems running the sameNetView configuration (that is, procedural or enterprise).

4.3 Network management environment

For the networking environment, the results of step 1 and step 2, the processof planning and defining the networking NetView environment, were asfollows:

• System SC66 running an enterprise NetView with base AON installed.This acted as the AON focal point for all three systems. It also ran RODMand GMFHS linked to an NMC server.

• System SC42 running a procedural NetView with base AON installed.

• System SC69 running a procedural NetView with base AON installed.

The NetView domain name in each case was the system name suffixed with‘N’, for example, SC66N.

The &DOMAIN. symbolic generated in this way can be used in the variousNetView configuration members and will be automatically resolved to itscorrect value. It was found that &DOMAIN. was, in fact, the most commonlyused symbolic and was the most useful in setting up the common libraries.

Note


4.3.1 Creation of common networking NetView librariesAfter completing step 3, the full featured test install of Tivoli NetView forOS/390, the next sections will describe step 4, the process ofcreation/modification of common networking libraries.

According to the recommended naming convention for the NetView librarystructure, the following common libraries were created:

- DSIPARM:

• NETVUSER.NETWORK.DSIPARM

• NETVUSER.NETWORK.DSIPARM.AON

• NETVUSER.NETWORK.DSIPARM.ENTERP

- DSIPRF:

• NETVUSER.NETWORK.DSIPRF

- VTAMLST:

• NETVUSER.NETWORK.VTAMLST

- CLIST:

• NETVUSER.NETWORK.CNMCLST

• NETVUSER.NETWORK.CNMCLST.ENTERP

- PANELS:

• NETVUSER.NETWORK.CNMPNL1

• NETVUSER.NETWORK.SEZLPNLU

- Where the .AON suffixed library contains common modified AONmembers, and the .ENTERP suffixed libraries contain modifiedmembers specific to enterprise versions of NetView.

The creation process of the common networking libraries involves workingthrough the NetView install procedures and the full featured test install ofNetView and populating the common libraries with exploitation of systemsymbolics to avoid the need for local customization as far as possible.

Using this approach, it was found that very little customization on the local(domain specific) library level was required to establish the networkmanagement environment. These local customizations are further describedin Section 4.3.6, “Creation of local (domain specific) NetView libraries” onpage 37.


All other networking customizations could be achieved by modifying thecommon networking library level, as described below.

4.3.1.1 Common networking DSIPARM libraryThe following table lists the modified members in the common networkingDSIPARM library.

Table 7. Modified members in NETVUSER.NETWORK.DSIPARM

4.3.1.2 Common networking DSIPARM library (specific AON)The following table lists the modified members in the common networkingDSIPARM library specifically for AON.

Table 8. Modified members in NETVUSER.NETWORK.DSIPARM.AON

MEMBER COMMENTS

DSIDMNB TASK MOD=CNMCSSIR,TSKID=&DOMAIN.SIR, etc.TASK MOD=DSIZDST,TSKID=&DOMAIN.LUC,MEM=DSILUCTD,etc.TASK MOD=CNMTARCA,TSKID=&DOMAIN.VMT,PRI=5,INIT=NTASK MOD=CNMTGBRW,TSKID=&DOMAIN.BRW,PRI=5,INIT=N

DSIDMNK NCCFID DOMAINID=&DOMAIN.,DMNPSW=&DOMAIN., etc.

DSITBL01 SYN %NV_DOMAIN% = '''&DOMAIN.''';

DSIVPARM VPDINITACBNAME=VPDACB,PASSWORD=&DOMAIN.,VPDREQ=001

DUIFPMEM SC = &DOMAIN.

DUIGINIT RODMNAME=RODM&SYSCLONE.NDOMAIN=&DOMAIN.

FLBSYSD RODMNAME="RODM&SYSCLONE.N"APPLNAME="&SYSNAME.NSNA"APPLPASS="&SYSNAME.N"

FLBSYSDA APPLPASS="&SYSNAME.N"

MEMBER COMMENTS

EZLCFG01 AUTOOPS GATOPER,ID=GAT&DOMAIN.


4.3.1.3 Common networking DSIPARM library (Enterprise feature)The following table lists the modified members in the common networkingDSIPARM library specifically for the Focal Point NetView (Enterprise feature).

Table 9. Modified members in NETVUSER.NETWORK.DSIPARM.ENTERP

4.3.1.4 Common networking CLIST library (Enterprise feature)The following table lists the modified members in the common networkingCLIST library specifically for the Focal Point NetView (Enterprise feature).

Table 10. Modified members in NETVUSER.NETWORK.CNMCLST.ENTERP

4.3.2 Setting up the base components NetView for OS/390After completing step 4, the process of creation of common networkinglibraries, the following sections describe the process of setting up the basecomponents of NetView for OS/390, the Resource Object Data Manager(RODM), and the Graphic Monitor Facility Host Subsystem (GMFHS).

To simplify the local process, it was first created a local install library(NETVUSER.LOCAL.INSTALL). This was shipped (asNETVUSER.&domain..INSTALL) to each domain and the local installationtasks run from there. A specimen install process and task list is shown inSection 4.3.6.1, “Local install process for the networking NetView domains”on page 38.

4.3.3 Setting up the Resource Object Data ManagerUsing system symbolics and the common library structure, all of theinitialization members were included in the common libraries, and no localcustomization was required to start an instance of RODM on any system.

MEMBER COMMENTS

DSIDMNB TASK MOD=CNMCSSIR,TSKID=&DOMAIN.SIR,PRI=5,INIT=NTASK MOD=DSIZDST,TSKID=&DOMAIN.LUC,MEM=DSILUCTD,etc.TASK MOD=CNMTARCA,TSKID=&DOMAIN.VMT,PRI=5,INIT=NTASK MOD=CNMTGBRW,TSKID=&DOMAIN.BRW,PRI=5,INIT=N

MEMBER COMMENTS

CNME1034 DUIFHPRC = 'GMFHS'||SUBSYM('&SYSCLONE.')||'N'EKGHPRC = 'EKGN'||SUBSYM('&SYSCLONE.')


4.3.4 Setting up the Graphic Monitor Facility Host SubsystemAs mentioned in Section 4.1, “Planning the Tivoli NetView for OS/390environment” on page 26, it was planned to only run two GMFHS instanceson the focal point system. However, using system symbolics and commonlibrary structure, almost all of the initialization members were included in thecommon libraries, and just one local customization was required to startGMFHS on any enterprise networking system.

The only local GMFHS customization required was to change the portaddress in the member DUIFPMEM within the local DSIPARM library to avoidconflicts, as it was decided in the project to run both the networking andautomation graphical focal points in the same LPAR (SC66).

4.3.5 Setting up the Automated Operation Network featureThe initial install of the base Automated Operation Network (AON) code wasincluded in the common networking library structure and initial setup. Only afew local customizations were maintained since the exploitation of AONfunctionality was not the focus of this ITSO project.

The local customization work for AON was performed as second part of thelocal (domain specific) install process described in the next section.

4.3.6 Creation of local (domain specific) NetView librariesStep 5, the process of creation/modification of local (domain specific)NetView libraries, is the last step to get the networking NetView environmentup and running. Using a combination of system, user symbolics, and commonlibraries significantly reduced the amount of local (domain specific) tailoring.

In the ITSO project, the only local (domain specific) modification required toestablish the basic network environment was:

• Focal Point NetView SC66N:

Member DUIFPMEM in the local (domain specific) DSIPARM library.

The following local (domain specific) modifications were performed for AON:

• Focal Point NetView SC66N:

The services file on the NMC server also has to be updated to use thesame port address. See Tivoli NetView for OS/390: NetView ManagementConsole User’s Guide, SC31-8665, Section 1.3.6.3.

Note


Members EZLCFG01 and EZLTREE in the local (domain specific)DSIPARM library.

• Procedural NetViews SC42N and SC69N:

Member EZLTREE in local (domain specific) DSIPARM library.

• All NetViews SC66N, SC42N and SC69N:

Update of all DDF panels and control files in the local (domain specific)AON panel library SEZLPNLU with the correct Domain ID.

4.3.6.1 Local install process for the networking NetView domainsThe created local install library (NETVUSER.&domain..INSTALL) was used torun the local install process. Table 11 shows the steps needed to perform thespecific install.

The TASK column cross references to the relevant section in the productdocumentation Tivoli NetView for OS/390, Installation and AdministrationGuide, SC31-8236.

Table 11. Local networking NetView install process

TASK COMMENTS

2.1.9 - Allocate all PDS CNMSJ002

2.1.10 - Change domain and SAnumbers

CNMSJ000 JCL and control cards

2.1.15 - Allocate VSAM clusters CNMSJ004 - Change domain in JCL

2.1.16 - Load VSAM files CNMSJ005 - Change VSAM high-level qualifier

2.1.17 - Assemble VTAM tables CNMSJ006 - Change high-level qualifier and adddomain - may not be required if shared VTAMLIB

2.4.3 - 2.4.6 - Create procedures Specimen procedures in LOCAL.INSTALLCopy to PROCLIB and update as required

3.3.2.7 STATMON preprocessor May not be required


4.3.6.2 Local install process for AONThe TASK column in Table 12 cross references the relevant section in theproduct documentation Tivoli NetView for OS/390, Installation andAdministration Guide, SC31-8236.

Table 12. Local AON install process

4.4 Automation environment

For the automation environment running System Automation, the results ofstep 1 and step 2, the process of planning and defining the automationNetView environment, were as follows:

• System SC66 running an enterprise NetView with System Automationinstalled. This system acted as the automation focal point for all threesystems. It also ran RODM and GMFHS linked to an NMC server.

• System SC42 running a procedural NetView with System Automationinstalled.

• System SC69 running a procedural NetView with System Automationinstalled.

The NetView domain name in each case was the system name suffixed with‘A’, for example, SC66A.

TASK COMMENTS

2.2.2 - Copy AON members tolocal (domain specific) AONpanel library SEZLPNLU

EZLSJ100 - First allocate the local (domain specific)AON library SEZLPNLU. Then run the step inEZLJS100 that copies the named members into thelocal AON library SEZLPNLU. The AON members forthe libraries DSIPRF and DSIPARM are already inthe NetView common libraries.

2.2.3 - Change domain ID Run against local SEZLPNLU only.

2.2.4 - Allocate datasets EZLSJ005, if required.

2.2.5 - Allocate RACF datasets EZLJS006, if required.

2.2.6 - Allocate VSAM files EZLJS008.

3.9.2 - Tailor DDF As required.

3.9.5 - Tailor Gateways and FP As required.


4.4.1 Creation of common automation NetView librariesThe creation of the common automation NetView libraries used to run theSystem Automation features follow the same pattern already described in thenetwork environment section.

According to the recommended naming convention for the NetView librarystructure, the following common libraries were created:

- DSIPARM:

• NETVUSER.SYSTEM.DSIPARM

• NETVUSER.SYSTEM.DSIPARM.ENTERP

- DSIPRF:

• NETVUSER.SYSTEM.DSIPRF

- VTAMLST:

• NETVUSER.SYSTEM.VTAMLST

- CLIST:

• NETVUSER.SYSTEM.CNMCLST

• NETVUSER.SYSTEM.CNMCLST.ENTERP

- PANELS:

• NETVUSER.SYSTEM.CNMPNL1

The creation process of the common automation libraries involves workingthrough the NetView install procedures and populating the common librarieswith exploitation of system symbolics to avoid the need for localcustomization as far as possible.

Using this approach, it was found that very little customization on the local(domain specific) library level was required to establish the systemautomation environment. These local customizations are further described inSection 4.4.6, “Creation of local (domain specific) NetView libraries” on page50.

All other automation customizations could be achieved by modifying thecommon automation library level as described in the following sections.

4.4.1.1 Common automation DSIPARM libraryTable 13 on page 41 lists the modified members in the common automationDSIPARM library compared to the NetView install DSIPARM library. These


modifications represent global changes to run System Automation in theNetView automation environment.

Table 13. Modified members in NETVUSER.SYSTEM.DSIPARM

MEMBER COMMENTS

AOFMSGSY Changed the following statements:SYN %AOFDOM% = '''&DOMAIN.'''SYN %AOFSYS% = '''&SYSNAME.'''SYN %AOFLOADERJOB% = '''AOFLOAD'''SYN %AOFOPGATOPER% = 'GAT&DOMAIN.'SYN %AOFSIRTASK% = '''&DOMAIN.SIR'''

AOFMSG00 Comment out the reference to clist CNME1035

AOFMSG01 Comment out %INCLUDE AOFMSGPMComment out %INCLUDE AOFMSGPAComment out %INCLUDE AOFMSGSTComment out %INCLUDE AOFMSGOP

AOFRINIT Change DEFAOF PPIRCVR=NETQTSKComment out DEFAOF PPIRCVR=PPICMDID

BNJMBDST Change DSTINIT FUNCT=VSAM

DSICMD Include %INCLUDE AOFCMDComment out %INCLUDE DSICMDT

DSICNM Uncomment O SECSTATComment out O MONIT

DSICRTTD Include DEFFOCPT PRIMARY=SC66ALUC,TYPE=ALERTInclude DEFFOCPT PRIMARY=SC66ALUC,TYPE=STATUS

DSIDMN Comment out %INCLUDE DSIDMNTInclude %INCLUDE AOFDMN


Additional comments on the above listing of modifications are as follows:

• AOFMSGSY

Change the synonym statements using the system symbolics available.

• AOFMSG00

DSIDMNB Comment out TASK MOD=CNMCSSIR,TSKID=CNMCSSIR,PRI=5,INIT=NInclude TASK MOD=CNMCSSIR,TSKID=&SYSNAME.ASIR,PRI=5,INIT=N

Change the following statements:TASK MOD=DSIZDST,TSKID=&DOMAIN.LUC,MEM=DSILUCTD,PRI=7,INIT=NTASK MOD=CNMTARCA,TSKID=&DOMAIN.VMT,PRI=5,INIT=NTASK MOD=CNMTGBRW,TSKID=&DOMAIN.BRW,PRI=5,INIT=N

Include TASK MOD=CNMCALRT,TSKID=NETCALRT, PRI=6,INIT=YComment out TASK MOD=CNMCALRT,TSKID=CNMCALRT,PRI=6,INIT=Y

Include TASK MOD=DSIZDST,TSKID=CNMTAMEL,MEM=DUIISC,PRI=5,INIT=NComment out TASK MOD=DSIZDST,TSKID=CNMTAMEL,MEM=DUIISFP,PRI=5,INIT=N

DSIDMNK Include NCCFID DOMAINID=&DOMAIN,DMNPSW=&DOMAIN.,DROP=YES,SUPPCHAR=?Comment out NCCFID DOMAINID=CNM01, DMNPSW=CNM01,DROP=YES, SUPPCHAR=?

Include NCCFIC IC=CNME1034 AOFMSG00Comment out NCCFIC IC=CNME1034 DSITBL01

Include VTAMCP USE=NOComment out VTAMCP USE=YES

Include SC66A RRDInclude SC42A RRDInclude SC69A RRD

DSIOPF Comment out %INCLUDE DSIOPFTInclude %INCLUDE AOFOPF

DSIOPFU Include the following operators:GATSC66A, GATSC69A, GATSC42A

MEMBER COMMENTS


The clist CNME1035 is no longer used in this NetView release. TheNetView initialization steps are now concentrated in the new clistCNME1034, which is coded in REXX and uses PIPEs.

• AOFMSG01

The members AOFMSGST and AOFMSGOP will only be used in theenterprise automation environment (focal point).

• BNJMBDST

Change FUNCT=VSAM will ensure that NPDA will come up as secondaryon the Automation NetView environment.

• DSICMD

The DSICMDT member will only be used in the enterprise automationenvironment. DSICMD should be copied and modified (uncommentDSICMDT statement) in the enterprise specific DSIPARM.

• DSICNM

Changes will set STATMON as secondary on System Automation NetView.

• DSICRTTD

The project environment used the LUC transport method to forward alertsto the specified focal point task.

• DSIDMN

The DSIDMNT member will only be used in the enterprise automationenvironment. DSIDMN should be copied and modified (uncommentDSIDMNT statement) in the enterprise specific DSIPARM.

• DSIDMNB

The TSKID value for the task CNMCALRT needs to be different than theone specified for networking NetView.

The TSKID value for the LUC task, the VMT task and the BRW task needto be different than the ones specified for the networking NetView.

Specifying a different initialization member for the task CNMTAMEL isnecessary to allow resource status forwarding from the status collectors tothe status focal point.

• DSIDMNK

Change VTAMCP to USE=NO to set up the automation NetView to be thesecondary (non networking) NetView.

Change NCCFIC IC=CNME1034 AOFMSG00 to reflect the specificSystem Automation message table AOFMSG00.


• DSIOPF

The DSIOPFT member will only be used in the enterprise automationenvironment. DSIOPT should be copied and modified (uncommentDSIOPFT statement) in the enterprise specific DSIPARM.

4.4.1.2 Common automation DSIPARM library (Enterprise feature)Table 14 lists the modified members in the common automation DSIPARMlibrary specifically for the Focal Point NetView (Enterprise feature) comparedto the NetView install DSIPARM library. These modifications represent globalchanges to run System Automation in the NetView automation focal pointenvironment.

Table 14. Modified members in NETVUSER.SYSTEM.DSIPARM.ENTERP


• AOFMSG01

MEMBER COMMENTS

AOFMSG01 Only copy to enterprise DSIPARM library as reference. No changes.

DSICMD Include statement %INCLUDE AOFCMD

DSICRTTD Only copy to enterprise DSIPARM library as reference. No changes.

DSIDMN Include statement %INCLUDE AOFDMN

DSIDMNB Comment out TASK MOD=CNMCSSIR,TSKID=CNMCSSIR,PRI=5,INIT=NInclude TASK MOD=CNMCSSIR,TSKID=&SYSNAME.ASIR,PRI=5,INIT=N

Change the following statements:TASK MOD=DSIZDST,TSKID=&DOMAIN.LUC,MEM=DSILUCTD,PRI=7,INIT=NTASK MOD=CNMTARCA,TSKID=&DOMAIN.VMT,PRI=5,INIT=NTASK MOD=CNMTGBRW,TSKID=&DOMAIN.BRW,PRI=5,INIT=N

Include TASK MOD=CNMCALRT,TSKID=NETCALRT, PRI=6,INIT=YComment out TASK MOD=CNMCALRT,TSKID=CNMCALRT,PRI=6,INIT=Y

Do not change MOD=DSIZDST,TSKID=CNMTAMEL,MEM=DUIISFP,PRI=5,INIT=N

DSIOPF Include statement %INCLUDE AOFOPF


It is not necessary change anything in this member. Copy only toenterprise DSIPARM library to override its reference in the commonDSIPARM library.

• DSICRTTD

It is not necessary to change anything in this member. Copy only toenterprise DSIPARM library to override its reference in the commonDSIPARM library.

• DSIDMNB

The TSKID value for the task CNMCALRT needs to be different than theone specified for networking NetView.

The TSKID value for the LUC task, the VMT task, and the BRW task needto be different than the ones specified for the networking NetView.

For the task CNMTAMEL, keep the focal point initialization memberDUIISFP.

4.4.1.3 Common automation CLIST libraryTable 15 lists the modified members in the common automation CLIST librarycompared to the NetView install CLIST library.

Table 15. Modified members in NETVUSER.SYSTEM.CNMCLST


• CNME1034

An alias for the automation GMFHS job name and procedure name usedwith CNME2101 is not needed in the procedural automation environment.

MEMBER COMMENTS

CNME1034 Comment out DUIFNAM = 'GMFHS'||SUBSYM('&SYSCLONE.')||'N'Comment out DUIFHPRC = 'GMFHS'||SUBSYM('&SYSCLONE.')||'N'Comment out 'GLOBALV PUTC DUIFHNAM DUIFHPRC'

Comment out EKGHNAM = 'EKGN'||SUBSYM('&SYSCLONE.')Comment out EKGHPRC = 'EKGN'||SUBSYM('&SYSCLONE.')Comment out 'GLOBALV PUTC EKGHNAM EKGHPRC'

CNME1015 Comment out SLIST3.2 = ‘AUTOTASK FLBTOPO’Comment out SNUM= 2Include SNUM = 1

Comment out SLIST3.8 = ‘AUTOTASK FLBTOPO’Comment out SLIST.0 = 8Include SLIST.0 = 7


An alias for the automation RODM job name and procedure name usedwith CNME1098 is not needed in the procedural automation environment.

• CNME1015

The Automation NetView does not need to monitor the SNA Topologyevents and, therefore, does not need to start the SNA Topology features.Comment out entries for the task, FLBTOPO, in this clist.

4.4.1.4 Common automation CLIST library (Enterprise feature)Table 16 lists the modified members in the common automation CLIST libraryspecifically for the Focal Point NetView (Enterprise feature) compared to theNetView install CLIST library.

Table 16. Modified members in NETVUSER.SYSTEM.CNMCLST


• CNME1034

Specify an alias for the automation GMFHS job name and procedurename used with CNME2101 in the enterprise automation environment.

Specify an alias for the automation RODM job name and procedure nameused with CNME1098 in the enterprise automation environment.

MEMBER COMMENTS

CNME1034 Include DUIFHNAM = 'GMFHS'||SUBSYM('&SYSCLONE.')||'A'Include DUIFHPRC = 'GMFHS'||SUBSYM('&SYSCLONE.')||'A'Include 'GLOBALV PUTC DUIFHNAM DUIFHPRC'

Include EKGHNAM = 'EKGA'||SUBSYM('&SYSCLONE.')Include EKGHPRC = 'EKGA'||SUBSYM('&SYSCLONE.')Include 'GLOBALV PUTC EKGHNAM EKGHPRC'

Please be aware that within this project the string ‘EKGA’, as well as thestring ‘EKGN’, was specified as a subsystem identification to OS/390.

Note


4.4.1.5 Common automation VTAMLST libraryTable 17 lists the modified or added members in the common automationVTAMLST library.

Table 17. Modified/added members in NETVUSER.SYSTEM.VTAMLST


• NETVAPPL or A01APPLS

If necessary, create a new VTAM APPL deck or update an existingNetView application member to apply changes to the PPT statement tospecify the secondary program operator (SPO) interface.

The following sections will describe the steps necessary to customize thebase NetView to be used with System Automation and cloning support.

4.4.2 Setting up the base NetView for OS/390After completing step 4, the process of creating common automation libraries,the following sections go on to describe the process of setting up the basecomponents of NetView for OS/390, the Resource Object Data Manager(RODM), and the Graphical Monitor Facility Host Subsystem (GMFHS).

Again, to simplify the local process, the first step was to create a local installlibrary (NETVUSER.LOCAL.INSTALL). This was shipped (asNETVUSER.&domain..INSTALL) to each domain, and the local installationtasks run from there. A specimen install process and task list is shown inSection 4.4.6.1, “Local install process for the automation NetView domains”on page 50.

4.4.3 Setting up the Resource Object Data ManagerIn the automation environment (running System Automation), RODM must beactive on all systems. Since some of the SA RODM definition members,AOFRODM and AOFSFMAP, as well as the member DSIQTSKI, do notsupport system symbolics, it was necessary to copy the System Automation

MEMBER COMMENTS

A01APPLS orNETVAPPL

Comment out &SYSNAME.NPPT APPL AUTH=(NVPACE,PPO),PRTCT=&SYSNAME.N,EAS=1,Include &SYSNAME.NPPT APPL AUTH=(NVPACE,SPO),PRTCT=&SYSNAME.N,EAS=1,


members shown in Table 18 to the local (domain-specific) libraries andchange them afterwards:

Table 18. Modified members in NETVUSER.&domain..DSIPARM


• AOFRODM

This member defines the RODMNAME and the RODMUSER used bySystem Automation for bulk updates to RODM.

• AOFSFMAP

This member contains user defined mapping tables of System Automationstatus information to RODM specific status information.

• DSIQTSKI

This is the initialization member of the NetView task to communicate withRODM. In the System Automation environment, the CMDRCVR statementshould be customized to reflect a different receiver ID than the networkenvironment. The REP statement should, accordingly, be changed toinclude this receiver ID definition and the RODM name related to this local(domain specific) system. Figure 4 shows an example:

Figure 4. DSIQTSKI member of the local DSIPARM library for System SC42

MEMBER COMMENTS

AOFRODM Define the correct RODMNAME and RODMUSER

AOFSFMAP Define the correct RODMNAME

DSIQTSKI Comment out CMDRCVR ID=DSIQTSKIInclude CMDRCVR ID=NETQTSK

Include REP <rodm name>,CONN=Y,AO=Y,T=12,ID=NETQTSK

Comment out REP RODM01,CONN=N,AO=N,T=12,CMD=STARTCNMComment out REP RODM02,CONN=N,AO=N,T=20,ID=NETOP1Comment out REP RODM03,CONN=N,AO=Y,T=30Comment out REP RODM04,CONN=N,AO=N,T=30Comment out REP RODM05,CONN=N,AO=N,T=19Comment out REP RODM06,CONN=N,AO=N,T=30

CMDRCVR ID=NETQTSKREP EKGA42,CONN=Y,AO=Y,T=12,ID=NETQTSK


The ID must be defined to RODM. If the ID is not specified correctly, thenNetView assumes the receiver ID is DSIQTSK. This initialization membershould only be customized in either the networking or the automationenvironment.

4.4.4 Customizing RODM load jobs in the automation environmentThe jobs used to load the RODM data model structures should be changed toinclude only the data model structures used to monitor the SystemAutomation objects.

An example job for the project system SC66 is listed for reference purposesin Appendix B, “System Automation V1R3 members and jobs” on page 233.

4.4.5 Setting up the Graphic Monitor Facility Host SubsystemGMFHS is only required on the focal point system, and no local (domainspecific) customization is required to start an instance of GMFHS on anyenterprise system.

Copy and modify only the following members in the common automationDSIPARM library (NETVUSER.SYSTEM.DSIPARM.ENTERP), specifically forthe Focal Point automation NetView (Enterprise feature):

• DUIFPMEM

This is the definition member for the CNMTAMEL task that defines aresource status manager and allows it to function as a status focal point.Add the following statements to the DUIFPMEM and modify themaccordingly to use TCP/IP to communicate with programmableworkstations:

USETCPIP=YESTCPANAME=<tcpaname on OS/390>PORT=<TCPIP port number of NMC server listening>

Define the status collectors that will be connected to the status focal point.Synchronization will be attempted with these status collectors when theresource status manager is initialized. These keywords are optional butare highly recommended for quick synchronization. The following is aproject example:

&ENTERP. SC = SC66A&ENTERP. SC = SC69A&ENTERP. SC = SC42A&PROCED. SC = &SYSCLONE.A

• DUIGINIT


Modify the following two statements to reflect correct initialization ofGMFHS:

RODMNAME=<RODM name of focal point system>DOMAIN=<NV domain name of focal point system>

4.4.6 Creation of local (domain specific) NetView librariesStep 5, the process of creation/modification of local (domain specific)NetView libraries, is the next step in getting the (System) Automation NetViewenvironment up and running. Using a combination of system and usersymbolics, and common libraries, significantly reduced the amount of local(domain specific) tailoring.

The only local (domain specific) modifications required to establish the basic(System) Automation environment were:

• Focal Point and all target systems:

- SDF members AOFTREE, AOFPNLS and other SDF membersreferring to AOFTREE and AOFPNLS.

- Members AOFRODM, AOFSMAP and DSIQTSKI that were alreadydescribed in Section 4.4.3, “Setting up the Resource Object DataManager” on page 47.

4.4.6.1 Local install process for the automation NetView domainsThe created local install library (NETVUSER.&domain..INSTALL) was used torun the local install process. The table below shows the steps needed toperform the specific install.

The TASK column cross references to the relevant section in productdocumentation, Tivoli NetView for OS/390, Installation and AdministrationGuide, SC31-8236.

Table 19. Local Automation NetView install process

TASK COMMENTS

2.1.9 - Allocate PDS CNMSJ002

2.1.10 - Change domain and SAnumbers

CNMSJ000 JCL and control cards

2.1.11 Loading members ofpartioned data sets

CNMSJ003 JCL

2.1.15 - Allocate VSAM clusters CNMSJ004 - Change domain in JCL

2.1.16 - Load VSAM files CNMSJ005 - Change VSAM high-level qualifier


4.4.6.2 Local install process specifically for SAThe TASK column cross references to the relevant section in the productdocumentation, Tivoli NetView for OS/390, Installation and AdministrationGuide, SC31-8236. Also refer as well to the System Automation for OS/390V1R3 Customization, GC28-1566.

Table 20. Local SA install process

2.1.17 - Assemble VTAM tables CNMSJ006 - Change high-level and add domain.May not be required if shared VTAMLIB.

2.4.3 - 2.4.6 - Create procedures Specimen procedures in LOCAL.INSTALLCopy to PROCLIB and update as required.

3.3.2.7 STATMON preprocessor May not be required.

TASK COMMENTS

2.2.2 - Copy SA members DSIPRF and DSIPARM members will already be inthe common libraries

2.1.1.2 Allocate data setscommon to systems

INGESYSA - Change qualifiers and volumes

2.1.1.3 Allocate Data Sets forDialogs

INGEDLGA

3.9.2 - Tailor SDF As required

3.9.5 - Tailor Gateways and FP As required

TASK COMMENTS



Chapter 5. Customization of System Automation for OS/390

This chapter contains an optimized setup and customization of SystemAutomation (SA) OS/390 V1R3, to avoid unnecessary definitions and providefaster system start-up. It further used addresses the setup of SystemAutomation policies, a policy data base, and provides information andrecommendations for cloning and resource/class support.

5.1 Base System Automation customization

Since System Automation is an application based on NetView, an availableautomation NetView environment, as described in Section 4.4, “Automationenvironment” on page 39, must be set up for System Automation. In additionto the automation NetView customization, it is required to customize and runsome base System Automation setup jobs before going into detailed SystemAutomation customization process. The following sections will detail and workthrough the System Automation preparation and setup process.

1. Preparation and setup jobs for System Automation

2. Modification to the OS/390 system library

3. Creation of a System Automation policy database dialog

The creation of System Automation policy database dialog tools is anecessary step to define what to automate and how automation should beperformed.

5.1.1 Preparation and set up jobs for System AutomationThe System Automation for OS/390 product is shipped independently fromthe OS/390 packages. The typical System Automation high-level qualifier ofits datasets after SMP/E installation is ING. System Automation provides a lotof sample definitions as references, including system parameters, startupprocedures, and sample clists in the sample datasets.

System Automation preparations begin, therefore, with modification andexecution of sample jobs from the SA library, ING.SINGSAMP.

5.1.1.1 Allocating VSAM datasets using INGESYSAThe member, INGESYSA, can be used to allocate System Automationdatasets required for both focal point systems and target systems. Adapt thefollowing statements in member INGESYSA and submit the job to create therequired VSAM datasets:


• Automation status file

• Gateway password verification file

• HCD trace file

• Local volume name

Change all occurrences of INGVOL to the corresponding local volumename.

• Mid-level qualifier for datasets

In the ITSO environment, the mid-level qualifier, USER.&domain., wasused where the dataset names, for example on the focal point systemSC66 ING.USER.SC66A.xxxx, match with the System Automation start-upprocedure.

5.1.1.2 Allocating datasets using INGEDLGAThe member INGEDLGA is used to allocate System Automation datasetsrequired only for the focal point system. It allocates datasets for the SystemAutomation I/O operation and the SA policy customization dialog. Modify thefollowing statements in member INGEDLGA and submit the job to create therequired datasets:

• Mid-level qualifier for datasets

In the ITSO environment, it was set to be SC66A, as this was thedesignated focal point system. Therefore, all datasets allocated by this jobbegan with ING.SC66A.xxxx. As an example, the SA policy dialog ISPFoutput table was set to be ING.SC66A.AOFTABL.

• OPTION statement

Change the OPTION statement to reflect the correct volume name anddevice type.

5.1.1.3 Creating System Automation start-up proceduresThe members, INGESSI and INGESO, are used as System Automation(Automation NetView) sample start-up procedures. Since the subsystemname for the NetView automation environment is defined to ‘NETV’, asdescribed in Section 4.2.2, “OS/390 subsystem extensions” on page 31, thetwo members, INGESSI and INGESO, were copied into the appropriateOS/390 procedure library (SYS1.PROCLIB) and renamed as NETVssSI andNETVssA, where <ss> denotes the specific system identifier.

Modify the members, NETVssSI and NETVssA, to reflect specific commonand local (domain specific) library dataset names.


Modify the DSIPARM library concatenation in the Automation NetViewstart-up procedure, NETVssA, by adding the dataset name of the SystemAutomation DSIPARM input (&SQ2..SINGNPRM) as in the following example:

//DSIPARM DD DSN=&Q1..&DOMAIN..DSIPARM,DISP=SHR// DD DSN=&SQ2..SINGNPRM,DISP=SHR// DD DSN=&SQ1..DSIPARM,DISP=SHR

5.1.1.4 Preparing load job for System Automation RODMIn contrast to the networking environment, the RODM load procedure for theSystem Automation environment needs to load the RODM structure andinstances during different steps of the job.

The sample load job, INGELOAD, provided in the library, ING.SINGSAMP,can be copied to the system procedure library (SYS1.PROCLIB) and modifiedto reflect the following changes:

//EKGIN1 DD DSN=NETVUSER.POLICYDB(LOADSTR0),DISP=SHR//AOFIN3 DD DSN=NETVUSER.POLICYDB,DISP=SHR

The library, NETVUSER.POLICYDB, is the designated output library of theSystem Automation RODM building function to contain the managed RODMobjects.

Modify the RODMNAME statement to reflect the appropriate RODM on thespecific system.

5.1.2 Preparing the OS/390 system environment and libraryWhen the previous customizations are completed, the OS/390 systemenvironment and the procedure library need to be modified for SystemAutomation effectiveness.

Modify the library, SYS1.PARMLIB, as follows:

1. Modify PROGxx to include the following datasets as APF authorizedlibraries:

ING.SINGMOD1ING.SINGMOD2ING.SINGMOD3

2. Modify LNKLSTxx to include the following link library:

ING.SINGMOD2

3. Modify LPALSTxx to include the following library:

ING.SINGMOD3

Chapter 5. Customization of System Automation for OS/390 55

4. Modify SCHEDxx to include the following statements:

PPT PGMNAME(DSIMNT) NOSWAPPPT PGMNAME(CNMINIT) NOSWAP NOCANCELPPT PGMNAME(BNJLINTX) NOSWAP

5. Modify/Check IEFSSNxx to include the additional subsystem names. Thefollowing subsystem strings were used for the automation environmentwithin the ITSO project:

NETV /* for Netview PPI and netview address space */EKGA /* for RODM prefix */

Restart, step by step, (IPL) the OS/390 system with CLPA on completion of allthe above procedures. CPLA is still required when migrating from ESCONManager to System Automation V1R3.

If not migrating from ESCON Manager to SA V1R3, and the IPL of theOS/390 system is not possible for a longer time frame, all the above modifiedparameters can be made effective dynamically by using the following OS/390commands:

SETPROG APF,FORMAT,FORMAT=DYNAMICSETPROG APF,ADD,DSNAME=ING.SINGMOD1SETPROG APF,ADD,DSNAME=ING.SINGMOD2SETPROG APF,ADD,DSNAME=ING.SINGMOD3SETPROG LNK,ADD,DSNAME=ING.SINGMOD2,NAME=LINKITSOSETPROG LPA,ADD,DSNAME=ING.SINGMOD3,MODNAME=(*),MASK(*)SETSSI ADD,SUBNAME=NETVSETSSI ADD,SUBNAME=EKGA

The System Automation address spaces are now ready to be started on theOS/390 system.

5.1.3 Creating System Automation policy database dialog panelsThe System Automation policy database contains all automation policies andinterfaces with the System Automation engine. A dialog tool should bedeveloped first, which will be used to create the System Automation policydatabase. The following section shows the procedure for setting up a dialogtool.

5.1.3.1 Set up a CLIST procedureTo set up the dialogs, first update the TSO logon procedure and set theCLIST member in the SYSPROC library, which is allocated by the TSO logonprocedure. A detailed description in System Automation for OS/390 V1R3Customization, GC28-1566, explains how to create a System Automation


policy dialog in the TSO logon procedure. A CLIST may also be used tocreate a procedure for the System Automation policy dialog.

After OS/390 ServerPac basic installation, the dataset ‘CPAC.CMDPROC’ bydefault will be the system CLIST or REXX library.

Create a new member by copying the existent ISPPDF member and add theSystem Automation datasets to related ALLOCATE statements. Themodifications in the newly-created member might be similar to the followingexample:

***************************** Top of Data ******************************PROC 0 PANEL()ALLOC FI(SYSPROC) SHR DA( +

'ING.SINGIREX' +'DGO.V5R1M0.SDGOEXEC' +'CPAC.CMDPROC' +'OS261270.SCPPCENU'

ALLOC FI(ISPLLIB) SHR DA( +'DGO.V5R1M0.SDGOLOAD' +'ING.SINGIMOD' +'DSN510.SDSNLOAD' +'DSN510.RUNLIB.LOAD' +'SYS1.DGTLLIB'

ALLOC FI(ISPPLIB) SHR DA( +'DSN510.SDSNSPFP' +'ING.SINGIPNL' +'DSN510.SDSNPFPE'

ALLOC FI(ISPMLIB) SHR DA( +'DSN510.SDSNSPFM' +'ING.SINGIMSG' +'QMF330.DSQMLIBE'

ALLOC FI(ISPTLIB) SHR DA( +'&DSNAME' +'ING.SINGITBL' +'ING.USER.SC66A.AOFTABL' +'SYS1.SERBT'

ALLOC FI(ISPSLIB) SHR DA( +'QMF330.DSQSLIBE' +'ING.SINGISKL' +'SYS1.SBLSKEL0'

ALLOC FI(AOFTABL) SHR DA('ING.USER.SC66A.AOFTABL')ALLOC FI(AOFIPDB) SHR DA('ING.SINGIPDB')ALLOC FI(IHVCONF) SHR DA('ING.USER.SC66A.IHVCONF')


5.1.3.2 Update ISPF panelAfter modifying the TSO logon procedure, update the master ISPF panel toinclude the System Automation dialog function. Therefore, modify theISP@MSTR member in ISPF panel library to include the followingstatements:

1. INIT section

$SA @SA @- System Automation dialog for ITSO TI3110

2. PROC section

SA,’CMD(%INGDLG SELECT(ADMIN) ALLOCATE(NO))’

After completing modifications to the TSO logon procedure and the ISPFpanel, the next time you log on to TSO and enter into the new TSO logonprocedure, the new TSO/ISPF master menu will appear as demonstrated inFigure 5.

Figure 5. Master TSO/ISPF panel.

Part of the System Automation datasets allocated are for reference useonly.

Note

Master Application Menu - SC66Opt => Sc => PAGE

USERID - GAOEnter SESSION MANAGER Mode ===> NO (YES or NO) TIME - 12:07

SA SA - System Automation dialog for ITSO TI3110CN CONS - Console Display and Search FacilityCP CPSM - CICSPlex SM 1.4 *NEW with CICS TS 1.3*EJ EJES - A JES3 Spooler Interface - (E)JES (Phoenix Software)HC HCD - Hardware Configuration DefinitionIH IHV - ESCON ManagerIP IPCS - Interactive Problem Control FacilityIS ISMF - Interactive Storage Management FacilityLR LOGREC - Interactive LOGR (CF) LOGREC ViewerOL OPERLOG - Interactive OPERLOG (Syslog) BrowserOP OPC - Operations Planning and Control / ESAP PDF - ISPF/Program Development FacilityR RACF - Resource Access Control FacilitySD SDSF - System Display and Search FacilitySJ J3SD - System Display and Search Facility (JES3)

F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


5.2 Usage of system symbolics and System Automation synonyms

In the ITSO project environment, the three systems, SC66, SC42, and SC69,were the OS/390 system objects. There are several common policies andcharacteristics among these systems, which prove the benefits of usingsymbolics and simplify system definitions and maintenance.

As for system symbolics, Table 21 lists the symbolics used during this ITSOproject.

Table 21. System symbolics used in the ITSO project

In addition to these system symbolics, NetView clone synonyms and SystemAutomation message automation table synonyms help to decrease duplicatedpolicy and object definitions. Some NetView clone synonyms were usedbased on system symbolics. Some System Automation synonyms were used,as well, for message automation table references.

A summary of the different synonyms used for the Automation NetView andSystem Automation is shown in Table 22 and Table 23.

The first table lists the most important NetView clone synonym used in thisITSO project. Using &DOMAIN., instead the hard-coded NetView domainname, enables usage of the member, AOFMSGSY, in a shared DSIPARMlibrary.

Table 22. NetView clone synonym used in the ITSO project

SYMBOLIC COMMENTS

&SYSNAME. System name, for example, SC66, SC42 or SC69.

&SYSCLONE. System identifier. It is defined as the last 2 digits ofSYSNAME, for example, 66,42, or 69.

SYNONYM NAME COMMENTS

&DOMAIN. NetView domain name, for example, SC66A, SC42A,or SC69A. This synonym is defined in the start-upprocedure of the specific NetView.


Table 23 on page 60 lists the System Automation message automation tablesynonyms used in this ITSO project.

Table 23. SA message automation table synonyms used in the ITSO project

5.3 Defining all systems and objects to System Automation

This section describes the definition of all systems and the focal pointstructure and their dependencies. The following steps describe how to enterthe necessary systems, their descriptions, and attributes:

1. Starting the System Automation policy database dialog

2. Creating a new System Automation policy database

3. Entering all systems and objects

4. Building the SA Automation control file (ACF)

5. Building the RODM load statements

It is important to notice that the System Automation policy database for theentire enterprise should be filled with all the object information that SystemAutomation uses. This ensures the best overall control and maintenance ifeverything is defined using the System Automation customization dialog.

Therefore, a thoughtful planning for creation of the object hierarchy and howto group the resources will have a great impact on how powerful the SystemAutomation for OS/390 graphic interface will be.

The chart in Figure 6 exemplifies the hierarchy for the various SystemAutomation objects used in this ITSO project. It was decided to group thesystems by geographical region and the type of applications.

SYNONYM NAME COMMENTS

&AOFDOM. NetView domain name, for example, SC66A for focalpoint system. SC42A and SC69A are for targetsystems. This synonym is defined in the SA memberAOFMSGSY.

&AOFSYS. System name, for example, SC66 for focal pointsystem. SC42 and SC69 are for target systems. Thissynonym is defined in the SA member AOFMSGSY.

&AOFVTAMJOB. VTAM job name defined in the SA memberAOFMSGSY.

&AOFLOADERJOB. RODM loader job name defined in the SA memberAOFMSGSY.


Figure 6. ITSO Enterprise hierarchy in the System Automation Policy DB

5.3.1 Starting the System Automation policy database dialogTo start the System Automation policy database dialog panel shown in Figure7, either:

• Select SA from TSO/ISPF master panel as shown in Figure 5 on page 58


or

• Enter the following TSO command from the ISPF command line panel:

INGDLG SELECT(ADMIN) ALLOCATE(NO)

Figure 7. System Automation PolicyDB Entrance panel

5.3.2 Creating a new System Automation policy databaseThe following steps are used to create a new System Automation policydatabase:

a. Issue the NEW command on the ISPF panel command line.

On the ISPF panel that appears, enter the following fields and continue withPF8 to the next screen:

b. PolicyDB Name: <choose a unique name>

c. Enterprise name: <choose a unique name>

d. Data Set name: <for example, NETVUSER.SA.POLICYDB>

e. Model PolicyDB Name: <for example, *SYSPLEX>

Figure 8 on page 63 shows the ITSO project definitions. To use the model of asingle or other PolicyDB, enter ‘?’ on the Model PolicyDB name, whichprompts the user for additional choices in selecting the Model PolicyDB type.

SA OS/390 PolicyDB Selection Select an entryCommand ===> ________________________________________________ SCROLL===> PAGE

Action PolicyDB Name Enterprise Name/Data Set Name******************************* Bottom of data *******************************



Figure 8. Creating Sysplex PolicyDB for the ITSO Environment

When all data entry is completed, press PF3 to start the generation processof the System Automation policy database with default policy and objectdefinitions according to the specified model PolicyDB.

Figure 9 on page 64 shows all automated resources and resource policyobjects that are generated. Select any resource definition on the left side, orany resource policy on the right side, by their item label.

SA OS/390 Create a New Policy DatabaseCommand ===>

To define a new policy database, specify the following information:PolicyDB Name. . . . . . ITSO_ENTERPRISEEnterprise Name. . . . . ITSO_ENTERPRISEData Set Name. . . . . . 'NETVUSER.SA.POLICYDB'

More: +Managed storage. . . . . NO YES NOManagement class . . . . Blank for default management class *Storage class. . . . . . Blank for default storage class *Volume serial. . . . . Blank for authorized default volume

Data class . . . . . . . Blank for default data class *Space units. . . . . . CYLINDERS CYLS TRKS BLKS KB MBPrimary quantity . . . 1 1 to 999 - In above unitsSecondary quantity . . 1 0 to 999 - In above unitsDirectory blocks . . . 50 1 to 999 or blank - Required for PDSRecord format. . . . : FBRecord length. . . . : 80Block size . . . . . . 3120Data Set Name type . . PDS LIBRARY PDS *Device Type. . . . . . SYSDA

* Used only if Managed storage = YES

Specify one of the existing policy databases to serve as the modelfor the policy database that is being created:

Model PolicyDB name. . . *SYSPLEX PolicyDB name or "?"for list of names



Figure 9. System Automation Entry Type Selection panel

This base System Automation policy database dialog screen allows you tocreate and enter all resource objects and their specific policy rules.

5.3.3 Entering all systems and objectsThe following examples will show how to enter the necessary informationabout the ITSO project environment into the System Automation policydatabase. It is recommended to enter the data in the following sequence:

• 6 - Application

• 5 - ApplicationGroup

• 4 - System

• 3 - SubGroup

• 2 - Group

5.3.3.1 Creating applicationsIn System Automation terms, an application is either an OS/390 subsystem,started task, application, batch job, or non-OS/390 resource that runs on asystem in the OS/390 enterprise environment.

The application definitions for automation include:

• Application name

SA OS/390 Entry Type Selection PolicyDB createdCommand ===>

PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Enterprise Resource Definitions Resource Policy DefinitionsMore: +

1 Enterprise ( ENT ) 30 Timers ( TMR )2 Group ( GRP ) 31 Timeout Settings ( TMO )3 SubGroup ( SBG ) 32 Tape Attendance ( TPA )4 System ( SYS ) 33 MVS Component ( MVC )5 ApplicationGroup ( APG ) 34 MVSCOMP Defaults ( MDF )6 Application (*) ( APL ) 35 System Defaults ( SDF )7 VolumeGroup ( VLG ) 36 Application Defaults ( ADF )8 Volume ( VOL ) 37 Auto Operators ( AOP )9 OperatorView ( OPV ) 38 Auto Msg Classes ( AMC )10 Processor ( PRO ) 39 Network ( NTW )11 Communications Path ( CMP ) 40 NNT Sessions ( NNT )

41 Resident CLISTs ( RES )F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


• Object type (class or instance)

• Application mode (online or batch)

• Application type (STANDARD, JES2, or JES3)

• The name of procedure that runs the job

• Service warning and alert thresholds

• Automation definition and policy

From the System Automation main menu, as shown in Figure 9 on page 64,select Option 6 or APL. An application dialog will be displayed as shown inFigure 10.

Figure 10. Application Entry Selection panel

There are two types of applications to select:

• Class

The application class is designed for applications that inherit a commonpolicy. If there are multiple applications owning generic policies, a classcan be created for these types of applications to allow for easy definitionsof application instances. Using application classes will minimize themaintenance workload when updating or changing something in theSystem Automation policy database.

• Instance

SA OS/390 Entry Selection Row 1 to 13 of 26Command ===> SCROLL===> PAGE

Entry Type : Application PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short Description*SYSTEM Special system jobAPPC APPC/MVS automation policyASCH ASCH automation policyDEFAULTS Application default policyGMFHS Graphical Monitoring Facility definitionINGERMFB RMF batch enquirer definitionINGESO Automation NetView definitionINGESSI NetView subsystem interfaceIO_HEARTBEAT_TASK I/O exception monitoring heartbeatIO_MON_EVENTPROC I/O exception monitoring event analyzerIO_MON_MSGPROC I/O monitoring message processing taskIO_MON_QUERYPROC I/O exception monitoring query taskIO_OPERATIONS I/O Operations functions main component



The application instance definition is used when the application will bemanaged by OS/390. The policy items omitted for an application instancewill be inherited from the application class associated with this type ofapplication instance. A policy item specified for an instance will overrideany application class specification.

In the ITSO project environment, there are two NetView subsystems on eachsystem, one for network environment, and another for system automationenvironment. Both NetViews have the common start-up, WTOR messages,and shutdown policy. Therefore, a class application called NETVIEW_CLASSwas defined for both NetViews, allowing them to share one CLASS for thosepolicies common to both.

Since start-up, WTOR messages, and shutdown policies are defined in theCLASS, there is no need to define them when defining the NetView instancesfor AON and System Automation.

The next section will detail how to create a CLASS in the policy database,and how to apply class to an instance application. On the SA applicationselection panel, enter the NEW command on the command line to go to thepanel that is shown in Figure 11.

Figure 11. Define Application Entry panel

On the Object Type field, choose CLASS to define this class application.

SA OS/390 Define New EntryCommand ===>

To define a new entry, specify the following information:Type. . . . . . . . . . ApplicationApplication Name. . . . NETVIEW_CLASSSubsystem Name. . . . . NETVIEW_CL

------------------------------------------------------------------------------More: +

Object Type . . . . . . CLASS CLASS INSTANCE

Application Type . . . STANDARD STANDARD JES2 JES3(These values cannot be changed after)(the application has been created )

INFOBridge Resource . .Application Mode. . . . BATCH BATCH ONLINEClone Job Name. . . . . NO YES NOJob Name. . . . . . . .Scheduling Subsystem. . MSTR, JES Subsystem or blank

------------------------------------------------------------------------------F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


Press PF3 to quit to application selection panel as shown in Figure 12 onpage 67.

The following steps will define Automation Info, Messages, and Shutdownpolicy items. These items will be inherited by the applications instancesassociated to this application class.

Figure 12. SA OS/390 Application Policy Selection panel

The following options can be customized in an application class.

Application Info: Enter or modify application mode (batch or online) andthe MVS application or job name by using the replication capability togenerate the application name.

Automation Info: This policy item is used to define the application toSystem Automation automation and will be used to define job type, systemname, Parent, start option, and restart option.

Automation Flags: Automation flags allow the user to enable and disableautomation and can also enable or disable automation for specificautomation phases.

It is important to notice that, in the class application definition, the JobName field should be left empty, or it will be valid for all applicationinstances of this applications class.

Note

SA OS/390 Policy Selection Row 1 to 13 of 15Command ===> SCROLL===> CSR

Entry Type : Application PolicyDB Name : ITSO_ENTERPRISEEntry Name : NETVIEW_CLASS Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionLINK TO INSTANCES Link class to instancesAPPLICATION INFO Enter and display Application informationINFO BRIDGE Enter INFO Bridge resource nameRMF Enter RMF objectives and reporting criteriaAUTOMATION INFO Define Application automation informationAUTOMATION FLAGS Define Application automation flagsMESSAGES Define Application messagesSHUTDOWN Define shutdown proceduresTHRESHOLDS Define error thresholdsRESTART Define commands executed at restartMINOR RESOURCES Define Application sub-component flagsSYSTEM ASSOCIATION Define primary and secondary associationsTRIGGER Select Application trigger


Messages: This policy item allows the user to specify automated actions,such as the issuing of a command or reply, to be taken in response to amessage issued by the application.

Shutdown: Specifies normal shutdown commands for any applicationusing System Automation.

Thresholds: Error threshold definitions for applications to define howmany abend errors may occur before a message is logged, or a restartprocess is stopped.

Minor Resources: This policy is used to define minor resources for anapplication.

System Association: This policy item is used to define the primary andsecondary system for the application.

Trigger: Each application may be linked to one or more trigger(s) thatcontrol the start-up or shutdown.

Creating automation Info for an application classSelect Automation Info from the panel, which is shown in Figure 12, and theApplication Automation Definition panel will be displayed as shown in Figure13 on page 69. Enter the JobType and the additional definitions that might benecessary for this application class. Keep in mind that this is a class definitionthat will be valid for other application instances.

The following fields are contained in this automation info Panel:

• Job type

Can be set to MVS, NOMVS, or TRANSIENT. As a standard MVS startprocedure, use MVS for this class definition.

• Startup

This field specifies how the application will be started.

• Edit startup

Select YES if using extra parameters. For this example, it will be keep thedefault.

• Restart option

This field defines the circumstances under which the application should berestarted. In this example, it will be used ALWAYS.


Figure 13. Automation Info for Class Application

Creating shutdown policy for an application classSelect Shutdown from the panel, which is shown in Figure 12 on page 67,and the Subsystem Shutdown Processing panel will be displayed as shown inFigure 14 on page 70.

The following panels define the shutdown commands for the exampleapplication class NetView for OS/390. There are four levels of shutdowncommands that may be used:

1. INIT

Enter commands and/or replies to be executed before a shutdown isactually initiated, for example, sending warning information to users.

2. NORM

Enter the commands and replies that perform a normal shutdown of thesubsystem.

3. IMMED

Enter the commands that perform an immediate shutdown of thesubsystem.

4. FORCE

Enter the commands and replies that perform a forced stop of thesubsystem (class) without any delay.

The following panels illustrate examples for the NetView application class.First, Figure 14 on page 70 shows the Subsystem Shutdown Processingpanel, followed by one Shutdown Reply Processing panel for the normal

SA OS/390 Application Automation Definition Top of dataCommand ===>


Subsystem : NETVIEW_CLDescription : Netview Defaults

Job Name :More: +

JobType . . . . . . MVS (MVS NONMVS TRANSIENT)Transient Rerun . . Transient Jobtype can be rerun (YES or NO)Command Prefix . . Console command character(s)

Sysname . . . . . . SC66 JES Sysname


shutdown reply sequence, and one Shutdown Command Processing panel forthe immediate shutdown commands.

Using the commands CMD or REP at the Actions column of the specificshutdown procedure will enter the appropriate data entry panel.

Figure 14. SA 0S/390 Application Subsystem Shutdown Processing panel

When entering the Shutdown Reply Processing panel, enter the Pass andReply Text fields with the commands that will be issued in a normal shutdownprocedure as shown in Figure 15 on page 71.

SA OS/390 Subsystem Shutdown ProcessingCommand ===>


Subsystem : NETVIEW_CLDescription : Netview Defaults

To specify automated commands or replies when shutting down this subsystem,enter the appropriate action for the particular shutdown type.

Actions: CMD = Command REP = Reply

Action Type Description CMD REPLY

INIT Executed when shutdown initiatedREP NORM Executed when normal shutdown invoked 2

IMMED Executed when immediate shutdown invokedFORCE Executed when force shutdown invoked


Figure 15. SA OS/390 Application Shutdown Reply Processing panel

When entering the Shutdown Command Processing panel, use the commonSystem Automation symbolic &SUBSJOB to substitute the subsystem name.This variable will be resolved to the specific subsystem name whenapplication instances are generated.

Figure 16. SA OS/390 Application Shutdown Command Processing panel

Automation FlagsSystem Automation sets the Automation Flags to default values, which shouldbe kept to enable automation and ensure best performance. The followingstep is only necessary if Automation Flags for specific resources are to be

SA OS/390 Shutdown Reply Processing Row 1 to 5 of 22Command ===> SCROLL===> CSR


Subsystem: NETVIEW_CLShutdown Type: NORM

Enter the replies to be issued when the selected shutdown type is invokedfor this subsystem.

Pass Retry Reply TextCount

1 _____ CLOSE IMMED____________________________________________2 _____ CLOSE IMMED____________________________________________

SA OS/390 Shutdown Command Processing Row 1 to 6 of 23Command ===> SCROLL===> CSR


Subsystem: NETVIEW_CLShutdown Type: IMMED

Enter commands to be executed when the selected shutdown type is invokedfor this subsystem.

Pass Automated Command TextFunction

1 MVS P &SUBSJOB2 MVS C &SUBSJOB3 MVS FORCE &SUBSJOB,ARM


changed from their default settings. If the main Automation Flag is set to NO,it disables the effect of the remaining Automation Flags.

The following Automation Flags for the application class can be specified:

• Automation

• Recovery

• Start

• Shutdown

• Initstart

• Restart

To check the Automation Flags, select the menu item Automation Flags onthe main Application Policy Selection panel as shown in Figure 12 on page67, and it displays the Flag Automation Specification panel illustrated inFigure 17.

Figure 17. SA OS/390 Flag Automation Specification panel

In the ITSO environment, the Automation and Recovery flags were kept to thedefault value of blank. The System Automation menu may also be used tomanually define and display automation flags in the System AutomationNetView.

SA OS/390 Flag Automation SpecificationCommand ===>


Resource: NETVIEW_CLEnter level of automation desired.

Automation Flags: Y = Yes N = No E = ExitsAssist Flags: D = Display L = Log N = None

Actions Flag Auto AssistAutomation . _____ _____Recovery . . _____ _____Start. . . . _____ _____ShutDown . . _____ _____Initstart. . _____ _____Restart. . . _____ _____

Enter or Display times to disable automation . . NO Yes No


Using link to application instancesAfter completing the application class definitions for start-up, shutdown, andautomation and recovery flags, link this application class to the appropriateapplication instances that will inherit these application class policy definitions.

This newly created application class, NETVIEW_CLASS, was linked to theapplication instances of the networking and automation NetView.

If these application instances have already been defined, select the optionLink To Instance on the main Application Policy Selection panel as shown inFigure 12 on page 67. The following panel (Figure 18) is a sample screen ofthe ITSO application instances linked to their application classes.

Figure 18. Link Application Class to NetView instances

An application instance is a subsystem, started task, or application that canoperate on OS/390. An application instance is created practically by using thesame procedure as for application classes with the exception of the keywordINSTANCE instead of CLASS as shown in Figure 11 on page 66.

As a practical example within the ITSO project, the application instanceSAOS390_NETVIEW was chosen to be automated. This application instancewill inherit the policy features defined in the application classNETVIEW_CLASS. The following illustrates the ease of an applicationinstance creation using application class association.

Issue the command, NEW SAOS390_NETVIEW, on the command line of the EntrySelection panel for applications as shown in Figure 19 on page 74.

SA OS/390 Link Class to Instances Row 10 to 16 of 23Command ===> SCROLL===> PAGE


Action Status Entry NameSELECTED NETWORK_NETVIEW

Currently linked to. . NETVIEW_CLASSNETWORK_NETVIEW_SSICurrently linked to. . GENERIC_CLASSNETWORK_RODMCurrently linked to. . RODM_CLASSPROCESSOR_OPERATIONSCurrently linked to. .SAOS390_GMFHSCurrently linked to. . GMFHS_CLASS

SELECTED SAOS390_NETVIEW


Figure 19. SA OS/390 Application Entry Selection panel

On the Define New Entry panel for applications, the following values andsymbols were entered in our scenario:

1. Subsystem Name: NETVSA

2. Clone Job Name (Instance): YES

3. Job Name: NETV&AOCCLONE.A

Using this clone variable will allow that this definition can be shared for all thesystems that will run the System Automation Netview. To use this variable it isnecessary to change the field Clone Job Name for the instance to YES.

In the ITSO environment, the System Automation NetView Job Names wereNETV66A, NETV69A, and NETV42A, and the &AOCCLONE. variable was setto contain the two digit of the OS/390 system identifier.

SA OS/390 Entry Selection Row 10 to 22 of 29Command ===> NEW SAOS390_NETVIEW SCROLL===> CSR


Action Entry Name C Short DescriptionLLA LLA automation policyNETVIEW_CLASS * Netview DefaultsNETVSA Automation NetView definitionNETWORK_GMFHS Network GMFHSNETWORK_NETVIEW Network NetviewNETWORK_NETVIEW_SSI Network Netview InterfaceNETWORK_RODM Network RODMPROCESSOR_OPERATIONS Processor Operations functionsRODM_CLASS * RODM DefaultsSAOS390_GMFHS System Automation GMFHSSAOS390_NETVIEW_SSI System Automation Netview InterfaceSAOS390_RODM RODM automation policy


Figure 20. SA OS/390 define new entry panel for applications

End defining the new application instance with PF3 and select theAutomation Info option to define the parent subsystem.

Figure 21. SA OS/390 Policy Selection panel for applications

Enter the System Automation SSI subsystem name, SSISA, in the ApplicationAutomation Definition panel as the Parent subsystem and return with PF3.


To define a new entry, specify the following information:Type. . . . . . . . . . ApplicationApplication Name. . . . OS390_NETVIEWSubsystem Name. . . . . NETVSA

------------------------------------------------------------------------------More: +

Object Type . . . . . . INSTANCE CLASS INSTANCE

Application Type . . . STANDARD STANDARD JES2 JES3(These values cannot be changed after)(the application has been created )

INFOBridge Resource . .Application Mode. . . . BATCH BATCH ONLINEClone Job Name. . . . . YES YES NOJob Name. . . . . . . . NETV&AOCCLONE.AScheduling Subsystem. . MSTR, JES Subsystem or blank

------------------------------------------------------------------------------


Entry Type : Application PolicyDB Name : ITSO_ENTERPRISEEntry Name : SAOS390_NETVIEW Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionLINK TO CLASS Link instance to classAPPLICATION INFO Enter and display Application informationINFO BRIDGE Enter INFO Bridge resource nameRMF Enter RMF objectives and reporting criteria

S AUTOMATION INFO Define Application automation informationAUTOMATION FLAGS Define Application automation flagsMESSAGES Define Application messagesSHUTDOWN Define shutdown proceduresTHRESHOLDS Define error thresholdsRESTART Define commands executed at restartMINOR RESOURCES Define Application sub-component flagsSYSTEM ASSOCIATION Define primary and secondary associations


Figure 22. SA OS/390 Application Automation Definition panel

The last step is to link this application instance to the application classpreviously defined. Select the Link To Class option on the Policy Selectionpanel for the application and select the appropriate application class.

Figure 23. SA OS/390 Application Link Instance to Class panel

The definition process for the System Automation NetView is completed. Allthe others definitions will be inherited from the application classNETVIEW_CLASS.

The same application instance definition process has to be executed to definethe networking NetViews to the System Automation policy database.

SA OS/390 Application Automation DefinitionCommand ===>


Subsystem : NETVSADescription : System Automation Netview

Job Name : NETVSA&AOCCLONE.More: +

JobType . . . . . . (MVS NONMVS TRANSIENT)Transient Rerun . . Transient Jobtype can be rerun (YES or NO)Command Prefix . . Console command character(s)

Sysname . . . . . . JES SysnameParent(s) . . . . . SSISA

Enter one or more parents (above)

Start on IPL . . . . Started after IPL (YES NO NONE blank)

SA OS/390 Link Instance to Class Row 1 to 4 of 4Command ===> SCROLL===> CSR


Action Status Entry NameGENERIC_CLASSGMFHS_CLASS

SELECTED NETVIEW_CLASSRODM_CLASS

******************************* Bottom of data ********************************


5.3.3.2 Creating an application groupAn application group is a set of applications to which a name is assigned.There are two types of application groups:

1. System application groups

Set of applications that reside on only one OS/390 system image.

2. Sysplex application groups

Set of applications that reside on multiple OS/390 system images within asysplex configuration.

When defining an application group as a sysplex application group, specifythe sysplex group name to which it belongs. A sysplex application group canbe associated with only one sysplex group.

From the main System Automation Entry Type Selection panel, as shown inFigure 9 on page 64, select 5 or APG for ApplicationGroup. The EntrySelection panel for application groups displayed in Figure 24 will appear.

Figure 24. SA OS/390 Application Group Entry Selection panel

Default application groups are available, but in the ITSO project scenario, itwas decided to create one generic system application group for each of thethree systems, regardless of its function as focal point or target system. Inaddition to these generic system application groups, one specific systemapplication group for the focal point system was created.

A sysplex application group can not be associated with a system group.

Note

SA OS/390 Entry Selection Row 1 to 6 ofCommand ===> NEW SCROLL===> PAG

Entry Type : ApplicationGroup PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short DescriptionAPPLL_GROUP_01 Application group 01DEFAULTS ApplicationGroup default policyOPERATIONS Operations componentsSAG_APPL Real APG to mirror the Sysplex APGSYSPLEX_APPLGROUP Sysplex application groupSYSTEM Special system ApplicationGroup

******************************* Bottom of data ******************************


The following system application groups were defined in the sample ITSOSystem Automation policy database:

• Network

• Operations

• SA_OS390

• SC42_Generic

• SC66_Generic

• SC69_Generic

Entering the NEW command in the command line of the Entry Selection panelfor application groups brings up the Define New Entry panel for applicationgroups as shown in Figure 25.

Figure 25. SA OS/390 Application Group Define New Entry panel

Since the set of applications for each particular application group resides onthe same OS/390 system in the ITSO environment, select SYSTEM on theApplication Group Type field and name the individual application group usingthe Name field. Complete the operation by pressing PF3. It appears thePolicy Selection panel for application groups as shown in Figure 26 on page79.


To define a new entry, specify the following information:Type . . . . . . . . . . ApplicationGroupName . . . . . . . . . . OPERATIONS

Application Group Type . SYSTEM SYSTEM SYSPLEX

------------------------------------------------------------------------------More: +

Short Description. . . .Extended Description . .

. .

. .

. .

. .


Figure 26. SA OS/390 Application Group Policy Selection panel

Select the option Applications, and the Applications for ApplicationGrouppanel is displayed as shown in Figure 27 on page 80.

Add or remove applications from the selection screen. APPC, ASCH, JES2,LLA, TCPIP, VLF, TSO, and VTAM were added into the system applicationgroup OPERATIONS. Other applications may be selected in other applicationgroups.

If the applications of the particular application group reside on the multipleOS/390 systems within the sysplex configuration, use SYSPLEX in theApplication Group Type field.

Note

SA OS/390 Policy Selection Row 1 to 9 of 9Command ===> SCROLL===> PAGE

Entry Type : ApplicationGroup PolicyDB Name : ITSO_ENTERPRISEEntry Name : OPERATIONS Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionAPPLGROUP INFO Display ApplicationGroup information

S APPLICATIONS Select Applications for ApplicationGroup-------------------- ---------------------------------------------WHERE USED List Systems linked to this entryUSED IN VIEWS List OperatorViews linked to this entryCOPY Copy data from existing entry-------------------- ---------------------------------------------PROPAGATION THRESH Define thresholds for propagation of status

******************************* Bottom of data ********************************


Figure 27. SA OS/390 Applications for Application Group panel

5.3.3.3 Creating a systemA system is any host system in the System Automation enterprise, and itsdefinition includes:

• Description of the system, including physical location

• Type of Operating System

• Processor operations information

• Details of which IBM automation products are operating on the system

• Member application groups

• NetView and OS/390-related information

• Automation policy for the system

From the main System Automation Entry Type Selection panel, as shown inFigure 9 on page 64, select 4 or SYS for System. The Entry Selection panelfor systems, displayed in Figure 28 on page 81, will appear.

SA OS/390 Applications for Applica Row 1 to 13 of 25Command ===> SCROLL===> PAGE

Entry Type : ApplicationGroup PolicyDB Name : ITSO_ENTERPRISEEntry Name : OPERATIONS Enterprise Name : ITSO_ENTERPRISE

Action Status Application*SYSTEM

SELECTED APPCSELECTED ASCH

GMFHSIO_OPERATIONS

SELECTED JES2SELECTED LLA

SAOS390_GMFHSSAOS390_NETVIEWSAOS390_NETVIEW_SSISAOS390_RODMSAOS390_RODM_DM

SELECTED TCPIPTESTTESTJOB1

SELECTED TSOSELECTED VLFSELECTED VTAM

******************************* Bottom of data ********************************


Figure 28. SA OS/390 System Entry Selection panel

As a sysplex policy database model, five system image objects have alreadybeen created. The system, SAMPLE_SYSTEM_01, is the system object ofthe main focal point system, and the others are backup focal point or targetsystems. This is a sample sysplex architecture.

In the ITSO project, three system objects were created for the SystemAutomation environment. System SC66 will act as the focal point system, andthe systems SC42 and SC69 are the target systems.

To create new system entries, enter the NEW command on the command lineof the Entry Selection panel. The Define New Entry panel, as shown in Figure29 on page 82, will appear.

SA OS/390 Entry Selection Row 1 to 6 of 6Command ===> NEW SCROLL===> PAGE

Entry Type : System PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short DescriptionDEFAULTS System default policySAMPLE_SYSTEM_01 Main focal point system definitionSAMPLE_SYSTEM_02 Backup focal point systemSAMPLE_SYSTEM_03 Target system 1SAMPLE_SYSTEM_04 Target system 2SAMPLE_SYSTEM_05 Sample Coupling Facility

******************************* Bottom of data *******************************


Figure 29. SA OS/390 Define New System Entry panel

SA OS/390 Define New Entry Top of dataCommand ===>

To define a new entry, specify the following information:Type. . . . . . . . . . SystemName. . . . . . . . . . SC66

More: +Operating system. . . . MVS MVS VM TPF VSE CF SNMP

For MVS systems, you must specify at least the following information:MVS SYSNAME . . . . . . SC66 MVS system nameSys-Ops NetView Domain. SC66A Name of the NetView domain

under which SA OS/390 Sys-Opsfunctions run

For non-MVS systems, you must specify at least the following informationif Enterprise Monitoring is to be used:

Unique 5-character ID . Unique ID, different from anyexisting NetView domain name

For SNMP systems, you must specify the following information:TCP/IP address. . . . . TCP/IP address of the

system, in dotted notation

Define system clone information (MVS systems only):Clone Id. . . . . . . . 66 &AOCCLONE.Clone Id 1. . . . . . . SC66 &AOCCLONE1.Clone Id 2. . . . . . . SC66A &AOCCLONE2.Clone Id 3. . . . . . . &AOCCLONE3.Clone Id 4. . . . . . . &AOCCLONE4.Clone Id 5. . . . . . . &AOCCLONE5.Clone Id 6. . . . . . . &AOCCLONE6.Clone Id 7. . . . . . . &AOCCLONE7.Clone Id 8. . . . . . . &AOCCLONE8.Clone Id 9. . . . . . . &AOCCLONE9.

Enter the following NetView and Enterprise Monitoring information:Sys-Ops NetView NetworkName. . . . . . . . . Network name for System Operations

NetView domain (MVS systems only)INFOBridge Resource . . System name as known to INFOBridgeSystem use. . . . . . . FOCALPOINT FOCALPOINT TARGET

The following fields are for Heartbeat processing (MVS systems only):SA OS/390 or AOC/MVSVersion and Release . SA13 SA13 (for SA OS/390 Rel.3),

SV01 (for SA OS/390 Rel.2) orV1R4 (for AOC/MVS Rel.4)

Heartbeat Interval. . . 5 1 - 60 (minutes)Missing Heartbeat Delay 30 1 - 3600 (seconds)

The following field is for Processor Operations functions:ProcOps name. . . . . . SC66 Processor Operations name

(non-SNMP systems only)


This example screen shows the definitions for the automation focal pointsystem:

• SC66 as the System Object name

• SC66A as System Automation NetView domain name

System Automation clone symbolics must be defined in system objects tosupport the cloned application. Therefore, three clone symbolics weredefined for each of the systems within the sysplex environment. In theexample for the automation focal point system:

1. Clone Id: 66

1. Clone Id 1: SC66

1. Clone Id 2: SC66A

Continue with PF8 to the second system definition and enter the ProcOpsName, which specifies the name of the system as known to processoroperation functions. For the automation focal point system, the ProcOpsName, SC66, was used.

When all system definitions are completed, continue with PF3 to enter thePolicy Selection panel for system SC66 as shown in Figure 30 on page 84.The following list specifies the policy items for a system object:

System Info: Specifies operating system type and system name for thissystem object.

Application Groups: Specifies application groups, which are related to thissystem object.

NetView: Specifies NetView-related details for this system object.

Automation: Specifies automation products (RMF, OPC, SDSF) used withthis system.

Automation Console: Defines the MVS route codes and MCSFLAGS for thissystem. WTO messages are sent to the Automation Console.

Automation Setup: Specifies details about the system environment forautomation.

Automation Timer: Displays a list of defined automation timer sets, thus,allowing the user to choose which set is to be associated with this system.


Auto Operators: Display a list of defined auto operators sets, thus, allowingthe user to choose which set is to be associated with the system.

Notify Operators: Specifies human NetView operators who receive a SystemAutomation notification message.

Processor Operations: Specifies information needed by System Automationprocessor operations.

Figure 30. SA OS/390 System Policy Selection panel

System InfoSelect the SYSTEM INFO function to enter the System Information panel asshown in Figure 31 on page 85.

SA OS/390 Policy Selection System createdCommand ===> SCROLL===> PAGE

Entry Type : System PolicyDB Name : ITSO_ENTERPRISEEntry Name : SC66 Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionLOCATION Enter System location

S SYSTEM INFO Enter and display system informationINFO BRIDGE Enter INFO Bridge resource nameAPPLICATION GROUPS Select ApplicationGroups for SystemVOLUME GROUPS Select VolumeGroups for SystemNETVIEW Enter NetView-related informationAUTOMATION Enter automation-related installed productsAUTOMATION CONSOLE Enter MVS route codes for notificationsAUTOMATION SETUP Define system environment for automationMINOR RESOURCES Define sub-component flagsAUTOMATION TIMERS Select Timers for SystemNNT SESSIONS Select NNT Sessions for System



Figure 31. SA OS/390 System Information panel (1/2)

Within the System Information panel, it is possible to define additional clonesymbolics as already previously done at the System Definition panel. IfSystem Automation is used to automate an application that runs on morethan one OS/390 system in the sysplex environment, up to 10 Clone IDs canbe defined for each system. These Clone ID values are automaticallyappended to the job name of a replicated application.

Again, in the ITSO environment, there were three clone symbolics defined foreach of the systems. For example, the following definitions were used forSC66:

AOCCLONE = 66AOCCLONE1 = SC66AOCCLONE2 = SC66A

Having defined these Clone IDs, all applications defined with the policysetting CLONE=YES are set to be cloned at load time of the AutomationControl File (ACF).

Continue with PF8 for the second System Information panel.

SA OS/390 System InformationCommand ===>


More: +Update the following information:

Operating system . . . . . MVS MVS VM TPF VSE CF SNMP

Update the following MVS SYSNAME information (MVS systems only):MVS SYSNAME. . . . . . . . SC66 MVS system name

Enter or update the following system clone information (MVS systems only):Clone Id . . . . . . . . . 66 &AOCCLONE.Clone Id 1 . . . . . . . . SC66 &AOCCLONE1.Clone Id 2 . . . . . . . . SC66A &AOCCLONE2.Clone Id 3 . . . . . . . . &AOCCLONE3.Clone Id 4 . . . . . . . . &AOCCLONE4.Clone Id 5 . . . . . . . . &AOCCLONE5.Clone Id 6 . . . . . . . . &AOCCLONE6.


Figure 32. SA OS/390 System Information panel (2/2)

The second System Information panel provides the following options to beset:

• Heartbeat interval

Specifies the time interval after which the SA system operations functionsends a generic alert from this system to the automation focal pointsystem. This parameter is used to verify the status forwarding path on themultiple systems within the sysplex environment. The default value is fiveminutes.

• Missing heartbeat delay

Specifies the time that the automation focal point system will wait after aheartbeat was expected. If this time expires without receiving theheartbeat, the automation focal point system will begin the missingheartbeat process for the target system. The default value is 30 seconds.

• System use

Specifies whether this system functions as focal point or target system.

In the ITSO environment, the system object, SC66, is the automation focalpoint system, and the system objects, SC42 and SC69, are targetsystems.

SA OS/390 System InformationCommand ===>


More: - +Version and Release. . . SA13 SA13 (for SA OS/390 Rel.3),

SV01 (for SA OS/390 Rel.2) orV1R4 (for AOC/MVS Rel.4)

Heartbeat Interval . . . . 5 1 - 60 (minutes)Missing Heartbeat Delay. . 30 1 - 3600 (seconds)System use . . . . . . . . FOCALPOINT FOCALPOINT TARGET

Update the following Enterprise Monitoring information for non-MVS systems:Unique 5-character ID. . . Unique ID, different from any

existing NetView domain name

Enter or update the following target system information forProcessor Operations functions (non-SNMP systems only):

ProcOps name . . . . . . . SC66 Processor Operations nameF1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


These system information settings are allowed to be tailored based accordingto individual environment requirements.

Application GroupsSelect the Application Groups option on the main System Selection panel,which is shown in Figure 31 on page 85, to enter the following ApplicationGroups Selection panel.

Figure 33. SA OS/390 ApplicationGroups for Systems panel

This Application Groups Selection panel allows specifying the requiredApplication Groups, as defined in Section 5.3.3.2, “Creating an applicationgroup” on page 77, for the particular system.

NetViewSelect the NetView option on the main System Selection panel, which isshown in Figure 31 on page 85, to enter the following NetView Informationpanel.

SA OS/390 ApplicationGroups for Systems Row 1 to 8 of 8Command ===> SCROLL===> PAGE


Action Status ApplicationGroupSELECTED DBDCSELECTED NETWORKSELECTED OPERATIONSSELECTED SA_OS390

SC42_GENERICSELECTED SC66_GENERIC

SC69_GENERICSELECTED SYSTEM

******************************* Bottom of data *******************************



Figure 34. SA OS/390 NetView Information for Systems panel

This NetView Information panel allows specifying the required SystemAutomation NetView domain name. In the ITSO environment, the fieldSys-Ops NetView Domain for system SC66 was set to SC66A.

Automation ConsoleSelect the Automation Console option on the main System Selection panel,which is shown in Figure 31 on page 85, to enter the following ConsoleDefinition panel illustrated in Figure 35 on page 89.

The automation console defines how the Write To Operator (WTO) messagesissued by System Automation should look. The logical MVS Console IDs canbe identified by issuing the MVS command D C on the SDSF Log screen.

SA OS/390 NetView InformationCommand ===>


You can specify the following NetView-related information aboutthis system.

Sys-Ops NetView Domain.. SC66A Name of the NetView domainunder which SA OS/390 System Operationsfunctions run

Sys-Ops NetView NetworkName. . . . . . . . . Network name for System Operations

NetView domain

Network NetView Domain. Name of the NetView domainunder which network automation runs



Figure 35. SA OS/390 Automation Console Definition panel (1/2)

The default logical MVS Console ID is 01, which was used within the ITSOenvironment. Select any route codes by selecting S on the list for Masterconsole action and press Enter.

Figure 36. SA OS/390 Automation Console Definition panel (2/2)

The MCSFLAGS panel will be displayed for further specifications. The chosensettings in the ITSO environment shown in Figure 36 are:

SA OS/390 Environment Definition: CONSOLE (Route Codes)Command ===>


Enter information and select S the route codes for SA OS/390 notifications.Console ID ==> 01

A Code DefinitionMore:

All Display ALL messagesS 1 Master console action

2 Master console information3 Tape pool4 Direct access pool5 Tape library6 Disk library7 Unit record pool8 Teleprocessing control


SA OS/390 Environment Definition: CONSOLE (MCSFLAGS)Command ===>


Select S the appropriate MCSFLAGS.

A Flag DefinitionNumber

S 1 Send message conditionally to console2 Send message unconditionally to console3 Immediate command response (RESP)

S 4 Reply to a WTOR (REPLY)S 5 Broadcast to all active consoles (BRDCST)

6 Queue for hard copy only (HDRCPY)


1. Send messages conditionally to console

2. Reply to a WTOR

3. Broadcast to all active consoles

Automation TimerAutomation Timers are sets of scheduled timers that run commands orautomation procedures at scheduled times. Create a new set of timers basedon specific needs.

For creation of new timer settings, enter option 30 or TMR on the SystemAutomation main entry selection panel illustrated in Figure 9 on page 64.Refer to the System Automation for OS/390 V1R3 Customization,GC28-1566, for a detailed description.

Select the Automation Timers option on the main System Selection panel,which is shown in Figure 31 on page 85, to enter the Timers for Systemspanel shown below.

Figure 37. SA OS/390 Timer for Systems panel

On this selection panel, select SCHEDULED_AUTOMATION.

MVS ComponentThe MVS Component selection allows the user to apply automation to variousOS/390 datasets, resources, and facilities. After defining a new MVScomponent, or using defaults, associate them with the specific system object.

For creation of new MVS components, enter option 33 or MVS on the SystemAutomation main entry selection panel illustrated in Figure 9 on page 64.

SA OS/390 Timers for System Row 1 to 2 of 2Command ===> SCROLL===> PAGE


Action Status TimersSAMPLE_SHUTDOWN

SELECTED SCHEDULED_AUTOMATION******************************* Bottom of data *******************************



Refer to the System Automation for OS/390 V1R3 Customization,GC28-1566, for a detailed description.

Select the MVS Component option on the main System Selection panel,which is shown in Figure 31 on page 85, to enter the MVS Component forSystems panel.

Figure 38. SA OS/390 MVS Component for Systems panel

For the ITSO environment, the default MVS_COMPONENT was selected.

NetworkWhen multiple OS/390 systems are integrated and require consolidatedoperations at one focal point system, use the focal point services to monitorand control the systems. The Network policy object enables you to:

• Define paths for sending messages, commands, or responses

• Define primary and backup focal point systems

• Define Gateway sessions connecting systems

• Define user Terminal Access Facility (TAF)

• Define user NNT sessions

For creation of the new Network policy objects, enter option 39 or NTW on theSystem Automation main entry selection panel illustrated in Figure 9 on page64. Refer to the System Automation for OS/390 V1R3 Customization,GC28-1566, for a detailed description.

Select the Network option on the main System Selection panel, which isshown in Figure 31 on page 85, to enter the following Network for Systemspanel.

SA OS/390 MVS Component for System Row 1 to 1 of 1Command ===> SCROLL===> PAGE


Action Status MVS ComponentSELECTED MVS_COMPONENT

******************************* Bottom of data ********************************



Figure 39. SA OS/390 Network for Systems panel

For the ITSO environment, the Network policy objects FOCAL_NETWORKand TARGET_NETWORK have been created. For this particular focal pointsystem SC66, select the FOCAL_NETWORK option, and for the targetsystems SC42 and SC69, select the option TARGET_NETWORK.

Auto OperatorsAutomation operators are automated operator tasks that can respond tomessages from the operating system, applications, and the networkenvironment without requiring a human interaction. This is necessary forsystem automation.

Automation operators are assigned specific messages on which to react.During automated operations, the messages are routed to the appropriateoperator by using the ASSIGN command.

Create a new set of automation operators, or use the provided default set ofautomation operators, and link to the particular system object.

Select the Auto Operator option on the main System Selection panel, whichis shown in Figure 30 on page 84, to enter the following Auto Operators forSystems panel.

SA OS/390 Network for System Row 1 to 2 of 2Command ===> SCROLL===> PAGE


Action Status NetworkSELECTED FOCAL_NETWORK

TARGET_NETWORK******************************* Bottom of data *******************************



Figure 40. SA OS/390 Auto Operator for Systems panel

In the ITSO environment, the Auto Operators BASE_AUTOOPS andFOCAL_OPERS were selected for the focal point system SC66. Select theappropriate Auto Operators options on other system objects as needed.

Notify OperatorsThe Notify Operators option specifies which message types should behighlighted (held) on specific operator screens. The options are:

• Which operator should receive highlighted (held) notifications

• What kind of messages are to be highlighted (held) for the operator:

- Information

- Eventual action

- Immediate decision

- System wait

- Immediate action

Select the Notify Operators option on the main System Selection panel,which is shown in Figure 30 on page 84, to enter the following OperatorNotification panel.

SA OS/390 Auto Operators for System Row 1 to 6 of 6Command ===> SCROLL===> PAGE


Action Status Auto OperatorsBACKUP_OPERS

SELECTED BASE_AUTOOPSBASE_AUTOOPS_IO

SELECTED FOCAL_OPERSTARGET1_OPERSTARGET2_OPERS

******************************* Bottom of data *******************************



Figure 41. SA OS/390 Operator Notification for Systems panel

Assuming the NetView operator, ITSO1, is the responsible operator, specifythe Notify option for ITSO1 to YES and select the appropriate message typeto be highlighted (held) with S in the specific message column.

After completion of this Operator Notification panel, the user will be promptedto specify a Message Class option. Set the response to ALL consoleautomation messages.

5.3.3.4 Creating a subgroupA subgroup is an intermediary grouping of systems within a larger group.Define a subgroup to a system object by selecting a member system andassigning the name of the subgroup. Subgroups do not need to be defined,but it may be useful in large enterprise environments.

Assuming the ITSO’s focal point system is located in Dallas, and targetsystems are located in Austin, then two geographical subgroups are going tobe created: One subgroup for the focal point system and one subgroup for thetarget systems.

For creation of new subgroup objects, enter option 3 or SBG on the SystemAutomation main entry selection panel, illustrated in Figure 9 on page 64, toenter the following SubGroup policy panel.

SA OS/390 Operator Notification Row 1 to 3 of 21Command ===> SCROLL===> PAGE


Enter operator information and select message type(s) to be held on screen.

Action : S = Select for message class assignment Notify: Yes or NoMessages: S = Select messages to be held

A Operator Operator Notify ---------- Messages ------------ID Description Information

Eventual ActionImmediate Decision

System WaitImmediate Action

S ITSO1 YES S S S S S



Figure 42. SA OS/390 SubGroup Selection panel

Creating a new SubgroupEnter the NEW DALLAS_MVS command to create a subgroup namedDALLAS_MVS. A SubGroup Policy Selection panel for the new subgroup isdisplayed as illustrated in Figure 43.

Figure 43. SA OS/390 SubGroup Policy Selection panel

As the focal point location, DALLAS_MVS must include the designated focalpoint system SC66. Select the SYSTEMS option and enter the appropriatesystems to the specific subgroup as shown in Figure 44 on page 96.

SA OS/390 Entry Selection Row 1 to 2 of 2Command ===> NEW DALLAS_MVS SCROLL===> PAGE

Entry Type : SubGroup PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short DescriptionAUSTIN_MVS Austin MVS Images Geographic SubGroupDEFAULTS SubGroup default policy

******************************* Bottom of data ********************************


SA OS/390 Policy Selection Row 1 to 10 of 10Command ===> SCROLL===> PAGE

Entry Type : SubGroup PolicyDB Name : ITSO_ENTERPRISEEntry Name : DALLAS_MVS Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionSUBGROUP INFO Display Subgroup informationLOCATION Enter SubGroup location

S SYSTEMS Select Systems for SubGroup-------------------- ---------------------------------------------WHERE USED List Groups linked to this entryUSED IN VIEWS List OperatorViews linked to this entryCOPY Copy data from an existing entry-------------------- ---------------------------------------------PROPAGATION THRESH Define thresholds for propagation of status

******************************* Bottom of data *******************************



Figure 44. SA OS/390 SubGroup Systems Selection panel

When the subgroup has been created, it needs to be linked to the sysplexgroup.

5.3.3.5 Creating a groupA group is the largest subdivision of a System Automation enterpriseenvironment. It is a set of systems, and/or subgroups, that can be associatedwith one another for the purpose of monitoring with the System Automationgraphic interface or for System Automation processor operation functions.

An System Automation enterprise may consist of many groups, eachconsisting of one or more systems and subgroups. Define a group byselecting the member systems and subgroups and assigning a name to thegroup.

The status of a group depends on the status of the systems and applicationsit is comprised of.

For creation of new group objects, enter option 2 or GRP on the SystemAutomation main entry selection panel, illustrated in Figure 9 on page 64, toenter the following Group Entry Selection panel.

SA OS/390 Systems for SubGroup Row 1 to 3 of 3Command ===> SCROLL===> PAGE

Entry Type : SubGroup PolicyDB Name : ITSO_ENTERPRISEEntry Name : DALLAS_MVS Enterprise Name : ITSO_ENTERPRISE

Action Status SystemSC42

S SC66SC69

******************************* Bottom of data *******************************



Figure 45. SA OS/390 Group Entry Selection panel

Enter the NEW USSOUTH_SINGLE command to create a new group namedUSSOUTH_SINGLE. A Group Definition Entry panel for the new group isdisplayed as illustrated in Figure 46.

Figure 46. SA OS/390 Define New Group Entry panel

For the ITSO environment, the following three groups were created:

• USNORTH_SYSPLEX_001

Defined as a sysplex group type

SA OS/390 Entry Selection Row 1 to 3 of 3Command ===> NEW USSOUTH_SINGLE SCROLL===> PAGE

Entry Type : Group PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short DescriptionDEFAULTS Group default policyUSNORTH_SINGLE USNORTH Group of Single MVS ImagesUSNORTH_SYSPLEX_001 USNORTH Group of Sysplex MVS Images

******************************* Bottom of data *******************************



To define a new entry, specify the following information:Type. . . . . . . . . . GroupName. . . . . . . . . . USSOUTH_SINGLE

Group Type . . . . . . . STANDARD STANDARD SYSPLEX

ProcOps Commands . . . . NO Group is valid for ProcessorOperations commands (YES/NO)

Short Description . . .Extended Description. .

. .

. .

. .

. .



• USNORTH_SINGLE

Defined as a standard group type

• USSOUTH_SINGLE

Defined as a standard group type

After creation of all three groups, the following Group Entry Selection panel,shown in Figure 47, shows the complete list of all defined System Automationgroups.

Figure 47. SA OS/390 System Automation Groups for ITSO project

5.3.4 Building SA Automation Control File (ACF)After all customizations have been completed, it is necessary to build theautomation policy objects from the data entered into the System Automationpolicy database. In the following sections, the RODM loader input file andAutomation Control File (ACF) will be built. A set of automation control filefragments is also used to add them into System Automation start-upprocedure.

Only some the System Automation customization dialog can be used tocomplete this task of building the object files. The following SystemAutomation dialog panels allow to perform these functions:

1. PolicyDB Selection panel

2. Entry Type Selection panel

3. Entry Selection panel

5.3.3.6 Build from the PolicyDB Selection panelUsing the PolicyDB Selection panel provides the option to build all enterpriseSystem Automation policy objects or a part of policy objects. To enter the


Entry Type : Group PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short DescriptionDEFAULTS Group default policyUSNORTH_SINGLE USNORTH Group of Single MVS ImagesUSNORTH_SYSPLEX_001 USNORTH Group of Sysplex MVS ImagesUSSOUTH_SINGLE

******************************* Bottom of data ********************************


Build Functions Menu panel, shown in Figure 48 on page 99, enter the BUILDcommand on the command line. If several SA policy databases are defined,the BUILD command must be followed by the specific SA policy databasename.

The following Build Functions Menu will appear when entering the command:

BUILD ITSO_ENTERPRISE

Figure 48. SA OS/390 Build Functions Menu panel

From this Build Functions Menu, it is possible to build every SA automationobject file. For this example, building the SA automation control file, select the4 - ACF option to enter the specific BUILDF Parameters panel as illustrated inFigure 49.

SA OS/390 Build Functions MenuCommand ===> 4

1 ALL - Build all files2 RODM - Build RODM loader input files3 Proc-Ops - Build Processor Control File4 ACF - Build automation control file5 NetView/VTAM - Build NetView and VTAM information6 PS/2 Profiles - Build PS/2 profile informationPS/2 profile data set. .


Figure 49. SA OS/390 ACF BUILDF Parameters panel

The BUILDF Parameters panel provides several choices for the specific buildmethod and entry ranges. The following selection fields are to be determinedbased on the automation environment:

• Build Mode

Select ONLINE for foreground, or BATCH for background job processing.

• Build Type

Select MODIFIED for only those entries that have been changed since lastbuild request, or ALL for all eligible entries that will be processed.

• Entry Type

* For all entry types, or specify a specific entry type (for example, APL).

• Entry Name

* For all entries, or specify a specific entry name (for example, GMFHS).

5.3.3.7 Build from the Entry Type Selection panelTo enter the Build Functions Menu panel, shown in Figure 48 on page 99,from the SA OS/390 Entry Type Selection panel, enter the BUILD commandon the command line.

For immediate invocation of the ACF BUILDF Parameters panels, use theBUILDF command on the command line. It is necessary to specify, as a

SA OS/390 BUILDF ParametersCommand ===>


More: +Specify information about the BUILD request:Build Output Dataset. . 'NETVUSER.SYSTEM.ACF1'Build Mode. . . . . . . ONLINE ONLINE BATCHBuild Type. . . . . . . ALL MODIFIED ALL

Specify information about the entry(s) that are to be processed:Entry Type. . . . . . . APL Enter three character entry type

or * to process all entry typesor ? to display list of entry types

Entry Name. . . . . . . GMFHS Enter entry nameor * to process all entriesor ? to display list of entry names

Re-build ACF. . . . . . YES YES NOFlag ICL's. . . . . . . YES YES NO

Specify JOB statement to be used for BATCH builds:F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


parameter to the BUILDF command, the three letter identifier for the policyobject that is to be build. For example, enter:

BUILDF SYS

to build all defined system objects defined to the SA policy database.

5.3.3.8 Build from the Entry Selection panelWhen entering any Entry Selection panel, for example, for applications orsystems, it is possible to enter the BUILDF Parameters panel for thatparticular object by selecting the action keyword F in front of the individualobject.

For example, when selecting 6 - APL (Applications) from the Entry TypeSelection panel to enter the Entry Selection panel for applications as shownin Figure 53 on page 105, it is possible to start the BUILD process for JES2by typing F in front of JES2 and pressing ENTER.

Figure 50. SA OS/390 Entry Selection panel

5.3.5 Build RODM loader input fileTo enter the Build Functions Menu panel, shown in Figure 51, enter one of thepreviously described methods. As an example, enter the Entry Type Selectionpanel for the appropriate SA policy database (ITSO_ENTERPRISE) andissue the BUILD command on the command line.



Action Entry Name C Short Description*SYSTEM Special system jobAPPC APPC/MVS automation policyASCH ASCH automation policyDEFAULTS Application default policyGENERIC_CLASS * Generic MVS Tasks DefinitionGMFHS Graphical Monitoring Facility definitionGMFHS_CLASS * GMFHS DefaultsIO_OPERATIONS I/O Operations functions main component

F JES2 JES2 policy definitionLLA LLA automation policyNETVIEW_CLASS * Netview DefaultsNETVSA Automation NetView definitionNETWORK_GMFHS Network GMFHS


Figure 51. SA OS/390 Build Functions Menu panel

Select the 2 - RODM option from Build Functions Menu, and the RODM LoadFunction panel will be displayed as illustrated in Figure 52 on page 102.

Figure 52. SA OS/390 RODM Build panel

On this RODM Build Menu, it is possible to specify the output dataset for theRODM Build function. This dataset name should match the input datasetname specified in the RODM start-up procedure and RODM load jobINGELOAD of the automation environment.

The RODM load job INGELOAD is designed for SA functionality. It isnecessary to customize this job accordingly before submitting it.

The following RODM policy object members will be created after the RODMbuild function is called. Some important members and their functions aredescribed as follows:

• LOADINS0

This file contains the instance definitions for all systems. The instanceloader file defines all instances of both the System Automation and theNetView GMFHS classes.

SA OS/390 Build Functions MenuCommand ===> 2

1 ALL - Build all files2 RODM - Build RODM loader input files3 Proc-Ops - Build Processor Control File4 ACF - Build automation control file5 NetView/VTAM - Build NetView and VTAM information6 PS/2 Profiles - Build PS/2 profile informationPS/2 profile data set. .

SA OS/390 Build MenuCommand ===>

1 BUILDR - Build RODM loader input filesEnterprise . . . . . . ITSO_ENTERPRISEOutput data set. . . . 'NETVUSER.SYSTEM.LOADRODM'

2 SUBMIT - Submit job to process BUILD outputthrough RODM loader

B BROWSE - Browse output data set All the "LOADxxxx"E EDIT - Edit output data set members are output


• LOADSTR0

This structure loader file contains the class definitions for SystemAutomation for OS/390 object classes.

• LOADxxxx

These files contain instance definitions for the one particular target systemonly.

• AOFACFMP

This member contains an indication as to how the system is used as afocal point or target system.

5.4 Defining dependencies and start-up behavior

The applications on OS/390 are composed of resources distributed overdifferent system images, especially in a sysplex environment, where theworkload could be beyond the capacity of a single system. Management forthose separated and distributed applications over several systems becomescritical within a sysplex environment.

System Automation is able to automate complex relationships amongdifferent applications and control their operations within the given systems.One of the key automation controls in System Automation for OS/390 is thehierarchy concept of a parent/child relationship. It is possible to define asubsystem on one system as to be the parent or child of a subsystem ofanother system in the sysplex environment. Once this relationship isestablished, System Automation will not start one child subsystem unless allparent subsystems are started and active. Only if the parent subsystemshave the status UP or ENDED, will System Automation try to start all of thedefined children subsystems (assuming that their automation flags are set toallow automated operation).

Likewise, when stopping a subsystem, System Automation will use theparent/child relationship to determine which subsystem is to shutdown and inwhich sequence the shutdown process has to take place.

5.4.1 Define dependenciesWithin System Automation for OS/390, it is required to define separatedependencies for starting and stopping applications or subsystems.

The parent field at the Application Policy Entry panel allows to specify whichapplications or subsystems need to be available before the given application


can be started. Specify only those applications or subsystems upon which thegiven application has an immediate dependency.

For any automated application, the System Automation engine can capture itsrelated messages and set the application status to UP when its start-upprocess is successfully completed. Once the specific application orsubsystem status is UP, System Automation continues to start the dependentchildren applications.

For this purpose, it is necessary to maintain the SA automation tableAOFMSG01 or create and include the new (self coded) automation tablemember for migration purposes. Within AOFMSG01, all key messages for theautomated applications need to be defined and maintained according to thespecific automation requirements. For example, the message, IST020I,indicates that the VTAM initialization process is complete, and SystemAutomation can set the status for VTAM to UP when it captures this message.After VTAM is set to status UP, System Automation will start up definedchildren subsystems of VTAM, such as TSO, TCPIP, and so on.

The AOFMSG01 is the master automation table that includes several otherautomation tables specific for applications defined to System Automation.The included automation table members consist of start-up, shutdown, orreply messages for the particular application.

The automation table, AOFMSG01, as it is shipped by default with SystemAutomation, already contains most of the OS/390 subsystems or applications.If a fragment for a new application is to be added, include a new automationtable member with its basic messages for its start-up and shutdowncompletion defined into AOFMSG01.

The automation table, AOFMSG01, takes over automation from DSITBL01 orAOFMSG00 after the Automation Control File (ACF) is loaded.

The policy to define dependencies depends on your system environment andautomation requirements. The application dependency is defined whenmaintaining the Application Policy definitions.

For example, when defining the TCPIP application as shown in Figure 53, it isnecessary to define its parent subsystem VTAM.


Figure 53. SA OS/390 Application Automation Definition panel

A subsystem or application may have one or more parents and can also haveone or more children. This relationship completely depends on the start-uplogic and sequence required for the individual OS/390 environment. For thegiven example of the subsystem, VTAM, the subsystems TCPIP and TSO areonly allowed to start after successful completion of VTAM initialization.

In the ITSO environment, dependencies were defined among all automatedapplications for the focal point system SC66 and the target systems SC42and SC69.

To obtain the dependency relationship among the automated applications,use the System Automation DISPTREE command. The dependency tree, asshown in Figure 54, demonstrate the relationship on the focal point systemSC66.


Entry Type : Application PolicyDB Name : NEW1Entry Name : TCPIP Enterprise Name : ITSO_ENTERPRISE

Subsystem : TCPIPDescription :

Job Name : TCPIPMVSMore: +

JobType . . . . . . MVS (MVS NONMVS TRANSIENT)Transient Rerun . . Transient Jobtype can be rerun (YES or NO)Command Prefix . . Console command character(s)

Sysname . . . . . . SC66 JES SysnameParent(s) . . . . . VTAM


Start on IPL . . . . Started after IPL (YES NO NONE blank)F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Be careful to avoid creating loop dependencies for applications whendefining applications within a sysplex environment.

Note


Figure 54. SA OS/390 Application Dependencies for Focal Point System SC66

5.4.2 Define start-up behaviorAll applications automated by System Automation may have different start-upbehavior. Use different start-up policies to automate the particularapplications. For example, define Start on IPL, Start on Recycle, or a specificStartup Policy as illustrated in Figure 55 on page 107.

AOFKTREE SA OS/390 - Command Dialogs Line 1 of 19Domain ID = SC66A -------- DISPTREE ---------- Date = 12/11/99Operator ID = GAO Time = 12:29:50

Subsystem ==> System ==>

SC66 --+DEFAULTS --+

SUBSYSTEM --+VLF --+

LLA --+SSISA+-- NETVSA

+-- JES2| +-- VTAM| +-- SSIAON| | +-- NETVAON| | +-- RODMAON| | +-- GMFHSAON| +-- TCPIP| +-- APPC| | +-- ASCH| +-- TSO+-- RODMSA

+-- GMFHSSA

Command ===>PF1=Help PF2=End PF3=Return PF4=Focus PF5=Info PF6=RollPF7=Back PF9=Refresh PF11=Right PF12=Retrieve


Figure 55. SA OS/390 Define Start Behavior for TCPIP

Considering system dependencies for automated applications, severalchoices are available to start applications. In the given example of theapplication TCPIP, select whether TCPIP is to start at system IPL and/or afterrecycle by System Automation. In addition, specify start-up criteria using theStartup field. Options for this field are:

• MVSSTART

Indicates this application uses the MVS START command. For example,the MVS S <jobname> command is issued for this application subsystem. Forediting additional start-up parameters, set the Edit startup field to YES, forexample, to add the command string, ‘,SUB=MSTR’.

• CUSTOMER

Indicates this application is to be started by a customized MVS command.Create the start-up parameters by setting the Edit startup field to YES andenter the appropriate start-up command, for example, ’=STA DB2’.

• PARENT

Indicates this application is directly started by its parent, and does notneed the start-up command.

In the ITSO environment, the application TCPIP has the parent VTAM, but isstarted using the MVS START command; so, the keyword, MVSSTART, isselected.


Entry Type : Application PolicyDB Name : NEW1Entry Name : TCPIP Enterprise Name : ITSO_ENTERPRISE

Subsystem : TCPIPDescription :

Job Name : TCPIPMVSMore: - +

Sysname . . . . . . SC66 JES SysnameParent(s) . . . . . VTAM


Start on IPL . . . . Started after IPL (YES NO NONE blank)Start on Recycle . . Started after recycle (YES NO NONE blank)Startup . . . . . . MVSSTART Startup control (MVSSTART PARENT CUSTOMER)Edit startup . . . NO Edit startup parameters (YES NO)F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


5.5 Customizing the Status Display Facility (SDF)

The Status Display Facility, a function of System Automation, is used tomonitor system resources on the focal point system as well as on othertargets systems. The SDF reads and captures resource objects from SystemAutomation policy database and monitors such resources on the AutomationNetView. The defined resources and their status information are representedby different colors.

To use SDF for monitoring resources, it is necessary at first to define the SDFpanel and structure tree. After the System Automation policy database isestablished, the user can work with the subsystem resources from theSystem Automation policy database.

During the initialization process of System Automation for OS/390, theAOFTDDF task loads SDF definition members for the panel format, panelflow, and its tree structure. Change the following members for SDF in theNetView DSIPARM library to have them reflect the specific systemautomation items.

The member AOFINIT defines parameters common to all SDF panels andbasic initialization specifications, such as screen size, default function keys,and the initial screen displayed when a SDF session is started.

The member AOFTREE includes the SDF status tree, and the memberAOFPNLS includes the panel tree for SDF.

5.5.1 Customizing the panel member AOFPNLSThe member AOFPNLS defines SDF status panels using specific paneldefinition statements. Panels can either be loaded automatically when SDFstarts, or dynamically loaded using the SDF PANEL command. For panels tobe loaded automatically, add an %INCLUDE statement, specifying theparticular panel definition member, to the main panel definition memberAOFPNLS in the NetView DSIPARM library.

For the ITSO environment, with its focal point system and the two targetsystems, the following %INCLUDE statements were added to the main SDFpanel member AOFPNLS:

•%INCLUDE(AOFPSYST)

•%INCLUDE(AOFPSC66)




The panel AOFPSYST represents the SDF main panel, while the otherincluded members represent each of the system objects.

The following example SDF panel member, AOFPSYST, shown in Figure 56,represents the main panel definitions for the ITSO environment. It specifiesthe entry panel that is displayed when issuing the SDF command in theAutomation NetView environment.

Figure 56. SDF Main panel member AOFPSYST

P(SYSTEM,24,80)TF(01,02,10,WHITE,NORMAL)TT(SYSTEM)TF(01,23,58,WHITE,NORMAL)TT(SA OS/390 - SUPPORT SYSTEMS)TF(03,05,10,T,U)TT(System)SF(SC66,05,05,10,N,,SC66)ST(SC66)SF(SC69,07,05,10,N,,SC69)ST(SC69)SF(SC42,09,05,10,N,,SC42)ST(SC42)TF(03,14,24,T,U)TT(Subsystems)SF(SC66.APPLIC,05,14,24,N,,SC66,Q1)SF(SC69.APPLIC,07,14,24,N,,SC69,Q1)SF(SC42.APPLIC,09,14,24,N,,SC42,Q1)TF(03,27,34,T,U)TT(WTORs)SF(SC66.WTOR,05,27,34,N,,SC66,1)SF(SC69.WTOR,07,27,34,N,,SC69,1)SF(SC42.WTOR,09,27,34,N,,SC42,1)TF(03,37,45,T,U)TT(Gateways)SF(SC66.GATEWAY,05,37,45,N,,SC66,1)SF(SC69.GATEWAY,07,37,45,N,,SC69,1)SF(SC42.GATEWAY,09,37,45,N,,SC42,1)TF(03,48,58,T,U)TT(Spool)SF(SC66.SPOOL,05,48,58,N,,SC66,1)SF(SC69.SPOOL,07,48,58,N,,SC69,1)SF(SC42.SPOOL,09,48,58,N,,SC42,1)TF(03,61,69,T,U)TT(MVS Comps)SF(SC66.MVSCOMP,05,61,69,N,,SC66,1)SF(SC69.MVSCOMP,07,61,69,N,,SC69,1)SF(SC42.MVSCOMP,09,61,69,N,,SC42,1)TF(24,01,47,T,NORMAL)TT(1=HELP 2=DETAIL 3=RETURN 6=ROLL 8=NEXT SCR)TF(24,48,79,T,NORMAL)TT( 10=LEFT 11=RIGHT 12=TOP)EP


The following objects were part of the ITSO System Automation environmentand defined to the SDF:

• System

• Subsystem

• WTORS

• Gateways

• Spool

• MVS Comps

5.5.2 Customizing the status member AOFTREEThe System Display Facility uses a tree structure to set up the hierarchy ofthe monitored resources displayed on the SDF status panels. A SDF treestructure starts with the system name that is defined in the SA policydatabase as the root node, and it has the level number 1.

Tree structure subordinate levels to the root node are the monitoredresources. The level numbers of these resources reflect their dependency oneach other. The member, AOFTREE, in the ITSO environment, includes thefollowing members:

•%INCLUDE(AOFTSC66)



According to the definitions of ITSO System Automation policy database, thesymbolic &AOCCLONE1. is the root node name for each system. A genericset of applications were selected as automated objects so that each systemhas the same resource types for SDF monitoring.

The following list represents the resource hierarchy of the focal point member,AOFTSC66:

1 SC662 SYSTEM3 APPLIC4 SUBSYS

2 WTOR2 SPOOL2 GATEWAY2 MVSCOMP


5.5.3 Defining SDF gatewaysTo monitor the resources on the multiple systems within a sysplexenvironment, it is necessary to define gateway policies to the SystemAutomation policy database in order to forward automation informationbetween target systems and the focal point system.

In the ITSO environment, a gateway for each system was defined. Thegateway name was specified to GAT&AOCCLONE2. to take advantage ofSA’s clone symbolics representing the particular NetView domain name, forexample, SC66A for the focal point system SC66.

5.5.4 Starting the SDF monitorSince the NetView data service task AOFTDDF supports the SDF feature,ensure the autotask AOFTDDF is up and running before starting SDF. Inorder to start the autotask, AOFTDDF, issue the following NetView command:

START TASK=AOFTDDF

To start the SDF environment, issue the NetView SDF command. Theexample screen displayed in Figure 57 represents the SDF main panel of theITSO environment.

Figure 57. SDF Main panel of the ITSO environment


The SDF main panel shows three lines representing the system objects(SC66, SC69, and SC42). Each system row is divided into subsystems,WTORs, gateways, spool, and MVS components.

For detailed information about one system, place the cursor on its row andpress PF2. The screen shown in Figure 58 demonstrates the informationavailable for the focal point system SC66.

Figure 58. Detail information about the Focal Point System SC66

This displays all subsystems as defined in the System Automation policydatabase, the OS/390 spool, and gateways to other systems. All monitoredresources are currently active, which is represented by the green color.

Further information about specific monitored resources can be obtained byplacing the cursor on the particular object and pressing PF2.

The following g screen illustrated in Figure 59 on page 113 details theinformation for the spool object JES2.


Figure 59. Detail information about the Spool Object JES2

It provides information for JES2 of its spool utilization status.



Chapter 6. Installation of the NetView Management Console

This chapter describes the installation and setup of the NetView ManagementConsole (NMC) server and client workstation. It details the necessary stepsto connect to Tivoli NetView for OS/390 and between the NMC server andclient workstations.

In addition to NMC, the functionality allowing the user to access and issuecommands to NetView from the Web along with the setup and basic usage ofthe NetView 3270 Management Console will be covered.

The following files shown in Table 24 were used as main references to assistin the setup and customization of the various procedures included in thischapter and may be helpful in future trouble shooting if the need arises.

Table 24. Main reference files to consult

These references have been obtained as of December, 1999. Access at anytime to the most up to date references to any of the Tivoli NetView for OS/390or System Automation for OS/390 related topics may be obtained via the Webat the following URL addresses:

http://www.tivoli.com/nv390http://www.s390.ibm.com/sa

File Name Description

egvread1.me NMC Topology Console from TivoliNetView CD \readme\enu

egvread2.me NMC Topology Server from Tivoli NetViewCD \readme\enu

flbread1.me NetView 3270 Management Console fromTivoli Netview CD \readme\enu

Redbook: An Introduction to TivoliNetView for OS/390 V1R2, SG24-5224

Chpt 6 - “MVS TCP/IP Support”Chpt 9 - “NetView Management Console”Chpt 14 - “NetView 3270 Java Client”Chpt 15 - “Web Access to NetView/390”

Redbook: Parallel Sysplex Automation:Using System Automation for OS/390,SG24-5442

Chpt 6 - “Using the Graphical Interface toManage SA on OS/390”

nmcpdf.zip IBM Web site: Systems Automationhomepage, download section using SA forOS/390


The diagram shown in Figure 60 summarizes the following topics covered bythis chapter:

• NMC Server setup

• NMC Client setup

• Web access to NetView OS/390

• NetView 3270 Management Console (Java)

Figure 60. Addressed topics about the NMC, Web access, and Java console


6.1 Prerequisites for NetView Management Console Version 1.3

For a detailed description of all software and hardware requirements, refer tothe Readme file available on the Tivoli NetView for OS/390 CD distributionmedia (/readme/enu/egvread2.html) or the latest Readme file availabledirectly on the Tivoli NetView for OS/390 Web support page(http://www.tivoli.com/nv390).

6.2 Setting up the NMC Server

This section contains information about the NetView Management ConsoleTopology Server Version 1.3.0. The server interacts with Tivoli NetView forOS/390 to obtain and display network and system views of your enterpriseenvironment. These views are displayed by the Java-based Tivoli NetViewManagement Console Topology Console.

The section is divided into the following categories:

1. Installing NMC Topology Server to run as a Windows NT service

- Software installation

- Environment setup

2. Setting up NMC Topology Server for Systems Automation

- Installing NMC for System Automation for OS/390

- Issuing SA OS/390 commands using the NMC

3. Starting the NMC Topology Server using TCP/IP

- Enabling TCP/IP for NetView on OS/390

- Starting the Topology Server

4. Uninstalling the NMC Topology Server

5. Hints and tips for the NMC Topology Server

6.2.1 Installing NMC Server to run as a Windows NT serviceThis section will explain, in detail, the install process and the setup procedurefor the NMC Topology server, which is, in general, the content of the provided

The following detailed sections on installation and customization of theNMC Topology Server describes only the platform Windows NT. The NMCTopology Server is also available on the platforms AIX and OS/2.

Note

Chapter 6. Installation of the NetView Management Console 117

Readme file EGVREAD2.ME on the NMC installation CD along with severalsituations derived from the actual install at the ITSO environment.

6.2.1.1 Selecting the correct filesTo install the NMC Topology Server on Windows NT, the correct files toinstall are located in the Tivoli NetView for OS/390 CD distribution mediaunder the directory \WIN32 for the Windows NT NMC Topology Server.The English version of NMC Topology Console will be in \ENU (or /ENU),and the Japanese version will be in \JPN (or /JPN).

The following file is distributed as part of the NetView ManagementConsole Server:

- This package, DUINMCSW.EXE, contains the NMC Topology Server ina self-extracting unzip file for Windows NT.

6.2.1.2 Software installationTo install the NMC Topology Server for the networking environment onWindows NT, follow these steps:

1. To install the NMC Topology Server from CD:

- Insert the Tivoli NetView for OS/390 CD distribution media into the CDdrive of the workstation.

- Find the correct drive and directory that the NetView ManagementConsole Server for Windows resides on. The directory is \win32\enu or\win32\jpn, and the file name is DUINMCSW.EXE. Running this filefrom the CD will start the unpacking process.

---OR---

1. To install the NMC Topology Server by HTTP download:

- With any Web browser, go to the following URL:http://www.tivoli.com/nv390/downloads

- Download the Windows version of the NetView Management ConsoleServer into a temporary directory as DUINMCSW.EXE.

To install the NMC Topology Server on OS/2 or AIX from the NetViewhost (mainframe) or CD via the Tivoli Software Installation Service, referto the EGVREAD5.ME file located under /usr/lpp/netview/install on yourOS/390 Unix System Services if Tivoli NetView for OS/390 FMIDJPZ8454 is installed, or under README/ENU on the Tivoli NetView forOS/390 CD.

Note


---OR---

1. To install the NMC Topology Server via a download from mainframe DASD:

- Use either a receive from an emulator session or ftp to do a binarydownload of member duinmcsw from the SEGVPS21 target library intoa temporary directory as DUINMCSW.EXE.

2. Running the DUINMCSW.EXE file will unpack the files and invoke theinstallshield setup application. To perform the install, follow these stepsafter starting DUINMCSW.EXE from the command line or by doubleclicking on the file icon.

3. The following dialog will ask the user to "Select Yes to continue with theinstallation”, on “Select No to exit the installation process". If No isselected, the process ends here. Select Yes to continue to the next step.

Figure 61. Installation Wizard Startup window

4. Displayed next will be a welcome dialog titled "NMC Topology Server -Welcome". Selecting the Next button will display a "NMC Topology Server- Installation Directory" dialog where the user selects the directory intowhich the installation files are unpacked. The default directory isx:\TEMP\NMCServer, where x: is the drive on which windows is installed.Selecting the Finish button will unpack the files and start the installationprocess. The user is then prompted to create the output directory if it doesnot already exist.

5. The following dialog named "Welcome" is the beginning of the NetViewManagement Console Server setup program. Selecting Next will display


the next "Information" dialog, which contains the read.me file for the userto review.

6. Selecting the Next button from the "Information" dialog will display the"Choose Destination Location" dialog. The drive may be changed, butchanging the path information is NOT recommended. The path is astandard used by Tivoli, and unpredictable results in the program canoccur if this is modified.

7. Selecting the Next button will display the "Setup Type" dialog. The defaultselection will have the Typical radio button already selected. This willinstall all of the files available for the server and is the recommendedselection.

- Choosing the Compact radio button will install all of the binaries exceptfor the tools files.

- Choosing the Custom button, a "Select Components" dialog isdisplayed. Use the check boxes to manually select the componentsdesired. The choices are "Program Files" or "Tools Files".

8. Selecting the Next button will display the "Start Copying Files" dialog.This shows the setup type that has been selected for the NetViewManagement Console Server and the path it will be installed into.

9. Selecting the Next button will cause the binaries to be installed.

10.When the binaries are installed, a "Setup Complete" dialog will bedisplayed. Click on Finish to end the installation process.

6.2.1.3 Information on copy problems with setup_env.cmdBy default installation, a file, SETUP_ENV.CMD, is copied to the%WINDIR%\system32\drivers\etc\Tivoli directory and updated for the NMCServer to start. However, if, for example, the Tivoli Framework has beeninstalled on the system, the copy and update of SETUP_ENV.CMD might beunsuccessful. If it fails, several warning messages, prior to the display of the"Setup Complete" dialog, will indicate this problem.

If the Tivoli Framework is installed on the workstation, make sure toinstall the NMC Server onto the same drive as the Tivoli Framework.This is because the setup_env.cmd file installed by the Tivoli Frameworkwill be used to set the %BINDIR% environment variable, which isneeded for the NMC Server to start correctly.

Note


The first message will inform the user "Could not copy the setup_env.cmd fileto the (drive:)\Winnt\system32\drivers\etc\Tivoli directory”. Subsequentmessages will describe reasons for the failure and instruct the user to copy itmanually and update it.

It is necessary to check and update the following two variables within theSETUP_ENV.CMD file:

• BINDIR

Specifies the directory of the server binaries, which is, in most cases, oneof the following directories, depending on what directory structure is used:

- (drive:)\Tivoli\bin\w32-ix86

- (drive:)\usr\local\Tivoli\bin\w32-ix86

- (drive:)\usr\Tivoli\bin\w32-ix86

• INTERP

Specifies the platform-dependent last directory string, which is forWindows NT on Intel-based processors W32-IX86.

A possible combination of both variables, for example, could be:

• set BINDIR=C:\Tivoli\bin\w32-ix86

• set INTERP=w32-ix86

6.2.1.4 Windows NT user rights for NMC executionThe user rights on for the NetView Management Console Server to run onWindows NT must be defined if this has not already been done. The followinguser rights need to be added to the userid under which the NetViewManagement Console Server will be executed:

Act as part of the operating system.

The following steps will add the appropriate user rights under Windows NT:

1. Log on to Windows NT with Administrator authority.

2. Select Start->Programs->Administrative Tools->User Manager orStart->Programs->Administrative Tools->User Manager for Domainsfor NT Server machines.

3. Select Policies->User Rights.

4. Check the Show Advanced User Rights check box.

5. Scroll through the "Right:" selection list and choose the Act as part of theoperating system right.


6. The "Grant To:" display area will list all the groups and users currentlygranted this right. If the target userid is already listed, go to step 11,otherwise, continue.

7. Click on Add.

8. Click on Show Users.

9. Select the target userid (the one under which the NetView ManagementConsole Server will be executed) and click on Add.

10.Click on OK.

11.Log off from Windows NT and log on to Windows NT again using thetarget userid so that the rights can take effect.

6.2.1.5 Add NMC Server as Windows NT serviceTo define the NMC Server as an Windows NT service, follow these steps:

1. On the NMC Server machine, open a command window

2. Change to the following NT directory, %BINDIR%\TDS\server\bin, wherethe variable %BINDIR% could be (drive:)\usr\local\Tivoli\bin\w32-ix86,(drive:)\local\Tivoli\bin\w32-ix86, or (drive:)\Tivoli\bin\w32-ix86

3. Issue the following command to install the NMC Server as a Windows NTservice:

service account_name password

where account_name represents an account name in the form“DomainName\Userid”, and password represents the correspondingpassword for the specified account.

If the account belongs only known and specified on the local workstation,then specify “.\Userid”.

4. The NMC Server will be installed as two NT services:

- NMC topology communications server

- NMC topology server

The illustration in Figure 62 shows the successful registration examplewithin the ITSO environment.


Figure 62. NMC Server Registration as NT service

The NT service startup option will be set, by default, to manual. To changethe NT service startup option to automatic, go to the Start->Settings->Control Panel and double-click on the Services icon. Select the NMCservices and change the startup option to automatic.

6.2.1.6 Remove NMC Server as Windows NT serviceTo remove the NMC Server as a Windows NT service, follow these steps:

1. On the NMC Server machine, open a command window.

2. Change to the following NT directory, %BINDIR%\TDS\server\bin, wherethe variable %BINDIR% could be (drive:)\usr\local\Tivoli\bin\w32-ix86,(drive:)\local\Tivoli\bin\w32-ix86, or (drive:)\Tivoli\bin\w32-ix86

3. Issue the following command to remove the NMC Server as a Windows NTservice:

ihsxsrv delete

The illustration in Figure 63 shows the successful registration removeexample within the ITSO environment.

Figure 63. NMC Server Registration removal as NT service

6.2.2 Setting up NMC Topology Server for Systems AutomationThis section provides information on how to exploit the NetView ManagementConsole to issue processor operations commands and system operationscommands for selected systems, subsystems, or application groups.

System Automation for OS/390 adds a selection of predefined processoroperations commands and system operations commands to the NetView

C:\Tivoli\nmc\TDS\server\bin>service .\NMCAdm testpwTivoli environment variables configured.BINDIR..... c:\tivoli\nmc

C:\Tivoli\nmc\TDS\server\bin>ihsxsrv install manual .\NMCAdm testpw c:\tivoli\nmc\TDS\server\binIHS5977I: Topology communications server service installed successfullyIHS5977I: Topology server service installed successfullyC:\Tivoli\nmc\TDS\server\bin>

C:\Tivoli\nmc\TDS\server\bin>ihsxsrv deleteIHS5975I: Topology server service deleted successfully.IHS5975I: Topology communications server service deleted successfully.


Management Console, thus, enabling the use of the NetView ManagementConsole as a front-end interface for managing the OS/390 host environment.

The sets of available commands are provided in these correspondingresponse files.

Table 25. System Automation response files for NMC exploitation

6.2.2.1 Installing NMC enhancements for System AutomationAfter applying the PTF UW90546, install the System Automation for OS/390NMC enhancement. This will enable the user to issue the most importantSystem Automation for OS/390 processor operations and system operationscommands from all NMC workstations.

Response File Name Description

README The README directory with installationand user information

ING_NMCCHLP_HELPFILES Subdirectory including the online help filesfor the system operations commands

ING_NMCS_DDF Subdirectory including data definition filesfor the provided system operationscommands

ISQ_NMCCCHLP_HELPFILES Subdirectory including the online help filesfor the provided processor operationscommands

ISQ_NMCS_DDF Subdirectory including data definition filesfor the provided processor operationscommands

ING_NMCS_CMD.RSP Response file for system operationscommands

ISQ_NMCS_CMD.RSP Response file for processor operationscommands

If you want to add or remove commands to or from the delivered sets, youcan use the provided Command Profile Editor (CPE) from the NMC. Fordetailed information on how to use this editor, refer to the Tivoli NetView forOS/390 NetView Management Console User's Guide, SC31-8665.

Related Topics:


After performing the steps described in the remainder of this section, it is nowpossible to use the System Automation for OS/390 NMC exploitation asdescribed in the readme documentation of the packed file INGNMCZP, “Howto Issue System Automation for OS/390 Commands Using the NetViewManagement Console”.

Applying the above PTF will provide two packed files for the NetViewManagement Console Server:

• ING.SINGPWS1(INGNMCZP)

Packed file for Windows NT or OS/2 workstations. Download this file withthe extension ZIP and unpack it using common tools, such as WINZIP orPKZIP.

• ING.SINGPWS1(INGNMCTZ)

Packed file for Unix workstations. Download this file with extension theTAR.Z and unpack or uncompress it using common tools, such asuncompress and tar.

The content of each packed file is divided into support files for systemoperations commands and for processor operations commands. Eachsupport file structure contains NMC response files for system operationscommands and for processor operations commands. The response filesinclude the definitions and profiles for the following NMC extensions:

• ING_SO_OPER SystemOperation Operator

• ING_PO_OPER ProcessorOperation Operator

• ING_SA_OPER SystemAutomation Operator

ING_SA_OPER includes a definition for both the system operations andthe processor operations commands

Furthermore, there are two subdirectories for the related data definition files,two subdirectories with the online help in HTML format, as well as aPostScript file to print the documentation.

With this separation of system operations and processor operationscommands, the user may install either the system operations commands or

The installation, as described in this section, is performed on the NMCServer only. Restart the individual NMC clients to take advantage of thisenhancement.

Note


the processor operations commands, or both, depending on specificrequirements.

The installation has to be done manually, as there is no common installationtool for the several supported platforms. This requires the user be familiarwith the common commands of the workstation operating system.

To perform the installation of the System Automation for OS/390 NMCenhancements on Windows NT, follow these steps:

1. Download the appropriate packed file in binary format to the NMC Server.

2. Unpack the file into a temporary directory of the NMC Server using anappropriate tool for the NMC Server operating system.

3. Copy the required help files for Windows NT fromtmp\INGNMCEX\ING_NMCCCHLP_HELPFILES and/ortmp\INGNMCEX\ISQ_NMCCCHLP_HELPFILES to the%BINDIR%\TDS\server\db\current\help directory

4. Copy the required data definition files for Windows NT fromtmp\INGNMCEX\ING_NMCS_DDF and/ortmp\INGNMCEX\ISQ_NMCS_DDF to the%BINDIR%\TDS\server\config\ddf directory

5. Copy the required response files for Windows NT from INGNMCEX to the%BINDIR%\TDS\server\sample directory

6. Verify the following:

a. To operate the NMC Server, the user must be logged on to NetView viaa 3270 host session.

b. The NetView userid must have NGMF or NMC administrator rights.

c. The NMC Server must be started and active.

d. The connection to the NMC Server must be established by issuing theNETCONV command on the NetView console.

7. Start the Command Profile Editor Batch Utility (CPEBATCH) by eitherdouble clicking on the CPE.CMD file in the %BINDIR%\TDS\server\bin orissue one of the following commands for Windows NT:

- %BINDIR%\TDS\server\sample\ CPEBATCH ING_NMCS_CMD.RSP and/or

- %BINDIR%\TDS\server\sample\CPEBATCH ISQ_NMCS_CMD.RSP

Both commands have to be issued followed by the -i and -g parameters.


8. Start the CPE online utility, logon with a valid userid and password, andapply the new profiles to the individual operators. Profiles can also beedited from the CPE utility. For example, right clicking on object within theNMC interface displays the context menu with commands that can beissued to the object. To add or delete commands, edit the specific profileand either select an existing command or create a new command.

This step loads the provided NMC enhancements into the NMC database.It is important to save the changes before leaving the CPEBATCH utility,which is not prompted, by default, to the user.

9. On the individual NMC Clients, restart the NetView Management Consoleto reflect the NMC enhancements to the NMC Server database.

6.2.3 Starting the NMC Topology Server using TCP/IPIf using the NMC Server program icon instead of Windows NT services, thefollowing screen messages will be displayed after normal start-up of the NMCtopology communication server:

Tivoli NetView Management Console 1.3.0.0Topology Communication Server5697-B82 (C) Copyright Tivoli Systems, an IBM Company 1997, 1999.All Rights Reserved.US Government Users Restricted Rights - Use, duplication ordisclosure restricted by GSA ADP Schedule Contract with IBM Corp.Portions copyright (c) 1992 by Free Software Foundation, Inc. All rightsreserved.

Note

For information on how to use this batch utility or the list of the variousparameters, refer to Chapter 6 of the ITSO redbook Parallel SysplexAutomation: Using System Automation for OS/390, SG24-5442.

The CPE online utility is only available for Intel based platforms. Forother platforms, edit the files with a text editor.

Note

For further information about the delivered commands refer to the onlinehelp or the System Automation for OS/390 V1R3 Technical Reference,GC28-1593.

Note


---------------------------------------------------------------------IHS0248I: Topology communications server 1.3.0.0 is initialized.IHS0252I: Issue the 'tserver stop' command to end this process.IHS0208E: The SNA communications server APPC subsystem is not loaded

For the NMC topology server, the following screen messages indicate asuccessful start-up of the NMC topology server:

Tivoli NetView Management Console 1.3.0.0Topology Server5697-B82 (C) Copyright Tivoli Systems, an IBM Company 1997, 1999.All Rights Reserved.US Government Users Restricted Rights - Use, duplication ordisclosure restricted by GSA ADP Schedule Contract with IBM Corp.Portions copyright (c) 1992 by Free Software Foundation, Inc. All rightsreserved.---------------------------------------------------------------------IHS2150I: Topology server 1.3.0.0 starting.IHS2200I: Topology server 1.3.0.0 is initialized.IHS0252I: Issue the 'tserver stop' command to end this process.

System messages during NMC server operations will be displayed in the logfile ihsmessage.log located in the directory:

%BINDIR%\TDS\SERVER\LOG

If the NMC topology server and NMC topology communications server startsuccessfully, it is possible to connect to Tivoli NetView for OS/390 using theNetView NETCONV command.

For connecting NetView for OS/390 to the specific NMC server, issue thefollowing command on the NCCF command line, or preferred by an autotaskat NetView start-up:

NETCONV ACTION=START IP=<IPAddr NMC Server>

6.2.4 Uninstalling the NMC Topology ServerTo uninstall the NMC topology server on Windows NT, the following stepsneed to be executed:

Issuing the NETCONV command by EXCMD <autotask> NETCONV... willexecute NETCONV from an autotask and will assure that connectivity betweenNetView and the NMC topology server will continue even if the operatorlogs off.

Note


1. Select Start -> Control Panel to open the control panel options forWindows NT.

2. Select the Add/Remove Programs icon in the control panel.

3. Select NetView Management Console Server in the list of programsavailable under the Install/Uninstall tab, and press the Add/Removebutton.

4. The user will be prompted to see if they desire to completely remove theNetView Management Console Server and all its components. SelectingYes will remove it. Selecting No will leave the program on the computer.

5. Selecting Yes will result in a "Remove Programs From Your Computer"dialog, which shows the status of the uninstall. A message saying"Uninstall Successfully Completed" will be displayed when the uninstall isdone. Click OK to finish.

6.2.5 Hints and tips for the NMC Topology ServerThis section is intended to help with common problems in getting the NMCserver up and running. Before starting the NMC server and connecting toNetView for OS/390, make sure that all of the necessary setup steps havebeen performed.

NMC Server installation on systems running the Tivoli Framework

If the Tivoli Framework is installed on the same workstation as the intendedinstall of the NetView Management Console Server, install the NetViewManagement Console Server into the same drive and binary path as theFramework. This is required because both products use the environmentvariables BINDIR and INTERP.

It would cause one or both products to fail if different drives and directoriesare used, and BINDIR is just set to reflect the binary path of one of theproducts.

If there is no Tivoli Framework installed on the same workstation, the NMCTopology Server installation process will define the BINDIR and INTERPenvironment variables and correctly create any necessary command or shellthat may be needed.

If the server does not start and the setup_env.cmd is not found

If the setup_env.cmd file is not found, the following message is displayed,"rc(5902) setup_env.cmd not found", and no updates are placed intoihsmessage.log in this situation.


To resolve this, it may be necessary to reinstall the server. First, try to copythe setup_env.cmd file from the /BIN directory to its correct place. This wouldtypically be the directory %WINDIR%\system32\drivers\etc\Tivoli for WindowsNT. Then, edit the file to ensure that the correct information is in place for the%BINDIR% environment variable as per the above section.

If the setup_env file is found, but the bindir is not set

If the setup_env.cmd file is found, but the %BINDIR% variable is not set, thefollowing messages are issued, and neither of the DOS or AIX commandwindows will come up. Also, note that no updates are placed intoihsmessage.log. The messages are:

"Tivoli environment variables configured."

"The system cannot find the path specified."

To resolve this problem, make sure the path of the %BINDIR% environmentvariable is correct.

In Windows NT the NMC topology server starts, but then closes

If the user right "Act as part of the operating system" is not set correctly tothe appropriate userid, the NMC topology communication server will start, butthe NMC topology server will start and immediately end.

A error message "IHS2133I: The server must be run under a userid that has'Act as part of the operating system' user right. The server is ending." isplaced in the log file ihsmessage.log.

To resolve this problem, set the appropriate user rights under Windows NT tothe correct userid.

Cannot start the NT services of NMC Server at start-up

Ensure that the used userid to execute the automatic NT service start-up andWindows NT machine or domain name are not the same.

For example, logging locally on to a workstation with the machine nameNMCSRV, and the same userid, NMCSRV, is used, an error will occur atWindows NT startup indicating that the userid is not recognized as a validuserid, and the services will not start even though that same userid hasadministrative privileges allowing them to start the NMC topology server orNMC communications server manually from the NT Services.

To resolve this problem, change the userid or machine name to be different.


6.3 Setting up the NMC client workstation

This section contains information about the NetView Management Consolealso known as the NMC Topology Console. It is a Java-based clientapplication and is in cooperation with the NMC topology server applicationproviding network and systems views of the enterprise.

This section is divided into the following:

1. Installing the NMC Topology Console for Windows NT

2. Starting the NMC Console using a TCP/IP connection

3. Uninstalling the NMC Topology Console

4. Hints and tips for the NMC Topology Console

6.3.1 Installing the NMC Topology ConsoleThis section will explain, in detail, the install process and the setup procedurefor the NMC Topology Console, which is, in general, the content of theprovided Readme file EGVREAD1.ME on the NMC installation CD along withseveral situations derived from the actual install at the ITSO environment.

To install the NMC Topology Console on Windows 95, 98, or NT, use thefollowing steps:

1. To install the NMC Topology Console from CD:

a. Insert the Tivoli NetView for OS/390 CD distribution media into the CDdrive of the workstation.

b. Find the correct drive and directory that the NMC Topology Console forWindows resides on. The directory is \win32\enu or \win32\jpn, and thefile name is DUINMCCW.EXE. Running this file from the CD will startthe unpacking process.

---- or ----

1. To install the NMC Topology Console by HTTP download:

a. With any web browser, go to the following URL:http://www.tivoli.com/nv390/downloads

b. Download the Windows version of the NMC Topology Console into atemporary directory as DUINMCCW.EXE.

---- or ----

1. To install the NMC Topology Console via a download from mainframeDASD:


a. To install the NMC Topology Console from your NetView host(mainframe), please read the EGVREAD5.ME file located under/usr/lpp/netview/install on your OS/390 Unix System Services if theoptional Tivoli NetView for OS/390 FMID JPZ8454 has been installed.This install is done using the Tivoli Software Installation Servicesoftware.

2. Running the DUINMCCW.EXE file will unpack the files and invoke theInstallshield setup application.

3. To perform the install, follow these steps after entering DUINMCCW fromthe command line.

a. The following dialog will be displayed asking the user to "Select Yes tocontinue with the installation. Select No to exit the installation process".If No is selected, the process ends here. If Yes is selected, thefollowing actions will occur:

Figure 64. Install wizard for NMC Client installation

b. A Welcome dialog titled "NetView Management Console TopologyConsole 1.3.0.0 - Welcome" will be displayed as shown above.Selecting the Next button will display a "NetView Management ConsoleTopology Console 1.3.0.0 - Installation Directory" dialog on which theuser selects the directory into which the installation files are unpacked.The default directory is x:\TEMP\NMCClient, where x: is the drive onwhich Windows is installed. Selecting the Finish button will unpack thefiles and start the installation process. The user will be prompted tocreate the output directory if it does not already exist.


c. The following dialog named "Welcome" is the beginning of the NMCTopology Console setup program. Selecting Next will display the next"Information" dialog which contains the read.me file that is available forreview.

d. Selecting the Next button from the "Information" dialog will display the"Choose Destination Location" dialog. The drive may be changed but itis not recommended that the path information be modified.

The path is a standard used by Tivoli, and by the statement within theoriginal Readme file, unpredictable results in the program can occur if itis changed.

e. Selecting the Next button will display the "Setup Type" dialog. Thedefault selection will have the "Typical" radio button already selected.This will install the files available for the NMC Topology Console, butnot the "NMC Productivity Kit". This option is equivalent to the Compactoption. The Compact radio button may also be selected. This will installall of the binaries except for the "NMC Productivity Kit".

If the Custom button is selected, a "Select Components" dialog isdisplayed. Use the check boxes to manually select the componentsdesired. The choices are NMC Program Files and NMC ProductivityKit. The NMC Program Files are all the files that enable thefunctionality of the NMC Topology Console. The NMC Productivity Kitconsists of an NMC Topology Console Demo and example Javaapplications and plug-ins.

f. Selecting the Next button will display to the "Start Copying Files"dialog. This shows the setup type selected for the NMC TopologyConsole and the path it will be installed into.

g. Selecting the Next button will start to install the binaries.

h. When the binaries are installed, a "Setup Complete" dialog will bedisplayed.

Unlike previous the NMC Version 1.2, there is no need to update thePATH and CLASSPATH environment variables to define Java.

6.3.2 Starting the NMC Console using a TCP/IP connectionUse the following steps to start the NetView Management Console:

1. Make sure that the NMC Server is started and connected to the NetViewhost.

2. To use the desktop icon to start the NMC Topology Console inWindows95/98/NT, double-click on the NMC Topology Console icon on


the Windows 95/98/NT desktop or in the programs group under the Startbutton. This will display the following NetView Sign On dialog box.

Figure 65. NMC Sign On dialog box

3. Sign on to the NMC Server and NetView by entering a valid RACF useridand password. In the field labeled Host Machine, enter the IP address orIP host name of the NMC topology server.

4. Click OK to complete the logon process.

6.3.3 Uninstalling the Tivoli NMC Topology ConsoleTo uninstall the NetView Management Console on Windows, the followingsteps need to be executed:

1. Select the Start -> Control Panel to open the control panel options forWindows NT.


3. Select the NetView Management Console Topology Console 1.3.0.0 inthe list of programs available under the Install/Uninstall tab and press theAdd/Remove button.


4. The user will be prompted to see if they desire to completely remove theNMC Topology Console and all its components. Selecting Yes will removeit. Selecting No will leave the program on the computer.

5. Selecting Yes will result in a Remove Programs From Your Computerdialog, which shows the status of the uninstall. A message sayingUninstall Successfully Completed will be displayed when the uninstall isdone. Click OK to finish.

6.3.4 Hints and tips for the NMC Topology ConsoleThe most common problem encountered with the NMC Topology Console inpast releases was not having Java set up correctly. By shipping Java as partof the NMC Topology Console binaries, the majority of Java-related problemshave been eliminated.

Another problem is a partial download of NMC files from the NMC Server.This is caused when communications drop as NMC is being downloaded fromthe server it is connected to. The problem will usually manifest itself as ahang once NMC is started. This is because only part of the .jar file thatcontains most of the NMC function was downloaded. This is easy to detect bycomparing the size of the ihseuc.jar file in the \TDS\client\lib directory of NMCwith that of the ihseuc.jar file in the \TDS\server\db\current\lib directory on theserver. They should be the same size.

To resolve this, you must uninstall NMC and also delete all the directories andfiles starting from \TDS. After successful uninstall, reinstall the NMC codeand then connect to the server again.

6.3.5 Issuing SA OS/390 commands using the NMCThe NMC may be used to monitor and control large portions of the enterprise.For a description of the benefits of the NMC and how to use it, refer to theTivoli NetView for OS/390 NetView Management Console User's Guide,SC31-8665. System Automation for OS/390 exploits these benefits to let theuser issue predefined system operations and processor operationscommands from context menus. This feature is embedded into the standarduse of the NetView Management Console.

This section gives a short introduction on how to find the System Automationfor OS/390 related context menus and how to issue the commands.

The mechanism on how to provide information for graphical monitoring via theNetView Management Console can briefly be described with the followingsteps:


1. Define the automated resources, for example, Application Groups orSystems, using the System Automation for OS/390 customization dialogdescribed in Section 5.3, “Defining all systems and objects to SystemAutomation” on page 60.

2. Group the automated resources into logical Operator View using the SAOS/390 customization dialog as described in Section 5.3.3, “Entering allsystems and objects” on page 64.

3. Use the BUILD function of the System Automation for OS/390customization dialog to build the RODM load files from the objectinformation in the stored in the SA OS/390 policy database.

4. When the created RODM load files are loaded to RODM, the NetViewManagement Console retrieves the information through GMFHS fromRODM and displays the defined OperatorView on its graphical interface.

In order to start the NetView Management Console, follow these steps:

1. Make sure that the NMC Server is started and connected to the NetViewhost using the NETCONV ACTION=START IP=<ipaddress> command on theNetView NCCF interface, where <ipaddress> represents the real IPaddress of the NMC Server.

2. On the workstation, start the NetView Management Console application.From the NetView Sign On panel, shown in Figure 66, log on to NetViewusing the correct RACF user ID and password.


Figure 66. NetView Sign On dialog

3. The Tivoli NetView for OS/390 Management Console is displayed. Expandthe SA_OS/390 selection under Networking Views to get a selection ofoperator views as defined in the customization dialog.


Figure 67. NMC Console View of the Focal Point System SC66

4. Select one of the view objects, as in this example, the focal point systemSC66, to the display the contained objects and their status information.

Use the Resource Properties selection of an object context menu fordetailed object information. Depending on the type of objects displayed inthe target view, the corresponding context menus for this object type mayvary:

- For aggregate objects, such as Operator Views, Groups, ApplicationGroups, and Volume Groups, the context menu displays processoroperations commands only. For example, it is possible to issue aprocessor operations START command to an aggregate object, whichwill start processor operations on the real objects belonging to thisaggregate object.

To start a processor operations command on a single system objectfrom this aggregate view, navigate to that specific system object.


- For real objects like Applications and Systems, the context menudisplays processor operations commands and system operationscommands (assuming both NMC enhancements are installed).

The screen shown in Figure 68 illustrates the SA OS/390 context menufor a real object, the focal point system SC66.

Figure 68. NMC Context Menu of the Focal Point System SC66

5. By selecting one of the applicable commands, a corresponding dialog boxmay be displayed to specify additional parameter for the specificcommand. An example is illustrated in Figure 69 of the dialog box for theDISPSTAT command. At the bottom of this dialog box, the appropriatecommand syntax is displayed.

NetView for OS/390 allows a maximum length of 255 characters percommand. If the parameter specifications exceed this limit, a messagewill be displayed that the command cannot be executed.

Note


Figure 69. NMC dialog box for additional command parameter

6. When finished, press the Send or Send and close button to submit thecommand to NetView OS/390. The command output is displayed in theNMC Response Log. View the NMC Response Log by selecting the TearAway Log item from the Options menu.

6.4 Setting up the Web interface to Tivoli NetView OS/390

The same installation process is used for setting up the Web interface forNetView V1R3 as for NetView V1R2. For documentation on this process, referto the Tivoli redbook An Introduction to Tivoli NetView for OS/390 V1R2,SG24-5224.

This reference covers the setup of, and logging on to, a Web browser to issuecommands to NetView, as well as examples of the responses from thosecommands. In general, commands that output messages can be issued.


Fullscreen commands are generally not supported, although the commonBROWSE is supported. You can browse members of concatenated datasetsas well as the Netview log.

6.4.0.1 Enabling NetView OS/390 Web accessEnsure that the following NetView DSIPARM members are customized duringNetView setup to enable Web access and TCP/IP connectivity. For a detaileddescription on how to customize NetView for OS/390, see Section 4.3,“Network management environment” on page 33 and Section 4.4,“Automation environment” on page 39.

• DSIDMNB - DSIWBTSK task definition:

**************************************************************** NOTE: THE FOLLOWING TASK STATEMENT IS NECESSARY FOR ** NETVIEW WEB SERVER. ****************************************************************TASK MOD=DSIZDST,TSKID=DSIWBTSK,MEM=DSIWBMEM,PRI=5,INIT=Y

• DSIWBMEM - Task parameters for DSIWBMEM:

DSTINIT FUNCT=OTHER,XITDI=DSIWBINTTCPANAME = T11ATCPSOCKETS = 100PORT = 9998

It is important to specify a unique port in the DSIWBMEM member.NetView V1R3 for OS/390 is shipped with a default port of 80. If other Webservers are running, port 80 is allocated to them, and another port has tobe allocated for the NetView Web server.

The most up-to-date references to any of the Tivoli NetView for OS/390related information may be obtained from the Web at:http://www.tivoli.com/nv390

Note

If there is a problem with the TCP/IP definitions, a BNH1671 message isreturned with an error code of 48.

Note


6.5 Setting up the NetView 3270 Management Console

This section contains information on the system requirements, setup, andoperation of the NetView 3270 Management Console. The following topicswill be covered:

1. Software requirements

a. Mainframe component

b. Workstation component

2. Selecting the correct files

3. Available documentation and technical information

4. Setting up the Host (Mainframe) environment

a. Setting up DSITCPCF

b. Setting up DSITCPRF

c. DSIDMNK sample member

d. Required host environment

5. Installing NetView 3270 Console on Windows 95, 98, and NT

6. Uninstalling the NetView 3270 Console on Windows 95, 98, and NT

7. Replicating the NetView 3270 Console across multiple machines

8. Operating notes, hints, and tips

6.5.1 Software requirementsThe NetView 3270 Management Console has two components:

- Mainframe component

- Workstation component

6.5.1.1 Mainframe componentsThe mainframe component provides the host connection and has thefollowing requirements:

- OS/390 Version 1 Release 3 (5645-001) or OS/390 Version 2 Release4 (5647-A01) or higher.

- TCP/IP Version 3 Release 2 or OS/390 Version 2 Release 5 for TCP/IPcommunication between the host and its clients.

- NetView for OS/390 Version 1 Release 3 installed for the specificNetView support for the NetView 3270 Management Console.


6.5.1.2 Workstation componentThe supported client environments are OS/2, Windows NT, Windows 95 and98, AIX, Solaris, and HP-UX. This section will describe the installation forWindows only. Additional specifics for the different client platforms are:

• OS2:

The NetView Java Client requires OS/2 Version 4.0 or higher as well asOS/2 TCP/IP Version 2.0 with UN64092 or a later version. The NetViewJava Client must be installed in an HPFS partition.

• Windows 95, 98, and NT:

The NetView Java Client requires Windows 95, 98, or NT 4.0 with TCP/IPsupport installed.

• AIX:

The NetView Java Client requires IBM AIX Version 4.2.0 or higher.

6.5.2 Selecting the correct filesTo install the NetView 3270 Management Console on Windows 9x and NTfrom the NetView host (mainframe) or CD via the Tivoli Software InstallationService, please read the EGVREAD5.ME file located under/usr/lpp/netview/install on the OS/390 Unix System Services, if Tivoli NetViewfor OS/390 FMID JPZ8454 has been installed, or under README/ENU on theTivoli NetView for OS/390 CD.

To install the NetView 3270 Management Console on Windows 9x and NT,using methods other than the Tivoli Software Installation Service, continuewith the following instructions.

The correct files to install are located in the Tivoli NetView for OS/390 CDdistribution media under the directory \WIN32 for the Windows 95, 98, and NTNetView 3270 Management Console. The actual files will be in a subdirectoryspecific to the appropriate language support. The English version of NetView3270 Management Console will be in \ENU (or /ENU).

The previous NetView release, V1R2, required that a Java DevelopmentKit (JDK) be downloaded and defined. Since NetView release V1R3, theJava support is integrated into the binaries so that there is no need toobtain Java support separately.

Note


The following file is distributed as part of the NetView 3270 ManagementConsole:

• FLB4WIN.EXE - This package contains the NetView 3270 ManagementConsole in a self-extracting unzip file for Windows 95, 98, and NT, which isfound on the CD and the Web.

6.5.3 Available documentation and technical informationInformation is available in HTML format, which you can view using a Webbrowser. Within the HELP subdirectory of the IBMFLB directory, there are:

• FLBHLP.HTM - Contains help information for the NetView 3270Management Console. This file is the top of the help HTML tree and isinstalled with the program files.

• FLBDPD.HTM - Contains problem determination information and isinstalled with the program files.

6.5.4 Setting up the host (mainframe) environment• Ensure that TCP/IP 3.2 for MVS or OS/390 V2R5 or higher with TCP/IP is

installed and operational on the OS/390 host.

• Ensure that the following DSIPARM and DSIPRF members have beencreated:

- DSITCPCF - Task parameters for DSITCPIP in DSIPARM

- DSITCPRF - TCP/IP logon encryption profiles in DSIPRF

- DSIDMNK - TCP/IP logon encryption profiles in DSIPRF

After creating the DSIPARM and DSIPRF members, NetView 3270Management Console access is enabled when NetView is started.

6.5.4.1 Setting up DSITCPCFAdd the following definitions to member DSITCPCF in DSIPRF:

- TCPANAME specifies the name of the TCP/IP address space(TCPIP32 procedure). For example:

TCPANAME=TCP32

- PORT defines the port on TCP32 on which NetView waits forconnection requests. The port is also used by the NetView 3270Management Console to specify the NetView that will receive aconnection request. Valid values are 1-65535. The default is 9999. Forexample:

PORT=9999


- SOCKETS defines how many users can log on to NetView usingTCP/IP. TCP/IP reserves a minimum of 50 sockets; so, numbers lessthan 50 are not used. Valid values are 50-1000. The default is 50. Forexample:

SOCKETS=50

- TIMEOUT defines how many seconds elapse before a request timesout. The default value is 3,600. For example:

TIMEOUT=60

- DIAGNOSE creates additional debugging messages in the log. SpecifyNO unless otherwise instructed by the Tivoli Support Center forproblem diagnosis. For example:

DIAGNOSE=NO

6.5.4.2 Setting up DSITCPRFMember DSITCPRF in DSIPRF defines encryption keys for each operator.The operator ID is followed by a colon and any number of blanks. The firstnon-blank field is the encryption key for the data flowing from the NetView3270 Management Console to NetView (command flow). The secondnon-blank field is the encryption key from NetView to the NetView 3270Management Console. The length of the keys can be in the range of 1-8characters. Using an 8-character key is recommended. Use the same keys todefine the NetView 3270 Management Console. It does not send the keys onany session. Place DSITCPRF in a secure (DSIPRF DD) library.

If both keys are "default", in lowercase, NetView uses a default encryptionkey. The default key is the same for any session but is not a published value.The default key provides encryption protection. Do not use "default" for onlyone of the encryption keys because NetView interprets this as a definitionerror.

If both keys are "disabled", in lowercase, encryption is not used. Specify"disabled" for debugging session problems in low-risk networks. Do not use"disabled" for only one of the encryption keys because NetView interprets thisas a definition error.

Define a NetView operator ID the same as existing IDs. As a security benefit,only operators defined in this file can log on to NetView using a NetView 3270Management Console. For example, if DSITCPRF only contains the followingstatement, a logon attempt from a NetView 3270 Management Console usingOPERX results in the message, "DSI029I: INVALID LOGON ATTEMPTFROM TERMINAL terminal, ERROR IN THE 'n' FIELD":


OPER1: default default

The following statement enables a NetView 3270 Management Console to logon as OPERX with no encryption:

OPERX: disabled disabled

Encryption keys can be mixed case. Choose random, printable, non-blankcharacters, such as:

OPER4: a1s2d3f4 lpmonibu

Specify the keyword ANY_OTHER to define a single set of keys that is usedby operators who are not defined in the DSITCPRF member. For example, toset up universal access with a single statement, specify:

ANY_OTHER: default default

6.5.4.3 DSIDMNK sample memberMember DSIDMNK in DSIPARM should include the following task definition:

TASK TSKID=DSITCPIP,MEM=DSITCPCF,MOD=DSITCPIP,PRI=6

6.5.4.4 Required host environmentThe following conditions must exist at the host environment to enable theNetView 3270 Management Console:

1. The host TCP/IP must be started each time the system is IPLed. To startTCP/IP after you IPL the system, issue an MVS command similar to:

S TCPIP32.TCP32

For further information, refer to the OS/390 TCP/IP OpenEdition User’sGuide, GC31-8305. The start-up profile is in TCP32.PROFILE.TCPIP.

2. NetView for OS/390 and the DSITCPIP optional task must be running. Thefollowing command can be used to start the optional task:

START TASK=DSITCPIP

START TASK=DSITCPIP,MOD=DSITCPIP,MEM=DSITCPCF,PRI=6

The second form is used if the TASK statement is not in the DSIDMNmember(s) and if the operator has security authorization for the START

command keywords used above.

6.5.5 Installing NetView 3270 Console on Windows 95, 98, and NTThis section will explain, in detail, the install process and the setup procedurefor the NetView 3270 Management Console, which is, in general, the contentof the provided Readme file FLBREAD1.ME on the NMC installation CD,


along with several situations derived from the actual install at the ITSOenvironment.

To install the NetView 3270 Management Console on Windows 95, 98, or NT,follow these steps:

1.To install the NetView 3270 Management Console from CD:

a. Insert the Tivoli NetView for OS/390 CD distribution media into the CDdrive of your workstation.

b. Find the correct drive and directory that the NetView 3270Management Console for Windows resides on. The directory is\win32\enu or \win32\jpn and the file name is FLB4WIN.EXE. Runningthis file from the CD will start the unpacking process.

---- Or ----

1. To install the NetView 3270 Management Console by HTTP download:

a. With any Web browser, go to the following URL:http://www.tivoli.com/nv390/downloads

b. Download the Windows version of the NetView 3270 ManagementConsole into a temporary directory as FLB4WIN.EXE.

---- Or ----

1. To install the NetView 3270 Management Console via a download frommainframe DASD:

a. To install the NetView 3270 Management console from the NetViewhost (mainframe), please read the EGVREAD5.ME file located under/usr/lpp/netview/install on your OS/390 Unix System Services if theoptional Tivoli NetView for OS/390 FMID JPZ8454 has been installed.This install is done using the Tivoli Software Installation Servicesoftware.

2. Select the directory that will be the root directory for the console programdirectory tree as the current directory. For example, if directory E:\ is thecurrent directory, the NetView 3270 Management Console program willexpand into a directory structure with the directory tree ofE:\usr\local\Tivoli\bin\generic_unix\TDS\ibmflb. This can be on a LANdrive so that many users share a common copy of the program. Individualsettings files are created later in the installation on local disks for eachuser.

3. Unpack the files by running the FLB4WIN.EXE self-extracting EXE file. Itwill prompt the user for the directory to unpack the files into with the


default being x:\TEMP\NMC3270, where x: is the system drive, and invokethe Installshield setup wizard. Erase the FLB4WIN.EXE file when satisfiedthat the installation has been successful. This file is not used by the rest ofthe installation process or the NetView 3270 Management Consoleprogram.

4. FLB4WIN.EXE will automatically invoke the Installshield program, whichwill install all of the files for the NetView 3270 Management Console andcreate a desktop entry to configure NetView 3270 Management Console.bat files. Simply follow the dialogs presented by the Installshield program(SETUP.EXE) to perform the install, click on the desktop icon, and selectConfigure the NetView 3270 Management Console. This will bring upthe console installation screen shown in Figure 70.

Figure 70. NetView 3270 Console setup screen

5. The FLBINST.BAT command file will ask for information, which must beentered in order to successfully connect NetView 3270 ManagementConsole to NetView OS/390. Explaining information is provided to guide inthe entering of information. The following list is a brief summary:

a. A unique name, such as an operator ID, that will be used as the batchfile name. The batch file, for example, oper1.bat, is created in the datadirectory you specify for the settings files.


b. The IP host name for the mainframe TCP/IP stack.

c. The IP port number for the mainframe TCP/IP stack.

d. The inbound and outbound encryption keys for the session.

e. The directory path for the user settings data and batch command files,for example, E:\MYDATA.

Special Cases:

1. If the path specified is already being used by your other sessions,the settings are shared among all sessions.

2. To separate settings for some of the sessions, use a separatedirectory for each case.

3. The installation process will create the data directories if they do notalready exist.

4. Since the batch files created in this directory contain encryptionkeys, ensure security protection of the disk, directory, and files.Typically, a local directory, not one on the LAN accessed by others,should be used.

f. The size of the display area should be equivalent to a 3270 screen.Possible values are (rows x characters):

• 0 for 24x80

• 1 for 32x80

• 2 for 43x80

• 3 for 32x132

To find the IP port number and IP host name being used by themainframe TCP/IP stack, log on to NetView and type the followingcommand:

LIST DSITCPIP

This will produce a response similar to the following:

TYPE: OPT TASKID: DSITCPIP TASKNAME: DSITCPIP STATUS: ACTIVEMEMBER: DSITCPCFHOSTNAME=tcphost HOSTID=1.2.3.4 PORT=9999LOADMOD: DSITCPIPTask Serial: 14END OF STATUS DISPLAY

Note


6. To set up program shortcuts for the 3270 Management Console:

a. Create a shortcut of FLBINST.BAT on the desktop using drag and dropfrom a view of its containing folder. For example, if installing to E:\, thepath and file is:E:\usr\local\Tivoli\bin\generic_unix\TDS\ibmflb\flbinst.bat.

b. Create a shortcut for the oper1.bat on the desktop using drag and dropfrom a view of its containing folder. For example, if the data directory isE:\MYDATA, and the name is oper1, the path and file is:E:\MYDATA\oper1.bat.

c. To start the NetView 3270 Management Console or installationprogram, click on the shortcut.

7. To start the NetView 3270 Management Console from a DOS commandwindow:

a. Select the data directory as the current directory, for example

CD E:\MYDATA.

b. Type the filename of the batch file and press Enter. For example:

OPER1.BAT

6.5.6 Uninstalling the NetView 3270 ConsoleThese uninstall procedures assume that new and unique names for thedirectories to store the NetView 3270 Management Console program and the(separate) data file directory structure have been selected. Avoid deleting thedirectories that are shared with other people or which have other data inthem. Check the contents of the directories carefully. If in doubt, back up thesystem first. Removing all of the files will typically free less than 20 MB of diskspace.

To uninstall the NetView 3270 Console on Windows the following steps needto be executed:

1. Select the Start -> Control Panel to open the control panel options forWindows NT.


To re-create the files in the data directory, rerun the installationprocedure to re-create missing directories or files in the data directory.

Note


3. Select the NetView 3270 Management Console in the list of programsavailable under the Install/Uninstall tab and press the Add/Removebutton.

4. The user will be prompted to see if they desire to completely remove theNetView 3270 Management Console and all its components. SelectingYes will remove it. Selecting No will leave the program on the computer.

5. Selecting Yes will result in a Remove Programs From Your Computerdialog, which shows the status of the uninstall. A message saying"Uninstall Successfully Completed" will be displayed when the uninstall isdone. Click OK to finish.

6.5.7 Replicating the NetView 3270 ConsoleA NetView 3270 Management Console can be set up on one machine andthen duplicated across multiple machines. This involves running the setupprogram and customizing the NetView 3270 Management Console and thencopying setup files created during the process to other machines. Thefollowing files need to be copied:

1. Batch or shell files created by the setup process (NT and Unix)

After running the TaskGuide setup wizard, which allows the user to specifysetup parameters, such as IP host name, IP port, encryption keys, andterminal type, a batch or shell file is created with a name supplied duringthe setup process. This file can be copied to another machine with theconsole program installed and then executed, thus eliminating the need forrunning the setup wizard on the target machine.

Note that the setup wizard asks for the name of a data directory on thelocal machine where data files will be stored. This local directory shouldalso be created on the target machine.

To duplicate the NetView 3270 Console on multiple machines, copy theIBMFLB folder containing the NetView 3270 files from the following pathfrom the source workstation machine to the same path on the targetworkstation:

(drive):\usr\local\tivoli\bin\generic_unix\TDS\ibmflb

The batch file created on the source workstation (for example,OPER1.bat) can then be copied to the target workstation.

Modify the copied batch file to ensure the path points to the IBMFLB folderon the target workstation, as in the example below, and that the IP hostname, IP port, and encryption keys are set to their correct values,respectively. The following example illustrates how such a batch file looks:


2. Configuration file

The data directory specified for the NetView 3270 Management Consolecontains a file called FLB_CONFIGURATION. This file maintains a list offull-screen sessions available to the console program along with font,color, key remapping, and session option information for each full-screensession. This file should be copied to the data directory of the targetmachine. It is a binary file and does not contain editable information. Itscontents created and modified by the NetView 3270 Management Consoleprogram.

6.5.8 Operating notes, hints, and tipsThe following provides operating hints and tips:

• When switching screens, click on the screen area containing the inputarea before typing in data, or press Enter.

• On some platforms, click on the tab areas to refresh the screen if icons arenot redrawn.

• If experiencing slow response time while running multiple, full-screenapplications, try running the applications in either one or fewer, full-screensessions. If possible, run multiple applications in one session. Use theNetView ROLL command to switch between them.

• If the environment runs with the LOGONPW command enabled, it is stillrequired that you log on to the NetView 3270 Management Console.

@REM NetView 3270 Management Console BAT file@SETLOCAL@C:@CD \usr\local\Tivoli\bin\generic_unix\TDS\ibmflb@SET JAVAPATH=..\..\..\w32-ix86\Tds\java@%JAVAPATH%\bin\jre -mx48M -ms16M -classpath .;.\jars\tivflb13.jar;%JAVAPATH%\lib\rt.jar; ...

... %JAVAPATH%\lib\i18n.jarsrc.ibmflb.FLB_NVClient 9999 tcphost.host.com ...

... BUFR NODIAG DEFAULT DEFAULT C:\MYDATA 3@ENDLOCAL

It is important to ensure that the values in the batch file are identical incase and character to those in the DSITCPRF member. For example, if themember defines the values as “default default”, and they are set to“DEFAULT DEFAULT” in the batch file, the console will start but willproduce unreadable text on the screen.

Note


• When installing the NetView 3270 Management Console in a UNIXenvironment, close your terminal window after installing the client andthen open another terminal window to run the client.

• Environment space errors in Windows 95 and 98. It might be possible thatthe batch files used to set up and launch the NetView 3270 ManagementConsole may require additional environment space. This can be adjustedvia the memory properties setting for MSDOS windows or through theshortcut icons.

• Screen corruption on scrollable panels. Panels with scrollbars may showscreen corruption when moving the scrollbar. Manipulating the scrollbarsfor a few seconds will clear up this condition.

• Out of memory errors on Windows 95. Opening a large number offull-screen sessions (typically, greater than 15) on Windows 95 may causeout of memory errors. Increasing the amount of memory on the machinemay help this problem.



Chapter 7. Maintenance of Tivoli NetView and System Automation

This chapter contains directions and tips for an optimized maintenance of theautomation features of Tivoli NetView and System Automation, which willinclude the AUTOMAN maintenance panels and performance issues for theautomation table structure.

7.1 Automation table maintenance using AUTOMAN

One of the various functions AON provides are the AUTOMAN maintenancepanels for servicing a single or multiple NetView automation tables. Thefollowing section describes how the AUTOMAN function can be enabled in theSystem Automation NetView and introduces the AUTOMAN functionality.

The AUTOMAN maintenance panels and the AON inform policy functions,further described in Section 9.3, “Using NetView AON inform policies bySystem Automation” on page 214, can be implemented on a SystemAutomation NetView without having to install any other AON code orfunctions.

7.1.1 Enabling the AUTOMAN function for the Automation NetViewTo enable the AUTOMAN function for the automation environment, theAutomation NetView start-up procedure and three members of the DSIPARMlibrary have to be modified to include the necessary AON library datasets andcommands.

7.1.1.1 Modifying the Automation NetView start-up procedureThe following changes to the Automation NetView start-up procedure need tobe performed in order to use AUTOMAN:

1. STEPLIB:

Add NETVIEW.V1R3M0.SZELLINK to the STEPLIB concatenation so thatAUTOMAN modules can be called in the Automation environment.

//STEPLIB DD DSN=&SQ2..SINGMOD1,DISP=SHR// DD DSN=&SQ1..CNMLINK,DISP=SHR// DD DSN=NETVIEW.V1R3M0.SEZLLINK,DISP=SHR// DD DSN=&SQ1..SEKGMOD1,DISP=SHR

2. DSICLD:

Add NETVIEW.V1R3M0.SEZLCLST to CLIST library so that operators canexecute AUTOMAN commands from NCCF panel of the AutomationNetview environment.


//DSICLD DD DSN=&Q1..&DOMAIN..CNMCLST,DISP=SH// DD DSN=&SQ2..SINGNREX,DISP=SHR// DD DSN=&SQ1..CNMCLST,DISP=SHR// DD DSN=NETVIEW.V1R3M0.SEZLCLST,DISP=SHR

3. DSIPNL1:

Add NETVIEW.V1R3M0.SEZLPNLU to PANEL library, so all AUTOMANpanels can be displayed when the AUTMAN command is issued in theAutomation NetView environment.

//CNMPNL1 DD DSN=&SQ2..SINGNPNL,DISP=SHR// DD DSN=&SQ1..CNMPNL1,DISP=SHR// DD DSN=NETVIEW.V1R3M0.SEZLPNLU,DISP=SHR// DD DSN=&SQ1..SEKGPNL1,DISP=SHR

7.1.1.2 Update the Automation DSIPARM libraryCopy the member DSICMDM from the NetView install library,NETVIEW.V1R3M0.DSIPARM, to the common automation NetView DSIPARMlibrary NETVIEW.SYSTEM.DSIPARM, and modify the member DSICMDM byuncommenting the statement %INCLUDE EZLCMDI.

After this modification, restart the Automation NetView, and the AUTOMANfunctions are enabled and available within the Automation NetView.

7.1.2 Using AUTOMAN commandAn automation table is made up of many included members. The automationtable management (AUTOMAN) enables manipulation of individual or multiple

Several AON functions such as INFORM, AUTOMAN, TIMER, SMTP emailand TCP/IP commands can be run without other AON automation functionsbeing active. The above steps will enable all of these functions.

The AON TIMER functions and the SA/390 TIMER functions cannot runsimultaneously in the same operating system environment. The default is theAON TIMER function.

Refer to Tivoli NetView for OS/390 Automated Operations Network UsersGuide, GC31-866, for further details.

For further detailed compatibility information and the latest System AutomationAPAR for NetView V1R3 toleration refer to Chapter A, “NetView 1.3 tolerationfor System Automation 1.3” on page 231.

Note


automation tables through a full-screen panel interface, also enablingchanges to selected tables or changes that have an affect on all automationtables.

The AUTOMAN command manages loading of tables, displays BEGIN/ENDstructures, and helps in several other useful ways, but it does not assist increating automation table statements. Using AUTOMAN is a convenient wayto perform actions against the automation tables without having to rememberthe AUTOTBL command syntax. The AUTOMAN panels may look similar toAON, but are easily accessible from the NetView NCCF interface.

For some of the AUTOMAN functions, there are LISTING members producedwithin the DSILIST dataset. These LISTING files may also be created withnative AUTOTBL commands, but it is not necessary to remember a stack ofparameters. Using AUTOMAN, this information, and all the parameters, isincluded.

The AUTOMAN command integrates AUTOTBL, AUTOCNT, and otherNetView AON functions, which makes it a panel-driven tool of ease andconvenience.

The key functions AUTOMAN provides include:

• Display function

• Insert Function

• Enable/Disable function

• Reload/Unload function

From the NetView NCCF interface, simply enter the AUTOMAN command. Itwill start the main menu of the AUTOMAN tool as shown in Figure 71 on page158.

Chapter 7. Maintenance of Tivoli NetView and System Automation 157

Figure 71. Automation Management Tool AUTOMAN

AUTOMAN initially displays all loaded tables in their correct order. Each tableon the panel is able to be addressed and edited by moving the cursor.

On the main menu of AUTOMAN, the predefined PF keys displayed at thebottom of the panel are used for the desired functions. Select an automationtable to work with and press PF4 for commands to that automation table, orselect PF10 to act on all automation tables to make global changes.

In the ITSO project example, the automation table, AOFMSG01, is selected,and by pressing PF4, the specific command menu is displayed as shown inFigure 72.

EZLK8500 AUTOMATION TABLE MANAGEMENT

AUTOMATION TABLE Enter any character in the selection fieldsSEL POS NAME STATUS MARKERS TASK DATE TIME_ 1 AOFMSG01 ENABLED AUTO1 12/07/99 16:45:47_ 2 AOFTST01 ENABLED GAO 12/09/99 12:21:39_ 3 DSITBL99 ENABLED GAO 12/09/99 12:22:01

Command ===>F1=Help F2=Main Menu F3=Return F4=Commands F5=Refresh F6=RollF7=Backward F8=Forward F9=Responses F10=Global Commands F12=Cancel


Figure 72. Commands Menu of AUTOMAN

The available command actions are as follows:

• DISABLE automation table

• ENABLE automation table

• RELOAD automation table

• TEST statement syntax of automation table

• INSERT a new automation table in active list

• DISPLAY every information about automation table

AUTOMAN is very beneficial for easily reloading a table that has beenchanged without having to remember the exact AUTOTBL command syntax.

7.1.2.1 AUTOMAN display functionAUTOMAN provides very strong display functionality on automation tables,including:

• Simple automation table without INLCUDEs

• Detail automation table with all INLCUDEs

• Synonyms of automation table

• Automation table utilization report

• Listing file on DSILIST

EZLKATBC AUTOMATION TABLE MANAGEMENT

AUTOMATION TABLE Enter any character in the selection fieldsSEL POS NAME .................................................../ 1 AOFMSG01 : COMMANDS (Choose a highlighted command option) :_ 2 AOFTST01 : :_ 3 DSITBL99 : 8 1 -ENABLE the selected tables :

: 2 -DISABLE the selected tables :: 3 -RELOAD the selected tables :: 4 -TEST the selected tables :: 5 -ENABLE/DISABLE parts of the :: selected tables :: 6 -UNLOAD selected tables :: 7 -INSERT a table :: 8 -DISPLAY options :: :: Enter=Execute Command F3 or F12=Cancel ::.................................................:

Command ===>F1=Help F2=Main Menu F6=Roll


To display information about automation table AOFMSG01, select theDISPLAY option by entering 8 from commands menu. This option will displaythe following DISPLAY menu as shown in Figure 73.

Figure 73. AUTOMAN display menu for INCLUDE structure

Using AUTOMANs DISPLAY function, any information about the automationtable can be selected and browsed.

For example, to review the INCLUDE structure of AOFMSG01, select 3 fromDISPLAY menu, and the INCLUDE structure list of AOFMSG01 will bedisplayed as shown in Figure 74 on page 161.

EZLKATLD AUTOMATION TABLE MANAGEMENT


.............................................................: DISPLAY OPTIONS (select option and press ENTER) :: :: 3 1 - Browse table with includes 8 - Browse listing :: 2 - Browse table without includes :: 3 - Display INCLUDE structure :: 4 - Display synonyms :: 5 - Display labels/blocks/groups :: 6 - Display disabled statements :: 7 - Display AUTOCNT statistics ::...........................................................:

Command ===>F1=Help F2=Main Menu F3=Return F6=Roll

F12=Cancel


Figure 74. %INCLUDE structure for automation table AOFMSG01

In addition to automation table structure information, the ability to collectutilization or statistics information about automation tables by using theAUTOCNT function is included in the AUTOMAN commend menu.

In the ITSO example, to display the automation table utilization ofAOFMSG01, option 7 from the DISPLAY menu was selected.

Figure 75. Display menu for AUTOCNT

CNMKWIND OUTPUT FROM %INCLUDE STRUCTURE DISPLAY LINE 0 OF 22*------------------------------- Top of Data --------------------------------*AOFMSG01 PRIMARY TABLE

AOFMSGSYAOFMSGGWAOFMSGSTAOFMSGTSAOFMSGMSAOFMSGHIAOFMSGBLAOFMIOAOFMNETVAOFMSGGNAOFMVTAMAOFMAPPCAOFMMVSAOFMJES2AOFMJES3AOFMTSO

TO SEE YOUR KEY SETTINGS, ENTER 'DISPFK'CMD==>

EZLKATLD AUTOMATION TABLE MANAGEMENT


.............................................................: DISPLAY OPTIONS (select option and press ENTER) :: :: 7 1 - Browse table with includes 8 - Browse listing :: 2 - Browse table without includes :: 3 - Display INCLUDE structure :: 4 - Display synonyms :: 5 - Display labels/blocks/groups :: 6 - Display disabled statements :: 7 - Display AUTOCNT statistics ::...........................................................:

Command ===>


The AUTOCNT statistics report panel is displayed in Figure 76.

Figure 76. AUTOCNT statistics report of AOFMSG01

The AUTOCNT report will be described in more detail in Section 7.2, “Netviewand automation table optimization for performance” on page 166.

More information about automation tables may be obtained by selecting otheritems from the DISPLAY menu of AUTOMAN.

7.1.2.2 AUTOMAN Insert FunctionAn automation table is easily inserted into the list of active automation tablesand is put in the correct position by using the AUTOMAN menu.

The following example shows how to insert the new automation table,AOFTST02, into AUTOMANs active tables list. Continue to select the mainautomation table, AOFMSG01, and choose option 7 from the commandsmenu as shown in Figure 77 on page 163.

CNMKWIND OUTPUT FROM AUTOCNT STATISTICS LINE 0 OF 374*------------------------------- Top of Data --------------------------------*DWO800I AUTOMATION TABLE MSG DETAIL REPORT BY GAO-----------( AOFMSG01/AOFMS292 MESSAGE DETAILS 12/03/99 00:00:20 )------------GAO COMPLETED INSERT FOR TABLE #1: AOFMSG01 AT 12/02/99 23:41:14

|-- PERCENTAGES --|STMT L SEQUENCE NUMBER/ MEMBER COMPARE MATCH E C A D MATCH/ COMP/ MATCH/NUMB I LABEL NAME NAME COUNT COUNT C I I I COMP TOTAL TOTAL-------------------------------------------------------------------------------MEMB AOFMSG01MEMB AOFMSGSY0051 S 00087000 AOFMSG01 110 110 0 X X 100.0 100.0 100.00052 S 00105000 AOFMSG01 110 0 0 0.0 100.0 0.00053 S 00113000 AOFMSG01 0 0 0 -.- 0.0 0.00054 S 00121000 AOFMSG01 0 0 0 -.- 0.0 0.00055 S 00129000 AOFMSG01 0 0 0 -.- 0.0 0.00056 S 00137000 AOFMSG01 0 0 0 -.- 0.0 0.00057 S 00145000 AOFMSG01 0 0 0 -.- 0.0 0.0MEMB AOFMSGGW0059 S 00037630 AOFMSGGW 110 0 0 0.0 100.0 0.00060 S 00041590 AOFMSGGW 110 0 0 0.0 100.0 0.00061 S 00051490 AOFMSGGW 110 95 0 86.4 100.0 86.4TO SEE YOUR KEY SETTINGS, ENTER 'DISPFK'CMD==>


Figure 77. Command menu for INSERT of an automation table

The INSERT function is called, and the following Table Insert panel isdisplayed.

Figure 78. Table Insert panel for an automation table



: 2 -DISABLE the selected tables :: 3 -RELOAD the selected tables :: 4 -TEST the selected tables :: 5 -ENABLE/DISABLE parts of the :: selected tables :: 6 -UNLOAD selected tables :: 7 -INSERT a table :: 8 -DISPLAY options :: :: Enter=Execute Command F3 or F12=Cancel ::.................................................:


F12=Cancel

EZLKATBI AUTOMATION TABLE MANAGEMENT

AUTOMATION TABLE INSERT PANEL (Press Enter to process INSERT request)

Preceding Table Focus Table AT= 1 Next Table---------------------- ---------------------- ----------------------N/A AOFMSG01 AOFTST01

SELECT INSERT OR TEST OPTION

2 1 - AT(DEFAULT) Table Name AOFTST02 (Required)2 - AFTER Listing Name AUTOM876 Default listing name3 - BEFORE (names can be reused,4 - REPLACE but cannot be in use5 - FIRST by another table)6 - LAST SELECT A MARKER OPTION

OR7 - AUTOTBL TEST Enter your own marker

Command ===>F1=Help F3=Return F6=Roll

F12=Cancel


The exact automation table position can be controlled by key parameter asshown in Figure 78 on page 163. Several options to determine where the newautomation table is to be inserted are available. In this example, the AFTERoption 2 is chosen, and the new AOFTST02 will be inserted after AOFMSG01and before AOFTST01.

In addition, it would be possible to test the new automation table and itsresults of insertion by selecting the AUTOTBL TEST option 7.

After the new automation table, AOFTST02, is inserted into the activeautomation table list, this list in displayed to the user as demonstrated inFigure 79.

Figure 79. Updated automation table list of AUTOMAN

7.1.2.3 AUTOMAN Enable/Disable functionThe AUTOMAN function of enabling or disabling is not limited to theautomation table as a whole member but, instead, can operate on variousrange levels of the automation table. Based on its structure, AUTOMAN canperform Enable/Disable action on statements, blocks, labels, groups, or entireautomation tables.

As an example, the following scenario details the Enable/Disable function foronly a part of the AOFMSG01 automation table. By selecting the specificautomation table, AOFMSG01, and option 5 from the commands menu, asshown in Figure 80 on page 165, the automation table statement selectionpanel will be displayed as illustrated in Figure 81 on page 165.

EZLK8500 AUTOMATION TABLE MANAGEMENT

AUTOMATION TABLE Enter any character in the selection fieldsSEL POS NAME STATUS MARKERS TASK DATE TIME_ 1 AOFMSG01 ENABLED AUTO1 12/07/99 16:45:47_ 2 AOFTST02 ENABLED GAO 12/09/99 12:27:44_ 3 AOFTST01 ENABLED GAO 12/09/99 12:21:39_ 4 DSITBL99 ENABLED GAO 12/09/99 12:22:01

Command ===>F1=Help F2=Main Menu F3=Return F4=Commands F5=Refresh F6=RollF7=Backward F8=Forward F9=Responses F10=Global Commands F12=Cancel


Figure 80. Commands menu for Enable/Disable function

AUTOMAN defines various function keys for every range, for example, group,block and statement as displayed in Figure 81.

Figure 81. Enable/Disable Selection panel


AUTOMATION TABLE Enter any character in the selection fieldsSEL POS NAME .................................................../ 1 AOFMSG01 : COMMANDS (Choose a highlighted command option) :_ 2 AOFTST02 : :_ 3 AOFTST01 : 5 1 -ENABLE the selected tables :_ 4 DSITBL99 : 2 -DISABLE the selected tables :

: 3 -RELOAD the selected tables :: 4 -TEST the selected tables :: 5 -ENABLE/DISABLE parts of the :: selected tables :: 6 -UNLOAD selected tables :: 7 -INSERT a table :: 8 -DISPLAY options :: :: Enter=Execute Command F3 or F12=Cancel ::.................................................:


F12=Cancel

EZLKENDI AUTOMATION TABLE MANAGEMENT More: - +

AUTOMATION TABLE (Place cursor on statement and select action)MEMBER LVL STATEMENTAOFMSG01 001 ALWAYS SYSLOG(N) NETLOG(Y) DISPLAY(Y) CONTINUE(Y);AOFMSG01 001 IF MCSFLAG(6) = '1' THEN BEGIN;AOFMSG01 002 IF SYSID¬='SC66' & MSGID = 'AOF' . THEN DISPLAY(N) NETLOG(N);AOFMSG01 002 IF TASK='PPT' & MSGID = 'AOF' . THEN DISPLAY(N) NETLOG(N);AOFMSG01 002 IF ATTENDED='1' & DISTAUTO='0' & AUTOTASK='1' THEN DISPLAY(N)AOFMSG01 002 NETLOG(N);AOFMSG01 002 IF MSGID = 'AOF' . & IFRAUSDR ¬= 'SC66ASIR' THEN DISPLAY(Y)AOFMSG01 002 NETLOG(N);AOFMSG01 002 IF IFRAUSDR¬='SC66ASIR' THEN DISPLAY(Y) NETLOG(Y);AOFMSG01 002 END;******** 001 START OF AOFMSGGWAOFMSGGW 001 IF MSGID = 'GWREQ' THEN DISPLAY(Y) NETLOG(N) SYSLOG(N);AOFMSGGW 001 IF MSGID = 'ROUTE' THEN DISPLAY(Y) NETLOG(Y) SYSLOG(N);Command ===>F1=Help F2=Main Menu F3=Return F4=EnableF5=Display Group/Block F6=Roll F7=Backward F8=ForwardF9=Disable Stmt/Member F10=Disable Block F11=Disable Group F12=Results


Select the appropriate group, block, or statement within the automation table,and press the specific function key to enable or disable the selected area.

For example, to disable a statement, place the cursor onto the prefix of thatstatement and press PF9, which will change the color of that statement. Thefollowing message will be displayed indicating that the action has completedsuccessfully:

EZL919I ALL ACTIONS SUCCESSFULLY COMPLETED

7.2 Netview and automation table optimization for performance

This section provides basic tuning considerations to improve general NetViewand automation table performance. Basics rules and hints will be given tohelp the NetView program and its network and automation environmentachieve a certain performance level in areas, such as response time,resource utilization, and data throughput.

7.2.1 NetView automation tableSince the NetView automation table is searched sequentially from top tobottom, a thoughtful automation table design and structure will provide asubstantial performance improvement.

Automation of system and network messages and MSUs is accomplishedwith automation table statements, such as IF-THEN, BEGIN-END, ALWAYS,SYN, and %INCLUDE within the NetView automation table, which is activatedby the AUTOTBL command. Messages and MSUs are passed through theactive NetView automation table structure to sequentially search one or moreof the above automation table statements that indicate actions to beperformed for that individual message or MSU.

The following sections describe basics guidelines for a reliable automationtable design and structure.

7.2.1.1 BEGIN/END statementsBEGIN/END statements provide a logical segmentation of the automationtable, reducing the number of automation statements that must be scanned.Automation tables should be designed so that each message prefix (such asDSI), each MSU major vector (such as major vector X'0000'), and specificsubvectors have BEGIN/END sections.

If BEGIN/END sections are dedicated to the specific message and MSUclasses, the number of statements that must be scanned is by far smaller


than all IF-THEN and ALWAYS statements to be scanned. If each messageclass has its own unique BEGIN/END section, placing ALWAYS statementsas the last ones in a section prevents the automation table from beingscanned further if no automation table match was found. The following screenin Figure 82 is a simple example of IF-THEN, BEGIN/END, ALWAYS usage:

Figure 82. Example of using BEGIN/END and IF statements

Another design criteria of building the automation table structure is thefrequency of use of specific statements or blocks. Order the BEGIN/ENDsections according to their frequency of use to eliminate frequently appearingmessages to pass long lists of statements before final matches occur.

For example, if a large number of VTAM messages are received, aBEGIN/END section to handle IST messages should be at or near the top ofthe automation table to decrease the number of statements that must beevaluated before the correct BEGIN/END section is found.

The following screen in Figure 83 on page 168 illustrates the summary outputresult of the AUTOCNT command.

IF MSGID = 'AOFDATA:'THENBEGIN;

IF ATF('DSICGLOB AOF.RPC.0DEBUG') = 'Y'THENDISPLAY(Y) NETLOG(Y);

ALWAYS DISPLAY(Y) NETLOG(N);

END;

The less criteria statements to be scanned before a match occurs, thebetter the overall performance of the system and its automation.

Note

Use the AUTOCNT command to determine the usage of automation tablestatements and find out what statements are more frequently used thanothers. Refer to the Tivoli Netview for OS/390 Tuning Guide, SC31-8240,for further information about the AUTOCNT command.

Note


Figure 83. AUTOCNT command summary results

7.2.1.2 Other automation table design guidelinesThe following considerations for designing the automation table structure helpto reduce processing overhead and enhance automation performance:

• Use IF-THEN statements and ALWAYS statements to specify that noaction should be performed, thus eliminating unnecessary processingtime.

• Use the ASSIGN command to split the messages among severalautotasks.

This will prevent automation performance bottlenecks due to a highnumber of unsolicited messages queueing for processing on one singleautotask.

• Eliminate simple command procedures (REXX clists) whose function canbe processed in the automation table directly.

The invocation of the clist and its interpretation takes longer than directprocessing from the automation table.

7.2.2 Additional hints and tuning considerationsThis section is a summary of other best practices and additional hints thathelp improve the overall NetView performance:

• Limit the number of system messages that the NetView program hasto process

The NetView automation table is searched for most messages that passthrough the NetView program. Therefore, it is important to limit the systemmessage traffic sent to the NetView program to only those messages that

NCCF Tivoli NetView SC66A GUIMARA 12/09/99 16:18:42* SC66A AUTOCNT REPORT=MSG,STATS=SUMMARY,DISPLAY' SC66ADWO801I AUTOMATION TABLE MSG SUMMARY REPORT BY GUIMARA-----------( AOFMSG01/******** MESSAGE SUMMARY 12/09/99 16:18:42 )------------AUTO1 COMPLETED INSERT FOR TABLE #1: AOFMSG01 AT 12/07/99 16:45:47STATISTICS STARTED = 12/07/99 16:45:47TOTAL MSGS PROCESSED = 17535MSGS MATCHED = 17535MSGS RESULTING IN COMMANDS = 176TOTAL COMMANDS EXECUTED = 194TOTAL ROUTES EXECUTED = 0AVERAGE COMPARES/MSG = 34.38AVERAGE MSGS/MINUTE = 6MINUTES ELAPSED = 2852


should be considered for automation or to those that are needed fordisplay purposes.

On OS/390 systems, the MPFLSTxx member of SYS1.PARMLIB identifieswhether a message is eligible for automation processing. SpecifyAUTO(YES) or AUTO(NO) to identify whether a message is eligible forautomation processing.

• Optimize the VSAM CISIZE’ and DSIZVLSR (LSR/DFR) buffer settings.

Use the VSAMPOOL command to check the buffer usage, and:

- Save main storage by removing buffers that were never used.

- Reduce the number/size of infrequently used buffers.

- For index buffers that are frequently used, the number of buffer finds(BFRFND) should be at least 10-20 times the number of buffers reads(BUFRDS).

It may be necessary to increase the number of buffers to achieve thisratio.

- For data buffers that are frequently used, the number of buffer findsshould be greater than the number of buffer reads.

• Use the improved MEMSTORE command to ensure that frequently usedclists are loaded in storage for faster access and reduced disk I/O.

The MEMSTORE command should be run periodically from the sametask, preferably an autotask. The MEMSTORE command obtains a list ofmembers that have been read very often from disk and loads thesemembers into storage specified by the command.

If necessary, members with low disk I/O, but previously being loaded intostorage by this task, will be unloaded.

• Use the IDLEOFF command to examines operator idle times and stopthem after a defined period of time. Idle time is defined as the time sincenew input was provided by the task owner.

Figure 84 on page 170 shows how to use the MEMSTORE and IDLEOFFcommands in the NetView initialization clist CNME1034.

To start automatically the MEMSTORE and IDLEOFF features, uncommentthese statements in the CNME1034 NetView initialization clist.

Note


Figure 84. MEMSTORE and IDLEOFF statements in the CNME1034 Clist

7.3 Maintenance of the System Automation policy data base

The System Automation policy database is created and built with the dialogtool described in Section 5.3, “Defining all systems and objects to SystemAutomation” on page 60 and in Chapter 6. An optimized structure of theSystem Automation policy database is recommended because the SystemAutomation workload depends on the structure of its policy database andusage of its advanced features.

The following sections provide some considerations, derived from theexperiences of the ITSO automation project, about how to use and optimizethe System Automation policy database. The topics are as follows:

• Design a hierarchical structure for the SA policy database

• Use ADD/REMOVE commands to reload/unload the SA policy database

• RACF considerations

• Migrate policies from previous AOC

• Build ACF and RODM

• Produce an SA policy database report

• Use ACFPLOAD command

7.3.1 Design a hierarchical structureBefore the creation of the System Automation policy database, design thedatabase structure first. Divide the applications into different groupsaccording to their characteristics and functions. Have applications withcommon policies share a generic application class. By using the classsupport, redundant definitions are eliminated, and changes to the SA policydatabase are substantially easier.

/* If you wish to run MEMSTORE to keep high-use PDS members instorage instead of on disk, modify and uncomment the followinglines. For more information enter HELP MEMSTORE and/or refer toto the commentary in CNME1054. */

/* 'PIPE CC AUTOTASK OPID=memstask | CONS' *//* 'OVERRIDE MAXIO=0,TASK=memstask' */

'EVERY 00:02:00 ROUTE=AUTO1 EVERYCON=YES MEMSTORE 5% 5'

/* If you wish to run IDLEOFF to log off idle operators, modify anduncomment the following line. For more information enterHELP IDLEOFF and/or refer to the commentary in CNME1057. */'IDLEOFF INIT AUTO1 60 10'


For example, automate TSO and TCPIP with a generic class, since TSO andTCPIP have very similar common policies, including the unique parentapplication VTAM, start-up, and shutdown behaviors. Define this genericapplication class with all the common policies, and associate this applicationclass to TSO and TCPIP.

In a sysplex policy database, the usage of clone names and symbolics is veryimportant for the applications to be able to run on the multiple systems withinthe sysplex environment.

A thoughtfully designed and optimized System Automation policy databasewill tremendously reduce the overall maintenance effort.

7.3.2 Using ADD/REMOVE commandsThe ADD command is used to add a policy database from a given dataset,which was previously removed. The ADD functions works like adding a newcatalog entry to the System Automation policy database list without actuallycreating a new policy database.

The REMOVE command is used for removing a policy database from SystemAutomation policy list, such as issuing an UNCATALOG command to thatexisting policy database. The dataset of the removed policy database is notactually deleted.

After a policy database has been created and applied on the system, it maybe removed from the policy database list, in the case that changes arenecessary. Submit the MVS IEBCOPY function to back up the policydatabase. When the required policy database changes are completed, it maybe added back to the policy database list.

On a sysplex environment, System Automation administrators on the targetsystems or focal point system sometimes need to review or change policydatabase settings to improve automation performance. Sharing one policydatabase is, for example, possible by using the ADD command for thisparticular policy database.

7.3.3 RACF considerationsIn general, the System Automation policy database is only used by itsadministrators. The RACF facility is used to protect the policy database, andto define this database as a RACF class resource.

Use the ADDSD command to add the policy database as a RACF class:

ADDSD <dsname> UACC(NONE) AUDIT(ALL(READ))


where <dsname> represents the policy dataset name.

Use the PERMIT command to grant userids to alter the policy database:

PERMIT <dsname> ID(<userid>) ACCESS(ALTER)

where <dsname> represents the policy dataset name and <userid> the SystemAutomation administrator.

7.3.4 System Automation migrationA migration function is provided by the System Automation policy dialog tomigrate from earlier release to current release. The following functions areavailable for System Automation V1R3:

• Add an existing AOC/MVS or SA OS/390 automation control file to thepolicy database

• Transform the format of existing AOC/MVS enterprise policy databases

• Add existing TSCF configuration

Use the System Automation MIGRATE command or the action menuMIGRATE to initiate a migration.

For detailed information on how to migrate, refer to System Automation forOS/390 V1R3 Customization, GC28-1566.

7.3.5 Building for ACF and RODMAfter the Automation NetView start-up, the current Automation Control File(ACF) and RODM policy data will be managed and controlled by NetView andRODM. During the online access of NetView and RODM to this policyinformation, the user is limited in the use and the update of this policydatabase.

It is recommended that different datasets are used for the policy databaseand ACF, RODM datasets. When building a policy database, the user isprompted by the function, Build Output Dataset. It is advised to use anotherdataset name at this point so that the policy database may be operated andupdated without any limitation.

For detailed information on how to build the ACF and the RODM loadstatements, refer to the manual System Automation for OS/390 V1R3Customization, GC28-1566.


7.3.6 Policy reportSystem Automation provides report functions to its administrator to print adescription for the automation policy. By using the REPORT command or theREPORT menu action, the report will be produced.

Use the GML or Bookmaster function to read or print the report.

7.3.7 ACFPLOADThe ACFPLOAD command allows changes to be made to the automationconfiguration policy without reloading the entire ACF or interrupting theautomation processing.

For ACFPLOAD command usage, the user needs to know the specificmember name of the configuration data to be loaded. This can be done fromthe NetView command interface, NCCF, by browsing the AOFACFMP memberto determine the current configuration file. With ACFPLOAD, localmodifications can be accomplished without the need to recycle the entireACF.



Chapter 8. Base automation features

This chapter explains the basic automation features of both products, TivoliNetView and System Automation. It describes base automation rules forSystem Automation to better understand and use its automation, as well asthe existent and new automation capabilities of Tivoli NetView for OS/390.

8.1 New automation table features of NetView for OS/390 V1R3

The following enhancements have been made to the automation tablefunctionality in NetView for OS/390:

• Support for multi-line messages

• Most IF-THEN condition items can now use substrings

• Support of greater-than and less-than operators

• Support of numeric comparisons

• Support of current date (format mm/dd/yy) and current time (formathh:mm:ss) values as condition items

• Values of variables can be used at various places on the IF side of theautomation table statement (VALUE() function)

• An EDIT action has been added to enable messages and MSUs to beparsed and reformatted

• A TRACE action has been added to trace the processing of a message orMSU through the automation table

• The AUTOMATED function has been added to test the status of thehandling of a message or MSU

Examples of these are given below.

8.1.1 Multi-line message supportThe multi-line message support uses the ACQUIRE automation tablecondition item, which makes use of the PIPE EDIT stage syntax and functionto extract AIFR data.

Refer to the Tivoli NetView for OS/390 Automation Guide, SC31-8225, forfull details of automation table statement syntax.

Note


An example is shown in Figure 85:

Figure 85. Example of multi-line message processing

8.1.2 IF-THEN condition item substringsThe IF-THEN condition item substrings allow a length to be specified on thecompare item instead of having to code a period (.) to terminate the length ofthe compare.

An example is given in Figure 86.

Figure 86. Automation table IF-THEN substrings

Issuing the command

DIS BILL

will result in the output shown in Figure 87 on page 177.

** THIS RESPONSE TO MVS D A,NPM SHOWS IT NEEDS STARTING**IEE115I 16.38.52 1999.347 ACTIVITY 908* JOBS M/S TS USERS SYSAS INITS ACTIVE/MAX VTAM OAS*00007 00050 00003 00030 00055 00003/00050 00026*NPM NOT FOUND*IF MSGID='IEE115I' &ACQUIRE('LINENUM 4 WORD 2.2') = 'NOT FOUND' &ACQUIRE('LINENUM 4 WORD 1') = 'NPM' THENEXEC(CMD('MVS S NPM'));

** Example of substrings in TOKEN** Output from DIS command if invalid resource is specified :* EG. DIS BILL* IST453I ID PARAMETER VALUE USIBMSC.BILL NOT VALID*IF MSGID='IST453I' &

TOKEN(5 3 3) = 'IBM' &TOKEN(5 1 7) = NETWORK &TOKEN(5 9) = RES THENEXEC(CMD('MSG ALL RESOURCE 'NETWORK'.'RES' IS INVALID')ROUTE(ONE *));

*


Figure 87. Output from DIS command exploiting IF-THEN substrings

8.1.3 Greater-than and less-than operator supportIt is now possible to specify comparison ranges using the ‘>=’ and ‘<=’operators. Figure 88 shows greater-than and less-than operators used todetermine the daily work shift hours.

Figure 88. Example of greater-than and less-than operator support

8.1.4 Numeric comparison and current time supportAs demonstrated in Figure 88, it is now possible to perform direct numericcomparison and use the current date (CURRDATE) and current time(CURRTIME) functions.

8.1.5 Variable value function supportThe new VALUE() function enables variables to be used on the IF side of theautomation table statement included in the ATF DSICGLOB function. Thisprovides flexibility and an opportunity to significantly reduce the number andcomplexity of automation table statements.

Figure 89 on page 178 demonstrates the new VALUE() function.

NCCF Tivoli NetView SC69N NETOP1 12/14/99 14:50:28C SC69N DISPLAY NET,ID=BILL,SCOPE=ALLSC69N IST453I ID PARAMETER VALUE USIBMSC.BILL NOT VALID

- SC69N DSI001I MESSAGE SENT TO ALLM SC69N DSI039I MSG FROM NETOP1 : RESOURCE USIBMSC.BILL IS INVALID-------------------------------------------------------------------------------

** Example of greater and less than numeric comparison and current time**IF MSGID='DSI123I' THENBEGIN;IF CURRTIME(1 2) >= '08' &IF CURRTIME(1 2) <= '17' THEN

EXEC(CMD('DAYSHFTC'));ALWAYS

EXEC(CMD('OFFSHFTC'));END;

*

Chapter 8. Base automation features 177

Figure 89. Example of variable value function support

In this example, the global variable

MYVAR.USIBMSC.FRED.ADD.TEXT

was set to the value

YES

On issuing the command

DIS FRED

the following output is displayed (Figure 90) showing that the condition in theautomation table was all true and that the COPY command was issued.

Figure 90. Output from DIS command exploiting automation table variables

8.1.6 Message reformattingThe EDIT action (PIPE EDIT functionality) has been added to make changesto an AIFR while it is in the automation table. With EDIT, messages andMSUs can be parsed and reformatted. The altered AIFR will continue throughthe automation table.

Figure 91 through Figure 93 show how a message would be displayed beforeEDIT processing, the automation table statements to reformat it, and how itwould appear after EDIT processing.

** Example of variable usage*IF MSGID='IST453I' &

TOKEN(5 6 2) = NETSUFF &TOKEN(5 1 7) = 'USIBM'VALUE(NETSUFF) &TOKEN(5 1 7) = NTWK &TOKEN(5 9) = RES &ATF('DSICGLOB MYVAR.'VALUE(NTWK)'.'VALUE(RES)'.ADD.TEXT') = 'YES'THENEDIT('COPY * /REISSUE DIS COMMAND SPECIFYING A VALID RESOURCE');

*

NCCF Tivoli NetView SC69N NETOP1 12/14/99 15:43:09C SC69N DISPLAY NET,ID=FRED,SCOPE=ALLSC69N

IST453I ID PARAMETER VALUE USIBMSC.FRED NOT VALIDREISSUE DIS COMMAND SPECIFYING A VALID RESOURCE-------------------------------------------------------------------------------


Figure 91. Output from REFRESH OPERS command before EDIT action

Figure 92. Automation table EDIT action statements

Figure 93. Output from REFRESH OPERS command after EDIT action

8.1.7 Automation table tracingThe TRACE action allows the tracing of a message, or MSU processing, as itgoes through the automation table. Detailed trace information is displayed onthe console by the BNH370I for each automation table statement that isprocessed.

An example of an automation table TRACE statement and the console output isshown in Figure 94 and Figure 95 on page 180.

Figure 94. Automation table TRACE statement

* SC69N REFRESH OPERS- SC69N DSI213I ACCESS TO 'REFRESH' IS NOT AUTHORIZED

** Example of EDIT action*IF MSGID='DSI213I' THEN

EDIT('COPY * /CALL USER SUPPORT AT 91-123456/');*

* SC69N REFRESH OPERS- SC69NDSI213I ACCESS TO 'REFRESH' IS NOT AUTHORIZEDCALL USER SUPPORT AT 91-123456

The BNH370I message is issued to the console. Logic can be included inthe automation table to direct it to the NetView log if desired. Do not specifya TRACE action for BNH370I, as this will cause a loop.

Note

** Example of automation table tracing*IF MSGID='DSI820I' THEN TRACE('DSI820trace');*


Figure 95. TRACE statement output

8.1.8 The AUTOMATED functionThe AUTOMATED function sets or checks an indicator for a message or alertthat shows whether it has already been automated. This is useful to preventstatements that make only a minor change from indicating that the messageor alert has already been automated, or it could be used at the end of theautomation table to act on messages and alerts that have not otherwise beenautomated. Figure 96 demonstrates the AUTOMATED function.

Figure 96. Examples of AUTOMATED function

8.2 System Automation framework

The following sections detail some major automation functions that weresummarized in Section 2.2, “Proactive management of OS/390 subsystemtasks” on page 12 and Section 2.3, “Monitoring and recovery capabilities ofOS/390 subsystems” on page 12.

BNH370I FAIL MSGID DSITBL01 DSITBL01 01440002DSI820TraceBNH370I FAIL AND DSITBL01 DSITBL01 01440002DSI820TraceBNH370I FAIL MSGID DSITBL01 DSITBL01 01570002DSI820TraceBNH370I FAIL AND DSITBL01 DSITBL01 01570002DSI820Trace

* AUTOMATED function examples:** This sets the AUTOMATED indicator to N (NO)*IF MSGID='IST' . THEN

SYSLOG(Y) NETLOG(Y) AUTOMATED(N) CONTINUE(Y);** This checks the AUTOMATED indicator** If a VTAM message has already been automated turn it BLUE,* Unautomated messages turn YELLOW*IF MSGID='IST' . THEN

BEGIN;IF AUTOMATED = '1' THEN

COLOR(BLU);ALWAYS COLOR(YEL);

END;*


8.2.1 Automating subsystemsAs an example, some routine procedures of automating subsystems using thenew the System Automation functions Events and Triggers will be described.

8.2.1.1 Sequential start-up of focal point subsystemsThe following example details the subsequent start-up logic of the RODM andGMFHS on the networking focal point system. It implies the following rules:

1. The NETWORK_RODM job is always cold-started.

2. The NETWORK_RODM_DM job is a transient job that loads the datamodels into RODM.

3. The NETWORK_GMFHS job will not start until the RODM data modelstructures are loaded successfully into RODM.

To define the subsequent logic and rules for these three start-up actions, it isnecessary to define appropriate messages in the NETWORK_RODMsubsystem that will be used as a trigger to start the NETWORK_RODM_DMjob when the RODM subsystem is started successfully.

Enter the System Automation policy database dialog, as shown in Figure 97on page 182, and select the 6 - Application option.

Refer to System Automation for OS/390 V1R3M0 Customization,GC28-1566, for further information about triggers, service periods, andevents.

Note


Figure 97. SA OS/390 Entry Type Selection panel

In the Application Entry Selection panel, select the desired application, which,in this example, is NETWORK_RODM as shown in Figure 98.


This selection will bring up the Application Policy Selection panel forNETWORK_RODM as illustrated in Figure 99 on page 183.

SA OS/390 Entry Type SelectionCommand ===> 6




41 Resident CLISTs ( RES )






SA OS/390 Entry Selection Row 11 to 22 of 28Command ===> SCROLL===> CSR


Action Entry Name C Short DescriptionNETVIEW_CLASS * NetView DefaultsNETVSA Automation NetView definitionNETVSSI NetView subsystem interfaceNETWORK_GMFHS Network GMFHSNETWORK_NETVIEW Network NetViewNETWORK_NETVIEW_SSI Network NetView Interface

S NETWORK_RODM Network RODMPROCESSOR_OPERATIONS Processor Operations functionsRODM_CLASS * RODM DefaultsSAOS390_GMFHS System Automation GMFHSSAOS390_NETVIEW System Automation NetViewSAOS390_NETVIEW_SSI System Automation NetView Interface



Select the MESSAGES option and press Enter to create a new messagecommand. On the specific Message Processing panel, show in Figure 100,enter the Action keyword, CMD, and the Message ID, ACTIVE.

Figure 100. SA OS/390 Application Message Processing panel

For the subsequent start-up of the NETWORK_RODM_DM application everytime the NETWORK_RODM is restarted and identified as to be ACTIVE, it isrequired that you specify the appropriate System Automation action as shownin Figure 101 on page 184.


Entry Type : Application PolicyDB Name : ITSO_ENTERPRISEEntry Name : NETWORK_RODM Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionLINK TO CLASS Link instance to classAPPLICATION INFO Enter and display Application informationINFO BRIDGE Enter INFO Bridge resource nameRMF Enter RMF objectives and reporting criteriaAUTOMATION INFO Define Application automation informationAUTOMATION FLAGS Define Application automation flags

S MESSAGES Define Application messagesSHUTDOWN Define shutdown proceduresTHRESHOLDS Define error thresholdsRESTART Define commands executed at restartMINOR RESOURCES Define Application sub-component flags

SA OS/390 Message Processing Row 1 to 6 of 22Command ===> SCROLL===> CSR


Resource: RODMAON

Enter messages issued by this resource that will result in automated actions.Actions: CMD = Command REP = Reply CODE = CODE

Action Message ID Description Cmd Rep Code

CMD ACTIVE


Figure 101. SA OS/390 Application Command Processing panel

This step finishes the dependency definition between the start-up ofNETWORK_RODM and NETWORK_RODM_DM. The same definition stepshave to be processed for the dependency of NETWORK_RODM_DM and thestart of NETWORK_GMFHS.

After all definition steps have been processed, it is required to rebuild theSystem Automation control file (ACF file) and recycle the NetView control fileto have these changes become effective.

8.2.1.2 Sequential shutdown of focal point subsystemsThe following example details the subsequent shutdown logic of theAutomation NetView. It implies the following rules:

1. The subsystem SAOS390_NETVIEW has the dependency to start andstop after the subsystem interface SAOS390_NETVIEW_SSI.

2. If all subsystems in the system environment are to be terminated, theSHUTSYS ALL command is being issued. The termination of thesubsystem, SAOS390_NETVIEW, has to be delayed until all otherapplications, including SAOS390_NETVIEW_SSI, have successfullyterminated.

To define the subsequent logic and rules for these shutdown actions it isnecessary to define an appropriate event and trigger for theSAOS390_NETVIEW_SSI subsystem that will be used to shutdown theSAOS390_NETVIEW application.

SA OS/390 CMD Processing Row 1 to 3 of 20Command ===> SCROLL===> CSR


Resource: RODMAONMessage ID: ACTIVE

Enter commands to be executed when resource issues the selected message.

Pass or AutomatedSelection Function

Command Text

SETSTATE NETWORK_RODM_DM,RESTART


Enter the System Automation policy database dialog and select the EVT or 44(Events) option as shown in Figure 102 on page 185.

Figure 102. SA OS/390 Entry Type Selection Main panel

In the Event Entry Selection panel, create a new event by entering the NEWcommand in the command line as shown in Figure 103.

Figure 103. SA OS/390 Event Entry Selection panel

Define the new event by entering the name, SSI_DOWN, and a shortdescription of its content as shown in Figure 104 on page 186.



Enterprise Resource Definitions Resource Policy DefinitionsMore: - +

8 Volume ( VOL ) 37 Auto Operators ( AOP )9 OperatorView ( OPV ) 38 Auto Msg Classes ( AMC )10 Processor ( PRO ) 39 Network ( NTW )11 Communications Path ( CMP ) 40 NNT Sessions ( NNT )

41 Resident CLISTs ( RES )(*) Multi-User-Capable 42 Status Details ( SCR )

43 Communications Task ( CMT )44 Events ( EVT )45 Service periods ( SVP )46 Triggers ( TRG )98 Includes ( ICL )

SA OS/390 Entry Selection Row 1 to 1 of 1Command ===> NEW SCROLL===> CSR

Entry Type : Event PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short DescriptionJES_DOWN JES2 is DOWN

******************************* Bottom of data ********************************


Figure 104. SA OS/390 Define New Event Entry panel

Having defined this new event, it is required to define the correspondingtrigger that is driven by the new event. This trigger will then initiate theshutdown of the SAOS390_NETVIEW application.

Return to the System Automation policy database dialog and select the TRGor 46 (Triggers) option as shown in Figure 105.


In the Trigger Entry Selection panel, create a new trigger by entering theNEW command in the command line as shown in Figure 106 on page 187.


To define a new entry, specify the following information:Type. . . . . . . . . . EventName. . . . . . . . . . SSI_DOWN

Unset Condition . . . . NONE DOWN NONE START UP

Short Description . . . SA OS390 NetView SSI is DOWNExtended Description. .

. .

. .

. .

. .



Enterprise Resource Definitions Resource Policy DefinitionsMore: - +

9 OperatorView ( OPV ) 38 Auto Msg Classes ( AMC )10 Processor ( PRO ) 39 Network ( NTW )11 Communications Path ( CMP ) 40 NNT Sessions ( NNT )

41 Resident CLISTs ( RES )(*) Multi-User-Capable 42 Status Details ( SCR )

43 Communications Task ( CMT )44 Events ( EVT )45 Service periods ( SVP )46 Triggers ( TRG )98 Includes ( ICL )99 User E-T Pairs ( UET )


Figure 106. SA OS/390 Trigger Entry Selection panel

Define the new trigger by entering the name, SHUT_NV, and a shortdescription of its content as shown in Figure 107.

Figure 107. SA/OS390 Trigger New Entry Definition panel

Having defined the new trigger, it is required to define the condition that willdrive this new trigger.

Select the CONDITION option as shown in Figure 108 on page 188, andcontinue with the trigger settings.

SA OS/390 Entry Selection Entry deletedCommand ===> NEW SCROLL===> CSR

Entry Type : Trigger PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short Description******************************* Bottom of data ********************************


To define a new entry, specify the following information:Type. . . . . . . . . . TriggerName. . . . . . . . . . SHUT_NV

Short Description . . . Shut down SA OS/390 NetViewExtended Description. .

. .

. .

. .

. .


Figure 108. SA OS/390 Trigger Policy Selection panel

From the Trigger Selection panel, shown in Figure 109, select one of theSHUTDOWN conditions available.

Figure 109. SA OS390 Trigger Conditions panel

The next step is to associate the SHUTDOWN trigger condition with theappropriate event that will drive this trigger.

SA OS/390 Policy Selection Trigger createdCommand ===> SCROLL===> CSR

Entry Type : Trigger PolicyDB Name : ITSO_ENTERPRISEEntry Name : SHUT_NV Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter description

S CONDITION Define the trigger condition-------------------- ---------------------------------------------WHERE USED List Applications using this entryCOPY Copy data from existing entry

******************************* Bottom of data ********************************

SA OS/390 Trigger Conditions Row 11 to 20 of 21Command ===> SCROLL===> CSR


Note: You have to define the service period before you can use it in aSTARTUP/SHUTDOWN condition.

Action Condition NamesSTARTUP 10

S SHUTDOWN 1SHUTDOWN 2SHUTDOWN 3SHUTDOWN 4SHUTDOWN 5SHUTDOWN 6SHUTDOWN 7SHUTDOWN 8SHUTDOWN 9


Figure 110. SA OS/390 Shutdown Condition for Trigger panel

On the SHUTDOWN Condition for Trigger panel in Figure 110 on page 189,select the previously defined event, SSI_DOWN.

The next step is to associate the SHUTDOWN trigger to an application,which, in this example, will be the Automation NetView SAOS390_NETVIEW.

Return to the SA OS/390 Entry Selection Main panel and select APL or 6(Applications) to enter the Application Selection panel as shown in Figure111.

Figure 111. SA OS/390 Application Selection panel

SA OS/390 SHUTDOWN Condition for Trigger Row 1 to 2 of 2Command ===> SCROLL===> CSR


Description. . . .

Service Period . . NO YES NO

Action Status Event Short DescriptionJES_DOWN JES2 is DOWN

S SSI_DOWN SA OS390 NetView SSI is DOWN******************************* Bottom of data ********************************



Action Entry Name C Short DescriptionJES2 JES2 policy definitionLLA LLA automation policyNETVIEW_CLASS * NetView DefaultsNETWORK_GMFHS Network GMFHSNETWORK_NETVIEW Network NetViewNETWORK_NETVIEW_SSI Network NetView InterfaceNETWORK_RODM Network RODMPROCESSOR_OPERATIONS Processor Operations functionsRODM_CLASS * RODM DefaultsSAOS390_GMFHS System Automation GMFHS

S SAOS390_NETVIEW System Automation NetViewSAOS390_NETVIEW_SSI System Automation NetView InterfaceSAOS390_RODM RODM automation policy


From the Application Selection panel, select the SAOS390_NETVIEWapplication and enter the TRIGGER option as demonstrated in Figure 112.


The appropriate trigger to select is SHUT_NV as illustrated in Figure 113

Figure 113. SA OS/390 Trigger for Application panel

These steps complete the definition of the SAOS390_NETVIEW applicationand the SHUT_NV trigger.

The last steps of this example will be to associate the termination of theSAOS390_NETVIEW_SSI subsystem with the SSI_DOWN event. Thisassociation will set this event every time the NetView subsystem interface isset to the AUTODOWN status for termination.



Action Policy Name Policy DescriptionAPPLICATION INFO Enter and display Application informationINFO BRIDGE Enter INFO Bridge resource nameRMF Enter RMF objectives and reporting criteriaAUTOMATION INFO Define Application automation informationAUTOMATION FLAGS Define Application automation flagsMESSAGES Define Application messagesSHUTDOWN Define shutdown proceduresTHRESHOLDS Define error thresholdsRESTART Define commands executed at restartMINOR RESOURCES Define Application sub-component flagsSYSTEM ASSOCIATION Define primary and secondary associations

S TRIGGER Select Application trigger-------------------- ---------------------------------------------

SA OS/390 Trigger for Application Row 1 to 1 of 1Command ===> SCROLL===> CSR


Action Status TriggerS SHUT_NV******************************* Bottom of data ********************************


To apply the association of the SSI_DOWN event to theSAOS390_NETVIEW_SSI application, enter the Application Selection panelas shown in Figure 114.


Select SAOS390_NETVIEW_SSI to enter the Application Policy Selectionpanel as displayed in Figure 115.

Figure 115. SA OS/390 Policy Selection panel



Action Entry Name C Short DescriptionJES2 JES2 policy definitionLLA LLA automation policyNETVIEW_CLASS * NetView DefaultsNETWORK_GMFHS Network GMFHSNETWORK_NETVIEW Network NetViewNETWORK_NETVIEW_SSI Network NetView InterfaceNETWORK_RODM Network RODMPROCESSOR_OPERATIONS Processor Operations functionsRODM_CLASS * RODM DefaultsSAOS390_GMFHS System Automation GMFHSSAOS390_NETVIEW System Automation NetView

S SAOS390_NETVIEW_SSI System Automation NetView InterfaceSAOS390_RODM RODM automation policy


Entry Type : Application PolicyDB Name : ITSO_ENTERPRISEEntry Name : SAOS390_NETVIEW_SSI Enterprise Name : ITSO_ENTERPRISE


S MESSAGES Define Application messagesSHUTDOWN Define shutdown proceduresTHRESHOLDS Define error thresholds

S RESTART Define commands executed at restartMINOR RESOURCES Define Application sub-component flagsSYSTEM ASSOCIATION Define primary and secondary associations


In order to set or reset the SSI_DOWN event, first, select the MESSAGESoption to create a new definition to set the event, and then select theRESTART option to reset this event when the subsystem is restarted.

First, on the Message Processing panel, as shown in Figure 116, enter theAction keyword, CMD, and the Message ID keyword, AUTODOWN.


The next step, shown in Figure 117, defines the command

SETEVENT ID=SSI_DOWN,FUNCTION=SET,SCOPE=TARGET

that will set the SSI_DOWN event every time the SAOS390_NETVIEW_SSIapplication reaches the AUTODOWN status. This event, SSI_DOWN, will kickoff the SHUT_NV trigger which was previously defined, that will beresponsible shutdown the SAOS390_NETVIEW application.

Figure 117. SA OS/390 Application Command Processing panel



Resource: SSISA



CMD AUTODOWN



Resource: SSISAMessage ID: AUTODOWN



Command Text_________ ________

SETEVENT ID=SSI_DOWN,FUNCTIN=SET,SCOPE=TARGET


Now, return to the Application Policy Selection panel, as displayed in Figure115 on page 191, and enter the RESTART option to enter the RestartProcessing panel shown in Figure 118.

Figure 118. SA OS/390 Application Restart Processing panel

In the Restart Processing panel, enter the command text

SETEVENT ID=SSI_DOWN,FUNCTION=UNSET,SCOPE=TARGET

that will reset the SSI_DOWN event every time the SAOS390_NETVIEW_SSIapplication is successfully restarted.

8.2.2 Automating messagesThis section describes how to add a message that has not been previouslyautomated to the automated operations environment and will give someexamples of situations that can be automated using the System Automationfacilities.

The routine actions that a system operator performs when a particularmessage is generated can be automated by the NetView automation tableand the System Automation. With automation enabled, the automation focalpoint system responds quickly and accurately to messages from any activetarget systems.

SA OS/390 RESTART Processing Row 1 to 6 of 20Command ===> SCROLL===> CSR


Subsystem : SSISADescription : System Automation NetView Interface

Enter commands to be executed when NetView is started orrecycled with this subsystem already active.

Automated Command TextFunction

SETEVENT ID=SSI_DOWN,FUNCTION=UNSET,SCOPE=TARGET

To automate a message using the System Automation framework, thismessage needs to be issued by an application previously defined to SAOS/390.

Note


8.2.2.1 Automating the response to the messageThe first step is to define the type of response that will be performed whenmessages appear. This can be to issue a reply, a command, or define amatch code to be tested in the message.

To get one application class, NETVIEW_CLASS, defined for both theAutomation and Network NetView, it is necessary to define a identificationcode in all issued messages to identify the corresponding applicationassociated to this class. If matches occur, an action keyword will be returnedto the invoking automation system.

Defining this message in an application class ensures that this automationdefinition will be inherited by all the application instances associated with thisapplication class.

From the System Automation Main Entry Selection panel, select the APL or 6(Application) option to enter the Application Selection panel.

Select the application class, NETVIEW_CLASS, and the Application PolicySelection panel for NETVIEW_CLASS will be shown as in Figure 119 on page195.

For detailed information about System Automation class definitions refer toChapter 5, “Customization of System Automation for OS/390” on page 53.

Note


Figure 119. SA OS/390 Policy Selection panel

From the Application Policy Selection panel, select the MESSAGES option tospecify message types for this application class.

On the Message Processing panel, displayed in Figure 120, specify theAction keyword, CODE, the Message ID keyword, WTORS, and a shortdescription of the action the response performs.


The following panel defines how messages DSI802A and DSI803A (NetViewreplies) will be handled when they are received from the subsystemsassociated with this class.



Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionLINK TO INSTANCES Link class to instancesAPPLICATION INFO Enter and display Application informationINFO BRIDGE Enter INFO Bridge resource nameRMF Enter RMF objectives and reporting criteriaAUTOMATION INFO Define Application automation informationAUTOMATION FLAGS Define Application automation flags

S MESSAGES Define Application messagesSHUTDOWN Define shutdown proceduresTHRESHOLDS Define error thresholdsRESTART Define commands executed at restartMINOR RESOURCES Define Application sub-component flagsTRIGGER Select Application trigger



Resource: NETVIEW_CL



CODE WTORS WTOR Classification 3


When the DSI802A message appears with any code, a value of NORMAL PRIis returned to the calling automation procedure. In addition, this message willbe displayed like a normal status message, for example, in the SDF panels.

Any other replies issued for these subsystems will be displayed in the SDFpanels as an unusual message.

Figure 121. SA OS/390 Application Message Code Processing panel

After these definitions, verify the message processing facility (MPF) table toassure that the default for this message is AUTO(YES). If required, add amessage processing facility list entry specifying the message ID and theAUTO(YES) parameter value.

When definitions to add message response and automation operatorinformation to the automation policy database are completed, return to the SAOS/390 Application Selection panel and enter the action command F(BUILDF) in the action column in front of the application that has been edited.This will initiate a rebuild for the application definitions.

System Automation for OS/390 builds the new automation definitions for theapplication, and after completion of this application rebuild, the SystemAutomation customization dialog can be exited.

The System Automation for OS/390 build function will place the newautomation definitions in the data set defined in the BUILDF Parameterspanel.

SA OS/390 Code Processing Row 1 to 6 of 23Command ===> SCROLL===> CSR


Resource: NETVIEW_CLMessage ID: WTORS

Enter the value to be passed to the calling CLIST when this resourceissues the selected message and the following codes are contained inthe message.

Code 1 Code 2 Code 3 Value ReturnedDSI802A * NORMAL PRIDSI803A * UNUSUAL PRI* UNUSUAL SEC


Copy the new automation definitions into the common Automation NetViewDSIPARM library specified in the Automation NetView start-up procedure andreload the NetView Control File.

Refer to System Automation for OS/390 V1R3M0 Customization, GC28-1566,for detailed information on how to add messages to the automation.

8.3 System Automation and NetView base automation rules

This section describes some guidelines for effectively propagating andmaintaining an automation environment.

The first step toward automating the entire data-processing enterprise is toensure that there is as much local automation as possible on each NetViewsystem.

Therefore, if a single-system automation is developed on one system or a fewtest systems, propagate that automation onto all of the NetView systems.Copy the automation routines and tailor the routines to the new systems. Forthis process, it is important to automate all of the systems consistently tokeep maintenance efforts as simple as possible.

The main guidelines for keeping the automation environment reliable andsimple are as follows:

• Automate close to the source

In a multi-system environment, automate as many tasks as possible on thedistributed systems and forward only those events that cannot be handledat the distributed systems to the focal point system.

At the distributed system, if the function of the operating system facility(the message processing facility - MPF) enables the goals for the systemto be met without using the automation table, use the appropriateoperating system function. Otherwise, use NetView and SystemAutomation facilities.

• Define autotasks consistently

This notice is a reminder that the CNME1035 clist is no longer used byTivoli NetView for OS/390 V1R3 as the initial NetView PPT start-up clist.Please check for any self-written customizations and move appropriatemodifications to the new NetView PPT start-up CNME1034 clist.

Note


Operator definitions for autotasks in DSIOPF or an SAF product, profiles,and operator passwords should be consistent across systems. Consistentdefinitions reduce the effort required to make changes among systems.

• Develop generic automation command procedures

To minimize the work required for development, maintenance, andsynchronization of automation procedures for multiple systems, writegeneric procedures to function the same in all applicable systems. Theseprocedures should also function on the focal point system when thesystem is not performing focal point functions.

To simplify migration, use global variables for system and resource namesrather than hard-coded resource names in command procedures.

By keeping the definition setup for the global variable in only a fewprocedures, it is then possible to migrate the same set of automatedprocedures to multiple systems and customize only a few procedures oneach system.

• Automation table usage

For individual automation it is advised to never code statements directly inmain automation table members, and either concatenate a newautomation table member or use %INCLUDE in the existing automationtable structure to allow easier release migration as well as LPAR to LPARmigration.

• Log intrasystem automation

Intrasystem automation that occurs in each system should be logged inthe local automation log. Messages and alerts that are forwarded to afocal point should be logged at both the distributed system and the focalpoint.

It is a good practice to have all procedures driven by automationidentifiable, for example, by name, within the log. The sample set forautomation has each command list write a message to the log that ispreceded by a less-than sign (<). A quick glance at the log enables theoperator to know whether automation has performed some action. Theseindicators provide an audit trail for automation and can also assist inproblem determination in the event of an automation failure.


Chapter 9. Automation example scenarios

This chapter shows automation scenarios of Tivoli NetView for OS/390 andSystem Automation for OS/390. Examples will be automation and recoverytasks of OS/390 subsystems.

9.1 NetView SMTP mail gateway support

NetView V1R3 supports SMTP e-mail with the following prerequisites:

• MVS TCP/IP V3R2 or above.

• SMTP is running in the same LPAR where NetView is running.

E-mail can be sent using the SMTP gateway:

• Based upon the AON Inform policy

• From the NetView command line

• From user-written REXX clists

E-mails using the SMTP gateway can actually be performed fromuser-written code without having to implement the AON Inform policy.

9.1.1 NetView provided samplesThe following samples are provided with NetView V1R3:

• EZLEMAIL - A full screen REXX clist used to create and send e-mail.

There are no facilities for NetView to receive e-mail.

Note

If you plan to use SMTP for sending e-mails from a NetView operatorconsole, SMTP must be active, and the EZLJSMTP sample must beinstalled and customized. EZLJSMTP provides sample JCL used to issueSMTP commands and must be customized to specify your SMTP addressspace name. The sample EZLJSMTP should be copied from the CNMSAMPdata set into your NetView DSIPARM library.

Note


The clist reads operator entered text, builds SMTP e-mail commands, putsthe complete data stream in a PIPE safe, and calls the provided clistmodule, EZLESSMT, to send the e-mail.

• EZLKMAIL - A full screen panel used by EZLEMAIL.

• EZLESSMT - A REXX clist that builds and submits a job to send thee-mail.

• EZLJSMTP - Sample JCL job that sends the e-mail.

This job needs to be customized for the SMTP job name (Figure 122).

• EZLESMTP - A REXX clist that sends e-mail based on the Inform policy.

This sample clist allows one line e-mails to be sent.

9.1.2 Required customizationThe only customization needed to send SMTP e-mail (provided theprerequisites have been met) using the samples provided, is to copy thesample JCL member, EZLJSMTP, into the NetView DSIPARM library, andthen provide the correct SMTP address space name in the SYSOUT field onthe SYSUT2 DD statement. An example is shown in Figure 122 on page 200:

Figure 122. Sample JCL Job EZLJSMTP

//EZLJSMTP JOB (999,AUS),'NVSMTP',CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),// REGION=0M,TIME=1440//***************************************************************//* *//* Licensed Materials - Property of Tivoli Systems *//* 5697-B82 (C) Copyright Tivoli Systems 1999 *//* All rights reserved. *//* *//* DISTRIBUTED AS MEMBER: EZLJSMTP *//* DESCRIPTION: Sample JCL to allow E-mail to be issued via *//* SMTP. This code will be read by command lists*//* in NetView which will insert the commands to *//* be passed to SMTP. *//***************************************************************//IEBGENER EXEC PGM=IEBGENER//SYSIN DD DUMMY//SYSUT1 DD */*//***************************************************************//* Change smtp below to the SMTP address space name. *//* Change B to the desired SYSOUT class *//***************************************************************//SYSUT2 DD SYSOUT=(B,SMTP),// DCB=(LRECL=80,BLKSIZE=80,RECFM=F,DSORG=PS)//SYSOUT DD SYSOUT=A//SYSPRINT DD SYSOUT=A


9.1.3 Sending SMTP e-mail with EZLEMAILTo send a simple e-mail from a NetView full screen session, enter thefollowing command

EZLEMAIL

on the NetView NCCF interface. A skeleton email form will be displayed,which is then completed as shown in Figure 123:

Figure 123. Skeleton e-mail

After the e-mail text is complete, pressing PF9 or PF5 will submit anEZLJSMTP batch job to send the e-mail.

The e-mail, for example, received in Lotus Notes, will appear as illustrated inFigure 124.

Chapter 9. Automation example scenarios 201

Figure 124. E-mail received in Lotus Notes

9.1.4 Sending SMTP e-mail from AON Inform policiesTo send e-mail from AON Inform policy, using the SMTP mail gateway,requires the correct definition in the AON Inform policy. It provides thefollowing features:

• Message support for one line messages.

• Default message.

• Message can be changed in the Inform policy.

The AON Inform policy requires little customization to send SMTP e-mail. Anexample of a customized AON Inform policy item is shown in Figure 125 onpage 203.

SMTP can only send e-mail. It does not provide pager support.

Note


Figure 125. AON Inform policy item customized for SMTP e-mail

9.1.5 Sending SMTP e-mail from user-written clistsUsers can create their own REXX clists to send SMTP e-mail. The clist willneed to call the provided clist module, EZLESSMT. The following restrictionsapply:

• User code must build a PIPE safe containing the SMTP e-mail commandsand then call the provided clist module, EZLESSMT.

• User code must pass EZLESSMT 2 PIPE safes:

- A safe containing the e-mail commands.

- A safe that will contain messages generated in response to EZLESSMTprocessing and batch job submission.

The clist module EZLESSMT provides the following return codes:

• 0 - Successful completion.• 7 - Variable has no value (AON internal clist error).• 8 - Invalid syntax (AON internal clist error).• 12 - No e-mail commands in passed PIPE safe.

An example of a REXX clist using the provided clist module EZLESSMT isshown in Figure 126.

* ** POLICY for CHIEF ** ** The Chief is available weekdays 9 - 5 ** *INFORM CHIEF;CONTACT ONCALLDAY=WEEKDAY,

ONCALLTIME=09:00 TO 17:00,SP=DUMMY,CONNECTION=EMAIL,[email protected],INTERFACE=EZLESMTP,NAME=BILL CLINTON;

* *


Figure 126. Example REXX using EZLESSMT

9.2 System Automation in a multi-system focal point environment

SDF can be configured so that multiple systems in an automationenvironment can forward their resource status information to the SDF on thefocal point system. In a multi-system environment, the following must bedefined:

• The tree structure for each system must be defined in the AOFTREEmember of NetView DSIPARM on the focal point system SDF. The rootname must be unique for each system tree structure.

/* REXX *//* ------------------------------------------------------------------ *//* *//* REXX TO SEND AN EMAIL USING EZLESSMT *//* *//* ARGS PASSED : *//* EMADDR - THE EMAIL ADDRESS *//* *//* ------------------------------------------------------------------ */Trace rARG emaddr

mail.1 = "Hello SMTP"mail.2 = "Mail from: <"opid()"@"cursys()">"mail.3 = "Rcpt to:<"emaddr">"mail.4 = "Data"mail.5 = "Date: "date('n')" "time()mail.6 = "From: "opid()" - NetView Domain "domain()" - "cursys()mail.7 = "To: "emaddrmail.8 = "Subject: Email using EZLESSMT"mail.9 = "This email was sent from NetView V1R3 using the SMTP email"mail.10 = "gateway. It called EZLESSMT - a supplied sample REXX exec"mail.11 = "."mail.12 = "QUIT"mail.0 = 12

'PIPE STEM MAIL. | SAFE MAILSAFE'

'EZLESSMT MAILSAFE RTRNSAFE'

r_code = rcIf r_code = 0

then text= 'EMAIL sent ok'else text= 'EMAIL failed with rc = 'r_code

'PIPE LIT /'text'/ | CONS'

Exit


• The focal point root name must match the SYSNAME value defined in theautomation policy. This value is specified in the customization dialog.

• For a target system SDF status update to occur on a focal point SDF,System Automation for OS/390 focal point services must already beimplemented.

Because each root name must be unique in a multi system environment, anystatus component on any system defined to the focal point SDF can beuniquely addressed by prefixing the status component with the rootcomponent name:

ROOT_COMPONENT.STATUS_COMPONENT

For example:

SC66.JES2

Similarly, any SDF status descriptors forwarded from the target system to thefocal point SDF are prefixed with the root name of the target system bySystem Automation for OS/390 routines.

To define message forwarding paths between different systems, the followingfeatures should be defined in System Automation:

• Primary focal point

• Backup focal-point (if required)

• Target systems

• Gateway sessions (between connected systems)

In addition to these definitions, it is necessary to modify some definitions inthe DSIOPF and DSIDMN members in the DSIPARM library.

9.2.1 Defining Automation Network processThe message forwarding paths between the connected systems must bedefined, and some modifications have to be performed to the definitions in theDSIOPF and DSIDMN members in the NetView DSIPARM library.

The SYSNAME for each system under System Automation for OS/390control must be the same as the system name under which the system wasIPLed.

Note


The following steps will describe the process to customize the focal pointservices in the System Automation process. For further information, refer toChapter 9, "Automating Networks" of System Automation for OS/390 V1R3Customization, GC28-1566.

The first step is to define the outbound gateway autotasks that will beresponsible in establishing and maintaining all connections to other systems.It is their function to send messages, commands, and responses to one ormore systems.

9.2.1.1 Defining the outbound gateway autotasksFrom the System Automation Entry Type Selection, shown in Figure 127 onpage 206, select the AOP or 37 (Auto Operators) option to enter the AutoOperator Entry Selection panel displayed in Figure 128 on page 207.


Select, one after another, the focal system and the target systems’ autooperators that will be used in the automation environment.







Figure 128. SA OS/390 Auto Operators Entry Selection panel

First, start with the focal point system and select the FOCAL_OPERS optionto enter the Auto Operator Policy Selection panel as shown in Figure 129.

Figure 129. SA OS/390 Auto Operators Policy Selection panel

From the Auto Operators Policy Selection panel, select the OPERATORSoption to display the Automation Operator Definitions panel shown in Figure130.

SA OS/390 Entry Selection Row 6 from 17Command ===> SCROLL===> CSR

Entry Type : Auto Operators PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short DescriptionBACKUP_OPERS Backup FP specific auto opersBASE_AUTOOPS Default automation operatorsBASE_AUTOOPS_IO Automation operators with I/O monitoring

S FOCAL_OPERS Focal point specific auto operatorsS TARGET1_OPERS Target1 specific auto opersS TARGET2_OPERS Target2 specific auto opers******************************* Bottom of data ********************************

F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE


Entry Type : Auto Operators PolicyDB Name : ITSO_ENTERPRISEEntry Name : FOCAL_OPERS Enterprise Name : ITSO_ENTERPRISE

Action Policy Name Policy DescriptionDESCRIPTION Enter description

S OPERATORS Define automation operators-------------------- ---------------------------------------------WHERE USED List Systems linked to this entryCOPY Copy data from an existing entry

******************************* Bottom of data ********************************


Figure 130. SA OS/390 Auto Operators Automation Operator Definitions panel

If GATOPER has not previously been defined, type the automation operatorname, GATOPER, in the Automated Function field. It is not necessary tospecify any messages for GATOPER. The Automation Operator NetViewUserids panel is displayed automatically as illustrated in Figure 131.

If GATOPER has previously been defined, then select it by entering an S inthe ACTION column.

Figure 131. SA OS/390 Automation Operator NetView Userids panel

In the Automation Operator NetView Userids panel, enter the value for theautotask, which is in the ITSO project environment, the name GATSC66A, todefine the outbound gateway autotask for system SC66.

Automation Operator Definitions Row 1 to 10 of 21Command ===> SCROLL===> CSR


Actions: S = Select M = Move B = Before A = After I = Insert

AutomatedAction Function Messages for this Operator (* notation ok)S GATOPER

Automation Operator NetView UseridsCommand ===>


Automated Function: GATOPERMessages assigned:

Enter automation operators and NetView operator(s) to receive messages.

Automation Operators NetView OperatorsPrimary ==> GATSC66A ==>Backup ==> ==>

==>==>==>==>


To define the target outbound gateways’ autotasks, repeat the previous stepsfor all of the target systems.

9.2.1.2 Defining gateway sessions with other systemsFrom the System Automation Entry Type Selection shown in Figure 132,select the NTW or 39 (Network) option to enter the Network Entry Selectionpanel displayed in Figure 133 on page 210.


The following steps will also be necessary for each of the target system afterdefinitions for the focal point system are completed.

From the Network Entry Selection panel, select the FOCAL_NETWORKoption to enter the Network Policy Selection panel.

On this Network Policy Selection panel, select the FORWARD option todisplay the Notification Forwarding panel shown in Figure 134 on page 210.







Figure 133. SA OS/390 Network Entry Selection panel

Figure 134. SA OS/390 Notification Forwarding panel

Define the focal point domain and backup focal point domain.

In the ITSO environment, only a primary focal point system was defined;however, it is recommended to define both primary focal point and backupfocal point. The backup will be always used when the primary focal pointbecomes unavailable.

This step is optional for the focal point definition because System Automationfor OS/390 considers the current system as the primary focal point anddisplays messages without forwarding them. This will occur if the forwardfocal point is not defined in the automation policy for the system, or thesystem specified in a forward focal point definition is the current system.

After completion of this step, continue to define the gateway sessionsbetween the systems.


Entry Type : Network PolicyDB Name : ITSO_ENTERPRISEEnterprise Name : ITSO_ENTERPRISE

Action Entry Name C Short Descriptions FOCAL_NETWORK Focal point network structure

TARGET_NETWORK Target network structure******************************* Bottom of data ********************************

SA OS/390 Notification ForwardingCommand ===>

Entry Type : Network PolicyDB Name : ITSO_ENTERPRISEEntry Name : FOCAL_NETWORK Enterprise Name : ITSO_ENTERPRISE

Enter the NetView domains for automation notification forwarding.

Primary Domain ==> SC66A Current Domain IDBackup Domain ==> Backup Domain ID


Return to the Network Policy Selection panel, shown in Figure 135, andselect the GATEWAY option.

Figure 135. SA OS/390 Network Policy Selection panel

The GATEWAY option will display the Gateway Definition panel illustrated inFigure 136.

Figure 136. SA OS/390 Network Gateway Definitions panel

On the Gateway Definition panel for the focal point and the backup focal pointsystems, enter the target domains to which the gateways sessions will beestablished.



Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionADJACENT NETVIEW Define adjacent NetViewFORWARD Define forward focal pointFULL SESSIONS Define TAF sessions (Applications)

S GATEWAY Define gatewaysSAF ENVIRONMENT Define System Authorization Facility (SAF)-------------------- ---------------------------------------------WHERE USED List Systems linked to this entryCOPY Copy data from an existing entry

******************************* Bottom of data ********************************

SA OS/390 GATEWAY Definitions Row 1 to 9 of 22Command ===> SCROLL===> CSR


Enter the following information for each NetView domain that commands orresponses are forwarded to. Use RACFNNT as the password if SA OS/390 isto retrieve the password from RACF.

Domain Password Logmode DescriptionSC42A GATEWAY Gateway to target SC42SC69A GATEWAY Gateway to target SC69


On the Gateway Definition panel for the target systems, enter the focal pointdomain and backup focal point domain.

Put either a password for the gateway operator or the value, RACFNNT, in thepassword field. If RACFNNT is entered, it will enable the use of the SAOS/390 password facility (see Section 9.2.1.3, “Considerations for the SApassword protection feature” on page 213). In the ITSO project, thepassword, GATEWAY, was chosen.

After completion of this step, continue to define where the focal point andtarget definitions will be used.

Return to the Network Policy Selection panel, shown in Figure 137, andselect the WHERE USED option.

Figure 137. SA OS/390 Network Policy Selection panel

The following Where Used panel will be displayed for selection of theparticular focal point system. In this example, SC66 is selected.



Action Policy Name Policy DescriptionDESCRIPTION Enter descriptionADJACENT NETVIEW Define adjacent NetViewFORWARD Define forward focal pointFULL SESSIONS Define TAF sessions (Applications)GATEWAY Define gatewaysSAF ENVIRONMENT Define System Authorization Facility (SAF)-------------------- ---------------------------------------------

S WHERE USED List Systems linked to this entryCOPY Copy data from an existing entry

******************************* Bottom of data ********************************


Figure 138. SA OS/390 Network Where Used panel

After completion of these definition steps for the focal point, backup focalpoint, and all target systems, rebuild the SA Automation Control File (ACF)and modify the DSIOPF and DSIDMN members to include the correctgateway userids (autotasks) and RRD definitions.

Refer the Appendix B, “System Automation V1R3 members and jobs” on page233 for further information about the statements changed in these members.

The last step is to recycle the NetView applications to reflect the newdefinitions and establish the gateways’ sessions.

9.2.1.3 Considerations for the SA password protection featureThe System Automation password protection is an optional feature that allowsSystem Automation to use a Security Authorization Facility (SAF) program,such as RACF or a functionally equivalent product, to manage gatewayoperator IDs and passwords. This feature is intended for systems thatestablish gateway sessions with two or more systems.

System Automation password protection feature involves the SystemAutomation password data set and the SAF program. The System Automationpassword data set contains only gateway operator ID and password entries.The SAF program manages all user IDs and their passwords, includinggateway operator IDs and their passwords.

Consider the following issues if planning to install the System Automationpassword protection feature:

• For an automation environment to use the System Automation passwordprotection feature, all systems in the automation environment must installthis feature.

SA OS/390 Where Used Row 1 to 3 of 3Command ===> SCROLL===> CSR


Action Status Entry Name Entry TypeSC42 SYS

SELECTED SC66 SYSSC69 SYS

******************************* Bottom of data ********************************


• A SAF program must be installed on all systems in the automationenvironment that are using the System Automation password protectionfeature.

• The number of gateway sessions each system in the automationenvironment establishes with other systems.

• Decide whether each system in the automation environment will have itsown SAF product data set, or whether several systems will share onepassword data set.

Refer to System Automation for OS/390 V1R3 Customization, GC28-1566,for more information about shared SAF data sets.

For a detailed description of how to define the System Automation passwordprotection feature, refer to Appendix 1.1.3 “Installing the SA/MVS PasswordProtection Feature” in System Automation for OS/390 V1R3 Planning andInstallation, GC28-1549.

9.3 Using NetView AON inform policies by System Automation

This section introduces the AON Inform policy, and describes how it can beimplemented in a System Automation NetView.

The AON Inform policy, provides a simple way to perform automatic eventnotification and escalation. It can be easily customized to support SMTPe-mail or other paging/e-mail gateways.

Samples are supplied within AON to support pager and e-mail communicationvia the service point Netfinity for OS/2. Refer to the Netfinity for OS/2 productdocumentation for setting up the required service point communication toTivoli NetView for OS/390.

As an example, the SMTP e-mail support is detailed in Section 9.1, “NetViewSMTP mail gateway support” on page 199. For an example of interfacingother e-mail software, see the ITSO redbook An Introduction to Tivoli NetViewfor OS/390 V1R2, SG24-5224.

Inform processing can be implemented on a System Automation NetViewwithout having to install any other AON code or functions.

9.3.1 Installation of AON inform policy in the Automation NetViewTo install AON Inform policy support, the following is required:


1. In the Automation NetView start-up procedure, check that the followingdataset concatenations are uncommented:

-STEPLIB:

// DD DSN=&SQ1..SEZLLINK,DISP=SHR

-DSICLD:

// DD DSN=&SQ1..SEZLCLST,DISP=SHR

-CNMPNL1:

// DD DSN=&Q1..&DOMAIN..SEZLPNLU,DISP=SHR

// DD DSN=&SQ1..SEZLPNLU,DISP=SHR

2. Check that the following INCLUDE statement is uncommented in theDSICMDM member of DSIPARM library:

%INCLUDE EZLCMDI

9.3.2 Inform policy customizingThe Inform policy is used to define who should be and how they should becontacted, when critical situations arise. Logically, the Inform policy is dividedinto individual contacts and groups of contacts. This enables different peopleto be contacted for an event, depending on the time that event happens,without having to work this out before the call to the Inform policy.

A sample Inform policy, EZLINSMP, is provided. The Inform policy containsthe following statements:

• SETUP

Several AON functions, such as INFORM, AUTOMAN, TIMER, SMTP e-mail,and TCP/IP commands, can be run without other AON automationfunctions being active. The above steps will enable all of these functions.

The AON TIMER functions and the SA/390 TIMER functions cannot runsimultaneously in the same operating system environment. The default is theAON TIMER function.

Refer to the Tivoli NetView for OS/390 Automated Operations NetworkUsers Guide, GC31-8661, for further details.

For further detailed compatibility information and the latest System AutomationAPAR for NetView V1R3 toleration refer to Appendix A, “NetView 1.3 tolerationfor System Automation 1.3” on page 231.

Note


Defines connection types and enables logging.

• INFORM

Gives a label to an inform policy that consists of a contact or list ofcontacts.

• CONTACT

Defines the criteria used to determine who is contacted and how.

• GROUP

Specifies a list of policies that form a logical group.

Refer to Chapter 4 in the Tivoli NetView for OS/390 Administration Reference,SC31-8222, for further coding and parameter details for the Inform policystatements.

An example of AON Inform policy statements is shown in Figure 139 on page217.


Figure 139. Example of AON Inform policy statements

9.3.3 Calling the Inform policyAfter the Inform policy has been customized, it needs to be loaded intoNetView before it can be accessed. The following two ways show how to loadand activate the Inform policy:

1. From a networking NetView (running AON), it can be loaded at AONcontrol file load by modifying the ENVIRON SETUP parameter in the AONcontrol file EZLCFG01 to include the statement

INFORMPM=EZLINSMP

(where EZLINSMP is the Inform policy member name)

2. From any NetView (running AON or SA), by issuing the following commandat the NetView NCCF interface:

* Add a setup statement, to define other connection types and ** enable logging. Specify log member name INFLOG, by default EZLIFLOG ** would be used. ** *SETUP CONNECTIONS=FAX,LOG=YES,MEMBER=INFLOG;* *GROUP NITEOPS,LIST=PERSONC;GROUP WEEKENDS,LIST=PERSONC,PERSOND;** ** POLICY for PERSONC ** ** PersonC is available every evening by EMAIL and additionally by ** Pager on the weekends. ** *INFORM PERSONC,SP=SP000002;CONTACT ONCALLDAY=*,

ONCALLTIME=16:00 TO 24:00,CONNECTION=EMAIL,INTERFACE=EZLESMTP,[email protected],NAME=C. PERSON;

CONTACT ONCALLDAY=WEEKEND,ONCALLTIME=16:00 TO 24:00,CONNECTION=ALPHAPAGE,ROUTE=6127555,NAME=C. PERSON,INTERFACE=EZLENETF,TAPACCESS=918007596366;

* ** POLICY for PERSOND ** ** PersonD is always available on Weekends by Pager. ** *INFORM PERSOND,SP=SP000002;CONTACT ONCALLDAY=WEEKEND,

CONNECTION=ALPHAPAGE,INTERFACE=EZLENETF,TAPACCESS=9-1-800-555-5555,ROUTE=1231111,NAME=D. PERSON;


INFORMTB EZLINSMP

(where EZLINSMP is the Inform policy member name)

The actual Inform policy is called by issuing the following INFORM command:

INFORM Policy_name Message

where

- Policy_name: Either an Inform policy name or Inform group name- Message: The message to be sent

The command can be issued from a NetView NCCF screen, a REXX clist, orcalled from the AON and System Automation control files.

9.3.4 Calling AON Inform policy from System AutomationThe following example shows the System Automation configuration andInform policy member definitions to perform automatic notification.

9.3.4.1 Example scenarioA DB2 subsystem, DB2AMSTR, is defined to System Automation. TheSystem Automation definition includes a call to the Inform policy ifDB2AMSTR goes to BROKEN status.

The Inform policy member contains Inform policy statements to do thefollowing notifications:

• If DB2AMSTR goes to BROKEN status between 9:00 A.M. and 5:00 P.M.,Monday to Friday, the following receivers are to be notified:

- The duty systems programmer via pager

- The help desk via e-mail and pager

- The Customer Service Manager via pager

• If DB2AMSTR goes to BROKEN status outside of the regular workinghours, the following receivers are to be notified:

- The duty systems programmer via pager

- The help desk via e-mail

In a System Automation NetView, the AON control file will not be loaded, somethod 2 must be used. This command could be issued from anAUTOTASK at System Automation control file load.

Note


- The Customer Service Manager via email

9.3.4.2 Definition and implementation processTo implement the above scenario, the following steps need to be performed:

a. Add the correct definitions to the System Automation control file andrebuild it.

b. Reload the automation control file (ACF) within the System AutomationNetView.

c. Add the correct definitions to the Inform policy member.

d. Load the Inform policy member into the System Automation NetView.

9.3.4.3 System Automation definitionsDB2AMSTR is defined to the System Automation policy database as aregular application running on system SC42. To trigger the automatic informprocessing, some additional definitions have to be performed in order to callthe Inform policy when DB2AMSTR goes to BROKEN status. This is achievedby using the System Automation facility to trigger commands on statuschange.

For detailed information, refer to Chapter 10, “How Automation Routines CanBe Triggered” in System Automation for OS/390 Customization, GC28-1566.

For this example using Inform policies, return to the System Automation EntryType Selection panel and select option APL or 6 (Application). On theApplication Entry Type Selection panel, select the defined application,DB2AMSTR, to enter the Application Policy Selection panel as shown inFigure 140 on page 220.


Figure 140. Selecting the MESSAGES option

Select the MESSAGES option to define specific message handling forDB2AMSTR. The Message Policy panel will be displayed as illustrated inFigure 141.

Figure 141. Calling a command from BROKEN status

In the Message Policy panel, enter the Action keyword CMD, the Message IDkeyword BROKEN, and a short description.


Entry Type : Application PolicyDB Name : POLICY_DBEntry Name : DB2AMSTR Enterprise Name : ITSO_ENTERPRISE


S MESSAGES Define Application messagesSHUTDOWN Define shutdown proceduresTHRESHOLDS Define error thresholdsRESTART Define commands executed at restartMINOR RESOURCES Define Application sub-component flags



Resource: DB2AMSTR



CMD BROKEN Invoke callout


Figure 142. Coding the INFORM command

In the following CMD Processing panel, shown in Figure 142, enter theINFORM command and the specific parameter that need to be passed to theInform policy for this example.

After completion of this definition to the System Automation policy database,rebuild the automation control file (ACF) and reload it in the AutomationNetView.

9.3.4.4 Inform policy definitionsFor the example of Inform policy notifications when DB2AMSTR goes tostatus BROKEN, the following Inform policy INFORM/CONTACT definitionsfor the DB2 systems programmers have to be performed as shown in Figure143 on page 222.



Resource: DB2AMSTRMessage ID: BROKEN



Command Text1 INFORM DB2PROB DB2AMSTR IS BROKEN


Figure 143. INFORM/CONTACT definitions for DB2 Systems Programmers

As second action, the following Inform policy INFORM/CONTACT definitionsfor the Help Desk have to be performed as shown in Figure 144 on page 223.

* ** POLICY for DB2SP (DB2 Systems Programmers) ** ** The inform policy for DB2SP indicates that there are 2 separate ** contacts depending on the day/time. ** ** The prime time contact is John Smith who is on pager# 0123456789 ** The out of hours contact is Fred Bloggs who is on pager# 9876543210 ** *INFORM DB2SP,SP=SP000002;CONTACT ONCALLDAY=WEEKDAY,

ONCALLTIME=09:00 to 17:00,CONNECTION=ALPHAPAGE,INTERFACE=EZLENETF,TAPACCESS=9-1-800-555-5555,ROUTE=0123456789,NAME=JOHN SMITH;

CONTACT ONCALLDAY=WEEKDAY,ONCALLTIME=17:00 to 24:00,CONNECTION=ALPHAPAGE,INTERFACE=EZLENETF,TAPACCESS=9-1-800-555-5555,ROUTE=9876543210,NAME=FRED BLOGGS;

CONTACT ONCALLDAY=WEEKDAY,ONCALLTIME=00:01 to 09:00,CONNECTION=ALPHAPAGE,INTERFACE=EZLENETF,TAPACCESS=9-1-800-555-5555,ROUTE=9876543210,NAME=FRED BLOGGS;

CONTACT ONCALLDAY=WEEKEND,CONNECTION=ALPHAPAGE,INTERFACE=EZLENETF,TAPACCESS=9-1-800-555-5555,ROUTE=9876543210,NAME=FRED BLOGGS;


Figure 144. INFORM/CONTACT definitions for Help Desk

As third action, the Inform policy INFORM/CONTACT definitions for theCustomer Service Manager have to be performed as shown in Figure 145:

Figure 145. INFORM/CONTACT definitions for Customer Service Manager

* POLICY for HDESK (Help Desk) ** HDESK is available during the prime time via pager# 1122334455 and ** email, and out of hours via email only. ** *INFORM HDESK,SP=SP000002;CONTACT ONCALLDAY=WEEKDAY,

ONCALLTIME=09:00 to 17:00,CONNECTION=ALPHAPAGE,INTERFACE=EZLENETF,TAPACCESS=9-1-800-555-5555,ROUTE=1122334455,NAME=HELP DESK;

CONTACT ONCALLDAY=*,CONNECTION=EMAIL,INTERFACE=EZLESMTP,[email protected],NAME=HELP DESK;

* *

* POLICY for CSMGR (Customer Service Manager) ** CSMGR is available in prime time via pager# 66778899, and out of ** hours via email. ** *INFORM CSMGR,SP=SP000002;CONTACT ONCALLDAY=WEEKDAY,

ONCALLTIME=09:00 to 17:00,CONNECTION=ALPHAPAGE,INTERFACE=EZLENETF,TAPACCESS=9-1-800-555-5555,ROUTE=66778899,NAME=CS MANAGER;

CONTACT ONCALLDAY=WEEKDAY,ONCALLTIME=17:00 to 24:00,CONNECTION=EMAIL,INTERFACE=EZLESMTP,[email protected],NAME=CS MANAGER;

CONTACT ONCALLDAY=WEEKDAY,ONCALLTIME=00:01 to 09:00,CONNECTION=EMAIL,INTERFACE=EZLESMTP,[email protected],NAME=CS MANAGER;

CONTACT ONCALLDAY=WEEKEND,CONNECTION=EMAIL,INTERFACE=EZLESMTP,[email protected],NAME=CS MANAGER;


The last action is to specify the Inform policy GROUP definition, whichlogically groups the contacts to the group DB2PROB:

Figure 146. Inform policy group definition

When all of the above definitions have been performed, load the Inform policymember into the System Automation NetView using the NetView command

INFORMTB <Inform policy member>

where <Inform policy member> represents the customized Inform policymember for this example.

9.3.4.5 System Automation processingIf the application DB2AMSTR goes to status BROKEN, System Automationwill execute the INFORM command to call the Inform policy.

The Inform policy will ensure that a notification will automatically be sent tothe correct people. The text of the notification in e-mail and on the pager willbe:

“DB2AMSTR IS BROKEN”

9.4 Brief comparison of NMC and SDF Consoles

The NetView Management Console (NMC) graphically displays the resourcesthat represent a network, a portion of a network, a system application, asubsystem, or a group of networks and/or subsystems at various levels ofdetail. These graphical views show the network and system resource objects,which are managed by the Networking (AON) or Automation (SA) NetView.When monitoring a network or system, resource status changes are reflecteddynamically in the graphical views.

* ** DB2PROB is the group of people to be informed of DB2 problems. ** *GROUP DB2PROB,LIST=DB2SP,HDESK,CSMGR;* *

Grouping simplifies the need to duplicate CONTACT entries under morethan one INFORM group.

Note


The Status Display Facility (SDF) is a System Automation function residingwithin the Automation NetView, that is used to monitor system resources onthe current system as well as on other target systems in 3270 sessionscreens. The resources are monitored by noting different colors to reflecttheir current status. When monitoring system resources, resource statuschanges are updated dynamically in the SDF 3270 screens.

Comparing the SDF with the NMC implementation, SDF is easy and quickerto setup and maintain. SDF does not need RODM or GMFHS to provide itsresource information, just the base Automation (SA) NetView. It only providesinformation about system resources managed by the Automation (SA)NetViews.

On the other hand does the NMC provide by far more powerful display andcommand functions, including online status refresh for all managed networkand system objects, as well as Network and System Automation commandsupport directly from NMC topology console.

9.5 Example NMC screens of the ITSO project scenario

The following section will show some NMC screen shots and examplesderived from the actual ITSO project implementation to monitor systemresources.

As mentioned in Chapter 5.3, “Defining all systems and objects to SystemAutomation” on page 60, the System Automation policy database for theentire enterprise should contain all the object information that SystemAutomation uses to produce the RODM objects (RODM load file). Theseobjects represent the displayed graphical objects in the NMC views forSystem Automation.

A thoughtful planning for creation of the object hierarchy and how to group theresources will have a great impact on how powerful the System Automationfor OS/390 graphic interface will be.

The chart in Figure 147 exemplifies again the monitoring hierarchy for thevarious System Automation objects used in this ITSO project. It was decidedto group the systems by geographical region and type of applications.


Figure 147. Example of ITSO Enterprise Monitoring Hierarchy

The following collection of screen shots from Figure 148 to Figure 153 onpage 229 demonstrate how the actual NMC System Automation views looklike. The background pictures were added for demonstration purpose.


Figure 148. NMC System Automation ITSO Enterprise object

Figure 149. NMC System Automation group objects


Figure 150. NMC System Automation subgroup objects

Figure 151. NMC System Automation system object


Figure 152. NMC System Automation application group objects

Figure 153. NMC System Automation application screen example



Appendix A. NetView 1.3 toleration for System Automation 1.3

Since Tivoli NetView for OS/390, NetView AON and System Automation havecommon usage of several commands and synonyms. A System Automationfor OS/390 APAR, OW42022, will be available by end of January 2000 toallow better coexistence of System Automation for OS/390 V1R3 running onTivoli NetView for OS/390 V1R3. The addressed items are:

• Toleration of command CHRON

CHRON timers set by operators:

- Display and delete function allowed

- Edit function rejected

• AOFCMD - Synonyms

SETTIMER:

Deletion of the two undocumented SA synonyms

- TIMER

- TIMERS

due to the compatibility problem with the TIMER command of TivoliNetView V1R3.

• EXIST

DOC / ++HOLD ACTION:

Manually remove or remark ( /* ... */ ) invocation of the EXIST functionwhen using Tivoli NetView V1R3. Otherwise, a duplicate invocation willoccur, and a warning message will be displayed.

• AON

Is per default activated in Tivoli NetView V1R3.


Make sure AON is disabled, and everything, except the commandEZLCMDI, which still has to be included in DSICMD, is removed orremarked (/*...*/). The EZLCMDI command is now part of Tivoli NetViewfor OS/390 V1R3 and no longer part of AON, even though its modulename still begins with EZL.

• NetView CLIST CNME1035

Invoked by initial msg load AOFMSG00 by earlier versions of TivoliNetView for OS/390. Since it is in Tivoli NetView OS/390 V1R3 integrated


into the NetView Clist, CNME1034, the following changes need to bedone.


Remove or remark ( /* ... */ ) the invocation of CNME1035 in memberAOFMSG00.

This notice is a reminder that the clist, CNME1035, is no longer used byTivoli NetView for OS/390 V1R3 as the initial NetView PPT startup clist.Please check for any self-written customizations and move appropriatemodifications to the new NetView PPT start-up clist CNME1034.

Note


Appendix B. System Automation V1R3 members and jobs

The following tables Table 26 and Table 27 on page 234 specify the definedapplications, application groups, and classes within the ITSO project.

Table 26. Applications defined in the ITSO Enterprise policy database

APPLICATION APPLICATION GROUP

ASCH OPERATIONS

APPC OPERATIONS

IO_OPERATIONS OPERATIONS

JES2 OPERATIONS

LLA OPERATIONS

NETWORK_GMFHS NETWORK

NETWORK_NETVIEW NETWORK

NETWORK_NETVIEW_SSI NETWORK

NETWORK_RODM NETWORK

PROCESSOR_OPERATIONS OPERATIONS

SAOS390_GMFHS SC66_GENERIC

SAOS390_NETVIEW SA_OS390

SAOS390_NETVIEW_SSI SA_OS390

SAOS390_RODM SA_OS390

SAOS390_RODM_DM SA_OS390

TSO OPERATIONS

VLF OPERATIONS

VTAM NETWORK

TSO OPERATIONS


Table 27. Classes defined in the ITSO Enterprise policy database

B.1 Other System Automation jobs and definitions

The following sections contain the actual sample procedures/jobs of the ITSOproject.

CLASS APPLICATIONS RELATED

GENERIC_CLASS This is a generic class application. It should be usedwith generic and local applications that will sharethe same definitions like shutdown commands,restart thresholds and others.

GMFHS_CLASS SAOS390_GMFHS and NETWORK_GMFHS

NETVIEW_CLASS SAOS390_NETVIEW and NETWORK_NETVIEW

RODM_CLASS SAOS390_RODM and NETWORK_RODM


B.1.1 Automation NetView start-up procedure

//AOFAPPL PROC Q1='NETVUSER', ** USER DSN HIGH LEVEL QUALIFIER// DOMAIN=SC&SYSCLONE.A, ** NETVIEW DOMAIN NAME// DOMAINPW='', ** NETVIEW DOMAIN PASSWORD// PROG=DSIMNT, ** PGM FOR AUTOMATION NETVIEW// SQ1=NETVIEW.V1R3M0, ** SYSTEM DSN HIGH LEVEL QUALIFIER// SQ2=ING, ** SYSOPS DSN HIGH LEVEL QUALIFIER// VQ1=NETVUSER, ** HIGH LVL DSN QUALIFIER-VSAM DSNS// VQ2=ING.USER, ** SYSOPS HIGH LVL DSN QUALIFIER-VSAM// SOUTA='*', ** DEFAULT PRINTED OUTPUT CLASS// REG=4096, ** REGION SIZE(IN K) FOR MAIN TASK// BFSZ=24, ** BUFFER SIZE(IN K)// SLSZ=200, **// ARM='*NOARM', ** NETVIEW AUTOMATIC RESTART (ARM) USAGE// SUBSYM='' ** NETVIEW SYMBOLIC SUBSTITUTION SWITCH//**********************************************************************//AOFAPPL EXEC PGM=&PROG,TIME=1440,// REGION=&REG.K,// PARM=(&BFSZ.K,&SLSZ,'&DOMAIN','&DOMAINPW','&ARM','&SUBSYM'),// DPRTY=(13,13)//DSICLD DD DSN=&Q1..&DOMAIN..CNMCLST,DISP=SHR// DD DSN=&Q1..SYSTEM.CNMCLST,DISP=SHR// DD DSN=&SQ2..SINGNREX,DISP=SHR// DD DSN=&SQ1..CNMCLST,DISP=SHR// DD DSN=&SQ1..CNMSAMP,DISP=SHR// DD DSN=&SQ1..SEZLCLST,DISP=SHR// DD DSN=&SQ1..SEKGSMP1,DISP=SHR//DSIOPEN DD DSN=&Q1..&DOMAIN..SDSIOPEN,DISP=SHR// DD DSN=&Q1..SYSTEM.SDSIOPEN,DISP=SHR// DD DSN=&Q1..&DOMAIN..SDSIOPEN,DISP=SHR// DD DSN=&SQ1..SDSIOPEN,DISP=SHR//DSIPARM DD DSN=&Q1..&DOMAIN..DSIPARM,DISP=SHR// DD DSN=&Q1..SYSTEM.ACF,DISP=SHR// DD DSN=&Q1..SYSTEM.DSIPARM.ENTERP,DISP=SHR// DD DSN=&Q1..SYSTEM.DSIPARM,DISP=SHR// DD DSN=&SQ2..SINGNPRM,DISP=SHR// DD DSN=&SQ1..DSIPARM,DISP=SHR//DSILIST DD DSN=&Q1..&DOMAIN..DSILIST,DISP=SHR//DSIVTAM DD DSN=&Q1..&DOMAIN..VTAMLST,DISP=SHR//* DD DSN=SYS1.VTAMLST,DISP=SHR//DSIPRF DD DSN=&Q1..&DOMAIN..DSIPRF,DISP=SHR// DD DSN=&Q1..SYSTEM.DSIPRF,DISP=SHR// DD DSN=&SQ2..SINGNPRF,DISP=SHR// DD DSN=&SQ1..DSIPRF,DISP=SHR//DSIMSG DD DSN=&SQ2..SINGNMSG,DISP=SHR// DD DSN=&SQ1..SDSIMSG1,DISP=SHR//BNJPNL1 DD DSN=&SQ1..BNJPNL1,DISP=SHR//BNJPNL2 DD DSN=&SQ1..BNJPNL2,DISP=SHR//CNMPNL1 DD DSN=&SQ2..SINGNPNL,DISP=SHR// DD DSN=&SQ1..CNMPNL1,DISP=SHR// DD DSN=&SQ1..SEZLPNLU,DISP=SHR// DD DSN=&SQ1..SEKGPNL1,DISP=SHR

Appendix B. System Automation V1R3 members and jobs 235

Figure 154. Common SA OS/390 start-up procedure

//*******************************************************************//* SYSOPS AUTOMATION STATUS FILE//*******************************************************************//AOFSTAT DD DSN=&VQ2..&DOMAIN..STATS,DISP=SHR//*******************************************************************//* SYSOPS SAF PASSWORD DATASET FOR GATEWAY OPERATORS//*******************************************************************//*AOFPSWD DD DSN=&VQ2..&DOMAIN..PASSWORD,DISP=SHR,AMP=AMORG//*******************************************************************//* NETVIEW LOG DATASETS//*******************************************************************//DSILOGP DD DSN=&VQ1..&DOMAIN..DSILOGP,// DISP=SHR,AMP='AMORG,BUFNI=10,BUFND=5'//DSILOGS DD DSN=&VQ1..&DOMAIN..DSILOGS,// DISP=SHR,AMP='AMORG,BUFNI=10,BUFND=5'//*******************************************************************//* TRACE LOG DATASETS//*******************************************************************//DSITRCP DD DSN=&VQ1..&DOMAIN..DSITRCP,// DISP=SHR,AMP=AMORG//DSITRCS DD DSN=&VQ1..&DOMAIN..DSITRCS,// DISP=SHR,AMP=AMORG//*******************************************************************//* SESSION MONITOR VSAM DATA BASES//*******************************************************************//AAUVSPL DD DSN=&VQ1..&DOMAIN..AAUVSPL,DISP=SHR,AMP='AMORG'//AAUVSSL DD DSN=&VQ1..&DOMAIN..AAUVSSL,DISP=SHR,AMP='AMORG'//********************************************************************//* HARDWARE MONITOR VSAM DATA BASES//********************************************************************//BNJLGPR DD DSN=&VQ1..&DOMAIN..BNJLGPR,DISP=SHR,AMP=AMORG//BNJLGSE DD DSN=&VQ1..&DOMAIN..BNJLGSE,DISP=SHR,AMP=AMORG//********************************************************************//* 4700 SUPPORT FACILITY VSAM DATA BASES//********************************************************************//BNJ36PR DD DSN=&VQ1..&DOMAIN..BNJ36PR,DISP=SHR,AMP=AMORG//BNJ36SE DD DSN=&VQ1..&DOMAIN..BNJ36SE,DISP=SHR,AMP=AMORG//********************************************************************//* CENTRAL SITE CONTROL FACILITY VSAM DATA BASE//********************************************************************//DSIKPNL DD DSN=&VQ1..&DOMAIN..DSIKPNL,DISP=SHR,AMP=AMORG//********************************************************************//* SAVE/RESTORE FACILITY VSAM DATA BASE//********************************************************************//DSISVRT DD DSN=&VQ1..&DOMAIN..DSISVRT,DISP=SHR,AMP=AMORG//********************************************************************//CNMMSGF DD DUMMY//CNMCMDF DD DUMMY//SYSPRINT DD SYSOUT=&SOUTA


B.1.2 System Automation RODM procedure

Figure 155. Common SA RODM start-up procedure

//*********************************************************************//* AUTOMATION RODM//*********************************************************************//RODMA PROC SQ1='NETVIEW.V1R3M0', ** SYSTEM DSN HIGH LEVEL QUALIFIER// VQ1='NETVUSER.&SYSNAME.A, ** HIGH LVL DSN QUALIFIER-VSAM DSNS// TYPE=COLDFORC, ** SELECT A COLD OR WARM START// NAME=RODM&SYSCLONE.A,// INIT=EKGLISLM,// CLRSSB=NO,// CUST=EKGCUST,// ARM=*NOARM, ** AUTOMATIC RESTART MANAGER OPTION// SUBSYM=*SUBSYM ** SYMBOL SUBSTITUTION OPTION//*********************************************************************//START EXEC PGM=EKGTC000,REGION=0K,TIME=1440,// PARM='&TYPE,&NAME,&INIT,&CLRSSB,&CUST,&ARM,&SUBSYM'//SYSPRINT DD SYSOUT=*//SYSABEND DD SYSOUT=*//SYSDUMP DD SYSOUT=*//SYSTERM DD SYSOUT=*//EKGLOGP DD DSN=&VQ1..EKGLOGP,DISP=SHR,// AMP=('BUFND=10')//EKGLOGS DD DSN=&VQ1..EKGLOGS,DISP=SHR,// AMP=('BUFND=10')//EKGCUST DD DSN=NETVUSER.SYSTEM.DSIPARM,DISP=SHR// DD DSN=&SQ1..DSIPARM,DISP=SHR// DD DSN=&SQ1..SEKGSMP1,DISP=SHR//EKGLANG DD DSN=&SQ1..SEKGLANG,DISP=SHR//*********************************************************************//* RODM CHECKPOINT DATASETS *//*********************************************************************//*EKGMAST DD DSN=&VQ1..EKGMAST,DISP=SHR//*EKGTRAN DD DSN=&VQ1..EKGTRAN,DISP=SHR//*EKGD001 DD DSN=&VQ1..EKGCK001,DISP=SHR//*EKGD002 DD DSN=&VQ1..EKGCK002,DISP=SHR//*********************************************************************//* UNCOMMENT THESE JCL STATEMENTS IF YOU INTEND TO LOAD *//* RODM DATA STRUCTURE USING AN INITIALIZATION METHOD. *//*********************************************************************//EKGLUTB DD DSN=&SQ1..SEKGLUTB,DISP=SHR//EKGPRINT DD SYSOUT=*//EKGIN2 DD DSN=NETVUSER.SYSTEM.SEKGCAS1,DISP=SHR// DD DSN=&SQ1..SEKGCAS1,DISP=SHR//EKGIN3 DD DUMMY//EKGIN1 DD DSN=&SQ1..CNMSAMP(DUIFSTRC),DISP=SHR// DD DSN=&SQ1..CNMSAMP(FLBTRDMG),DISP=SHR


B.1.3 Automation GMFHS start-up procedure

Figure 156. SA GMFHS start-up procedure used on System SC66

//*********************************************************************//* SA GMFHS STARTUP PROCEDURE//*********************************************************************//GMFHSA PROC Q1='NETVUSER', ** USER DSN HIGH LEVEL QUALIFIER// SQ1='NETVIEW.V3R1M0', ** SYSTEM DSN HIGH LEVEL QUALIFIER// DOMAIN=&SYSNAME.A, ** NETVIEW DOMAIN NAME// PROG=DUIFT000, ** PGMUSED TO START GMFHS HOST MAIN TASK// REG=32M, ** REGION SIZE IN K FOR MAIN TASK// AGGRST=N, ** RUN AGG CALCULATION ON STARTUP// RESWS=NO, ** RESOURCE STATUS WARM START// ARM=*NOARM, ** AUTOMATIC RESTART MANAGER// SUBSYM=*SUBSYM ** SYMBOL SUBSTITUTION//*//STEP1 EXEC PGM=&PROG,REGION=&REG,TIME=1440,// PARM='&AGGRST,RESWS=&RESWS,DOMAIN=&DOMAIN,ARM=&ARM,SUBSYM=&SUBSYM'//*********************************************************************//* INITIALIZATION PARAMETERS DATASET//*********************************************************************//CNMPARM DD DSN=&Q1..&DOMAIN..DSIPARM,DISP=SHR// DD DSN=&Q1..SYSTEM.DSIPARM,DISP=SHR// DD DSN=&SQ1..DSIPARM,DISP=SHR//*********************************************************************//* GMFHS MESSAGES DATASET//*********************************************************************//CNMMSG1 DD DSN=&SQ1..SDUIMSG1,DISP=SHR//CNMM DD SYSOUT=*//CNMD DD SYSOUT=*//CNMI DD SYSOUT=*//CNMO DD SYSOUT=*//CNMF DD SYSOUT=*//CNME DD SYSOUT=*//CNMV DD SYSOUT=*//CNMC DD SYSOUT=*


B.1.4 SA RODM data model load job

Figure 157. SA RODM data model load job used on System SC66

//INGELOAD JOB (999,AUS),'NVINSTALL',CLASS=A,MSGCLASS=X,// MSGLEVEL=(1,1),REGION=0M,TIME=1440,NOTIFY=&SYSUID//*******************************************************************///* STEP TO PROCESS CLASS STRUCTURE DEFINITIONS *///*******************************************************************///INGSTRLD EXEC PGM=EKGLOTLM,// PARM=('OPERATION=LOAD',// 'NAME=EKGA66',// 'LOAD=STRUCTURE',// 'SEVERITY=WARNING',// 'LISTLEVEL=ALLSYNTAX')//EKGLANG DD DSN=NETVIEW.V3R1M0.SEKGLANG,DISP=SHR//EKGLUTB DD DSN=NETVIEW.V3R1M0.SEKGLUTB,DISP=SHR//EKGPRINT DD SYSOUT=*//EKGIN1 DD DSN=NETVUSER.SYSTEM.LOADRODM(LOADSTR0),DISP=SHR//EKGIN2 DD DSN=NETVUSER.SYSTEM.LOADRODM,DISP=SHR//*EKGIN3 DD DUMMY//SYSPRINT DD SYSOUT=*//PLIDUMP DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//*******************************************************************///* STEP TO DELETE ALL GMFHS OBJECTS OF THE PREVIOUSLY LOADED *///* ENTERPRISE DATA MODEL *///*******************************************************************///CLEANUP EXEC PGM=AOFECLN,// PARM=('EKGA66,,')//*//STEPLIB DD DSN=ING.SINGIMOD,DISP=SHR//SYSPRINT DD SYSOUT=*//*******************************************************************///* STEP TO PROCESS INSTANCE DEFINITIONS *///*******************************************************************///INGINSLD EXEC PGM=IKJEFT01,DYNAMNBR=30,REGION=4096K//SYSEXEC DD DSN=ING.SINGIREX,DISP=SHR//SYSTSPRT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//EKGLANG DD DSN=NETVIEW.V3R1M0.SEKGLANG,DISP=SHR//EKGLUTB DD DSN=NETVIEW.V3R1M0.SEKGLUTB,DISP=SHR//EKGPRINT DD SYSOUT=*//EKGIN1 DD DUMMY//EKGIN2 DD DUMMY//AOFIN3 DD DSN=NETVUSER.SYSTEM.LOADRODM(LOADZ994),DISP=SHR//*EKGIN3 DD ALLOCATED AND FREED BY AOFRILOD//PLIDUMP DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSTSIN DD *%AOFRILOD OPERATION=LOAD,+

NAME=EKGA66,+LOAD=INSTANCE,+SEVERITY=WARNING,+LISTLEVEL=ALLSYNTAX



Appendix C. One RODM/GMFHS focal point configuration

The following section provides a check list of customization tasks that arenecessary to perform to have two NetViews on one logical partition (LPAR)connected to only one RODM/GMFHS application pair. This check list is toperform in addition to the regular tasks involved to customize the networkingand System Automation NetViews on the focal point system.

For further details refer to the following documentations:

• System Automation for OS/390 V1R3 Planning and Installation,GC28-1549

• Tivoli NetView for OS/390 V1R3 Installation and Administration Guide,SC31-8236

Table 28. Check list of tasks to enable one RODM/GMFHS configuration

Networking NetView System Automation NetView

RODM

Update EKGINMTB to include EKGSPPIBuild LOADER files

(See Appendix “Loading EKGSPPI intoRODM” in System Automation OS/390V1R3 Planning and Installation,GC28-1549)

Automation Table

Modify the member AOFMSGSY toenable the statement%INCLUDE AOFMSG03

Add the RODM and NetView domainname

No modifications specifically for graphics

NPDA

Prior to perform the check list tasks below, ensure to perform the SystemAutomation work steps to load the one (networking) RODM application withthe data model for all System Automation objects.

Note


Be sure filters are set to pass alerts(See Chapter “Customize NetView AlertInformation” in System AutomationOS/390 V1R3 Planning and Installation,GC28-1549)

NPDA is not required. However, it ispossible to include the same VSAM in theAutomation NetView procedure as it isdone in the Networking NetViewprocedure.(See Appendix “Running Two GraphicalNetView Releases on the Same System” inTivoli NetView OS/390 V1R3 Installationand Administration Guide, SC31-8236)especially:BNJMBDST -- BNJDSERV initializationmember:Change FUNCT=BOTH to FUNCT=VSAM

Tasks (DSIDMN)

Modify DSIPARM member DSIDMNB to:MOD=CNMCALRT,TSKID=AOFALRT,PRI=6,INIT=Y

Check member AOFDMN to ensure the initmember of task AOFRDST has notchanged from the default(MEM=AOFRINIT)

Modify the init member AOFRINIT to reflectthe same PPI receiver task as in DSIQTSKIDEFAOF PPIRCVR=AOFQTSK

Modify the init member DSIQTSKI of taskDSIQTSK to reflect a different PPIreceiver task (for example):CMDRCVR ID=AONQTSK

Modify the init member DSIQTSKI of taskDSIQTSK to reflect the same PPI receivertask as in AOFRINIT:CMDRCVR ID=AOFQTSK

Include a statement for the focal pointRODM:REP RODM=<RODM name of networkingfocal point system, e.g. EKGN66>,CONN=Y,AO=Y,ID=<Name of CMDRCVRID task, e.g. AOFQTSK>

Modify the init member DSI6INIT of taskDSI6DST to reflect the correct networkingfocal point NetView:DEFFOCPT TYPE=ALERT,PRIMARY=<NetId>.<Networking NetViewDomain-Name, e.g. USIBMSC.SC66N>



Commands (DSICMD)

Modify the member DSICMD to enablethe statement%INCLUDE AOFCMDST

Additional members to check

Ensure the clist AOFRODIN and the initmember AOFRODM reflect the correctRODM userid and networking focal pointRODM name(Don’t forget security !)

Modify the member AOFSFMAP to reflect acorrect autotask name (e.g. AUTO1) andthe networking focal point RODM name(e.g. EKGN66)

RODM name of focal point system RODM name of focal point system

Must be specified in member:AOFMSGSY

Must be specified in member:AOFRODMAOFSFMAPDSIQTSKI (REP statement)


Appendix C. One RODM/GMFHS focal point configuration 243


Appendix D. Special notices

This publication is intended to help OS/390 customers, business partners andspecialists to setup and customize Tivoli NetView for OS/390 and SystemAutomation for OS/390 in their enterprise environment. The information in thispublication is not intended as the specification of any programming interfacesthat are provided by Tivoli NetView for OS/390 and System Automation forOS/390. See the PUBLICATIONS section of the IBM ProgrammingAnnouncement for Tivoli NetView for OS/390 and System Automation forOS/390 for more information about what publications are considered to beproduct documentation.

References in this publication to IBM products, programs or services do notimply that IBM intends to make these available in all countries in which IBMoperates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM's product, program, or service may beused. Any functionally equivalent program that does not infringe any of IBM'sintellectual property rights may be used instead of the IBM product, programor service.

Information in this book was developed in conjunction with use of theequipment specified, and is limited in application to those specific hardwareand software products and levels.

IBM may have patents or pending patent applications covering subject matterin this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to the IBMDirector of Licensing, IBM Corporation, North Castle Drive, Armonk, NY10504-1785.

Licensees of this program who wish to have information about it for thepurpose of enabling: (i) the exchange of information between independentlycreated programs and other programs (including this one) and (ii) the mutualuse of the information which has been exchanged, should contact IBMCorporation, Dept. 600A, Mail Drop 1329, Somers, NY 10589 USA.

Such information may be available, subject to appropriate terms andconditions, including in some cases, payment of a fee.

The information contained in this document has not been submitted to anyformal IBM test and is distributed AS IS. The use of this information or theimplementation of any of these techniques is a customer responsibility anddepends on the customer's ability to evaluate and integrate them into thecustomer's operational environment. While each item may have been


reviewed by IBM for accuracy in a specific situation, there is no guaranteethat the same or similar results will be obtained elsewhere. Customersattempting to adapt these techniques to their own environments do so at theirown risk.

Any pointers in this publication to external Web sites are provided forconvenience only and do not in any manner serve as an endorsement ofthese Web sites.

This document contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examplescontain the names of individuals, companies, brands, and products. All ofthese names are fictitious and any similarity to the names and addressesused by an actual business enterprise is entirely coincidental.

The following terms are trademarks of the International Business MachinesCorporation in the United States and/or other countries:

The following terms are trademarks of other companies:

Tivoli, Manage. Anything. Anywhere.,The Power To Manage., Anything.Anywhere.,TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, PlanetTivoli, and Tivoli Enterprise are trademarks or registered trademarks of TivoliSystems Inc., an IBM company, in the United States, other countries, or both.In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - TivoliA/S.

C-bus is a trademark of Corollary, Inc. in the United States and/or othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States and/or othercountries.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of

AIX CICSDB2 DFSMSIBM IMSMVS NetViewNWAYS OpenEditionOS/2 OS/390RACF REXXS/390 System/370System/390 System AutomationTivoli TSO


Microsoft Corporation in the United States and/or other countries.

PC Direct is a trademark of Ziff Communications Company in the UnitedStates and/or other countries and is used by IBM Corporation under license.

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of IntelCorporation in the United States and/or other countries.

UNIX is a registered trademark in the United States and other countrieslicensed exclusively through The Open Group.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarksowned by SET Secure Electronic Transaction LLC.

Other company, product, and service names may be trademarks or servicemarks of others.

Appendix D. Special notices 247


Appendix E. Related publications

The publications listed in this section are considered particularly suitable for amore detailed discussion of the topics covered in this redbook.

E.1 IBM Redbooks

For information on ordering these publications see “How to get ITSOredbooks” on page 251.

• Integrated Centralized Automated/Advanced Operation, SG24-2599(Available online)

• An Introduction to TME 10 NetView for OS/390, SG24-4922 (Availableonline)

• An Introduction to Tivoli NetView for OS/390 V1R2, SG24-5224

• Parallel Sysplex Automation: Using System Automation for OS/390,SG24-5442

E.2 IBM Redbooks collections

Redbooks are also available on the following CD-ROMs. Click the CD-ROMsbutton at http://www.redbooks.ibm.com/ for information about all the CD-ROMsoffered, updates and formats.

E.3 Other resources

These publications are also relevant as further information sources:

CD-ROM Title Collection KitNumber

System/390 Redbooks Collection SK2T-2177

Networking and Systems Management Redbooks Collection SK2T-6022

Transaction Processing and Data Management Redbooks Collection SK2T-8038

Lotus Redbooks Collection SK2T-8039

Tivoli Redbooks Collection SK2T-8044

AS/400 Redbooks Collection SK2T-2849

Netfinity Hardware and Software Redbooks Collection SK2T-8046

RS/6000 Redbooks Collection (BkMgr) SK2T-8040

RS/6000 Redbooks Collection (PDF Format) SK2T-8043

Application Development Redbooks Collection SK2T-8037

IBM Enterprise Storage and Systems Management Solutions SK3T-3694




• Tivoli NetView for OS/390 AON Customization Guide, SC31-8662

• Tivoli NetView for OS/390 Automated Operations Network Users Guide,GC31-8661

• Tivoli NetView for OS/390 Automation Guide, SC31-8225

• Tivoli NetView for OS/390 Customization Guide, SC31-8228

• Tivoli NetView for OS/390 Messages and Codes, SC31-8237

• Tivoli NetView for OS/390 Installation and Administration Guide,SC31-8236

• Tivoli NetView for OS/390 Administration Reference, SC31-8222

• Tivoli NetView for OS/390 NetView Management Console User’s Guide,GC31-8665

• Tivoli NetView for OS/390 V1R3 Planning Guide, GC31-8226

• Tivoli Netview for OS/390 Tuning Guide, SC31-8240

• System Automation for OS/390 V1R3 Planning and Installation,GC28-1549

• System Automation for OS/390 V1R3 Customization, GC28-1566

• System Automation for OS/390 V1R3 Operations, GC28-1550

• System Automation for OS/390 V1R3 Messages and Codes, GC28-1569

• System Automation for OS/390 V1R3 Technical Reference, GC28-1593

• SNA Management Services Reference, SC30-3346

• OS/390 TCP/IP OpenEdition User’s Guide, GC31-8305

E.4 Referenced Web sites

These Web sites are also relevant as further information sources:

• http://www.s390.ibm.com/sa

• http://www.tivoli.com/nv390


How to get ITSO redbooks

This section explains how both customers and IBM employees can find out about ITSO redbooks,redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.

• Redbooks Web Site http://www.redbooks.ibm.com/

Search for, view, download, or order hardcopy/CD-ROM redbooks from the redbooks Web site. Alsoread redpieces and download additional materials (code samples or diskette/CD-ROM images) fromthis redbooks site.

Redpieces are redbooks in progress; not all redbooks become redpieces and sometimes just a fewchapters will be published this way. The intent is to get the information out much quicker than theformal publishing process allows.

• E-mail Orders

Send orders by e-mail including information from the redbooks fax order form to:

• Telephone Orders

• Fax Orders

This information was current at the time of publication, but is continually subject to change. The latestinformation may be found at the redbooks Web site.

In United StatesOutside North America

e-mail [email protected] information is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)Canada (toll free)Outside North America

1-800-879-27551-800-IBM-4YOUCountry coordinator phone number is in the “How to Order”section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)CanadaOutside North America

1-800-445-92691-403-267-4455Fax phone number is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

IBM employees may register for information on workshops, residencies, and redbooks by accessingthe IBM Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button.Look in the Materials repository for workshops, presentations, papers, and Web pages developedand written by the ITSO technical professionals; click the Additional Materials button. Employees mayaccess MyNews at http://w3.ibm.com/ for redbook, residency, and workshop announcements.

IBM Intranet for Employees


http://www.elink.ibmlink.ibm.com/pbl/pbl



http://w3.itso.ibm.com/

http://w3.ibm.com/

http://www.redbooks.ibm.com




mailto:[email protected]




IBM Redbook fax order form

Please send me the following:

We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card notavailable in all countries. Signature mandatory for credit card payment.

Title Order Number Quantity

First name Last name

Company

Address

City Postal code

Telephone number Telefax number VAT number

Invoice to customer number

Country

Credit card number

Credit card expiration date SignatureCard issued to


Glossary

AIX operating system. IBM implementation ofthe UNIX operating system. The RS/6000system, among others, runs the AIX operatingsystem.

Browse.(1) To look at records in a file.(2) In the NetView Graphic Monitor Facility, toopen a view that cannot receive status changesfrom Tivoli NetView for OS/390. This contrastswith monitor.

Central Processing Unit (CPU). The part of acomputer that includes the circuits that controlthe interpretation and execution of instructions.A CPU is the circuitry and storage that executesinstructions. Traditionally, the completeprocessing unit was often regarded as the CPU;whereas, today the CPU is often a microchip. Ineither case, the centrality of a processor orprocessing unit depends on the configuration ofthe system or network in which it is used.

Command Line Interface (CLI). A type ofcomputer interface in which the input commandis a string of text characters. Contrast withgraphical user interface.

DB2. An IBM relational database managementsystem that is available as a licensed programon several operating systems. Programmersand users of DB2 can create, access, modify,and delete data in relational tables using avariety of interfaces.

Direct Access Storage Device (DASD). Amass storage medium on which a computerstores data. Contrast with random accessmemory.

Distributed Monitoring. See Tivoli DistributedMonitor.

Distributed Monitoring Engine. In a Tivolienvironment, the client software that is installedon each managed node, gateway, and endpointthat is being monitored by Tivoli DistributedMonitoring. The Distributed Monitoring enginemonitors resources, compares data from

© Copyright IBM Corp. 2000

monitored resources against configuredthresholds, and runs automated responses.

Extended Architecture (XA). An extension toSystem/370 architecture that takes advantageof continuing high performance enhancementsto computer system hardware.

Graphical User Interface (GUI). A type ofcomputer interface consisting of a visualmetaphor of a real-world scene, often of adesktop. Within that scene are icons,representing actual objects, that the user canaccess and manipulate with a pointing device.Contrast with command line interface.

Hypertext Markup Language (HTML). Amarkup language that is specified by an SGMLdocument type definition (DTD) and isunderstood by all Web servers.

Hypertext Transfer Protocol (HTTP). In theInternet suite of protocols, the protocol that isused to transfer and display hypertextdocuments.

Internet Protocol (IP). In the Internet suite ofprotocols, a connectionless protocol that routesdata through a network or interconnectednetworks and acts as an intermediary betweenthe higher protocol layers and the physicalnetwork.

Java. An object-oriented programminglanguage for portable interpretive code thatsupports interaction among remote objects.Java was developed and specified by SunMicrosystems, Incorporated.

Monitor.(1) A device that observes and records selectedactivities within a data processing system foranalysis. Possible uses are to indicatesignificant departure from the norm or todetermine levels of utilization of particularfunctional units.(2) Software or hardware that observes,supervises, controls, or verifies operations of asystem.(3) The function required to initiate the

253

transmission of a token on the ring and to providesoft-error recovery in case of lost tokens,circulating frames, or other difficulties. Thecapability is present in all ring stations.(4) Software that monitors specific applications orthe systems on which the applications rely.Monitors typically monitor information, such asavailable disk space or application errors, andcompares the information to defined thresholds.When thresholds are exceeded, either system ornetwork administrators can be notified or anautomated response can be performed.(5) In the NetView Graphic Monitor Facility, toopen a view that can receive status changes fromTivoli NetView for OS/390. Problemdetermination and correction can be performeddirectly from the view. Contrast with browse.

MVS. Multiple Virtual Storage. Implies MVS/390,MVS/XA, MVS/ESA, and the MVS element of theOS/390 operating system.

NetView. See Tivoli NetView and Tivoli NetViewfor OS/390.

Open Database Connectivity (ODBC). Astandard application programming interface (API)for accessing data in both relational andnon-relational database management systems.Using this API, database applications canaccess data stored in database managementsystems on a variety of computers even if eachdatabase management system uses a differentdata storage format and programming interface.ODBC is based on the call level interface (CLI)specification of the X/Open SQL Access Groupand was developed by Digital EquipmentCorporation (DEC), Lotus, Microsoft, andSybase. Contrast with Java DatabaseConnectivity.

Policy. In a Tivoli environment, a set of rules thatare applied to managed resources. A specific rulein a policy is referred to as a policy method.

Policy Region. In a Tivoli environment, a groupof managed resources that share one or morecommon policies. Tivoli administrators use policyregions to model the management andorganizational structure of a network computingenvironment. The administrators can groupsimilar resources, define access to and control

the resources, and associate rules for governingthe resources. The policy region containsresource types and the list of resources to bemanaged. A policy region is represented on theTivoli desktop by an icon that resembles a capitolbuilding (dome icon). When a Tivoli ManagementRegion (TMR) is created, a policy region with thesame name is also created. In this case, the TMRhas only one policy region. However, in mostcases, a Tivoli administrator creates other policyregions and subregions to represent theorganization of the TMR. A TMR addresses thephysical connectivity of resources, whereas, apolicy region addresses the logical organizationof resources.

Policy Subregion. In a Tivoli environment, apolicy region created or residing in another policyregion. When a policy subregion is created, itinitially uses the resource and policy properties ofthe parent policy region. The Tivoli administratorcan later change or customize these properties toreflect the specific needs and differences of thesubregion.

Profile.(1) Data that describes the significantcharacteristics of a user, a group of users, or oneor more computer resources.(2) In a Tivoli environment, a container forapplication-specific information about a particulartype of resource. A Tivoli application specifies thetemplate for its profiles; the template includesinformation about the resources that can bemanaged by that Tivoli application.

A profile is created in the context of a profilemanager; the profile manager links a profile tothe Tivoli resource (for example, a managednode) that uses the information contained in theprofile. A profile does not have any directsubscribers.

Random Access Memory (RAM). A temporarystorage location in which the central processingunit (CPU) stores and executes its processes.Contrast with direct access storage device.

Scripting Language. The programminglanguage in which a script is written.


Script Stub. A place holder for a particular shellscript. For example, the Tivoli Module Buildergenerates a script stub (using a skeleton file) if adeveloper does not provide the script forimplementing a particular task or monitor whendefining the task or monitor. The script stub thendisplays a message that the script executedsuccessfully and displays any variables that werepassed to the script.

SMS. See Storage Management Subsystem.

Software Distribution. See Tivoli SoftwareDistribution.

SQL. A programming language that is used todefine and manipulate data in a relationaldatabase.

Structured Programming Facility (SPF). AnIBM product that is a full-screen editor.

Structured Query Language. See SQL.

System Management Facility (SMF). Astandard feature of OS/390 that collects andrecords a variety of system and job-relatedinformation.

Storage Management Subsystem (SMS). ADFSMS/MVS facility that is used to automate andcentralize the management of storage. UsingSMS, a storage administrator describes dataallocation characteristics, performance andavailability goals, backup and retentionrequirements, and storage requirements to thesystem.

TCP. See Transmission Control Protocol.

TCP/IP. See Transmission ControlProtocol/Internet Protocol.

Time Sharing Option (TSO). An option of theMVS operating system that provides interactivetime sharing from remote terminals.

Tivoli Client. A client of a Tivoli server. See TMRclient and TMR server.

Tivoli Desktop. In a Tivoli environment, thedesktop that system administrators use tomanage their network computing environment.

Tivoli Distributed Monitoring. A Tivoli productthat monitors system resources, initiates any

necessary corrective actions, and informs systemadministrators of potential problems. TivoliDistributed Monitoring consists of a group ofmonitors that are installed on each managednode that is to be monitored. It resolves someevents on its own and may send others to theTivoli Enterprise Console.

Tivoli Developer’s Toolkit. A Tivoli tool thatenables developers to describe the managementcharacteristics of an application or businesssystem and that generates the applicationdescription files and application managementpackages that the Tivoli management softwareuses to manage applications and businesssystems.

Tivoli Enterprise Console (TEC). A Tivoliproduct that collects, processes, andautomatically initiates corrective actions forsystem, application, network, and databaseevents. It is the central control point for eventsfrom all sources. The Tivoli Enterprise Consoleprovides a centralized, global view of the networkcomputing environment. It uses distributed eventmonitors to collect information, a central eventserver to process information, and distributedevent consoles to present information to systemadministrators.

Tivoli Environment. The Tivoli applications,based upon the Tivoli Management Framework,that are installed at a specific customer locationand that address network computingmanagement issues across many platforms. In aTivoli environment, a system administrator candistribute software, manage user configurations,change access privileges, automate operations,monitor resources, and schedule jobs.

Tivoli Management Framework. The basesoftware that is required to run the applications inthe Tivoli product suite. This softwareinfrastructure enables the integration of systemsmanagement applications from Tivoli SystemsInc. and the Tivoli Partners. The TivoliManagement Framework includes the following:

-Object request broker (oserv)-Distributed object database-Basic administration functions-Basic application services

255

-Basic desktop services, such as the graphicaluser interface

In a Tivoli environment, the Tivoli ManagementFramework is installed on every client and server;however, the TMR server is the only server thatholds the full object database.

Tivoli Management Region (TMR). In a Tivolienvironment, a Tivoli server and the set of clientsthat it serves. An organization can have morethan one TMR. A TMR addresses the physicalconnectivity of resources; whereas, a policyregion addresses the logical organization ofresources.

Tivoli Service Desk. A Tivoli product that is anintegrated set of tools including Tivoli AssetsManagement, Tivoli Change Management andTivoli Problem Management. The informationabout the enterprise IT services and support ismaintained in a relational data base that can beaccessed via users in a 3-tier environment. Itprovides a structure that supports the gathering,organizing, locating, and reporting of informationrelated to problem, change, and assetmanagement.

Tivoli Service Desk for OS/390. A Tivoli productthat is an integrated set of tools, services, andinterfaces for automating and customizing aorganization's IT service and support operation inan OS/390 environment. It provides a structurethat supports the gathering, organizing, locating,and reporting of information related to problem,change, and asset management.

Tivoli Software Distribution. A Tivoli productthat automates software distribution to clients andservers in a network computing environment. Anorganization can use this product to install andupdate applications and software in acoordinated, consistent manner across anetwork. Tivoli Software Distribution creates filepackages and distributes them to predefinedsubscribers.

TMR. See Tivoli Management Region.

TMR Client. In a Tivoli environment, anycomputer, except the TMR server, on which theTivoli Management Framework is installed. Theoserv daemon runs on the TMR client, and the

TMR client maintains a local object database.See Tivoli client and Tivoli server.

TMR Server. A Tivoli server for a specific TivoliManagement Region (TMR). See Tivoli client andTMR client.

TSD. See Tivoli Service Desk.

Transmission Control Protocol (TCP). Acommunications protocol used in the Internet andin any network that follows the InternetEngineering Task Force (IETF) standards forinternetwork protocol. TCP provides a reliablehost-to-host protocol between hosts inpacket-switched communications networks and ininterconnected systems of such networks. It usesthe Internet Protocol (IP) as the underlyingprotocol.

Transmission Control Protocol/InternetProtocol (TCP/IP). A set of communicationsprotocols that support peer-to-peer connectivityfunctions for both local and wide area networks.

UNIX. An operating system developed by BellLaboratories that features multi-programming in amulti-user environment. The UNIX operatingsystem was originally developed for use onminicomputers but has been adapted formainframes and microcomputers. The AIXoperating system is IBM implementation of theUNIX operating system.


Abbreviations and acronyms

ACF Automation Control File

AIX AIX Operating System

AOC Automated OperationControl

AON Automated OperationNetwork

API Application ProgramInterface

APPC Application Peer-to-PerCommunication

CLI Command LineInterface

CLIST Command List

CPE Command ProfileEditor

CPU Central Processing Unit

DASD Direct Access StorageDevice

DNS Domain Name Services

E/AS Event/AutomationServer

FTP File Transfer Protocol

GMFHS Graphic Monitor FacilityHost Subsystem

GUI Graphical UserInterface

HCD Host ConfigurationDefinition

HLL/API High Level LanguageApplication ProgramInterface

HPFS High Performance FileSystem

HTML Hypertext MarkupLanguage

HTTP Hypertext TransferProtocol


IBM International BusinessMachines

IP Internet Protocol

IPC Inter-ProcessCommunication

IPL Initial Program Load

ITSO International TechnicalSupport Organization

JDK Java Development Kit

JES Job Entry System

JFF Just for Fun

JRE Java RuntimeEnvironment

MIB ManagementInformation Block

MIF ManagementInformation Format

MPF Message ProcessingFacility

MVS/ESA Multiple VirtualStorage/ExtendedStorage Architecture

MVS/XA Multiple VirtualStorage/ExtendedArchitecture

NGMF NetView GraphicMonitor Facility

NMC NetView ManagementConsole

NLS National LanguageSupport

NNT NetView-NetView Task

NTFS NT File System

OS/390 Operation System/390

OST Operator Station Task

PPI Program-ProgramInterface

257

RACF Resource AccessControl Facility

RDBMS Relational Data BaseManagement Systems

REXX Name of an InterpretedCommand ListLanguage

RFA Request forAnnouncement

RODM Resource Object DataManager

SA System Automation

SAF Security AuthorizationFacility

SDF System Display Facility

SMS Storage ManagementSubsystem.

SMTP Simple Mail TransportProtocol

SNA System NetworkArchitecture

SNMP Simple NetworkManagement Protocol

SYSLOG System Log

TCP/IP Transmission ControlProtocol/InternetProtocol

T/EC Tivoli/EnterpriseConsole

TMA Tivoli ManagementAgent

TME Tivoli ManagementEnvironment

TMR Tivoli ManagementRegion

TN3270 Telnet 3270

TSO Time Sharing Option

VTAM Virtual TransactionAccess Method

WLM Workload Manager

WTOR Write To Operator


Index

AA01APPLS 47ACF 60, 98, 104, 172, 184, 213ACFPLOAD 14, 170, 173ACQUIRE 175ADDSD 171aggregate objects 138AIFR 175AIX 253Alert Forwarding 19ALWAYS 168AOC/MVS 172AOCCLONE 74AOCCLONE1 110AOCQRES 14AOFACFMP 173AOFINIT 108AOFMSG00 41, 42, 104AOFMSG01 41, 43, 44, 104, 158, 164AOFMSGSY 41, 42, 60AOFPNLS 50, 108AOFPSYST 109AOFRINIT 41AOFRODM 48, 50AOFSFMAP 48AOFSMAP 50AOFTDDF 108, 111AOFTREE 50, 108AOFTSC42 110AOFTSC66 110AOFTSC69 110AOFTST02 162AON 37, 66AON Inform policy 199, 202, 214, 217, 218APL 65APPC 79Application 64ApplicationGroup 64APPN 8ASCH 79ASSIGN 92ATF DSICGLOB 177Auto Operators 92AUTOCNT 157, 162AUTOMAN 6, 156, 157, 159, 161, 215AUTOMATED function 175, 180


Automated Operation Network 37Automation Console 88Automation Control File 104Automation control file 60Automation Flags 72Automation policy database 60Automation table 155Automation Table Management tool 157Automation Timer 90AUTOTBL 157, 166Available Documentation and Technical Information144

BBASE_AUTOOPS 93Batch or shell files 151BEGIN/END 157, 166BINDIR 120, 121, 129, 130BNH370I 179BNJMBDST 41, 43

CCannot start the NT services 130child 103CHRON 2, 6CLASS 66CLPA 56CNME1015 45, 46CNME1034 36, 45, 46Command line interface 253Command Profile Editor 124, 126Common automation CLIST library 45Common automation CLIST library (Enterprise fea-ture) 46Common automation DSIPARM library 40Common automation DSIPARM library (Enterprisefeature) 44common automation NetView libraries 40Common automation VTAMLST library 47common networking NetView libraries 34CPE online utility 127CPEBATCH 126, 127CURRDATE 177current date 175, 177current time 175, 177CURRTIME 177

259

CUSTOMER 107customization 53Customizing RODM load jobs 49

DDALLAS_MVS 95DB2 8, 253DDF 38default directory 119default encryption key 145default por 141Define a NetView operator ID 145depedency relationship 105dependencies 103dependency 104DIAGNOSE 145dialog 53Disable 157, 164disabling 164Display 157DISPTREE 105Distributred Monitoring 253domain specific 37, 50DSI6DST task 19DSICGLOB 177DSICMD 41, 43, 44DSICNM 41, 43DSICRTR task 20DSICRTTD 41, 43, 44, 45DSIDMN 41, 43, 44DSIDMNB 35, 36, 42, 43, 44, 45, 141DSIDMNK 35, 42, 43, 144DSIDMNK Sample member 146DSILIST 157, 159DSIOPF 42, 44DSIOPFU 42DSIPARM 37, 108DSIPARM and DSIPRF members 144DSIPARM members 141DSIQTSKI 48, 50DSITBL01 35, 104DSITCPCF 144DSITCPIP 146DSITCPRF 144DSIVPARM 35DSIWBMEM 141DUIFPMEM 35, 37, 49DUIGINIT 35, 49

duinmccw.exe 131, 132duinmcsw.exe 118, 119

EEDIT 178EDIT action 175, 178egvread1.me 115egvread2.me 115EGVREAD5.ME 118, 132, 143, 147Enable 157, 164Enable/Disable 164Enabling TCP/IP for NetView 141encryption is not used 145encryption key 145enhancement 126Environment setup 121, 122, 123Environment space errors 153Events 13events 181EXECIO 8EZLCFG01 35, 37, 38EZLTREE 37, 38

FFLB4WIN.EXE 147flb4win.exe 144, 147FLBDPD.HTM 144FLBHLP.HTM 144flbinst.bat 148, 150flbread1.me 115FLBSYSD 35FLBSYSDA 35Focal Point 37focal point system 105FOCAL_NETWORK 92FOCAL_OPERS 93FORCE 69FTP 4

GGAT&AOCCLONE2 111Gateway 91, 112gateway 22Gateway Sessions 209GATOPER 208GMFHS 21, 37Graphical user interface 253


Greater-than 175greater-than 177Group 64

HHDRMTYPE 8Heartbeat 86Heartbeat Interval 86Hints and Tips for the Tivoli NMC Topology Console135Hints and Tips for the Tivoli NMC Topology Server117, 129host TCP/IP 146How to Issue SA OS/390 Commands Using the Net-View Management Console 125HTTP 253

Iibmflb folder 151IDLEOFF 8, 169IEASYMxx 33IF-THEN 168IF-THEN condition item 175, 176ihsmessage.log 128, 129, 130IMMED 69inbound and outbound encryption keys 149ING.SINGPWS1(INGNMCTZ)

125ING.SINGPWS1(INGNMCZP)

125ING_NMCCHLP_HELPFILES 124ING_NMCS_CMD.RSP 124ING_NMCS_DDF 124INGDLG 62INGELOAD 55INGNMCTZ 125INGNMCZP 125INIT 69Insert 157Installing NetView 3270 Console on Windows 95,98, and NT 146Installing NMC for SA OS/390 124Installing NMC Topology Server 117Installing the NMC Topology Console for WindowsNT 131INTERP 121, 129ints and Tips for the Tivoli NMC Topology Console131

IP 253IP Management 3IPL 107IPSTAT 4ISQ_NMCCCHLP_HELPFILES 124ISQ_NMCS_CMD.RSP 124ISQ_NMCS_DDF 124Issuing SA OS/390 commands 135

JJAVA 253Java Development Kit 143Java interface 115Java set up 135JDK 143JES2 65, 112, 113JES3 65

Kkeyword "ANY_OTHER" 146

Lless-than 175, 177Link to Instances 73LLA 79local (domain specific) NetView libraries 37, 50Local install process for the networking NetView do-mains 38LPAR 37LU 6.2 session 19LUC session 19

MMainframe Component 142MCSFLAGS 89MEMSTORE 8, 169Message 194Message Class 94MIB 2, 4MIGRATE 172Missing Heartbeat Delay 86MLWTO 6MPF table 196multi system focal point 204multi-line messages 175MVS Component 90MVS_COMPONENT 91

261

MVSSTART 107

NNETCONV 5NETLOG 8NETSTAT 4NETVAPPL 47NETVIEW 76NetView 3270 Management Console 115, 142,143NetView Management Console 115NetView ROLL command 152NetView Sign On panel 136NETVIEW_CLASS 66, 76NETVSA42 74NETVSA66 74NETVSA69 74network node 8NEW 66NMC 1, 2, 4, 5, 6, 7, 9, 20, 33, 37, 39, 115, 224,225NMC communications server 122NMC server 115, 122NMC Topology Console setup program 133NMC Topology Server 118NMC topology server starts, but then closes 130NMC-Log 140nmcpdf.zip 115NNT 91Norm 69Notify 94Notify Operators 93nstalling the Tivoli NMC Topology Console 131NT service 122, 123NTW 91, 94, 96numeric 177Numeric comparison 177numeric comparison 177Numeric comparisons 175

Ooper1.bat 150operator ID 145OperatorView 136OST-NNT session 19Out of memory errors 153OUTMODE 14

PPARENT 107parent 103partial download of NMC from the server 135performance 166PERMIT 172PING 4PIPE EDIT 6policy database 53policyDB 170PORT 144problem with the TCP/IP definitions 141Procedural 38Processor operations 80processor operations 139processor operations start command 138ProcessorOperation Operator 125ProcOps 83PTF UW90546 124

RREADME 124READSEC 8real objects 139refresh the screen 152relationship 105Reload 157Replicating the NetView 3270 Console Across Mul-tiple Machines 151REPORT 173Report 173Required Host Environment 146response files 125RMTCMD 7RODM 20, 172RODMNAME 55RRD 213Running the duinmcsw.exe 119

SSA OS/390 172SA_OS390 78SAF 213SAMPLE_SYSTEM_01 81SAOS390_NETVIEW 73SC42 112SC42_Generic 78SC66 81, 112


SC66_Generic 78SC69 112SC69_Generic 78SCHEDULED_AUTOMATION 90, 91Screen corruption 153SDF 13, 22, 108, 109, 204, 224, 225SDFPANEL 108Selecting the correct files 143Server intallation on system running Tivoli Frame-work 129ServerPac 57service 122, 123Service periods 13Service Point Command Line 5Session Management 4session management 4Setting up DSITCPCF 144Setting up DSITCPRF 145Setting up NMC Topology Server 117Setting up the base NetView for OS/390 47Setting up the Graphic Monitor Facility Host Sub-system 49Setting up the Host (Mainframe) Environment 144Setting up the NetView 3270 Management Console142Setting up the NMC client workstation 131Setting up the Resource Object Data Manager 47Setting up the Web interface to Tivoli NetViewOS/390 140setup 53setup_env file is found, but the bindir is not set 130SETUP_ENV.CMD 120, 121setup_env.cmd 120, 129setup_env.cmd is not found 129SEZLPNLU 38SHUTSYS 14slow response time 152SMF 8SMTP 4, 6, 156, 199, 202, 214, 215SMTP email 199, 200, 201, 202SNMP 1, 2, 3, 4, 5SOCKET 7socket 2, 4SOCKETS 145Software Distribution 255Software installation 118, 120Software requirements 142SQL 255start the NetView 3270 Management Console from

an MS-DOS prompt150

start the NetView Management Console 136Starting the NMC Console 131Starting the NMC Console using a TCP/IP connec-tion 133Starting the Tivoli NMC Topology Server 117, 127Startup 155Status Display Facilit 108Status Display Facility 108step 33, 39step 1 33, 39step 2 33, 39step 3 34step 4 34step 5 37, 50SubGroup 64, 94, 96SUBMIT 8SUBSJOB 71switching screens 152Synonym 59SYSCLONE 32SYSLOG 12SYSNAME 32sysplex 59System 64system and user defined symbolic 27, 32System Automation 66SYSTEM INFO 84, 87, 90, 91, 92, 93system operations 139system operations commands 139system requirements 142System use 86SystemAutomation Operator 125SystemOperation Operator 125

TTAF 91TARGET_NETWORK 92TCP 256TCP/IP 256TCPANAME 144TCPIP 79, 105TEC 255telnet 4Terminal Access Facility 91TIMEOUT 145TIMER 6

263

Timer 90Tivoli Developer’s Toolkit 255Tivoli Enterprise Console 255Tivoli Framework 120Tivoli Service Desk 256Tivoli Service Desk for OS/390 256Tivoli Software Distribution 256TME 10 NetView for OS/390 Management Console137TMR 90, 91, 94, 96TN3270 2, 4TopologyServer version 1.3.0 117TRACE action 175, 179TRACERTE 4TRANSIENT 68traps 3Triggers 13triggers 181TSO 79, 105

UUninstalling the NetView 3270 Console on Windows95, 98, and NT 150Uninstalling the Tivoli NMC Topology Console 131,134Uninstalling the Tivoli NMC Topology Server 117,128UNIX 256Unload 157user rights 121UW90546 124

VVALUE() function 175, 177Values of variables 175Variable value function 177VLF 79VSAMPOOL 169VTAM 79, 105

WWeb 115WINDIR 120Windows NT service 117Workstation Component 143WRITESEC 8WTOR 66



IBM Redbooks review

Your feedback is valued by the Redbook authors. In particular we are interested in situations where aRedbook "made the difference" in a task or problem you encountered. Using one of the followingmethods, please review the Redbook, addressing value, subject matter, structure, depth andquality as appropriate.

• Use the online Contact us review redbook form found at http://www.redbooks.ibm.com/• Fax this form to: USA International Access Code + 1 914 432 8264• Send your comments in an Internet note to [email protected]

Document NumberRedbook Title

SG24-5515-00Automation Using Tivoli NetView OS/390 V1R3 and SystemAutomation OS/390 V1R3

Review

What other subjects would youlike to see IBM Redbooksaddress?

Please rate your overallsatisfaction:

O Very Good O Good O Average O Poor

Please identify yourself asbelonging to one of thefollowing groups:

O Customer O Business Partner O Solution DeveloperO IBM, Lotus or Tivoli EmployeeO None of the above

Your email address:The data you provide here maybe used to provide you withinformation from IBM or ourbusiness partners about ourproducts, services or activities.

O Please do not use the information collected here for futuremarketing or promotional contacts or other communications beyondthe scope of this transaction.

Questions about IBM’s privacypolicy?

The following link explains how we protect your personal information.http://www.ibm.com/privacy/yourprivacy/




http://www.ibm.com/privacy/yourprivacy/

Printed in the U.S.A.

SG24-5515-00

Autom

ationU

sing

TivoliN

etView

OS/390

V1R

3an

dSystem

Autom

ationO

S/390

V1R

3S

G24-5515-00

®