an introduction to tivoli netview for os-390 v1r2 sg245224

7/31/2019 An Introduction to Tivoli NetView for OS-390 V1R2 Sg245224

1/405

An Introduction to Tivoli NetViewfor OS/390 V1R2

Arne Olsson, Brett Petersen, Budi Darmawan, Francois Lepage

International Technical Support Organization

SG24-5224-00

http://www.redbooks.ibm.com


2/405


3/405

International Technical Support Organization SG24-5224-00

An Introduction to Tivoli NetViewfor OS/390 V1R2

September 1998


4/405

Copyright International Business Machines Corporation 1998. All r ights reservedNote to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions

set forth in GSA ADP Schedule Contract with IBM Corp.

First Edition (September 1998)

This edition applies to Tivoli NetView for OS/390 V1R2.

Comments may be addressed to:IBM Corporation, International Technical Support OrganizationDept. HZ8 Building 678P.O. Box 12195Research Triangle Park, NC 27709-2195

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

Before using this information and the product it supports, be sure to read the general information in Appendix D,Special Notices on page 37 1.

Take Note!


5/405

Copyright IBM Corp. 1998 iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Introduction to TME 10 NetView V1R 2 . . . . . . . . . . . . . . . . . . . . .11.1 Summary of TME 10 NetView for OS/390 V1R2 Functions . . . . . . . . . . . . .11.2 ITSO Residency Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41.3 Dependencies for Various TME 10 NetView for OS/390 V1R2 Functions . .5

Part 1. NetView Automation Enhancement s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Chapter 2. Automation Table Enhancement s . . . . . . . . . . . . . . . . . . . . . . . .92.1 New AUTOTEST Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2.1.1 AUTOTEST Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.1.2 Logical Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.1.3 AUTOTEST Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

2.2 New AUTOTBL Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162.2.1 Principles of Multiple Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162.2.2 AUTOTBL Syntax Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172.2.3 AUTOTBL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Chapter 3. Automation Notification Enhancemen ts . . . . . . . . . . . . . . . . . .233.1 Concept of Automation Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233.2 Implementing Automation Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

3.2.1 Configuration Files Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243.2.2 Notification Policy Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263.2.3 Information Policy Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

3.3 Commands in Automation Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . .293.3.1 EZLEASLN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

3.3.2 INFORM Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333.3.3 INFORMTB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343.3.4 ILOG Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

3.4 RODM Notification Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Chapter 4. Pipe and REXX PPI Enhancement s . . . . . . . . . . . . . . . . . . . . . .394.1 SPLIT Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394.2 APPEND Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404.3 NLS Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .414.4 DELDUPES Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .424.5 VARLOAD Stage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .434.6 INSTORE Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .444.7 EDIT Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .454.8 EXPOSE Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464.9 QSAM Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .474.10 LOOKUP Stage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .484.11 TAKE/DROP Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .504.12 PPI Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .504.13 REXX PPI Interface: DSIPHONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Chapter 5. RODM/GMFHS Enhancement s . . . . . . . . . . . . . . . . . . . . . . . . . .555.1 Cloning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .555.2 Date/Time for Formatting or Printing of the RODM Log . . . . . . . . . . . . . . .56


6/405iv An Introduction to Tivoli NetView for OS/390 V1R2

5.3 Automatic Restart Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.4 RODM Checkpoint Data Set Failure Handling . . . . . . . . . . . . . . . . . . . . . 57

Chapter 6. MVS TCP/IP Suppor t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.1 Software Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

6.1.1 Software Customization - DSIPARM . . . . . . . . . . . . . . . . . . . . . . . . 596.1.2 TSO Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626.1.3 Software Customization - TCP/IP Definitions . . . . . . . . . . . . . . . . . . 62

6.2 AON MVS TCP/IP Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636.2.1 TCP/IP Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646.2.2 Issue PING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676.2.3 MVS TCP/IP Session Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696.2.4 Issue TSO Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.2.5 Trace Route Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 7. Event/Automation Servic e . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777.1 Event/Automation Service Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.1.1 Prepare IHSAEVNT Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787.1.2 Customizing the NPDA Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807.1.3 Workstation Software Instal lation . . . . . . . . . . . . . . . . . . . . . . . . . . . 807.1.4 Tivoli Enterprise Console Preparation . . . . . . . . . . . . . . . . . . . . . . . 82

7.2 Events from Tivoli Enterprise Console to OS/390 . . . . . . . . . . . . . . . . . . 847.3 Alerts from OS/390 to TEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.4 Messages from OS/390 to TEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 8. Miscellaneous Enhancement s . . . . . . . . . . . . . . . . . . . . . . . . . 978.1 SETCONID Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978.2 IDLEOFF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

8.2.1 IDLEOFF Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998.2.2 IDLEOFF Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008.2.3 IDLEOFF Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

8.3 Allocate/Free DD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028.4 Console Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038.5 Timer Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

8.5.1 New Options for the DEFAULTS Command . . . . . . . . . . . . . . . . . . 1058.5.2 New Options for the OVERRIDE Command . . . . . . . . . . . . . . . . . . 1058.5.3 New Options for the AT and AFTER Commands . . . . . . . . . . . . . . 1068.5.4 New Options for the EVERY Command . . . . . . . . . . . . . . . . . . . . . 106

8.6 Storage Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068.7 Log, Member Browse and List CLIST Enhancements . . . . . . . . . . . . . . 1098.8 MSM Initialization Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108.9 LISTAE CLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108.10 ASSIGN Command Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128.11 DOM Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148.12 CMIP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

8.12.1 Prerequisi tes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168.12.2 Start Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168.12.3 Migration Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

8.13 AON and MultiSystem Manager Integration . . . . . . . . . . . . . . . . . . . . . 117


7/405

v

Part 2. Graphical Monitoring of Network Resource s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Chapter 9. NetView Management Consol e . . . . . . . . . . . . . . . . . . . . . . . . .1219.1 Installation and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

9.1.1 NetView Management Console Installation . . . . . . . . . . . . . . . . . . .1229.1.2 Operating the NetView Management Console Server . . . . . . . . . . .140

9.2 Understanding NetView Management Console . . . . . . . . . . . . . . . . . . . .1429.2.1 NetView Management Console Main Menu . . . . . . . . . . . . . . . . . . .1449.2.2 NetView Management Console Window Customization . . . . . . . . . .1469.2.3 Managing Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1499.2.4 NetView Management Console Console Properties . . . . . . . . . . . . .1519.2.5 View Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1629.2.6 Resource Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1679.2.7 Display Status History and Alert History . . . . . . . . . . . . . . . . . . . . .1719.2.8 Topology Display Subsystem View . . . . . . . . . . . . . . . . . . . . . . . . .178

9.3 Command Profile Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1829.3.1 Creating a Command Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1849.3.2 Creating a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

9.3.3 Creating an Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1879.3.4 Saving a Command Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

9.4 NetView Management Console Command Support . . . . . . . . . . . . . . . . .1899.4.1 Command Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .1899.4.2 Command Service Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1899.4.3 NetView/390 Commands from the NMC Client . . . . . . . . . . . . . . . .1909.4.4 NetView 3270 Java Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Chapter 10. Tivoli Management Region Featur e . . . . . . . . . . . . . . . . . . . .19710.1 Tivoli Management Region Feature Customization . . . . . . . . . . . . . . . .198

10.1.1 Automation Table Customization . . . . . . . . . . . . . . . . . . . . . . . . . .19810.1.2 MultiSystem Manager Initialization Members . . . . . . . . . . . . . . . . .19910.1.3 MultiSystem Manager Exception Views . . . . . . . . . . . . . . . . . . . . .20010.1.4 Installing the MSM Agent Software . . . . . . . . . . . . . . . . . . . . . . . .20110.1.5 Customizing Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . .20210.1.6 Customizing TME 10 Distributed Monitoring . . . . . . . . . . . . . . . . .20210.1.7 Configuring the Tivoli Management Region Agent . . . . . . . . . . . . .214

10.2 Tivoli Management Region Process Flows . . . . . . . . . . . . . . . . . . . . . .21510.2.1 MultiSystem Manager INITTOPO and GETTOPO Flow . . . . . . . . .21510.2.2 MultiSystem Manager Flow for Status Changes . . . . . . . . . . . . . .21710.2.3 Sending Commands to TME Resources from NetView/390 . . . . . .219

10.3 Operating the Tivoli Management Region Services . . . . . . . . . . . . . . . .22010.3.1 Starting the MultiSystem Manager Agent . . . . . . . . . . . . . . . . . . . .22010.3.2 Verifying Command Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22210.3.3 Stopping the MultiSystem Manager Agent . . . . . . . . . . . . . . . . . . .223

10.4 MSMAgent Topology with NetView Management Console . . . . . . . . . .22310.4.1 Tivoli Management Region Object Hierarchy . . . . . . . . . . . . . . . . .22310.4.2 Exception Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22910.4.3 Resource-Specific Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .230

10.5 Secure TCP/IP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232

Chapter 11. NetWare Agen t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23311.1 Customization of the MultiSystem Manager NetWare Environment . . . .23311.2 Customization of the NetWare Agent Code . . . . . . . . . . . . . . . . . . . . . .23711.3 NetWare Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240


8/405vi An Introduction to Tivoli NetView for OS/390 V1R2

11.3.1 NetWare Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24011.3.2 NetWare Resource-Specific Commands . . . . . . . . . . . . . . . . . . . 248

Chapter 12. Topology Correlatio n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25112.1 Correlation Concept and Implementation . . . . . . . . . . . . . . . . . . . . . . . 251

12.1.1 Correlation Method Implementation . . . . . . . . . . . . . . . . . . . . . . . 25212.1.2 Modifying FLBSYSD Member of SNA Topology Manager. . . . . . . 255

12.2 Default Correlation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25512.3 Free-Form Text Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Chapter 13. Visual BLDVIEW S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25913.1 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

13.1.1 Software Installation on the Workstation . . . . . . . . . . . . . . . . . . . 25913.1.2 Software Installation on the Host . . . . . . . . . . . . . . . . . . . . . . . . . 259

13.2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26013.3 Resource Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

13.3.1 Network Resource Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26313.3.2 Selective Control Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26513.3.3 View Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

13.4 Build/Set Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26713.5 Build Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

13.5.1 Sample Building Network View . . . . . . . . . . . . . . . . . . . . . . . . . . 27113.5.2 An Example of an Exception View . . . . . . . . . . . . . . . . . . . . . . . . 28113.5.3 Using Wildcards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

13.6 Visual BLDVIEWS and RODMVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Part 3. New NetView Interface s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Chapter 14. NetView 3270 Java Clien t . . . . . . . . . . . . . . . . . . . . . . . . . . . 29514.1 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

14.1.1 Software Installation on MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29514.1.2 Software Installation on a Windows 95 Workstation . . . . . . . . . . . 296

14.2 How to Work with NetView Java Client . . . . . . . . . . . . . . . . . . . . . . . . 30414.2.1 Log On to TME 10 NetView for OS/390 . . . . . . . . . . . . . . . . . . . . 30414.2.2 Command Facil ity Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30614.2.3 Other Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31014.2.4 Hardware Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31014.2.5 Define a New Full-Screen Session . . . . . . . . . . . . . . . . . . . . . . . . 31114.2.6 Managing Your Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Chapter 15. Web Access to NetView/39 0 . . . . . . . . . . . . . . . . . . . . . . . . . 31715.1 Software Installation on MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31715.2 Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

15.3 Issuing Commands Using the Web Browser . . . . . . . . . . . . . . . . . . . . 320Chapter 16. DB2 Access from NetView/39 0 . . . . . . . . . . . . . . . . . . . . . . . 32516.1 Activating DB2 Access for NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . 32516.2 DB2 Access PIPE Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

16.2.1 SQL Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32716.2.2 SQLCODES Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32816.2.3 SQSELECT Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

16.3 DB2 Access Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32916.3.1 Creating DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32916.3.2 Automation to Collect Data from System . . . . . . . . . . . . . . . . . . . 331


9/405

vii

16.3.3 Automation Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333

Chapter 17. Commands to OS/390 UNIX (OpenEditio n) . . . . . . . . . . . . . .33517.1 Defining the UNIX Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33517.2 Starting the UNIXSERV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33717.3 Stopping the UNIXSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33817.4 Issuing Commands to OS/390 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . .33817.5 Command Server (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340

Chapter 18. Commands to TS O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34318.1 Defining the TSOSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34318.2 Starting the TSOSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34418.3 Stopping the TSOSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34518.4 Issuing Commands to TSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34618.5 Command Server (TSO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348

Part 4. Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351

Appendix A. Sample Control File s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353A.1 Output from nvtec.sh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Appendix B. Sample REXX Program s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357B.1 LISTAE CLIST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357B.2 Initializing DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358B.3 Creating Object with Correlater Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360B.4 VBDENETF REXX Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361B.5 VBDNOTF.REX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364B.6 EML5224 Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Appendix C. Sample JCL s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369C.1 Copy EAS to OpenEdition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Appendix D. Special Notice s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Appendix E. Related Publication s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373E.1 International Technical Support Organization Publications. . . . . . . . . . . . . . 373E.2 TME 10 NetView for OS/390 V1R2 Publications. . . . . . . . . . . . . . . . . . . . . . 373

List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375

How to Get ITSO Redbook s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377How IBM Employees Can Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . 377How Customers Can Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378IBM Redbook Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381

ITSO Redbook Evaluatio n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393


10/405viii An Introduction to Tivoli NetView for OS/390 V1R2


11/405

Copyright IBM Corp. 1998 ix

Preface

This redbook will help you install, tailor and configure the new functions in TME10 NetView for OS/390 V1R2. This redbook is divided into three sections:

1. Automation enhancements

This section will help you understand all the automation enhancementsincluding management of TCP/IP resources and TCP/IP sessions to TCP/IPfor MVS. You will find examples of how notification and inform policies can beused to send TEC events and e-mail. We provide examples of how NetViewcan send messages and alerts to TEC and how to send TEC events toNetView. The automation table testing and PIPE enhancements are alsodescribed in this section.

2. Graphical monitoring of network resources

This section will help you install, tailor and use the new Java-based graphicaluser interface called NetView Management Console. The Tivoli MultiSystemManager agent allows you to manage your distributed Tivoli environments

from TME 10 NetView for OS/390 V1R2. We provide you with information onhow to install and customize the agent and the prerequisite products such asTivoli Enterprise Console and TME 10 Distributed Monitoring. The newNetWare agent with TCP/IP support and access to NDS is also covered in thissection. We provide examples of how you can use the Visual BLDVIEWS toolto create customized views for NGMF and NetView Management Console. Inaddition you find examples of the new topology correlation functions.

3. New NetView interfaces

The 3270 Java client allows you to access NetView through TCP/IP and runNetView applications from many Java-capable workstations. The Web serverallows you to send NetView commands and receive responses using a Webbrowser. The new PIPE SQL stages makes it possible to access DB/2 fromNetView. You find some program examples showing the capability of this newinterface. The TSO server and UNIX server allow you to issue TSO andOS/390 UNIX commands from NetView.

The Team That Wrote This RedbookThis redbook was produced by a team of specialists from around the worldworking at the Systems Management and Networking ITSO Center, Raleigh.

Arne Olsson is an International Technical Support Organization specialist at theSystems Management and Networking ITSO Center, Raleigh. His responsibilitiesat the ITSO include TME 10 NetView for OS/390 and TME 10 Global EnterpriseManager. Before joining the ITSO he worked as a Systems Engineer in Swedenfor 18 years primarily with network and systems management solutions for largecustomers.

Brett Petersen is a Systems Management Specialist in South Africa. He has 14years of experience in the IT field, of which the last six have been in the systemsmanagement arena.

Budi Darmawan is an Advisory I/T Specialist in IBM Indonesia. He has five yearsof experience in system and network management. He has worked at IBM for


12/405x An Introduction to Tivoli NetView for OS/390 V1R2

eight years. His areas of expertise include Tivoli and general systemmanagement in mainframes and distributed systems.

Francois Lepage is a Customer Service I/T Specialist in IBM France. He has sixyears of experience in system and network management. He has worked at IBMfor 13 years. His areas of expertise include NetView for OS/390, SystemAutomation and Helpdesk. He was responsible for the first NGMF V2R3implementation with nine network environments at a large Europeanmanufacturing customer.

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

Kathryn CasamentoCarla SadtlerKarl WozabalSystems Management and Networking ITSO Center,Raleigh

Anthony Boddie

Scott BrownLarry GreenBill IrlbeckRob JohnsonPam McleanSteve MonroeSimon PercivalPaul QuigleyBob RisleyChris SchaubachDavid SchmidtGregory SmithJeff WeinerIBM RTP, Tivoli NetView for OS/390 Development

Sandy KlemashRoy MitchellAngela PittsKay SintalMark WrightIBM RTP, Tivoli NetView for OS/390 Beta Programs


13/405

Copyright IBM Corp. 1998 1

Chapter 1. Introduction to TME 10 NetView V1R2

This chapter provides you with a brief overview of the new and enhancedfunctions in TME 10 NetView for OS/390 V1R2. We also provide you with someinformation about the configuration we used during the residency. A complete listof all the hardware and software requirements for each TME 10 NetView forOS/390 V1R2 function is provided in the announcement letter and also in theTME 10 NetView for OS/390 V1R2 Planning Guide .

The first question you might ask yourself is why is the book called An Introduction to Tivoli NetView for OS/390 V1R2 and not An Introduction to TME 10 NetView for OS/390 V1R2 . The reason is that the that all new products will use the Tivolibrand name rather than the TME 10 brand name. The decision to change to theTivoli brand name was taken just before the announcement of TME 10 NetViewfor OS/390 V1R2, so this name change was not implemented in this release ofthe product.

Another important topic these days is whether products are ready for the year

2000. TME 10 NetView for OS/390 V1R2 is ready for the year 2000 and this isnow documented in the announcement letter.

1.1 Summary of TME 10 NetView for OS/390 V1R2 FunctionsThis release of NetView for OS/390 contains many new functions addressingmany different areas. For example, you might have a special interest inautomation or how you can manage your networks resources graphically. Wegrouped the new functions into three different sections in this redbook to make iteasier to find the topics of most interest to you.

NetView Automation Enhancements

Automation table enhancementsThe automation table enhancements include the capability to test theautomation table prior to putting it into production. You can have multipletables and turn portions of the automation table on and off. You find adescription in Chapter 2, Automation Table Enhancements on page 9.

Automation notification

The AON function in TME 10 NetView for OS/390 V1R2 now allows youdefine a notification policy for notification when a certain network devicehas encountered a problem. The notification method can be the use of apager, e-mail, alerts or TEC events. In TME 10 NetView for OS/390 V1R1 anew RODM status called Automation In Progress was defined. In TME 10

NetView for OS/390 V1R2 you have a new RODM status called OperatorIntervention Required. When no more automation is defined for a particularresource you can enable the linking of this object to the new OperatorIntervention Required View (refer to Chapter 3, Automation NotificationEnhancements on page 23 ).

Pipe enhancements

Several new PIPE stages have been added in this release including, SPLIT,APPEND, NLS, DELDUPES, VARLOAD and INSTORE. Existing pipestages have been enhanced including the EDIT, EXPOSE, QSAM,LOOKUP and TAKE/DROP stages. There are examples of these new and


14/4052 An Introduction to Tivoli NetView for OS/390 V1R2

enhanced PIPE stages in Chapter 4, Pipe and REXX PPI Enhancementson page 39 .

RODM/GMFHS enhancements

Cloning and ARM support was introduced in TME 10 NetView for OS/390V1R1. In TME 10 NetView for OS/390 V1R2 Cloning and ARM support isnow provided for RODM and GMFHS. You can take advantage of the newstart date/time and stop date/time parameters when printing the RODM log.Using these parameters will help reduce the amount of output. This releaseprovides you with new options on how to handle RODM checkpoint failures.You will find a description of these functions i n Chapter 5, RODM/GMFHSEnhancements on page 55 . You can also find additional information aboutcloning and ARM in An Introduction to TME 10 NetView V1R1, SG24-4922.

MVS TCP/IP suppor t

TME 10 NetView for OS/390 V1R2 provides management functions forMVS TCP/IP resources. The AON component has been enhanced toprovide NetView 390 operators with this capability. The TCP/IPmanagement includes the ability automate management of TCP/IPresources (refer to Chapter 6, MVS TCP/IP Support on page 5 9).

Event Automation Service

Event Automation Service has been integrated into TME 10 NetView forOS/390 V1R2. Event Automation Services was previously available in theGlobal Enterprise Manager. It provides the required adapters to sendmessages and alerts from TME 10 NetView for OS/390 V1R2 to TivoliEnterprise Console. Events from Tivoli Enterprise Console can also besent to TME 10 NetView for OS/390 V1R2 giving you flexibility to choosewhich platform you want to manage your environment from. The EventAutomation Service is described in Chapter 7, Event/Automation Serviceon page 77 .

Miscellaneous enhancementsThis chapter documents many of the enhanced commands and some of thesamples shipped with TME 10 NetView for OS/390 V1R2. Enhancedcommands in this release includes SETCONID, IDLEOFF,ALLOCATE/FREE, CONSOLE, BROWSE and LIST.

Timer commands such as AT, AFTER and EVERY have also beenenhanced.

Some of the samples shipped with TME 10 NetView for OS/390 V1R2 aredescribed such as MEMSTAT, which allows you to keep frequently usedmembers in storage. You find examples of these enhancements i n Chapter8, Miscellaneous Enhancements on page 9 7.

Graphical Monitoring of Network Resources

NetView Management Console

In addition to NGMF this release provides you with a new Java-basedgraphical user interface. NetView Management Console consists of aserver and a client component. The client uses Java and provides you witha platform-independent solution to manage your network resourcesgraphically (refer to Chapter 9, NetView Management Console on page121 ).


15/405

Introduction to TME 10 NetView V1R2 3

Tivoli Topology Service

The Tivoli Topology Service from Global Enterprise Manager has beenintegrated into TME 10 NetView for OS/390 V1R2. This function allows youto manage your distributed Tivoli environment from TME 10 NetView forOS/390 V1R2. This is described in Chapter 10, Tivoli Management RegionFeature on page 197 . You can find additional information in TME 10 Global Enterprise Manager, Topology Service and NetView Java Client ,SG24-2121.

NetWare agent

There is a new NetWare agent that uses TCP/IP communication to TME 10NetView for OS/390 V1R2. This new NetWare agent has also beenenhanced to access NetWare Directory Service (NDS). An overview ofthese functions is provided in Chapter 11, NetWare Agent on page 23 3. Amore comprehensive description of how to manage NetWare from NetViewfor OS/390 can be found in Managing NetWare Environments from MVS Using NPM, MSM-NetWare, SG24-4527.

Visual BLDVIEWS

Managing your network using NGMF or NetView Management Consolemay require that you want to create customized views. The VisualBLDVIEWS tool allows you to create such customized views more easily.The tool runs on a workstation and uses drag and drop technique tocustomize your views before uploading the views to RODM. The VisualBLDVIEWS tool can also be used to display and change values of objectsin RODM, using RODMVIEW (refer to Chapter 13, Visual BLDVIEWS onpage 259 ).

Topology correlation

Topology correlation is enhanced and allows dynamic correlation ofnetworking resources. You can also specify correlation on user-definedvalues. You find a description and examples i n Chapter 12, TopologyCorrelation on page 251 .

New NetView Interfaces

NetView 3270 Java Client

The 3270 Java Client allows access to TME 10 NetView for OS/390 V1R2from AIX, Windows 95/NT, OS/2, HP-UX and Sun Solar is. It uses TCP/IP tocommunicate with TME 10 NetView for OS/390 V1R2 and allows you to runcommand facility and full-screen applications. I n Chapter 14, NetView3270 Java Client on page 29 5 you find information on how we used it onWindows/95.

Web Access to TME 10 NetView for OS/390 V1R2

Using the TME 10 NetView for OS/390 V1R2 Web server function you cansend commands to TME 10 NetView for OS/390 V1R2 using a Webbrowser. This is described in Chapter 15, Web Access to NetView/390 onpage 317 .

DB/2 access from NetView

The DB/2 access is provided by the new PIPE SQL stages. You can find adescription and examples of how to use this interface i n Chapter 16, DB2Access from NetView/390 on page 32 5.



Commands to TSO

Using the new TSO server function you can issue commands to TSO fromTME 10 NetView for OS/390 V1R2. If you want to send NetView commandsfrom TSO, you can use the provided sample CNMS8029. These functionsare described in Chapter 18, Commands to TSO on page 34 3.

Commands to OS/390 UNIX

The UNIX server function allows you to send commands from TME 10NetView for OS/390 V1R2 to OS/390 UNIX. The sample CNMS8029 canbe used to send commands from OS/390 UNIX to NetView. You will find adescription of these functions in Chapter 17.4, Issuing Commands toOS/390 UNIX on page 33 8.

1.2 ITSO Residency EnvironmentThe following is a high-level diagram of the environment we used during ourresidency at the ITSO.

Figure 1. ITSO Configuration


17/405

Introduction to TME 10 NetView V1R2 5

1.3 Dependencies for Various TME 10 NetView for OS/390 V1R2 FunctionsIn Table 1 , we list the prerequisites for each function that we used during theresidency. You should refer to the official documentation for a complete list ofhardware and software prerequisites. Table 1 is provided for you to see the levelswe used during our residency.

We used the Enterprise Option of TME 10 NetView for OS/390 V1R2. Thehigh-level language used for TME 10 NetView for OS/390 V1R2 was AD/CycleLE/370. TME 10 NetView for OS/390 V1R2 was installed on an OS/390 R3system with TCP/IP for MVS V3R2. All features that do not appear in the list haveall the prerequisites available in the MVS portion of TME 10 NetView for OS/390V1R2.

Table 1. Feature Dependency Summary

Feature Dependency/Requirement

Automation Notification Event Automation Service is needed for TEC event notification

TCP/IP for MVS Management Commands to TSO (TSOSERV)

Event Automation Service AIX 4.2Tivoli Framework 3.2Tivoli Enterprise Console 3.1

NetView Management Console NetView Management Console server on Windows NT 4.0 withTCP/IP and SNA connection to MVSNetView Management Console client on Windows NT 4.0 with TCP/IPconnection to NetView Management Console serverJDK 1.1.6

Tivoli Management Region Feature AIX 4.2Tivoli Framework 3.2Tivoli Enterprise Console 3.1Tivoli Distributed Monitoring 3.5

NetWare Agent NetWare 4.11 Server

Visual BLDVIEWS Windows NT workstation with TCP/IP connection to TME 10 NetViewfor OS/390 V1R2

Topology Correlation MultiSystem Manager Agent for TivoliMultiSystem Manager Agent for IPLNM 2.0

3270 Java Client Windows/95 Workstation with Java 1.1.6 and TCP/IP connection

Web Access to TME 10 NetView forOS/390

TCP/IP connection and Netscape Web Browser

DB2 Access from TME 10 NetView forOS/390 DB2 V5

UNIX Server OS/390 R3 and OS/390 UNIX (formerly known as OpenEdition)


19/405


Part 1. NetView Automation Enhancements


21/405


Chapter 2. Automation Table Enhancements

The automation table enhancements in TME 10 NetView for OS/390 V1R2 allowyou to test your automation table to see what would have happened if this tablewas put into production. You can now work with multiple logical tables and thenew loading function allows you to add and remove segments of the automationtable.

2.1 New AUTOTEST CommandPreviously, the AUTOTBL command had a TEST keyword, which enabled you tocatch incorrect automation table syntax. It was not able to handle other kinds ofproblems, such as:

Logical errors

Maybe you created a logical error by simply forgetting quotes.

Ordering errors

Maybe you have a generic automation table entry and you forgot to codeCONTINUE=YES.

Unintended matching

Maybe you have had messages and alerts match on statements not intendedto.

Not matching on a statement as intended due to a mismatch

Perhaps you failed to match on a message or alert because you coded themessage or alert details incorrectly in the automation table.

One message or alert matching on multiple statements unexpectedly

Maybe you have seen cases where a message or alert matched multiplestatements and that wasn't what you intended.

The new AUTOTEST command helps you to avoid these problems. It enables youto discover and correct any logic, typographical, or ordering problems prior toputting a new automation table into your production environment. It has thecapability to simulate production messages and MSUs and run them through atest automation table in batch mode.



2.1.1 AUTOTEST SyntaxThe syntax of the AUTOTEST command is:

AUTOTEST OFF - Turn off testingSTATUS - Show current TESTING status.MEMBER=name, - Table member name for testing

DD=DSIPARM/DSIASRC, - DD name of table memberLISTING=name, - Listing fileREPLACE - Replace member of the same name

SOURCE=OFF - Turn off messages and alerts=PARALLEL - Take production input in parallel=sname - Take input stored in a file

TASKNAME=taskname, - Autotask that does the processing.REPORT=repname, - Output report member name

RPTREPL - Replace member of the same nameRECORD

=OFF - Turn off recording of msg traffic=recname, - Store messages/alerts in file

LOGREPL - Replace member of same name

There is a new task that must be started before automation table testing can takeplace. This is the DSIATOPT task and it is started with the command:

START TASK=DSIATOPT

Note: The AUTOCNT statement has a new TEST parameter related to theAUTOTEST command. You can specify the TEST parameter to request a reportfor the automation table being tested with the AUTOTEST command.

2.1.2 Logical FlowsThe AUTOTEST command has multiple options. The following pages give you ahigh-level flow of how these options work. Three functions are described:

AUTOTEST testing options

AUTOTEST in batch mode

AUTOTEST stop options

AUTOCNT RESET REPORT=MSG/MSU/BOTH TEST


23/405

Automation Table Enhancements 11

Figure 2. AUTOTEST Testing Options

Messages and alerts flow from NetView interfaces 0 into the active automationtable. If you use the automation table testing capability, you will use a test table.The testing of the test automation table can be done in either batch mode or inparallel with the active automation table . Figure 2 shows you the high-level flowfor the testing options and how to obtain input for your test table:

With the Record parameter 1 you can store messages and alerts from thenormal flow in a data set (AUTOTEST RECORD=Member). The elements inthis file are in AIFR block format. The recorded member is stored in a new DDname: DSIASRC. When you have recorded enough messages use the OFFoption on the Record parameter (AUTOTEST RECORD=OFF).

After recording messages, you have to use the sname option from the Sourceparameter 2 of the AUTOTEST command to use the recorded messages andalerts for your testing (AUTOTEST MEMBER=Membername,SOURCE=Source name).

With the Parallel option the normal flow of messages and alerts 3 can be usedfor testing in parallel with the active automation table (AUTOTESTMEMBER=Member name,SOURCE=PARALLEL).



Figure 3. AUTOTEST in Batch Mode

If you have previously chosen to save the input messages and aler ts in a file, thenyou need to issue the AUTOTEST command again and you need to specify whichautomation table member you want to use. The automation table you havespecified 4 in the Member parameter will be compiled and stored in memory asthe AUTOTBL command does with active automation table.

You can specify an automation table member from DSIPARM or DSIASRC DDnames. The source file member is in the DSIARSC DDNAME with the name usedwhen recording the messages and alerts. The result of the testing is documentedin a report member 5 in a new DD name: DSIARPT. The Listing option creates alisting of the tested table in the DSILIST DD name. The automation table listing isused to map the report file with the statements numbers in the tested table. Thelisting and report parameters are both required.


25/405


Figure 4. AUTOTEST Stop Options

If you use the option Source=parallel 6 , then you can stop processing by issuingthe AUTOTEST=OFF command 9 to clear your test environment and remove thetest table from memory.

The other option is to use Source=OFF 7 . This option gives you the ability to retrythe AUTOTEST command without reloading and recompiling the test table. In factthe compiled test table is still loaded in memory. NetView will look for an alreadycompiled and loaded table if you omit the member= option in the AUTOTESTcommand. This gives you the ability to use, for example, another source and thealready compiled and loaded table.

If you have chosen to test recorded messages from an input file 8 , then theAUTOTEST process will automatically stop at the end of the input file.

When all your tests are finished 9 , then you can clear the AUTOTESTenvironment with the AUTOTEST OFF command 10 . The compiled test table willbe removed from storage.



2.1.3 AUTOTEST ExamplesIn Figure 5 the first command starts recording of messages and alerts in amember called TESTREC, which will be used later as input to test the automationtable in batch mode. The second command switches recording off.

Figure 5. AUTOTEST Command with Record Option

In Figure 6 we used the AUTOTEST command to test DSITBL01, with the inputbeing the file created previously, TESTREC, the LISTING file being TESTLISTand the output being generated to TESTREPT.

Figure 6. AUTOTEST Command with Source Option

Figure 7 shows the content of the listing member TESTLIST. As you can see, itcontains the automation table source statements as well as statement numbers.

Figure 7. AUTOTEST Listing Result

The following is the TESTREPT file generated by the AUTOTEST command. Notethat each message that was generated goes through the entire automation tablemember, producing information on the number of hits, statement number of the hitand the automation table member name of the statement.

NCCF TME 10 NetView RABAN TMEID4 05/29/98 16:19:02* RABAN AUTOTEST RECORD=TESTREC- RABAN BNH345I AUTOMATION RECORDING TO MEMBER TESTREC IS ACTIVATED A

05/29/98 16:17:50 BY TMEID4' RABAN P%

* RABAN AUTOTEST RECORD=OFF- RABAN BNH342I AUTOMATION RECORDING STOPPED, MEMBER = TESTREC

-------------------------------------------------------------------------------???

NCCF TME 10 NetView RABAN TMEID4 05/29/98 16:40:32* RABAN AUTOTEST

MEMBER=DSITBL01,LISTING=TESTLIST,SOURCE=TESTREC,REPORT=TESTREPT- RABAN BNH347I TEST AUTOMATION TABLE LISTING TESTLIST SUCCESSFULLY

GENERATED- RABAN BNH336I DSIPARM MEMBER DSITBL01 IS BEING USED FOR NETVIEW

AUTOMATION TABLE TESTING- RABAN BNH340I AUTOMATION TABLE TESTING IS ACTIVATED AT 05/29/98 16:40:32

BY TMEID4- RABAN BNH341I AUTOMATION TABLE TESTING SOURCE = TESTREC, REPORT =

TESTREPT, TASK = NONE- RABAN BNH382I AUTOMATION TABLE TESTING STOPPED, SOURCE = TESTREC-------------------------------------------------------------------------------

************************************************************************ NOTE: THE NEXT FOUR STATEMENTS SET SYNONYMS FOR STATMON IMPORTANT ** MESSAGE INDICATORS. *************************************************************************0001 001 SYN %NETL1% = 'NETLOG(YES 1 +STATGRP)';

0002 001 SYN %NETL2% = 'NETLOG(YES 2 +STATGRP)';0003 001 SYN %NETL3% = 'NETLOG(YES 3 +STATGRP)';0004 001 SYN %NETL4% = 'NETLOG(YES 4 +STATGRP)';*0005 001 SYN %NV_DOMAIN% = 'RABAN';


27/405


Figure 8. AUTOTEST Output Report File

>> Automation table test of member DSIPARM.DSITBL01 Listing: TESTLIST>> Time: 05/29/98 16:40:32 Requesting operator: TMEID4 Source: TESTREC

-----------> Input number: 1. Type = Message --------------

DSI208I TIME EXPIRATION - ID= 'ADOIV ' - CMD= 'EZLEOIVT'

Matches: 7 Comparisons: 39Match Location Location Type Member----- ---------------- ---------------- --------

01. 39 Statement Number DSITBL0102. 89 Statement Number EZLDSIAO03. 90 Statement Number EZLDSIAO04. 91 Statement Number EZLDSI2005. 339 Statement Number FKVMSU0106. 347 Statement Number FKWMSU0107. 372 Statement Number CNMSIHSA

-----------> Input number: 2. Type = Message --------------

IST663I CDINIT REQUEST FROM RAK FAILED , SENSE=08570003

IST664I REAL OLU=USIBMRA.RAKT20A REAL DLU=USIBMRA.RABT11AIST889I SID = F8D3D16440ABF817IST264I REQUIRED RESOURCE RABT11A NOT ACTIVEIST314I END

Matches: 6 Comparisons: 44Match Location Location Type Member----- ---------------- ---------------- --------

01. 122 Statement Number DSITBL0102. 124 Statement Number FKVISTAO03. 231 Statement Number FKVISTAO04. 235 Statement Number FKVSA6005. 339 Statement Number FKVMSU01



2.2 New AUTOTBL DesignThe enhancements to automation table loading in TME 10 NetView for OS/390V1R2 enable you to make changes to the automation table flexibly and easily. Inprevious releases of NetView, you had only one table loaded and compiled inmemory. This table can be composed of multiple physicals members if you use

%INCLUDE statements in your main table. Once loaded the table was searchedas one logical entity and you had to code CONTINUE(YES) on your automationtable statements to allow processing to continue after the first match.

2.2.1 Principles of Multiple TablesIn TME 10 NetView for OS/390 V1R2, it is possible to have several automationtables that can include many members. In Figure 9 you see several logical tables;each logical table includes several members. The advantage is that individualmembers can be loaded, replaced or unloaded, without having to disable theentire automation table.

Figure 9. AUTOTBL Multiple Logical Tables

In Figure 9 we have three tables: A, B and C. Once loaded, tables A,B and C willbe searched as separate entities. Having separate tables could makemaintenance of your automation table easier since you don't have to ensure thatCONTINUE(YES) is coded in your automation table statements for processing tocontinue. Within each logical table CONTINUE(YES) allows processing tocontinue and CONTINUE(NO) stops processing in the current table. If you haveseveral logical tables loaded, the next logical table will be searched. If you do notwant processing to continue to the next logical table, you must use theCONTINUE(STOP) option.


29/405


2.2.2 AUTOTBL Syntax DetailThe syntax of the AUTOTBL command is as follows:

AUTOTBL OFF - Turns automation processing OFFSTATUS - Lists the status of all tablesMEMBER=membername - Member name of table

TEST - For syntax checkingSWAP AT=number - Swap this table for one already

loadedINSERT AT=number - Insert this table AT table number

BEFORE=number - Insert BEFORE table numberAFTER=number - Insert AFTER table numberFIRST - This table will be the FIRST tableLAST - This table will be the LAST table

LISTING=name - Create a table LISTINGREPLACE - Replace listing with same name

DISABLE/ENABLE NAME=name - DISABLE or ENABLE this table nameSEQUENCE=seqnum - Only this one statementLABEL=label - Only the statement with LABELENDLABEL=label - Only the statement with ENDLABEL

BLOCK=label - The block defined by LABEL/ENDLABELpairGROUP=label - All statements with GROUP name

REMOVE NAME=name - remove from the list of activeautomation tables

2.2.3 AUTOTBL ExamplesIn this example, we loaded two message tables, MSGTBL1 and MSGTBL2, withan INSERT of FIRST and LAST respectively. Then we issued an AUTOTBLSTATUS command to list the status of the two tables.

Figure 10. AUTOTBL Insert Option

We used the DISABLE function to disable table MSGTBL1. The status commandtells us that that MSGTBL1 is in a DISABLED state.

NCCF TME 10 NetView RABAN TMEID3 04/28/98 10:08:02* RABAN AUTOTBL MEMBER=MSGTBL1,INSERT FIRST- RABAN DSI410I DSIPARM MEMBER MSGTBL1 BEING USED FOR NETVIEW AUTOMATION* RABAN AUTOTBL MEMBER=MSGTBL2,INSERT LAST- RABAN BNH360I INSERT REQUEST COMPLETED FOR DSIPARM MEMBER MSGTBL2 AT

LOCATION 2 WITHIN THE LIST OF ACTIVE AUTOMATION TABLES* RABAN AUTOTBL STATUS' RABANBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:TMEID4 COMPLETED INSERT FOR TABLE #1: MSGTBL1 AT 05/29/98 10:07:50 (FIRST)TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL2 AT 05/29/98 10:07:55 (LAST)-------------------------------------------------------------------------------



Figure 11. AUTOTBL Disable Option

Figure 12 shows that SYNONYMS are not carried from table member to tablemember. You must include your SYNONYMS in each table.

Figure 12. AUTOTBL Synonyms Resolution

The REMOVE option in Figure 13 shows the flexibility to change the list and orderof tables loaded. You can use timer functions to add or remove tables namesdepending on your needs.

NCCF TME 10 NetView RABAN TMEID4 05/29/98 10:11:47* RABAN AUTOTBL DISABLE,NAME=MSGTBL1- RABAN BNH366I AUTOTBL DISABLE REQUEST COMPLETED FOR NAME: MSGTBL1* RABAN AUTOTBL STATUS' RABANBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:

TMEID4 COMPLETED DISABLE FOR TABLE #1: MSGTBL1 AT 05/29/98 10:11:37 (FIRST)TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL2 AT 05/29/98 10:07:55 (LAST)

' RABANBNH363I THE AUTOMATION TABLE CONTAINS THE FOLLOWING DISABLED STATEMENTS:TABLE: MSGTBL1 INCLUDE: __n/a___-------------------------------------------------------------------------------

NCCF TME 10 NetView RABAN TMEID4 05/29/98 12:28* RABAN AUTOTBL STATUSBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:RABANPPT COMPLETED INSERT FOR TABLE #1: DSITBL01 AT 05/27/98 09:34:32TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 12:20:26 (LAST)

* RABAN AUTOTBL MEMBER=MSGTBL2 INSERT LAST- RABAN DSI412I THE FOLLOWING ERRORS ENCOUNTERED IN PROCESSING DSIPARM

MEMBER MSGTBL2- RABAN CNM585E INVALID SYNONYM USAGE FOR 'NV_DOMAIN'- RABAN DSI417I MSGTBL2 : (NO SEQ) : IF TEXT= .'BNJDSERV'. & %NV_DOMAIN%

='NETV11' THEN EXEC(CMD('SETCGLOBEZLNPDA TO UP') ROUTE(ONE AUTO1));

- RABAN DSI415I END OF MSGTBL2 ERROR DISPLAY- RABAN DSI416I PROCESSING FAILED FOR 'AUTOTBL MEMBER=MSGTBL2 INSERT LAST'

COMMAND- RABAN BNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF

MEMBERS:' RABANRABANPPT COMPLETED INSERT FOR TABLE #1: DSITBL01 AT 05/27/98 09:34:32TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 12:20:26 (LAST)------------------------------------------------------------------------


31/405


Figure 13. AUTOTBL Remove Option

The SWAP option is used in Figure 1 4 to replace the table name specified in theNAME= parameter with the table specified in the MEMBER= parameter.

Figure 14. AUTOTBL Swap Option

In Figure 15 you can see that you cannot replace a table name loaded in first orlast position with the SWAP option if your new table has another name. You mustuse the REMOVE and the INSERT options. However, you can swap the sametable name to activate your changes.

NCCF TME 10 NetView RABAN TMEID4 05/29/98 13:49* RABAN AUTOTBL STATUS' RABANBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:RABANPPT COMPLETED INSERT FOR TABLE #1: DSITBL01 AT 05/27/98 09:34:32TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 12:20:26 (LAST)

* RABAN AUTOTBL REMOVE NAME=MSGTBL1- RABAN BNH360I REMOVE REQUEST COMPLETED FOR DSIPARM MEMBER MSGTBL1 AT

LOCATION 2 WITHIN THE LIST OF ACTIVE AUTOMATION TABLES* RABAN AUTOTBL STATUS- RABAN DSI410I DSIPARM MEMBER DSITBL01 BEING USED FOR NETVIEW AUTOMATION- RABAN DWO040I AUTOMATION TABLE DSITBL01 ACTIVATED 05/27/98 09:34:32

RABANPPT------------------------------------------------------------------------

* RABAN AUTOTBL STATUS- RABAN DSI410I DSIPARM MEMBER DSITBL01 BEING USED FOR NETVIEW AUTOMA- RABAN DWO040I AUTOMATION TABLE DSITBL01 ACTIVATED 05/27/98 09:34:32* RABAN AUTOTBL MEMBER=MSGTBL2 SWAP NAME=DSITBL01- RABAN DSI410I DSIPARM MEMBER MSGTBL2 BEING USED FOR NETVIEW AUTOMATION* RABAN AUTOTBL STATUS- RABAN DSI410I DSIPARM MEMBER MSGTBL2 BEING USED FOR NETVIEW AUTOMATION- RABAN DWO040I AUTOMATION TABLE MSGTBL2 ACTIVATED 05/29/98 14:10:21* RABAN AUTOTBL MEMBER=DSITBL01 SWAP NAME=MSGTBL2- RABAN DSI410I DSIPARM MEMBER DSITBL01 BEING USED FOR NETVIEW AUTOMATION* RABAN AUTOTBL MEMBER=MSGTBL1 INSERT LAST- RABAN BNH360I INSERT REQUEST COMPLETED FOR DSIPARM MEMBER MSGTBL1 AT

LOCATION 2 WITHIN THE LIST OF ACTIVE AUTOMATION TABLES* RABAN AUTOTBL MEMBER=MSGTBL2 SWAP NAME=DSITBL01- RABAN BNH360I SWAP REQUEST COMPLETED FOR DSIPARM MEMBER MSGTBL2 AT

LOCATION 1 WITHIN THE LIST OF ACTIVE AUTOMATION TABLES* RABAN AUTOTBL STATUSBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:TMEID4 COMPLETED INSERT FOR TABLE #1: MSGTBL2 AT 05/29/98 14:17:09TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 14:15:28 (LAST)------------------------------------------------------------------------



Figure 15. AUTOTBL SWAP, FIRST and LAST Restrictions

One of parameters on the ENABLE/DISABLE options is GROUP. This parameterallows you to activate or deactivate a group of messages. You must putGROUP:grpname in the statements you want to group together.

In Figure 16 you see an example of the definitions for some BNH messages wewanted to group together by adding the GROUP definition in the DSITBL02member.

Figure 16. DSITBL02 Disable Group Definitions

In Figure 17 you can see the result when we disabled this BNH35 group.

NCCF TME 10 NetView RABAN TMEID4 05/29/98 14:32BNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:TMEID4 COMPLETED INSERT FOR TABLE #1: MSGTBL1 AT 05/29/98 14:15:28 (LAST)* RABAN AUTOTBL MEMBER=DSITBL01 INSERT FIRST- RABAN BNH360I INSERT REQUEST COMPLETED FOR DSIPARM MEMBER DSITBL01

LOCATION 1 WITHIN THE LIST OF ACTIVE AUTOMATION TABLES

* RABAN AUTOTBL STATUSBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:TMEID4 COMPLETED INSERT FOR TABLE #1: DSITBL01 AT 05/29/98 14:30:05 (FIRST)TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 14:15:28 (LAST)* RABAN AUTOTBL MEMBER=MSGTBL2 SWAP NAME=MSGTBL1- RABAN BNH367E UNABLE TO COMPLETE AUTOTBL SWAP REQUEST. REASON CODE 208* RABAN AUTOTBL MEMBER=DSITBL01 SWAP NAME=DSITBL01- RABAN BNH360I SWAP REQUEST COMPLETED FOR DSIPARM MEMBER DSITBL01 AT

LOCATION 1 WITHIN THE LIST OF ACTIVE AUTOMATION TABLES* RABAN AUTOTBL STATUSBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:TMEID4 COMPLETED INSERT FOR TABLE #1: DSITBL01 AT 05/29/98 14:32:33 (FIRST)TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 14:15:28 (LAST)------------------------------------------------------------------------???

EDIT TME10.RABAN.V1R2.DSIPARM(DSITBL02) - 01.01 Member DSITBL02Command ===> Scroll ===000017 ;000018 * BNH352I THRESHOLD000019 IF MSGID='BNH352I' THEN000020 EXEC(CMD('PIPE SAFE * | TSROUTE'))000021 ;000022 * BNH353I REL THRESHOLD000023 IF (GROUP:BNH35) MSGID='BNH353I' THEN000024 EXEC(CMD('PIPE SAFE * | TSROUTE'))000025 ;000026 * BNH354I CONN CHANGE000027 IF (GROUP:BNH35) MSGID='BNH354I' THEN000028 EXEC(CMD('PIPE SAFE * | TSROUTE'))000029 ;000030 IF MSGID='BNH161I' & ACTIONDL='' & TEXT=MESSAGE THEN000031 DOMACTION(AUTOMATE)

000032 EXEC(CMD('CNME3024 MSG' MESSAGE) ROUTE (ONE AUTOAMI))


33/405


Figure 17. AUTOTBL Disable Group Result

The AUTOTBL Status command shows that the group named BNH35 is disabledin automation table DSITBL02.

NCCF TME 10 NetView RABAN TMEID4 05/29/98 17:06* RABAN AUTOTBL STATUSBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:TMEID4 COMPLETED INSERT FOR TABLE #1: DSITBL02 AT 05/29/98 16:57:55 (TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 14:15:28 (* RABAN AUTOTBL DISABLE NAME=DSITBL02,GROUP=BNH35

- RABAN BNH366I AUTOTBL DISABLE REQUEST COMPLETED FOR NAME: DSITBL02BNH35* RABAN AUTOTBL STATUSBNH361I THE AUTOMATION TABLE CONSISTS OF THE FOLLOWING LIST OF MEMBERS:TMEID4 COMPLETED INSERT FOR TABLE #1: DSITBL02 AT 05/29/98 16:57:55 (TMEID4 COMPLETED INSERT FOR TABLE #2: MSGTBL1 AT 05/29/98 14:15:28 (' RABANBNH363I THE AUTOMATION TABLE CONTAINS THE FOLLOWING DISABLED STATEMENTS:TABLE: DSITBL02 INCLUDE: __n/a___ GROUP : BNH35------------------------------------------------------------------------


35/405


Chapter 3. Automation Notification Enhancements

This chapter discusses the new Notification and Inform policy that comes withAON in TME 10 NetView for OS/390 V1R2. This chapter discusses thisenhancement in the following sections:

Concepts of Automation Notification Implementing Automation Notification

Commands in Automation Notification

RODM Notification with NetView Management Console

3.1 Concept of Automation NotificationFigure 18 shows the concept of notification and inform policy in TME 10 NetViewfor OS/390 V1R2.

Figure 18. Notification and Inform Policy

1 The event happens, and based on the automation table and AON configurationfile, AON can decide to notify an operator.

2 Based on the environment setup, AON can decide to change the correspondingRODM object to show that there is an Automation In Progress (AIP) or put theobject in the Operator Intervention View (OIV). Se e 3.4, RODM NotificationProcessing on page 36 .



3 When AON decides to invoke the notification system using the EZLENFRM orEZLEASLN CLIST, it evaluates the notify policies to determine what notificationshould be sent out and where.

4 If the notification policy includes the statement INFORM=policyname, theINFORM policy is invoked to send notification using e-mail or pager. You can alsodefine your own user-defined method such as FAX as shown in EZLINSMP.

Previously, automation with AON could result in a huge amount of notificationseither using DDF or RODM, and only limited by resource type. With the newautomation notification scheme, we can:

Select by resource name that notification is needed

Select by event type for those resource

Determine the notification methods

The inform policy is one of the notification methods. This inform policy provides amechanized way of informing a certain person or group of persons on an eventby:

Resource name Resource type Event type Day of week Time of day

The sample inform policy provides communication through NetFinity for OS/2. Itsupports pager and e-mail notification.

The notification policy is defined in the AON configuration file (EZLCFG01) andthe inform policy is defined in a member of DSIPARM that is referred fromEZLCFG01. The default is EZLINSMP.

3.2 Implementing Automation NotificationThe following steps show an outline of actions necessary to enable thenotification policy:

Set up the configuration files

Set up notification policy entries

Set up the inform policy

3.2.1 Configuration Files Changes

We perform the following changes to our configuration files (besides thenotification policy):

Changes to DSITBL01 to enable event forwarding to TEC if you need to notifythrough TEC.

This requires that the Event/Automation Service (IHSAEVNT) has beencustomized according to Chapter 7, Event/Automation Service on page 77.AON uses subfield 07 of subvector 10 that contains the word TECUPD . Figure19 shows part of DSITBL01 that we uncommented.


37/405

Automation Notification Enhancements 25

Figure 19. DSITBL01 Update for AON

Modify the ENVIRON SETUP clause in the AON configuration file(EZLCFG01) to establish the notification functions . Figure 2 0 shows theENVIRON SETUP clause.

Figure 20. EZLCFG01 - Definition of ENVIRON SETUP Clause

In this clause we defined:

1 You must specify GENALERT=YES to update RODM and NetViewManagement Console.

2 , 3 and 4 defines the RODM destination and AIP/OIV processing asdescribed in 3.4, RODM Notification Processing on page 3 6.

5 defines the INFORM policy member. ENVIRON AIP that defines the resources to be put into AIP (Automation In

Progress) status. Figure 2 1 shows the ENVIRON AIP clause.

Figure 21. EZLCFG01 - Definition of ENVIRON AIP Clause

Optional modification of THRESHOLD and MONIT definitions to set how themonitoring and threshold will be handled for notification processing.

************************************************************************ BEGINNING OF AON MSU Automation Members: ** ** ** Uncomment the following statement if you want AON events routed ** to the Tivoli Enterprise Console *

* *IF MSUSEG(0000.10.11.07 3)='TECUPD' THENSRF(TECROUTE PASS);

ENVIRON SETUP,NETVIEW=NET,GENALERT=YES, 1 FTAFPFX=TAFA1F,SYSNAME=RABAN,TRACE=NONE,DBMAINT=REUSE,RODMAIP=YES, 2 RODMOIV=YES, 3 RODMNAME=RODM1, 4 HELDMSG=(INFO,WARN,ERROR,ACTION),RODMDOM=RABAN,INFORMPM=EZLINSMP 5

*** AIP ***ENVIRON AIP,LINEPORT=Y, LINE aka PORT resource Types

PULINKSTA=Y, PU aka LINKSTA resource TypesCDRM=Y, CDRM resource TypeNCP=Y, NCP resource TypeLANMGR=Y, LANMGR resource TypeLANBRIDGE=Y LANBRIDGE resource Type



3.2.2 Notification Policy SetupThe notification policy contains the definition of the NOTIFY clauses inEZLCFG01. The NOTIFY clause has the following syntax:

DEFAULTS defines the default notification.

ResourceType:

The resource type for NOTIFY can be any AON-supported resource type. The

supported resource types are defined in EZLRT statements in EZLTABLE,FKVTABLE, FKWTABLE and FKXTABLE. The following are examples of AONsupported resource types:

LINE PU CDRM NCP LANMGR LANPORT LANBRIDGE NAMESERV

ResourceName:

You can put a wildcard at the end of resource name for a group of resourceswith similar names

Eventtype:

CRITTHRS: When critical threshold is exceeded. NOMOMONS: When no more monitoring intervals are defined. REMIND: A reminder that a resource is sti ll down. BRGCONGEST: LAN bridge congestion. ADPCONGEST: LAN adapter congestion. NAMESERV: Name server failure threshold exceeded.

The following parameters define whether these notifications will be generated

or not: ALERT: Generating aler t or TEC event (implies aler t generated) INFORM: Generating inform action with a specific inform policy MSG: Generating messages DDF: Shows the notification on DDF

Exit10 code that can override any notification action.

The NOTIFY definitions that we created are i n Figure 2 2.


39/405


Figure 22. Notification Policy Definition in EZLCFG01

This notification policy defines:

The default is that no notification is generated. For example, if a resourcecalled ABC* failed (and it was not a reminder or critical threshold event), thenno notification would take place.

For resources with a name starting with RABU* we notify by all methods.

For resources that have the name of WTR*, NetView sends INFORM action tothe policy named WTR_POL and sends TEC events.

CRITTHRS events send notification to TEC.

REMIND events will issue messages only.

3.2.3 Information Policy SetupInformation policy setup definition is performed in EZLINSMP as stated in theENVIRON SETUP clause in EZLCFG01. This member can have the %INCLUDEdirective. All lines started with an asterisk '*' are comments.

The following directives are used to define the inform policy:

SETUP This setup defines the global values used in the policy definitions.This directive is only used once. The syntax is:

INFORM This clause defines a group of CONTACT definitions that will beused by this INFORM policy. The syntax is:

CONTACT This clause defines the person or persons this notification policywill contact. You can define on-duty times and how these personsshould be contacted. The syntax is:

NOTIFY DEFAULTS,ALERT=NO,MSG=NO,DDF=NO,INFORM=NONOTIFY RABU*,ALERT=TEC,MSG=YES,DDF=YES,INFORM=ALL_POLNOTIFY WTR*,ALERT=TEC,MSG=NO,DDF=NO,INFORM=WTR_POLNOTIFY CRITTHRS,ALERT=TEC,MSG=NO,DDF=NO,INFORM=NONOTIFY REMIND,ALERT=NO,MSG=YES,DDF=NO,INFORM=NO



GROUP This clause groups a set of inform policies. We can refer to this groupas an inform policy to inform several other policies at one time. Thesyntax for this GROUP clause is:

The setup we did for the inform policy was to have one inform policy for eachperson, and group persons with similar responsibility into one group. In theINFORM definition we used these groups instead of using individual informpolicies. (see Figure 22 ).

Figure 23 shows the contents of our EZLINSMP.


41/405


Figure 23. Contents of Inform Policy in EZLINSMP

We modified the EZLENETF program to call the REXX socket that activates amail program in a Windows 95 workstation. The REXX program in TME 10NetView for OS/390 is called VBDENETF (see B.4, VBDENETF REXX Programon page 361 ). The INTERFACE parameter in our inform policy points to thisroutine. The program in Windows 95 is run under IBM Object REXX for Windows95 and is called VBDNOTF.REX (see B.5, VBDNOTF.REX on page 3 64). Thisprogram uses the mailto freeware that can be found athttp://www.winfiles.com/apps/98/mail-command.html from [email protected].

3.3 Commands in Automation NotificationThere are several commands and CLISTs that can be used in the notification andinform policies.

EZLEASLN: Notification program that uses the notification policy.

SETUP LOG=YES,MEMBER=INFLOG;* ** Define groups so contact statements do not need to be duplicated ** *GROUP ALL_POL,LIST=BUDI,FRANCOIS,ARNE;GROUP WTR_POL,LIST=BUDI,FRANCOIS;

* ** POLICY for Budi ** *INFORM BUDI;CONTACT CONNECTION=EMAIL,

[email protected],NAME=Budi Darmawan,INTERFACE=VBDENETF;

* *CONTACT ONCALLDAY=WEEKDAY,

ONCALLTIME=08:00 to 17:00,CONNECTION=EMAIL,[email protected],NAME=Budi Darmawan,INTERFACE=VBDENETF;

* ** POLICY for Francois ** *INFORM FRANCOIS;CONTACT CONNECTION=EMAIL,

[email protected],NAME=Francois Lepage,INTERFACE=VBDENETF;

* *CONTACT ONCALLDAY=WEEKDAY,

CONNECTION=EMAIL,[email protected],NAME=Francois Lepage,INTERFACE=VBDENETF;

* ** POLICY for Arne ** *INFORM ARNE;CONTACT CONNECTION=EMAIL,

[email protected],NAME=Arne Olsson,INTERFACE=VBDENETF;



INFORMTB: Activate, test or inactivate an INFORM table (similar to AUTOTBLcommand).

INFORM: Informing a certain person (that is, policy name).

ILOG: Inform log panel.

3.3.1 EZLEASLN CommandThis command serves as the API for the notification system. We can utilize thenotification system in our own code by calling this routine. The syntax for callingEZLEASLN is:

This command can be used to trigger a notify event in a REXX program such asthat shown in Figure 24 .

Figure 24. Sample Notification Program

The result of running this sample program is shown i n Figure 2 5.

When testing this example we found that it is best to pass a resource typesupported by AON to EZLEASLN. In the example we used PU as the resourcetype. AON will only generate the alert and TEC notification if the resource type isknown. You can in fact define additional resource types in AON and thereby use

the notification and inform policy and other AON functions for resource typesspecific to your environment.

NCCF TME 10 NetView RABAN TMEID5 07/08/98 00:30:03* RABAN PIPE < DSICLD.SLNSAMP | CONSOLE| RABAN /*REXX Displays the sample NOTIFICATION */| RABAN parse arg status res_type res| RABAN 'EZLEASLN NOTIFY=Y,AON,'status',SLNSAMP,EZL531,'date()','time(),| RABAN ','res','res_type','opid();* RABAN SLNSAMP INACTV PU RABUDI------------------------------------------------------------------------------

???


43/405


Figure 25. Notification Action in NETLOG

Our NOTIFY definition specified that events for resources with a name startingwith RABU* should be sent to policy ALL_POL. This group contains the policiesfor BUDI, FRANCOIS and ARNE and their contact methods (which are all e-mail).The NETLOG documents that these e-mails were sent successfully.

1 shows the message form of the notification (since we put the MSG=YES in theNOTIFY clause).

In Figure 26 you can see the e-mail message in Lotus Notes. You see themessage text INFORM FOR NODE RABUDI STATUS=CONCTDOMAIN=RABAN. The first line of the message text is indented and this wasprobably caused by our sample interface routine.

STATMON.BROWSE ACTS NETWORK LOG FOR07/08/98 (98189) COLS 024 101HOST: HOST01 *1* *2* *3* *4* SCROLL =

-+----3----+----4----+----5----+----6----+----7----+----8----+----9---00:30:03 SLNSAMP INACTV PU RABUDI

00:30:04 *EZL531I PU RABUDI IS INACTIVE DUE TO OPERATOR TMEID5 1 00:30:04 CNM493I DSITBL01 : (NO SEQ) : DUIFECMV00:30:40 BR NETLOGA00:30:47 Send result OK00:31:12 CNM493I CNMSIHSA : (NO SEQ) : PIPE SAFE * | PPI TECROUTE00:31:12 DSI208I TIME EXPIRATION - ID= 'FKX00138' - CMD= 'FKXEACT200:31:55 CNM493I CNMSIHSA : (NO SEQ) : PIPE SAFE * | PPI TECROUTE00:31:55 DSI208I TIME EXPIRATION - ID= 'DSITDQD ' - CMD= 'CNMETDQD00:31:59 BR EZLCFG0100:32:11 CNM493I CNMSIHSA : (NO SEQ) : PIPE SAFE * | PPI TECROUTE00:32:11 DSI208I TIME EXPIRATION - ID= 'ADOIV ' - CMD= 'EZLEOIVT

**** END OF LOG ****



Figure 26. Inform E-Mail Message in Lotus Notes

The other notifications that are generated for NODE RABUDI are an alert and aTEC event. Figure 27 shows the Alert Detail window of the event. Thesenotifications are generated since we put ALERT=TEC in the notification policy.

Figure 27. Alert Notification

N E T V I E W SESSION DOMAIN: RABAN TMEID5 07/08/98 00:30:04NPDA-43S * EVENT DETAIL * PAGE

RABAN RABUDI+--------+

DOMAIN | CTRL |+--------+

DATE/TIME: RECORDED - 07/08 00:30 CREATED - 07/08/98 00:30:04

EVENT TYPE: PERMANENT

DESCRIPTION: OPERATOR INTERVENTION REQUIRED

PROBABLE CAUSES:NETWORK OPERATOR

APPLICATION PROGRAM TEXT:*EZL531I PU RABUDI IS INACTIVE DUE TO OPERATOR TMEID5 INTERVENTION

UNIQUE ALERT IDENTIFIER: PRODUCT ID - 5697B8200 ALERT ID - 00010204

ENTER A (ACTION) OR DM (DETAIL MENU)

???CMD==>


45/405


Figure 28 shows the TEC event that is generated.

Figure 28. TEC Event Notification

3.3.2 INFORM CommandThe INFORM command is a synonym for EZLECALL that invokes the inform

policy for a person. The syntax is as follows:

In Figure 29 you see an example where we used the INFORM command to notifyBUDI.



Figure 29. Issuing INFORM Command Directly

The notification policy for BUDI specifies that notification should be sent throughe-mail. As a result we get the following e-mail in Lotus Notes:

Figure 30. Inform E-Mail Message in Lotus Notes

3.3.3 INFORMTB CommandThe INFORMTB command allows you to test, load or unload the INFORM policy

member. It works similar to the AUTOTBL command. The syntax of this commandis:

The following is a sample from running the INFORMTB commands:

NCCF TME 10 NetView RABAN TMEID5 06/02/98 11:11:58* RABAN INFORM BUDI TEST INFORMATION ON INFORM COMMAND 001C RABAN Send result OKC RABAN EZL460I EMAIL ACTION WAS SUCCESSFULLY ISSUED FOR POLICY BUDI BY

OPERATOR TMEID5C RABAN Send result OK

C RABAN EZL460I EMAIL ACTION WAS SUCCESSFULLY ISSUED FOR POLICY BUDI BYOPERATOR TMEID5------------------------------------------------------------------------------

???


47/405


Figure 31. INFORMTB Command

3.3.4 ILOG CommandThe ILOG command is used to show the status of notification s. Figure 32 showsthe INFORM record list panel when you invoke either the ILOG command or AON1.9.

Figure 32. Status of Issued INFORM

There are several statuses of these entries, which are:

ISSUED: The request has been sent.

ACKNOWLEDGED: An operator has acknowledged this entry.

NCCF TME 10 NetView RABAN TMEID5 06/02/98 11:33:36* RABAN INFORMTB STATUSC RABAN EZL453I INFORM POLICY ACTIVATED AT 07:17:23 ON 06/02/98 BY AUTO1C RABAN EZL452I DSIPARM MEMBER EZLINSMP IS BEING USED FOR INFORM POLICY* RABAN INFORMTB OFFC RABAN EZL450I INFORM POLICY INACTIVE

* RABAN INFORMTB STATUSC RABAN EZL448I NO INFORM POLICY MEMBER IS LOADED* RABAN INFORMTB EZLINSM1 TESTC RABAN EZL447E A SETUP/INFORM/GROUP STATEMENT WAS EXPECTED AT LINE 46C RABAN EZL451I TEST OF INFORM POLICY MEMBER DSICMD WAS UNSUCCESSFUL* RABAN INFORMTB EZLINSMP TESTC RABAN EZL451I TEST OF INFORM POLICY MEMBER EZLINSMP WAS SUCCESSFUL* RABAN INFORMTB EZLINSMPC RABAN EZL452I DSIPARM MEMBER EZLINSMP IS BEING USED FOR INFORM POLICY* RABAN INFORMTB STATUSC RABAN EZL453I INFORM POLICY ACTIVATED AT 11:33:30 ON 06/02/98 BY TMEID5C RABAN EZL452I DSIPARM MEMBER EZLINSMP IS BEING USED FOR INFORM POLICY------------------------------------------------------------------------------

???

EZLKINFL INFORM LOG UTILITY More : +

Enter 1 -ACKNOWLEDGE 2 -REINFORM 3 -REINFORM/NEW MESSAGE 4 -DELETE

_ CONTACT ENTRY NUMBER 1 OUT OF 21 CURRENT CONTACT STATUS REINFORMED

BUDI DARMAWAN EMAIL AT 15:14:36 ON 06/01/98INFORM FOR PU RABUDI STATUS=CONCT DOMAIN=RABAN _ CONTACT ENTRY NUMBER 2 OUT OF 21 CURRENT CONTACT STATUS ACKNOWLEDGED

BUDI DARMAWAN EMAIL AT 15:14:36 ON 06/01/98INFORM FOR PU RABUDI STATUS=CONCT DOMAIN=RABAN

_ CONTACT ENTRY NUMBER 3 OUT OF 21 CURRENT CONTACT STATUS ISSUEDFRANCOIS LEPAGE EMAIL AT 15:14:36 ON 06/01/98INFORM FOR PU RABUDI STATUS=CONCT DOMAIN=RABAN

_ CONTACT ENTRY NUMBER 4 OUT OF 21 CURRENT CONTACT STATUS DELETEDFRANCOIS LEPAGE EMAIL AT 15:14:36 ON 06/01/98INFORM FOR PU RABUDI STATUS=CONCT DOMAIN=RABAN

_ CONTACT ENTRY NUMBER 5 OUT OF 21 CURRENT CONTACT STATUS ISSUEDARNE OLSSON EMAIL AT 15:14:36 ON 06/01/98INFORM FOR PU RABUDI STATUS=CONCT DOMAIN=RABAN

Command ===> _F1=Help F2=Main Menu F3=Return F5=Refresh F6=RollF7=Backward F8=Forward F9=Search F12=Cancel



DELETED: Deleted from the log database.

ROUTED: Sent to another NetView domain.

REINFORMED: Reissued to the destination.

REINFORMED/NEW: Reissued to the destination and has a new log entry.

FAILED: The send was not successful.

NOTROUTED: Could not send to the target NetView domain.

UNKNOWN ENTRY: Inform Log Corruption Error.

The functions you can perform on this panel are:

ACKNOWLEDGE: To acknowledge this entry use 1 in the command field.

DELETE: To remove entry from the log database use 4 in the command field.

REINFORM: To reissue the message to the destination use 2 in the commandfield.

REINFORM/NEW MESSAGE: To reissue the message to the destination butchange the message text use 3 in the command field.

3.4 RODM Notification ProcessingAON in TME 10 NetView for OS/390 V1R1 can change the status of an SNA andLAN RODM objects into Automation In Progress status. This shows that AON istrying to recover the object. However, when no more automation is defined forthat resource, there is no mechanism to tell the operators that they need to dosomething.

In TME 10 NetView for OS/390 V1R2, AON creates a new Network_View objectcalled Operator Intervention View if you set RODMOIV=YES as i n Figure 2 0. Thisview enables a collection for objects that has had the AIP status, and AON doesnot have another automation action defined. Those objects are linked to this viewdirectly. Figure 33 shows you the view hierarchy and the sample failed resource.


49/405


Figure 33. Operator Intervention View

An automatic timer ADOIV is invoked every 3 minutes to clean up satisfactoryresources from the Operator Intervention View. The timer is started fromEZLCFG01. The resource will typically be removed from the OperatorIntervention View when it is recovered. AON uses the ADOIV timer to performcleanup of the Operator Intervention View resources in the unlikely event that theresource was recovered and no notification was received.

Figure 34. ADOIV Setup in EZLCFG01

************************************************************************* TIMER SAMPLE FOR DOING OPERATOR INTERVENTION VIEW CLEANUP @D8A @P9C *************************************************************************TIMER ADOIV,TIME='EVERY 3',

TASK=AUTOIV1,COMMAND='EZLEOIVT'


51/405


Chapter 4. Pipe and REXX PPI Enhancements

This chapter describes the PIPE enhancements in TME 10 NetView for OS/390V1R2. Several new PIPE stages have been added and there are also several newoperands for existing PIPE stages. We only provide a few examples and werecommend you look at the NetView online help and CNMS1101 for additionalinformation and examples.

These new stages are available:

SPLIT stage

APPEND stage

NLS stage

DELDUPES stage

VARLOAD stage

INSTORE stage

These stages are enhanced: EDIT stage

EXPOSE stage

QSAM stage

STRIP stage

LOOKUP stage

TAKE/DROP stage

PPI stage

There is also a brief description of the DSIPHONE module in this chapter.DSIPHONE is a REXX external subroutine that enables you to send and receivedata across the NetView PPI.

There are three other new PIPE stages that are discussed in separate chapters:

SQL stage: See Chapter 16, DB2 Access from NetView/390 on page 3 25

TSO stage: See Chapter 18, Commands to TSO on page 34 3

UNIX stage: See Chapter 17.4, Issuing Commands to OS/390 UNIX on page338

4.1 SPLIT StageSPLIT is used to split input lines based on a certain conditions. The following isthe syntax for the SPLIT stage:



Figure 35 shows the usage of the SPLIT stage.

Figure 35. SPLIT Stage Examples

4.2 APPEND StageAPPEND is used to append the output of a PIPE to the output of a sub-pipe. Itfunctions as a reservoir, holding all the primary pipe's output until the secondarypipe finishes executing, and sends the output in succession. The following is thesyntax of the APPEND stage:

The stage separator needs to be different for stages that appear in the sub-pipethat is appended. As you can see in the following example, the stage separator isrepeated, which means that for the first APPEND stage you have || as the stageseparator, and for the next APPEND stage (inside the previous stage) you have|||| as the stage separator.

Figure 36 shows the use of APPEND to give the header and footer of a commandoutput and set the entire result underscored.

NCCF TME 10 NetView RABAN TMEID5 05/21/98 14:54* RABAN PIPE LIT /THIS IS A TEST/ | SPLIT | CONSOLE| RABAN THIS| RABAN + IS

| RABAN + A| RABAN + TEST* RABAN PIPE LIT /THIS IS ANOTHER TEST/ | SPLIT AFTER STR /T/ | CONSOLE| RABAN T| RABAN + HIS IS ANOT| RABAN + HER T| RABAN + EST* RABAN PIPE LIT /THIS IS YET ANOTHER TEST/ | SPLIT 5 BEFORE STR /S/ |

CONSOLE| RABAN T| RABAN + HIS IS YET

an introduction to tivoli netview for os-390 v1r2 sg245224

Documents