Installation: Configuring the GDPS Active/Active …...NetV iew pr ogram and the NetV iew for z/OS Enterprise Management Agent for the GDPS Active/Active Continuous A vailability solution

IBM Tivoli NetView for z/OSVersion 6 Release 2

Installation: Configuring the GDPSActive/Active Continuous AvailabilitySolution

SC14-7477-03

IBM

IBM Tivoli NetView for z/OSVersion 6 Release 2

Installation: Configuring the GDPSActive/Active Continuous AvailabilitySolution

SC14-7477-03

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 197.

This edition applies to version 6, release 2 of IBM Tivoli NetView for z/OS (product number 5697-NV6) and to allsubsequent versions, releases, and modifications until otherwise indicated in new editions.

This edition replaces SC14-7477-02.

© Copyright IBM Corporation 2011, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

About this publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixIntended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixPublications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

IBM Tivoli NetView for z/OS library . . . . . . . . . . . . . . . . . . . . . . . . . . ixRelated publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiAccessing terminology online . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiUsing NetView for z/OS online help . . . . . . . . . . . . . . . . . . . . . . . . . . xiiAccessing publications online . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiOrdering publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiService Management Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiTivoli technical training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiTivoli user groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiDownloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiSupport information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivConventions used in this publication . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Typeface conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivOperating system-dependent variables and paths. . . . . . . . . . . . . . . . . . . . . . xvSyntax diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1NetView role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Monitoring the solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Tivoli Enterprise Portal user interface . . . . . . . . . . . . . . . . . . . . . . . . . . 33270 user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2. Configuring the NetView program . . . . . . . . . . . . . . . . . . . . 7Considerations for configuring the NetView program. . . . . . . . . . . . . . . . . . . . . . 7Installing the NetView program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Updating configuration statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

CNMSTLIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9CNMSTREP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Updating Event/Automation Service class definition statements . . . . . . . . . . . . . . . . . . 19Reviewing security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Password authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Command authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3. Choosing the monitoring server environment . . . . . . . . . . . . . . 23Hot standby monitoring server running on a pair of non-z/OS servers . . . . . . . . . . . . . . . 23High availability monitoring server running in a z/OS sysplex . . . . . . . . . . . . . . . . . . 25Remote monitoring servers running in z/OS monoplexes . . . . . . . . . . . . . . . . . . . . 26

Chapter 4. Scenario: Configuring remote monitoring servers to run in z/OSmonoplexes using the PARMGEN method . . . . . . . . . . . . . . . . . . . . 29Creating and configuring an RTE to contain the remote monitoring server and NetView agent on the primarycontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Creating and configuring an RTE to contain the remote monitoring server and NetView agent on the backupcontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Loading the agent data files and configuring the portal server . . . . . . . . . . . . . . . . . . 46

Loading agent data files and configuring the portal server in a Windows environment . . . . . . . . . 46Loading agent data files and configuring the portal server in the Linux and AIX environments . . . . . . 47

© Copyright IBM Corp. 2011, 2014 iii

||

|||||||||||||||

Historical data collection and reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 50Creating a custom navigator view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5. Monitoring and controlling data . . . . . . . . . . . . . . . . . . . . 55Starting data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Lifeline Advisor monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Replication monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Displaying data collection statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Changing the sampling interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

CNMSTYLE statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56ACTVCTL command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Stopping data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Lifeline Advisor monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Replication monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Monitoring data using 3270 commands . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 6. Automating EIF events . . . . . . . . . . . . . . . . . . . . . . . . 59Understanding which events are processed . . . . . . . . . . . . . . . . . . . . . . . . . 59Adding additional automation for hardware monitor alerts . . . . . . . . . . . . . . . . . . . 60Modifying hardware monitor logging filters . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 7. Switching solution components on controller systems . . . . . . . . . . 63Moving the NetView program and IBM Tivoli Monitoring components to the backup controller . . . . . . . 63

Moving the Active/Active enterprise master NetView program . . . . . . . . . . . . . . . . . 63Controller switch when running remote monitoring servers . . . . . . . . . . . . . . . . . . 64

Manually returning components to the primary controller . . . . . . . . . . . . . . . . . . . . 64Change Master operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Commands to return components to the primary controller . . . . . . . . . . . . . . . . . . 65

Appendix A. CNMSTYLE statements . . . . . . . . . . . . . . . . . . . . . . . 67ACTACT.BKTEMS.Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67ACTACT.BKTEMS.procStr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68ACTACT.PriCont.System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68ACTACT.DB2INT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69ACTACT.DB2PATH.APPx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70ACTACT.DB2PATH.CAPx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70ACTACT.IMSINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71ACTACT.IMSPATH.APPx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72ACTACT.IMSPATH.CAPx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72ACTACT.LIFEINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73ACTACT.MASTER.DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74ACTACT.VSAMINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75ACTACT.VSAMPATH.APPx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75ACTACT.VSAMPATH.CAPx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76AUTOTASK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77EMAAUTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78ENT.ACTIVEACTIVE.ROLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79ENT.ALT.CONTROLLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80ENT.CONNCHECK.INT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81ENT.SYN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81ENT.SYSTEMS.name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82ENT.TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84function.autotask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85INIT.EMAAUTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86NACMD.ROWSxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86RMTALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89RMTINIT.IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91RMTSYN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92TOWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94XCF.RANK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

iv Installation: Configuring the GDPS Active/Active Continuous Availability Solution

||||

||||||||

>

||||||||

||||||

Appendix B. Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 101ACTVCTL (NCCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101ACTVLIFE (NCCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104ACTVREPL (NCCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107RESTYLE (NCCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Appendix C. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113AQN Prefix Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113BNH Prefix Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139DSI Prefix Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Appendix D. Scenario: Configuring remote monitoring servers to run in z/OSmonoplexes using the configuration tool . . . . . . . . . . . . . . . . . . . . 149Installing the Tivoli Management Services components . . . . . . . . . . . . . . . . . . . . 149Setting up the configuration tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Creating or updating the configuration tool work library . . . . . . . . . . . . . . . . . . . 150Starting the configuration tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Setting up your work environment . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Installing NetView agent code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Configuring the IBM Tivoli Monitoring environment on the primary and backup controller systems . . . . . 154

Creating and configuring an RTE to contain the remote monitoring server and NetView agent on the primarycontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Creating and configuring an RTE to contain the remote monitoring server and NetView agent on the backupcontroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Loading agent data files and configuring the portal server in a Windows environment . . . . . . . . . 187Loading agent data files and configuring the portal server in the Linux and AIX environments . . . . . . 188Historical data collection and reporting. . . . . . . . . . . . . . . . . . . . . . . . . 190Creating a custom navigator view . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Programming Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Privacy policy considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Contents v

|||

vi Installation: Configuring the GDPS Active/Active Continuous Availability Solution

Figures

1. NetView environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22. Primary and backup controller environments. . . . . . . . . . . . . . . . . . . . . . . 33. Hot standby monitoring server configuration . . . . . . . . . . . . . . . . . . . . . . 244. High availability monitoring server configuration . . . . . . . . . . . . . . . . . . . . . 255. Remote monitoring servers configuration . . . . . . . . . . . . . . . . . . . . . . . 266. z/OS Installation and Configuration Tools panel . . . . . . . . . . . . . . . . . . . . . 317. Parameter Generator (PARMGEN) Workflow panel . . . . . . . . . . . . . . . . . . . . 318. z/OS Installation and Configuration Tools panel . . . . . . . . . . . . . . . . . . . . . 399. Parameter Generator (PARMGEN) Workflow panel . . . . . . . . . . . . . . . . . . . . 40

10. Installation option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4811. Edit View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5012. Create New Navigator View window . . . . . . . . . . . . . . . . . . . . . . . . . 5113. Edit Navigator View window with new view name . . . . . . . . . . . . . . . . . . . . 5114. Navigator Item Properties window. . . . . . . . . . . . . . . . . . . . . . . . . . 5215. Navigator Item Properties window (assigned members) . . . . . . . . . . . . . . . . . . . 5316. Assigned member options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5317. List of available Navigator views . . . . . . . . . . . . . . . . . . . . . . . . . . 5418. Customized Navigator view for My Active/Active Sites . . . . . . . . . . . . . . . . . . 5419. Main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15120. Set up work environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15221. Specify options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15222. Set up configuration environment. . . . . . . . . . . . . . . . . . . . . . . . . . 15323. Product Selection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15524. Runtime environments panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 15525. Add runtime environment panel for FULL scenario . . . . . . . . . . . . . . . . . . . . 15626. Second runtime environment panel for FULL scenario . . . . . . . . . . . . . . . . . . . 15627. Runtime environments panel for hub monitoring server RTE . . . . . . . . . . . . . . . . 15828. Configure the TEMS for the selected RTE panel . . . . . . . . . . . . . . . . . . . . . 15829. Specify configuration values panel . . . . . . . . . . . . . . . . . . . . . . . . . 15930. Communication selection panel . . . . . . . . . . . . . . . . . . . . . . . . . . 15931. Specify configuration - hub values for remote TEMS panel . . . . . . . . . . . . . . . . . 16032. Specify advanced configuration values panel . . . . . . . . . . . . . . . . . . . . . . 16033. Specify communication protocols panel . . . . . . . . . . . . . . . . . . . . . . . . 16134. Specify IP.PIPE communication protocol panel . . . . . . . . . . . . . . . . . . . . . 16135. Configure Persistent Datastore panel . . . . . . . . . . . . . . . . . . . . . . . . . 16236. Persistent data store specifications panel . . . . . . . . . . . . . . . . . . . . . . . 16337. Configure NetView for z/OS V6.2.0 panel . . . . . . . . . . . . . . . . . . . . . . . 16438. Specify configuration parameters panel . . . . . . . . . . . . . . . . . . . . . . . . 16539. Specify agent address space parameters panel . . . . . . . . . . . . . . . . . . . . . 16640. Specify Advanced Agent Configuration Values panel . . . . . . . . . . . . . . . . . . . 16641. Communications Selection panel . . . . . . . . . . . . . . . . . . . . . . . . . . 16742. Specify Agent Secondary TEMS Values . . . . . . . . . . . . . . . . . . . . . . . . 16743. Specify Nonstandard Parameters panel . . . . . . . . . . . . . . . . . . . . . . . . 16844. Specify agent IP.PIPE configuration values panel . . . . . . . . . . . . . . . . . . . . . 16845. Specify persistent data store values panel . . . . . . . . . . . . . . . . . . . . . . . 16946. Configure persistent data store for the monitoring agent . . . . . . . . . . . . . . . . . . 17047. Persistent data store specifications panel . . . . . . . . . . . . . . . . . . . . . . . 17048. Runtime environments panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 17349. Add runtime environment panel for FULL scenario . . . . . . . . . . . . . . . . . . . . 17350. Second runtime environment panel for FULL scenario . . . . . . . . . . . . . . . . . . . 17451. Configure the TEMS for the selected RTE panel . . . . . . . . . . . . . . . . . . . . . 17552. Specify configuration values panel . . . . . . . . . . . . . . . . . . . . . . . . . 17653. Configure Persistent Datastore panel . . . . . . . . . . . . . . . . . . . . . . . . . 17754. Persistent data store specifications panel . . . . . . . . . . . . . . . . . . . . . . . 17855. Configure NetView for z/OS V6.2.0 panel . . . . . . . . . . . . . . . . . . . . . . . 179

© Copyright IBM Corp. 2011, 2014 vii

||

>||||||||||||||||||||||||||

||||||

||

||||

||

||||||||||||||||

56. Specify configuration parameters panel . . . . . . . . . . . . . . . . . . . . . . . . 18057. Specify agent address space parameters panel . . . . . . . . . . . . . . . . . . . . . 18158. Specify Advanced Agent Configuration Values panel . . . . . . . . . . . . . . . . . . . 18159. Communications Selection panel . . . . . . . . . . . . . . . . . . . . . . . . . . 18260. Specify Agent Secondary TEMS Values . . . . . . . . . . . . . . . . . . . . . . . . 18261. Specify Nonstandard Parameters panel . . . . . . . . . . . . . . . . . . . . . . . . 18362. Specify agent IP.PIPE configuration values panel . . . . . . . . . . . . . . . . . . . . . 18363. Specify persistent data store values panel . . . . . . . . . . . . . . . . . . . . . . . 18464. Configure persistent data store for the monitoring agent . . . . . . . . . . . . . . . . . . 18565. Persistent data store specifications panel . . . . . . . . . . . . . . . . . . . . . . . 18566. Installation option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18967. Edit View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19168. Create New Navigator View window . . . . . . . . . . . . . . . . . . . . . . . . 19269. Edit Navigator View window with new view name. . . . . . . . . . . . . . . . . . . . 19270. Navigator Item Properties window . . . . . . . . . . . . . . . . . . . . . . . . . 19371. Navigator Item Properties window (assigned members) . . . . . . . . . . . . . . . . . . 19472. Assigned member options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19473. List of available Navigator views . . . . . . . . . . . . . . . . . . . . . . . . . . 19574. Customized Navigator view for My Active/Active Sites . . . . . . . . . . . . . . . . . . 195

viii Installation: Configuring the GDPS Active/Active Continuous Availability Solution

||||||||||||||||||||

||||

||||

About this publication

The IBM® Tivoli® NetView® for z/OS® product provides advanced capabilities thatyou can use to maintain the highest degree of availability of your complex,multi-platform, multi-vendor networks and systems from a single point of control.This publication, the IBM Tivoli NetView for z/OS Installation: Configuring the GDPSActive/Active Continuous Availability Solution, describes how to install and use theNetView program and the NetView for z/OS Enterprise Management Agent forthe GDPS Active/Active Continuous Availability solution.

Intended audienceThis publication is for system programmers who implement the IBMImplementation Services for Geographically Dispersed Parallel Sysplex - IBMGDPS Active/Active Continuous Availability solution.

PublicationsThis section lists publications in the IBM Tivoli NetView for z/OS library andrelated documents. It also describes how to access Tivoli publications online andhow to order Tivoli publications.

IBM Tivoli NetView for z/OS libraryThe following documents are available in the IBM Tivoli NetView for z/OS library:v Administration Reference, SC27-2869, describes the NetView program definition

statements required for system administration.v Application Programmer's Guide, SC27-2870, describes the NetView

program-to-program interface (PPI) and how to use the NetView applicationprogramming interfaces (APIs).

v Automation Guide, SC27-2846, describes how to use automated operations toimprove system and network efficiency and operator productivity.

v Command Reference Volume 1 (A-N), SC27-2847, and Command Reference Volume 2(O-Z), SC27-2848, describe the NetView commands, which can be used fornetwork and system operation and in command lists and command procedures.

v Customization Guide, SC27-2849, describes how to customize the NetView productand points to sources of related information.

v Data Model Reference, SC27-2850, provides information about the GraphicMonitor Facility host subsystem (GMFHS), SNA topology manager, andMultiSystem Manager data models.

v Installation: Configuring Additional Components, GC27-2851, describes how toconfigure NetView functions beyond the base functions.

v Installation: Configuring Graphical Components, GC27-2852, describes how to installand configure the NetView graphics components.

v Installation: Configuring the GDPS Active/Active Continuous Availability Solution,SC14-7477, describes how to configure the NetView functions that are used withthe GDPS Active/Active Continuous Availability solution.

v Installation: Configuring the NetView Enterprise Management Agent, GC27-2853,describes how to install and configure the NetView for z/OS EnterpriseManagement Agent.

© Copyright IBM Corp. 2011, 2014 ix

v Installation: Getting Started, GI11-9443, describes how to install and configure thebase NetView program.

v Installation: Migration Guide, GC27-2854, describes the new functions that areprovided by the current release of the NetView product and the migration of thebase functions from a previous release.

v IP Management, SC27-2855, describes how to use the NetView product to manageIP networks.

v Messages and Codes Volume 1 (AAU-DSI), GC27-2856, and Messages and CodesVolume 2 (DUI-IHS), GC27-2857, describe the messages for the NetView product,the NetView abend codes, the sense codes that are included in NetViewmessages, and generic alert code points.

v Programming: Assembler, SC27-2858, describes how to write exit routines,command processors, and subtasks for the NetView product using assemblerlanguage.

v Programming: Pipes, SC27-2859, describes how to use the NetView pipelines tocustomize a NetView installation.

v Programming: PL/I and C, SC27-2860, describes how to write command processorsand installation exit routines for the NetView product using PL/I or C.

v Programming: REXX and the NetView Command List Language, SC27-2861, describeshow to write command lists for the NetView product using the RestructuredExtended Executor language (REXX) or the NetView command list language.

v Resource Object Data Manager and GMFHS Programmer's Guide, SC27-2862,describes the NetView Resource Object Data Manager (RODM), including howto define your non-SNA network to RODM and use RODM for networkautomation and for application programming.

v Security Reference, SC27-2863, describes how to implement authorization checkingfor the NetView environment.

v SNA Topology Manager Implementation Guide, SC27-2864, describes planning forand implementing the NetView SNA topology manager, which can be used tomanage subarea, Advanced Peer-to-Peer Networking, and TN3270 resources.

v Troubleshooting Guide, GC27-2865, provides information about documenting,diagnosing, and solving problems that occur in the NetView product.

v Tuning Guide, SC27-2874, provides tuning information to help achieve certainperformance goals for the NetView product and the network environment.

v User's Guide: Automated Operations Network, SC27-2866, describes how to use theNetView Automated Operations Network (AON) component, which providesevent-driven network automation, to improve system and network efficiency. Italso describes how to tailor and extend the automated operations capabilities ofthe AON component.

v User's Guide: NetView, SC27-2867, describes how to use the NetView product tomanage complex, multivendor networks and systems from a single point.

v User's Guide: NetView Enterprise Management Agent, SC27-2876, describes how touse the NetView Enterprise Management Agent.

v User's Guide: NetView Management Console, SC27-2868, provides informationabout the NetView management console interface of the NetView product.

v Licensed Program Specifications, GC31-8848, provides the license information forthe NetView product.

v Program Directory for IBM Tivoli NetView for z/OS US English, GI11-9444, containsinformation about the material and procedures that are associated with installingthe IBM Tivoli NetView for z/OS product.

x Installation: Configuring the GDPS Active/Active Continuous Availability Solution

v Program Directory for IBM Tivoli NetView for z/OS Japanese, GI11-9445, containsinformation about the material and procedures that are associated with installingthe IBM Tivoli NetView for z/OS product.

v Program Directory for IBM Tivoli NetView for z/OS Enterprise Management Agent,GI11-9446, contains information about the material and procedures that areassociated with installing the IBM Tivoli NetView for z/OS EnterpriseManagement Agent.

v IBM Tivoli NetView for z/OS V6R2 Online Library, LCD7-4913, contains thepublications that are in the NetView for z/OS library. The publications areavailable in PDF and HTML formats.

Related publicationsYou can find additional product information on the NetView for z/OS web site athttp://www.ibm.com/software/tivoli/products/netview-zos/.

For information about the NetView Bridge function, see Tivoli NetView for OS/390Bridge Implementation, SC31-8238-03 (available only in the V1R4 library).

Accessing terminology onlineThe IBM Terminology web site consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology web site athttp://www.ibm.com/software/globalization/terminology/.

For NetView for z/OS terms and definitions, see the IBM Terminology web site.The following terms are used in this library:

NetViewFor the following products:v Tivoli NetView for z/OS version 6 release 2v Tivoli NetView for z/OS version 6 release 1v Tivoli NetView for z/OS version 5 release 4v Tivoli NetView for z/OS version 5 release 3v Tivoli NetView for OS/390® version 1 release 4v NetView releases that are no longer supported

CNMCMDFor the CNMCMD member and the members that are included in it usingthe %INCLUDE statement

CNMSTYLEFor the CNMSTYLE member and the members that are included in it usingthe %INCLUDE statement

DSIOPFFor the DSIOPF member and the members that are included in it using the%INCLUDE statement

PARMLIBFor SYS1.PARMLIB and other data sets in the concatenation sequence

MVS™ For z/OS operating systems

MVS elementFor the base control program (BCP) element of the z/OS operating system

VTAM®

For Communications Server - SNA Services

About this publication xi

http://www.ibm.com/software/tivoli/products/netview-zos/

http://www.ibm.com/software/globalization/terminology/

IBM Tivoli Network ManagerFor either of these products:v IBM Tivoli Network Managerv IBM Tivoli OMNIbus and Network Manager

IBM Tivoli Netcool/OMNIbusFor either of these products:v IBM Tivoli Netcool/OMNIbusv IBM Tivoli OMNIbus and Network Manager

Unless otherwise indicated, topics to programs indicate the latest version andrelease of the programs. If only a version is indicated, the topic is to all releaseswithin that version.

When a topic is made about using a personal computer or workstation, anyprogrammable workstation can be used.

Using NetView for z/OS online helpThe following types of NetView for z/OS mainframe online help are available,depending on your installation and configuration:v General help and component informationv Command helpv Message helpv Sense code informationv Recommended actions

Accessing publications onlineThe documentation DVD, IBM Tivoli NetView for z/OS V6R2 Online Library containsthe publications that are in the product library. The publications are available inPDF and HTML formats. Refer to the readme file on the DVD for instructions onhow to access the documentation.

IBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Documentation Centralwebsite at https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli%20Documentation%20Central

Note: If you print PDF documents on other than letter-sized paper, set the optionin the File > Print window that enables Adobe Reader to print letter-sized pageson your local paper.

Ordering publicationsYou can order many Tivoli publications online at http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:1. Go to http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss.2. Select your country from the list and click Go.

xii Installation: Configuring the GDPS Active/Active Continuous Availability Solution

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli%20Documentation%20Central

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli%20Documentation%20Central

http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss



3. Click About this site to see an information page that includes the telephonenumber of your local representative.

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. Standard shortcutand accelerator keys are used by the product and are documented by the operatingsystem. Refer to the documentation provided by your operating system for moreinformation.

For additional information, see the Accessibility appendix in the User's Guide:NetView.

Service Management ConnectConnect, learn, and share with Service Management professionals: product supporttechnical experts who provide their perspectives and expertise.

Access Service Management Connect at http://www.ibm.com/developerworks/servicemanagement/z/. Use Service Management Connect in the following ways:v Become involved with transparent development, an ongoing, open engagement

between other users and IBM developers of Tivoli products. You can access earlydesigns, sprint demonstrations, product roadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoliand the NetView community.

v Read blogs to benefit from the expertise and experience of others.v Use wikis and forums to collaborate with the broader user community.

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM TivoliEducation website at http://www.ibm.com/software/tivoli/education.

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

Access the Tivoli Users Group at http://www.tivoli-ug.org.

DownloadsClients and agents, NetView product demonstrations, and several free NetViewapplications can be downloaded from the NetView for z/OS support web site:

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliNetViewforzOS.html

In the “Support shortcuts” pane, expand Tivoli NetView for z/OS, and click Fixes(downloads) to go to a page where you can search for or select downloads.

These applications can help with the following tasks:

About this publication xiii

http://www.ibm.com/developerworks/servicemanagement/z/

http://www.ibm.com/developerworks/servicemanagement/z/

http://www.ibm.com/software/tivoli/education

http://www.tivoli-ug.org



v Migrating customization parameters and initialization statements from earlierreleases to the CNMSTUSR member and command definitions from earlierreleases to the CNMCMDU member.

v Getting statistics for your automation table and merging the statistics with alisting of the automation table

v Displaying the status of a job entry subsystem (JES) job or canceling a specifiedJES job

v Sending alerts to the NetView program using the program-to-program interface(PPI)

v Sending and receiving MVS commands using the PPIv Sending Time Sharing Option (TSO) commands and receiving responses

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineAccess the Tivoli Software Support site at http://www.ibm.com/software/sysmgmt/products/support/index.html?ibmprd=tivman. Access the IBMSoftware Support site at http://www.ibm.com/software/support/probsub.html.

IBM Support AssistantThe IBM Support Assistant is a free local software serviceability workbenchthat helps you resolve questions and problems with IBM softwareproducts. The Support Assistant provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe Support Assistant software, go to http://www.ibm.com/software/support/isa/.

Troubleshooting informationFor more information about resolving problems with the NetView for z/OSproduct, see the IBM Tivoli NetView for z/OS Troubleshooting Guide.Additional support for the NetView for z/OS product is available throughthe NetView user group on Yahoo at http://groups.yahoo.com/group/NetView/. This support is for NetView for z/OS customers only, andregistration is required. This forum is monitored by NetView developerswho answer questions and provide guidance. When a problem with thecode is found, you are asked to open an official problem managementrecord (PMR) to obtain resolution.

Conventions used in this publicationThis section describes the conventions that are used in this publication.

Typeface conventionsThis publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip:, and Operating system considerations:)

xiv Installation: Configuring the GDPS Active/Active Continuous Availability Solution

http://www.ibm.com/software/sysmgmt/products/support/index.html?ibmprd=tivman

http://www.ibm.com/software/sysmgmt/products/support/index.html?ibmprd=tivman

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa/

http://www.ibm.com/software/support/isa/

http://groups.yahoo.com/group/NetView/

http://groups.yahoo.com/group/NetView/

v Keywords and parameters in text

Italic

v Citations (examples: titles of publications, diskettes, and CDsv Words defined in text (example: a nonswitched line is called a

point-to-point line)v Emphasis of words and letters (words as words example: “Use the word

that to introduce a restrictive clause.”; letters as letters example: “TheLUN address must start with the letter L.”)

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data.

v Variables and values you must provide: ... where myname represents...

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Operating system-dependent variables and pathsFor workstation components, this publication uses the UNIX convention forspecifying environment variables and for directory notation.

When using the Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash (\) indirectory paths. The names of environment variables are not always the same inthe Windows and UNIX environments. For example, %TEMP% in Windowsenvironments is equivalent to $TMPDIR in UNIX environments.

Note: If you are using the bash shell on a Windows system, you can use the UNIXconventions.

Syntax diagramsThe following syntax elements are shown in syntax diagrams. Read syntaxdiagrams from left-to-right, top-to-bottom, following the horizontal line (the mainpath).v “Symbols”v “Parameters” on page xviv “Punctuation and parentheses” on page xviv “Abbreviations” on page xvii

For examples of syntax, see “Syntax examples” on page xvii.

SymbolsThe following symbols are used in syntax diagrams:

►► Marks the beginning of the command syntax.

► Indicates that the command syntax is continued.

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

►◄ Marks the end of the command syntax.

About this publication xv

ParametersThe following types of parameters are used in syntax diagrams:

RequiredRequired parameters are shown on the main path.

OptionalOptional parameters are shown below the main path.

DefaultDefault parameters are shown above the main path. In parameterdescriptions, default parameters are underlined.

Syntax diagrams do not rely on highlighting, brackets, or braces. In syntaxdiagrams, the position of the elements relative to the main syntax line indicateswhether an element is required, optional, or the default value.

When you issue a command, spaces are required between the parameters unless adifferent separator, such as a comma, is specified in the syntax.

Parameters are classified as keywords or variables. Keywords are shown inuppercase letters. Variables, which represent names or values that you supply, areshown in lowercase letters and are either italicized or, in NetView help, displayedin a differentiating color.

In the following example, the USER command is a keyword, the user_id parameteris a required variable, and the password parameter is an optional variable.

►► USER user_idpassword

►◄

Punctuation and parenthesesYou must include all punctuation that is shown in the syntax diagram, such ascolons, semicolons, commas, minus signs, and both single and double quotationmarks.

When an operand can have more than one value, the values are typically enclosedin parentheses and separated by commas. For a single value, the parenthesestypically can be omitted. For more information, see “Multiple operands or values”on page xviii.

If a command requires positional commas to separate keywords and variables, thecommas are shown before the keywords or variables.

When examples of commands are shown, commas are also used to indicate theabsence of a positional operand. For example, the second comma indicates that anoptional operand is not being used:COMMAND_NAME opt_variable_1,,opt_variable_3

You do not need to specify the trailing positional commas. Trailing positional andnon-positional commas either are ignored or cause a command to be rejected.Restrictions for each command state whether trailing commas cause the commandto be rejected.

xvi Installation: Configuring the GDPS Active/Active Continuous Availability Solution

AbbreviationsCommand and keyword abbreviations are listed in synonym tables after eachcommand description.

Syntax examplesThe following examples show the different uses of syntax elements:v “Required syntax elements”v “Optional syntax elements”v “Default keywords and values”v “Multiple operands or values” on page xviiiv “Syntax that is longer than one line” on page xviiiv “Syntax fragments” on page xviii

Required syntax elements:Required keywords and variables are shown on the main syntax line. You mustcode required keywords and variables.

►► REQUIRED_KEYWORD required_variable ►◄

A required choice (two or more items) is shown in a vertical stack on the mainpath. The items are shown in alphanumeric order.

►► REQUIRED_OPERAND_OR_VALUE_1REQUIRED_OPERAND_OR_VALUE_2

►◄

Optional syntax elements:Optional keywords and variables are shown below the main syntax line. You canchoose not to code optional keywords and variables.

►►OPTIONAL_OPERAND

►◄

A required choice (two or more items) is shown in a vertical stack below the mainpath. The items are shown in alphanumeric order.

►►OPTIONAL_OPERAND_OR_VALUE_1OPTIONAL_OPERAND_OR_VALUE_2

►◄

Default keywords and values:Default keywords and values are shown above the main syntax line in one of thefollowing ways:v A default keyword is shown only above the main syntax line. You can specify

this keyword or allow it to default. The following syntax example shows thedefault keyword KEYWORD1 above the main syntax line and the rest of theoptional keywords below the main syntax line.

v If an operand has a default value, the operand is shown both above and belowthe main syntax line. A value below the main syntax line indicates that if youspecify the operand, you must also specify either the default value or anothervalue shown. If you do not specify the operand, the default value above themain syntax line is used. The following syntax example shows the default valuesfor operand OPTION=* above and below the main syntax line.

About this publication xvii

►► COMMAND_NAMEKEYWORD1

KEYWORD1KEYWORD2KEYWORD3

OPTION=*

OPTION= *VALUE1VALUE2

►◄

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

►►

▼

,

REPEATABLE_OPERAND_OR_VALUE_1REPEATABLE_OPERAND_OR_VALUE_2REPEATABLE_OPERAND_OR_VALUE_3

▼

,

KEYWORD= ( value_n ) ►◄

Syntax that is longer than one line:If a diagram is longer than one line, each line that is to be continued ends with asingle arrowhead and the following line begins with a single arrowhead.

►► OPERAND1 OPERAND2 OPERAND3 OPERAND4 OPERAND5 OPERAND6 OPERAND7 ►

► OPERAND8 ►◄

Syntax fragments:Some syntax diagrams contain syntax fragments, which are used for lengthy,complex, or repeated sections of syntax. Syntax fragments follow the maindiagram. Each syntax fragment name is mixed case and is shown in the maindiagram and in the heading of the fragment. The following syntax example showsa syntax diagram with two fragments that are identified as Fragment1 andFragment2.

►► COMMAND_NAME Fragment1Fragment2

►◄

Fragment1

KEYWORD_A=valueA KEYWORD_B KEYWORD_C

Fragment2

KEYWORD_D KEYWORD_E=valueE KEYWORD_F

xviii Installation: Configuring the GDPS Active/Active Continuous Availability Solution

Chapter 1. Overview

The GDPS Active/Active Continuous Availability solution minimizes recovery timeand data loss when systems or sites go down, whether planned or unplanned. Thesolution is designed for environments where two or more sites, separated byunlimited distances, run the same applications and have the same data. Thesolution provides cross-site workload balancing and near-continuous availabilityand disaster recovery. The NetView program provides monitoring and automationservices for the solution. The NetView program is used with the Active/Standbyand Active/Query configurations. With the Active/Query configuration, you canuse the capacity in the secondary site, thus taking advantage of an additionalworkload balancing capability.

NetView roleThe NetView product is used with the GDPS Active/Active ContinuousAvailability solution. The NetView product provides the following functions:v Sampled and real-time monitoring capability using the Tivoli Enterprise Portal

(portal) and the 3270 command interface for the following products:– IBM Multi-site Workload Lifeline V2.0 (Lifeline Advisor)– IBM InfoSphere® Data Replication for DB2® for z/OS V10.2.1 (Q replication or

DB2 replication)– IBM InfoSphere Data Replication for IMS™ for z/OS V11.1– IBM InfoSphere Data Replication for VSAM for z/OS V11.1

v Failover capability for the Active/Active enterprise masterv Automation in response to designated conditions

Figure 1 on page 2 shows how the NetView product works with the GDPSActive/Active Continuous Availability solution.

© Copyright IBM Corp. 2011, 2014 1

||||||||||

|

||

|

|

|

The NetView program resides on the controller systems, and on the productionsystems in the sites where replication servers run. The controller provides a pointof control for the systems and workloads participating in the GDPS® Active/Activeenvironment for both planned actions and recovery actions. Planned actionsinclude IPL as well as directing a workload to an active sysplex. Recovery actionsinclude reacting to unplanned outages. For redundancy, the GDPS Active/ActiveContinuous Availability solution includes a primary and backup controller.

The primary controller is a system on which the Active/Active enterprise masterNetView program runs. The Active/Active enterprise master NetView program isan extension to the existing enterprise master NetView program capability.

The Active/Active enterprise master NetView program is the control point forsampled and real-time monitoring for the solution. Sampled monitoring uses theTivoli Enterprise Portal (portal) and real-time monitoring uses 3270 commands.The Active/Active enterprise master NetView program runs where the primaryLifeline Advisor component of the Multi-site Workload Lifeline product runs.Replication data from the production systems is forwarded to this NetViewprogram for consolidation.

For failure scenarios, the NetView program also runs on the backup controller. ThisNetView program is configured almost identical to the Active/Active enterprisemaster NetView program so that it can take over the Active/Active enterprisemaster NetView functions.

Replication

Netview Agent andIBM Tivoli Monitoring

EIF Flow

Data Collection

RMTCMD connections

Distributed Components

z/OS or Distributed

Component

PortalServer

Application/database tier

Primary Controller

Primary Advisor

NetView/SA/GDPS

sys_bNetView/SA

IMS Capture

QREP CaptureNetView/SA

sys_a

TivoliEnterprise

Portal

Sysplex 2

Site 2

Backup Controller

Secondary Advisor

NetView/SA/GDPS

NetView Agent

Application/database tier

sys_d

NetView/SA

IMS Apply

QREP Apply

NetView/SA

sys_c

Site 1

Sysplex 1

Hub

Monitoring

Server

VSAM Apply

E/AS

NetView PPI

VSAM Capture

E/AS

NetView PPI

Remote Monitoring

Server

NetView Agent

Remote Monitoring

Server

Figure 1. NetView environment

2 Installation: Configuring the GDPS Active/Active Continuous Availability Solution

The Active/Active enterprise master NetView program uses the RMTCMDcommand to communicate with other NetView programs in the environment. Allcommunications are initiated from the Active/Active enterprise master NetViewprogram for security reasons.

Monitoring the solutionYou can display sampled monitoring information using the portal and the TivoliNetView for z/OS Enterprise Management Agent (NetView agent), or you candisplay real-time monitoring information using the NetView 3270 interface. Theseare done from the controller where the Active/Active enterprise master NetViewprogram runs.

Tivoli Enterprise Portal user interfaceWhen you use the portal to display monitoring information, the NetView agent isconfigured on both the primary and backup controllers. The NetView agent runson the primary controller, and might be running on the backup controller tomonitor the NetView program on that system. If the NetView agent is not runningon the backup controller, it will be started there during primary controller failurescenarios.

The monitoring server to which the agent connects runs on either the controllersystem or another system. See Chapter 3, “Choosing the monitoring serverenvironment,” on page 23 for information about monitoring server environments.

Figure 2 shows an overview of the primary and backup controller environmentswith respect to the monitoring server and agent configuration.

To configure the primary and secondary remote monitoring server environment,follow the configuration steps in Chapter 4, “Scenario: Configuring remotemonitoring servers to run in z/OS monoplexes using the PARMGEN method,” onpage 29. By using remote primary and secondary monitoring servers, operationsare simpler when a failure occurs because the remote monitoring servers are activeon both controllers as part of normal operations. When there is an enterprisemaster NetView program switch to the backup controller, it is only necessary tostart the agent on the backup controller, if it is not already active. For moreinformation about starting the agent on the backup controller, see Chapter 7,“Switching solution components on controller systems,” on page 63.

Lifeline Advisor - primary role

Active/Active enterprisemaster NetView

Remote Tivoli Enterprise MonitoringServer

NetView agent

Lifeline Advisor -secondary role

NetView

Remote Tivoli Enterprise MonitoringServer

NetView agent

Primary controller Backup controller

Figure 2. Primary and backup controller environments

Chapter 1. Overview 3

|

|||

||

|||

You can monitor the following components:v Lifeline Advisorv Q replicationv IMS replicationv VSAM replication

You can monitor the following data:v Load Balancersv Load Balancer Groupsv Load Balancer Workloadsv Replication Detailsv Replication Serversv Replication Workloads summaryv Workloads

– Active/Query Workloadsv Workload Lifeline Advisorsv Workload Lifeline Agentsv Workload Serversv Workload Sitesv Workload Site Details

The NetView agent also provides situations and expert advice for the data beingmonitored. For more information about monitoring this data, see the IBM TivoliNetView for z/OS User's Guide: NetView Enterprise Management Agent.

3270 user interfaceYou can use the ACTVLIFE and ACTVREPL commands to display similarinformation to that which is displayed on the portal. These commands must beissued from the Active/Active enterprise master NetView program. The keywordsfor these commands correspond to the various portal workspaces. The datadisplayed by these commands is in a format that provides the user with aprogrammable interface. The 3270 commands do not provide event notification forthe data being monitored.

AutomationYou can use the NetView automation table to define a set of actions to occur inresponse to predefined conditions. The GDPS Active/Active ContinuousAvailability solution provides sample automation statements in the AQNSACTAmember.

The AQNSACTA automation sample performs the following tasks:v Starts Lifeline Advisor and replication data collection at NetView initializationv Handles Lifeline Advisor data collection based on messages received from the

Multi-site Workload Lifeline productv Provides Lifeline Advisor information on changes in latency state for

Active/Query workloadsv Provides GDPS information on some changes in latency state for both

Active/Standby and Active/Query workloadsv Handles replication data collection based on the dynamic start and stop of

replication serversv Handles changes for replication socket path name implemented using the

RESTYLE command


|

|

|

||

||

v Instantiates replication configuration information about the Active/Activeenterprise master NetView program for use by the ACTVREPL command

In addition to the automation included by the AQNSACTA sample member, theGDPS Active/Active Continuous Availability solution uses automation providedby base NetView functions. To make sure that you include all the necessaryautomation that is used with the GDPS Active/Active Continuous Availabilitysolution, configure the AUTOCMD statement in the CNMSTYLE member to loadthe DSITBL01 automation sample member.

Replication components of the GDPS Active/Active Continuous Availabilitysolution use the EIF facility to send events to an event receiver. You can use theNetView Event/Automation Service (E/AS) to convert these events into NMVTformatted alerts. The converted alerts are forwarded to the NetView hardwaremonitor where they are filtered and routed to the NetView automation table. TheNetView program validates the information in the alert, and if the informationpasses validation, it is forwarded to the Lifeline Advisor and GDPS components.

Chapter 1. Overview 5

|||||||


Chapter 2. Configuring the NetView program

To configure the NetView program to work with the GDPS Active/ActiveContinuous Availability solution, follow these procedures:v “Installing the NetView program”v “Updating configuration statements” on page 8v “Reviewing security” on page 19

The way you configure the NetView program for the solution depends on thesystem on which the NetView program is running. If the NetView program runson the primary or backup controller, then configure the NetView program forLifeline Advisor monitoring. If the NetView program runs on a production system,a system in the sysplex where replication runs, then configure the NetViewprogram for replication monitoring.

Note: Lifeline and Replication monitoring cannot run on the same NetViewprogram.

Considerations for configuring the NetView programThe NetView programs for the GDPS Active/Active Continuous Availabilitysolution are full-function programs that run with System Automation for z/OS andGDPS. During planning for the GDPS Active/Active Continuous Availabilitysolution, consider the following NetView configurations:v A single NetView installation that combines network and automationv In an environment with multiple NetView programs, enable the Active/Active

NetView function in an automation NetView program. The Active/Activefunction includes, but is not limited to XCF, RMTCMD communications, andmonitoring using the NetView agent.

Installing the NetView programTo install the NetView program, follow these steps:1. Perform the SMP/E installation of the NetView product as described in the

NetView program directory.2. Configure the NetView program by following the procedures listed in IBM

Tivoli NetView for z/OS Installation: Getting Started.3. Configure the Event/Automation Service by following the procedures listed in

IBM Tivoli NetView for z/OS Installation: Configuring Additional Components.

Table 1 on page 8 lists NetView samples that are used for the GDPS Active/ActiveContinuous Availability solution.

Usage note: The NetView solution samples do not contain all of the definitionsthat are required for the solution. Base NetView function definitions are alsorequired.


||||

|

||||

||

|||

Table 1. List of solution samples

Distributed as Name Description Data set name

AQNCAT same This sample provides NetView CommandAuthorization Table statements for theGDPS Active/Active ContinuousAvailability solution.

SAQNPARM

AQNCMD same This sample provides NetView CMDDEFstatements for the GDPS Active/ActiveContinuous Availability solution.

SAQNPARM

AQNOPF same This sample provides NetView operatordefinitions and passwords for the GDPSActive/Active Continuous Availabilitysolution.

SAQNPARM

AQNSACTA same This sample provides NetView automationstatements for the GDPS Active/ActiveContinuous Availability solution.

SAQNPARM

AQNSAF same This sample provides RACF® definitions forNetView operators and commands that areused with the GDPS Active/ActiveContinuous Availability solution.

SAQNSAMP

CNMSTACT same This sample is used with the GDPSActive/Active Continuous Availabilitysolution. It includes CNMSTYLEconfiguration statements based on theACTIVEACTIVE subtower that you specifyin the CNMSTYLE member.

SAQNPARM

CNMSTLIF same This sample is used for the GDPSActive/Active Continuous Availabilitysolution. It defines statements that arerequired for a NetView program running onthe primary or backup controller.

SAQNPARM

CNMSTREP same This sample is used for the GDPSActive/Active Continuous Availabilitysolution. It defines CNMSTYLE statementsthat are required for a NetView programrunning on a z/OS image in the sysplexwhere replication servers are running.

SAQNPARM

Updating configuration statementsThe CNMSTYLE member is used during NetView initialization. To change astatement in the CNMSTYLE member or its included members, copy the statementto either the CNMSTUSR or CxxSTGEN member. You can then modify thestatement. For information about changing CNMSTYLE statements, see IBM TivoliNetView for z/OS Installation: Getting Started. For information about CNMSTYLEstatements, see Appendix A, “CNMSTYLE statements,” on page 67.

Table 2. Updating configuration statements

Configuration statement Controller systems Production systems

Update TOWER statement to includeACTIVEACTIVE tower

Yes Yes

Update TOWER statement to includeTEMA tower

Yes No


Table 2. Updating configuration statements (continued)

Configuration statement Controller systems Production systems

Update TOWER.TEMA to includeACTIVEACTIVE subtower

Yes No

Update TOWER.ACTIVEACTIVE statementto include LIFELINE subtower

Yes No

Update TOWER.ACTIVEACTIVE statementto include REPLICATION subtower

No Yes

Update appropriate REPLICATIONsubtower depending on the type ofreplication that you are doing

No Yes

Include DSITBL01 for automation onAUTOCMD statements

Yes Yes

Usage Notes:

1. Uncomment only one of the LIFELINE or REPLICATION subtowers.Unpredictable results can occur if both are uncommented.

2. For the solution, the NetView agent is only required on the controllers.3. Update the TEMA tower or subtower configuration after you configure and

start the NetView agent. Otherwise, error messages are sent to the NetView log.4. The CNMSTACT include member includes the CNMSTLIF or CNMSTREP

members. Update statements from these members as required for yourinstallation.

5. NetView automation for the solution includes cross-domain messages from theproduction systems to the controllers.

6. When a NetView program that is not running the GDPS Active/ActiveContinuous Availability solution connects to a NetView agent that is being usedby the solution, make sure that you leave the ACTIVEACTIVE tower and theTEMA.ACTIVEACTIVE subtower statements commented out on thenon-Active/Active NetView program. Enabling these tower and subtowerstatements on the non-Active/Active NetView program can cause the NetViewagent to try to collect Active/Active data from the wrong NetView program.

CNMSTLIFReview and customize the statements in the CNMSTLIF member. The statementsin CNMSTLIF provide the following functions:v “Collecting data” on page 10v “Granting access to data” on page 11v “Processing alerts” on page 11v “Setting up RMTCMD communication” on page 12v “Configuring the Active/Active enterprise master NetView program” on page 12v “Starting the monitoring server and the NetView agent on the primary

controller” on page 15v “Starting the monitoring server and the NetView agent on the backup

controller” on page 16

Copy the CNMSTLIF statements that require modification, or must be appendedafter other existing CNMSTYLE member statements, to either CNMSTUSR orCxxSTGEN member and modify them there. Many of the statements in theCNMSTLIF member are existing CNMSTYLE statements. If you already

Chapter 2. Configuring the NetView program 9

||

|||||||

customized any of these statements, make sure that the statements for theActive/Active configuration are not overridden. If you add statements to theCxxSTGEN member, make sure that they are after the CNMSTACT includemember. To enable the statements that you change, run the appropriate RESTYLEcommand.

Collecting dataThe statements in Table 3 are used to define the autotask, sampling interval, andsize of the NetView agent workspaces for monitoring of the Lifeline Advisorcomponent.

Table 3. CNMSTYLE statements for Lifeline Advisor monitoring

Statement Purpose

function.autotask.ACTTSK1 Specifies the autotask (ACTTSK1) on which datacollection runs.

AUTOTASK.?ACTTSK1.Console Specifies the MVS console that is associated withthe autotask (ACTTSK1).

ACTACT.LIFEINT Specifies how often data is collected from theLifeline Advisor.

function.autoask.ACTDATA Specifies the autotask that formats LifelineAdvisor data for the Tivoli Enterprise Portal.

AUTOTASK.?ACTDATA.Console Specifies the MVS console that is associated withthe autotask (ACTDATA).

NACMD.ROWSADVISORS Specifies the number of rows of data to collectfor the Workload Lifeline Advisors workspace.

NACMD.ROWSAGENTS Specifies the number of rows of data to collectfor the Workload Lifeline Agents workspace.

NACMD.ROWSLOADBALS Specifies the number of rows of data to collectfor the Load Balancers workspace.

NACMD.ROWSLOADGRPS Specifies the number of rows of data to collectfor the Load Balancer Groups workspace and theLoad Balancer Workloads workspace.

NACMD.ROWSSITES Specifies the number of rows of data to collectfor the Workload Sites workspace.

NACMD.ROWSWORKLOADS Specifies the number of rows of data to collectfor the Workloads workspace and theActive/Query Workloads workspace.

NACMD.ROWSWORKSRVRS Specifies the number of rows of data to collectfor the Workload Servers workspace.

The statements in Table 4 specify the size of the NetView agent workspaces for thereplication component.

Table 4. CNMSTYLE statements that specify the size of the NetView agent workspaces forreplication monitoring

Statement Purpose

NACMD.ROWSDB2APPSRVNACMD.ROWSDB2APPWKLNACMD.ROWSDB2CAPSRVNACMD.ROWSDB2CAPWKL

Specifies the number of rows of data to collectfor the DB2 Replication Details workspace andthe DB2 Replication Details for Workloadworkspace.

NACMD.ROWSIMSAPPDETNACMD.ROWSIMSCAPDET

Specifies the number of rows of data to collectfor the IMS Replication Details workspace.


||||

||

||

|||

|||

|||

|||

|||

|||

|||

|||

||||

|||

||||

||||

||

|||

||

||||

||||

||||

Table 4. CNMSTYLE statements that specify the size of the NetView agent workspaces forreplication monitoring (continued)

Statement Purpose

NACMD.ROWSVSAMAPPDETNACMD.ROWSVSAMCAPDET

Specifies the number of rows of data to collectfor the VSAM Replication Details workspace.

NACMD.ROWSREPSRVRS Specifies the number of rows of data to collectfor the Replication Servers workspace.

NACMD.ROWSREPWKLS Specifies the number of rows of data to collectfor the Replication Workloads Summaryworkspace.

For more information about controlling the size of NetView agent workspaces, seeIBM Tivoli NetView for z/OS Installation: Configuring the NetView EnterpriseManagement Agent.

Granting access to dataThe NetView program must be authorized to access Lifeline Advisor data in theGDPS Active/Active Continuous Availability solution. To allow access, grant oneof the following permissions to the SAF user ID under which the NetViewprogram runs:v Grant z/OS UNIX superuser authority to the user ID assigned to the NetView

job or started procedure. You can grant superuser authority by setting the z/OSUNIX user ID (UID) attribute to zero for the user ID.

v Grant the user ID access to the AQS.NETMGMT.DISPLAY SAF profile in theSERVAUTH class.

For more information, see the Multi-site Workload Lifeline library.

Processing alertsHardware monitor alerts are generated from Event Integration Facility (EIF) eventsthat are sent by replication products.

The following events are forwarded to the Lifeline Advisor for Active/Queryworkloads:v AA_replication_max_average_latency_exceededv AA_replication_reset_average_latency_metv AA_replication_critical_average_latency_exceededv AA_replication_constrained_average_latency_exceededv AA_replication_heartbeatv AA_replication_workload_down

The following events are forwarded to GDPS for Active/Standby andActive/Query workloads:v AA_replication_max_average_latency_exceededv AA_replication_reset_average_latency_metv AA_replication_heartbeatv AA_replication_workload_upv AA_replication_workload_down

The statements in Table 5 on page 12 define the autotask that processes thehardware monitor (NPDA) alerts.


||

||

||||

|||

||||||||

|||

||||||||

|||||||

||

Table 5. CNMSTYLE statements that define the autotask that processes NPDA alerts

Statement Purpose

function.autotask.ACTTSKEV Specifies the autotask that processes hardwaremonitor alerts that are generated by replicationEIF events.

AUTOTASK.?ACTTSKEV.Console Specifies MVS console that is associated with theautotask (AUTOAEVT).

Setting up RMTCMD communicationFor the GDPS Active/Active Continuous Availability solution, use IP for RMTCMDcommunication between NetView programs:RMTINIT.IP = Yes

Configuring the Active/Active enterprise master NetView programConfigure the NetView program that is running on the primary controller to be theenterprise master NetView program for Active/Active data. To configure theActive/Active enterprise master NetView program, follow these steps:v Define the type of the enterprise master NetView program.v Define the role of the NetView program as primary.v Define the XCF rank of the NetView program as master.v Define production system information so that replication server data can be

monitored.v Optional: Define primary and second IP addresses for systems that are specified

on ENT.SYSTEMS statements.v Optional: Define a delta interval in addition to the data collection sample

interval that is used to determine whether replication data sent to the controllersystem is current.

Defining the type of enterprise master NetView program: The Active/Activeenterprise master NetView program can also act as the enterprise master fordiscovery manager. The ENT.TYPE statement in the CNMSTYLE member specifiesthe type of enterprise master program. The initial setting is ACTIVEACTIVE. Thisstatement must be coded the same on both the primary and backup controllers.

You can have a separate enterprise master NetView program for discoverymanager on non-controller systems. For this configuration, you do not have toconfigure the ENT.TYPE statement.

Defining the Active/Active enterprise master NetView role: The Active/Activeenterprise master NetView role specifies whether the NetView program initializesas the Active/Active enterprise master. On the primary controller, specifyPRIMARY for the ENT.ACTIVEACTIVE.ROLE statement in the CNMSTYLEmember. On the backup controller, specify BACKUP for theENT.ACTIVEACTIVE.ROLE statement. If the primary controller fails over to thebackup controller, these values are programmatically updated to reflect this changein roles.

Defining the Active/Active XCF rank for the enterprise master NetViewprogram: The XCF.RANK statement determines the rank of the NetView programwithin the sysplex, or a NetView program running as a MONOPLEX orXCFLOCAL system. Specify a value of 250 for the XCF rank for the enterprisemaster NetView program to enable it to immediately assume the enterprise masterrole and contact systems in the production sites.


||

||

||||

||||

|

|

||

|||

|||

||||||

Defining production system information: The Active/Active enterprise masterNetView program communicates with z/OS images that collect replicationinformation using RMTCMD communications over IP communications. Data isforwarded from the remote system to the controller system for consolidation anddisplay for the following NetView user interfaces:v portalv 3270 console

Use the ENT.SYSTEMS.name, RMTSYN, and RMTALIAS statements in theCNMSTYLE member to define at least one production system in each sysplex. TheENT.SYSTEMS.name statement specifies an entry point and backup entry pointsinto a sysplex or stand-alone system. Specify only one ENT.SYSTEMS.namestatement for each sysplex.

See detailed information in Table 6 to configure the Active/Active enterprisemaster NetView program.

Table 6. CNMSTYLE statements that specify configuration values for an Active/Activeenterprise NetView program

Statement Purpose

ACTACT.MASTER.DELAY Defines a delta interval in addition to the datacollection sample interval that is used todetermine whether replication data sent to thecontroller system is current.

When the modified sampling interval elapses onthe controller system without the controllersystem receiving updated replication data, thecontroller system considers the data from theproduction system to not be current. Data that isnot current causes workload aggregate data tobe flagged as inaccurate. The value is used tocompensate for network response time andinternal NetView program processing.

ENT.ACTIVEACTIVE.ROLE This statement is required on controller systemsand specifies whether the enterprise NetViewprogram processes enterprise statements duringinitialization. If the value is PRIMARY, theenterprise statements are processed. If the valueis BACKUP, the statements are not processed.Usage notes:

1. This statement is ignored by RESTYLE ENTprocessing to avoid conflicts withautomation.

2. If the Active/Active enterprise masterNetView program also acts as the discoverymanager enterprise master, the discoverymanager enterprise master moves with theActive/Active enterprise master from onecontroller to the other.

ENT.ALT.CONTROLLER Defines the NetView domain name for theprimary or backup controller . If you are on theprimary controller, this is the NetView domainname for the backup controller. If you are on thebackup controller, this is the NetView domainname for the primary controller.


|||

|||

|||||

|||||||||

||||||||

|||

||||||

|||||||

Table 6. CNMSTYLE statements that specify configuration values for an Active/Activeenterprise NetView program (continued)

Statement Purpose

ENT.CONNCHECK Specifies the interval between connectivitychecks to managed production systems for asysplex master or enterprise master NetViewprogram.

ENT.SYN.role.site.domain Specifies a primary and secondary IP address fora NetView domain that has a RMTALIAS namedefined on an ENT.SYSTEMS statement. Use thisstatement for a NetView program that has an IPaddress that changes as a result of a planned orunplanned outage.

ENT.SYSTEMS.name Specify entry points into sysplex systems orstand-alone systems that can be managed.Usage note: If ENT.SYSTEMS specifies an entrypoint and backup entry points into a sysplexwith a mixture of NetView V6R2 and earliersystems, use the NetView V6R2 systems as theentry points on the ENT.SYSTEMS statements.NetView V6R2 and higher entry points containfunction that is required to support theActiveActive enterprise masters.

ENT.TYPE This statement is required on controller systemsand specifies the type of enterprise masterNetView program:

ACTIVEACTIVEActive/Active enterprise master

ACTIVEACTIVE DISCOVERYActive/Active enterprise master thatincludes resources that were discoveredwhen the DISCOVERY function wasstarted. These resources include sysplex,TCP/IP stack, IP interface, Telnet serverand port, OSA, and HiperSockets™ data.

Usage note: You can also specify the ENT.TYPE =DISCOVERY statement on non-controller systemsto forward discovery manager data to anon-controller system. You must includeACTIVEACTIVE on the ENT.TYPE statement to startreplication data forwarding.

function.autotask.ACTDATA Specifies the distributed autotask that forwardsActive/Active data from production systems tocontroller systems.

RMTALIAS.alias Specify an IP alias for a given remote domain.

RMTSYN.netid.domain Specify the IP address or host name, portnumber, and domain with which theActive/Active enterprise master NetViewprogram communicates to its managed NetViewprograms. To enable the change, use theRESTYLE RMTSYN command.

XCF.RANK Specify the group rank of master for NetViewprograms running on the primary and backupcontrollers. Set this value to 250.


||

||

|||||

|||||||

|||||||||||

||||

||

|||||||||||||

||||

For more information about configuring an enterprise master NetView program,see IBM Tivoli NetView for z/OS IP Management.

Optional: Defining primary and secondary IP address for ENT.SYSTEMStargets: If the IP address of a NetView program that is used as the target on anENT.SYSTEMS statement might change (for example, as part of a recoveryscenario), use ENT.SYN statements with RMTSYN values that specify these IPaddresses. You can then use the RMTALIAS specification on the ENT.SYSTEMSstatement to refer to these RMTSYN aliases. You can use ACTVCTL CONNECTcommand to control the IP address to which the RMTALIAS resolves.

The ENT.SYN statement specifies the following values:v Indicator for PRI or SECv Site namev NetView domain namev RMTALIAS name that is specified on the ENT.SYSTEMS statementv Value that is required for the RMTSYN statement that the NetView program

generates

For example, the following ENT.SYN statement defines a primary IP address forthe CNM01 domain and CNM01AL for the RMTALIAS name:ENT.SYN.PRI.PLEX1.CNM01 = CNM01AL,CNM01.SAMPLE.COM IPV4 ON USIBMNT

When you specify the ENT.SYN statement, do not specify the RMTSYN andRMTALIAS statements. The NetView program defines a CNM01AL RMTALIASstatement and an RMTSYN statement.

Optional: Defining a delay interval: Replication data is collected and forwardedto controller NetView programs based on a sampling interval that is defined on theproduction systems. If the data at the production system from a replication serveris older than its sampling interval plus a delay factor, the NetView programconsiders the data to not be current. The delay factor is intended to account fornetwork and internal NetView processing. The NetView program then marks thedata aggregation status as UNSATISFACTORY on the Replication Workloadsworkspace in the Tivoli Enterprise Portal.

The sampling interval is determined by the controller. The default delay value is 3seconds. You can use the ACTACT.MASTER.DELAY statement on the controllersystems to increase the delay interval up to 60 seconds.

Starting the monitoring server and the NetView agent on theprimary controllerYou can use the NetView program on the primary controller to start themonitoring server and NetView agent during initialization. To set up thisautomation, use the statements in Table 7 on page 16.

Note: See Chapter 3, “Choosing the monitoring server environment,” on page 23before completing this configuration step. The monitoring server part of thisconfiguration is not applicable if the monitoring server is not running on thecontroller systems.


|

|||||||

|

|

|

|

|

||

||

|

|||

||||||||

|||

Table 7. CNMSTYLE statements to start the monitoring server and NetView agent duringNetView initialization

Statement Purpose

INIT.EMAAUTO Set this statement to Yes. Specifies to process theEMAAUTO.TEMS.procStr statement and theEMAAUTO.TEMA.procStr statement.

EMAAUTO Specifies whether the monitoring server(EMAAUTO.TEMS.procStr) or the NetView agent(EMAAUTO.TEMA.procStr) is to be started duringNetView initialization. The TEMA tower must beenabled.

function.autotask.EMAAUTOM Specifies the EMAAUTOM autotask on whichthe automation runs

AUTOTASK.?EMAAUTOM.Console Specifies MVS console that is associated with theEMAAUTOM autotask

Starting the monitoring server and the NetView agent on thebackup controllerYou can use the NetView program on the backup controller to start the monitoringserver and NetView agent. To set up this automation, use the statements in Table 8.

Note: See Chapter 3, “Choosing the monitoring server environment,” on page 23before completing this configuration step. The monitoring server part of thisconfiguration is not applicable if the monitoring server is not running on thecontroller systems.

Table 8. CNMSTYLE statements to start the monitoring server and NetView agent on thebackup controller

Statement Purpose

INIT.EMAAUTO Set this statement to Yes. Specifies to process theEMAAUTO.TEMS.procStr statement and theEMAAUTO.TEMA.procStr statement.

EMAAUTO Specifies whether the monitoring server(EMAAUTO.TEMS.procStr) or the NetView agent(EMAAUTO.TEMA.procStr) is to be started duringNetView initialization. The TEMA tower must beenabled.

function.autotask.EMAAUTOM Specifies the EMAAUTOM autotask on whichthe automation runs

AUTOTASK.?EMAAUTOM.Console Specifies MVS console that is associated with theEMAAUTOM autotask

Tuning considerationsSome functions for GDPS Active/Active Continuous Availability solution createextensive automation message traffic on the NetView program that runs on thecontroller. Examples of functions that create message traffic include:v Replication products for Active/Standby and Active/Query workloads that

generate EIF eventsv Replication data monitoring

To reduce the volume of messages in your Canzlog log, you can issue thefollowing commands:


|||

||

||||

||||||

|||

|||

||||

||

|

||

Table 9. Reducing messages in the Canzlog log

Event type Command to suppress messages

Replication events OVERRIDE CNM493I=NO TASK=BNJDSERV

Replicationmonitoring data

OVERRIDE CNM493I=NO TASK=AUTOXCF

CNMSTREPIf you are using Replication monitoring, review and customize the CNMSTYLEstatements in the CNMSTREP member. The statements in the CNMSTREP memberprovide the following functions:v “Collecting data”v “Granting access to data” on page 18v “Setting up RMTCMD communication” on page 19

Copy the CNMSTREP statements that require modification, or must be appendedafter other existing CNMSTYLE member statements, to either CNMSTUSR orCxxSTGEN member and modify them there. Some of the statements in theCNMSTREP member are existing CNMSTYLE statements. If you alreadycustomized any of these statements, make sure that the statements for theActive/Active configuration are not overridden. If you add statements to theCxxSTGEN member, make sure that they are after the CNMSTACT includemember. To enable the statements that you change, run the appropriate RESTYLEcommand.

Collecting dataThe statements in Table 10 define the autotask, sampling interval, socket pathnames, and XCF rank for the replication monitoring component:

Table 10. CNMSTYLE statements that define the autotask and sampling interval forreplication monitoring

Statement Purpose

function.autotask.ACTTSK2 Specifies the autotask (ACTTSK2) that controlsDB2 replication data collection.

AUTOTASK.?ACTTSK2.Console Specifies MVS console that is associated with theACTTSK2 autotask.

ACTACT.DB2INT Specifies how often data is collected from theDB2 replication servers.

ACTACT.DB2PATH.n Specifies the socket path names for DB2replication data collection.

function.autotask.ACTTSK3 Specifies the autotask (ACTTSK3) that controlsIMS replication data collection.


function.autotask.ACTDATA Specifies the distributed autotask that is used toforward replication data to the controller system.

AUTOTASK.?ACTDATA.Console Specifies MVS console that is associated with theACTDATA autotask.

ACTACT.IMSINT Specifies how often data is collected from theIMS replication server.


||

||

||

|||

|

|

|

||

||

Table 10. CNMSTYLE statements that define the autotask and sampling interval forreplication monitoring (continued)

Statement Purpose

ACTACT.IMSPATH.n Specifies the socket path names for IMSreplication data collection.

ACTACT.VSAMINT Specifies how often data is collected from theVSAM replication server.

ACTACT.VSAMPATH.n Specifies the socket path names for VSAMreplication data collection.

function.autotask.ACTTSK4 Specifies the autotask (ACTTSK4) that controlsVSAM replication data collection.


XCF.RANK Specifies the XCF rank for this productionsystem to enable forwarding of replication datato the controller NetView program. A minimumvalue of 0 is required for replication dataforwarding to occur.

Usage notes:

1. The ACTIVEACTIVE tower and the ACTIVEACTIVE.REPLICATION subtower(DB2, IMS, VSAM, or any combination) must be active on the productionsystems.

2. For information about the size of the NetView agent workspaces for thereplication component, see Table 4 on page 10.

Granting access to dataThe NetView program must be authorized to access Replication Server data onproduction systems in the GDPS Active/Active Continuous Availability solution.

To allow access to Q replication data, grant one of the following permissions to theSAF user ID under which the NetView program runs:v Grant z/OS UNIX superuser authority to the user ID assigned to the NetView

job or started procedure. You can grant superuser authority by setting the z/OSUNIX user ID (UID) attribute to zero for the user ID.

v Grant the user ID access to the QREP.NETMGMT.DISPLAY SAF profile in theSERVAUTH class.

For more information, see the Q replication product library.

If IMS or VSAM replication data is protected by specifying the SAFEXIT statementin the IMS or VSAM Replication server, grant one of the following permissions tothe SAF user ID under which the NetView program runs:v If a security exit is provided, grant the user ID access to the profile and class

specified on the SAFEXIT statement by the MONCLASS and MONPROFkeywords.

v If a security exit is provided without specifying the MONCLASS andMONPROF keywords, grant the user ID access to the CEC.MONITOR SAFprofile in the SERVAUTH class.

For more information, see the IMS or VSAM product library.


|||

|||

|||

|||

||||||

|||

||

|

|||

|||

|||

|

Setting up RMTCMD communicationFor the GDPS Active/Active Continuous Availability solution, use IP for RMTCMDcommunication between NetView programs:RMTINIT.IP = Yes

Tuning considerationsThe NetView program monitors replication information on production systemsacross two sysplexes. These production system LPARs are started at different times.Because of this, NetView data collection is also started at different times.

For the NetView program to display the best performance metrics for the GDPSActive/Active Continuous Availability solution, you might want to stop datacollection after your environment is completely started, and restart data collectionat the same time using NetView timer functions. For example, if your applyreplication server is started before your capture replication server, your bytesreceived metric might be higher than your bytes sent metric.

Updating Event/Automation Service class definition statementsThe AQNCDS member of the SCNMUXCL data set provides class definitionstatements for the event receiver task (EVENTRCV) in E/AS. The statements mapEIF events from components of the GDPS Active/Active Continuous Availabilitysolution to alert NMVTs that are handled by NetView automation. Do not modifythe contents of the AQNCDS member because the NetView automation samplesdepend on the mappings defined in this member.

The IHSAECDS member in the SCNMUXCL data set provides sample definitionclass statements. Update the IHSAECDS member to uncomment the %INCLUDEstatement for AQNCDS.

Reviewing securityYou can use the NetView program to provide the following types of securityauthorizations:v “Password authorization”v “Command authorization” on page 20

The following members are provided for Active/Active security authorization:

AQNCATSample NetView Active/Active command authorization table

AQNOPFSample NetView Active/Active operator definitions

AQNSAFSample to set RACF definitions for NetView Active/Active operators andcommands

These members do not contain all of the security that is required for the GDPSActive/Active Continuous Availability solution. These members are used with baseNetView function security.

Password authorizationThe NetView program provides the option of specifying whether passwordchecking is performed by SAF security, such as RACF, or the NetView program.


||||

||||||

|

||||||

|||

SAF securityIf an SAF product, such as RACF, is installed on your system, you can use it forpassword protection (rather than using static passwords in the DSIOPF andAQNOPF members).

To use an SAF product for password authorization, follow these steps:1. In the CNMSTUSR or CxxSTGEN member, specify SECOPTS.OPERSEC

statement with values of SAFPW, SAFCHECK, or SAFDEF. For moreinformation about updating CNMSTYLE statements, see IBM Tivoli NetView forz/OS Administration Reference.

2. Review the RACF definitions in the CNMSAF2 and AQNSAF samples. Updateany definitions as necessary for your environment. For your changes to takeeffect, refresh the NETCMDS class definitions in the SAF product. For moreinformation about using an SAF product for password authorization, see theIBM Tivoli NetView for z/OS Security Reference.

NetView product securityThe passwords that are stored in the DSIOPF and AQNOPF members can be usedto check logon password authorization.

To use the NetView product for password authorization, follow these steps:1. In the CNMSTUSR or CxxSTGEN member, specify SECOPTS.OPERSEC

statement with a value of NETVPW. For more information about updatingCNMSTYLE statements, see IBM Tivoli NetView for z/OS Administration Reference.

2. The passwords stored in the DSIOPF member and the AQNOPF member(included in the DSIOPF member) are used to check logon passwordauthorization. Update these members to change a password.

RMTCMD securityReview the RMTINIT security statements in your CNMSTYLE member. RMTCMDcommunication is required between the controller systems and production systems.Also, RMTCMD communication between the controller and production systems isnot on the same autotask. Ensure that you allow RMTCMD communicationbetween the following autotasks:v ?ACTDATA autotask (default is AUTOADAT)v ?ACTREPL autotask (default is AUTOARPL)v ?PRIMARY autotask (default is AUTO1)v ?XCF autotask (default is AUTOXCF)

Command authorizationWith the NetView program, you can use the command authorization table or SAFcommand authorization to restrict access to commands, certain keywords, andvalues. For more information about which commands, keywords, and values areeligible for protection, see the IBM Tivoli NetView for z/OS Security Reference.

The following Active/Active autotasks are defined in the AQNOPF member that isincluded in the DSIOPF member:

Table 11. Autotasks defined in the AQNOPF member

Autotask Purpose

AUTOACTn Used for data collection by the Lifeline Advisorand the replication monitoring components


|

Table 11. Autotasks defined in the AQNOPF member (continued)

Autotask Purpose

AUTOACTA Used for starting the monitoring server and theNetView agent when an ACTVCTL TAKEOVERcommand is issued

AUTOADAT Used by the Lifeline Advisor and the replicationmonitoring components

AUTOAEVT Used to process replication events.

AUTOARPL Used with the ACTVREPL command on productionsystems

SAF productSAF command authorization enables you to use RACF or a comparable SAFproduct, to restrict access to commands, keywords, and values, and to grantoperator access to them. You do this by defining the commands, keywords, andvalues as resources in the NETCMDS class of the SAF product, and then selectivelygranting operator access. You can also specify commands, keywords, and valuesthat are accessible universally.

To use an SAF product for command authorization, follow these steps:1. Review the RACF definitions in the CNMSAF2 and AQNSAF samples. Update

any definitions as necessary for your environment. For example, you mightwant to restrict the ACTVCTL CONNECT and ACTVCTL TAKEOVER commands.

2. For your changes to take effect, refresh the NETCMDS class definitions in theSAF product.

NetView product securityThe NetView command authorization table enables you to restrict access tocommands, keywords, and values. It then allows you to permit operators andgroups of operators to access these restricted commands, keywords, and values.You can also specify commands, keywords, and values that pass authorizationchecking.

To use the NetView product for command authorization, follow these steps:1. Review the CNMSCAT2 table and the AQNCAT table (included in the

CNMSCAT2 table). The NetView command authorization table is stored as amember of the DSIPARM data set. Update definitions as necessary for yourenvironment. For example, you might want to restrict the ACTVCTL CONNECT andACTVCTL TAKEOVER commands.

2. After you make changes, use the REFRESH command to dynamically updateyour table.


||

|||

|

|


Chapter 3. Choosing the monitoring server environment

Before you can configure the IBM Tivoli Monitoring environment, you mustdetermine the environment and configuration of the monitoring servers. There aremany alternatives for monitoring server environments. The following are someexamples:v “Hot standby monitoring server running on a pair of non-z/OS servers”v “High availability monitoring server running in a z/OS sysplex” on page 25v “Remote monitoring servers running in z/OS monoplexes” on page 26

If this is the first time you are configuring the IBM Tivoli Monitoring environment,review the progression of tasks defined in the IBM Tivoli OMEGAMON® XEMonitoring Agents on z/OS: Quick Start Guide.

Note: See the following documentation for instructions on creating andconfiguring the IBM Tivoli Monitoring environment, rather than performing thesteps in this chapter:v For the hub monitoring server:

– IBM Tivoli NetView for z/OS Installation: Configuring the NetView EnterpriseManagement Agent, “Creating a new runtime environment”

– OMEGAMON XE and Tivoli Management Services Installation and Setup Guide

v For the NetView agent running on the controller system: IBM Tivoli NetView forz/OS Installation: Configuring the NetView Enterprise Management Agent, “Updatingthe NetView agent in an existing RTE”

After following the instructions in these publications, you can create a customnavigator view for the GDPS Active/Active Continuous Availability solution asdescribed in “Creating a custom navigator view” on page 50.

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

Configuring the IBM Tivoli Monitoringenvironment

v IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: CommonPlanning and Configuration Guide

v IBM Tivoli Management Services on z/OS:Configuring the Tivoli Enterprise MonitoringServer on z/OS

Configuring the NetView agent IBM Tivoli NetView for z/OS Installation:Configuring the NetView Enterprise ManagementAgent

Hot standby monitoring server running on a pair of non-z/OS serversFigure 3 on page 24 is an example environment with two identical hub monitoringservers that run in a hot standby configuration. As changes are made to the activemonitoring server, they are automatically replicated to the mirror monitoringserver.


||

|||

These are the advantages of using a hot standby configuration:v Monitoring servers are automatically kept synchronous.v The mirror monitoring server automatically becomes the active monitoring

server when necessary.

These are the disadvantages of using a hot standby configuration:v When a monitoring server switch occurs, the portal server must be reconfigured

to use the active monitoring server and then recycled.


Configuring the IBM Tivoli Monitoringenvironment for this configuration




LIfeline monitoringconnections

Backup Controller

Secondary Advisor

NetView Agent

NetView/SA/GDPS

MonitoringServer

z/OS LPAR

Primary Controller

Primary Advisor

NetView Agent

MonitoringServer

z/OS LPAR

Tivoli

Enterprise Portal

Lifeline AdvisorsConfiguration

MonitoringComponents

Linux on System z LPAR

Portal Server

Monitoring ServerReplication

NetView/SA/GDPS

Linux on System z LPAR

Figure 3. Hot standby monitoring server configuration


High availability monitoring server running in a z/OS sysplexFigure 4 is an example environment with the monitoring server that has the abilityto move from one LPAR in the sysplex to another. The monitoring server data setsare on shared DASD.

The advantages of this configuration are:v No synchronization is required because all data sets are shared between the two

LPARs.v The monitoring server switch appears to the portal server as a hub monitoring

server restart.

The disadvantages of this configuration are:v The monitoring server must be stopped on its original LPAR, and then started

on its new target LPAR.v The portal server must be restarted.


Configuring the IBM Tivoli Monitoringenvironment for this configuration



Portal Server


Backup Controller

NetView AgentMonitoring

Server

Sysplex A

z/OS LPAR

Primary Controller

NetView Agent

NetView/SA/GDPS

MonitoringServer

z/OS LPAR

SharedDASD

Tivoli

Enterprise Portal

AIX



Secondary Advisor

Primary Advisor

NetView/SA/GDPS

Figure 4. High availability monitoring server configuration

Chapter 3. Choosing the monitoring server environment 25



Remote monitoring servers running in z/OS monoplexesFigure 5 is an example of an environment with remote monitoring servers that arerunning on independent LPARs, each with a dedicated set of monitoring serverdata sets. The data is sent to the hub monitoring server that resides on an IBMLinux on System z® system.

Notes for monitoring when the primary controller is restarted:

1. Monitoring stays on the backup controller for the GDPS Active/ActiveContinuous Availability solution until the NetView agent on the primarycontroller detects that the monitoring server on the primary controller is active.The NetView agent checks for the reactivation of the monitoring server usingthe value that is specified on the CTIRA_PRIMARY_FALLBACK_INTERVAL parameter.For more information about CTIRA_PRIMARY_FALLBACK_INTERVAL, see Chapter 4,“Scenario: Configuring remote monitoring servers to run in z/OS monoplexesusing the PARMGEN method,” on page 29 and Appendix D, “Scenario:Configuring remote monitoring servers to run in z/OS monoplexes using theconfiguration tool,” on page 149.

2. Running the NetView agent and monitoring server on the backup controllerprovides quicker failover; you can also monitor your NetView program on thebackup controller.

These are the advantages of using this configuration:

NetView/SA/GDPS

Portal Server


Backup Controller

Secondary Advisor

NetView Agent

NetView/SA/GDPS

z/OS LPAR

Primary Controller

Primary Advisor

NetView Agent

RemoteMonitoring

Server

z/OS LPAR

Tivoli

Enterprise Portal



RemoteMonitoring

Server

HubMonitoring

Server

Linux on System z

Figure 5. Remote monitoring servers configuration


|

>

>>>>>>>>>>

>>>

v The hub monitoring server does not have to be recycled when controllerswitches occur.

v The portal server does not have to be reconfigured or recycled when controllerswitches occur.

v Situations and events are not lost when there is a controller outage.

See Chapter 4, “Scenario: Configuring remote monitoring servers to run in z/OSmonoplexes using the PARMGEN method,” on page 29 for installation steps.

Chapter 3. Choosing the monitoring server environment 27


Chapter 4. Scenario: Configuring remote monitoring serversto run in z/OS monoplexes using the PARMGEN method

The configuration described in Figure 5 on page 26 has a hub monitoring serverthat runs on a Linux on System z server. There are two remote monitoring servers,one running on the primary controller LPAR, and the other running on the backupcontroller LPAR. The configuration steps use the following host names andmonitoring server names:

Table 12. Host names and monitoring server names for scenario 2

Host nameand role

Monitoring servernode ID and type RTE name Data set name prefix

TIVLNX21(non-z/OS)

HUBTEM21:CMS(hub monitoringserver)

n/a n/a

PCHOST(primarycontroller)

PCRTEM22:CMS(remote monitoringserver)

PCRTEM22 NETVIEW.EMAMVS22.PCRTEM22

BCHOST(backupcontroller)

BCRTEM23:CMS(remote monitoringserver)

BCRTEM23 NETVIEW.EMAMVS23.BCRTEM23

The hub monitoring server is already configured. For details on configuring thehub monitoring server on platforms other than z/OS platforms, including Linuxon System z platforms, see the IBM Tivoli Monitoring Installation and Setup Guide.For details on configuring a hub monitoring server on a z/OS system, seeConfiguring the Tivoli Enterprise Monitoring Server on z/OS.

To configure the IBM Tivoli Monitoring environment on the primary and backupcontroller systems using the PARMGEN method, follow these procedures:1. Make sure that you have the Tivoli Management Services components installed

and the NetView agent installed.During the installation process, you must provide a host name or IP address forthe hub monitoring server. You are also required to enter passwords on somepanels. For some operating systems, you are required to provide a password of6 or more characters. Check the password requirements for your operatingsystem before you begin the installation process.

2. “Creating and configuring an RTE to contain the remote monitoring server andNetView agent on the primary controller” on page 30

3. “Creating and configuring an RTE to contain the remote monitoring server andNetView agent on the backup controller” on page 38

4. “Loading the agent data files and configuring the portal server” on page 465. “Historical data collection and reporting” on page 506. “Creating a custom navigator view” on page 50


|

|

|

|||||

||

||||||

|||||

||

|||

|||

||

|||

|||

||

|

|||||

||

||

|||||

||

||

|

|

|

Creating and configuring an RTE to contain the remote monitoringserver and NetView agent on the primary controller

The example in this section uses a full runtime environment (RTE) namedPCRTEM22. This environment contains all the libraries required by the remotemonitoring server and is self-contained. All base libraries and LPAR-specificlibraries are allocated within the PCRTEM22 runtime environment.RTE Name: PCRTEM22Type: FULLHilev: NETVIEW.V6R2RTEShares with: (none)

Complete these procedures to create and configure an RTE to contain the remotemonitoring server on the primary controller:1. Access and start the PARMGEN tool2. Set up the PARMGEN work environment for an RTE3. Review the PARMGEN job index4. Update the interim libraries and create profiles5. Customize PARMGEN configuration profiles6. Validate PARMGEN profile parameter values7. Create the RTE members and jobs8. Submit batch jobs to complete the PARMGEN setup

Starting the PARMGEN tool

Follow these steps to start the PARMGEN tool:1. Log on to a TSO session.2. Enter ISPF.3. From the Primary Option Menu, enter option 6 (Command).4. If you are using a 3270 Model 2 (24 x 80) display, turn off the predefined

function (PF) keys so that the function keys are not truncated. To do this, enterPFSHOW on the command line and repeat this command until the ISPF defaultfunction keys are no longer displayed.

5. From the command line, enter the following command:EX ’&shilev.TKANCUS’

&shilev is the high-level qualifier that you specified when you installed TivoliManagement Services,A panel similar to Figure 6 on page 31 is displayed.


||

|

||||

||||

||

|

|

|

|

|

|

|

|

|

|

|

|

|

||||

|

|

||

||

6. Review the checklists by selecting options 1 - 3.7. You can skip option 4. You already performed this step when you installed

Tivoli Management Services.8. From the z/OS Installation and Configuration Tools panel, selection option 5 to

display the Parameter Generator (PARMGEN) Workflow panel.A panel similar to Figure 7 is displayed.

9. Enter the following parameter values for your environment:

GBL_USER_JCLThe name of the JCL library to be created for PARMGEN jobs, forexample NETVIEW.EMAMVS22.JCL

Welcome to the z/OS Installation and Configuration Tools forIBM Tivoli Management Services (TMS) dependent products

Read/Print Checklists prior to installation and configuration:

1. Checklist: Planning and Acquisition2. Checklist: Prepare the system3. Checklist: Review the product components & installation steps

4. SMP/E-install z/OS products with Install Job Generator (JOBGEN)5. Configure z/OS products with Parameter Generator Workflow (PARMGEN)

6. Checklist: Complete the post-configuration steps

7. About joining the community: Service Management Connect (SMC)

P. Print checklist(s) selectively

Option ===>

Figure 6. z/OS Installation and Configuration Tools panel

--------------- PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME --------------Enter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: ____________________________________________

PARMGEN common/global library for RTEs (CONFIG DD lib. in STCs)RTE_PLIB_HILEV: ________________________

High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: ________ (Type ? for a list of configured RTEs)

Runtime environment (RTE) name for this LPAR

Enter n (1-11) to perform tasks. Status DateEnter ns (1s-11s) to display detailed status. --------- ----------

1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (Optional)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup profile (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

Option ===> Scroll ===>

Figure 7. Parameter Generator (PARMGEN) Workflow panel

Chapter 4. Scenario: Configuring remote monitoring servers to run in z/OS monoplexes using the PARMGEN method 31

|||||||||||||||||||||||||

|||||||||||||||||||||||||||||||

|

||

||

||

|

|||

RTE_PLIB_HILEVThe high-level qualifier for the PARMGEN work libraries, for exampleNETVIEW.EMAMVS22.

RTE_NAMEThe name of the runtime environment to be created, for examplePCRTEM22.

Option 1. KCIJPCFG Setting up the PARMGEN work environmentfor an RTE1. Select option 1 to display the Set Up PARMGEN Work Environment panel.2. From the Set Up PARMGEN Work Environment panel, enter a job statement

to be used for PARMGEN jobs, for example://USER1A JOB MSGLEVEL=1,MSGCLASS=A,NOTIFY=USER1

3. If the GBL_USER_JCL library that you specified on the Parameter Generator(PARMGEN) Workflow panel does not exist, a popup is displayed. Press Enterto allocate the JCL library and return to the Set Up PARMGEN WorkEnvironment panel. Press Enter to continue setting up the PARMGEN workenvironment.

4. From the Set Up PARMGEN Work Environment panel (2 of 3), specify a valuefor the following fields:

GBL_TARGET_HILEVThe high-level qualifier for your SMP/E target libraries, for exampleNETVIEW.V6R2M0

GBL_SYSDA_UNITThe disk unit name for non-VSAM data sets, for example SYSDA.

Press Enter.5. From the Set Up PARMGEN Work Environment panel (3 of 3), enter any

values required by your installation for creating new data sets. Press Enter.6. The Display PARMGEN Environment Analysis panel lists the components

installed in your TKANCUS data set. Press Enter to display the ExcludeProducts from PARMGEN Customization panel.

7. To exclude any products from PARMGEN customization, enter X to the left ofthe product code. Exclude all components except for KDS and KNA. Whenyou finish, specify Y in the confirm field and press Enter.

8. Review and submit the KCIJPCFG job. Verify that the job ends with a 0 returncode.If the job does not end with a 0 return code, correct the job and resubmit it.

9. Press F3 to display messages for the submitted job.10. Press Enter to return to the Parameter Generator (PARMGEN) Workflow

panel. Note the status and date to the right of the step that you justcompleted.

Option 2. $JOBINDX Reviewing the PARMGEN job index1. From the Parameter Generator (PARMGEN) Workflow panel, select option 2 to

display the PARMGEN job index.2. Review the information on this panel.3. Press F3.


|||

|||

||

|

||

|

|||||

||

|||

||

|

||

|||

|||

||

|

|

|||

|

||

|

|

Option 4. KCIJPUP1 Updating interim libraries and creatingprofiles

The PARMGEN tool uses sets of interim and working libraries to storeconfiguration values. Interim libraries are created and populated based on theproducts that you selected to configure and the values that were supplied duringPARMGEN tool processing when you set up the work environment.1. From the Parameter Generator (PARMGEN) Workflow panel, select option 4 to

update interim libraries and create profiles.2. Review and submit the KCIJPUP1 job. Verify that the job ends with a 0 return

code.If the job does not end with a 0 return code, correct the job and resubmit it.

3. Press F3 to display messages for the submitted job.4. Press Enter to return to the Parameter Generator (PARMGEN) Workflow panel.

Option 8. Customizing PARMGEN configuration profiles1. From the Parameter Generator (PARMGEN) Workflow panel, select option 8 to

customize configuration profiles.Use Option 8 to override or specify values for the configuration files. Most ofthe IBM Tivoli Monitoring and NetView agent parameters are set in the RTELPAR profile. You can use the global parameters selection to specify thelocation of key libraries on your system.Use the TSO editor session when you make changes. Some optional values arecommented out in the file. If you modify any of these values, make sure thatyou uncomment the statement.

2. Select option 1 to customize the RTE LPAR profile.3. The CONFIGURE_PRODUCTS section shows the products that are included or

excluded. Review the default settings and update them as necessary for yourinstallation. Parameters beginning with KDS are for the monitoring server. TheNetView agent uses parameters beginning with KNA.Make sure that you review and update the following parameters:v Type of monitoring server (remote).

This is controlled by the KDS_TEMS_TYPE parameter. This is set to REMOTE.For the NetView agent to connect to the monitoring server, make sure thatthe KNA_TEMS_LOCAL_CONNECT_FLAG parameter is set to Y and that theKNA_TEMS_TCP_HOST parameter is correct. In this example, PCHOST is the hostname.The monitoring server defined in this scenario is a remote monitoring server.Information for the hub monitoring server to which it connects is set by theparameters beginning with KDS_HUB. Verify or set the following parameters:– KDS_HUB_TEMS_NAME_NODEID

In this scenario, HUBTEM21:CMS is the value for this parameter.– KDS_HUB_TCP_HOST

In this scenario, TIVLNX21 is the value for this parameter.– KDS_HUB_TCP_xxxxx_PORT_NUM where xxxxx corresponds to the

communications protocol (PIPE,UDP,PIPE6,UDP6,PIPES,PIPE6S) used tocontact the hub.In this scenario, IP.PIPE is used as the protocol and theKDS_HUB_TCP_PIPE_PORT_NUM parameter is set to 1918.


||

||||

||

||

|

|

|

|

||

||||

|||

|

||||

|

|

|

||||

|||

|

|

|

|

|||

||

To define a backup monitoring server, use the parameters beginning withKNA_TEMS_BKUP1. Verify or set the following parameters– KNA_TEMS_BKUP1_NAME_NODEID

In this scenario, BCRTEM23:CMS is the value for this parameter.– KNA_TEMS_BKUP1_TCP_HOST

In this scenario, BCHOST is the value for this parameter.v Communications-related information (for example TCP addresses).

The addresses are assigned default values. Verify that the followingmonitoring server parameters are correct:– RTE_TCP_HOST– RTE_TCP_PORT_NUM– RTE_TCP_STC

Verify that the following NetView agent parameters are correct:– KNA_AGT_TCP_HOST– KNA_TCP_STC

Verify that the following parameters that control the communicationsprotocols used by the monitoring server and the NetView agent are correct:– KDS_TEMS_COMM_PROTOCOLn, where n is a value 1-7– KNA_AGT_COMM_PROTOCOLn, where n is a value 1-7– KDS_TEMS_TCP_xxxxx_PORT_NUM where xxxxx corresponds to the

communications protocol (PIPE,UDP,PIPE6,UDP6,PIPES,PIPE6S)– KNA_TEMS_TCP_xxxxx_PORT_NUM where xxxxx corresponds to the

communications protocol (PIPE,UDP,PIPE6,UDP6,PIPES,PIPE6S)In this scenario, IP.PIPE is used as the communication protocol. Set or verifythe following parameter values:– RTE_TCP_HOST - PCHOST– RTE_TCP_STC - #– RTE_TCP_PORT_NUM - 1918– KDS_TEMS_TCP_HOST - PCHOST– KDS_TEMS_TCP_STC - #– KDS_TEMS_COMM_PROTOCOL1 - IPPIPE– KDS_TEMS_TCP_PIPE_PORT_NUM - 1918– KNA_AGT_TCP_HOST - PCHOST– KNA_TCP_STC - #– KNA_TEMS_TCP_HOST - PCHOST– KNA_AGT_COMM_PROTOCOL1 - IPPIPE– KNA_AGT_TCP_PIPE_PORT_NUM - 1918Make sure that the KDS_TEMS_KLX_TCP_TOLERATERECYCLE andKNA_AGT_KLX_TCP_TOLERATERECYCLE parameters are set to Y. This enables themonitoring server and the NetView agent to reconnect to its TCP/IP stackwithout being recycled after the TCP/IP stack is recycled.

v PPI sender and receiver names

Important: The KNA_PPIRCV_PPI_RECEIVER_CNMEMARX andKNA_PPISND_PPI_SENDER_CNMEMATX parameters control the PPI sender andreceiver names that are used by the NetView agent.

The receiver name is controlled by the KNA_PPIRCV_PPI_RECEIVER_CNMEMARXparameter. This name must match the DESTPPI receiver name that isspecified in the CNMSTYLE member or its include member. The defaultvalue is CNMEMARX.


||

|

|

|

|

|

|||||

|||

||

|

|

||

||

||||||||||||||

||||

|

|||

||||

The sender name is controlled by the KNA_PPISND_PPI_SENDER_CNMEMATXparameter. The default name is CNMEMATX. There is no matchingCNMSTYLE statement.

v Security settings to enable encryption for the monitoring serverv Security settings to enable Take Action command forwarding.

System commands issued from the Tivoli Enterprise Portal using Take Actioncommands or situations run without command authorization or an audittrail. You can use the NetView product to perform command authorizationfor these system commands and to provide an audit trail.Command authorization for the Take Action system commands uses theportal user ID, which is sent to the NetView program with the command.The portal user ID that is sent is used to determine the user ID that issuesthe command. When a command is sent from a situation, the user ID that issent is the last one that edited the situation. Password validation is notperformed. If a NetView operator ID exists that matches the portal user IDand has the required command authorization, then the command is run onthe existing NetView operator ID. For more information about protectingMVS system commands, refer to the IBM Tivoli NetView for z/OS SecurityReference.Some agents provide their own Take Action commands, known as agentcommands. Agent commands have an associated two-character prefix fortheir product code. These commands are not sent to the NetView programfor command authorization. The only agent commands that are sent to theNetView program for authorization are the NetView agent commandsprefixed with NA. For information about creating or editing a Take Actioncommand, refer to the IBM Tivoli Monitoring: Tivoli Enterprise Portal User'sGuide.You can display Take Action commands and command responses in theNetView Command Response workspace. Additionally, you can display theBNH806I and BNH807I audit trail messages in the NetView Audit Logworkspace.Use the following parameters to enable command authorization checking forsystem commands sent from the hub monitoring server:– KDS_PPI_RECEIVER

Specifies the name of the NetView PPI Receiver. The value must match thePPI receiver name specified on the NetView APSERV command. Thedefault value is CNMPCMDR.

– KDS_PPI_SENDER

Optional: Specify a value for the PPI sender. If you do not specify a value,the job name of the monitoring server is used when the command iswritten to the NetView log.

Equivalent parameters are available to enable command authorizationchecking for commands sent from the NetView agent:– KNA_AGT_KGLHC_PPI_RECEIVER


– KNA_AGT_KGLHC_PPI_SENDER

Optional: Specify a value for the PPI sender.For definitions for the common parameters, see the IBM Tivoli OMEGAMONXE and Tivoli Management Services on z/OS: Parameter Reference. For NetViewagent definitions, see IBM Tivoli NetView for z/OS Installation: Configuring the


|||

|

|

||||

||||||||||

||||||||

||||

||

|

|||

|

|||

||

|

|||

|

|

|||

NetView Enterprise Management Agent. For information about configuringsecurity settings for a monitoring server running in a z/OS environment, seeIBM Tivoli OMEGAMON XE and Tivoli Management Services: Configuring theTivoli Enterprise Monitoring Server on z/OS.

4. Press F3 to return to the menu panel.5. Select option 2 to review and specify global parameters. Review the default

settings and update them as necessary for your installation.

Usage notes:

v The global parameters define system data sets that include started taskprocedures, load modules, and configuration files. In many cases, the defaulthigh-level qualifier for the data set is SYS1. Review the global parametersstarting with the GLBL_DSN_SYS1 parameter and verify that the correct datasets are defined.

v The GBL_DSN_NETVIEW_CNMLINK parameter specifies the name of the NetViewCNMLINK data set. Review this parameter and make sure that the data setname is correct. In this scenario, NETVIEW.V6R2M0.CNMLINK is the value for thisparameter.

6. Press F3 to return to the menu panel.7. Select option 7 (WCONFIG). Locate the KNA$PENV member and edit it. Verify

that it contains the following statements:CTIRA_RECONNECT_WAIT = 60CTIRA_HEARTBEAT = 1

Add the following statements:KNA_ACTACT=YESCTIRA_PRIMARY_FALLBACK_INTERVAL=150

For more information about the CTIRA_ environment variables, see the IBMTivoli Monitoring: Installation and Setup Guide.

8. Press F3 to return to the menu panel.9. Press F3 again to return to Parameter Generator (PARMGEN) Workflow panel.

Option 9. KCIJPVAL Validating PARMGEN profile parametervalues1. From the Parameter Generator (PARMGEN) Workflow panel, select option 9 to

validate the profile parameter values.2. Review and submit the KCIJPVAL job. Verify that the job ends with a 0 return



Option 10. Creating the RTE members and jobs

Prior to creating the runtime environment, the PARMGEN tool stores the suppliedconfiguration in a set of members in a working library. These members are used tocreate the configuration files in the runtime environment.1. From the Parameter Generator (PARMGEN) Workflow panel, select option 10 to

create the RTE members and jobs.2. Select option 1 to edit the composite $PARSE job.


||||

|

||

|

|||||

||||

|

>>

>>

>

>>

>>

|

|

||

||

||

|

|

|

|

|||

||

|

3. Review and submit the KCIJPPRS job. Verify that the job ends with a 0 returncode.If the job does not end with a 0 return code, correct the job and resubmit it.

4. Press F3 to display messages for the submitted job.5. Press Enter to return to the menu panel.6. Press F3 to return to the Parameter Generator (PARMGEN) Workflow panel.

Option 11. Submitting batch jobs to complete the PARMGENsetup1. From the Parameter Generator (PARMGEN) Workflow panel, select option 11

to submit batch jobs to complete the set up. These jobs create the runtimeenvironment files.

2. Select option 1 to edit the composite master submit job.3. Review and submit the KCIJPSUB job. Verify that the jobs end with a 0 return

code. The KCIJPIVP job might end with return code of 4 because thecomposite master job did not run the conditional jobs.If a job does not end with the expected return code, correct the job andresubmit it.

Usage note: You can submit conditional jobs by uncommenting statements inthe KCIJPSUB job or you can submit jobs separately from the Submit BatchJobs panel. This example submits the KCIJPUSS, KCIJPSYS, KCIJPW2R andKCIJPIVP jobs separately.

4. Press F3 to display messages for the submitted job.5. Press Enter to return to the menu panel.6. Select option 2 to edit allocate runtime libraries.7. Review and submit the KCIJPALO job. Verify that the job ends with a 0 return


8. Press F3 to display messages for the submitted job.9. Press Enter to return to the menu panel.

10. Select option 3 to load the TK* to RK* runtime libraries.11. Review and submit the KCIJPLOD job. Verify that the job ends with a 0 return


12. Press F3 to display messages for the submitted job.13. Press Enter to return to the menu panel.14. Select option 7 to edit the USS system setup job.15. Review and submit the KCIJPUSS job. Verify that the job ends with a 0 return


16. Press F3 to display messages for the submitted job.17. Press Enter to return to the menu panel.18. Select option 8 to edit the system setup job.19. Review and submit the KCIJPSYS job. Verify that the job ends with a 0 return


20. Press F3 to display messages for the submitted job.


||

|

|

|

|

||

|||

|

|||

||

||||

|

|

|

||

|

|

|

|

||

|

|

|

|

||

|

|

|

|

||

|

|

21. Press Enter to return to the menu panel.22. Select option 11 to edit the WK* to RK* deployment job.23. Review and submit the KCIJPW2R job. Verify that the job ends with a 0 return


24. Press F3 to display messages for the submitted job.25. Press Enter to return to the menu panel.26. Select option 12 to edit the configuration verification job.27. Review and submit the KCIJPIVP job. Verify that the job ends with a 0 or 4

return code.If the job does not end with a 0 or 4 return code, correct the job and resubmitit. If the job ends with a 4 return code, examine the job output for the reason.

28. Press F3 to display messages for the submitted job.29. Press Enter to return to the menu panel.30. Press F3 to return to the Parameter Generator (PARMGEN) Workflow panel.31. Press F3 twice to exit the PARMGEN tool.

Creating and configuring an RTE to contain the remote monitoringserver and NetView agent on the backup controller

A full runtime environment (RTE) named BCRTEM23 contains all the librariesrequired by the remote monitoring server and is self-contained. All base librariesand LPAR-specific libraries are allocated within the BCRTEM23 runtimeenvironment.RTE Name: BCRTEM23Type: FULLHilev: NETVIEW.V6R2RTEShares with: (none)

Complete these procedures to create and configure an RTE to contain the remotemonitoring server on the backup controller:1. Access and start the PARMGEN tool2. Set up the PARMGEN work environment for an RTE3. Review the PARMGEN job index4. Update the interim libraries and create profiles5. Customize PARMGEN configuration profiles6. Validate PARMGEN profile parameter values7. Create the RTE members and jobs8. Submit batch jobs to complete the PARMGEN setup

Starting the PARMGEN tool

Follow these steps to start the PARMGEN tool:1. Log on to a TSO session.2. Enter ISPF.3. From the Primary Option Menu, enter option 6 (Command).4. If you are using a 3270 Model 2 (24 x 80) display, turn off the predefined

function (PF) keys so that the function keys are not truncated. To do this, enterPFSHOW on the command line and repeat this command until the ISPF defaultfunction keys are no longer displayed.


|

|

||

|

|

|

|

||

||

|

|

|

|

||

|

||||

||||

||

|

|

|

|

|

|

|

|

|

|

|

|

|

||||

5. From the command line, enter the following command:EX ’&shilev.TKANCUS’

&shilev is the high-level qualifier that you specified when you installed TivoliManagement Services,A panel similar to Figure 6 on page 31 is displayed.

6. Review the checklists by selecting options 1 - 3.7. You can skip option 4. You already performed this step when you installed

Tivoli Management Services.8. From the z/OS Installation and Configuration Tools panel, selection option 5 to

display the Parameter Generator (PARMGEN) Workflow panel.A panel similar to Figure 7 on page 31 is displayed.

Welcome to the z/OS Installation and Configuration Tools forIBM Tivoli Management Services (TMS) dependent products

Read/Print Checklists prior to installation and configuration:

1. Checklist: Planning and Acquisition2. Checklist: Prepare the system3. Checklist: Review the product components & installation steps

4. SMP/E-install z/OS products with Install Job Generator (JOBGEN)5. Configure z/OS products with Parameter Generator Workflow (PARMGEN)

6. Checklist: Complete the post-configuration steps

7. About joining the community: Service Management Connect (SMC)

P. Print checklist(s) selectively

Option ===>

Figure 8. z/OS Installation and Configuration Tools panel


|||||||||||||||||||||||||

|

|

||

||

|

||

||

||

9. Enter the following parameter values for your environment:

GBL_USER_JCLThe name of the JCL library to be created for PARMGEN jobs, forexample NETVIEW.EMAMVS23.JCL

RTE_PLIB_HILEVThe high-level qualifier for the PARMGEN work libraries, for exampleNETVIEW.EMAMVS23.

RTE_NAMEThe name of the runtime environment to be created, for exampleBCRTEM23.

Option 1. KCIJPCFG Setting up the PARMGEN work environmentfor an RTE1. Select option 1 to display the Set Up PARMGEN Work Environment panel.2. From the Set Up PARMGEN Work Environment panel, enter a job statement

to be used for PARMGEN jobs, for example://USER1A JOB MSGLEVEL=1,MSGCLASS=A,NOTIFY=USER1

3. If the GBL_USER_JCL library that you specified on the Parameter Generator(PARMGEN) Workflow panel does not exist, a popup window is displayed.Press Enter to allocate the JCL library and return to the Set Up PARMGENWork Environment panel. Press Enter to continue setting up the PARMGENwork environment.

4. From the Set Up PARMGEN Work Environment panel (2 of 3), specify a valuefor the following fields:

GBL_TARGET_HILEVThe high-level qualifier for your SMP/E target libraries, for exampleNETVIEW.V6R2M0

GBL_SYSDA_UNITThe disk unit name for non-VSAM data sets, for example SYSDA.

--------------- PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME --------------Enter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: ____________________________________________

PARMGEN common/global library for RTEs (CONFIG DD lib. in STCs)RTE_PLIB_HILEV: ________________________

High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: ________ (Type ? for a list of configured RTEs)

Runtime environment (RTE) name for this LPAR

Enter n (1-11) to perform tasks. Status DateEnter ns (1s-11s) to display detailed status. --------- ----------

1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (Optional)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup profile (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

Option ===> Scroll ===>

Figure 9. Parameter Generator (PARMGEN) Workflow panel


||||||||||||||||||||||||||||||||

|||

|||

|||

||

|

||

|

|||||

||

|||

||

Press Enter.5. From the Set Up PARMGEN Work Environment panel (3 of 3), enter any

values required by your installation for creating new data sets. Press Enter.6. The Display PARMGEN Environment Analysis panel lists the components

installed in your TKANCUS data set. Press Enter to display the ExcludeProducts from PARMGEN Customization panel.

7. To exclude any products from PARMGEN customization, enter X to the left ofthe product code. Exclude all components except for KDS and KNA. Whenyou finish, specify Y in the confirm field and press Enter.

8. Review and submit the KCIJPCFG job. Verify that the job ends with a 0 returncode.If the job does not end with a 0 return code, correct the job and resubmit it.

9. Press F3 to display messages for the submitted job.10. Press Enter to return to the Parameter Generator (PARMGEN) Workflow

panel. Note the status and date to the right of the step that you justcompleted.

Option 2. $JOBINDX Reviewing the PARMGEN job index1. From the Parameter Generator (PARMGEN) Workflow panel, select option 2 to

display the PARMGEN job index.2. Review the information on this panel.3. Press F3.

Option 4. KCIJPUP1 Updating interim libraries and creatingprofiles1. From the Parameter Generator (PARMGEN) Workflow panel, select option 4 to

update interim libraries and create profiles.2. Review and submit the KCIJPUP1 job. Verify that the job ends with a 0 return



Option 8. Customizing PARMGEN configuration profiles1. From the Parameter Generator (PARMGEN) Workflow panel, select option 8 to

customize configuration profiles.2. Select option 1 to customize the RTE LPAR profile.3. The CONFIGURE_PRODUCTS section shows the products that are included or

excluded. Review the default settings and update them as necessary for yourinstallation.Make sure that you review and update the following information:v Type of monitoring server (remote)

This is controlled by the KDS_TEMS_TYPE parameter. This is set to REMOTE.For the NetView agent to connect to the monitoring server, make sure thatthe KNA_TEMS_LOCAL_CONNECT_FLAG parameter is set to Y and that theKNA_TEMS_TCP_HOST parameter is correct. In this example, BCHOST is the hostname.The monitoring server defined in this scenario is a remote monitoring server.Information for the hub monitoring server to which it connects is set by theparameters beginning with KDS_HUB. Verify or set the following parameters:


|

||

|||

|||

||

|

|

|||

|

||

|

|

||

||

||

|

|

|

|

||

|

|||

|

|

|

||||

|||

– KDS_HUB_TEMS_NAME_NODEID

In this scenario, HUBTEM21:CMS is the value for this parameter.– KDS_HUB_TCP_HOST

In this scenario, TIVLNX21 is the value for this parameter.– KDS_HUB_TCP_xxxxx_PORT_NUM where xxxxx corresponds to the

communications protocol (PIPE,UDP,PIPE6,UDP6,PIPES,PIPE6S) used tocontact the hub.In this scenario, IP.PIPE is used as the protocol and theKDS_HUB_TCP_PIPE_PORT_NUM parameter is set to 1918.

To define a backup monitoring server, use the parameters beginning withKNA_TEMS_BKUP1. Verify or set the following parameters– KNA_TEMS_BKUP1_NAME_NODEID

In this scenario, PCRTEM22:CMS is the value for this parameter.– KNA_TEMS_BKUP1_TCP_HOST

In this scenario, PCHOST is the value for this parameter.v Communications-related information (for example TCP addresses)

The addresses are assigned default values. Verify that the followingmonitoring server parameters are correct:– RTE_TCP_HOST– RTE_TCP_PORT_NUM– RTE_TCP_STC

Verify that the following NetView agent parameters are correct:– KNA_AGT_TCP_HOST– KNA_TCP_STC

Verify that the following parameters that control the communicationsprotocols used by the monitoring server and the NetView agent are correct:– KDS_TEMS_COMM_PROTOCOLn, where n is a value 1-7– KNA_AGT_COMM_PROTOCOLn, where n is a value 1-7– KDS_TEMS_TCP_xxxxx_PORT_NUM where xxxxx corresponds to the

communications protocol (PIPE,UDP,PIPE6,UDP6,PIPES,PIPE6S)– KNA_TEMS_TCP_xxxxx_PORT_NUM where xxxxx corresponds to the

communications protocol (PIPE,UDP,PIPE6,UDP6,PIPES,PIPE6S)In this scenario, IP.PIPE is used as the communication protocol. Set or verifythe following parameter values:– RTE_TCP_HOST - BCHOST– RTE_TCP_STC - #– RTE_TCP_PORT_NUM - 1918– KDS_TEMS_TCP_HOST - BCHOST– KDS_TEMS_TCP_STC - #– KDS_TEMS_COMM_PROTOCOL1 - IPPIPE– KDS_TEMS_TCP_PIPE_PORT_NUM - 1918– KNA_AGT_TCP_HOST - BCHOST– KNA_TCP_STC - #– KNA_TEMS_TCP_HOST - BCHOST– KNA_AGT_COMM_PROTOCOL1 - IPPIPE– KNA_AGT_TCP_PIPE_PORT_NUM - 1918Make sure that the KDS_TEMS_KLX_TCP_TOLERATERECYCLE andKNA_AGT_KLX_TCP_TOLERATERECYCLE parameters are set to Y. This enables themonitoring server and the NetView agent to reconnect to its TCP/IP stackwithout being recycled after the TCP/IP stack is recycled.

v PPI sender and receiver names


|

|

|

|

|||

||

||

|

|

|

|

|

|||||

|||

||

|

|

||

||

||||||||||||||

||||

|

Important: The KNA_PPISND_PPI_SENDER_CNMEMATX andKNA_PPIRCV_PPI_RECEIVER_CNMEMARX parameters control the PPI sender andreceiver names that are used by the NetView agent.

The receiver name is controlled by the KNA_PPIRCV_PPI_RECEIVER_CNMEMARXparameter. This name must match the DESTPPI receiver name that isspecified in the CNMSTYLE member or its include member. The defaultvalue is CNMEMARX.

The sender name is controlled by the KNA_PPISND_PPI_SENDER_CNMEMATXparameter. The default name is CNMEMATX. There is no matchingCNMSTYLE statement.

v Security settings to enable encryption for the monitoring serverv Security settings to enable take action command forwardingv Security settings to enable Take Action command forwarding.

System commands issued from the Tivoli Enterprise Portal using Take Actioncommands or situations run without command authorization or an audittrail. You can use the NetView product to perform command authorizationfor these system commands and to provide an audit trail.Command authorization for the Take Action system commands uses theportal user ID, which is sent to the NetView program with the command.The portal user ID that is sent is used to determine the user ID that issuesthe command. When a command is sent from a situation, the user ID that issent is the last one that edited the situation. Password validation is notperformed. If a NetView operator ID exists that matches the portal user IDand has the required command authorization, then the command is run onthe existing NetView operator ID. For more information about protectingMVS system commands, refer to the IBM Tivoli NetView for z/OS SecurityReference.Some agents provide their own Take Action commands, known as agentcommands. Agent commands have an associated two-character prefix fortheir product code. These commands are not sent to the NetView programfor command authorization. The only agent commands that are sent to theNetView program for authorization are the NetView agent commandsprefixed with NA. For information about creating or editing a Take Actioncommand, refer to the IBM Tivoli Monitoring: Tivoli Enterprise Portal User'sGuide.You can display Take Action commands and command responses in theNetView Command Response workspace. Additionally, you can display theBNH806I and BNH807I audit trail messages in the NetView Audit Logworkspace.Use the following parameters to enable command authorization checking forsystem commands sent from the hub monitoring server:– KDS_PPI_RECEIVER


– KDS_PPI_SENDER

Optional: Specify a value for the PPI sender. If you do not specify a value,the job name of the monitoring server is used when the command iswritten to the NetView log.

Equivalent parameters are available to enable command authorizationchecking for commands sent from the NetView agent:


|||

||||

|||

|

|

|

||||

||||||||||

||||||||

||||

||

|

|||

|

|||

||

– KNA_AGT_KGLHC_PPI_RECEIVER


– KNA_AGT_KGLHC_PPI_SENDER

Optional: Specify a value for the PPI sender.For definitions for the common parameters, see the IBM Tivoli OMEGAMONXE and Tivoli Management Services on z/OS: Parameter Reference. For NetViewagent definitions, see IBM Tivoli NetView for z/OS Installation: Configuring theNetView Enterprise Management Agent. For information about configuringsecurity settings for a monitoring server running in a z/OS environment, seeIBM Tivoli OMEGAMON XE and Tivoli Management Services: Configuring theTivoli Enterprise Monitoring Server on z/OS.

4. Press F3 to return to the menu panel.5. Select option 2 to review and specify global parameters. Review the default

settings and update them as necessary for your installation.

Usage notes:

v The global parameters define system data sets that include started taskprocedures, load modules, and configuration files. In many cases, the defaulthigh-level qualifier for the data set is SYS1. Review the global parametersstarting with the GLBL_DSN_SYS1 parameter and verify that the correct datasets are defined.

v The GBL_DSN_NETVIEW_CNMLINK parameter specifies the name of the NetViewCNMLINK data set. Review this parameter and make sure that the data setname is correct. In this scenario, NETVIEW.V6R2M0.CNMLINK is the value for thisparameter.

6. Press F3 to return to the menu panel.7. Select option 7 (WCONFIG). Locate the KNA$PENV member and edit it. Verify

that it contains the following statements:CTIRA_RECONNECT_WAIT = 60CTIRA_HEARTBEAT = 1

Add the following statements:KNA_ACTACT=YESCTIRA_PRIMARY_FALLBACK_INTERVAL=150

For more information about the CTIRA_ environment variables, see the IBMTivoli Monitoring: Installation and Setup Guide.

8. Press F3 to return to the menu panel.9. Press F3 again to return to Parameter Generator (PARMGEN) Workflow panel.

Option 9. KCIJPVAL Validating PARMGEN profile parametervalues1. From the Parameter Generator (PARMGEN) Workflow panel, select option 9 to

validate the profile parameter values.2. Review and submit the KCIJPVAL job. Verify that the job ends with a 0 return




|

|||

|

|

|||||||

|

||

|

|||||

||||

|

>>

>>

>

>>

>>

|

|

||

||

||

|

|

|

Option 10. Creating the RTE members and jobs1. From the Parameter Generator (PARMGEN) Workflow panel, select option 10 to

create the RTE members and jobs.2. Select option 1 to edit the composite $PARSE job.3. Review and submit the KCIJPPRS job. Verify that the job ends with a 0 return


4. Press F3 to display messages for the submitted job.5. Press Enter to return to the menu panel.6. Press F3 to return to the Parameter Generator (PARMGEN) Workflow panel.

Option 11. Submitting batch jobs to complete the PARMGENsetup1. From the Parameter Generator (PARMGEN) Workflow panel, select option 11

to submit batch jobs to complete the set up.2. Select option 1 to edit the composite master submit job.3. Review and submit the KCIJPSUB job. Verify that the jobs end with a 0 return

code. The KCIJPIVP job might end with return code of 4 because thecomposite master job did not run the conditional jobs.If a job does not end with the expected return code, correct the job andresubmit it.

4. Press F3 to display messages for the submitted job.5. Press Enter to return to the menu panel.6. Select option 2 to edit allocate runtime libraries.7. Review and submit the KCIJPALO job. Verify that the job ends with a 0 return



10. Select option 3 to load the TK* to RK* runtime libraries.11. Review and submit the KCIJPLOD job. Verify that the job ends with a 0 return


12. Press F3 to display messages for the submitted job.13. Press Enter to return to the menu panel.14. Select option 7 to edit the USS system setup job.15. Review and submit the KCIJPUSS job. Verify that the job ends with a 0 return


16. Press F3 to display messages for the submitted job.17. Press Enter to return to the menu panel.18. Select option 8 to edit the system setup job.19. Review and submit the KCIJPSYS job. Verify that the job ends with a 0 return




|

||

|

||

|

|

|

|

||

||

|

|||

||

|

|

|

||

|

|

|

|

||

|

|

|

|

||

|

|

|

|

||

|

|

|

22. Select option 11 to edit the WK* to RK* deployment job.23. Review and submit the KCIJPW2R job. Verify that the job ends with a 0 return


24. Press F3 to display messages for the submitted job.25. Press Enter to return to the menu panel.26. Select option 12 to edit the configuration verification job.27. Review and submit the KCIJPIVP job. Verify that the job ends with a 0 or 4

return code.If the job does not end with a 0 or 4 return code, correct the job and resubmitit. If the job ends with a 4 return code, examine the job output for the reason.

28. Press F3 to display messages for the submitted job.29. Press Enter to return to the menu panel.30. Press F3 to return to the Parameter Generator (PARMGEN) Workflow panel.31. Press F3 twice to exit the PARMGEN tool.

Loading the agent data files and configuring the portal serverFollow these procedures to load the NetView agent data files and to configure theportal server:v “Loading agent data files and configuring the portal server in a Windows

environment”v “Loading agent data files and configuring the portal server in the Linux and AIX

environments” on page 47

Loading agent data files and configuring the portal server in aWindows environment

The NetView agent data files are found on the IBM Tivoli NetView for z/OSEnterprise Management Agent data files CD. Do these steps to install the files.1. Log on to Windows using an ID with administrator authority.2. Close any running applications.3. Insert the Tivoli NetView for z/OS Enterprise Management Agent DVD into

your DVD drive.v Installation begins automatically.v If the installation process does not start, run setup.exe from the Windows

directory of the installation CD. If setup.exe initialization fails, you mightnot have enough free disk space to extract the setup files.

4. From the Tivoli NetView for z/OS Enterprise Management Agent installationWelcome window, click Next. The Install Prerequisites window is displayed.

5. From the Install Prerequisites window, click Next. The Software LicenseAgreement is displayed.

6. Read and accept the software license agreement. Click Accept to display theSelect Features window.

7. Under Tivoli Enterprise Monitoring Services, select Tivoli Enterprise PortalServer and TEP Desktop Client.

8. Click Next. The Start Copying Files window is displayed.9. Click Next. When the files have been copied, the Setup Type window is

displayed.


|

||

|

|

|

|

||

||

|

|

|

|

||

||||||

|

|

||

|

|

||

|

|||

||

||

||

||

|

||

10. Ensure that Install Application Support Files for a Local/Remove TivoliEnterprise Monitoring Server, Configure Tivoli Enterprise Portal andLaunch Manage Tivoli Enterprise Monitoring Services are selected, and thenclick Next.

11. In the remaining windows in the installation wizard, you are prompted toprovide information specific to your environment.

12. When the installation wizard is finished, the InstallShield Wizard Completewindow is displayed. Make sure that the Display the Readme file checkboxis selected. Click Finish to exit the wizard.

13. Review the readme file and then close the window.14. When the installation process completes, the Manage Tivoli Enterprise

Monitoring Services window is displayed.If the Manage Tivoli Enterprise Monitoring Services window is not displayed,you can open it by clicking Start > Programs > IBM Tivoli Monitoring>Manage Tivoli Monitoring Services.

15. If your hub Tivoli Enterprise Monitoring Server does not have theself-describing agent function enabled, you must manually add the applicationsupport to the hub monitoring server:a. Right-click Tivoli Enterprise Monitoring Server, select Advanced, then

select Add TEMS application support.b. In the Add Application Support to the TEMS dialog, select On a different

computer, then click OK.c. Click OK on the reminder window to ensure that the monitoring server is

configured and running.d. In the Non-Resident TEMS Connection dialog, enter the monitoring server

name in the TEMS Name field. Ensure that the IP.PIPE protocol and HubTEMS type are selected, then click OK.

e. In the next Non-Resident TEMS Connection dialog, enter the host name oraddress of the hub monitoring server, then click OK.

f. In the Select the Application Support to Add to the TEMS panel, select allinstances of the component. Ensure that the New Distribution List setting isselected, then click OK.

g. Review the results in the Application Support Addition Complete dialog toensure that the application support was successfully added to the hubmonitoring server.

h. Recycle the hub monitoring server.

Usage Note: Add the application support to both the primary and backuphub monitoring servers.

16. Review the portal server Status field. If the server is not already started,right-click Tivoli Enterprise Portal Server and then click Start.

17. To log on to Tivoli Enterprise Portal, right-click Tivoli Enterprise PortalBrowser and then click Start. The default user ID is sysadmin.

18. Verify that the Enterprise Status window is displayed.

Loading agent data files and configuring the portal server inthe Linux and AIX environments

To complete this process, the components on which you are to install support mustbe in the same directory structure as defined by the $install_dir environmentvariable or the value of the -h flag when using the install.sh installation script.


||||

||

|||

|

||

|||

|||

||

||

||

|||

||

|||

|||

|

||

||

||

|

|

|

|||

Do these steps to install the agent data files:1. Stop the portal server by entering the following command from the

$install_dir/bin directory:./itmcmd agent stop cq

2. Run the following command from the installation media:./install.sh -h $install_dir

$install_dir is the home directory for the IBM Tivoli Monitoring products.3. When you are prompted for the IBM Tivoli Monitoring home directory, do

one of the following steps:v Press Enter to accept the default directory (/opt/IBM/ITM).v Enter the full path to the installation directory that you used.

4. When you are prompted for an installation option, enter 1 as shown inFigure 10.

5. Review the license agreement and enter 1 to accept the terms of theagreement.

6. A list of currently installed products is displayed followed by a numbered listof categories for which product packages are available. Enter the number thatcorresponds to the Tivoli Enterprise Portal Browser Client support.

7. At the prompt, enter y to confirm the request.8. When the next list of the components to install is displayed, enter the number

that corresponds to the NetView for z/OS Enterprise Management Agent.9. At the prompt, enter y to confirm the installation. The installation begins.

10. Install the agent data files for each IBM Tivoli Monitoring component that ison the server. For example, you might want to load support for the TivoliEnterprise Portal server and client.a. Select the number corresponding to the component for which you want

support.b. At the prompt, enter 1 for Yes to confirm the request.c. Select the number corresponding to NetView for z/OS Enterprise

Management Agent.d. At the prompt, enter 1 for Yes to confirm the request.e. If you have additional components, enter 1 for Yes and repeat these steps

for the next component.11. After all of the components are installed, you are prompted whether you want

to install additional products or product support packages. Enter n.12. To configure the portal server with the new agent information, enter the

following command from the $install_dir/bin directory:./itmcmd config -A cq

Select one of the following:

1) Install products to the local host.2) Install products to depot for remote deployment (requires TEMS).3) Install TEMS support for remote seeding4) Exit install.

Please enter a valid number: 1

Figure 10. Installation option


||||||||||||

|

||

|

|

|

|

||

|

|

|||

||

|||

|

||

|

|||

||

|

||

|

||

||

||

|

13. Complete the configuration as prompted. For information about configuringthe Tivoli Enterprise Portal Server, see the IBM Tivoli Monitoring: Installationand Setup Guide.

14. If your hub monitoring server resides on a different server, and does not havethe self-describing agent function enabled, you must manually add theapplication support to the hub monitoring server:a. Start the Manage Tivoli Enterprise Monitoring Services application by

entering the following command from the $install_dir/bin directory:./itmcmd manage

Usage Note: The Manage Tivoli Enterprise Monitoring Services applicationrequires an X server.

b. On the Manage Tivoli Enterprise Monitoring Services window, selectActions, and then select Install Product Support.

c. In the Add TEMS Application Support dialog, select On a differentcomputer, then click OK.

d. Click OK on the reminder window to ensure that the monitoring server isconfigured and running.

e. In the Non-Resident TEMS Connection dialog, enter the monitoring servername in the TEMS Name field. Ensure that the IP.PIPE protocol and HubTEMS type are selected, then click OK.

f. In the next Non-Resident TEMS Connection dialog, enter the host name orIP address of the hub monitoring server, then click OK.

g. In the Install Product Support dialog, select all instances of the component.Make sure that the NONE option is selected, then click INSTALL.

h. Review the results in the Messages section of the Manage Tivoli EnterpriseMonitoring Services window to ensure that the application support wassuccessfully added to the hub monitoring server.

i. Recycle the hub monitoring server.


15. Start the portal server from your UNIX or Linux command window.16. To log on to Tivoli Enterprise Portal, follow these steps:

a. On Windows computer, open a browser window.b. Enter the following web address:

http://hostname:1920

where hostname is the host name or IP address of the portal server todisplay the service index.

c. Click on the IBM Tivoli Enterprise Portal Web Client entry to display thelogon window.

d. Enter your user ID and password.The default user ID is sysadmin.



|||

|||

||

|

||

||

||

||

|||

||

||

|||

|

||

|

|

|

|

|

||

||

|

|

|

Historical data collection and reportingSome of the workspaces for the GDPS Active/Active Continuous Availabilitysolution support historical data collection. For information about configuringhistorical data collection, see IBM Tivoli NetView for z/OS Installation: Configuring theNetView Enterprise Management Agent and the IBM Tivoli Monitoring: Tivoli EnterprisePortal User's Guide.

The NetView agent provides predefined historical reports at the Tivoli EnterprisePortal. For information on predefined historical reports for the solution that areavailable from the portal, see IBM Tivoli NetView for z/OS Installation: Configuringthe NetView Enterprise Management Agent.

Creating a custom navigator viewThe Tivoli Enterprise Portal displays physical and custom navigator views. TheNavigator physical view (default view) shows the enterprise as a physical mappingof platforms, systems, agents, and monitored resources. A custom navigator viewcan be created to show a logical hierarchy. For example, a custom navigator viewcan represent the enterprise, sites, workloads, and other managed resources.

To create a custom navigator view that displays the GDPS Active/ActiveContinuous Availability solution workspaces, follow these steps:1. Log on to the Tivoli Enterprise Portal client with a user ID that has Modify

permission for the Custom Navigator Views feature.

2. In the Navigator toolbar, click the Edit Navigator View icon ( ). The EditView window is displayed as shown in Figure 11.

Notice in the right panel that the Navigator physical view is the source view.The custom navigator view or the most recently opened navigator view is thetarget view in the left panel.

3. To edit the target view, click the Create New Navigator View icon ( ). TheCreate New Navigator View window is displayed as shown in Figure 12 onpage 51.

Figure 11. Edit View window


|

|||

||

|||||

||||

||

|||||

||

||

|||

|||

||||

4. Enter the Navigator View Identity (for example, My Active/Active Sites) andoptionally the description, and click OK. The Navigator view name isdisplayed as Enterprise in Figure 13.

If you receive a duplicate names message that the name exists, enter adifferent name. Because Navigator views are assigned to user IDs, you mightnot be able to see Navigator views that other users created.

5. To assign managed systems to a Navigator item, right-click the MyActive/Active Sites item, and click Properties. The Navigator Item Propertieswindow is displayed as shown in Figure 14 on page 52.

Figure 12. Create New Navigator View window

Figure 13. Edit Navigator View window with new view name


|

|||

|

|||

||||

|||

||||

6. To assign managed system groups to the Navigator item as dynamic members(child items), click the Dynamic items tab. When managed systems are addedor removed from the managed system groups, the Navigator item and theitems that it contains are updated automatically. Notice in Figure 14 thatAvailable Members displays the managed system groups that can be assignedas dynamic members of the Navigator item.

7. To add a managed system group for the GDPS Active/Active ContinuousAvailability solution, select *ZNETVIEW_ACTIVEACTIVE in the Available

Members list and click the Left Arrow icon ( ). The updates are shownin Figure 15 on page 53.

Figure 14. Navigator Item Properties window


|

|||||||||

||

|||

8. Click the Options icon ( ) to display the Assigned member options window.9. Customize the view by assigning member options to filter out branch-level or

host-level items from the view. To assign member options, check Includeattribute-level items of managed systems as shown in Figure 16.

10. Click OK to exit the Assigned member options window.11. Click OK to exit the Navigator Item Properties window.12. Click Close to exit the Edit Navigator View window.

13. Click the Navigator update pending icon ( ) in the Navigator toolbar torefresh the Navigator view.

14. Click the My Active/Active Sites view from the list of available Navigatorviews as shown in Figure 17 on page 54.

Figure 15. Navigator Item Properties window (assigned members)

Figure 16. Assigned member options


|

|||

|

|||

|

||||

|

|

|

||

|||

The customized navigator view is displayed as shown in Figure 18.

Figure 17. List of available Navigator views

Figure 18. Customized Navigator view for My Active/Active Sites


|

|||

|

|||

||

Chapter 5. Monitoring and controlling data

To monitor and control the data that is being collected by the GDPS Active/ActiveContinuous Availability solution, follow these procedures:v “Starting data collection”v “Displaying data collection statistics”v “Changing the sampling interval” on page 56v “Stopping data collection” on page 57v “Monitoring data using 3270 commands” on page 57

Starting data collectionTo start data collection for Lifeline Advisor monitoring or Replication monitoring,ensure that the CNMSTYLE statements are updated for the ACTIVEACTIVE tower,and the Lifeline Advisor monitoring or the Replication monitoring subtowers. Forinformation on updating the CNMSTYLE statements, see “Updating configurationstatements” on page 8.

Data collection will be started automatically at NetView initialization or when thedata collection interface becomes active. See the AQNSACTA automation samplefor details.

Lifeline Advisor monitoring dataTo start Lifeline Advisor data collection, enter the following command from theNetView console:ACTVCTL START=LIFELINE

Replication monitoring dataTo start replication monitoring data collection, follow one or more of these stepsdepending on the type of data that you are collecting:v To start Q replication data collection, enter the following command from the

NetView console:ACTVCTL START=DB2

v To start IMS replication data collection, enter the following command from theNetView console:ACTVCTL START=IMS

v To start VSAM replication data collection, enter the following command from theNetView console:ACTVCTL START=VSAM

Displaying data collection statisticsUse the ACTVCTL command to determine the following information about GDPSActive/Active Continuous Availability solution data collection:v Data that is being collectedv The average and maximum collection timev How many collections occurred


|

|

||

|

||

|

To display data collection statistics for all the Active/Active data collectors, enterthe following command:ACTVCTL LISTINFO=ALL

You can also display data collection information for the individual data collectors:v Workload Lifeline Advisorv Q replicationv IMS replicationv VSAM replication

For more information about the ACTVCTL LISTINFO command, see “ACTVCTL(NCCF)” on page 101.

Changing the sampling intervalYou can change the sampling interval by updating CNMSTYLE statements andthen using the RESTYLE command, or by using the ACTVCTL command.

Updates made with the RESTYLE command occur when the current interval ends.Use the ACTVCTL command for instantaneous changes for data collection. Theinterval returns to the configured value if data collection is stopped and restarted.

CNMSTYLE statementsTo change the sampling interval for Lifeline Advisor monitoring:1. Update the ACTACT.LIFEINT statement in the CNMSTLIF member. For

information on how to update the CNMSTYLE statements, see “Collectingdata” on page 10.

2. From the NetView console, enter the following command :RESTYLE ACTACT

To change the sampling interval for Replication monitoring:1. Update one or more of the following statements, depending on the type of data

that you are collecting:v For Q replication data, update the ACTACT.DB2INT statement in the

CNMSTREP member.v For IMS replication data, update the ACTACT.IMSINT statement in the

CNMSTREP member.v For VSAM replication data, update the ACTACT.VSAMINT statement in the

CNMSTREP member.

For information about updating CNMSTYLE statements, see “Collecting data”on page 17.

2. Enter the following command from the NetView console:RESTYLE ACTACT

ACTVCTL commandYou can use the ACTVCTL command to dynamically reset the sampling intervalfor Active/Active data collectors. For example, to reset the sampling interval to 10seconds for all the Active/Active data collectors, enter the following command:ACTVCTL RESET=ALL,INTERVAL=10

You can also reset the sampling interval for the individual data collectors:


|

|

||

v Workload Lifeline Advisorv Q replicationv IMS replicationv VSAM replication

For more information about the ACTVCTL command, see “ACTVCTL (NCCF)” onpage 101.

Stopping data collectionYou can manually stop data collection for Lifeline Advisor or Replication data.

Lifeline Advisor monitoring dataTo stop the collection of all Lifeline Advisor monitoring data, enter the followingcommand from the NetView console:ACTVCTL STOP=LIFELINE

Replication monitoring dataTo stop the collection of all replication monitoring data, enter the followingcommand from the NetView console:ACTVCTL STOP=(DB2,IMS,VSAM)

The ACTVCTL STOP command can also be issued for individual replicationsubtowers. For more information on the ACTVCTL command, see “ACTVCTL(NCCF)” on page 101.

Monitoring data using 3270 commandsTo retrieve Lifeline Advisor or replication monitoring data immediately, you canissue the following commands from the enterprise master NetView program:v ACTVLIFEv ACTVREPL

You must use the INTERVAL keyword to receive valid data.

Chapter 5. Monitoring and controlling data 57

|

|

|

|


Chapter 6. Automating EIF events

The replication products in the GDPS Active/Active Continuous Availabilitysolution use the Event Integration Facility (EIF) to send events to an event receiver.You can use the NetView Event/Automation Service (E/AS) to convert theseevents into NMVT formatted alerts. The converted alerts are then forwarded to theNetView hardware monitor where they are filtered and routed to the NetViewautomation table.

Using automation, the NetView program processes the alerts and sendsinformation to the Lifeline Advisor component of the Multi-site Workload Lifelineproduct and to the GDPS/Active-Active offering. The NetView product also filtershardware monitor logging of the AA_replication_heartbeat alert when the latencystate attribute value is Unknown or Normal.

To automate EIF events and modify hardware monitor filters, follow theseprocedures:v “Understanding which events are processed”v “Adding additional automation for hardware monitor alerts” on page 60

For example, you might want to forward information from the events to anevent console.

v “Modifying hardware monitor logging filters” on page 61

Understanding which events are processedInformation from the following events is forwarded to the Lifeline Advisor forActive/Query workloads:v AA_replication_reset_average_latency_metv AA_replication_critical_average_latency_exceededv AA_replication_constrained_average_latency_exceededv AA_replication_critical_average_latency_exceededv AA_replication_max_latency_exceededv AA_replication_heartbeatv AA_replication_workload_down

Information from the following events is forwarded to GDPS for Active/Standbyand Active/Query workloads:v AA_replication_reset_average_latency_metv AA_replication_max_latency_exceededv AA_replication_heartbeatv AA_replication_workload_upv AA_replication_workload_down

An additional event, AA_replication_discrete_latency, is sent by the replicationproducts. The alert that is generated for this event is not forwarded to othercomponents in the GDPS Active/Active Continuous Availability solution.


|

|

||||||

|||||

||

|

|

||

|

||

||

|

|

|

|

|

|

|

||

|

|

|

|

|

|||

Adding additional automation for hardware monitor alertsHardware monitor alerts are automated using the NetView MSUSEG automationfunction. Depending on the type of additional automation that you might want toenable, review the contents of subvector 31 that is generated for GDPSActive/Active Continuous Availability solution alerts.

Table 13 displays the required attributes in GDPS Active/Active ContinuousAvailability solution-generated alerts, including their subvector 31 number that isused with the MSUSEG automation function. The position for each attribute doesnot change

Table 13. Required attributes

Subvector 31number Attribute name

1 event name that starts with AA_

2 version

3 sysplex_name

4 system_name

5 job_name

6 data_source

7 workload_name

8 consistency_group

9 consistency_group_total

10 workload_type

11 latency_state

12 apply_latency_time

13 point_in_time_consistency

14 time_stamp

15 msg

16 severity

17 reserved01

18 reserved02

19 reserved03

20 reserved04

21 reserved05

22 and beyond optional attributes per replication product

For more information on the MSUSEG automation function, see the IBM TivoliNetView for z/OS Automation Guide.

For more information on the solution-generated alerts, see the appropriatereplication product documentation.


||

||||

||||

||

|||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

|||

||

||

Modifying hardware monitor logging filtersTo prevent excessive logging of GDPS Active/Active Continuous Availabilitysolution-alerts to the hardware monitor database, the NetView AQNSACTAautomation sample contains logic to prevent logging of specific alerts underspecified conditions. The following automation statements in the AQNSACTAsample prevents AA_replication_heartbeat alerts from being logged if thelatency_state attribute value is Unknown or Normal:IF (MSUSEG(0000.05.10 5) = HEX(’C1D8D5C5C1E2’) .) &

(ATF(’DSICGLOB AQNACT.ADVJOB’) ¬= ’’) THENBEGIN;IF (MSUSEG(0000.31(1).30 3) = ’AA_replication_heartbeat’ . ) &

((MSUSEG(0000.31(11).30 17) = ’Normal;’ . ) |(MSUSEG(0000.31(11).30 17) = ’Unknown;’ .)) THEN

SRF (ESREC BLOCK) CONTINUE(Y);ALWAYS

EXEC(CMD(’AQNEEVNT’) ROUTE(ONE ?ACTTSKEV))CONTINUE(N);

END;

You can change this automation as required for your installation. For examples, see“Example: Preventing an alert from being logged” and “Example: Logging specificalerts.”

Example: Preventing an alert from being logged

Th following automation example prevents an alert from being logged in thehardware monitor database if the latency_state attribute value is Unknown or Normaland the workload_name attribute is TELNET23Q.IF (MSUSEG(0000.05.10 5) = HEX(’C1D8D5C5C1E2’) .) &


((MSUSEG(0000.31(11).30 17) = ’Normal;’ . ) |(MSUSEG(0000.31(11).30 17) = ’Unknown;’ .)) &(MSUSEG(0000.31(7).30 17) = ’TELNET23Q’ .) THEN



END;

Example: Logging specific alerts

Th following automation example logs the first two alerts in a 24-hour period inthe hardware monitor database if the latency_state attribute value is Unknown orNormal and the workload_name attribute is TELNET23Q.IF (MSUSEG(0000.05.10 5) = HEX(’C1D8D5C5C1E2’) .) &


((MSUSEG(0000.31(11).30 17) = ’Normal;’ . ) |(MSUSEG(0000.31(11).30 17) = ’Unknown;’ .)) &(MSUSEG(0000.31(7).30 17) = ’TELNET23Q’ .) &THRESHOLD(3) = ’1’ THEN



END;

Chapter 6. Automating EIF events 61

||

||||||

|||||||||||

|||

|

|||

||||||||||||

|

|||

|||||||||||||

For more information about the THRESHOLD automation function, see the IBMTivoli NetView for z/OS Automation Guide.


||

Chapter 7. Switching solution components on controllersystems

A planned or unplanned outage on the primary controller can cause key GDPSActive/Active Continuous Availability solution components to move to the backupcontroller. This allows for seamless control and monitoring of production systems.Movement of key components is usually managed by the GDPS/Active-Activecomponent through its control and automation facilities. This chapter explains themovement of NetView functions and requisite IBM Tivoli Monitoring componentswhen the GDPS/Active-Active component detects that controller components needto move to the backup controller. This chapter also provides manual instructionsfor returning components to their proper state on the primary controller.

Usage notes:

1. The GDPS/Active-Active component issues one of the following commandswhen it successfully moves the Lifeline Advisor component of the Multi-siteWorkload Lifeline product to the backup controller:v ACTVCTL TAKEOVER ENABLE = (NVAGT)v ACTVCTL TAKEOVER ENABLE = (TEMS,NVAGT)

2. If you manually issue the ACTVCTL TAKEOVER command, you can causeunintended results for the GDPS Active/Active Continuous Availabilitysolution.

Moving the NetView program and IBM Tivoli Monitoring components tothe backup controller

“Moving the Active/Active enterprise master NetView program” explains themovement of the NetView program to the backup controller.

“Controller switch when running remote monitoring servers” on page 64 explainsstarting the IBM Tivoli Monitoring components on the backup controller.

Moving the Active/Active enterprise master NetView programThe Active/Active enterprise master NetView program is the control point formonitoring information for the GDPS Active/Active Continuous Availabilitysolution. To provide this information, the Active/Active enterprise master NetViewprogram runs where the primary Lifeline Advisor component of the Multi-siteWorkload Lifeline product runs. When the primary Lifeline Advisor componentmoves to the backup controller, the NetView program on the backup controllerbecomes the Active/Active enterprise master NetView program.

The ACTVCTL TAKEOVER command moves the Active/Active enterprise masterNetView program to the system on which the ACTVCTL TAKEOVER command isissued. If the takeover is successful, all of the systems that were previously part ofthe scope for the old enterprise master are now part of the scope for the newenterprise master. You can verify this by issuing the following command:LIST STATUS=XCFGRPS


>>

After the takeover, Lifeline Advisor, and replication monitoring data flow to thenew Active/Active enterprise master NetView program. ACTVLIFE andACTVREPL commands can also be issued from this enterprise master.

The ENABLE keyword on the ACTVCTL TAKEOVER command specifies whetherto start the monitoring server, the NetView agent, or both. Configuration settingsin your CNMSTYLE member determine whether any action is taken on the newActive/Active enterprise master NetView program. For more information, see“Controller switch when running remote monitoring servers.”

Usage notes:

1. When an Active/Active enterprise master takeover completes successfully, theNetView program on the primary controller does not automatically become theActive/Active enterprise master during NetView initialization, even though itis configured to be the enterprise master. You must issue the ACTVCTLTAKEOVER command to return the NetView program on the primarycontroller to the Active/Active enterprise master role.

2. If the NetView program becomes inactive on the backup controller after itbecame the Active/Active enterprise master, the NetView program will notinitialize as the Active/Active enterprise master. In this case, change the role ofthe NetView program to that of the enterprise master by issuing the ACTVCTLTAKEOVER command.

Controller switch when running remote monitoring serversThis section is not applicable if the remote monitoring server does not run on astandalone controller system.

When running remote monitoring servers on the controller systems, the remotemonitoring server must always be active on both controller systems. For controllerswitch scenarios with this configuration, there is no movement of the monitoringservers. If the NetView agent's connection to the local remote monitoring serverfails, the NetView agent switches its connection to the alternate controller's remotemonitoring server.

To accomplish this, configure the EMAAUTO.TEMS.procStr and EMAAUTO.TEMA.procStrstatements in the CNMSTYLE member to ensure that monitoring continues.

The process to switch the enterprise master NetView program and monitoring tothe backup controller is started when the GDPS/Active-Active component issuesthe following command:ACTVCTL TAKEOVER ENABLE=(TEMS,NVAGT)

If the remote monitoring server or NetView agent were not started on the backupcontroller, then they are started as a result of the ACTVCTL TAKEOVER command.

Manually returning components to the primary controllerTo return the components to their original state on the primary controller after anoutage is resolved, you can:v Select Change Master on the GDPS/Active-Active Web Interface Controllers

panel.v Issue commands manually.


>

>>

>

>

>>>>>>

>>

>>

Change Master operationsWhen you select Change Master on the GDPS/Active-Active Web InterfaceControllers panel, the following NetView and IBM Tivoli Monitoring operations areperformed:1. The NetView role changes to Active/Active enterprise master.2. The remote monitoring server and NetView agent start as a result of the

EMAAUTO configuration statements or as a result of the ACTVCTLTAKEOVER ENABLE=(NVAGT,TEMS) command that is issued by theGDPS/Active-Active component as part of the Change Master operation.

Commands to return components to the primary controllerTo move NetView and IBM Tivoli Monitoring components back to the primarycontroller manually, issue the following commands:1. Change the NetView role to the Active/Active enterprise master:

ACTVCTL TAKEOVER

2. Start the monitoring server and the NetView agent on the primary controller byissuing either the following ACTVCTL TAKEOVER command or both of thefollowing START commands:v ACTVCTL TAKEOVER ENABLE=(NVAGT,TEMS)v START monitoring_server_procv START NetView_agent_proc

Chapter 7. Switching solution components on controller systems 65

>>>>>>


Appendix A. CNMSTYLE statements

NetView initialization statements are defined in the CNMSTYLE member in theDSIPARM data set. To modify a CNMSTYLE statement, copy the statement toeither the CNMSTUSR or CxxSTGEN member and then make any necessaryupdates. For more information about NetView initialization and updatingCNMSTYLE statements, see IBM Tivoli NetView for z/OS Installation: Getting Started.

ACTACT.BKTEMS.EnablePurpose

The ACTACT.BKTEMS.Enable statement is deprecated.

The ACTACT.BKTEMS.Enable statements specifies that you want the NetViewprogram to start a Tivoli Enterprise Monitoring Server (monitoring server) on thebackup controller when there is an outage on the primary controller.

Before the NetView program starts the monitoring server on the backup controller,you are prompted to indicate whether the monitoring server on the primarycontroller is inactive. If the monitoring server on the primary controller is activeand the Tivoli Enterprise Portal Server (portal server) has an existing connection toit, the portal server cannot connect to the monitoring server on the backupcontroller.

Syntax

The ACTACT.BKTEMS.Enable statement has the following syntax:

ACTACT.BKTEMS.Enable

►►ACTACT.BKTEMS.Enable = No

ACTACT.BKTEMS.Enable = Yes►◄

where:

No Indicates not to process the ACTACT.BKTEMS.procStr statement. This is theinitial setting in the CNMSTYLE member.

YesIndicates to process the ACTACT.BKTEMS.procStr statement.

Usage notesv Specify the ACTACT.BKTEMS.Enable statement only if you are implementing

the GDPS Active/Active Continuous Availability solution and your monitoringserver is on a stand-alone system.

v If the monitoring server is active on both the primary and backup controllerssimultaneously, results can be unpredictable.

v To implement definition changes while the NetView program is active, changethe value in the CNMSTUSR or CxxSTGEN member, and enter the RESTYLE


>

ACTACT command. For more information about changing CNMSTYLEstatements, see IBM Tivoli NetView for z/OS Installation: Getting Started.

ACTACT.BKTEMS.procStrPurpose

The ACTACT.BKTEMS.procStr statement is deprecated.

The ACTACT.BKTEMS.procStr statement specifies the Tivoli Enterprise MonitoringServer (monitoring server) startup procedure name and startup parameters to beused when the monitoring server is started on the backup controller.

Syntax

The ACTACT.BKTEMS.procStr statement has the following syntax:

ACTACT.BKTEMS.procStr

►► ACTACT.BKTEMS.procStr = procedure_cmdstr*NONE*

►◄

where:

procedure_cmdstrSpecifies the startup procedure and startup parameters.

*NONE*Specifies no startup procedure name. This is the initial setting.

Usage notesv Specify the ACTACT.BKTEMS.procStr statement only if you are implementing

the GDPS Active/Active Continuous Availability solution.v The ACTACT.BKTEMS.Enable statement must be set to Yes for the

ACTACT.BKTEMS.procStr statement to be processed.v To implement definition changes while the NetView program is active, change

the value in the CNMSTUSR or CxxSTGEN member, and enter the RESTYLEACTACT command. For more information about changing CNMSTYLEstatements, see IBM Tivoli NetView for z/OS Installation: Getting Started.

ACTACT.PriCont.SystemPurpose

The ACTACT.PriCont.System statement is deprecated.

The ACTACT.PriCont.System statement specifies the system name of the primarycontroller. This information is used in the prompt if the ACTACT.BKTEMS.Enablestatement is set to Yes.

Syntax

The ACTACT.PriCont.System statement has the following syntax:


>

>

ACTACT.PriCont.System

►► ACTACT.PriCont.System = system_name ►◄

where:

system_nameSpecifies the z/OS image name of the primary controller.

Usage notesv Specify the ACTACT.PriCont.System statement only if you are implementing the

GDPS Active/Active Continuous Availability solution.v To process the ACTACT.PriCont.System statement, set the

ACTACT.BKTEMS.Enable statement to Yes.v To implement definition changes while the NetView program is active, change


ACTACT.DB2INTPurpose

The ACTACT.DB2INT statement specifies how often data is collected from the Qreplication servers.

Syntax

The ACTACT.DB2INT statement has the following syntax:

ACTACT.DB2INT

►►ACTACT.DB2INT=30

ACTACT.DB2INT=seconds►◄

where:

secondsSpecifies the data collection interval. The valid range is 10 - 43200 seconds. Thedefault value is 30 seconds.

Usage notesv Specify the ACTACT.DB2INT statement only if you are implementing the GDPS

Active/Active Continuous Availability solution.v To implement definition changes while the NetView program is active, change


Appendix A. CNMSTYLE statements 69

||

ACTACT.DB2PATH.APPxPurpose

The ACTACT.DB2PATH.APPx statement specifies the apply server socket pathnames for Q replication data collection.

Syntax

The ACTACT.DB2PATH.APPx statement has the following syntax:

ACTACT.DB2PATH.APPx

►►ACTACT.DB2PATH.APPx=path

►◄

where:

pathSpecifies the socket path name for the apply server.

The path name must match the name that Q replication uses. For additionalinformation about the socket path name, see the Q replication product library.

x Specifies the statement number: 1 - 50. This value must be incrementedsequentially.

Usage notesv Specify the ACTACT.DB2PATH.APPx statement only if you are implementing

the GDPS Active/Active Continuous Availability solution.v You can define connectivity to multiple replication servers for each LPAR. If you

specify more than one socket path definition for capture servers, increment xsequentially. If the socket path definitions are not defined sequentially, theACTVREPL command will fail for this replication server. Data in the TivoliEnterprise Portal will be displayed correctly.

v To implement definition changes while the NetView program is active, changethe value in the CNMSTUSR or CxxSTGEN member, and enter the RESTYLEACTACT command. For more information about changing CNMSTYLEstatements, see IBM Tivoli NetView for z/OS Installation: Getting Started.

ACTACT.DB2PATH.CAPxPurpose

The ACTACT.DB2PATH.CAPx statement specifies the capture server socket pathnames for Q replication data collection.

Syntax

The ACTACT.DB2PATH.CAPx statement has the following syntax:

ACTACT.DB2PATH.CAPx

►►ACTACT.DB2PATH.CAPx=path

►◄


||

||

||

||

where:

pathSpecifies the socket path name for the capture server.

The path name must match the name that Q replication uses. For additionalinformation about the socket path name, see the Q replication product library.

x Specifies the statement number: 1 - 50. This value must be incrementedsequentially.

Usage notesv Specify the ACTACT.DB2PATH.CAPx statement only if you are implementing




ACTACT.IMSINTPurpose

The ACTACT.IMSINT statement specifies how often data is collected from the IMSreplication servers.

Syntax

The ACTACT.IMSINT statement has the following syntax:

ACTACT.IMSINT

►►ACTACT.IMSINT=30

ACTACT.IMSINT=seconds►◄

where:


Usage notesv Specify the ACTACT.IMSINT statement only if you are implementing the GDPS




||

||

||

ACTACT.IMSPATH.APPxPurpose

The ACTACT.IMSPATH.APPx statement specifies the apply server socket pathnames for IMS replication data collection.

Syntax

The ACTACT.IMSPATH.APPx statement has the following syntax:

ACTACT.IMSPATH.APPx

►►ACTACT.IMSPATH.APPx=path

►◄

where:

pathSpecifies the socket path name for the apply server.

The path name must match the IMS replication server part of theNMICOMMSTRING statement that is configured to the MonitoringAdministration Agent (MAA) service. Configure the portion of theNMICOMMSTRING statement that starts with /var/sock to match theNetView socket path definition value. For example, IMS replication specifiesthe following statement:NMICOMMSTRING=’/var/sock/IMSREPabc’

Configure /var/sock/IMSREPabc for the NetView socket path definition value.For more information about the NMICOMMSTRING statement, see the IMSreplication product library.

x Specifies the statement number: 1- 50. This value must be incrementedsequentially.

Usage notesv Specify the ACTACT.IMSPATH.APPx statement only if you are implementing the

GDPS Active/Active Continuous Availability solution.v You can define connectivity to multiple replication servers for each LPAR. If you



ACTACT.IMSPATH.CAPxPurpose

The ACTACT.IMSPATH.CAPx statement specifies the capture server socket pathnames for IMS replication data collection.


||

||||||

|

|||

||

||

Syntax

The ACTACT.IMSPATH.CAPx statement has the following syntax:

ACTACT.IMSPATH.CAPx

►►ACTACT.IMSPATH.CAPx=path

►◄

where:


The path name must match the IMS replication server part of theNMICOMMSTRING statement that is configured to the MonitoringAdministration Agent (MAA) service. Configure the portion of theNMICOMMSTRING statement that starts with /var/sock to match theNetView socket path definition value. For example, IMS replication specifiesthe following statement:NMICOMMSTRING=’/var/sock/IMSREPabc’

Configure /var/sock/IMSREPabc for the NetView socket path definition value.For more information about the NMICOMMSTRING statement, see the IMSreplication product library.

x Specifies the statement number: 1- 50. This value must be incrementedsequentially.

Usage notesv Specify the ACTACT.IMSPATH.CAPx statement only if you are implementing



v To implement definition changes while the NetView program is active, changethe value in the CNMSTUSR orCxxSTGEN member, and enter the RESTYLEACTACT command. For more information about changing CNMSTYLEstatements, see IBM Tivoli NetView for z/OS Installation: Getting Started.

ACTACT.LIFEINTPurpose

The ACTACT.LIFEINT statement specifies how often data is collected from theLifeline Advisor.

Syntax

The ACTACT.LIFEINT statement has the following syntax:


||||||

|

|||

ACTACT.LIFEINT

►►ACTACT.LIFEINT=10

ACTACT.LIFEINT=seconds►◄

where:


Usage notesv Specify the ACTACT.LIFEINT statement only if you are implementing the GDPS



ACTACT.MASTER.DELAYPurpose

The ACTACT.MASTER.DELAY statement defines a delta interval in addition to thedata collection sample interval that is used to determine whether replication datasent to the controller system is current.

When the modified sampling interval elapses on the controller system without thecontroller system receiving updated replication data, the controller systemconsiders the data from the production system to not be current. Data that is notcurrent causes workload aggregate data to be flagged as inaccurate. The value isused to compensate for network response time and internal NetView programprocessing.

This statement is applicable to NetView programs on controller systems in the IBMTivoli NetView for z/OS Installation: Configuring the GDPS Active/ActiveContinuous Availability Solution.

Syntax

The ACTACT.MASTER.DELAY statement has the following syntax:

ACTACT.MASTER.DELAY

►►ACTACT.MASTER.DELAY = 3

ACTACT.MASTER.DELAY = elapse_time►◄

where:

elapse_timeSpecifies the number of seconds to add to the sampling interval on productionsystems. The value must be between 3 and 60 seconds, The default value is 3seconds.


|

|

|||

||||||

>>>

|

|

|

|||||||||||||||

|

|

||||

Usage notesv Specify the ACTACT.MASTER.DELAY statement only if you are implementing

the GDPS Active/Active Continuous Availability solution.v To implement definition changes while the NetView program is active, change


ACTACT.VSAMINTPurpose

The ACTACT.VSAMINT statement specifies how often data is collected from theVSAM replication servers.

Syntax

The ACTACT.VSAMINT statement has the following syntax:

ACTACT.VSAMINT

►►ACTACT.VSAMINT=30

ACTACT.VSAMINT=seconds►◄

where:


Usage notesv Specify the ACTACT.VSAMINT statement only if you are implementing the

GDPS Active/Active Continuous Availability solution.v To implement definition changes while the NetView program is active, change


ACTACT.VSAMPATH.APPxPurpose

The ACTACT.VSAMPATH.APPx statement specifies the apply server socket pathnames for VSAM replication data collection.

Syntax

The ACTACT.VSAMPATH.APPx statement has the following syntax:

ACTACT.VSAMPATH.APPx

►►ACTACT.VSAMPATH.APPx=path

►◄


|

||

||||

||

|

||

|

|

|

|||||||||||||||

|

|

|||

|

||

||||

||

|

||

|

|

|

||||||||||||

|

where:

pathSpecifies the socket path name for the apply server. The path name is casesensitive.

The path name must match the VSAM replication server part of theNMICOMMSTRING statement that is configured to the MonitoringAdministration Agent (MAA) service. Configure the portion of theNMICOMMSTRING statement that starts with /var/sock to match theNetView socket path definition value. For example, VSAM replication specifiesthe following statement:NMICOMMSTRING=’/var/sock/VSAMREPabc’

Configure /var/sock/VSAMREPabc for the NetView socket path definition value.For more information about the NMICOMMSTRING statement, see the VSAMreplication product library.

x Specifies the statement number: 1 - 50. Increment this value sequentially.

Usage notesv Specify the ACTACT.VSAMPATH.APPx statement only if you are implementing




ACTACT.VSAMPATH.CAPxPurpose

The ACTACT.VSAMPATH.CAPx statement specifies the capture server socket pathnames for VSAM replication data collection.

Syntax

The ACTACT.VSAMPATH.CAPx statement has the following syntax:

ACTACT.VSAMPATH.CAPx

►►ACTACT.VSAMPATH.CAPx=path

►◄

where:


The path name must match the VSAM replication server part of theNMICOMMSTRING statement that is configured to the MonitoringAdministration Agent (MAA) service. Configure the portion of the


|

|||

||||||

|

|||

||

|

||

|||||

||||

||

|

||

|

|

|

||||||||||||

|

|

||

|||

NMICOMMSTRING statement that starts with /var/sock to match theNetView socket path definition value. For example, VSAM replication specifiesthe following statement:NMICOMMSTRING=’/var/sock/VSAMREPabc’

Configure /var/sock/VSAMREPabc for the NetView socket path definition value.For more information about the NMICOMMSTRING statement, see the VSAMreplication product library.

x Specifies the statement number: 1 - 50. Increment this value sequentially.

Usage notesv Specify the ACTACT.VSAMPATH.CAPx statement only if you are implementing




AUTOTASKPurpose

The AUTOTASK statement is used to start an automated operator and optionallyto associate an MVS console with this automated operator.

Syntax

The AUTOTASK statement has the following syntax:

AUTOTASK

►► AUTOTASK . autotask_name . Console=console_nameInitCmd=command

►◄

where:

autotask_nameIs the autotask name.

ConsoleSpecifies the MVS console name that is to be associated with the autotask.

console_nameSpecifies a 2 - 8 character console name. You can also specify thefollowing values:

*INTERN*You can use CONSOLE=*INTERN* to assign an autotask torespond to commands from the INTERNAL console.


|||

|

|||

||

|

||

|||||

||||

|

*ANY*Assigns an autotask to respond to commands from any consolenot otherwise assigned to an autotask.

*MASTER*Use the *MASTER* value to assign an autotask to respond tocommands from any console with master authority nototherwise assigned to an autotask. Use this value if you are notusing the *ANY* value or if you want consoles that have masterauthority to use a different autotask from consoles that haveless authority.

*NONE*Does not assign a console to be associated with the autotask.

InitCmdSpecifies the initial command to be used when the autotask is started, insteadof the initial command from the profile for the task.

commandSpecifies the initial command.

Usage notesv The autotask does not process commands until CNMSTYLE processing

completes.v You can also use the AUTOTASK command to start an automated operator and

optionally associate an MVS console with this automated operator. For moreinformation, see the IBM Tivoli NetView for z/OS Command Reference Volume 1(A-N) or the NetView online help.

v You can use a question mark (?) followed by the function name instead ofspecifying an operator ID for the autotask, for example:AUTOTASK.?Primary.Console = *NONE*

If you do this, use the function.autotask statement to define the operator ID:function.autotask.primary = AUTO1

Note that if the name used with a question mark (Primary) is not specified in afunction.autotask statement, the autotask statement is ignored. Function namescan be a maximum length of 15 characters.

EMAAUTOPurpose

The EMAAUTO statement specifies whether the Tivoli NetView for z/OSEnterprise Management Agent or the Tivoli Enterprise Monitoring Server is to bestarted during NetView initialization. The TEMA tower must be enabled.

Syntax

The EMAAUTO statement has the following syntax:

EMAAUTO

►► EMAAUTO. TEMA .procStr = procedure_cmdstrTEMS *NONE*

►◄


where:

procedure_cmdstrSpecifies the startup procedure and startup parameters.

*NONE*Specifies that the procedure_name should not be started.

TEMA.procStrSpecifies the NetView for z/OS Enterprise Management Agent startupprocedure. If you do not want the NetView program to start this procedure,specify *NONE* for procedure_name.

TEMS.procStrSpecifies the Tivoli Enterprise Monitoring Server startup procedure name. Ifyou do not want the NetView program to start this procedure, specify *NONE*for procedure_name.

Usage notesv The TEMA tower must be enabled.v The INIT.EMAAUTO statement must be set to Yes for the

EMAAUTO.TEMA.procStr and EMAAUTO.TEMS.procStr statements to beprocessed.

v The NetView program only processes one startup procedure statement. If youspecify a value other than *NONE* for EMAAUTO.TEMS.procStr statement, theTivoli Enterprise Monitoring Server is started. When successfully started, theNetView message automation starts the NetView for z/OS EnterpriseManagement Agent by starting the procedure specified with theEMAAUTO.TEMA.procStr statement. See the CNMSEMAA automation memberfor more information. You can specify parameters for the Tivoli EnterpriseMonitoring Server startup procedure by adding them to theEMAAUTO.TEMS.procStr statement.

v If you only want the NetView for z/OS Enterprise Management Agent to bestarted, specify *NONE* on the EMAAUTO.TEMS.procStr statement and specifythe name of the startup procedure on the EMAAUTO.TEMA.procStr statement.You can specify parameters for the NetView for z/OS Enterprise ManagementAgent startup procedure by adding them to the EMAAUTO.TEMA.procStrstatement.

v If you are implementing the GDPS Active/Active Continuous Availabilitysolution, specify the NetView agent startup procedure on both controllers. Onthe primary controller, specify INIT.EMAAUTO = Yes. If you are only using theNetView agent on this system for the GDPS Active/Active ContinuousAvailability solution, specify INIT.EMAAUTO = No on the backup controller.The NetView agent is required on the backup controller for monitoring tocontinue when there are outages on the primary controller.

ENT.ACTIVEACTIVE.ROLEPurpose

The ENT.ACTIVEACTIVE.ROLE statement specifies the role of the NetViewprogram running on the primary or backup controller.

Syntax

The ENT.ACTIVEACTIVE.ROLE statement has the following syntax:


ENT.ACTIVEACTIVE.ROLE

►► ENT.ACTIVEACTIVE.ROLE= PRIMARYBACKUP

►◄

where:

PRIMARYThis value indicates that the NetView program is an Active/Active enterprisemaster NetView program.

BACKUPThis value indicates that the NetView program is the backup Active/Activeenterprise master NetView program.

Usage notesv Specify the ENT.ACTIVEACTIVE.ROLE statement only if you are implementing

the GDPS Active/Active Continuous Availability solution.v This statement is required on controller systems. There is no default or initial

value for the ENT.ACTIVEACTIVE.ROLE statement.v If the Active/Active enterprise master NetView program also acts as the

discovery manager enterprise master, the discovery manager enterprise mastermoves with the Active/Active enterprise master from one controller to the other.

v The ENT.ACTIVEACTIVE.ROLE statement is ignored by RESTYLE ENTprocessing to avoid conflicts with automation.

ENT.ALT.CONTROLLERPurpose

The ENT.ALT.CONTROLLER statement is used by NetView programs that areconfigured as controller systems in the GDPS Active/Active ContinuousAvailability solution. This statement specifies the domain name of another NetViewprogram that also can be a controller in the solution. The primary controllercontains a statement for the backup controller; the backup controller contains astatement for the primary controller. The ENT.ALT.CONTROLLER statementenables the controllers to exchange control information that is required for thesolution.

Syntax

The ENT.ALT.CONTROLLER statement has the following syntax:

ENT.ALT.CONTROLLER

►► ENT.ALT.CONTROLLER=domain ►◄

where:

domainThe domain name of the other controller in the solution.


||

|

|

||||||||

|

|

|

||||||||

|

||

Usage notev Specify the ENT.ACTIVEACTIVE.ROLE statement only if you are implementing

the GDPS Active/Active Continuous Availability solution.v NetView communication between the two controllers requires that a RMTSYN

statement is coded for the domain.v To implement definition changes while the NetView program is active, change

the value in the CNMSTUSR or CxxSTGEN member, and enter the RESTYLEENT command. For more information about changing CNMSTYLE statements,see IBM Tivoli NetView for z/OS Installation: Getting Started.

ENT.CONNCHECK.INTPurpose

The ENT.CONNCHECK.INT statement specifies the interval for how often asysplex master or enterprise master NetView program verifies RMTCMDconnectivity to other systems in the sysplex or enterprise.v For sysplex masters, connectivity is checked to other systems in the sysplex.v For enterprise masters, connectivity is checked to systems that are specified on

ENT.SYSTEMS statements and that were contacted. If a contacted system is in asysplex, connectivity to other systems in the sysplex is also checked.

Syntax

The ENT.CONNCHECK.INT statement has the following syntax:

ENT.CONNCHECK.INT

►►ENT.CONNCHECK.INT = 1

ENT.CONNCHECK.INT = minutes►◄

where:

minutesSpecifies the number of minutes (1 - 60). The default value is 1 minute.

Usage notesv To implement definition changes while the NetView program is active, change


ENT.SYNPurpose

The ENT.SYN statement specifies a primary and secondary IP address for aNetView domain that has a RMTALIAS name defined on an ENT.SYSTEMSstatement.

Use this statement for a NetView program that has an IP address that changes as aresult of a planned or unplanned outage.


|

||

||

||||

||

|

|||

|

|||

|

|

|

|||||||||||||||

|

|

||

|

||||

||

|

|||

||

Syntax

The ENT.SYN statement has the following syntax:

ENT.SYN

►► ENT.SYN. PRI .site.domain = alias,rmtsyn_valueSEC

►◄

where:

PRISpecifies the primary IP address for the domain.

SECSpecifies the secondary IP address for the domain.

siteSpecifies the 1 - 8 character user-specified name of the Active/Active site thatidentifies the Active/Active site.

domainSpecifies the 1 - 5 character name of the remote NetView domain.

aliasSpecifies the RMTALIAS name that is specified on an ENT.SYSTEMSstatement.

rmtsyn_valueSpecifies the value that is specified on the RMTSYN statement. For additionalinformation on how to specify the value, see the RMTSYN statement.

Usage notesv Specify the ENT.SYN statement on controller systems if you are implementing

the GDPS Active/Active Continuous Availability solution. This statement is notrequired if the NetView programs in the solution do not change their IPaddresses. For additional information about the solution, see IBM Tivoli NetViewfor z/OS Installation: Configuring the GDPS Active/Active Continuous AvailabilitySolution.

v The rmtsyn_value cannot specify SNA.v To implement definition changes while the NetView program is active, change


Example

The following statements are examples of ENT.SYN statements:ENT.SYN.PRI.PLEXSITE.CNM01 = SANDIEGO,ip_addr1ENT.SYN.SEC.PLEXSITE.CNM01 = SANDIEGO,ip_addr2

ENT.SYSTEMS.namePurpose

The ENT.SYSTEMS.name statement specifies entry points into XCF groups insysplex systems or stand-alone systems that can be managed.


|

|

|

||||||||||||||||

|

|

||

||

|||

||

|||

|||

|

||||||

|

||||

|

|

||

||

|

||

An entry point into a sysplex is a NetView domain that returns information aboutother NetView domains in its XCF group in the sysplex to the enterprise master.This enables the enterprise master to discover all domains in a sysplex withoutrequiring configuration for contacting each domain. Only configuration forcontacting the entry point or points (a RMTALIAS definition) is required.

To provide backup entry points, you can specify more than one entry point on theENT.SYSTEMS.name statement. If you do not specify a backup entry point, you canlose connectivity to remote systems.

Syntax

The ENT.SYSTEMS.name statement has the following syntax:

ENT.SYSTEMS.name

►► ▼ENT.SYSTEMS.name= alias ►◄

where:

nameSpecifies a label for the entry point into a sysplex or stand-alone system.

aliasSpecifies one or more defined RMTCMD aliases that you can use to contact asysplex member or stand-alone system. In the case of a sysplex, additionalaliases (to additional NetView domains) can serve as backup entry points intothe sysplex. The NetView program processes the aliases specified on thestatement from left to right until one of the entry points is contacted.

For additional information on how to specify the RMTCMD alias, see theRMTALIAS and RMTSYN statements.

Usage notesv The enterprise master NetView program goes through the aliases in sequence

until it successfully contacts a sysplex member or stand-alone system, or the listis ended.

v If DVIPA connectivity exists to the sysplex and the sysplex is using theXCF.MASTDVIPA statement to define a DVIPA address for the master NetViewprogram, you can specify an alias for the DVIPA address of the master NetViewprogram. This alias can be used to reach the master NetView program regardlessof its location in the sysplex. By using the ENT.SYSTEMS.name statement, youcan reduce the number of aliases that are required to contact a system in thesysplex.

v Make sure that the RMTALIAS and RMTSYN statements define the aliases thatyou specify on the ENT.SYSTEMS.name statement.

v The NetView V6R1 program contains function that is required to process theACTVCTL TAKEOVER command that is used by the GDPS Active/Active ContinuousAvailability solution. You can only specify NetView V6R1 and later systemaliases in the entry point list.

v To implement definition changes while the NetView program is active, changethe value in the CNMSTUSR or CxxSTGEN member, and enter the RESTYLEENT command.


|||||

|||

|

||||

Examplesv An example ENT.SYSTEMS.name statement follows for the CALPLEX sysplex

that specifies TAMPA and SANDIEGO as RMTCMD aliases:ENT.SYSTEMS.CALPLEX = TAMPA SANDIEGO

These aliases must also be specified on the RMTCMD statement:RMTALIAS.SANDIEGO = LU62.CNM01RMTALIAS.TAMPA = USIBMNT.CNM02

v An example ENT.SYSTEMS.name statement follows for the ONESYS system.ENT.SYSTEMS.ONESYS = SPV6

ENT.TYPEPurpose

The ENT.TYPE statement specifies the type of enterprise master NetView program.

Syntax

The ENT.TYPE statement has the following syntax:

ENT.TYPE

►►ENT.TYPE=DISCOVERY

ENT.TYPE=ACTIVEACTIVE DISCOVERY

►◄

where:

ACTIVEACTIVEIndicates that this NetView program displays enterprise data that is related tothe GDPS Active/Active Continuous Availability solution, including LifelineAdvisor and replication data.

DISCOVERYIndicates that this NetView program displays enterprise data for theDISCOVERY tower. Data for the DISCOVERY tower includes sysplexes,TCP/IP stacks, IP interfaces, Telnet servers and ports, OSAs, and HiperSockets.

Usage notesv The ENT.TYPE statement is required on controller systems and specifies the type

of enterprise master NetView program:

ACTIVEACTIVEActive/Active enterprise master

ACTIVEACTIVE DISCOVERYActive/Active enterprise master that includes resources that werediscovered when the DISCOVERY function was started. These resourcesinclude sysplex, TCP/IP stack, IP interface, Telnet server and port, OSA,and HiperSockets data.

v You can specify ENT.TYPE=DISCOVERY on non-controller systems to forwarddiscovery manager data to a non-controller system.

v For Active/Active systems, you must specify the ACTIVEACTIVE value on theENT.TYPE statement to enable replication data forwarding.


v The ENT.TYPE statements for both the primary and backup controllers mustmatch. If the primary controller is a discovery manager enterprise master, thebackup controller must also be defined as a discovery manager enterprisemaster.

v The initial value of the ENT.TYPE statement in the CNMSTLIF member isACTIVEACTIVE.

v If you do not specify an ENT.TYPE statement, the default value is DISCOVERY.v To implement definition changes while the NetView program is active, change

the value in the CNMSTUSR or CxxSTGEN member, and enter the RESTYLEENT command.

function.autotaskPurpose

The function.autotask statement defines the autotask for the specified function.Refer to the CNMSTYLE member for specific information on the function.autotaskstatements.

Syntax

The function.autotask statement has the following syntax:

function.autotask

►► function.autotask. function_name =autotask_name ►◄

where:

autotask_nameSpecifies the autotask name. The autotask name must be 1 - 8 alphanumericcharacters in length; can contain no special characters except #, @, and $; andmust start with either an alphabetic character or #, @, or $.

function_nameSpecifies the function name. The function name can be 1 - 15 characters andcan contain letters, numbers, and periods. The first character must be a letter.

You can prefix function_name with a question mark (?) and then use this inother areas of the NetView program. This allows the function name to be usedin many places where an operator ID is required. For example, you can use?function_name on the AUTOTASK statement , the QOS command, and theAUTOTASK command.

Usage notesv For a list of autotasks and their functions, see IBM Tivoli NetView for z/OS

Installation: Getting Started.v The function.autotask.primary statement provides a set of related processes,

possibly including timed commands, message automation, data services task(DST) services, and control (operator) commands. This statement is also theautotask that is used when an error is encountered with the task name onanother function.autotask statement. Because of this, thefunction.autotask.primary statement is required and cannot contain a value of*NONE*.

v The following statement is used by MultiSystem Manager:


(MSM)function.autotask.MSMdefault = AUTOMSMD

The MSMdefault autotask is used if the AUTOTASK keyword is not specified onthe GETTOPO command and the related service point object is not in RODM.

v For any autotasks that you define to the NetView program, also considerdefining them to the SAF product. The automation table and other NetViewfunctions use these definitions.

INIT.EMAAUTOPurpose

The INIT.EMAAUTO statement specifies whether the EMAAUTO.TEMS.procStrstatement or the EMAAUTO.TEMA.procStr is to be processed.

Syntax

The INIT.EMAAUTO statement has the following syntax:

INIT.EMAAUTO

►►INIT.EMAAUTO = YES

INIT.EMAAUTO = NO►◄

where:

NO Indicates not to process either the EMAAUTO.TEMS.procStr or theEMAAUTO.TEMA.procStr statement.

YESIndicates to process the EMAAUTO.TEMS.procStr statement and theEMAAUTO.TEMA.procStr statement.

Usage notesv If you are implementing the GDPS Active/Active Continuous Availability

solution, specify the NetView agent startup procedure on both controllers. Onthe primary controller, specify INIT.EMAAUTO = Yes. On the backup controller,specify INIT.EMAAUTO = No if you are only using the NetView agent on thissystem for the GDPS Active/Active Continuous Availability solution. TheNetView agent is required on the backup controller for monitoring to continuewhen there are outages on the primary controller.

v The INIT.EMAAUTO statement requires that the TEMA tower be enabled.

NACMD.ROWSxxxPurpose

The NACMD.ROWSxxx statement defines the number of rows of data to collect forthe Tivoli Enterprise Portal workspaces that are associated with the NetView forz/OS Enterprise Management Agent.

Syntax

The NACMD.ROWSxxx statement has the following syntax:


NACMD.ROWSxxx

►► NACMD.ROWSxxx=number ►◄

where:

ROWSxxxSpecifies the number of rows of data to collect for each of the workspaces. Thefollowing values can be used:

ROWSALOGNetView Audit Log workspace. The default number of rows is 50000.The maximum number of rows is 200000.

ROWSCONINACTInactive TCPIP Connection Data workspace. The default number ofrows is 20000. The maximum number of rows is 80000.

ROWSCONNACTTCPIP Connection Data workspace. The default number of rows is200000. The maximum number of rows is 800000.

ROWSDVCONNDVIPA Connections workspace. The default number of rows is 10000.The maximum number of rows is 40000.

ROWSDVDEFDSDVIPA Definition and Status workspace. The default number of rows is10000. The maximum number of rows is 40000.

ROWSDVROUTCRDistributed DVIPA Connection Routing workspace. The defaultnumber of rows is 150000. The maximum number of rows is 600000.

ROWSDVROUTVRVIPA Routes workspace. The default number of rows is 256. Themaximum number of rows is 1024.

ROWSDVTADDTDistributed DVIPA Targets workspace. The default number of rows is10000. The maximum number of rows is 40000.

ROWSDVTADSDDVIPA Sysplex Distributors workspace. The default number of rows is10000. The maximum number of rows is 40000.

ROWSDVTADSHDistributed DVIPA Server Health workspace. The default number ofrows is 10000. The maximum number of rows is 40000.

ROWSHEALTHNetView Tasks workspace. The default number of rows is 500. Themaximum number of rows is 4096.

ROWSHIPERSOCKHiperSockets Configuration and Status workspace. The default numberof rows is 256. The maximum number of rows is 1024.

ROWSNVAPPSNetView Applications workspace. The default number of rows is 256.The maximum number of rows is 1024.


ROWSNVCMDNetView Command Response workspace. The default number of rowsis 100000. The maximum number of rows is 400000.

ROWSNVLOGNetView Log workspace. The default number of rows is 1000. Themaximum number of rows is 4000.

ROWSOSAOSA Channels and Ports workspace. The default number of rows is128. The maximum number of rows is 256.

ROWSSESSACTSession Data workspace. The default number of rows is 200000. Themaximum number of rows is 800000.

ROWSSTCKCFGStack Configuration and Status workspace. The default number of rowsis 256. The maximum number of rows is 1024.

ROWSTELCFGTelnet Server Summary table view in the Telnet Server Configurationand Status workspace. The default number of rows is 256. Themaximum number of rows is 1024.

ROWSTELPRTTelnet Server Port Summary table view in the Telnet ServerConfiguration and Status workspace. The default number of rows is256. The maximum number of rows is 1024.

The following information specifies the number of rows of data to collect forGDPS Active/Active Continuous Availability solution workspaces.

ROWSADVISORSWorkload Lifeline Advisors workspace. The default number of rows is2. The maximum number of rows is 6.

ROWSAGENTSWorkload Lifeline Agents workspace. The default number of rows is128. The maximum number of rows is 1024.

ROWSDB2APPSRVDB2 apply servers workspace. The default number of rows is 256. Themaximum number of rows is 1024.

ROWSDB2APPWKLDB2 apply workloads workspace. The default number of rows is 256.The maximum number of rows is 1024.

ROWSDB2CAPSRVDB2 capture servers workspace. The default number of rows is 256.The maximum number of rows is 1024.

ROWSDB2CAPWKLDB2 capture workloads workspace. The default number of rows is 256.The maximum number of rows is 1024.

ROWSIMSAPPDETIMS apply details workspace. The default number of rows is 256. Themaximum number of rows is 1024.


ROWSIMSCAPDETIMS capture details workspace. The default number of rows is 256. Themaximum number of rows is 1024.

ROWSLOADBALSLoad Balancers workspace. The default number of rows is 16. Themaximum number of rows is 32.

ROWSLOADGRPSLoad Balancer Groups workspace. The default number of rows is 128.The maximum number of rows is 512.

ROWSREPSRVRSReplication servers workspace. The default number of rows is 512. Themaximum number of rows is 2048.

ROWSREPWKLSReplication workloads workspace. The default number of rows is 256.The maximum number of rows is 1024.

ROWSSITESWorkload Sites workspace. The default number of rows is 400. Themaximum number of rows is 6144.

ROWSVSAMAPPDETVSAM apply details workspace. The default number of rows is 256.The maximum number of rows is 1024.

ROWSVSAMCAPDETVSAM capture details workspace. The default number of rows is 256.The maximum number of rows is 1024.

ROWSWORKLOADSWorkloads workspace. The default number of rows is 200. Themaximum number of rows is 3072.

ROWSWORKSRVRSWorkload Servers workspace. The default number of rows is 128. Themaximum number of rows is 2048.

numberThe number of rows. The default and maximum values are listed with theworkspace row name.

Usage notes

To implement definition changes for the NACMD.ROWS statement, the NetViewprogram must be recycled. For more information about changing CNMSTYLEstatements, see IBM Tivoli NetView for z/OS Installation: Getting Started.

RMTALIASPurpose

The RMTALIAS statement specifies the RMTSYN definition that applies when thealias identifier is specified as the target domain on a RMTCMD SEND command.You can use multiple RMTALIAS statements to define a combination of networks(netid), domains and transports (IPv4, IPv6, or SNA).


||

|||

||

|||

|||

||

Syntax

Syntax for the RMTALIAS statement:

RMTALIAS

►► RMTALIAS. alias = second. third ►◄

where:

aliasSpecifies a 1 - 8 character identifier that resolves to a particular RMTSYN name

secondSpecifies the second element (1 - 8 characters) of the RMTSYN name to beused. This value corresponds to the network ID that is specified on theRMTSYN statement and might or might not be a real network ID.

thirdSpecifies the third element (1 - 5 characters) of the RMTSYN name to be used.This value corresponds to the domain ID specified on the RMTSYN statementand is a real domain ID.

Usage notes

The second position in the RMTALIAS value is not necessarily a real network ID.The ON keyword of the RMTSYN statement is used to provide the real network IDfor the alias being defined by the RMTALIAS/RMTSYN statement pair.

Examplesv Example 1: Defining an alias for the RMTCMD command over IPv6 for the

CNM01 domain in the NETA network

The following statements define the XXIPV6 alias for the CNM01 domain in theNETA network. The name of the host at which the target NetView programresides is host6.company.com, and the RMTCMD server (DSIUDST task) in theCNM01 domain is listening for connection requests on the 4022 port. When theNetView program requests resolution of the host name, an IPv6 address isrequested so that the transport that is used by the RMTCMD command is TCPover IPv6.RMTALIAS.XXIPV6 = XXNETA.CNM01RMTSYN.XXNETA.CNM01 = host6.company.com/4022 IPV6 ON NETA

The following RMTCMD SEND command uses the XXIPV6 alias:RMTCMD SEND,DOMAIN=XXIPV6,command

v Example 2: Defining an alias for the RMTCMD command over IPv4 for theCNM01 domain in the NETA network

The following statements define the YYIP alias for the CNM01 domain in theNETA network. The name of the host at which the target NetView resides ishost.company.com, and the RMTCMD server (DSIUDST task) in the CNM01domain is listening for connection requests on the 4022 port. When the NetViewprogram requests resolution of the host name, an IPv4 address is requested sothat the transport that is used by the RMTCMD command is TCP over IP (IPv4).RMTALIAS.YYIP = YYNETA.CNM01RMTSYN.YYNETA.CNM01 = host.company.com/4022 IPV4 ON NETA


The following RMTCMD SEND command uses the YYIP alias:RMTCMD SEND,DOMAIN=YYIP,command

v Example 3: Defining an alias for the RMTCMD command over SNA for theCNM01 domain in the NETA network

The following statements define the ZZSNA alias for the CNM01 domain in theNETA network. The CNM01 domain is also the LU name for the target NetViewapplication. Because the value of the RMTSYN statement indicates SNA, an SNALU6.2 conversation with the target NetView LU is used to transport the remotecommand. For additional information on creating a RMTALIAS/RMTSYN pair,see the Usage Notes for the RMTSYN statement.RMTALIAS.ZZSNA = ZZNETA.CNM01RMTSYN.ZZNETA.CNM01 = SNA ON NETA

The following RMTCMD SEND command uses the ZZSNA alias:RMTCMD SEND,DOMAIN=ZZSNA,command

RMTINIT.IPPurpose

The RMTINIT.IP statement specifies whether all TCP/IP remote operations (IPv4and IPv6) are enabled for RMTCMD and ENDTASK processing.

For IPv6: IPv6 networking must already be enabled in the TCP/IP stack (theAF_INET6 address family is enabled) and the IPv6Env CNMSTYLE statement mustbe set to MIXED or ONLY.

Syntax

The RMTINIT.IP statement has the following syntax:

RMTINIT.IP

►►RMTINIT.IP=NO

RMTINIT.IP=YES►◄

where:

YESSpecifies that TCP/IP remote operations is enabled. This is the initial setting inthe CNMSTYLE member.

NO Specifies that TCP/IP remote operations is not enabled. This is the defaultvalue if you do not specify a RMTINIT.IP statement.

Usage notesv By default, not all NetView functions have RMTCMD for TCP/IP enabled. There

might be additional configuration that is required for these functions.


RMTSYNPurpose

The RMTSYN statement specifies the protocol used for communications by thePIPE ROUTE stage and by the RMTCMD and LABEL commands.

Syntax

Syntax for the RMTSYN statement:

RMTSYN

►► RMTSYN. netid. domain =SNA

/4022IP_host

/port_number IPV4IPV6

►

►ON netid

►◄

where:

netidSpecifies the 1 - 8 character name of the real network containing the domain oran identifier used to associate an RMTALIAS definition with the RMTSYNstatement. An RMTALIAS statement is associated with this RMTSYN statementwhen the second position in the RMTALIAS value matches this identifier.

domainSpecifies the 1 - 5 character name of the remote NetView domain.

IP_hostSpecifies a standard IP host name or address for the remote NetView domain.When communicating using an IP transport, the IP host can be followed by aport number. IP host names are resolved to IP addresses after the main part ofinitialization.

port_numberSpecifies the port number. A slash (/) separates the port_number from IP_host.The default port number is 4022.

IPV4Specifies to use the IPV4 protocol to communicate with the specified domain.Use the IPV4 keyword with IP_host when it is a host name.

IPV6Specifies to use the IPV6 protocol to communicate with the specified domain.Use the IPV6 keyword with IP_host when it is a host name.

ON netidSpecifies the 1 - 8 character name of the network containing the domain. Usethe ON netid specification when an RMTSYN statement is associated with anRMTALIAS statement.


SNASpecifies to use SNA LU 6.2 to communicate with the specified domain. This isthe default.

Usage notesv If the IPV4 or IPV6 keyword is coded in an RMTSYN value and if the target

host is identified by an IP address, then the IPV4 or IPV6 keyword (whichever iscoded) is ignored by RMTCMD command processing.

v The network ID that is specified with the ON keyword is used as the networkID for a target NetView domain under the following conditions:– NETID=* is specified or set as the default value for a RMTCMD SEND

command.– RMTSYN statement is part of a RMTALIAS/RMTSYN statement pair that is

defining an alias for a target NetView domain.v If the RMTSYN definition is part of a RMTALIAS/RMTSYN statement pair used

to define an alias, the RMTSYN statement cannot be used to resolve the value ofthe DOMAIN keyword of RMTCMD unless the pseudo-network-ID portion ofthe RMTALIAS and RMTSYN statements matches the real network ID of theNetView domain to be targeted. Consider this example:– Define an alias, NTVGGV6, for remote domain NTVGG, specifying an IPv6

network transport, a host name, port number 40220, and real network IDUSIBMNTRMTALIAS.NTVGGV6 = XXV6.NTVGG

| | || | |

Alias Pseudo Realnetwork domainID ID

RMTSYN.XXV6.NTVGG = your.host.com/40220 IPV6 ON USIBMNT

| | || | |

Pseudo Real Realnetwork domain networkID ID ID

With these definitions, the NTVGGV6 alias may be used to send a command toNetView domain NTVGG in network USIBMNT like this:RMTCMD SEND DOMAIN=NTVGGV6 OPERID=OPER1 AUTOTBL STATUS

If you attempt to send a command from the current NetView domain, presumed toalso be in network USIBMNT in this example, to NetView domain NTVGG likethis:RMTCMD SEND DOMAIN=NTVGG OPERID=OPER1 AUTOTBL STATUS

The RMTSYN statement cannot be used to resolve NetView domain NTVGG innetwork USIBMNT to the applicable IP address, port, and network transport,because the network ID portion of the RMTSYN statement, XXV6, does not matchthe real network ID, USIBMNT.

Examplesv An example RMTSYN statement follows using an IP host name:

RMTSYN.NETA.CNM01 = host6.company.com/4022 // resolve later


Because this RMTSYN statement does not include a transport keyword, the IP(IPv4 or IPv6) address is determined based on the setting of the IPv6Envstatement:– NONE: IPv4 address is used, if available– ONLY: IPv6 address is used, if available– MIXED: first address returned is used (either IPv4 or IPv6)

v An example RMTSYN statement follows using an IP address and a default port:RMTSYN.NETB.CNM03 = 10.67.50.22 // IP address & default port

v An example RMTSYN statement follows for a session using LU 6.2:RMTSYN.NETX.NTVAA = SNA // use LU6.2 for this domain

v An example RMTSYN statement follows for a session using IPv6:RMTSYN.NETX.NTVXX = 2002:92A:111:501:10:10:163:7/4022

For additional examples, see the RMTALIAS statement.

TOWERPurpose

The TOWER statement activates NetView components and other products.

Syntax

The TOWER statement has the following syntax:

TOWER

►► ▼TOWER = component_name ►◄

where:

component_nameIdentifies the tower name. Tower names are alphanumeric (includes @, #, and$) and are from 1 - 16 characters.

The following towers are provided with the NetView product:

Tower Description

ACTIVEACTIVE Enables the GDPS Active/Active Continuous Availability solution.

SubtowerDescription

LIFELINEEnables data to be collected from the Lifeline Advisorcomponent of the Multi-site Workload Lifeline product.

REPLICATIONEnables data to be collected from software replication captureand apply servers.

SubtowerDescription


DB2 Enables data to be collected from capture and applyservers for Q (DB2) replication.

IMS Enables data to be collected from capture and applyservers for IMS replication.

VSAMEnables data to be collected from capture and applyservers for VSAM replication.

AMI Enables the Application Management Instrumentation.

AON Enables network automation (AON component).

SubtowerDescription

SNA SNA automation (AON/SNA)

SubtowerDescription

X25 AON/SNA X.25 support

TCP TCP/IP automation (AON/TCP)

SubtowerDescription

IDS Intrusion Detection Services (IDS) support

DISCOVERYEnables the discovery of sysplexes, z/OS systems, coupling facilities,TCP/IP stacks, TCP/IP subplexes, and NetView applications.

SubtowerDescription

INTERFACESEnables the discovery of stack interface information.

SubtowerDescription

OSA Enables the discovery of OSA channels and ports.

HIPERSOCKETSEnables the discovery of HiperSockets configurationand status information.

TELNETEnables the discovery of Telnet servers and ports.

DVIPAEnables the collection of dynamic virtual IP addressing (DVIPA)definition and status data.

SubtowerDescription

DVCONNEnables the collection of DVIPA connections data.

DVROUTEnables the collection of VIPA routes and distributed DVIPAconnection routing data.


|

||

|||

||

DVTADEnables collection of DVIPA sysplex distributors, distributedDVIPA targets, distributed DVIPA server health statistics, anddistributed DVIPA statistics (if enabled).

GRAPHICSEnables the NetView Management console.

SubtowerDescription

SNATMSNA Topology Manager.

IPMGTEnables IP Management

SubtowerDescription

ACTMONPerforms active monitoring for IP resources without enablingthe AON component (AON tower). Do not enable theACTMON subtower if you have the AON TCP subtowerenabled.

IDS Enables Intrusion Detection automation without enabling theAON component (AON tower). Do not enable the IDSsubtower if you have the AON TCP subtower enabled.

MSM Enables the MultiSystem Manager.

SubtowerDescription

ITNM IBM Tivoli Network Manager feature.

OPN Open feature.

MVScmdMgtEnables MVS command management.

The MVS Command Management function is deprecated and isreplaced by the MVS Command Revision function. The MVSCommand Revision function does not require the MVScmdMgt towerto be enabled. For more information, see the IBM Tivoli NetView forz/OS Automation Guide.

NLDMEnables the session monitor.

NPDAEnables the hardware monitor.

NVSOAEnables the Web Services Gateway function.

SA Enables System Automation for z/OS.

TARA Enables the 4700 support facility.

TCPIPCOLLECTEnables the collection of TCP/IP connection and packet trace data fromz/OS Communications Server.


SubtowerDescription

TCPCONNRequired for the collection of TCP/IP connection data usingthe TCPCONN START and TCPCONN STOP commands.

PKTS Required for the collection of TCP/IP packet trace data usingthe PKTS START and PKTS STOP commands, and for thecollection of OSA packet trace data.

TEMAEnables the NetView program to communicate with the Tivoli NetViewfor z/OS Enterprise Management Agent.

Usage Note: Do not enable the TEMA tower unless you are installingthe Tivoli NetView for z/OS Enterprise Management Agent. Onlyenable the TEMA tower on one NetView program for each LPAR.

SubtowerDescription

ACTIVEACTIVEEnables the display of GDPS Active/Active ContinuousAvailability solution workspaces.

CONINACTEnables the collection and display of inactive TCP/IPconnections.

CONNACTEnables the collection and display of active TCP/IPconnections.

DVCONNEnables the display of DVIPA connections.

DVDEFEnables the display of DVIPA definition and status data.

DVROUTEnables the display of VIPA route data.

DVTADEnables the display of distributed DVIPA data.

HEALTHEnables the collection and display of NetView task data.

HIPERSOCKETSEnables the display of HiperSockets configuration and statusinformation. (Requires RODM.)

OSA Enables the display of OSA channels and ports information.(Requires RODM.)

SESSACTEnables the collection and display of active sessions.

The SESSACT subtower is only supported in one NetViewprogram per system.

SYSPLEXEnables the display of stack configuration and status data.


TELNETEnables the display of Telnet servers and Telnet server portinformation.

Usage notesv To disable a tower, either remove the name or prefix the name with an asterisk.

For example, enable the installation of MultiSystem Manager (MSM) byincluding MSM in the TOWER statement: TOWER = *AON MSM . To disableinstallation of MultiSystem Manager, remove MSM from the tower statement orprefix it with an asterisk (*MSM).

v Towers can have subtowers. For example, the MSM tower has a subtower foreach of its features. For more information about the TOWER statement andsubtowers, see the CNMSTYLE member and the IBM Tivoli NetView for z/OSInstallation: Getting Started manual.

XCF.RANKPurpose

The XCF.RANK statement determines the rank of the NetView program within thesysplex, or a NetView program running as a MONOPLEX or XCFLOCAL system.

Syntax

The XCF.RANK statement has the following syntax:

XCF.RANK

►►XCF.RANK=1

XCF.RANK=rank_number►◄

where:

rank_numberSpecifies the rank of the NetView program within the sysplex. The valueranges from -1 (cannot participate in the NetView group) - 250 (masterNetView program). A value of 0 indicates the NetView program participates inthe group, but cannot assume the master role. A value 1 - 249, with 249 beingthe highest, means the NetView program is master-capable. The default valueis 1.

Usage notesv Specify only one NetView program within the sysplex as the master.v NetView programs in a GDPS Active/Active Continuous Availability solution

configuration must enable XCF support to enable forwarding of replication datato the controller NetView program. Specifying the minimal level of 0 onproduction systems is sufficient to enable data forwarding.The primary controller that is also the master NetView program, and the backupcontroller that can become the master, must each set XCF.RANK to a value of250.

v To implement definition changes while the NetView program is active, changethe value in the CNMSTUSR or CxxSTGEN member, and enter the RESTYLE


||

||||

|||

XCF command. For information about changing CNMSTYLE statements, seeIBM Tivoli NetView for z/OS Installation: Getting Started.

v You can use the following command to dynamically change the rank of aNetView program:PLEXCTL RANK=rankvalue


||

|


Appendix B. Commands

You can enter NetView commands from the command facility or from any otherNetView component.

The commands are listed in alphabetic order. Each command description includesthe format and description of operands and, where applicable, usage notes,responses, and examples.

For online help for a specific command, enter:HELP command

Where command is the name of the command.

ACTVCTL (NCCF)Syntax

ACTVCTL

►► ACTVCTL

▼

▼

▼

CONNECT= P SITE=domain_siteS

LISTINFO= ALLDB2IMSLIFELINEVSAM

RESET= ALL INTERVAL=secondsDB2IMSLIFELINEVSAM

START= ALLsubtower_name

,

( subtower_name )STOP= ALL

subtower_name,

( subtower_name )TAKEOVER

ENABLE= component,

( component )

►◄

Purpose of Command

Note: This command is used only with the GDPS Active/Active ContinuousAvailability solution.The ACTVCTL command provides the following capabilities:v Displays data collection statistics


|||||

v Dynamically resets the data collection intervalv Dynamically starts and stops data collectorsv Moves the enterprise master NetView program from one controller to anotherv Establishes connections from the enterprise master NetView program to NetView

domains in the primary or secondary production sysplex.

Operand Descriptions

CONNECTEstablishes connections to the NetView domains using the IP addressesspecified on ENT.SYN CNMSTYLE statements.

P Connects to the NetView domains using the IP addresses specified on theENT.SYN.PRI CNMSTYLE statements.

S Connects to the NetView domains using the IP addresses specified on theENT.SYN.SEC CNMSTYLE statements.

Important: Issuing the ACTVCTL CONNECT command can cause unintendedresults for the Active/Active solution. For more information, see "Optional:Defining primary and secondary IP address for ENT.SYSTEMS targets" inInstallation: Configuring the GDPS Active/Active Continuous Availability Solution.

SITESpecifies the Active/Active site where the NetView domain resides. The sitevalue can be 1-8 characters in length.

The SITE keyword restricts the scope of the ACTVCTL CONNECT commandto those ENT.SYN statements that also specify the same site.

LISTINFODisplays the average and maximum time for the data collectors to collect dataduring a given data collection interval. The display includes statistics forActive/Active data collectors:

ALLDisplays information about all ACTIVEACTIVE subtowers.

DB2Displays DB2 software replication (Q replication) information.

IMSDisplays IMS software replication information.

LIFELINEDisplays Multi-site Workload Lifeline Advisor information.

VSAMDisplays VSAM software replication information.

RESETResets the sampling interval for the specified subtower. This keyword requiresthe INTERVAL keyword. The following values are valid for the RESETkeyword:

ALLResets sampling intervals for all data collectors that are supported by theACTVCTL command if their subtowers are enabled in the CNMSTYLEmember.

DB2Resets sampling intervals for DB2 software replication (Q replication).


||

|||

|||

|||

||||

|||

||

|

||

IMSResets sampling intervals for IMS software replication.

LIFELINEResets sampling intervals for Multi-site Workload Lifeline Advisor.

VSAMResets sampling intervals for VSAM software replication.

INTERVALSpecifies the sampling interval for data collection for the subtower orsubtowers that are specified on the RESET keyword. If the RESET keyword isspecified as ALL, all Active/Active data collection sampling intervals are set tothe specified value. The range can be 10 - 43200 seconds.

STARTStarts the collection of data for the specified subtower. The subtower must beenabled in the CNMSTYLE member for the data collection to start. Thefollowing values are valid for the START option:

ALLStarts all data collectors that are supported by the ACTVCTL command iftheir subtowers are enabled in the CNMSTYLE member.

subtower_nameStarts the data collectors for one or more of the following subtowers:v DB2v IMSv LIFELINEv VSAM

STOPStops the data collection for the specified subtower. The following values arevalid for the STOP option:

ALLStops all data collectors that are supported by the ACTVCTL command.

subtower_nameStops the data collectors for one or more of the following subtowers:v DB2v IMSv LIFELINEv VSAM

TAKEOVERMoves the Active/Active enterprise master NetView program to the system onwhich the ACTVCTL TAKEOVER command is issued.

Note: Issuing the ACTVCTL TAKEOVER command can cause unintendedresults for the Active/Active solution. For more information, see Switchingsolution components on controller systems in IBM Tivoli NetView for z/OSInstallation: Configuring the GDPS Active/Active Continuous Availability Solution.

ENABLESpecifies the component for which the NetView program can start the addressspaces, as follows:

TEMS Tivoli Enterprise Monitoring Server

NVAGTNetView for z/OS Enterprise Management Agent

Appendix B. Commands 103

||

|

|

||||

Note: Specifying only TEMS is the equivalent of specifying both TEMS andNVAGT.

Usage Notes

The ACTIVEACTIVE tower must be enabled in the CNMSTYLE member tosuccessfully run this command.

Example: Using ACTVCTL LISTINFO=LIFELINE

This example shows the results of issuing ACTVCTL LISTINFO=LIFELINEACTVCTL LISTINFO=LIFELINE

AQN007I DISPLAY ACTIVE/ACTIVE DATA COLLECTION INFORMATION--------------------------------------------------------------------------------Tower Name : Multi-site Workload LifelineStatus : Active , next data collection starts in 74 secondsTask Information : VOST: DSI#0008 Attach Name: LIFE0001Path : /var/sock/aqsmgmtAverage Time : < 1 SecondsMaximum Time : < 1 SecondsNumber Of Iterations : 38--------------------------------------------------------------------------------

ACTVLIFE (NCCF)Syntax

ACTVLIFE

►► ACTVLIFE ►

► ADVISORSAGENTSLBGROUPS LBIP = ip_addressLBSLBWRKLDS LBIP = ip_addressSERVERSSITES WORKLOAD = workload_name

ROLE = * WORKLOAD = *WRKLOADS

ROLE = QUERY WORKLOAD = workload_nameSTANDBY

►◄

Purpose of Command

The ACTVLIFE command displays information that is collected by the Multi-siteWorkload Lifeline Advisor product. The following information can be displayed:v Lifeline Advisorsv Lifeline Agentsv Load balancer groupsv Load balancersv Load balancer workloadsv Workload serversv Sitesv Workloads


||||||||||||||


ADVISORSDisplays the primary Multi-site Workload Lifeline Advisor that is used tocalculate the best site for routing new TCP/IP connections. If configured, thesecondary Lifeline Advisor is also displayed.

Lifeline Advisor data is returned in the multi-lined AQN020I message. To seethe format of the data that is returned by the AQN020I message, see the onlinehelp.

AGENTSDisplays all Multi-site Workload Lifeline Agents that gather server capacityand health information for registered servers and send data to the primaryLifeline Advisor.

Lifeline Agent data is returned in the multi-lined AQN021I message. To see theformat of the data that is returned by the AQN021I message, see the onlinehelp.

LBGROUPSDisplays group configuration information for the specified external loadbalancer.

Load Balancer Group data is returned in the multi-lined AQN022I message. Tosee the format of the data that is returned by the AQN022I message, see theonline help.

LBIP=ip_addressSpecifies the IP address of the load balancer for which you want to displayinformation.

LBSDisplays the external load balancers and sysplex distributors that are definedto load balance workloads.

Load Balancer data is returned in the multi-lined AQN023I message. To see theformat of the data that is returned by the AQN023I message, see the onlinehelp.

LBWRKLDSDisplays workload configuration information for the specified external loadbalancer or sysplex distributor.

Load Balancer Workload data is returned in the multi-lined AQN024I message.To see the format of the data that is returned by the AQN024I message, see theonline help.

ROLE= * | QUERY | STANDBYSpecifies the role of the workload.

* Both Active/Query and Active/Standby workloads are displayed. Therole of the workload determines the output:v If you specify an Active/Query workload name, only the

Active/Query workload is displayed.v If you specify an Active/Standby workload name, both the

Active/Standby and the associated Active/Query workloads aredisplayed.

QUERYOne or more Active/Query workloads are displayed.


||

|||

||

|||

||

STANDBYOne or more Active/Standby workloads are displayed.

SERVERSDisplays all servers that make up the defined workloads.

Workload server data is returned in the multi-lined AQN025I message. To seethe format of the data that is returned by the AQN025I message, see the onlinehelp.

SITESDisplays all sites for the specified workload. Workload site data is returned inthe multi-lined AQN026I message. To see the format of the data that isreturned by the AQN026I message, see the online help.

WORKLOAD=* | workload_nameSpecifies the workload name for which you want to display information:

* Specifies all workloads that are specified using the WRKLOADSkeyword.

workload_nameSpecifies which workloads are displayed.v For the SITES specification, site information for the specified

workload is displayed.v For the WRKLOADS ROLE=* specification, the role of the workload

determines the output:– If you specify an Active/Query workload name, only the

Active/Query workload is displayed.– If you specify an Active/Standby workload name, both the

Active/Standby and the associated Active/Query workloads aredisplayed.

v For the WRKLOADS ROLE=QUERY specification, the Active/Queryworkload with the specified name is displayed.

v For the WRKLOADS ROLE=STANDBY specification, theActive/Standby workload with the specified name is displayed.

WRKLOADSDisplays workloads that are defined to the Lifeline Advisor. The ROLE andWORKLOAD keywords specify which workloads are displayed.

Workload data is returned in the multi-lined AQN027I message. To see theformat of the data that is returned by the AQN027I message, see the onlinehelp.

Usage Notesv The ACTIVEACTIVE.LIFELINE subtower must be enabled in the CNMSTYLE

member to successfully run this command.v This command must be issued from the Active/Active enterprise master

NetView program. If this command is issued on the Active/Active controllersystem and Lifeline Advisor is running in the secondary role, the socketconnection for data collection fails.


||

||

|||

||

||

||

||

|||

||

||

|||

|||

ACTVREPL (NCCF)Syntax

ACTVREPL

►► ACTVREPL ►

►TYPE=* VIEW=SUMMARY

WORKLOAD= *workload_name TYPE= * VIEW= SUMMARY

DB2 COMMONIMS DETAILSVSAM

VIEW=COMMONSERVER= * TYPE= DB2

server_name IMS VIEW= COMMONVSAM DETAILS

SENDQ= *send_queue

RCVQ= *receive_queue

►

►INTERVAL=seconds

►◄

Purpose of Command

Note: This command is used only with the GDPS Active/Active ContinuousAvailability solution.

The ACTVREPL command can display information for IMS replication, Q (DB2)replication, and VSAM replication. The following information is displayed:v Summary information for all workloads, including single consistency group and

multiple consistency group workloadsv Common workload information that is sent by all replication products, including

capture data, apply data, or bothv Detailed IMS replication or VSAM replication workload informationv Q replication server informationv Q replication send and receive queue information for a specific workload


INTERVAL=secondsSpecifies the amount of time to delay before retrieving information a secondtime from the capture and apply servers. Many replication data fields, such asaverage latency, are calculated across an interval. This keyword enables thosefields to be calculated and displayed. If the INTERVAL keyword is notspecified, only values that apply to a single data collection are displayed. Therange is 1 - 300 seconds.

RCVQ=*|receive_queueDisplays information about the specified receive queue. An asterisk (*)specifies all receive queues. For details, see the AQN034I message.


|||||||

||

||

||

|

|

|||

SENDQ=*|send_queueDisplays information about the specified send queue. An asterisk (*) specifiesall send queues. For details, see the AQN033I message.

SERVER=*|server_nameDisplays information about the specified replication server or about workloadson the specified server. An asterisk (*) specifies all servers.

If VIEW=COMMON (the default), the display contains workload informationfor the workloads that run on the specified servers. For details, see theAQN030I message.

If VIEW=DETAILS, the following information is displayed:v For Q replication, server information for the specified servers and sites. For

details if a specific server is specified, see the AQN035I and AQN036Imessages. For details if * is specified, see the AQN050I and AQN051Imessages.

v For IMS and VSAM replication, detailed workload information for theworkloads that run on the specified server or servers. For details, see theAQN031I and AQN032I messages.

TYPE=*|DB2|IMS|VSAM (for WORKLOAD keyword)Specifies the type of replication data to retrieve as follows:* IMS replication, Q replication, and VSAM replication data. This is the

default value.DB2

Q replication dataIMS

IMS replication dataVSAM

VSAM replication data

TYPE=DB2|IMS|VSAM (for SERVER keyword)Specifies the type of replication data to retrieve as follows:DB2

Q replication dataIMS

IMS replication dataVSAM

VSAM replication data

VIEW=SUMMARY|COMMON|DETAILS (for WORKLOAD keyword)Specifies the type of information to display when the WORKLOAD keyword isspecified. For more information, see the WORKLOAD keyword.

COMMONDisplays replication workload information for the specified workload.

DETAILSDisplays the following information:v IMS replication: Detailed workload information for the specified

workloadv Q replication:

– Send and receive queue information for the specified workload– Capture and apply server information

v VSAM replication: Detailed workload information for the specifiedworkload


|||

|||

|||

|

||||

|||

|

|||

||

|

||

|||

||

|||||||||

SUMMARYDisplays summary information for replication workloads. This value is thedefault value.

VIEW=COMMON|DETAILS (for SERVER keyword)Specifies the type of information to display when the SERVER keyword isspecified. For more information, see the SERVER keyword.

COMMONDisplays replication workload information. This value is the default value.

DETAILSDisplays the following information:v IMS replication: Detailed workload information for the specified

workloadv Q replication: Capture and apply server informationv VSAM replication: Detailed workload information for the specified

workload

WORKLOAD=*|workload_nameDisplays information about the specified workload. An asterisk (*) specifies allworkloads.

If VIEW=COMMON, replication server workload information is displayed. Fordetails, see the AQN030I message.

If VIEW=DETAILS, the following information is displayed:v For Q replication, send and receive queue information for the specified

workloads. For details, see the AQN033I and AQN034I messages.v For IMS and VSAM replication, detailed workload information for the

specified workloads. For details, see the AQN031I and AQN032I messages.

If VIEW=SUMMARY (the default), summary information for the specifiedworkload or workloads is displayed. For details, see the AQN049I message.

Usage Notesv The ACTIVEACTIVE.REPLICATION subtowers (one or more of DB2, IMS, or

VSAM) must be enabled on the production systems in the CNMSTYLE memberto successfully run this command.

v This command must be issued from the Active/Active enterprise masterNetView program.

v If you run the ACTVREPL command at regular intervals by using a timer,coordinate the timer interval with the value of the INTERVAL operand (ifspecified). The timer interval must not be less than the INTERVAL operandvalue. If the values are the same, avoid very short intervals (for example, 1 or 2seconds). The command might not complete before another instance of thecommand is started. In this case, the second command is queued to process afterthe first one completes.

v The ACTVREPL command can fail because of a configuration problem on theproduction system. Check the NetView log for messages indicating:– No socket path definitions found (AQN001)– Duplicate socket path definitions (AQN006)– Socket path definitions not sequential (AQN041)

v NETVASIS must be specified if mixed case values are used for the WORKLOAD,SENDQ, or RCVQ keyword values. If information is requested for a mixed casename without specifying NETVASIS, the uppercase version of the input is used.


|||

||||||

|||

||

||

||

>>>>>>>

RESTYLE (NCCF)Syntax

RESTYLE

►► RESTYLE ACTACTALRTRCVNAMEARCHIVECBECOMMONCORRELATIONDISCOVERYDLADVIPAENTGHBIDLEOFFIPLOGLUCMEMSTOREMVSPARMNACMDNLDMNPDANRMNVSPOPDSPREFIXREXECRMTSYNRSHRTNDEFRTTTAMELVBVWEBWEBMENUWEBSITEXCF

►◄

Purpose of Command

The RESTYLE command reads the CNMSTYLE member and sets new valuesrelated to the keyword specified.


ACTACTRereads all ACTACT statements.

If replication data collection is stopped for a subtower, the RESTYLEACTACT command processes any socket path names and starts replicationdata collection for that subtower.

ALRTRCVNAMERereads the alert receiver name and recycles the CNMCALRT task.

ARCHIVERereads all ARCHIVE statements.


CBE Rereads the Common Base Event template file specified by theCBE.TEMPLATES statement in the CNMSTYLE member.

COMMONAll common global variables defined with the COMMON keyword areredefined. No variable definitions are removed.

CORRELATIONRereads all CORRELATION stem values and recycles the DSICORSV task.

DISCOVERYRereads DISCOVERY variables. This includes the intervals for theCOLLCTL command for the APPL, INTERFACES, and TELNET subtowers.

DLA Rereads all DLA stem values.

DVIPARereads all DVIPA statements.

ENT Updates the global variables associated with Enterprise support. The ENTdefinitions in the CNMSTYLE member are reprocessed. New systems arediscovered. Systems are dropped when CNMSTYLE is processed andsystems have been removed from CNMSTYLE.

GHB Rereads all GHB stem values and recycles DUIDGHB.

IDLEOFFReads or rereads all IDLEOFF stem values except for the autotask name,and resets any IDLEOFF settings. Starts IDLEOFF autotask if it is currentlyinactive.

IPLOGRereads all IPLOG stem values and recycles the DSIIPLOG task.

LUC Rereads all LUC stem values and recycles the domid LUC task.

MEMSTORERefreshes the MEMSTORE definitions. Removes from storage all memberscontrolled by the MEMSTORE component.

MVSPARMRereads the MVSPARM definitions from CNMSTYLE and recycles theCNMCSSIR task without loss of any automatable MVS messages.

NACMDRereads the parameters for the NACMD command. The NACMDcommand does not end and restart.

If the values for the NACMD.ROWS statement in the CNMSTYLE memberare changed, the NetView program must be recycled before the changestake effect.

NLDMRereads all NLDM stem values and recycles the three NLDM tasks.

NPDARereads all NPDA stem values and recycles the BNJDSERV task.

NRM Rereads the NetView Resource Manager parameters, and shuts downNetView Resource Manager. NetView Resource Manager is restarted ifINIT.NRM is Yes.

NVSP Rereads the NetView Web Services server (NVSOA) stem values andrecycles the AUTONVSP task.


OPDSPREFIXRereads the operator data set prefix. You must reissue OVERRIDEcommands for data sets using the prefix (set in LOGPROF1).

REXECRereads all REXEC stem values and recycles the DSIRXEXC task.

RMTSYNRereads all RMTSYN and RMTALIAS stem values and restarts the processof resolving any domain names in those definitions.

RSH Rereads all RSH stem values and recycles the DSIRSH task.

RTNDEFRereads the RTNDEF statements.

RTT Rereads all RTT stem values and recycles the DSIRTTR task.

TAMELRereads all TAMEL stem values and recycles the CNMTAMEL task.

VBV Rereads the parameters for the Visual BLDVIEWS server, except theautotask.

WEB Rereads all WEB stem values and recycles the DSIWBTSK task.

WEBMENUReprocesses the definitions in the CNMSTWBM member.

WEBSITERereads the definitions for the WEBSITES command.

XCF Updates global variables pertaining to XCF services. The state field isupdated for any variables that are exposed in the user state field. Many ofthe XCF variables allow customization of the actions that the NetViewprogram takes when it assumes the role of master NetView program.Takeover-related changes take effect the next time the NetView programassumes the master role in the sysplex.

If the XCF.RANK statement in the CNMSTYLE member is changed suchthat a NetView program is to enter or leave a group, the STARTXCFGROUP or STOP XCFGROUP command is issued for that DSIPLXnngroup. A change in rank results in an internal PLEXCTL RANK=new_rankcommand being issued.

If the XCF.GROUPNUM statement in the CNMSTYLE member is changed,the NetView program might generate STOP XCFGROUP and STARTXCFGROUP commands.

Example: Reloading the NPDA specifications

You can change the characteristics of the hardware monitor by changing NPDAstatements in the CNMSTUSR or CxxSTGEN member. For information aboutchanging CNMSTYLE statements, see IBM Tivoli NetView for z/OS Installation:Getting Started. After you make your changes, enter the following command to setthe new values and to restart the hardware monitor:RESTYLE NPDA


Appendix C. Messages

This section lists the messages that are used with the GDPS Active/ActiveContinuous Availability solution. The messages are sent to the NetView operator orthe authorized message receiver.

AQN Prefix MessagesThis section lists the AQN prefix messages.

AQN001I NO SOCKET PATH NAMES FOUNDFOR DATA SOURCE subtower_nameDOMAIN domain

Explanation: This message can be issued forreplication data collection or as a response to theACTVREPL command.

If the message is issued for replication data collection,no configured or dynamic socket path names werefound for the specified replication subtower for thespecified domain. The domain is the local NetViewdomain.

If the message is received as a response to anACTVREPL command, no configured socket pathnames were found for the specified replicationsubtower for the specified domain. The domain is aremote NetView domain.

A configured socket path name is one defined to theNetView program in a user-defined CNMSTGEN orCNMSTUSR member. A dynamic socket path name isone that the NetView program determines only throughmessage automation when a replication server starts. Adynamic socket path name is not also configured.

Message Variables

subtower_nameFor the ACTIVEACTIVE REPLICATIONsubtower:v DB2v IMSv VSAM

domain The NetView domain.

System action: If the message is issued for replicationdata collection, then data collection is stopped for thespecified subtower.

If the message is issued as a response to theACTVREPL command, the command fails for thespecified subtower.

System programmer response: Verify that replicationdata collection is enabled for the specified subtower. Ifit is not enabled, comment out the subtower name inthe user-defined CNMSTGEN or CNMSTUSR member,and then recycle the NetView program.

Verify that the socket path names are configured for thespecified replication subtower. If you update the socketpath names, issue the RESTYLE ACTACT command.

AQN002I DATA COLLECTION FAILED FORDATA SOURCE subtower_name, SOCKETPATH NAME path

Explanation: The NetView program attempted toconnect to the specified socket path name for thespecified subtower, and the connection failed.

Message Variables


path The configured or dynamic socket path name

A configured socket path name is defined tothe NetView product in a user-definedCNMSTGEN or CNMSTUSR member. Adynamic socket path name is determined bythe NetView product through messageautomation when a replication server starts. Adynamic socket path name is not alsoconfigured.

System action: If all socket path names fail for asubtower, data collection for that subtower is stopped.If a RESTYLE ACTACT is issued or a message from areplication server is received with an active socket pathname, data collection is restarted.

Operator response: If the replication server is notstarted, this message can be ignored.

After the replication server is started, verify that datacollection started for the specified socket path name byusing the ACTVCTL LISTINFO command.

System programmer response: Verify that the socketpath name is configured correctly for the specifiedreplication subtower, and issue a RESTYLE ACTACTcommand. The updated socket path name is read at thenext data collection interval.


|

AQN003I LOCAL DOMAIN domain_name NOWENTERPRISE MASTER FORACTIVEACTIVE

Explanation: This message is issued when theNetView program becomes an enterprise master and itsenterprise master configuration that is specified on theENT.TYPE statement includes ACTIVEACTIVE.

Message Variables

domain_nameName of the local NetView domain

AQN004E ENT.ACTIVEACTIVE.ROLESTATEMENT REQUIRED IFACTIVEACTIVE SPECIFIED ONENT.TYPE

Explanation: This message is issued when a requiredENT.ACTIVEACTIVE.ROLE statement is not coded inthe CNMSTYLE member. If you specifyACTIVEACTIVE as the type of enterprise masterNetView program on the ENT.TYPE statement, thenyou must also specify the ENT.ACTIVEACTIVE.ROLEstatement.

When the AQN004I message is issued, processing ofENT.SYSTEMS statements ends. The NetView programdoes not become an enterprise master.

Operator response: Notify the system programmer.

System programmer response:

Review and update the ENT.TYPE andENT.ACTIVEACTIVE.ROLE statements in theCNMSTYLE member.

AQN006I DUPLICATE subtower_name, SOCKETPATH NAME path IGNORED

Explanation: A duplicate socket path name for thespecified subtower was specified and is ignored.

For data collection, the duplicate paths are ignored inorder to prevent duplicate data collection.

For the ACTVREPL command, no production systempath configuration information is forwarded to thecontroller system for the particular data source (DB2,IMS, or VSAM) and function (capture or apply).

Message Variables


path The configured socket path name

A configured socket path name is defined tothe NetView program in a user-definedCNMSTGEN or CNMSTUSR member.

System action: For data collection, one connection willbe attempted for the specified socket path name.

For ACTVREPL, the command will fail for the NetViewdomain for the specified data source (DB2, IMS, orVSAM) and function (capture or apply).

Operator response: Notify the system programmer ofthe duplicate socket path name.

System programmer response: Change the duplicatesocket path name in the CNMSTGEN or CNMSTUSRsample.

AQN007I DISPLAY ACTIVE/ACTIVE DATACOLLECTION INFORMATION

Explanation: This message is received when theACTVCTL LISTINFO command is issued. Theinformation provided is based on the value specifiedfor the LISTINFO keyword. There can be multipleentries for the replication subtowers because there canbe multiple replication servers for each data source(DB2, IMS, VSAM) on each z/OS image.

The AQN007I message lists the following information:

Tower name Specifies the Active/Active tower or subtowerdescriptive name

Status Indicates whether data collection is active orinactive. If multiple replication servers areconfigured for each data source, and aconnection to at least one data source issuccessful, the status is Active. The samplinginterval is the same for all replication serversfor each data source.

Path Specifies the socket path name on which datacollection occurs.

Task informationSpecifies the virtual OST (VOST) and theassociated attach name of the VOST on whichdata collection runs. Data collection control(sampling interval) is done at the configuredautotask, but the actual data collection is doneon a VOST.

Average timeSpecifies the average amount of time incurredfor data collection across intervals. This valueresets if data collection is stopped andrestarted.

Maximum timeSpecifies the maximum amount of time for asingle data collection across one samplinginterval. This value resets if data collection isstopped and restarted. If this value is larger

AQN003I • AQN007I


|

|

|||

||||

|

|||

|

than your sampling interval, considerincreasing the sampling interval.

Number of iterationsSpecifies the number of times data collectionoccurred since it was started. This value resetsif data collection is stopped and restarted.

Operator response: Contact your system programmerif a data collection is inactive for a specified socket pathname, and if it should be active.

System programmer response: Use the information inthis message to set an optimal data collection interval.You can also use this message for diagnostic purposes.

Usage Note: If there are multiple socket path namesfor a replication data source, and data collection failedfor a particular socket path name, Task Informationfields display N/A, and the statistics display zero (0).

AQN008I REPLICATION SERVER SITUATIONOR POLICY NAME IS name

Explanation: This is the first line of a multilinemessage for displaying information related toreplication server situations. This message is issued as anotification for automation by the GeographicallyDispersed Parallel Sysplex® (GDPS) solution. The datalines for this message provide keyword and value pairsthat provide detailed attribute information related tothe situation.

Message Variables

name The message variable is an abbreviated versionof the situation or policy name:

APPSERVERSTATUSIndicates that theNAS_AA_RS_AppServerStatussituation fired

CAPSERVERSTATUSIndicates that theNAS_AA_RS_CapServerStatussituation fired

DB2WORKLOADSTATEIndicates that theNAS_AA_RS_DB2WorkloadStatesituation fired

IMSWORKLOADSTATEIndicates that theNAS_AA_RS_IMSWorkloadStatesituation fired

LATENCYEXCEEDEDIndicates that theNAS_AA_RS_LatencyExceededsituation fired

LATENCYRESETIndicates that theNAS_AA_RS_LatencyExceeded

situation was resolved as defined inthe NAP_AA_RS_LatencyReset policy

VSAMWORKLOADSTATEIndicates that theNAS_AA_RS_VSAMWorkloadStatesituation fired

For more information about the situations andthe attributes related to the situations, refer tothe NetView for z/OS Enterprise ManagementAgent online help or the IBM Tivoli NetView forz/OS User's Guide: NetView EnterpriseManagement Agent.

AQN009I DATA COLLECTION FORsubtower_name RESTARTED

Explanation: Data collection for the specifiedsubtower was stopped and restarted. This action occurswhen data collection is already started for a replicationserver for the specified subtower, and anotherreplication server for the specified subtower is started.The data collection stop and start allows data from thenew server to be immediately available without waitingfor the next sampling interval.

Message Variables


AQN010I DATA COLLECTION FORsubtower_name ALREADY STARTED

Explanation: Data collection for the specifiedsubtower was already started. The command is notprocessed.

Message Variables

subtower_nameFor the ACTIVEACTIVE subtower:v DB2v IMSv LIFELINEv VSAM

Operator response: Use the ACTVCTL LISTINFOcommand to display information about Active/Activedata collection.

AQN011I DATA COLLECTION FORsubtower_name ALREADY STOPPED

Explanation: Data collection for the specifiedsubtower was already stopped. The command is notprocessed.

Message Variables

AQN008I • AQN011I

Appendix C. Messages 115

||||

|

|

subtower_nameFor the ACTIVEACTIVE tower:v DB2v IMSv LIFELINEv VSAM

Operator response: Use the ACTVCTL LISTINFOcommand to display information about Active/Activedata collection.

AQN012I cmd COMMAND NOT PROCESSED.CURRENT VALUE interval FORsubtower_name MATCHES CHANGEVALUE.

Explanation: An ACTVCTL RESET command wasissued with the same interval value that is currentlybeing used for data collection for the specifiedsubtower. The command ends with no changes.

Message Variables

cmd The command that was issued

interval The data collection sampling interval for thespecified subtower


Operator response: Specify a different interval value.

AQN013I DATA COLLECTION INTERVAL FORsubtower_name SET TO interval

Explanation: The data collection sampling intervalwas changed for the specified subtower using theACTVCTL RESET command.

Message Variables


interval The data collection sampling interval for thespecified subtower

System action: When data collection is active for thespecified subtower and the sampling interval ischanged, data collection is stopped and thenimmediately restarted. When data collection is inactivefor the specified subtower and the sampling interval ischanged, the new interval is used when data collectionis started.

AQN014E ACTIVEACTIVE.LIFELINE SUBTOWERREQUIRES A VALUE OFACTIVEACTIVE ON THE ENT.TYPESTATEMENT

Explanation: This message is issued during enterprisemaster processing on an Active/Active controllersystem. This error occurs when anACTIVEACTIVE.LIFELINE subtower is enabled and anENT.TYPE statement is not found in CNMSTYLEprocessing or the value for the ENT.TYPE statement doesnot include ACTIVEACTIVE.

System action: Enterprise master processing is ended.

Operator response: Contact your system programmer.

System programmer response: For Active/Activecontroller systems, you must code an ENT.TYPEstatement that includes ACTIVEACTIVE.

AQN015E ACTIVEACTIVE ENTERPRISEMASTER PROCESSING FAILED

Explanation: This message is issued during enterprisemaster processing on an Active/Active controllersystem. This error occurs for the followingconfiguration errors:v Errors in CNMSTYLE configuation, such as the

following:– The ENT.TYPE statement specifies

ACTIVEACTIVE, but theACTIVEACTIVE.LIFELINE tower is not enabled.

– The ACTIVEACTIVE.LIFELINE tower is enabled,but no ENT.TYPE statement is present.

– No valid types are specified by the ENT.TYPEstatement.

– The ENT.TYPE statement is present, but noENT.SYSTEMS statements are present.

– The ENT.ACTIVEACTIVE.ROLE statementspecifies a value that is not valid.

– The ENT.TYPE statement specifiesACTIVEACTIVE, but noENT.ACTIVEACTIVE.ROLE statement is present.

v The NetView program is not in the master role in itsXCF group.

v Another NetView program is the Active/Activeenterprise master NetView program.

System action: Enterprise master processing is ended.


System programmer response: Review the NetViewlog for additional error messages that might identifythe cause of the problem.

AQN016A Reply Yes if Tivoli EnterpriseMonitoring Server is inactive on systemsystem. Otherwise, reply No.

Explanation: This message is issued when the valuefor the ACTACT.BKTEMS.Enable statement in theCNMSTYLE member is Yes. For more information

AQN012I • AQN016A


|

|

|

||||||||||||||||

about when this message is issued, see the descriptionfor the ACTACT.BKTEMS.Enable statement in theCNMSTLIF include member.

Message Variables

system The z/OS image name of the primarycontroller system on which the hub TivoliEnterprise Monitoring Server (monitoringserver) resides. The system is defined to theNetView program on theACTACT.PriCont.System statement in theCNMSTYLE member.

System action: If the reply is Yes, the monitoringserver is started using the startup procedure that isspecified on the ACTACT.BKTEMS.procStr statement inthe CNMSTYLE member.

Operator response: Respond as follows:

1. If any of the following conditions are true, replyYes:

v The monitoring server on the specified system isnot active or will be stopped in the immediatefuture.

v The specified system is not available.

v The Tivoli Enterprise Portal Server (portal server)lost contact with the monitoring server on thespecified system.

When you reply YES, the monitoring server isstarted using the startup procedure that isspecified on the ACTACT.BKTEMS.procStrCNMSTYLE statement. If the portal server is stillcommunicating with the monitoring server on thespecified system, it does not connect to thismonitoring server, and there is no data from thisActive/Active enterprise master NetViewprogram in the portal server.

2. If the monitoring server on the specified system isstill active and communicating with the portalserver, reply No.

3. Contact your system programmer.

System programmer response: Determine the cause ofthe outage.

AQN017I domain ON system IS ALREADY ANACTIVEACTIVE ENTERPRISEMASTER NETVIEW

Explanation: The NetView program on which anACTVCTL TAKEOVER command was issued is alreadyan Active/Active enterprise master NetView program.

Message Variables

domain The NetView domain

system The z/OS image name of the system on whichthis NetView program resides

System action: The ACTVCTL TAKEOVER commandfails.

Operator response: Do not issue the ACTVCTLTAKEOVER command unless directed to do so by yoursystem programmer. Issuing the ACTVCTL TAKEOVERcommand can cause unintended results from theActive/Active solution standpoint. Refer to the section"Switching solution components on controller systems"in the IBM Tivoli NetView for z/OS Installation:Configuring the GDPS Active/Active ContinuousAvailability Solution for more information.

AQN018I Tivoli Enterprise Monitoring Serverprocstr is already active. Results may beunpredictable.

Explanation: The Tivoli Enterprise Monitoring Server(monitoring server) is already active on the backupcontroller. If the monitoring server is active on both theprimary and backup controller z/OS images, you canhave unpredictable results in your NetViewActive/Active Sites workspaces on the Tivoli EnterprisePortal.

Message Variables

procstr The startup procedure that is specified on theACTACT.BKTEMS.procStr statement in theCNMSTYLE member.

System programmer response: Make sure that themonitoring server is only started on one controllersystem at a time. Except for an outage, the hubmonitoring server must run on the primary controller.

AQN019E CONNECTION FAILURE TO server ONSOCKET PATH path. REPORTINGMODULE=module_name. RC:return_code REASON: reason

Explanation: This message is a result of a failure toestablish or maintain a data collection connection on anActive/Active server.

Message Variables

server The type of server (DB2, IMS, LIFELINE, orVSAM)

path The UNIX path that was used

module_nameThe control section (CSECT) name where anerror condition was detected

return_codeThe return code

reason Description of the return code:v Attach command failurev Command authorization failurev Connection already startedv Connection already stoppedv Could not connect socketv Initialization subroutine failurev Invalid action parameter valuev Invalid socket path name

AQN017I • AQN019E


|||||||||

||

v Invalid tower/subtower configurationv Invalid type parameter valuev LRCE storage not foundv No text availablev Should not occur condition encounteredv Unable to obtain storagev Unable to push LRCE storagev Unable to obtain UNIX socketv UNIX socket closedv Unspecified command syntax error

AQN020I DISPLAY OF LIFELINE ADVISORS

Explanation: This multiline message is issued inresponse to the ACTVLIFE ADVISORS command. Itconsists of one header line, three label lines, and one ormore data lines, with each data line providinginformation about a Lifeline Advisor.

Each data line includes the following information:

ColumnsDescription

1-8 The name of the z/OS operating system wherethe Multi-site Workload Lifeline Advisorresides.

12-26 The IPv4 address of the Multi-site WorkloadLifeline Advisor.

30-74 The IPv6 address of the Multi-site WorkloadLifeline Advisor.

78-86 The role of the Multi-site Workload LifelineAdvisor. The following values are valid:v PRIMARYv SECONDARY

90-94 The number of active load balancers andsysplex distributors that are registered withthe Multi-site Workload Lifeline Advisor. Thisattribute is not applicable for secondaryMulti-site Workload Lifeline Advisors.

102-111 The number of Multi-site Workload LifelineAgents that are connected to the Multi-siteWorkload Lifeline Advisor. This attribute is notapplicable for secondary Multi-site WorkloadLifeline Advisors.

System action: The ACTVLIFE ADVISORS commandprocessing is complete.

AQN021I DISPLAY OF LIFELINE AGENTS

Explanation: This multiline message is issued inresponse to the ACTVLIFE AGENTS command. Itconsists of one header line, three label lines, and one ormore data lines, with each data line providinginformation about a Lifeline Agent.


ColumnsDescription

1-45 The IP address of the Multi-site WorkloadLifeline Agent.

49-56 The z/OS image name where the Multi-siteWorkload Lifeline Agent resides.

60-67 The name of the site (for example, the sysplexname) where the Multi-site Workload LifelineAgent resides.

71-80 The number of server applications that arebeing monitored by this Multi-site WorkloadLifeline Agent.

84-91 The state of the Multi-site Workload LifelineAgent. The following values are valid:v ACTIVEv INACTIVE

System action: The ACTVLIFE AGENTS commandprocessing is complete.

AQN022I DISPLAY OF LOAD BALANCERGROUPS FOR LOAD BALANCER ATIP ADDRESS ipaddress

Explanation: This multiline message is issued inresponse to the ACTVLIFE LBGROUPS command. Itconsists of one header line, three label lines, and one ormore data lines, with each data line providinginformation about a load balancer group.


ColumnsDescription

1-45 The IP address for a server application that isregistered for the group.

49-53 The port number for a server application thatis registered for the group.

57-311 The name of the group that is registered to theload balancer. For internal load balancers(sysplex distributors), this attribute does notapply.

Message Variables

ipaddressThe IPv4 or IPv6 address of the load balancer.

System action: The ACTVLIFE LBGROUPS commandprocessing is complete.

AQN023I DISPLAY OF LOAD BALANCERS

Explanation: This multiline message is issued inresponse to the ACTVLIFE LBS command. It consists ofone header line, three label lines, and one or more datalines, with each data line providing information about aload balancer.


AQN020I • AQN023I


ColumnsDescription

1-45 The IP address of the load balancer.

49-60 The role of the load balancer. The followingvalues are valid:v 1st TIERv 2nd TIERv UNKNOWNv INTERMED

Note: The 1st TIER and 2nd TIER values donot pertain to the TIER1 and TIER2 keywordsthat are provided by the z/OSCommunications Server VIPADYNAMICstatement.

64-71 The status of the load balancer. The followingvalues are valid:v ACTIVEv INACTIVE

75-93 The type of load balancer. The followingvalues are valid:v EXTERNALv SYSPLEX DISTRIBUTOR

97-102 The number of groups that are registered bythe load balancer. For internal load balancers(sysplex distributors), this attribute does notapply.

System action: The ACTVLIFE LBS commandprocessing is complete.

AQN024I DISPLAY OF LOAD BALANCERWORKLOADS FOR LOAD BALANCERAT IP ADDRESS ipaddress

Explanation: This multiline message is issued inresponse to the ACTVLIFE LBWRKLDS command. Itconsists of one header line, three label lines, and one ormore data lines, with each data line providinginformation about a load balancer workload.


ColumnsDescription

1-64 The name of the workload.

72-74 An indication of whether the serverapplications on the active site are availableand if these server applications are able tohandle additional requests for this workload.The following values are valid:

v YES: The server applications for thisworkload are available and able to handlenew workload requests.

v NO: The server applications for thisworkload are either not available or not ableto handle new workload requests.

83-127 The IP address for a server application that isregistered for the group.

131-135 The port number for a server application thatis registered for the group.

Message Variables

ipaddressThe IPv4 or IPv6 address of the load balancer.

System action: The ACTVLIFE LBWRKLDS commandprocessing is complete.

AQN025I DISPLAY OF WORKLOAD SERVERS

Explanation: This multiline message is issued inresponse to the ACTVLIFE SERVERS command. Itconsists of one header line, three label lines, and one ormore data lines, with each data line providinginformation about a workload server.


ColumnsDescription

1-8 The MVS job name of the server application.

12-56 The IPv4 or IPv6 address of a serverapplication that is defined for the workload.

60-64 The number of the port on which the serverapplication listens.

68-75 The z/OS image name where the serverapplication resides.

79-86 The name of the site (for example, the sysplexname) where the server application resides.

90-97 The state of the server application. Thefollowing values are valid:v ACTIVEv INACTIVE

101-102 The net weight for this server applicationrelative to other server instances that aredefined for this workload on the same site.This value is calculated by applying theCommunications Server health as a percentageof the WLM weight for this server. It is thennormalized against the other server instances(active on this same site) that are defined forthis workload. If the value for this field isblank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

110-111 The Workload Manager (WLM) weight valuefor the server application. This value is ameasure of how well the server application isimplementing the WLM policies of the serverapplication. It represents the amount ofdisplaceable processor capacity based on theimportance of the server application ascompared to other server instances (active on

AQN024I • AQN025I


|

|

|

|

|

this same site) that are defined for thisworkload. The WLM weight is a compositeweight and includes the sum of the CP, zAAP,and zIIP weights. If the value for this field isblank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

119-122 The rate of abnormal transaction completionsper 1000 transactions for this serverapplication. This value is optionally suppliedby server applications to the WorkloadManager, which uses it to adjust the reportedWLM weight. If the value for this field isblank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

134-137 The health indicator of the server application.This indicator is available only for servers thatprovide this information to WorkloadManager. For servers that are healthy or arenot reporting this information, a value of 100is returned. This value is treated as apercentage and is used to adjust the reportedWLM weight. If the value for this field isblank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

143-144 The CPU factor in the WLM weight. This isthe amount of displaceable general CPUcapacity based on the importance of the serverapplication as compared to other serverinstances (active on the same site) that aredefined for this workload and modified by theproportion of general CPU capacity that isused by this server, as compared to zAAP andzIIP processors. If the value for this field isblank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

152-153 The zAAP factor in the WLM weight. This isthe amount of displaceable zAAP capacitybased on the importance of the serverapplication as compared to other serverinstances (active on this same site) that aredefined for this workload and modified by theproportion of zAAP capacity that is used bythis server, as compared to general CPU andzIIP processors. If the value for this field isblank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

161-162 The zIIP factor in the WLM weight. This is theamount of displaceable zIIP capacity based onthe importance of the server application ascompared to other server instances (active onthis same site) that are defined for thisworkload and modified by the proportion ofzIIP capacity that is used by this server, as

compared to general CPU and zAAPprocessors. If the value for this field is blank,look in the NetView log for the AQN029Imessage to see if the value is out of range.

170-173 The health of the server application asdetermined by z/OS Communications Server.The value is calculated based on how well theserver keeps up with new connection requestson the backlog of the server, how well theserver establishes new connections, andwhether the server drops connections. Thisvalue is treated as a percentage and is used toadjust the net weight. If the value for this fieldis blank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

System action: The ACTVLIFE SERVERS commandprocessing is complete.

AQN026I DISPLAY OF WORKLOAD SITES FORWORKLOAD workload_name

Explanation: This multiline message is issued inresponse to the ACTVLIFE SITES command. It consistsof one header line, three label lines, and one or moredata lines, with each data line providing informationabout a workload site.


ColumnsDescription

1-8 The name of the site where the workload canbe distributed.

12-23 The routing state of the workload on this site.The following values are valid:v ACTIVE: If the workload is active on this

site, this is the active site.v QUIESCED: If the workload is quiesced on

this site, this is the standby site.

Note: If the workload is quiesced on bothsites, the workload on the active site mightnot be activated yet.

27-28 The routing weight of the workload on thissite. For an Active/Standby workload, theworkload routing weight is 0 for the standbysite or 1 for the active site. For anActive/Query workload, the workload routingweight is in the range 0 - 64, whichcorresponds to the current routing distributionto this site

38-40 An indication of whether the site is preferredwhen the Role attribute value isACTIVE/QUERY and the workload routingtype, as defined to the Multi-site LifelineWorkload product, is DYNAMIC. Otherwisethis value does not apply and is set to N/A.The following values are valid:

AQN026I


||||||||

||||||||

v Yesv Nov N/A

50-63 The role of the workload. The following valuesare valid:v ACTIVE/STANDBYv ACTIVE/QUERY

Message Variables

workload_nameThe workload name for which the siteinformation is displayed.

System action: The ACTVLIFE SITES commandprocessing is complete.

AQN027I DISPLAY OF role WORKLOADS FORWORKLOAD NAME workload_name

Explanation: This multiline message is issued inresponse to the ACTVLIFE WRKLOADS command. Itconsists of one header line, three label lines, and one ormore data lines, with each data line providinginformation about a workload.


ColumnsDescription


68-81 The overall status of the workload. This valueis calculated from the workload status that isreported by the Multi-site Workload Lifelineproduct and the workload status that isreported by the replication server that isassociated with the workload. The followingvalues are valid:v SATISFACTORY: Both statuses are

satisfactory.v UNSATISFACTORY: At least one of the

statuses is unsatisfactory.

85-96 The monitoring component that detected afailure when the Workload Status attributevalue is UNSATISFACTORY. The followingvalues are valid:v BOTHv REPLICATIONv ROUTING

The value of NONE is specified when theWorkload Status attribute value isSATISFACTORY.

100-113 The role of the workload. The following valuesare valid:v ACTIVE/QUERYv ACTIVE/STANDBY

117-122 The number of servers that make up theworkload.

130-145 The failure state of the workload as reportedby the Multi-site Workload Lifeline productwhen the Workload Status attribute value isUNSATISFACTORY and the Detected Failureattribute value is either BOTH or ROUTING.The following values are valid:v QUIESCED: The Multi-site Workload

Lifeline product is reporting anunsatisfactory workload status becauseeither the Active/Standby workload or theActive/Query workload is quiesced on bothsites.

v SITE FAILURE: The Multi-site WorkloadLifeline product is reporting anunsatisfactory workload status because thesite where the workload is active failed.– For Active/Standby workloads, the

Active site failed.– For Active/Query workloads, the site or

sites where the workload is active failed.v SITE NOT OPTIMAL: The Multi-site

Workload Lifeline product is reporting anunsatisfactory workload status because anActive/Query workload with a workloadrouting type of STATIC is being routed to asite that is not optimal.– One of the sites had a workload or site

failure but connections for the workloadare still being routed to that site.

– The maximum replication latencythreshold was exceeded for the workloadbut connections for the workload are stillbeing routed to the Standby site.

v WORKLOAD FAILURE: The Multi-siteWorkload Lifeline product is reporting anunsatisfactory workload status because noserver applications are available for theworkload.– For Active/Standby workloads, no

servers are available on the site where theworkload connections are being routed.

– For Active/Query workloads, no serversare available on the site or sites wherethe workload connections are beingrouted.

A value of N/A is displayed when either ofthe following conditions is true:v The Workload Status attribute value is

SATISFACTORY.v The Workload Status attribute value is

UNSATISFACTORY and the DetectedFailure attribute value is REPLICATION.

149-164 The routing type of the workload when theRole attribute value is ACTIVE/QUERY.Otherwise this value does not apply and is setto N/A. The following values are valid:v STATIC: Indicates that query transactions

are routed to each of the sites based on theconfigured percentages.

AQN027I


|||

|||||

||

|

||||||||||||||||||||||||||||||||||||||||||||||

|||||||

||||||||

v DYNAMIC: Indicates that querytransactions are routed based on the healthof the server applications, the availablecapacity of the systems that make up thesite, and the average replication latency ofthe associated Active/Standby workload.

168-183 The latency state of the workload when theRole attribute value is ACTIVE/QUERY.Otherwise this value does not apply and is setto N/A. The following values are valid:v ACUTEv CONSTRAINEDv CRITICALv NORMALv UNKNOWN

187-191 The number of Active/Query workloads thatare associated with this Active/Standbyworkload when the Role attribute value isACTIVE/STANDBY. Otherwise this value doesnot apply and is set to N/A. The number ofActive/Query workloads that can beassociated with an Active/Standby workloadis 0, 1, or 2.

202-265 The name of the Active/Standby workloadthat is associated with this Active/Queryworkload when the Role attribute value isACTIVE/QUERY. Otherwise this value doesnot apply and is set to N/A.

Message Variables

role The role of the workload. The following valuesare valid:

v ALL: Indicates that the ROLE keyword isnot specified or that ROLE=* is specified.

v Active/Standby: Indicates thatROLE=STANDBY is specified.

v Active/Query: Indicates that ROLE=QUERYis specified.

workload_nameThe name of the workload as specified for theWORKLOAD keyword. A value of * indicatesthat the WORKLOAD keyword is not specifiedor that WORKOAD=* is specified.

System action: The ACTVLIFE WRKLOADScommand processing is complete.

AQN028I SOCKET PATH NAME path NOTCONFIGURED FOR subtower_name

Explanation: A message was received from IMS orVSAM replication indicating that an interface for datacollection was started, but the socket path name in themessage is not configured to the NetView program.The socket path name must be configured to theNetView program for data collection to start.

Message Variables

path The socket path name.

subtower_nameFor the ACTIVEACTIVE tower, IMS/VSAM

System programmer response: Configure the specifiedsocket path name to the NetView program and thenissue the RESTYLE ACTACT command.

AQN029I UNEXPECTED VALUE value RECEIVEDFOR fieldname FOR DATA SOURCEsubtower_name

Explanation: This message is written to the NetViewlog for the following conditions:

v As a response to an ACTVLIFE or ACTVREPL commandwhen the data value for the specified field is out ofrange.

A message is issued for each field in the messageoutput for which the data value is invalid.

v As a response to invalid information in a subvector31, subfield 30, that is generated from an EventIntegration Facility (EIF) event that is sent from areplication product

Message Variables

value The data value that is out of range.

fieldnameThe field name for which the data value is outof range.

subtower_nameFor the ACTIVEACTIVE tower:v DB2v IMSv LIFELINEv VSAM

If a value of unknown is specified, the NetViewprogram encountered an EIF event that had adata source attribute missing or processing ofan alert ended before the data source wasknown.


If the message is issued as a result of issuing anACTVLIFE or ACTVREPL command, contact IBM SoftwareSupport with the information in the message.

If the message is issued with Subfield_30 for the fieldname, contact IBM Software Support for the specifiedreplication product.

AQN030I DISPLAY OF REPLICATION SERVERWORKLOADS workload_name FORDATA SOURCE type

Explanation: This multiline message is issued inresponse to the following commands:

AQN028I • AQN030I


||||||

||||||||||

|||||||||

||||||

|

|

||||

|

|||||

|

|||

|||

v ACTVREPL SERVER=* | server_job_nameVIEW=COMMON

Replication server workload information for thespecified server or servers is displayed.

v ACTVREPL WORKLOAD=* | workload_nameVIEW=COMMON

Replication server workload information for thespecified workload or workloads is displayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about a replication server workload.


ColumnsDescription


68-75 The type of workload. The following valuesare valid:v DB2v IMSv VSAM

79-88 The average latency is the average elapsedtime in milliseconds between the time thattransactions were committed to the sourcetable or database and the time thattransactions were committed to the target tableor database. This average includes only thetransactions that were processed during thelast sampling interval.

92-108 The date and time that the NetView programreceived the data from the capture server forthis workload.

112-131 The state of the workload as determined bythe capture server.

When the value of Workload Type is DB2, thefollowing values are valid:v INACTIVEv REPLICATE CONTINUOUS

When the value of Workload Type is IMS orVSAM, the following values are valid:v DESCRIBEv ENDING CONTROLLEDv ENDING IMMEDIATELYv ERRORv INACTIVEv REPLICATE CONTINUOUSv STARTING

135-142 The job name of the capture server.

149-152 The address space ID of the capture server.This is a four-digit hexadecimal number.

163-170 The status of the NetView data collectionconnection to the capture server. The followingvalues are valid:

v ACTIVEv INACTIVE

179-185 The z/OS image name of the capture server.

192-199 The name of the capture site (sysplex).

204-223 The cumulative total number of bytes thatwere sent to the target server.

227-246 The cumulative total number of transactionsthat were sent to the target server.

250-269 The cumulative total number of rows thatwere sent to the target server.

273-282 The average capture latency is the averageelapsed time in milliseconds between the timethat transactions were committed to the sourcetable or database and the time thattransactions were sent to the target server. Thisaverage includes only the transactions thatwere processed during the last samplinginterval.

When the value of Workload Type is DB2,average capture latency is the average elapsedtime in milliseconds between the time thattransactions were committed to the sourcetable and the time that the Q Capture programputs the last message for the transactions onthe send queue.

When the value of Workload Type is IMS,average capture latency is the average elapsedtime in milliseconds between the time that atransaction was committed to the sourcedatabase and the time that the transaction wassent to the target server.

291-300 The average network latency is the averageelapsed time in milliseconds between the timethat transactions were sent to the target serverand the time that the target server receivedthem. This average includes only thetransactions that were processed during thelast sampling interval.

When the value of Workload Type is DB2,average network latency is the average elapsedtime in milliseconds between the time that theQ Capture program put messages on the sendqueue and the time that the Q Apply programgot them from the receive queue.

When the value of Workload Type is IMS,average network latency is the average elapsedtime in milliseconds between the time that atransaction was sent to the target server andthe time that the transaction was received bythe target server.

309-325 The date and time that the NetView programreceived the data from the apply server forthis workload.

AQN030I


||

||

||

||

|

||

329-348 The state of the workload as determined bythe apply server.

When the value of Workload Type is DB2, thefollowing values are valid:v INACTIVEv REPLICATE CONTINUOUS

When the value of Workload Type is IMS orVSAM, the following values are valid:v DESCRIBEv ENDING CONTROLLEDv ENDING IMMEDIATELYv ERRORv INACTIVEv REPLICATE CONTINUOUSv STARTING

352-359 The job name of the apply server.

366-369 The address space ID of the apply server. Thisis a four-digit hexadecimal number.

380-387 The status of the NetView connection to theapply server. The following values are valid:v ACTIVEv INACTIVE

396-403 The z/OS image name of the apply server.

409-416 The name of the apply site (sysplex).

421-440 The cumulative total number of bytes thatwere received by the target server.

444-463 The cumulative total number of transactionsthat were received by the target server.

467-486 The cumulative total number of rows thatwere received by the target server.

490-506 A time stamp that represents the point in timeat which all transactions have been applied tothe target without gaps that might result fromparallel apply.

510-529 The average apply latency is the averageelapsed time in milliseconds between the timethat transactions were received by the targetserver and the time that transactions werecommitted to the target data source. Thisaverage includes only the transactions thatwere processed during the last samplinginterval.

When the value of Workload Type is DB2,average apply latency is the average elapsedtime in milliseconds between the time that theQ Apply program read transactions from thereceive queue and the time that they werecommitted to the target.

When the value of Workload Type is IMS,average apply latency is the average elapsedtime in milliseconds between the time that atransaction was received by the target serverand the time that the processing of the

transaction was completed by the databasemanagement system (DBMS).

533-537 The number of consistency groups that makeup the workload as defined by the replicationproduct.

541-604 The name of the consistency group. Aconsistency group is a single capture andapply server pair for a workload.

Message Variables

workload_nameThe name or asterisk (*) as specified on theACTVREPL WORKLOAD command. Anasterisk indicates that the WORKLOADkeyword was not specified or that WORKLOAD=*was specified.

type The data source for which replication serverworkload information is displayed. Thefollowing values are valid:v * (indicates that the TYPE keyword was not

specified or that TYPE=* was specified)v DB2v IMSv VSAM

System action: The ACTVREPL SERVER andACTVREPL WORKLOAD command processing iscomplete.

AQN031I DISPLAY OF type CAPTUREWORKLOAD DETAILS FORWORKLOAD workload_name


v ACTVREPL SERVER=* | server_job_name TYPE=typeVIEW=DETAILS

Detailed workload information for all workloads onthe specified capture server or servers is displayed.

v ACTVREPL WORKLOAD=* | workload_name TYPE=*| type VIEW=DETAILS

Detailed workload information for the specifiedworkload or workloads on all IMS or VSAM (orboth) capture server or servers is displayed.

It consists of one header line, three label lines, and oneor more data lines. Each data line provides detailedIMS or VSAM workload information for the workloadsthat are running on the specified IMS or VSAMreplication capture server or servers.


ColumnsDescription

1-20 The state of the workload as determined bythe capture server. The following values arevalid:

AQN031I


||

||||

||||

|||||

||

|

|||

|

|

|

|||||

v DESCRIBEv ENDING CONTROLLEDv ENDING IMMEDIATELYv ERRORv INACTIVEv REPLICATE CONTINUOUSv STARTING

24-31 For a Capture Workload State attribute valueof ERROR, the error identification is shown asa hexadecimal code. Otherwise, the value doesnot apply and is set to N/A. For moreinformation about error codes, see the IMS orVSAM replication documentation.

37-53 A time stamp that represents when the valueof the Capture Workload State attribute waslast changed.

57-76 The cumulative total number of bytes thatwere received by the source server.

80-99 The cumulative total number of rows thatwere received by the source server.

103-122 The cumulative total number of commitmessages that were received by the sourceserver. The number of commits reflects thenumber of transactions.

126-145 The cumulative total number of insertmessages that were sent to the target server.

149-168 The cumulative total number of updatemessages that were sent to the target server.

172-191 The cumulative total number of deletemessages that were sent to the target server.

195-214 The cumulative number of rollbacks that wereprocessed.

218-221 The percentage of the source (capture) cachethat is in use (queue depth), computed as(Current Cache Size/Maximum CacheSize)*100 and rounded down to the nearestwhole integer. If the value for this field isblank, look in the NetView log for theAQN029I message to see if the value is out ofrange.

233-252 The maximum size of the source (capture)cache in bytes.

256-272 The current size of the source (capture) cachein bytes.

279-286 The job name of the capture server


Message Variables

type The type of the workload. The followingvalues are valid:v IMSv VSAMv * (IMS and VSAM)

workload_nameThe name of the workload for which data isdisplayed. If an asterisk (*) is specified for theworkload name, the display is for all IMS orVSAM (or both) workloads on the specifiedcapture server or servers.


AQN032I DISPLAY OF type APPLY WORKLOADDETAILS FOR WORKLOADworkload_name


v ACTVREPL SERVER=* | server_job_name TYPE=typeVIEW=DETAILS

Detailed workload information for all workloads onthe specified apply server or servers is displayed.

v ACTVREPL WORKLOAD=* | workload_name TYPE=*| type VIEW=DETAILS

Detailed workload information for the specifiedworkload or workloads on all IMS or VSAM (orboth) apply server or servers is displayed.

It consists of one header line, three label lines, and oneor more data lines. Each data line provides detailedIMS or VSAM workload information for the workloadsthat are running on the specified IMS or VSAMreplication apply server or servers.


ColumnsDescription

1-20 The state of the workload as determined bythe apply server. The following values arevalid:v DESCRIBEv ENDING CONTROLLEDv ENDING IMMEDIATELYv ERRORv INACTIVEv REPLICATE CONTINUOUSv STARTING

24-31 For an Apply Workload State attribute value ofERROR, the error identification is shown as ahexadecimal code. Otherwise, the value doesnot apply and is set to N/A.

For more information about error codes, seethe IMS or VSAM replication documentation.

37-53 A time stamp that represents when the valueof the Apply Workload State attribute was lastchanged.

57-76 The cumulative total number of bytes thatwere applied.

AQN032I


||||||

||

||

||||||

|||||

|||

|

|

|

|||||

||

80-99 The cumulative total number of rows thatwere applied.

103-122 The cumulative total number of commitmessages that were applied. The number ofcommits reflects the number of transactions.

126-145 The cumulative total number of insertmessages that were applied.

149-168 The cumulative total number of updatemessages that were applied.

172-191 The cumulative total number of deletemessages that were applied.

195-214 The cumulative total number of rollbacks thatwere processed.

218-221 The percentage of the target (apply) cache inuse (queue depth), computed as (CurrentCache Size/Maximum Cache Size)*100 androunded down to the nearest whole integer. Ifthe value for this field is blank, look in theNetView log for the AQN029I message to seeif the value is out of range.

233-252 The maximum size of the target (apply) cachein bytes.

256-275 The current number of bytes that are in use inthe target (apply) cache.



Message Variables

type The type of the workload. The followingvalues are valid:v IMSv VSAMv * (IMS and VSAM)

workload_nameThe name of the workload for which data isdisplayed. If an asterisk (*) is specified for theworkload name, the display is for all IMS orVSAM (or both) workloads on the specifiedapply server or servers.


AQN033I DISPLAY OF Q REPLICATION DATAFOR SEND QUEUE send_queueWORKLOAD workload_name


v ACTVREPL SENDQ=* | send_queue

Send queue information for the specified SENDQname or names and the associated workload orworkloads is displayed.

v ACTVREPL WORKLOAD=* | workload_name TYPE=*| DB2 VIEW=DETAILS

Information for the send queue or queues for thespecified workload or workloads is displayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about the Q replication send queue orqueues for one or more workloads.


ColumnsDescription

1-20 The state of the workload as determined bythe capture server. The following values arevalid:v INACTIVEv REPLICATE CONTINUOUS

24-33 The number of rows (individual insert, update,or delete operations) that the Q Captureprogram put on this send queue.

37-46 The number of transactions that the Q Captureprogram put on this send queue.

52-61 The number of messages that were put on thesend queue during the collection interval.

68-77 The number of bytes that were put on thesend queue during the collection interval,including data from the source table and themessage header.

81-104 The most recent logical log sequence numberin the recovery log that the Q Captureprogram read for this send queue.

For DB2 for z/OS Version 10 or earlier, thisvalue is set to the current log sequencenumber and, for DB2 for z/OS Version 11, it isset to N/A.

108-131 The logical log sequence number from whichthe Q Capture program starts puttingmessages on this send queue during a warmrestart. This value represents the earliest logsequence number that the Q Capture programfound that did not have a commit or abortrecord.

For DB2 for z/OS Version 10 or earlier, thisvalue is set to the restart log sequence numberand, for DB2 for z/OS Version 11, it is set toN/A.

135-144 The number of times that the Q Captureprogram retried putting messages (MQPUT)on this send queue.

149-158 The number of changed rows that were notput on this send queue because the changeswere to columns that are not part of a Qsubscription or publication. The

AQN033I


||

||

||||||

|||||

|

|||

||

||

||||

|||

||||

|||||||

||||

ALL_CHANGED_ROWS parameter in theIBMDB2_SUBS table was set to the defaultvalue of No.

164-173 The number of delete row operations thatwere not put on this send queue because theQ subscription or publication was created withthe option to suppress replication of deleteoperations.

178-187 The number of rows that the Q Captureprogram did not transmit to this send queuebecause they did not meet the search conditionthat is defined in the Q subscription orpublication.

191-238 The name of the send queue.


309-372 The name of the consistency group. Aconsistency group, which is also known as aqueue map, is a single send queue and receivequeue pair. A workload is made up of one ormore consistency groups.

376-423 The name of the WebSphere MQ queuemanager that the Q Capture program workswith.

427-490 The most recent logical log sequence numberin the recovery log that the Q Captureprogram read for this send queue.

For DB2 for z/OS Version 11, this value is setto the current log sequence number, and, forDB2 for z/OS Version 10 or earlier, it is set toN/A.

494-557 The logical log sequence number from whichthe Q Capture program starts puttingmessages on this send queue during a warmrestart. This value represents the earliest logsequence number that the Q Capture programfound that did not have a commit or abortrecord.

For DB2 for z/OS Version 11, this value is setto the restart log sequence number, and, forDB2 for z/OS Version 10 or earlier, it is set toN/A.

Message Variables

send_queueThe name of the send queue on the captureserver for which data is displayed. Ifworkload_name=*, all send queues aredisplayed.

workload_nameThe name of the workload for which data isdisplayed. If workload_name=*, all send queuesare displayed.

System action: The ACTVREPL SENDQ and

ACTVREPL WORKLOAD command processing iscomplete.

AQN034I DISPLAY OF Q REPLICATION DATAFOR RECEIVE QUEUE receive_queueWORKLOAD workload_name


v ACTVREPL RCVQ=* | receive_queue

Receive queue information for the specified receivequeue or queues and the associated workload orworkloads is displayed.

v ACTVREPL WORKLOAD=* | workload_name TYPE=*| DB2 VIEW=DETAILS

Information for the receive queue or queues for thespecified workload or workloads is displayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about the Q replication receive queue orqueues for one or more workloads.


ColumnsDescription

1-20 The state of the workload as determined bythe apply server. The following value is valid:v INACTIVEv REPLICATE CONTINUOUS

24-33 The number of insert, update, and deleteoperations from this receive queue that the QApply program applied to the target.

37-46 The number of transactions from this receivequeue that the Q Apply program committed tothe target.

52-61 The number of transactions that conflictedwith another transaction, because of either arow conflict or a referential integrity conflict.In these cases, the Q Apply program suspendsparallel processing and applies the rowchanges within the transaction in the orderthat they were committed at the source.

67-70 The fullness of the queue as a percentage. Ifthe value for this field is blank, look in theNetView log for the AQN029I message to seeif the value is out of range.

82-91 The number of seconds that the Q Applyprogram was unable to build transactions fromthis receive queue because its agents wereusing all the available memory to applytransactions.

95-104 The number of transactions that exceeded thememory limit for the receive queue that wasset in the IBMDB2_RECVQUEUES table.

AQN034I


||

||

||||||

||||

||||

||||

||||||||

||||

||||

|||

|

|||

||

||

||||

|

||

|||||

||||

||||

||||||||

|||||

||||||

||||

110-119 The number of times that the Q Applyprogram reapplied row changes because oflock timeouts and deadlocks.

123-132 The number of Q Apply agents.

136-145 The number of milliseconds that Q Applyagents for this receive queue were idle whilewaiting for work.

149-158 The amount of memory in bytes that the QApply browser thread used for readingtransactions from this queue.

162-171 The number of messages on the queue.

175-191 The time stamp at the Q Apply server whenthe receive queue was started.

195-204 The number of bytes that were read from thisreceive queue.

208-217 The number of transactions that were readfrom this receive queue.

223-232 The number of rows that were read from thisreceive queue.

236-245 The number of rows that were applied butmight not yet be committed to the target.

249-258 The number of rows that were unable to beapplied and were entered in theIBMDB2_EXCEPTIONS table.

262-271 The total number of replication key constraintsthat were detected, forcing transactions to beserialized.

277-286 The total number of referential integrity (RI)conflicts that were detected, forcingtransactions to be serialized.

292-301 The total number of unique index constraintsthat were detected, forcing transactions to beserialized.

307-316 The number of transactions that are delayedbecause of job name dependencies.

322-331 The number of times that the Q Applyprogram had to reapply row changes becauseof referential integrity (RI) conflicts when thetransactions that they were part of wereexecuted in parallel.

335-344 The number of times that the Q Applyprogram tried to reapply rows that were notapplied in parallel because of unique indexconstraints.

348-357 The number of rows that the Q Applyprogram sent to temporary spill queues whiletargets were being loaded or while Qsubscriptions were placed into a spill state bythe spillsub parameter of the MODIFY orasnqacmd command.

361-370 The number of spilled rows that were appliedto the target.

376-395 A time stamp that represents the sourcecommit time of the oldest currently in-flighttransaction. An in-flight transaction was notfully applied and committed at the target.

399-422 The commit log sequence number (LSN) fromthe source recovery log that corresponds to theoldest transaction that was applied.

For DB2 for z/OS Version 10 or earlier, thisvalue is set to the oldest commit LSN, and, forDB2 for z/OS Version 11, it is set to N/A.

426-449 An internal log marker that corresponds to theoldest transaction that was applied.

For DB2 for z/OS Version 10 or earlier, thisvalue is set to the oldest commit sequencenumber, and, for DB2 for z/OS Version 11, it isset to N/A.

453-462 The number of row changes that caused anSQL error that is defined as acceptable in theOKSQLSTATES field of theIBMQREP_TARGETS table. The Q Applyprogram ignores these errors.

466-475 The heartbeat latency is the average elapsedmilliseconds between the time that heartbeatmessages were sent by the Q Capture programand the time that they were received by the QApply program.

479-526 The name of the receive queue.


597-660 The name of the consistency group. Aconsistency group, which is also known as aqueue map, is a single send queue and receivequeue pair. A workload is made up of one ormore consistency groups.

664-673 The number of transactions that are currentlybeing processed by the apply server, but havenot yet been applied.

679-698 A time stamp that represents the highestsource transaction commit time of thetransactions that have been read for allconsistency groups for this workload.

702-721 A time stamp that represents the highestcommon source transaction commit timeacross all transactions that have been read forall consistency groups for this workload.

725-744 A time stamp that represents the next stoppoint for this consistency group. Onlytransactions with a source transaction committime up to the value of this time stamp areapplied. Transactions are not applied if thesource transaction commit time is later thanthe value of this time stamp.

AQN034I


||||

||

||||

||||

||

|||

|||

|||

|||

|||

||||

||||

||||

||||

|||

||||||

|||||

|||||||

|||

|||||

||||

|||

|||

||||

||

||

||||||

||||

|||||

|||||

||||||||

748-779 The synchronization state of the consistencygroup. The following values are valid:v ACTIVEv INACTIVE

783-830 The name of the WebSphere MQ queuemanager that the Q Apply program uses.

834-897 The commit log sequence number (LSN) fromthe source recovery log that corresponds to theoldest transaction that was applied.

For DB2 for z/OS Version 11, this value is setto the oldest commit LSN, and, for DB2 forz/OS Version 10 or earlier, it is set to N/A.

901-964 An internal log marker that corresponds to theoldest transaction that was applied.

For DB2 for z/OS Version 11, this value is setto the oldest commit sequence number, and,for DB2 for z/OS Version 10 or earlier, it is setto N/A.

Message Variables

receive_queueThe name of the receive queue on the applyserver for which data is displayed. Ifworkload_name=*, all receive queues aredisplayed.

workload_nameThe name of the workload for which data isdisplayed. If workload_name=*, all receivequeues are displayed.

System action: The ACTVREPL RCVQ andACTVREPL WORKLOAD commands are complete.

AQN035I DISPLAY OF Q REPLICATIONCAPTURE SERVER server_job_nameDATA ON SITE server_site

Explanation: This multiline message is issued inresponse to the following command:

v ACTVREPL SERVER=server_job_name TYPE=DB2VIEW=DETAILS

Capture server information for the specified server isdisplayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about a Q Replication capture server.


ColumnsDescription

1-8 The status of the NetView connection to thecapture server. The following values are valid:v ACTIVEv INACTIVE

12-19 The DB2 subsystem or the DB2 group attachname.

23-32 The number of rows (individual insert, update,or delete operations) that the Q Captureprogram read from the log.

36-45 The number of transactions that the Q Captureprogram processed.

51-74 The most recent logical log sequence numberin the recovery log that the Q Captureprogram read.

For DB2 for z/OS Version 10 or earlier, thisvalue is set to the current log sequencenumber, and, for DB2 for z/OS Version 11, it isset to N/A.

78-101 The logical log sequence number in therecovery log at which the Q Capture programstarts during a warm restart. This valuerepresents the earliest log sequence numberthat the Q Capture program found that didnot have a commit or abort record.

For DB2 for z/OS Version 10 or earlier, thisvalue is set to the restart log sequence number,and, for DB2 for z/OS Version 11, it is set toN/A.

105-121 The time stamp at the Q Capture server of thelatest database commit that was seen by the QCapture log reader.

125-134 The number of transactions (containingchanged rows) that were not put on queuesbecause the changes were to columns that arenot part of a Q subscription or publication, forexample, the ALL_CHANGED_ROWSparameter in the IBMDB2_SUBS table was setto NO.

140-149 The number of transactions that the Q Captureprogram spilled to a file after exceeding theMEMORY_LIMIT threshold.

155-164 The memory that the Q Capture program usedto construct transactions from the log.

169-178 The largest transaction, in bytes, that the QCapture program processed.

188-204 The time stamp at the Q Capture controlserver when the Q Capture program reachedthe end of the log.

208-224 The number of milliseconds that the QCapture program spent using the DB2 log readapplication programming interface (API) toretrieve log records

228-237 The number of log read API calls that the QCapture program made.

241-250 The number of times that the Q Captureprogram reached the end of the log.

AQN035I


|||||

|||

||||

|||

|||

||||

||||

|||

||||

||||||

||||

254-263 The number of seconds that the Q Capture logreader thread slept because there were nochanges to capture or because the Q Captureprogram is operating at its memory limit.





Message Variables

server_job_nameThe specified capture server job name.

server_siteThe site (sysplex) on which the server isrunning.

System action: The ACTVREPL SERVER commandprocessing is complete.

AQN036I DISPLAY OF Q REPLICATION APPLYSERVER server_job_name DATA ON SITEserver_site


v ACTVREPL SERVER=server_job_name TYPE=DB2VIEW=DETAILS

Apply server information for the specified server isdisplayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about a Q Replication apply server.


ColumnsDescription



23-39 A time stamp that represents when the QApply task was started.

43-52 The total count of active subscriptions acrossall active queues.

Message Variables

server_job_nameThe specified apply server job name.

server_siteThe site (sysplex) on which the server isrunning.


AQN037I DOMAIN domain IS NOTPARTICIPATING IN AN XCF GROUP

Explanation: This message can be issued in responseto the ACTVCTL TAKEOVER command or theACTVREPL command.

For the ACTVCTL TAKEOVER command, the NetViewprogram on which the command is issued is notparticipating in an XCF group.

For the ACTVREPL command, the target domain onthe production system is not participating in an XCFgroup or it is not part of the purview for thisActive/Active enterprise master.

Participating in an XCF group is a prerequisite for theGDPS Active/Active Continuous Availability solution.

Message Variables



System programmer response: Verify that theXCF.RANK statement in the CNMSTYLE member isnot set to -1 for the specified NetView domain. If it is-1, set an appropriate XCF rank so that the specifiedNetView domain can participate in an XCF group.

If the command that is issued is ACTVREPL, verifythat the specified domain is in a sysplex targeted by anENT.SYSTEMS.name CNMSTYLE member statement.

AQN038I DOMAIN NOT FOUND FOR server_typeSITE sysplex SYSTEM system

Explanation: This message is issued as a response tothe ACTVREPL command when the CAPSITE orAPPSITE and CAPSYS or APPSYS keywords arespecified.

The Active/Active enterprise master NetView does nothave the specified NetView domain for the specifiedsite and system in its XCF group.

Message Variables

AQN036I • AQN038I


||||

||||

|||||||

||||

|||

|||

server_typeThe requested server type, capture or apply,for the site and system.

sysplex The sysplex name.

system The z/OS image name.

Operator response: Verify that the correct site andsystem names were entered on the command.

System programmer response: Verify that theENT.SYSTEMS.name CNMSTYLE statements areconfigured properly.

AQN039I TOWERACTIVEACTIVE.REPLICATION.subtwrNOT ENABLED FOR DOMAIN domain

Explanation: An ACTVREPL command was issued,and the specified replication subtower is not enabledfor the specified domain. The subtower corresponds tothe TYPE keyword on the ACTVREPL command.

Message Variables

subtwr The replication subtower for theACTIVEACTIVE tower:

v DB2

v IMS

v VSAM


Operator response: Verify that the appropriate valuesare specified on the command, and reissue it.

System programmer response: Verify that thereplication subtower is enabled for the specifieddomain. If it is not enabled, uncomment the subtowername in the user-defined CNMSTGEN or CNMSTUSRmember, and then recycle the NetView program.

AQN040I COMMON GLOBAL VARIABLEvariable IS NOT DEFINED FORDOMAIN domain

Explanation: The ACTVREPL command could notfind the specified common global variable for thespecified NetView domain. The variables represent:v Status of the replication subtower on the production

system.v Number of replication capture and apply socket path

names defined on the production system.v Replication capture and apply socket path names

defined on the production system.

These variables are derived from information sent fromthe production system for the following situations:v Activation of a replication autotask.v Establishment of an enterprise master NetView

program.v Issuance of the RESTYLE ACTACT command.

Note:

1. The AQN001I message is issued if no paths arefound for the specified domain.

2. The AQN041I message is issued if the socket pathdefinition is not sequential.

3. The AQN006I message is issued if the socket pathdefinition is a duplicate.

4. See automation sample member AQNSACTA formore information about messages used to sendreplication information from the production systemsto the controller system.

Message Variables

variable The common global variable name


System action: The command fails.

Operator response: Verify the following:v That the correct destination information was

specified on the ACTVREPL command.v That the specified domain is in the LIST

STATUS=XCFGRPS command output.v That there are no messages in the NetView log for

the specified domain that indicate that there areproblems with the socket path definition statements.

System programmer response: Verify theconfiguration on the production system with thespecified domain:v Enable the replication subtower, if necessary, and

recycle NetView.v Configure or change socket path names for the

replication subtower, if necessary, and issue theRESTYLE ACTACT command.

Verify that automation for ACTVREPL (sampleautomation member AQNSACTA) is enabled on bothproduction systems and controller systems.

AQN041I SOCKET PATH DEFINITION statementIS NOT SEQUENTIAL

Explanation: The path number for an ACTACT socketpath definition statement is not sequential. Socket pathname information is not forwarded to the enterprisemaster NetView program. The CNMSTYLE memberstatements are:

v ACTACT.DB2PATH.CAPx

v ACTACT.DB2PATH.APPx

v ACTACT.IMSPATH.CAPx

v ACTACT.IMSPATH.APPx

v ACTACT.VSAMPATH.CAPx

v ACTACT.VSAMPATH.APPx

The value for x must start with 1 and increasesequentially up to a maximum of 50 for each of thesestatements. If a non-sequential definition is found, nosocket path name information for the particular datasource and server type is forwarded to the controller

AQN039I • AQN041I


|

|

|

system. The ACTVREPL command fails if thedestination is for this particular set of socket pathdefinitions.

Message Variables

statementThe CNMSTYLE statement that is notsequential

System programmer response: Correct theCNMSTYLE member statements and issue theRESTYLE ACTACT command.

AQN042I MAXIMUM NUMBER OF subtower_nameserver_type SOCKET PATHDEFINITIONS EXCEEDED

Explanation: More than 50 socket path definitionswere defined for Q replication capture servers, Qreplication apply servers, IMS replication captureservers, or IMS replication apply servers.

This message can be issued on the production systemor on the controller system. If it is issued on thecontroller system, the cumulative total of each servertype for the data source is over 50.

Message Variables

subtower_nameFor the ACTIVEACTIVE tower:v DB2v IMSv VSAM

server_typeThe server type, capture or apply, on thesocket path definition.

System programmer response: Verify that the socketpath definitions are correct on the production systems.Make any necessary changes, and issue the RESTYLEACTACT command.

If more path definitions are required for yourenvironment, contact IBM Software Support.

AQN043I AQN043I NO subtower_name server_typeSOCKET PATH INFORMATIONFORWARDED TO CONTROLLER,REASON 'reason'

Explanation: The specified socket path definition isnot configured correctly for one of the followingreasons:

DUPLICATE PATH NAME The same socket path name was specifiedmore than once on different CNMSTYLEmember statements.

INVALID PATH NAMEThe socket path name did not start with aleading forward slash (/).

If an incorrect definition is found, no socket pathinformation for the specified subtower and replicationserver type is forwarded to the controller system. TheACTVREPL command fails if the destination is for thisparticular set of socket path definitions.

The CNMSTYLE member statements are:v ACTACT.DB2PATH.CAPxv ACTACT.DB2PATH.APPxv ACTACT.IMSPATH.CAPxv ACTACT.IMSPATH.APPx

Message Variables

subtower_nameFor the ACTIVEACTIVE tower:v DB2v IMSv VSAM

server_typeAPPLY or CAPTURE

reason One of the following reasons, including thesocket path name in error:v DUPLICATE PATH NAMEv INVALID PATH NAME

System action: No production system pathconfiguration information is forwarded to the controllersystem for the specified data source (DB2, IMS, orVSAM) and function (APPLY or CAPTURE).

System programmer response: Verify that the socketpath definitions are correct on the production systems.Make any necessary changes, and issue the RESTYLEACTACT command.

AQN044I ATTRIBUTE attribute_name IS MISSINGFOR data_source REPLICATION EVENTclass_name

Explanation: This message is written to the NetViewlog when a required attribute in an Event IntegrationFacility (EIF) event that is sent by a replication productis not present in the alert. The alert is generated by theNetView Event/Automation Facility (E/AS) EventReceiver.

If the missing attribute is one that impacts the routingof workloads by the GDPS Active/Active ContinuousAvailability solution, the AQN047I message is alsoissued indicating that no information is forwarded. Thismeans that event information is not sent to the LifelineAdvisor component of the Multi-site Workload Lifelineproduct or to the GDPS/Active-Active component.

The attribute might be missing for one of the followingreasons:

v The specified replication product did not send theattribute in the EIF event.

AQN042I • AQN044I


|

|||||

|||

||||

|||

|||||

|||||

|

|||||

||

|||||

||||

||||

||||

||||||

|||||||

||

||

v The NetView E/AS Event Receiver Class DefinitionStatement (CDS) member for the GDPSActive/Active Continuous Availability solution wasmodified.

Notes:

1. The AQN044I message is issued one time for thespecified event. If more than one attribute value ismissing, the following order is used to determinethe attribute name that is specified in the AQN044Imessage:

v The first major attribute that is found to bemissing. A major attribute is required by theLifeline Advisor for routing.

v The first minor attribute that is found to bemissing. A minor attribute is not required by theLifeline Advisor for routing.

2. EIF event information is sent to the Lifeline Advisorfor Active/Query workloads.

3. EIF event information is sent to theGDPS/Active-Active component for bothActive/Standby and Active/Query workloads.

For more information, see the help for the AQN047Imessage.

Message Variables

attribute_nameThe attribute name specified in the EIF event.

The following example represents anattribute-value pair in an EIF event:

workload_name=TELNET23Q;

data_sourceThe value specified in the data_sourceattribute in the EIF event:v DB2v IMSv VSAMv unknown_data_source

The unknown_data_source value is specifiedby the NetView program when thedata_source attribute is missing orprocessing of the alert ends before the datasource is known.

class_nameThe EIF event class name.

System action: If the AQN047I message is issued withthe AQN044I message, processing stops. If theAQN044I message is issued by itself, the EIF eventinformation is forwarded to the Lifeline Advisor andthe GDPS/Active-Active component.

Operator response: Look for the AQN047I message inthe NetView log. Contact your system programmerwith all messages and the NPDA alert information forthis event.


Verify that the E/AS Event Receiver CDS member (oran included member) was not modified to prevent thisattribute from being generated in the NPDA alert. If itwas modified, correct the statements. Otherwise,contact IBM Software Support for the specifiedreplication product.

AQN045I INVALID VALUE RECEIVED FORdata_source REPLICATION EVENTclass_name, ATTRIBUTE attribute_name

Explanation: This message is written to the NetViewlog when the value for a required attribute in an EventIntegration Facility (EIF) event that is sent by areplication product is invalid in the alert. The alert isgenerated by the NetView Event/Automation Facility(E/AS) Event Receiver.

If the attribute is one that impacts the routing ofworkloads by the GDPS Active/Active ContinuousAvailability solution, the AQN047I message is alsoissued indicating that no information is forwarded. Thismeans that event information is not sent to the LifelineAdvisor component of the Multi-site Workload Lifelineproduct or to the GDPS/Active-Active component.

The attribute might be invalid for one of the followingreasons:

v The specified replication product did not send thecorrect attribute value in the EIF event.

v The NetView E/AS Event Receiver Class DefinitionStatement (CDS) member for the GDPSActive/Active Continuous Availability solution wasmodified.

v The length of the attribute value might be incorrect.

v The attribute value was an unexpected value.

v The attribute value did not end with a semicolon (;).

v The attribute value was not present.

Notes:

1. The AQN045I message is issued one time for thespecified event. If more than one attribute value isinvalid, the following order is used to determine theattribute name that is specified in the AQN045Imessage:

v The first major attribute that is found to beinvalid. A major attribute is required by theLifeline Advisor for routing.

v The first minor attribute that is found to beinvalid. A minor attribute is not required by theLifeline Advisor for routing.

2. EIF event information is sent to the Lifeline Advisorfor Active/Query workloads.

3. EIF event information is sent toGDPS/Active-Active component for bothActive/Standby and Active/Query workloads.

AQN045I


||||

|

|||||

|||

|||

||

|||

||

|

||

||

|

|||||||

|||||

||

|||||

||||

|

||||||

||||

||||||

|||||||

||

||

||||

|

|

|

|

|

|||||

|||

|||

||

|||


Message Variables

data_sourceThe value that is specified in the data_sourceattribute in the EIF event:v DB2v IMSv VSAMv unknown_data_source



attribute_nameThe attribute name specified in the EIF event.

The following example represents anattribute-value pair in an EIF event:

workload_name=TELNET23Q;

System action: If the AQN047I message is issued withthe AQN045I message, processing stops. If theAQN045I message is issued by itself, the EIF eventinformation is forwarded to the Lifeline Advisor andthe GDPS/Active-Active component.

Operator response: Look for the AQN047I message inthe NetView log. Contact your system programmerwith all messages and the NPDA alert information forthis event.


Verify that the E/AS Event Receiver CDS member (oran included member) was not modified to prevent thisattribute value from being generated correctly in theNPDA alert.

If the CDS member was modified, correct thestatements. Otherwise contact IBM Software Supportfor the specified replication product.

AQN046I REPLICATION EVENT class_name ISNOT RECOGNIZED

Explanation: This message is written to the NetViewlog when the class name in an alert is not recognized inan Event Integration Facility (EIF) event that is sent bya replication product. The alert is generated by theNetView Event/Automation Facility (E/AS) EventReceiver.

The event class name might not be recognized for oneof the following reasons:

v The replication product did not send the correct classname in the EIF event.

v The NetView E/AS Event Receiver Class DefinitionStatement (CDS) member was modified.

An AQN047I message is also issued because noinformation for this event is forwarded to the LifelineAdvisor component of the Multi-site Workload Lifelineproduct or to the GDPS/Active-Active component.

The replication EIF event class names for the GDPSActive/Active Continuous Availability solution are asfollows:v AA_replication_reset_average_latency_metvAA_replication_constrained_average_latency_exceededv AA_replication_critical_average_latency_exceededv AA_replication_max_average_latency_exceededv AA_replication_discrete_latency_exceeded

AA_replication_heartbeatv AA_replication_workload_down

AA_replication_workload_up


Message Variables


System action: Processing stops.

Operator response: Contact your system programmerwith the information in the NPDA alert that matchesthis event class name.


Verify that the E/AS Event Receiver CDS member (oran included member) was not modified to change theevent name that is generated in the NPDA alert.

If the CDS member was modified, correct thestatements. Otherwise contact IBM Software Supportfor the specified replication product.

AQN047I data_source REPLICATION EVENTclass_name NOT FORWARDED.RETURN CODE: return_code

Explanation: This message is issued when theNetView program does not forward information aboutan Event Integration Facility (EIF) event to the LifelineAdvisor component of the Multi-site Workload Lifelineproduct or the GDPS/Active-Active component.

See the return code to determine the reason whyinformation was not forwarded.

Message Variables

data_sourceThe value that is specified in the data_sourceattribute in the EIF event:v DB2v IMS

AQN046I • AQN047I


||

|

|||||||

|||||

||

||

||

|

|||||

||||

|

||||

|||

|||

||||||

||

||

||

||||

||||||||||||

||

|

||

|

|||

|

|||

|||

||||

|||||

||

|

|||||

v VSAMv unknown_data_source



return_codeThe return code has one of the followingvalues:8 An attribute value for a major

attribute is invalid.12 A major attribute is missing. The

major attributes are as follows:v sysplex_namev workload_namev consistency_group_namev consistency_group_totalv latency_state with one of the

following values:– Normal– Constrained– Critical– Acute

16 EIF event class name is not supportedby the GDPS Active/ActiveContinuous Availability solution.

20 Information is not forwarded to theLifeline Advisor because it is notactive in primary role. Because theinformation is not forwarded to theLifeline Advisor, it is also notforwarded to the GDPS/Active-Activecomponent.

AQN048I data_source REPLICATION EVENTVERSION replication_version DOES NOTMATCH NETVIEW EVENT VERSIONnetview_version

Explanation: This message is issued when areplication Event Integration Facility (EIF) event is sentwith a version attribute value that does not match theversion that the NetView program supports. There is afunction mismatch, and results are unpredictable.

This message is issued only once for each data sourcefor the current instance of the NetView program. Ifother problems are found with the EIF event that issent by the replication product, this message is notissued.

Message Variables

data_sourceThe value specified in the data source attributein the EIF event:v DB2v IMS

v VSAM

replication_versionThe value for the version attribute sent in theEIF event for the specified data source

netview_versionThe value that the NetView program currentlysupports


System programmer response: Apply maintenance forthe NetView program or the replication product that isidentified by the data source. If all current maintenanceis applied, contact IBM Software Support.

AQN049I DISPLAY OF REPLICATIONWORKLOADS


v ACTVREPL WORKLOAD=* | workload_nameVIEW=SUMMARY

Summary information for the specified replicationworkload or workloads is displayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about a replication workload.


ColumnsDescription

1-64 The name of the workload. A workload ismade up of one or more consistency groups.

68-75 The name of the capture site.

80-87 The name of the apply site.

92-96 The number of consistency groups that makeup the workload as defined by the replicationproduct.

113-117 The number of consistency groups for aworkload for which the NetView program hasdata, which is to be used for aggregation.

134-143 The highest average latency of all of theconsistency groups for this workload.

Average latency is the average elapsed time inmilliseconds between the time thattransactions were committed to the sourcetable or database and the time thattransactions were committed to the target tableor database. This average includes only thetransactions that were processed during thelast polling interval.

147-156 The number of transactions that are currentlybeing processed by the apply server but havenot yet been applied.

AQN048I • AQN049I


||

|||||

||

|||||||||||||||||||||||||||||||

|||||

|||||

|||||

|

|||||

|

|||

|||

|

||||

|||

||

||

||

|||

|

||

|||

||

||

||||

||||

|||

||||||||

||||

162-181 A time stamp that represents the highestsource transaction commit time of thetransactions that have been read for allconsistency groups for this workload.

185-204 A time stamp that represents the highestcommon source transaction commit timeacross all transactions that have been read forall consistency groups for this workload.

208-239 The state of the replication workload asdetermined by the state of all of the captureand apply servers for the workload. If thestate of any of the capture and apply serversfor the workload is INACTIVE, then the valueof Replication Workload State is INACTIVE.

The following values are valid:v INACTIVEv REPLICATE CONTINUOUS

243-262 The aggregate of the cumulative total numberof bytes that were sent to the target server forall of the consistency groups for this workload.

266-285 The aggregate of the cumulative total numberof transactions that were sent to the targetserver for all of the consistency groups for thisworkload.

289-308 The aggregate of the cumulative total numberof rows that were sent to the target server forall of the consistency groups for this workload.

312-331 The aggregate of the cumulative total numberof bytes that were received by the target serverfor all of the consistency groups for thisworkload.

335-354 The aggregate of the cumulative total numberof transactions that were received by the targetserver for all of the consistency groups for thisworkload.

358-377 The aggregate of the cumulative total numberof rows that were received by the target serverfor all of the consistency groups for thisworkload.

381-397 A time stamp that represents the point in timeat which all transactions have been applied tothe target without gaps that might result fromparallel apply, across all consistency groups inthe workload. The time stamp comes from thesource DBMS log and is expressed in GMT.This time stamp provides the age of the oldestdata for the workload. For example, if thecurrent GMT time is 5:00:01.10 andpoint-in-time consistency is 5:00:01.08, then nodata on the target database is any older than 2seconds in relation to the source database forthis workload.

401-416 An indication of the amount of replicationinformation that has been received for aworkload, as determined by the NetView

program that is running on the controllersystem. The following values are valid:

v SATISFACTORY: All capture and apply datahas been received for the workload and isbeing used for aggregation.

v UNSATISFACTORY: Incomplete capture orapply data has been received for theworkload. Data has been aggregated usingthe available replication data, but themissing data might lead to inaccurateresults.

420-435 An explanation for the aggregation statusvalue, as determined by the NetView programthat is running on the controller systems. Thefollowing values are valid:

v COMPLETE DATA: All capture and applydata has been received for the workload.

v PARTIAL DATA: Not all of the capture andapply data is received for the workload.

v STALE DATA: All of the capture and applydata for the workload is not received withina calculated window, which is based on thesampling interval as defined on theproduction system. The window value is thesampling interval plus the value of theACTACT.MASTER.DELAY CNMSTYLEstatement, which defaults to 3 seconds. Forinformation about theACTACT.MASTER.DELAY statement, seethe NetView for z/OS Administration Reference.


AQN050I DISPLAY OF Q REPLICATIONCAPTURE SERVERS DATA


v ACTVREPL SERVER=* TYPE=DB2 VIEW=DETAILS

Capture server information for one or more QReplication servers is displayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about a Q Replication capture server.


ColumnsDescription

1-8 The status of the NetView connection to thecapture server. The following values are valid:v ACTIVEv INACTIVE


AQN050I


|||||

|||||

|||||||

|||

||||

|||||

||||

|||||

|||||

|||||

||||||||||||||

||||

||

|||

||||||

|||||

||

||

|||||||||||

|||

|||

||

|

||

|||

|

||

|||||

|||

23-32 The number of rows (individual insert, update,or delete operations) that the Q Captureprogram read from the log.

36-45 The number of transactions that the Q Captureprogram processed.


For DB2 for z/OS Version 10 or earlier, thisvalue is set to the current log sequencenumber, and, for DB2 for z/OS Version 11, it isset to N/A.


For DB2 for z/OS Version 10 or earlier, thisvalue is set to the restart log sequence number,and, for DB2 for z/OS Version 11, it is set toN/A.

105-121 The time stamp at the Q Capture server of thelatest database commit that was seen by the QCapture log reader.

125-134 The number of transactions (containingchanged rows) that were not put on queuesbecause the changes were to columns that arenot part of a Q subscription or publication, forexample, the ALL_CHANGED_ROWSparameter in the IBMDB2_SUBS table was setto NO.

140-149 The number of transactions that the Q Captureprogram spilled to a file after exceeding theMEMORY_LIMIT threshold.

155-164 The memory that the Q Capture program usedto construct transactions from the log.

169-178 The largest transaction, in bytes, that the QCapture program processed.

188-204 The time stamp at the Q Capture controlserver when the Q Capture program reachedthe end of the log.

208-224 The number of milliseconds that the QCapture program spent using the DB2 log readapplication programming interface (API) toretrieve log records

228-237 The number of log read API calls that the QCapture program made.

241-250 The number of times that the Q Captureprogram reached the end of the log.

254-263 The number of seconds that the Q Capture logreader thread slept because there were no

changes to capture or because the Q Captureprogram is operating at its memory limit.

267-274 The job name of the capture server.

281-288 The name of the capture site.






AQN051I DISPLAY OF Q REPLICATION APPLYSERVERS DATA


v ACTVREPL SERVER=* TYPE=DB2 VIEW=DETAILS

Apply server information for one or more QReplication servers is displayed.

It consists of one header line, three label lines, and oneor more data lines, with each data line providinginformation about a Q Replication apply server.


ColumnsDescription



23-39 A time stamp that represents when the QApply task was started.

43-52 The total count of active subscriptions acrossall active queues.


73-80 The name of the apply site.

AQN051I


||||

|||

||||

||||

|||||||

||||

||||

||||||||

||||

|||

|||

||||

|||||

|||

|||

|||

||

||

||

||||

||||

|||||||

||||

||

|||

||

|

||

|||

|

||

|||||

|||

|||

|||

||

||


AQN052I ENT.SYN.prisec.site.domain FORDOMAIN domain_id SPECIFIES SNA

Explanation: This message is issued during ACTVCTLCONNECT processing when the RMTSYN value that isspecified on an ENT.SYN statement specifies to useSNA RMTCMD communications.

Message Variables

prisec Specifies the primary or secondary ENT.SYNstatement:

ENT.SYN.PRI.site.domainPrimary IP addresses for the NetViewdomain. .site.domain identifies thedomain and the site in which itresides.

ENT.SYN.SEC.site.domainSecondary IP addresses for theNetView domain. .site.domainidentifies the domain and the site inwhich it resides.

domain_idSpecifies the remote NetView domain.

System action: Processing continues, but the ENT.SYNstatement is ignored and a RMTALIAS statement is notgenerated. This might cause connectivity problems tosystems that are specified on ENT.SYSTEMS statementsthat use the RMTALIAS statement.

Operator response: Contact the system programmerresponsible for adding ENT.SYN CNMSTYLEstatements.

System programmer response: Update the ENT.SYNstatement to use an IP address. The ACTVCTLCONNECT command supports only IP addressing.

AQN053I command FAILED. Reason: reason. ReasonCode: reason_code

Explanation: This message is issued when a NetViewcommand for the GDPS Active/Active ContinuousAvailability solution fails. The reason and reason codeprovide more information about why the commandfailed.

Message Variables

commandThe command that failed, namely, theACTVREPL command, which is issued from aGDPS Active/Active Continuous Availabilitysolution controller system. The ACTVREPLcommand uses stored socket path nameinformation to identify the GDPS

Active/Active Continuous Availability solutionproduction systems from which to retrievereplication information.

reason The possible reasons for the command failureare as follows:

v Replication server information is notavailable

No replication information for anyproduction system is available (or waspreviously available) to the NetViewprogram on the controller system, which canoccur for the following reasons:

– The NetView program is not anenterprise master NetView program.

– No production systems hadcommunicated information to thecontroller system when the commandwas issued, which can be caused by thefollowing circumstances:

- The NetView program or one or moreof the replication products are notinitialized on any production system.

- Communication between the NetViewprogram on the controller system andall production systems has failed.

v No replication information is available fromproduction system NetView domains

The NetView program that is running onthe controller system does not have anyreplication configuration information fromany production system NetView program.The replication configuration information isrequired to collect information for theACTVREPL command. This situation canoccur when the NetView program that isrunning on the controller system previouslyhad information from production systemNetView domains, but all of the productionsystem NetView programs are currentlyinactive.

v No replication subtowers are enabled

The NetView program on the controllersystem has information about productionsystems, but no replication subtowers areenabled on the production systems.

v No socket path definitions are defined

The NetView program on the controllersystem has information about productionsystems and replication subtowers areenabled, but no socket paths definitions aredefined.

reason_codeThe following reason codes are valid:

16 Replication server information is notavailable.

AQN052I • AQN053I


||

|||

||||

|

|||

|||||

|||||

||

|||||

|||

|||

|||

|||||

|

|||||||

|||

|||

||

|||||

||

|||||

|||

|||

||

|||||||||||||

|

||||

|

|||||

||

|||

12 No replication information isavailable from production systemNetView domains.

10 No replication subtowers are enabled.

8 No socket path definitions aredefined.

System action: Processing stops.

Operator response: If the reason is either thatreplication server information is not available or thatno replication information is available from productionsystem NetView domains, verify the following items:

v The NetView program on which the command isissued is the enterprise master NetView program.

v The NetView programs in the production systemdomains are active and successfully communicatingwith the enterprise master NetView program.

v The production system NetView log contains noerrors that are related to replication configuration.

Note:

1. On the controller system, issue the LISTSTATUS=XCFGRPS command to determine whetherthe NetView program is the enterprise masterNetView program.

2. On the production systems, issue the RMTCMDQUERY LCLAUTOS command. In the commandoutput, look in the RMTCMD AUTOTASK columnfor an entry with the name of the autotask that isdefined by the function.autotask.ACTDATAstatement; AUTOADAT is the default name for thisautotask.

Otherwise, contact the system programmer.

System programmer response: Verify the replicationconfiguration on the production systems:

v Appropriate towers and subtowers are enabled.

v Socket paths are defined for enabled replicationsubtowers.

Verify the network connectivity between the enterprisemaster NetView program and the NetView programson the production systems.

Review the ENT.SYSTEMS.name statements in theCNMSTYLE member to ensure that the enterprisemaster NetView program is contacting all the necessaryproduction systems.

AQN054I REQUIRED ENT.ALT.CONTROLLERSSTATEMENT MISSING

Explanation: During processing of ENT.SYNstatements as a result of ACTVCTL CONNECT orRESTYLE ENT commands, no ENT.ALT.CONTROLLERstatement was found for an ACTIVEACTIVE enterprisemaster.

System action: ENT.SYN statement processing ends.No RMTALIAS statements are generated fromENT.SYN statements.


System programmer response: Add the requiredENT.ALT.CONTROLLER CNMSTYLE statement.

BNH Prefix MessagesThis section lists the BNH prefix messages.

BNH803I VALUE value1 FOR KEYWORD keyword1CONFLICTS WITH VALUE value2 FORKEYWORD keyword2

Explanation: A command failed because the value ofone valid keyword was not compatible with the valueof another valid keyword. The keyword could be aCNMSTYLE statement.

Message Variables

value1 The value causing the conflict.

keyword1The keyword whose value is causing theconflict.

value2 The other value with which the conflict occurs.

keyword2The other keyword whose value is in conflict.

System action: Processing continues.

Operator response: Correct the command specification

and reenter the command. See the NetView online helpfor the syntax of the command involved.

System programmer response: Correct the specifiedCNMSTYLE statement and ask the operator to reenterthe command.

BNH804I 'intfc_name' 'intfc_qual' INTERFACEINITIALIZATION IS action

Explanation: When the action is STARTING, theindicated interface is initializing. When the action isCOMPLETE, the initialization process completed.

For the Tivoli NetView for z/OS EnterpriseManagement Agent, a Program to Program Interface(PPI) connection is established with the NetViewprogram.

For the ACTIVEACTIVE, DISCOVERY, DVIPA, orTEMA tower, data collection for the specified subtoweris starting.

Message Variables

AQN054I • BNH804I


||||

||

|||

|

||||

||

|||

||

|

||||

|||||||

|

||

|

||

|||

||||

|||

|||||

|||

|

||

intfc_nameThis can be one of the following:v Tivoli NetView for z/OS Enterprise

Management Agentv ACTIVEACTIVE, DISCOVERY, DVIPA, or

TEMA tower

intfc_qualFor the NetView for z/OS EnterpriseManagement Agent interface, this is the PPIreceiver name for the agent.

For the ACTIVEACTIVE, DISCOVERY, DVIPA,or TEMA tower, this is a subtower.

action The action is either STARTING or COMPLETE

BNH805I 'intfc_name' 'intfc_qual' INTERFACE ISTERMINATING DUE TO 'reason' rc

Explanation: An interface is ending because of theindicated reason.

Message Variables

intfc_nameThis can be one of the following:v Tivoli NetView for z/OS Enterprise

Management Agentv ACTIVEACTIVE, DISCOVERY, DVIPA, or

TEMA tower

intfc_qualQualifying information for the interface name.

For the NetView for z/OS EnterpriseManagement Agent interface, this is the PPIreceiver name for the agent.

For the ACTIVEACTIVE, DISCOVERY, DVIPA,or TEMA tower, this is a subtower.

reason The reason the interface ended, which can beone of the following reasons:

CNME8202 FAILEDThe CNME8202 command list wasended by a halt request.

DATA COLLECTION TASK TERMINATIONA data collector autotask is no longeractive for the specified subtower.

DATA SPACE WRITE ERRORA failure occurred when trying toaccess the NetView for z/OSEnterprise Management Agent dataspace. See the correspondingDWO050E message and reason codein the NetView log.

HALT REQUESTThe NACMD command was canceled.

INTERNAL ERRORThis is a condition that must notoccur within NACMD commandprocessing.

INVALID SYNTAXA syntax error occurred when theNACMD command was issued.Either information was provided thatwas not valid or required informationwas missing.

NACMD ALREADY ACTIVEAn NACMD command has alreadybeen issued for this NetViewprogram.

NETVIEW ENTERPRISE MANAGEMENTAGENT TERMINATION

The NetView for z/OS EnterpriseManagement Agent has ended, whichcauses all data collection for TEMAsubtowers to stop.

NETVIEW ENTERPRISE MANAGEMENTINTERNAL ERROR

The NetView for z/OS EnterpriseManagement Agent has ended withan internal error, which causes alldata collection for TEMA subtowersto stop.

OPERATOR REQUESTThe operator requested one of thefollowing actions:

v Stop the PPI connectivity betweenthe NetView program and theNetView for z/OS EnterpriseManagement Agent.

v Stop data collection for a subtower.

v Stop the NetView for z/OSEnterprise Management Agentusing the NetView STOPNAcommand or the z/OS STOPcommand. In this case, the messageincludes a reason code of 00000012.

PPI REGISTRATION FAILUREAn NACMD command failed toregister a subnode to the NetView forz/OS Enterprise Management Agent.

PPI SESSION ENDINGA PPI session to the NetView forz/OS Enterprise Management Agentended. Look for the correspondingDWO050E message and the reasoncode in the NetView log. See theDWO050E message help for theappropriate action to take based onthe specified reason codes.

BNH805I


REXX FAILURE SIGNALA REXX failure occurred with theNACMD command.

REXX NOVALUE ERRORA REXX no value error occurred withthe NACMD command.

REXX SYNTAX ERRORA REXX syntax error occurred withthe NACMD command.

TEMA TOWER NOT ACTIVEAn NACMD command was issued,but the TEMA tower is not enabled inthe CNMSTYLE member.

rc Optional reason code.

System action: The NACMD command ends and theconnection to the agent is disconnected or datacollection has been suspended for a TEMA, DVIPA, orDISCOVERY subtower.

Operator response: Reissue the NACMD command ifthe HALT REQUEST or OPERATOR REQUEST reasonis received. If the problem persists, contact the systemprogrammer.

System programmer response: Take the appropriateaction based on the reason received:

CNME8202 FAILEDBrowse the NetView log for additional errormessages. Contact IBM Software Support.

DATA COLLECTION TASK TERMINATIONStart the autotask associated with the specifiedACTIVEACTIVE, DISCOVERY, DVIPA, orTEMA subtower again.

DATA SPACE WRITE ERRORThe DWO050E message is written to theNetView log when this reason is specified.Look for the reason code in the DWO050Emessage and take the appropriate action.

104 Internal Error.

Contact IBM Software Support.

120 Internal Error.


124 NetView storage failure.

Determine which task is using anexcessive amount of storage and takeaction as appropriate.

128-132 Internal Error.


204 One or more of the followingconditions has occurred:

v The NetView for z/OS EnterpriseManagement Agent is inactive.

v The agent is active, but theNACMD command was not issued.

Verify that the agent is active and theNACMD was issued successfully.

400+ The NetView for z/OS EnterpriseManagement Agent data space couldnot be created. Look for the CNM273Imessage in the NetView log or in theRKLVLOG log of the agent todetermine the reason for the failure.Contact IBM Software Support.

INTERNAL ERRORContact IBM Software Support.

INVALID SYNTAXVerify that the NACMD parameters are correctin the CNMSTYLE member.

NACMD ALREADY ACTIVEAn NACMD command was already issued forthis NetView program. If you want to issuethe command with different parameters, stopthe current NACMD command by using theSTOPNA command. Then issue the NACMDcommand again.

NETVIEW ENTERPRISE MANAGEMENT AGENTINTERNAL ERROR


NETVIEW ENTERPRISE MANAGEMENT AGENTTERMINATION

If the NetView for z/OS EnterpriseManagement Agent was stopped by anoperator request, start the agent again. If theNetView for z/OS Enterprise ManagementAgent ended abnormally, look for errormessages in syslog or RKLVLOG to determinethe reason for the failure. If you cannot resolvethe problem, contact IBM Software Support.

PPI REGISTRATION FAILURETake the appropriate action as indicated by thereason code. If the reason code is not includedwith this message, look for the reason code inthe DWO050E message that is written to theNetView log.

00000004The NetView for z/OS EnterpriseManagement Agent PPI receiver isnot active. Verify that the NetViewsubsystem interface (SSI) and theagent are active.

00000022Internal Error.




BNH805I


00000024The PPI is not available. Verify thatthe NetView subsystem interface (SSI)is active.

00000026The DESTPPI receiver is not definedor is not yet active. Verify that theNetView for z/OS EnterpriseManagement Agent is active.

00000028The NetView subsystem interface(SSI) is active, but the PPI option isnot enabled. Restart the SSI with thePPI option enabled.

00000032A NetView storage failure occurred.Determine which task is using anexcessive amount of storage and takeaction as appropriate.









PPI SESSION ENDINGThe DWO050E message is written to theNetView log when this reason is specified.Look for the reason code in the DWO050Emessage and take the appropriate action.

00000001The local PPI is not available. TheNetView subsystem interface (SSI)might be down. Start the SSI and tryagain.

00000003The local PPI receiver failed. Start theNetView for z/OS EnterpriseManagement Agent again and reissuethe NACMD command.

00000006The NACMD command or the datareceived by the command is notvalid. Stop the current NACMDcommand and reissue it. If theproblem persists, contact IBMSoftware Support.

00000008Unknown data was received on thelocal PPI sender (LCLPPIRV). Stopthe current NACMD command andreissue it. If the problem persists,contact IBM Software Support.

00000010The NetView for z/OS EnterpriseManagement Agent subnode for thisNetView program ended. Verify thatthe agent is active and has notencountered an abend.

00000201The primary NetView for z/OSEnterprise Management Agent PPIsession is not available. Verify thatthe NetView subsystem interface (SSI)is active with the PPI option enabled.If the SSI is inactive, start it.

00000203A receive failure occurred for the PPIreceiver for the NetView for z/OSEnterprise Management Agent.Contact IBM Software Support.Restarting the agent and reissuing theNACMD command might resolve theproblem.

00000204The primary PPI session received anunknown initial command. ContactIBM Software Support. Stop thecurrent NACMD and reissue it.

00000207A duplicate node name was found.Verify that the NetView programsissuing the NACMD command haveunique domain names.

00000209The PPI name was already defined.Restart the NetView for z/OSEnterprise Management Agent with aunique name.

REXX FAILURE SIGNALContact IBM Software Support.

REXX NOVALUE ERRORContact IBM Software Support.

REXX SYNTAX ERRORContact IBM Software Support.

TEMA TOWER NOT ACTIVEThe NACMD command was issued, but theTEMA tower is not enabled in the CNMSTYLEmember. Enable the TEMA tower statementand recycle the NetView program.

BNH805I


BNH881I DATA COLLECTION FAILED FORSUBTOWER subtower_name, REASON'reason'

Explanation: The data collection command failed forone of the following reasons:

ADVISOR NOT AVAILABLE OR ROLE NOTPRIMARY

The connection for NetView data collection forthe specified subtower was not attemptedbecause there was no listening socket availablefor the Lifeline Advisor component of theMulti-site workload Lifeline product. TheLifeline Advisor component was either notstarted or not started in the primary role.

COMMAND FAILEDThe NetView data collection command for thespecified subtower failed. This can occur forthe following reasons:

v Data collection is started on a task otherthan the one for which it was designated inthe CNMSTYLE member.

v Data collection for the designated subtoweris not supported on the current level of thez/OS program.

v The underlying data collection commandfails.

INACTIVE NACMDThe NACMD command is not active. Whenthe command ends, it stops all data collectors.This reason code indicates that there might bea time delay in stopping data collection afterthe NACMD ends.

INTERNAL ERRORAn internal error occurred in the NetViewprogram. This can occur when any of theunderlying NetView services encounterproblems such as insufficient NetView storageor a task abnormally ending.

TEMA TOWER NOT ENABLEDThe NetView data collection command for thespecified subtower was not attempted becausethe TEMA tower was not enabled. If supportfor the monitoring agent is not wanted, youcan ignore this message.

Message Variables

subtower_nameThe name of the subtower for which data isbeing collected.

The following TEMA subtowers have datacollection that is managed through the NACTLcommand:v HEALTHv CONNACTv CONINACT

v SESSACT

The following subtowers have data collectionthat is managed through the COLLCTLcommand:

v DVIPA subtowers:– DVTAD– DVCONN– DVROUT

v DISCOVERY subtowers:– INTERFACES– TELNET

Other possible values:v DVDEF (equivalent to DVIPA tower data

collection)v APPL (equivalent to NetView application

data collection under the DISCOVERYtower)

The following ACTIVEACTIVE subtowershave data collection that is managed throughthe ACTVCTL command:

v DB2

v IMS

v LIFELINE

v VSAM

reason The reason for the failure. The values are:v ADVISOR NOT AVAILABLE OR ROLE

NOT PRIMARYv COMMAND FAILEDv INACTIVE NACMDv INTERNAL ERRORv TEMA TOWER NOT ENABLED.

System action: Data collection for the designatedsubtower is stopped.

Operator response: Take action based on the reasoncode received.

For the COMMAND FAILED reason, review theNetView log for additional messages. If necessary,contact your system programmer.

System programmer response: For an internal error,see the NetView log for a series of DWO050I messagesthat provide more information about the problem.

If the command failed, correct the autotask definitionsin the CNMSTYLE member. If the problem persists,contact IBM Software Support with the informationfrom the NetView log.

BNH900I ENTERPRISE MASTER FOR TYPEdata_type ESTABLISHED

Explanation: This message is issued on systems thathave been contacted by an enterprise master NetViewprogram and is forwarding management data to theenterprise master NetView program.

BNH881I • BNH900I


|||||||||

|

||

The BNH900I message is the first message in a groupof messages that can include the BNH901I, BNH902I,and BNH903I messages.

Message Variables

data_typeType of management data being forwarded.These are the types:

v ACTIVEACTIVE

v DISCOVERY

BNH901I NEW MASTER: domain ON system INXCF GROUP xcf_group IN SYSPLEXsysplex

Explanation: This message identifies the newenterprise master NetView program.

Message Variables

domain NetView domain name

system z/OS image name

xcf_groupXCF group of the enterprise master NetViewprogram

sysplex Name of the sysplex, or the sysplex nameused for a stand-alone system, where theenterprise master NetView program resides

BNH902I OLD MASTER: domain ON system INSYSPLEX sysplex

Explanation: This message identifies the old enterprisemaster NetView program. This message is not issued ifthere is no existing enterprise master NetView programwhen a new enterprise master takes over.

Message Variables



sysplex Name of the sysplex, or the sysplex nameused for a stand-alone system where theenterprise master NetView program resides

BNH903I Reason: reason_code

Explanation: This message specifies the reason thatthe enterprise master NetView program assumedcontrol.

Message Variables

reason_codeIndicates one of the following reasons:v 0: Initialization processing of ENT

statementsv 1: Restyle processing of ENT statementsv 2: Connectivity check driven by an internal

heartbeat timer

v 3: ACTVCTL TAKEOVER commandprocessing

BNH904I ENTERPRISE MASTER SWITCH FORTYPE data_type IN XCF GROUPxcf_group IN SYSPLEX sysplex

Explanation: This message is issued on a system thatis being acquired when it has an existing enterprisemaster NetView program. This message is not issued ifthere is no existing enterprise master NetView programwhen a new enterprise master takes over.

The BNH904I message is the first message in a groupof messages that can include the BNH901I andBNH903I messages.

Message Variables

data_typeType of data:v ACTIVEACTIVEv DISCOVERY

xcf_groupXCF group of the master NetView program

sysplex Name of the sysplex, or the sysplex nameused for a stand-alone system where themanaged NetView program resides

BNH905I ENTERPRISE MASTER PROCESSINGFINISHED. SYSTEMS FORWARDINGDATA:

Explanation: This message is issued at an enterprisemaster NetView program following completion ofENT.SYSTEMS statement processing. It is followed by aBNH906I message that includes a list of the systemsthat were taken over.

BNH906I DOMAIN SYSTEM SYSPLEX GROUPTYPES domain image_name sysplexxcf_group data_type

Explanation: This message accompanies a BNH905Imessage and contains a heading, followed by a list ofmanaged systems.

Message Variables

domain NetView domain name.

image_namez/OS image name.


xcf_groupXCF group

data_typeOne or more types of data:v ACTIVEACTIVE

BNH901I • BNH906I


v DISCOVERY

BNH907I ENTERPRISE MASTER REQUESTREJECTED FOR GROUP xcf_group INSYSPLEX sysplex FOR TYPE data_type.EXISTING MASTER IS system ONimage_name IN SYSPLEXmaster_sysplex_id. REASON=reason_code

Explanation: The enterprise master request is rejectedbecause another NetView system is already anenterprise master for this type of data. ENT.SYSTEMSprocessing initiated by NetView initialization, RESTYLEprocessing, or internal retry timers does not cause theNetView system to take over as enterprise master whenanother NetView system is already in that role.

Message Variables

xcf_groupXCF group.

sysplex Name of the sysplex, or the sysplex nameused for a stand-alone system




master_sysplex_idName of the sysplex, or the sysplex nameused for a stand-alone system where theenterprise master NetView program resides

reason_codeIndicates why the existing enterprise masterassumed that role:v 0 - Initialization processing of ENT

statementsv 1 - Restyle processing of ENT statementsv 2 - Connectivity check driven by an internal

heartbeat timerv 3 - ACTVCTL command processing

BNH908I DOMAIN domain_name ON SYSTEMimage_name IN SYSPLEX sysplexSUPPORTS ONLY THE DISCOVERYENTERPRISE DATA TYPE

Explanation: This message is issued at a masterNetView program when it encounters a system thatdoes not support the ACTIVEACTIVE category of data.Depending on the configuration, the master NetViewprogram might take over as master for DISCOVERYdata.

Message Variables

domain_nameNetView domain name

image_namez/OS image name.


BNH909I ERROR ENCOUNTERED INENTERPRISE PROCESSING FOR TYPEdata_type AT domain_name ONimage_name IN SYSPLEX sysplex

Explanation: This message is issued to the log whenan enterprise master NetView program encounters anerror in takeover processing on the NetView domainidentified in the message. The error identified by themessage applies only to the data_type, such asDISCOVERY, specified in the message. It mioght beable to take over for other types of data, such asACTIVEACTIVE. The errors are frequently due toconfiguration errors at the remote system, such as arequired tower not being enabled. The data_typespecifies the type of enterprise.

This message can accompany a DSI416I message thatidentifies the CNMEXCON DISCONNECT commandas failing and also identifies the root error message.

Message Variables


domain_nameNetView domain name

image_namez/OS system image

sysplex Name of the sysplex

System action: The data_type data is not forwarded tothe enterprise master from the remote system. Othertypes of data can be forwarded if the enterprise masteris configured for more than one type.

BNH910I NO SYSTEMS FORWARDING DATAFOR TYPE data_type

Explanation: This message is issued when theNetView program is unable to acquire any systems forthe data_type specified. BNH909 messages in the logmight indicate why it was unable to do so.

This message can accompany a BNH909I message.

Message Variables


BNH907I • BNH910I


BNH911I request : NO DATA FOUND FOR 'subject'

Explanation: No data is available for the specifiedrequest. This might be normal. Possible causes are asfollows:v No resources are configured or available.v The command is for a domain that is not in the

sysplex.v Other system failures, such as SNMP, have occurred.v For the ACTVLIFE and ACTVREPL commands:

– There is no data for the specified request. Thiscould be for one of the following reasons:- The command and its values are correct, and

there is no data.- A value specified in the command is for a

resource that does not exist.- For the ACTVLIFE command, the Load

Balancer might not be active.– A failure occurred collecting the requested

information.

Message Variables

request The function for which no data was found.

subject The requested data.

System action: Processing for the request ends.

Operator response: Verify the format and spelling ofthe specified operands. If the command uses a domainname, ensure that the correct domain is specified. If theformat, spelling, and domain are correct, notify thesystem programmer.

For the ACTVLIFE and ACTVREPL commands:

v Verify that the command is issued correctly.v Look in the NetView log for errors related to the

command. Contact the system programmer, ifnecessary, to resolve the error.

System programmer response: Verify that thefollowing conditions are true:v The local system, or the specified system (using the

NetView domain), has the specified data.v The specified NetView domain is known to the

master NetView program in a sysplex or theenterprise.– The enterprise master NetView program does not

have DVIPA data.– Use the LIST STATUS=XCFGRPS command to

determine acceptable domains from a masterNetView program.

v Related functions, such as SNMP, are active. See IBMTivoli NetView for z/OS Installation: ConfiguringAdditional Components for configuration informationabout the specified subject. Also, check the NetViewlog for other messages that are related to thisrequest.

For the ACTVLIFE and ACTVREPL commands:v Verify that the ACTIVEACTIVE towers and

subtowers are enabled on the correct systems.v For the ACTVLIFE command, verify that the

Multi-Site workload Lifeline product is active on thesystem where the command is issued.

v For the ACTVREPL command, verify that the Qreplication, IMS replication, or VSAM replicationproduct is active on the production system orsystems.

DSI Prefix MessagesThis section lists the DSI prefix messages.

DSI031I SPECIFIED NAME 'name' INVALID

Explanation: One of the following conditions mighthave occurred:

v The name you entered might not exist.

v The name is not valid for the specified use. Forexample, you might have issued the STOP TASKcommand for one of the following tasks: DSIATFMT,DSIBRWMT, DSIDCBMT, DSILOGMT. The NetViewprogram automatically restarts these tasks.

v The name is not in your span of control.

v The name is that of a command list that is defined inCNMCMD, but the member defined on theCMDDEF statement cannot be found.

v An attempt was made to delete the specifiedcommand name, but it cannot be deleted eitherbecause it is not defined or because it is an internalcommand and therefore cannot be deleted.

v The name is that of an operator that is currently inuse or has been deleted from the NetView program.

v The name is that of an operator that is currently notpermitted in the APPL class of the SAF product tolog on to this NetView.

v The name is reserved for use as the name of a virtualOST (VOST) to be created with the ATTACHcommand.

v The Tivoli Enterprise Portal Logonid value is toolong or contains characters that are not supported incommon global variable names.

v The mapped Tivoli Enterprise Portal Logonid doesnot meet the operator ID criteria for the NetViewprogram.

v The name is an autotask operator name that has beenrevoked by the SAF product.

v The socket path name for the Q replication, IMSreplication, or VSAM replication product does notstart with a forward slash (/), which is required.

For data collection, the invalid path is ignored, andthere is no connection attempt.

Additionally, no production system pathconfiguration information will be forwarded to the

BNH911I • DSI031I


||||

|||

||

||

controller system for the particular data source (DB2,IMS, or VSAM) and function (capture or apply). Thismight impact the execution of the ACTVREPLcommand.

v ENT.GROUP definition processing identified a groupthat is not valid. A group might be including itself asa member or specifying an invalid group as amember.

Message Variables

name The incorrect name specified or implied bydefault in the command.

System action: The command stops processing.

Operator response: Verify that the name is anoperator already in use. Check that the operator is avalid NetView operator ID. See the NetView onlinehelp for the correct command syntax. Enter thecommand again if you had syntax errors.


||||

||||


Appendix D. Scenario: Configuring remote monitoring serversto run in z/OS monoplexes using the configuration tool

The configuration described in Figure 5 on page 26 includes a hub monitoringserver that runs on a Linux on System z server. There are two remote monitoringservers, one running on the primary controller LPAR, and the other running on thebackup controller LPAR. The configuration steps for this scenario use the followinghost names and monitoring server names:

Table 14. Host names and monitoring server names for scenario 2

Host nameand role

Monitoring servernode ID and type RTE name Data set name prefix

TIVLNX21(non-z/OS)

HUB_TIVLNX21(hub monitoringserver)

n/a n/a

PCHOST(primarycontroller)

PCRTEM22:CMS(remote monitoringserver)

PCRTEM22 NETVIEW.EMAMVS22.PCRTEM22

BCHOST(backupcontroller)

BCRTEM23:CMS(remote monitoringserver)

BCRTEM23 NETVIEW.EMAMVS23.BCRTEM23

This scenario assumes that the hub monitoring server is already configured.

During the installation process, you must provide a host name or IP address forthe hub monitoring server. You are also required to enter passwords on somepanels. For some operating systems, you are required to provide a password of 6or more characters. Check the password requirements for your operating systembefore you begin the installation process.

Follow these steps to setup and configure the IBM Tivoli Monitoring environmentand the NetView agent using the configuration tool:v “Installing the Tivoli Management Services components”v “Setting up the configuration tool” on page 150v “Installing NetView agent code” on page 154v “Configuring the IBM Tivoli Monitoring environment on the primary and

backup controller systems” on page 154

Installing the Tivoli Management Services componentsTivoli Management Services consists of the following commonly sharedcomponents:v Tivoli Enterprise Portal Server and clientsv Tivoli Data Warehousev TMS:Enginev Event synchronization componentv Tivoli Enterprise Portal Server extended services

For a description of these components, see the OMEGAMON XE and TivoliManagement Services on z/OS Common Planning and Configuration Guide.


|

For information about installing these components, see the IBM Tivoli Monitoring:Installation and Setup Guide.

Setting up the configuration toolThe configuration tool uses ISPF dialog panels to guide you through productconfiguration steps. You must run some of the steps outside of the configurationtool because they affect system data sets. The configuration tool is restartable. Ifnecessary, you can end the dialog, start it again, and continue from the point ofinterruption.

The configuration tool provides default values wherever possible. You can changethe default values to meet the needs of your enterprise. For information about theconfiguration tool features, see the OMEGAMON XE and Tivoli Management Serviceson z/OS Common Planning and Configuration Guide.

You can also use the configuration tool to create a batch job that builds, configures,and loads a runtime environment. This is a useful way of replicating runtimeenvironments to other z/OS systems.

For instructions on installing the configuration tool, see the IBM Tivoli MonitoringServices Program Directory.

Creating or updating the configuration tool work libraryYou can set up the configuration tool in an existing consolidated softwareinventory (CSI), a cloned copy of an existing CSI, or a new CSI. To set up theconfiguration tool, copy the contents from the &thilev.TKCIINST target library intothe &shilev.INSTLIB work library. For sample JCL, see the OMEGAMON XE andTivoli Management Services on z/OS Common Planning and Configuration Guide.

Starting the configuration toolFollow these steps to start the configuration tool:1. Log on to a TSO session.2. Enter ISPF.3. From the Primary Option Menu, enter option 6 (Command).4. If you are using a 3270 Model 2 (24 x 80) display, turn off the predefined

function (PF) keys so that the configuration tool function keys are nottruncated. To turn off the predefined PF keys, enter PFSHOW on the commandline and repeat this command until the ISPF default function keys are no longerdisplayed.

5. From the command line, enter the following command:EX ’&shilev.INSTLIB’

&shilev is the high-level qualifier that you specified when you created theINSTLIB data set (for example, NETVIEW.V6R2INST).A panel like Figure 19 on page 151 is displayed or a job is displayed that youcan use to update the configuration tool to the most recent version.


Configuration tool usage notes:

a. Do not use the ISPF feature for edit recovery. If the ISPF RECOVERY ONcommand is entered, edits produce a recovery error message. Enter theRECOVERY OFF command to suppress the error messages.

b. ISPF supports a split screen configuration. Avoid using this mode becausethe last line of information at the bottom of the screen might not bedisplayed; you cannot scroll down. A split screen configuration can causeyou to miss important messages or steps.

c. The online help for the configuration tool contains detailed informationabout using the configuration tool panels. To display help information, pressthe F1 key (Help) or enter HELP on the command line.

d. The configuration tool readme files provide additional usage information. Ifyou enter R on the Runtime Environments panel, the configuration tooldisplays a list of available readme files for the selection.

Setting up your work environmentTo set up the work environment, specify the location of the work libraries andcustomize the JCL for submitted jobs. If you do not submit a job when you arerunning the configuration tool, the job is stored in the CI$UPG2 member in theINSTJOBS data set. You can submit the job later when you exit the configurationtool.

To set up the work environment, follow these steps:1. From the Main Menu panel shown in Figure 19, enter 1. The Set Up Work

Environment panel is displayed as shown in Figure 20 on page 152.

---------------------------------- MAIN MENU ----------------------------------OPTION ===>

Enter the number to select an option:

1 Set up work environment

2 Install products (Optional: for file-tailored SMP/E jobs)

3 Configure products

I Installation informationS Services and utilities

Installation and Configuration Assistance Tool Version 310.16© Copyright IBM Corp. 1992-2009

Licensed Material - Program Property of IBM

F1=Help F3=Back

Figure 19. Main menu

Appendix D. Scenario: Configuring remote monitoring servers to run in z/OS monoplexes using the configuration tool 151

2. Enter 1 to specify options that are used to create work data sets. The SpecifyOptions panel is displayed as shown in Figure 21.

3. Modify the values on the Specify Options panel as required by yourenterprise. These values are used to create the job statement for JCL that isgenerated by the configuration tool.

4. Press Enter to return to the Set Up Work Environment panel.5. Enter 2 to set up the configuration environment. The Set Up Configuration

Environment panel is displayed as shown in Figure 22 on page 153. Thevalues on this panel are used to customize JCL that is created by theconfiguration tool. The configuration tool is designed to configure products inmultiple runtime environments.

--------------------------- SET UP WORK ENVIRONMENT ---------------------------OPTION ===>

Last selectedEnter the number to select an option: Date Time

1 Specify JCL options2 Set up configuration environment3 Create batch mode job4 Allocate work libraries

Note: Once you create and submit the "Allocate work libraries" job,you must exit the installer and allow the job to run beforerestarting the installer.

F1=Help F3=Back

Figure 20. Set up work environment

------------------------------- SPECIFY JCL OPTIONS ---------------------------COMMAND ===>

Specify allocation and processing options:

JCL REGION value ==> 0M (Specify K/M suffix)

Unit/ Storclas/VolSer Mgmtclas PDSE

Installation work datasets ................ xxxxxx Nxxxxxx

Specify the job statement for Installer-generated JCL:

==> //useridA JOB (ACCT),’NAME’,CLASS=A,MSGCLASS=A,NOTIFY=&SYSUID==> //* DEFAULT JCL==> //*==> //*

Figure 21. Specify options


6. Verify that the VSAM, non-VSAM, and SMP/E (product target libraries) dataset high-level qualifiers are specified correctly. The length of the high-levelqualifier for the runtime libraries must be 26 characters or less.v Ensure that the Runtime Datasets High-Level Qualifier matches the qualifier

that you chose for the INSTLIB data set.v If high-level qualifiers for the runtime libraries have already been specified,

unlock them by selecting Unlock Runtime High-level Qualifiers from theConfiguration Services and Utilities panel. Refer to OMEGAMON XE andTivoli Management Services on z/OS Common Planning and Configuration Guidefor more information.

v For new high-level qualifiers, update the values.7. Review the unit and volume serial information and make any changes

required for your enterprise.8. After changing the values, press the Enter key to set the configuration values.9. Press the Enter key again (with no changes) to return to the Set Up Work

Environment panel.10. Enter 3 to create the batch mode job.11. Enter 4 to allocate work libraries.12. Update the Allocate Work Libraries job as required for your enterprise.

These work libraries are allocated by this job:

LibraryDescription

INSTDATAContains all installation-specific information.

INSTDATWContains installation-specific information that was loaded from thedistribution media.

INSTJOBSContains all generated jobs.

INSTLIBWContains the latest release of the installer component found on thedistribution media. If necessary, the contents of this data set is movedto the &shilev.INSTLIB data set.

----------------------- SET UP CONFIGURATION ENVIRONMENT ----------------------COMMAND ===>

RTE allocation routine ==> IKJEFT01 (IKJEFT01/IEFBR14)

Runtime Unit/ Storclas/Datasets High-Level Qualifier VolSer Mgmtclas PDSEVSAM NETVIEW.V6R2INST xxxxxx

xxxxxxNon-VSAM NETVIEW.V6R2INST xxxxxx N

xxxxxxWork ................................ xxxxxx

SMP/EDatasets High-Level QualifierTarget &thilev

Enter=Next F1=Help F3=Back

Figure 22. Set up configuration environment


INSTQLCK Used by installer internal processes as a locking data set. It is used toprevent concurrent updates to the same data set.

INSTSTATContains status-specific installation information.

Depending on the environment into which you are installing, some of the dataset members might not contain data.

13. On the command line, enter submit to run the Allocate Work Libraries job.14. Press F3 multiple times until you exit the configuration tool.

Note: You must exit the configuration tool for the Allocate Work Libraries jobto run.

15. Verify that you have a return code of 0 for the Allocate Work Libraries job.

Installing NetView agent codeTo install NetView agent code, perform the SMP/E installation as described in theNetView agent program directory.

Configuring the IBM Tivoli Monitoring environment on the primary andbackup controller systems

To configure the IBM Tivoli Monitoring environment on the primary and backupcontroller systems, follow these procedures:1. “Creating and configuring an RTE to contain the remote monitoring server and

NetView agent on the primary controller”2. “Creating and configuring an RTE to contain the remote monitoring server and

NetView agent on the backup controller” on page 1723. “Loading the agent data files and configuring the portal server” on page 464. “Historical data collection and reporting” on page 505. “Creating a custom navigator view” on page 50

Creating and configuring an RTE to contain the remotemonitoring server and NetView agent on the primary controller

The example in this section uses a full runtime environment (RTE) namedPCRTEM22. This environment contains all the libraries required by the remotemonitoring server and agent and is self-contained.RTE Name: PCRTEM22Type: FULLHilev: NETVIEW.EMAMVS22Midlev: PCRTEM22Shares with: (none)

Accessing the product selection panelFollow these steps to access the runtime environment component of theconfiguration tool:1. From the configuration tool Main Menu, enter 3. The Configure Products panel

is displayed.2. To select a product to configure, enter 1. The Product Selection Menu is

displayed as shown in Figure 23 on page 155.


||

||

|

|

|

Creating a full runtime environmentTo create the full runtime environment, you must add, build, configure, and loadthe runtime environment (RTE).

To add the runtime environment, follow these steps:1. From the product selection menu (Figure 23), enter S in the Actions field for

IBM Tivoli NetView for z/OS Agent V6.2.0. The Runtime Environments panelis displayed as shown in Figure 24. The actions associated with runtimeenvironments are shown on this panel.

2. From the Runtime Environments panel, enter the following information:a. In the Action field, type A to add an RTE.b. In the name field, type a name for this RTE. PCRTEM22 is the name used in

this example. The name is a unique identifier (up to eight characters),automatically used as the mid-level qualifier for FULL RTEs.

c. In the Type field, enter the type of RTE that your are creating. In this case,you are creating an RTE of the FULL type.

d. In the Description field, type a description for this RTE.3. Press Enter to add the new full RTE. The Add Runtime Environment panel is


---------------------------- PRODUCT SELECTION MENU ---------------------------

Actions: S Select product

IBM Tivoli Management Services on z/OS V6.3.0s IBM Tivoli NetView for z/OS Agent V6.2.0

F1=Help F3=Back F5=Refresh F7=Up F8=Down

Figure 23. Product Selection Menu

------------------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------

*** Current product entry selected: ***IBM Tivoli NetView for z/OS Agent V6.2.0

Actions: A Add RTE, B Build libraries, C Configure,L Load all product libraries after SMP/E,D Delete, U Update, V View values, Z UtilitiesR README Table of Contents

Action Name Type Sharing DescriptionA PCRTEM22 FULL Pri Cont NV62 EMA RTEMS HTEMS on TIVLNX21

F1=Help F3=Back (No RTEs defined, use Action A to Add)

Figure 24. Runtime environments panel


|

||||||||||||||||||

|||||

4. From the Add Runtime Environment panel, type the information required todefine the FULL RTE. The values you enter into the fields are used to allocateruntime libraries and to provide defaults for product configuration panels. Youmust enter a JCL suffix character. This RTE contains a Tivoli EnterpriseMonitoring Server.

5. Press Enter. The second Add Runtime Environment panel is displayed asshown in Figure 26.

6. Review and update the values as needed for your environment.v The configuration tool supports z/OS system symbolic variables for some of

the generated configuration values. You can enable system variable support,which is disabled by default. For more information, use the README SYScommand or see the OMEGAMON XE and Tivoli Management Services on z/OSCommon Planning and Configuration Guide.

v Blank out the VTAM values:– Applid prefix

-------------------- ADD RUNTIME ENVIRONMENT (1 of 3) -------------------------

RTE: PCRTEM22 Type: FULL Desc: Pri Cont NV62 EMA RTEMS HTEMS on TIVLNX21

Libraries High-level Qualifier Volser Unit Storclas Mgmtclas PDSENon-VSAM NETVIEW.EMAMVS22 xxxxxx 3390 NVSAM NETVIEW.EMAMVS22 xxxxxxMid-level qualifier ==> PCRTEM22

JCL suffix ==> A Remote RTE for transport ==> N (Y, N)STC prefix ==> CANS Runtime members analysis ==> Y (Y, N)SYSOUT class ==> X Diagnostic SYSOUT class ==> XLoad optimization ==> N (Y, N)

Will this RTE have a Tivoli Enterprise Monitoring Server ==> Y (Y, N)If Y, TEMS name ==> PCRTEM22:CMS (Case sensitive)

Copy configuration values from RTE ==> (Optional)


Figure 25. Add runtime environment panel for FULL scenario


Use z/OS system variables? ==> N (Y, N) Use VTAM model applids? ==> N (Y, N)RTE name specification ==> &SYSNAMERTE base alias specification ==>Applid prefix specification ==> K&SYSCLONE.

Security system ==> NONE (RACF, ACF2, TSS, NAM, None)ACF2 macro library ==>Fold password to upper case ==> Y (Y, N)

VTAM values are required under certain conditions. Press F1=Help:Applid prefix ==> Network ID ==>Logmode table ==> LU6.2 logmode ==>

If you require TCP/IP communications for this RTE, complete these values:Hostname ==> ip_address or host_name

Started task ==> * (Recommended default = *)Port number ==> 1918Enter=Next F1=Help F3=Back

Figure 26. Second runtime environment panel for FULL scenario


|||||||||||||||||||||||||

||||||||||||||||||||||||||

– Logmode table– Network ID– LU6.2 logmode

v Specify the IP address or host name for the remote monitoring server.v Specify the TCP/IP stack name to be used. If your LPAR contains a single

TCP/IP stack, you can specify an asterisk (*). If your LPAR contains multipleTCP/IP stacks, specify the TCP/IP stack to be used by the agent to establisha connection to the monitoring server.The following values are valid:

* Specifies that the first TCP/IP stack that was started is to be used.

# Translated by the configuration tool to a blank; specifies that theTCP/IP environment is to choose the stack to use, either throughTCP/IP definitions or through the use of the SYSTCPD DDstatement.

stack_nameSpecifies that the named TCP/IP stack is to be used. This stack nameis the TCP/IP started task name.

Note: Whichever method is used to select a TCP/IP stack in a multi-stackenvironment, the IBM Tivoli Monitoring platform continues to use that stack.This selected stack is used even if conditions change such that a differentstack becomes the primary stack.

v The port number specifies the base port number of the monitoring server.7. Press Enter. A VTAM warning panel is displayed.8. Press Enter again. A third Add Runtime Environment panel is displayed.

Review and update the values as required for your environment.9. Press Enter to return to the main Runtime Environments panel.

To build the libraries for this runtime environment, follow these steps:1. From the Runtime Environments panel, type B in the Action field and then

press Enter. The JCL to allocate the runtime libraries is displayed.2. Review the JCL and then submit the job.3. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Runtime Environments (RTE) panel.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.

Configuring the remote Tivoli Enterprise Monitoring ServerTo configure the remote Tivoli Enterprise Monitoring Server, follow these steps:1. Start this configuration at the Runtime Environments panel as shown in

Figure 27 on page 158.


||

2. Enter C in the Action field next to the PCRTEM22 RTE to display the ProductComponent Selection menu.

3. Enter 1 to select the Tivoli Enterprise Monitoring Server component. TheConfigure the TEMS Menu panel as shown in Figure 28 is displayed.

Complete the steps on this panel in the order shown, starting with step 2 (Specifyconfiguration values). This monitoring server does not use SNA. The Date andTime fields on this panel are blank when you first access this panel. As youperform the tasks, the Date and Time fields are displayed to help you to track yourprogress.

The steps in this process are explained in the sections that follow.

Specifying configuration parameters: Do these steps to define this remote TivoliEnterprise Monitoring Server.1. From the Configure the TEMS panel, enter 2. The Specify Configuration

Values panel as shown in Figure 29 on page 159 is displayed.

------------------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------COMMAND ===>



Action Name Type Sharing Description

C PCRTEM22 FULL Pri Cont NV62 EMA RTEMS HTEMS on TIVLNX21Enter=Next F1=Help F3=Back F7=Up F8=Down

Figure 27. Runtime environments panel for hub monitoring server RTE

-------------------- CONFIGURE THE TEMS / RTE: PCRTEM22 -----------------------

Each RTE can contain only one TEMS. To configure Last selectedthe TEMS for this RTE, perform these steps in order: Date Time

I Configuration information (What’s New) <=== Revised

1 Create LU6.2 logmode2 Specify configuration values3 Specify communication protocols4 Configure TEMS Self-Describing Agent parameters5 Create runtime members6 Configure persistent datastore7 Complete the configuration

Optional:

8 View TEMS list and registration status9 Generate sample migration JCL

F1=Help F3=Back

Figure 28. Configure the TEMS for the selected RTE panel


||||||||||||||||||||||||||

2. If necessary, update the TEMS started task field.3. Specify REMOTE in the Type field.4. To configure the Program to Program Interface Information to forward Take

Action commands to the NetView program, see IBM Tivoli NetView for z/OSInstallation: Configuring the NetView Enterprise Management Agent.

5. Press Enter. The Communication Selection Panel as shown in Figure 30 isdisplayed.

6. Press F5. The Specify Configuration - Hub Values for Remote TEMS as shownin Figure 31 on page 160 is displayed.

------------------------- SPECIFY CONFIGURATION VALUES ------------------------

Started task ==> CANSDSSTType (Hub or Remote) ==> REMOTEHub TEMS type ==> (HA=High Availability)

Security settings:Validate security? ==> N (Y, N)

TMS password encryption information:Integrated Cryptographic Service Facility (ICSF) installed? ==> N (Y, N)

ICSF load library==> CSF.SCSFMOD0TMS encryption key==> IBMTivoliMonitoringEncryptionKey

Program to Program Interface (PPI) information:Forward Take Action commands to NetView for z/OS? ==> N (Y, N)

NetView PPI receiver ==> CNMPCMDRTEMS PPI sender ==>

Enter=Next F1=Help F3=Back F5=Advanced

Figure 29. Specify configuration values panel

----------------- COMMUNICATION SELECTION PANEL FOR PCRTEM22 -----------------COMMAND ===>

Select the hub (primary TEMS) to connect to this remote TEMS.

The TEMS table below lists eligible TEMS that you have configured inthis NETVIEW.EMAMVS22.INSTLIB.Enter S next to the TEMS that you wish to connect to this remote.Important: To manually enter the *TEMS information, press F5=Advanced.

* Typically applicable to non-local TEMS in another platformor in another RTE not known to this installation environment.

-----------------------------------------------------------------------------TEMS RTE name RTEType (mid-level) Description

-----------------------------------------------------------------------------F1=Help F3=Back F5=Advanced F7=Up F8=Down

Figure 30. Communication selection panel


7. Press Enter to return to the Specify Configuration Values panel.8. Press F5. The Specify Advanced Configuration Values panel as shown in

Figure 32 is displayed.

9. Accept the default values or make changes required by your enterprise.For the Reconnect after TCP/IP Recycle field, specify Y. This allows TCP/IP tobe restarted without having to restart the monitoring server.

10. Press Enter to return to the Specify Configuration Values panel.11. Press Enter again to return to the Configure the TEMS panel.

Specifying communication protocols: Use the Specify Communication Protocolspanel to specify the communication protocol for the Tivoli Enterprise MonitoringServer. You can also define the communication protocol priority sequence. Whencommunication with another component is initiated, the product tries the protocolsin the specified order.

------------ SPECIFY CONFIGURATION - HUB VALUES FOR REMOTE TEMS ---------------

Hub TEMS name (Case sensitive) ==> HUB_TIVLNX21

Complete this section if the Remote TEMS is connecting to its Hub TEMSusing SNA. Enter the applicable VTAM values of its Hub TEMS:

Global location broker applid of Hub ==>Network ID of Hub ==>

Complete this section if the Remote TEMS is connecting to its Hub TEMSusing IP. Enter the applicable network address and respective port number(s):

Network address (Hostname of Hub):==> TIVLNX21

IP.PIPE port number ==> 1918 (Non-secure NCS RPC)IP6.PIPE port number ==> (IP.PIPE for IPV6)IP.SPIPE port number ==> (Secure IP.PIPE)IP6.SPIPE port number ==> (Secure IP.PIPE for IPV6)IP.UDP port number ==> (Non-secure NCS RPC)IP6.UDP port number ==> (IP.UDP for IPV6)


Figure 31. Specify configuration - hub values for remote TEMS panel

-------------------- SPECIFY ADVANCED CONFIGURATION VALUES -------------------COMMAND ===>

Enable Web Services SOAP Server ==> Y (Y, N)Enable Tivoli Event Integration Facility (EIF) ==> N (Y, N)

Enable startup console messages ==> Y (Y, N)Enable communications trace ==> N (Y, N, D, M, A)Reconnect after TCP/IP recycle ==> Y (Y, N)Enable storage detail logging ==> Y (Y, N)

Storage detail logging: Hours ==> 0 (0-24) Minutes ==> 60 (0-60)Flush VSAM buffers: Hours ==> 0 (0-24) Minutes ==> 30 (0-60)

Virtual IP Address (VIPA) type ==> N (S=Static, D=Dynamic, N=None)Minimum extended storage ==> 768000 KMaximum storage request size ==> 16 (Primary) ==> 24 (Extended)Language locale ==> 1 (Press F1=Help for a list of codes)

z/OS Audit collection values:Enable/Disable z/OS audit collection ==> (M, B, D, X)Maximum in-memory cache entries ==> (10-1000)Domain ==>

Enter=Next F1=Help F3=Back F5=Advanced F6=PDS F10=CMS List

Figure 32. Specify advanced configuration values panel


|||||||||||||||||||||||||

|||||||||||||||||||||||||||

1. From the Configure the TEMS panel, enter 3. The Specify CommunicationProtocols panel is displayed as shown in Figure 33.

2. Review the default values for the priority sequence. The IP.PIPE protocol ischosen because it is connection-oriented and can be used to detect and recoverfrom communication errors more quickly.

3. Press Enter. The panel for the priority 1 protocol (IP.PIPE) as shown inFigure 34 is displayed.

4. Review the default values on the Specify IP.Pipe Communication Protocol paneland make any changes necessary for your environment.

5. Press Enter to complete the IP.Pipe configuration. A warning panel is displayedbecause you did not specify the SNA protocol.

6. Press Enter to accept the warning and return to the Configure the TEMS panel.

Optional: Specifying self-describing agent parameters: Do these steps toauthorize the processing of self-describing agent data.

----------------------- SPECIFY COMMUNICATION PROTOCOLS -----------------------

Specify the communication protocols in priority sequence forTEMS PCRTEM22:CMS.

IP.PIPE ==> 1 (Non-secure NCS RPC)IP.UDP ==> (Non-secure NCS RPC)IP6.PIPE ==> (IP.PIPE for IPV6)IP6.UDP ==> (IP.UDP for IPV6)IP.SPIPE ==> (Secure IP.PIPE)IP6.SPIPE ==> (Secure IP.PIPE for IPV6)SNA.PIPE ==> (Non-secure NCS RPC)

Note: SNA.PIPE is required under certain conditions. Press F1=Help.* This Remote TEMS reports to a Hub that uses IP.PIPE to connect.

Ensure that this Remote TEMS also specifies the IP.PIPE protocol.* The protocol(s) in use by the Hub TEMS are:

-Unsecured IP.PIPE


Figure 33. Specify communication protocols panel

-------------------- SPECIFY IP.PIPE COMMUNICATION PROTOCOL -------------------

Specify IP.PIPE communication values.

* Network address (Hostname):==> ip_address or host_name

Started task ==> * (Recommended default = *)Network interface list: (If applicable)==>

Port number ==> 1918 (IP.PIPE)Port number ==> (IP.PIPE for IPV6)Port number ==> (Secure IP.PIPE)Port number ==> (Secure IP.PIPE for IPV6)

Address translation ==> N (Y, N)Partition name ==>

* Note: See F1=Help for TSO HOMETEST command instructions.Enter=Next F1=Help F3=Back

Figure 34. Specify IP.PIPE communication protocol panel


||||||||||||||||||||||||||

1. From the Configure the TEMS panel, enter 4. The Configure TEMSSelf-Describing Agent Parameters panel is displayed.

2. Select option 1 to specify the parameters that the monitoring server requires toprocess self-describing agent data.

3. Selection option 2 to create and configure runtime members.4. Selection option 3 to create USS directories and copy files to USS.5. Press enter until you return to the Configure the TEMS panel.

For more information about enabling the self-describing agent functions, see IBMTivoli OMEGAMON XE and Tivoli Management Services Configuring the TivoliEnterprise Monitoring Server on z/OS.

Creating runtime members: Do these steps to create the runtime membersrequired by the remote Tivoli Enterprise Monitoring Server. These members arecreated in the runtime libraries for this runtime environment.1. From the Configure the TEMS panel, enter 5 to create runtime members.2. Review and edit the JCL to make changes required by your enterprise.3. Submit the job.4. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Configure the TEMS panel.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.

Configuring the persistent data store: You are required to configure thepersistent data store. The persistent data store contains generic history for theTivoli Enterprise Monitoring Server. Use the following steps to do theconfiguration:1. From the Configure the TEMS panel, enter 6 to configure the persistent data

store. The Configure Persistent Datastore panel is displayed as shown inFigure 35.

2. To modify and review data store specifications, select 1 and then press Enter.The Persistent Datastore Specifications panel is displayed as shown inFigure 36 on page 163.

------------------------ CONFIGURE PERSISTENT DATASTORE -----------------------Last selected

Perform these configuration steps in order: Date Time

1 Modify and review datastore specifications2* Create or edit PDS maintenance jobcard3 Create runtime members4 Allocate and initialize datastore files5 Complete persistent datastore configuration

* Note: The initial PDS maintenance jobcard defaults to the jobcardset on the Set up work environment option. This jobcard isshared by all products that configured historical collectionwithin this RTE=PCRTEM22. Change to a generic jobcard, asnecessary.

F1=Help F3=Back

Figure 35. Configure Persistent Datastore panel


|

|

3. Update the values on this panel to control the size, placement, and number ofdata sets that make up the persistent data store.

4. For the values to take effect, press Enter.5. To return to the Configure Persistent Datastore panel, press F3.6. To create or edit parameters used on the persistent data store maintenance job

card, select 2 from the Configure Persistent Datastore panel and press Enter.The job card is used by the following persistent data store maintenance jobs:v KPDPROCC member in the RKANSAM data setv KPDPROC1 member in the RKANSAMU data set

7. Edit the job card and make changes required by your enterprise.8. To return to the Configure Persistent Datastore panel, press Enter.9. From the Configure Persistent Datastore panel, select 3 and press Enter to

create runtime members. This job creates the persistent data store allocationconfiguration members.

10. Review and edit the JCL and make any changes necessary for your enterprise.11. Submit the job.12. Verify that the job completes and check the return code.

v If the job completes successfully, the return code is 0 or 4 (COPYUSRJ orCOPYUSRP step). Press F3 to return to the Configure Persistent Datastorepanel.

v If the return code is not 0 or 4, check the job log to diagnose errors andthen run the job again.

13. On the Allocate Persistent Datastore panel, select 4 and press Enter to reviewthe job that allocates the persistent data store.


v If the job completes successfully, the return code is 0. Press F3 to return tothe Configure Persistent Datastore panel.

v If the return code is not 0, check the job log to diagnose errors and then runthe job again.

17. Press F3 twice to return to the Product Component Selection Menu panel.

For information about maintaining the persistent data store, see the IBM TivoliMonitoring: Administrator's Guide.

Configuring the NetView agent (primary controller)To configure the NetView agent, follow these steps:

--------------------- PERSISTENT DATASTORE SPECIFICATIONS ---- Row 1 to 1 of 1COMMAND ===>

Modify persistent datastore allocation and maintenance information as required.Press Enter to accept values and then F3 to return.

Datastore high-level qualifier: NETVIEW.EMAMVS22.PCRTEM22

Group -Datasets in Group- Volser/ Storclas/ -Est Cyl- -Maintenance-Name Lowlev Count Unit Mgmtclas Space Backup Export Extract-------------------------------------------------------------------------------GENHIST RGENHIS 3 xxxxxx ________ 36__ N N N

3390____ ________F1=Help F3=Back

Figure 36. Persistent data store specifications panel


||

1. From the Product Component Selection Menu panel, enter 2 to select theNetView for z/OS Agent. The Configure NetView for z/OS Agent V6.2.0 panelis displayed as shown in Figure 37.

Complete the steps on this panel in the order shown, beginning with step 1.The Date and Time fields on this panel are blank when you first access thispanel. As you perform the tasks, these fields are completed to help you to trackyour progress.The steps in this process are explained in the sections that follow.

Registering with the local Tivoli Enterprise Monitoring Server: Do the followingsteps to register the NetView agent with the local Tivoli Enterprise MonitoringServer.1. Select 1 and press Enter.2. Review and edit the JCL, and then submit the job.3. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Configure NetView for z/OS Agent panel.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.

Specifying configuration parameters: Follow these steps to specify configurationvalues required by the NetView agent.1. From the Configure NetView for z/OS Agent V6.2.0 panel, enter 2. The Specify

Configuration Parameters panel is displayed as shown in Figure 38 on page165.

----- CONFIGURE NetView for z/OS Agent V6.2.0 / RTE: PCRTEM22 --–-----–-----–--Last selected

Perform the appropriate configuration steps in order: Date Time


If you have defined a TEMS in this RTE that this Agentwill communicate with, select option 1.

1 Register with local TEMS

2 Specify configuration parameters

3 Specify Agent address space parameters

4 Create runtime members

5 Configure persistent datastore (in Agent)

6 Complete the configuration

F1=Help F3=Back F5=Advanced

Figure 37. Configure NetView for z/OS V6.2.0 panel


2. Verify the following information on the panel and change it as needed for yourenvironment:v The NetView Enterprise Management Agent PPI receiver is required for

communication with the NetView address space. The default isCNMEMARX. If you change this value, also change the NACMD.DESTPPIstatement in the CNMSTUSR or CxxSTGEN member to match this value. Forinformation about changing CNMSTYLE statements, see IBM Tivoli NetViewfor z/OS Installation: Getting Started. For information about accepted values ofthe PPI receiver name, see the RECEIVER-ID section in the IBM TivoliNetView for z/OS Application Programmer's Guide.

v The NetView agent uses the NetView CNMLINK link library. The defaultlibrary is NETVIEW.V6R2M0.CNMLINK. The link library is listed in the NetViewCNMPROC (CNMSJ009) procedure.

3. Press Enter to return to the Configure NetView for z/OS Agent V6.2.0 panel.

Specifying agent address space parameters: Do the following steps to specify theagent address space parameters.1. From the Configure NetView for z/OS Agent V6.2.0 panel, select 3 and press

Enter. The Specify Agent Address Space Parameters panel is displayed asshown in Figure 39 on page 166.

--------------- SPECIFY CONFIGURATION PARAMETERS / RTE: PCRTEM22 --------------

Specify the following information:

NetView Enterprise Management Agent PPI Receiver (CNMEMARX):==> CNMEMARX

NetView Enterprise Management Agent PPI Sender (CNMEMATX):==> CNMEMATX

Specify the following library:

NetView linklib (NETVIEW.V6R2M0.CNMLINK):==> NETVIEW.V6R2M0.CNMLINK

F1=Help F3=Back

Figure 38. Specify configuration parameters panel


2. Review the default values and make any changes required by your enterprise.The communication protocols that you specify must match the protocols thatwere specified when the Tivoli Enterprise Monitoring Server was configured.Specify only the IP.PIPE connection as shown in Figure 39. IP.PIPE isconnection-oriented and can be used to detect and recover fromcommunication errors more quickly.

3. Press F5. The Specify Advanced Agent Configuration Values panel isdisplayed as shown in Figure 40.

4. Specify Y to enable the secondary monitoring server.5. Specify Y to reconnect after a TCP/IP recycle.6. To configure the Program to Program Interface Information to forward Take


-------------------- SPECIFY AGENT ADDRESS SPACE PARAMETERS -------------------

The following information is needed to define the Agent address space.Agent started task ==> CANSNAConnect to TEMS in this RTE ==> Y (Y, N)

Name of Primary TEMS ==> PCRTEM22:CMS

Specify the communication protocols in priority sequence.IP.PIPE ==> 1 (Non-secure NCS RPC)IP.UDP ==> (Non-secure NCS RPC)SNA.PIPE ==> (Non-secure NCS RPC)IP6.PIPE ==> (IP.PIPE for IPV6)IP6.UDP ==> (IP.UDP for IPV6)IP.SPIPE ==> (Secure IP.PIPE)IP6.SPIPE ==> (Secure IP.PIPE for IPV6)

Note: Enable only protocol(s) in use by the Primary TEMS.

Enter=Next F1=Help F3=Back F5=Advanced F10=CMS List

Figure 39. Specify agent address space parameters panel

----------------- SPECIFY ADVANCED AGENT CONFIGURATION VALUES -----------------

Specify the advanced configuration options for this Agent.

Enable secondary TEMS ==> Y (Y, N)Name of secondary TEMS ==> None

Enable startup console messages ==> N (Y, N)Enable WTO messages ==> N (Y, N)Reconnect after TCP/IP recycle ==> Y (Y, N)Intervals (hh:mm):


Virtual IP Address (VIPA) type ==> N (S=Static, D=Dynamic, N=None)Minimum extended storage ==> 256000 KLanguage locale ==> 1 (Press F1=Help for a list of codes)Program to Program Interface (PPI) information:

Forward Take Action commands to NetView for z/OS? ==> N (Y, N)NetView PPI receiver ==> CNMPCMDR Agent PPI sender ==>

z/OS Audit collection values:Enable/Disable z/OS audit collection ==> (M, B, D, X)Maximum in-memory cache entries ==> (10-1000)Domain ==>

Enable Self-Describing Agent processing (TEMA_SDA) ==> Y (Y, N)


Figure 40. Specify Advanced Agent Configuration Values panel


|||||||||||||||||||||||||

7. Review the remaining values and make any changes necessary for yourenvironment.

8. Press Enter to display the Communications Selection panel as shown inFigure 41.

9. Press PF5 (Advanced) to display the Specify Agent Secondary TEMS Valuespanel as shown in Figure 42.

10. Review the Backup TEMS Name and Network Address fields and press Enter.11. Press PF5 (Advanced) again. The Specify Nonstandard Parameters panel is


----------------- COMMUNICATION SELECTION PANEL FOR PCRTEM22 Row 1 to 1 of 1COMMAND ===>

Select the secondary TEMS to connect to this agent.

The TEMS table below lists eligible TEMS that you have configured inthis NETVIEW.EMAMVS22.INSTLIB.Enter S next to the TEMS that you wish to connect to this agent.Important: To manually enter the *TEMS information, press F5=Advanced.



-----------------------------------------------------------------------------_ REMOTE PCRTEM22 Pri Cont NV62 EMA RTEMS HTEMS on TIVLNX21F1=Help F3=Back F5=Advanced F7=Up F8=Down

Figure 41. Communications Selection panel

-------------------- SPECIFY AGENT SECONDARY TEMS VALUES ----------------------COMMAND ===>

Backup TEMS name ==> BCRTEM23:CMS (case sensitive)

Complete this section if the Agent is connecting to its secondary TEMSusing the SNA and/or IP protocol(s):

SNA protocol (Enter applicable VTAM values of its secondary TEMS):LU6.2 logmode ==>Local location broker applid ==>Network ID ==>

IP protocol (Enter applicable network address values):* Network address (Hostname of Secondary TEMS):

==> BCHOST

* Note: See F1=Help for TSO HOMETEST command instructions.


Figure 42. Specify Agent Secondary TEMS Values


Enter the following values:v KNA_ACTACT (parameter)v =YES (value for the first parameter)v CTIRA_PRIMARY_FALLBACK_INTERVAL (parameter)v =150 (value for the second parameter)v RKANPARU (low-level data set qualifier)v KNAENV (member name)

12. To return to the Specify Agent Address Space Parameters panel, press Enterand then press PF3.

13. From the Specify Agent Address Space Parameters panel, press Enter. TheSpecify Agent IP.PIPE Configuration Values panel is displayed as shown inFigure 44.

14. Review the default values on the Specify Agent IP.PIPE Configuration Valuespanel and make any changes necessary for your environment.


Creating runtime members: Do the following steps to create runtime membersfor the NetView agent.

---------------- SPECIFY NONSTANDARD PARAMETERS / RTE: PCRTEM22 --------------OPTION ===>

This panel is used to add nonstandard parameters to runtime members.

Warning: This should be used under the guidance of IBM Software Support.

Parameter: KNA_ACTACT_____________________________New Value: =YES_____________________________________________Old Value (if replacing): ___________________________________________________Low-level dataset qualifier: RKANPARU Member: KNAENV__

Parameter: CTIRA_PRIMARY_FALLBACK_INTERVAL________New Value: =150______________________________________________Old Value (if replacing): ___________________________________________________Low-level dataset qualifier: RKANPARU Member: KNAENV__

Parameter: _______________________________________New Value: _________________________________________________Old Value (if replacing): ___________________________________________________Low-level dataset qualifier: ________ Member: ________

Figure 43. Specify Nonstandard Parameters panel

------------------ SPECIFY AGENT IP.PIPE CONFIGURATION VALUES -----------------

Specify the IP.PIPE communication values for this Agent. These networkaddress-related values are for the z/OS system where the Agent runs on.


Started task ==> * (Recommended default = *)Network interface list:

==>

Specify additional configuration values.




Figure 44. Specify agent IP.PIPE configuration values panel


|

>

|

1. From the Configure NetView for z/OS Agent V6.2.0 panel, select 4 and pressEnter.

2. Review the JCL and make any changes necessary for your environment, thensubmit the job.

3. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.4. Press F3 to return to the Configure NetView for z/OS Agent V6.2.0 panel.

Configuring persistent data store in the agent: Persistent data stores areassociated with each Tivoli Enterprise Monitoring Server and each agent. Thepersistent data store in this section is for the NetView agent.

The following procedure generates JCL that configures a persistent data store thatis added to the agent address space for historical data collection. You start thecollection of short-term history at the Tivoli Enterprise Portal using the HistoryCollection Configuration dialog. If the person who configures the collection at theTivoli Enterprise Portal chooses TEMS for Collection Location, these agent data setsare not used. You might run out of storage for short-term history, depending onpersistent data store collection at the Tivoli Enterprise Monitoring Server. If youperform this procedure, configure historical collection to Collect at Agent.

Do these steps to configure a persistent data store for the NetView agent.1. From the Configure NetView for z/OS Agent V6.2.0 panel, select 5 and press

Enter. The Specify Persistent Datastore Values panel is displayed as shown inFigure 45.

2. Specify the values for allocating the persistent data store and then press Enter.The Configure Persistent Datastore panel is displayed as shown in Figure 46on page 170.

--------------------- SPECIFY PERSISTENT DATASTORE VALUES ---------------------

The following values are used to allocate and maintain PersistentDatastore for standalone Agents. For efficiency, use the samemaintenance procedure prefix for all your runtime environments (RTEs).

Datastore high-level prefix: NETVIEW.EMAMVS22.PCRTEM22

Maintenance procedure prefix ==> KPDPROCAllocation volume ==> xxxxxxAllocation unit ==> 3390Allocation STORCLAS ==>Allocation MGMTCLAS ==>


Figure 45. Specify persistent data store values panel


3. To modify and review the data store specification, enter 1. The PersistentDatastore Specifications panel is displayed as shown in Figure 47.

4. Review the values on this panel, change them as necessary, and then pressEnter.

5. Press F3 to return to the Configure Persistent Datastore panel.6. From the Configure Persistent Datastore panel, select 2, and press Enter to

create or edit parameters used on the persistent data store maintenance jobcard. The job card is used by the following persistent data store maintenancejobs:v KPDPROCC member in the RKANSAM data setv KPDPROC1 member in the RKANSAMU data set

7. Edit the job statement and make changes that are necessary for yourenvironment.

8. Press Enter to return to the Configure Persistent Datastore panel.9. From the Configure Persistent Datastore panel, select 3 and press Enter.

Information about a simplified PDS maintenance procedure is displayed.10. Press Enter to review the job that creates the runtime members.11. Review and update the JCL as needed for your environment, and submit the

job.12. Verify that the job completes and check the return code.

v If the job completes successfully, the return code is 0 or 4 (COPYUSRJ step).Press F3 to return to the Configure Persistent Datastore panel.




* Note: The initial PDS maintenance jobcard defaults to the jobcardset on the Set up work environment option. This jobcard isshared by all products that configured historical collectionwithin this RTE=PCRTEM22. Change to a generic jobcard, asnecessary.

F1=Help F3=Back

Figure 46. Configure persistent data store for the monitoring agent



Datastore high-level qualifier: NETVIEW.EMAMVS22.PCRTEM22

Group -Datasets in Group- Volser/ Storclas/ -Est Cyl- -Maintenance-Name Lowlev Count Unit Mgmtclas Space Backup Export Extract-------------------------------------------------------------------------------KNA RKNAHIS 3 xxxxxx ________ 140_ N N N

3390____ ________F1=Help F3=Back



v If the return code is not 0 or 4, check the job log to diagnose errors and runthe job again.

13. On the Configure Persistent Datastore panel, select 4 and press Enter toreview the job that allocates the persistent data store.

14. Review and update the JCL as needed for your environment, and submit thejob.

15. Verify that the job completes and then check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Configure Persistent Datastore panel.v If the return code is not 0, check the job log to diagnose errors and run the

job again.16. Press F3 multiple times until you return to the Runtime Environments panel.


Loading the runtime librariesFollow these steps to load the runtime libraries for the monitoring server:1. From the Runtime Environments panel, enter L in the Action field next to the

PCRTEM22 FULL RTE.2. Review the JCL and make any changes necessary for your environment, and

then submit the jobs.3. Verify that the jobs complete and check the return codes.v If both jobs complete successfully with return code is 0. Exit the

configuration tool.v If either job ends with a return code other than 0, check the job log to

diagnose errors and then run the job again.

Completing the configuration on the primary controllerTo complete the configuration:v APF-authorize your librariesv Authorize the KPDDSCO progamv Copy the started task procedures to your procedure library

The configuration tool is not used to perform these steps.

APF-authorizing your libraries: Some of the libraries created by the configurationtool must be APF-authorized. Ensure that the following libraries are added to thelist of APF-authorized libraries:v RKANMOD for the PCRTEM22 RTEv RKANMODL for the PCRTEM22 RTEv RKANMODU for the PCRTEM22 RTEv Any other runtime libraries that are concatenated in the STEPLIB DDNAME and

in the RKANMODL DDNAME of the CANSNA and CANSDSST started tasks

For information about APF-authorizing these data sets, see IBM Tivoli NetView forz/OS Installation: Getting Started.

Authorizing the KPDDSCO program: Persistent data store maintenance uses theKPDDSCO program. This program must run as an authorized program under TSO.


||

||

||

|

|

|

|

|||

|

|

|

||

||

||

To authorize the KPDDSCO program, update the IKJTSOxx member in theSYS1.PARMLIB data set. For information about authorizing this program, see IBMTivoli NetView for z/OS Installation: Getting Started.

You can refresh the IKJTSOnn member by issuing the following SET command:T IKJTSO=nn

Copying the started task procedures to your procedure library: You used theconfiguration tool to create started task procedures in the RKANSAMU data set. Tocomplete the configuration, do these steps:1. Copy the Tivoli Enterprise Monitoring Server started task (CANSDSST) from

the RKANSAMU data set to your PROCLIB data set.2. Copy the started task (CANSNA) from the RKANSAMU data set to your

PROCLIB data set.3. The started task procedures include a SYSTCPD DD statement that is

commented out. Tivoli Management Services requires that host names beresolvable by TCP/IP. If your environment does not include a domain nameservice, uncomment this DD statement and modify it to comply with yourenvironment.

4. Copy the persistent data store maintenance procedure (KPDPROC1) from theRKANSAMU data sets to your PROCLIB data set.

You can now start the monitoring server and the NetView agent, for example:s cansdssts cansna

Creating and configuring an RTE to contain the remotemonitoring server and NetView agent on the backup controller

The example in this section uses a full runtime environment (RTE) namedBCRTEM23. This environment contains all the libraries required by the remotemonitoring server and agent and is self-contained.RTE Name: BCRTEM23Type: FULLHilev: NETVIEW.EMAMVS23Midlev: BCRTEM23Shares with: (none)

Accessing the product selection panelFollow these steps to access the runtime environment component of theconfiguration tool:1. From the configuration tool Main Menu, enter 3. The Configure Products panel

is displayed.2. To select a product to configure, enter 1. The Product Selection Menu is

displayed.

Creating a full runtime environmentTo create the full runtime environment, you must add, build, configure, and loadthe runtime environment (RTE).

To add the runtime environment, follow these steps:1. From the product selection menu, enter S in the Actions field for IBM Tivoli

NetView for z/OS Agent V6.2.0. The Runtime Environments panel is displayedas shown in Figure 48 on page 173. The actions associated with runtime


|||

|

|

|||

||

||

|||||

||

|

||

|

|

|||

|||||

|||

||

||

|||

|

|||

environments are shown on this panel.

2. From the Runtime Environments panel, enter the following information:a. In the Action field, type A to add an RTE.b. In the name field, type a name for this RTE. BCRTEM23 is the name used in

this example. The name is a unique identifier (up to eight characters),automatically used as the mid-level qualifier for FULL RTEs.

c. In the Type field, enter the type of RTE that your are creating. In this case,you are creating an RTE of the FULL type.

d. In the Description field, type a description for this RTE.3. Press Enter to add the new full RTE. The Add Runtime Environment panel is

displayed as shown in Figure 49.

4. From the Add Runtime Environment panel, type the information required todefine the FULL RTE. The values you enter into the fields are used to allocateruntime libraries and to provide defaults for product configuration panels. Youmust enter a JCL suffix character. This RTE contains a Tivoli EnterpriseMonitoring Server.

5. Press Enter. The second Add Runtime Environment panel is displayed asshown in Figure 50 on page 174.

------------------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------



Action Name Type Sharing DescriptionA BCRTEM23 FULL Bkp Cont NV62 EMA RTEMS HTEMS on TIVLNX21

F1=Help F3=Back (No RTEs defined, use Action A to Add)

Figure 48. Runtime environments panel


RTE: BCRTEM23 Type: FULL Desc: Bkp Cont NV62 EMA RTEMS HTEMS on TIVLNX21

Libraries High-level Qualifier Volser Unit Storclas Mgmtclas PDSENon-VSAM NETVIEW.EMAMVS23 xxxxxx 3390 NVSAM NETVIEW.EMAMVS23 xxxxxxMid-level qualifier ==> BCRTEM23

JCL suffix ==> A Remote RTE for transport ==> N (Y, N)STC prefix ==> CANS Runtime members analysis ==> Y (Y, N)SYSOUT class ==> X Diagnostic SYSOUT class ==> XLoad optimization ==> N (Y, N)

Will this RTE have a Tivoli Enterprise Monitoring Server ==> Y (Y, N)If Y, TEMS name ==> BCRTEM23:CMS (Case sensitive)

Copy configuration values from RTE ==> (Optional)


Figure 49. Add runtime environment panel for FULL scenario


||||||||||||||||||

|||||||||||||||||||||||||

||

|

|

|||

||

|

|||

|||||

|||

6. Review and update the values as needed for your environment.v The configuration tool supports z/OS system symbolic variables for some of

the generated configuration values. You can enable system variable support,which is disabled by default. For more information, use the README SYScommand or see the OMEGAMON XE and Tivoli Management Services on z/OSCommon Planning and Configuration Guide.

v Blank out the VTAM values:– Applid prefix– Logmode table– Network ID– LU6.2 logmode

v Specify the IP address or host name for the remote monitoring server.v Specify the TCP/IP stack name to be used. If your LPAR contains a single

TCP/IP stack, you can specify an asterisk (*). If your LPAR contains multipleTCP/IP stacks, specify the TCP/IP stack to be used by the agent to establisha connection to the monitoring server.The following values are valid:

* Specifies that the first TCP/IP stack that was started is to be used.

# Translated by the configuration tool to a blank; specifies that theTCP/IP environment is to choose the stack to use, either throughTCP/IP definitions or through the use of the SYSTCPD DDstatement.

stack_nameSpecifies that the named TCP/IP stack is to be used. This stack nameis the TCP/IP started task name.

Note: Whichever method is used to select a TCP/IP stack in a multi-stackenvironment, the IBM Tivoli Monitoring platform continues to use that stack.This selected stack is used even if conditions change such that a differentstack becomes the primary stack.

v The port number specifies the base port number of the monitoring server.7. Press Enter. A VTAM warning panel is displayed.


Use z/OS system variables? ==> N (Y, N) Use VTAM model applids? ==> N (Y, N)RTE name specification ==> &SYSNAMERTE base alias specification ==>Applid prefix specification ==> K&SYSCLONE.

Security system ==> NONE (RACF, ACF2, TSS, NAM, None)ACF2 macro library ==>Fold password to upper case ==> Y (Y, N)

VTAM values are required under certain conditions. Press F1=Help:Applid prefix ==> Network ID ==>Logmode table ==> LU6.2 logmode ==>

If you require TCP/IP communications for this RTE, complete these values:Hostname ==> ip_address or host_name

Started task ==> * (Recommended default = *)Port number ==> 1918Enter=Next F1=Help F3=Back

Figure 50. Second runtime environment panel for FULL scenario


|||||||||||||||||||||||||||

|||||

|||||

|

||||

|

||

|||||

|||

||||

|

|

8. Press Enter again. A third Add Runtime Environment panel is displayed.Review and update the values as required for your environment.

9. Press Enter to return to the Runtime Environments panel.

To build the libraries for this runtime environment, follow these steps:1. From the Runtime Environments panel, type B in the Action field and then

press Enter. The JCL to allocate the runtime libraries is displayed.2. Review the JCL and then submit the job.3. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Runtime Environments (RTE) panel.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.

Configuring the remote Tivoli Enterprise Monitoring ServerTo configure the remote Tivoli Enterprise Monitoring Server, follow these steps:1. Start this configuration at the Runtime Environments panel.2. Enter C in the Action field next to the BCRTEM23 RTE to display the Product

Component Selection menu.3. Enter 1 to select the Tivoli Enterprise Monitoring Server component. The

Configure the TEMS Menu panel as shown in Figure 51 is displayed.

Complete the steps on this panel in the order shown, starting with step 2 (Specifyconfiguration values). This monitoring server does not use SNA. The Date andTime fields on this panel are blank when you first access this panel. As youperform the tasks, the Date and Time fields are displayed to help you to track yourprogress.

The steps in this process are explained in the sections that follow.

Specifying configuration parameters: Do these steps to define this remote TivoliEnterprise Monitoring Server.

-------------------- CONFIGURE THE TEMS / RTE: PCRTEM22 -----------------------

Each RTE can contain only one TEMS. To configure Last selectedthe TEMS for this RTE, perform these steps in order: Date Time


1 Create LU6.2 logmode2 Specify configuration values3 Specify communication protocols4 Configure TEMS Self-Describing Agent parameters5 Create runtime members6 Configure persistent datastore7 Complete the configuration

Optional:

8 View TEMS list and registration status9 Generate sample migration JCL

F1=Help F3=Back

Figure 51. Configure the TEMS for the selected RTE panel


||||||||||||||||||||||||||

||

|

|

||

|

|

||

||

||

|

||

|||

|||||

|

||

1. From the Configure the TEMS panel, enter 2. The Specify ConfigurationValues panel as shown in Figure 52 is displayed.

2. If necessary, update the TEMS started task field.3. Specify REMOTE in the Type field.4. To configure the Program to Program Interface Information to forward Take


5. Press Enter. The Communication Selection Panel is displayed.6. Press F5. The Specify Configuration - Hub Values for Remote TEMS is

displayed.7. Press Enter to return to the Specify Configuration Values panel.8. Press F5. The Specify Advanced Configuration Values panel is displayed.9. Accept the default values or make changes required by your enterprise.

For the Reconnect after TCP/IP Recycle field, specify Y. This allows TCP/IP tobe restarted without having to restart the monitoring server.

10. Press Enter to return to the Specify Configuration Values panel.11. Press Enter again to return to the Configure the TEMS panel.

Specifying communication protocols: Use the Specify Communication Protocolspanel to specify the communication protocol for the Tivoli Enterprise MonitoringServer. You can also define the communication protocol priority sequence. Whencommunication with another component is initiated, the product tries the protocolsin the specified order.1. From the Configure the TEMS panel, enter 3. The Specify Communication

Protocols panel is displayed.2. Review the default values for the priority sequence. The IP.PIPE protocol is

chosen because it is connection-oriented and can be used to detect and recoverfrom communication errors more quickly.

3. Press Enter. The panel for the priority 1 protocol (IP.PIPE) is displayed.4. Review the default values on the Specify IP.Pipe Communication Protocol panel

and make any changes necessary for your environment.

------------------------- SPECIFY CONFIGURATION VALUES ------------------------

Started task ==> CANSDSSTType (Hub or Remote) ==> REMOTEHub TEMS type ==> (HA=High Availability)

Security settings:Validate security? ==> N (Y, N)

TMS password encryption information:Integrated Cryptographic Service Facility (ICSF) installed? ==> N (Y, N)

ICSF load library==> CSF.SCSFMOD0TMS encryption key==> IBMTivoliMonitoringEncryptionKey

Program to Program Interface (PPI) information:Forward Take Action commands to NetView for z/OS? ==> N (Y, N)

NetView PPI receiver ==> CNMPCMDRTEMS PPI sender ==>

Enter=Next F1=Help F3=Back F5=Advanced

Figure 52. Specify configuration values panel


||||||||||||||||||||||||||

|||

|

|

|||

|

||

|

|

|

||

|

|

|||||

||

|||

|

||

5. Press Enter to complete the IP.Pipe configuration. A warning panel is displayedbecause you did not specify the SNA protocol.

6. Press Enter to accept the warning and return to the Configure the TEMS panel.

Creating runtime members: Do these steps to create the runtime membersrequired by the remote Tivoli Enterprise Monitoring Server. These members arecreated in the runtime libraries for this runtime environment.1. From the Configure the TEMS panel, enter 4 to create runtime members.2. Review and edit the JCL to make changes required by your enterprise.3. Submit the job.4. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Configure the TEMS panel.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.

Configuring the persistent data store: You are required to configure thepersistent data store. The persistent data store contains generic history for theTivoli Enterprise Monitoring Server. Use the following steps to do theconfiguration:1. From the Configure the TEMS panel, enter 5 to configure the persistent data

store. The Configure Persistent Datastore panel is displayed as shown inFigure 53.

2. To modify and review data store specifications, select 1 and then press Enter.The Persistent Datastore Specifications panel is displayed as shown inFigure 54 on page 178.




* Note: The initial PDS maintenance jobcard defaults to the jobcardset on the Set up work environment option. This jobcard isshared by all products that configured historical collectionwithin this RTE=BCRTEM23. Change to a generic jobcard, asnecessary.

F1=Help F3=Back

Figure 53. Configure Persistent Datastore panel


|||||||||||||||||||||||

||

|

|||

|

|

|

|

||

||

||||

||||

||||

3. Update the values on this panel to control the size, placement, and number ofdata sets that make up the persistent data store.

4. For the values to take effect, press Enter.5. To return to the Configure Persistent Datastore panel, press F3.6. To create or edit parameters used on the persistent data store maintenance job

card, select 2 from the Configure Persistent Datastore panel and press Enter.The job card is used by the following persistent data store maintenance jobs:v KPDPROCC member in the RKANSAM data setv KPDPROC1 member in the RKANSAMU data set

7. Edit the job card and make changes required by your enterprise.8. To return to the Configure Persistent Datastore panel, press Enter.9. From the Configure Persistent Datastore panel, select 3 and press Enter to

create runtime members. This job creates the persistent data store allocationconfiguration members.


v If the job completes successfully, the return code is 0 or 4 (COPYUSRJ orCOPYUSRP step). Press F3 to return to the Configure Persistent Datastorepanel.

v If the return code is not 0 or 4, check the job log to diagnose errors andthen run the job again.

13. On the Allocate Persistent Datastore panel, select 4 and press Enter to reviewthe job that allocates the persistent data store.


v If the job completes successfully, the return code is 0. Press F3 to return tothe Configure Persistent Datastore panel.

v If the return code is not 0, check the job log to diagnose errors and then runthe job again.

17. Press F3 twice to return to the Product Component Selection Menu panel.


Configuring the NetView agent (backup controller)To configure the NetView agent, follow these steps:



Datastore high-level qualifier: NETVIEW.EMAMVS23.BCRTEM23

Group -Datasets in Group- Volser/ Storclas/ -Est Cyl- -Maintenance-Name Lowlev Count Unit Mgmtclas Space Backup Export Extract-------------------------------------------------------------------------------GENHIST RGENHIS 3 xxxxxx ________ 36__ N N N

3390____ ________F1=Help F3=Back



||||||||||||||||||||

|

|

|||||

|

|

|||

|

|

|

|||

||

||

|

|

|

||

||

|

||

||

1. From the Product Component Selection Menu panel, enter 2 to select theNetView for z/OS Agent. The Configure NetView for z/OS Agent V6.2.0 panelis displayed as shown in Figure 55.

Complete the steps on this panel in the order shown, beginning with step 1.The Date and Time fields on this panel are blank when you first access thispanel. As you perform the tasks, these fields are completed to help you to trackyour progress.The steps in this process are explained in the sections that follow.

Registering with the local Tivoli Enterprise Monitoring Server: Do the followingsteps to register the NetView agent with the local Tivoli Enterprise MonitoringServer.1. Select 1 and press Enter.2. Review and edit the JCL, and then submit the job.3. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Configure NetView for z/OS Agent panel.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.

Specifying configuration parameters: Follow these steps to specify configurationvalues required by the NetView agent.1. From the Configure NetView for z/OS Agent V6.2.0 panel, enter 2. The Specify

Configuration Parameters panel is displayed as shown in Figure 56 on page180.

----- CONFIGURE NetView for z/OS Agent V6.2.0 / RTE: BCRTEM23 --–-----–-----–--Last selected

Perform the appropriate configuration steps in order: Date Time


If you have defined a TEMS in this RTE that this Agentwill communicate with, select option 1.

1 Register with local TEMS

2 Specify configuration parameters

3 Specify Agent address space parameters

4 Create runtime members

5 Configure persistent datastore (in Agent)

6 Complete the configuration

F1=Help F3=Back F5=Advanced

Figure 55. Configure NetView for z/OS V6.2.0 panel


||||||||||||||||||||||||||

||||

||||

|

|||

|

|

|

||

||

||

||||

2. Verify the following information on the panel and change it as needed for yourenvironment:v The NetView Enterprise Management Agent PPI receiver is required for

communication with the NetView address space. The default isCNMEMARX. If you change this value, also change the NACMD.DESTPPIstatement in the CNMSTUSR or CxxSTGEN member to match this value. Forinformation about changing CNMSTYLE statements, see IBM Tivoli NetViewfor z/OS Installation: Getting Started. For information about accepted values ofthe PPI receiver name, see the RECEIVER-ID section in the IBM TivoliNetView for z/OS Application Programmer's Guide.

v The NetView agent uses the NetView CNMLINK link library. The defaultlibrary is NETVIEW.V6R2M0.CNMLINK. The link library is listed in the NetViewCNMPROC (CNMSJ009) procedure.


Specifying agent address space parameters: Do the following steps to specify theagent address space parameters.1. From the Configure NetView for z/OS Agent V6.2.0 panel, select 3 and press

Enter. The Specify Agent Address Space Parameters panel is displayed asshown in Figure 57 on page 181.

--------------- SPECIFY CONFIGURATION PARAMETERS / RTE: BCRTEM23 --------------

Specify the following information:

NetView Enterprise Management Agent PPI Receiver (CNMEMARX):==> CNMEMARX

NetView Enterprise Management Agent PPI Sender (CNMEMATX):==> CNMEMATX

Specify the following library:

NetView linklib (NETVIEW.V6R2M0.CNMLINK):==> NETVIEW.V6R2M0.CNMLINK

F1=Help F3=Back

Figure 56. Specify configuration parameters panel


|||||||||||||||||||||||

||||||||

|||

|

||

||||

2. Review the default values and make any changes required by your enterprise.The communication protocols that you specify must match the protocols thatwere specified when the Tivoli Enterprise Monitoring Server was configured.Specify only the IP.PIPE connection as shown in Figure 57. IP.PIPE isconnection-oriented and can be used to detect and recover fromcommunication errors more quickly.

3. Press F5. The Specify Advanced Agent Configuration Values panel isdisplayed as shown in Figure 58.

4. Specify Y to enable the secondary monitoring server.5. Specify Y to reconnect after a TCP/IP recycle.6. To configure the Program to Program Interface Information to forward Take


7. Review the remaining values and make any changes necessary for yourenvironment.

-------------------- SPECIFY AGENT ADDRESS SPACE PARAMETERS -------------------

The following information is needed to define the Agent address space.Agent started task ==> CANSNAConnect to TEMS in this RTE ==> Y (Y, N)

Name of Primary TEMS ==> BCRTEM23:CMS

Specify the communication protocols in priority sequence.IP.PIPE ==> 1 (Non-secure NCS RPC)IP.UDP ==> (Non-secure NCS RPC)SNA.PIPE ==> (Non-secure NCS RPC)IP6.PIPE ==> (IP.PIPE for IPV6)IP6.UDP ==> (IP.UDP for IPV6)IP.SPIPE ==> (Secure IP.PIPE)IP6.SPIPE ==> (Secure IP.PIPE for IPV6)

Note: Enable only protocol(s) in use by the Primary TEMS.


Figure 57. Specify agent address space parameters panel

----------------- SPECIFY ADVANCED AGENT CONFIGURATION VALUES -----------------

Specify the advanced configuration options for this Agent.

Enable secondary TEMS ==> Y (Y, N)Name of secondary TEMS ==> None

Enable startup console messages ==> N (Y, N)Enable WTO messages ==> N (Y, N)Reconnect after TCP/IP recycle ==> Y (Y, N)Intervals (hh:mm):


Virtual IP Address (VIPA) type ==> N (S=Static, D=Dynamic, N=None)Minimum extended storage ==> 256000 KLanguage locale ==> 1 (Press F1=Help for a list of codes)Program to Program Interface (PPI) information:

Forward Take Action commands to NetView for z/OS? ==> N (Y, N)NetView PPI receiver ==> CNMPCMDRAgent PPI sender ==>


Figure 58. Specify Advanced Agent Configuration Values panel


||||||||||||||||||||||||

||||||||||||||||||||||||||

|||

|||

|||

|

|

|||

||

8. Press Enter to display the Communications Selection panel as shown inFigure 59.

9. Press PF5 (Advanced) to display the Specify Agent Secondary TEMS Valuespanel as shown in Figure 60.

10. Review the Backup TEMS Name and Network Address fields and press Enter.11. Press PF5 (Advanced) again. The Specify Nonstandard Parameters panel is


----------------- COMMUNICATION SELECTION PANEL FOR BCRTEM23 Row 1 to 1 of 1COMMAND ===>

Select the secondary TEMS to connect to this agent.

The TEMS table below lists eligible TEMS that you have configured inthis NETVIEW.EMAMVS23.INSTLIB.Enter S next to the TEMS that you wish to connect to this agent.Important: To manually enter the *TEMS information, press F5=Advanced.



-----------------------------------------------------------------------------_ REMOTE BCRTEM23 Bkp Cont NV62 EMA RTEMS HTEMS on TIVLNX21F1=Help F3=Back F5=Advanced F7=Up F8=Down

Figure 59. Communications Selection panel

-------------------- SPECIFY AGENT SECONDARY TEMS VALUES ----------------------COMMAND ===>

Backup TEMS name ==> PCRTEM22:CMS (case sensitive)

Complete this section if the Agent is connecting to its secondary TEMSusing the SNA and/or IP protocol(s):

SNA protocol (Enter applicable VTAM values of its secondary TEMS):LU6.2 logmode ==>Local location broker applid ==>Network ID ==>

IP protocol (Enter applicable network address values):* Network address (Hostname of Secondary TEMS):

==> PCHOST



Figure 60. Specify Agent Secondary TEMS Values


||||||||||||||||||||||

|||||||||||||||||||||||||||

|||

|||

|

|||

Enter the following values:v KNA_ACTACT (parameter)v =YES (value for the first parameter)v CTIRA_PRIMARY_FALLBACK_INTERVAL (parameter)v =150 (value for the second parameter)v RKANPARU (low-level data set qualifier)v KNAENV (member name)

12. Press enter until you return to the Specify Agent Address Space Parameterspanel.

13. From the Specify Agent Address Space Parameters panel, press Enter. TheSpecify Agent IP.PIPE Configuration Values panel is displayed as shown inFigure 62.

14. Review the default values on the Specify Agent IP.PIPE Configuration Valuespanel and make any changes necessary for your environment.


Creating runtime members: Do the following steps to create runtime membersfor the NetView agent.

---------------- SPECIFY NONSTANDARD PARAMETERS / RTE: BCRTEM23 --------------OPTION ===>

This panel is used to add nonstandard parameters to runtime members.

Warning: This should be used under the guidance of IBM Software Support.

Parameter: KNA_ACTACT_____________________________New Value: =YES_____________________________________________Old Value (if replacing): ___________________________________________________Low-level dataset qualifier: RKANPARU Member: KNAENV__

Parameter: CTIRA_PRIMARY_FALLBACK_INTERVAL________New Value: =150_____________________________________________Old Value (if replacing): ___________________________________________________Low-level dataset qualifier: RKANPARU Member: KNAENV__

Parameter: _______________________________________New Value: _________________________________________________Old Value (if replacing): ___________________________________________________Low-level dataset qualifier: ________ Member: ________

Figure 61. Specify Nonstandard Parameters panel

------------------ SPECIFY AGENT IP.PIPE CONFIGURATION VALUES -----------------

Specify the IP.PIPE communication values for this Agent. These networkaddress-related values are for the z/OS system where the Agent runs on.


Started task ==> * (Recommended default = *)Network interface list:

==>

Specify additional configuration values.




Figure 62. Specify agent IP.PIPE configuration values panel


||||||||||||||>>>>>>>>>>

||||||||||||||||||||||

||||>||

||

||||

||

|

||

1. From the Configure NetView for z/OS Agent V6.2.0 panel, select 4 and pressEnter.

2. Review the JCL and make any changes necessary for your environment, thensubmit the job.

3. Verify that the job completes and check the return code.v If the job completes successfully, the return code is 0.v If the return code is not 0, check the job log to diagnose errors and then run

the job again.4. Press F3 to return to the Configure NetView for z/OS Agent V6.2.0 panel.

Configuring persistent data store in the agent: Persistent data stores areassociated with each Tivoli Enterprise Monitoring Server and each agent. Thepersistent data store in this section is for the NetView agent.

The following procedure generates JCL that configures a persistent data store thatis added to the agent address space for historical data collection. You start thecollection of short-term history at the Tivoli Enterprise Portal using the HistoryCollection Configuration dialog. If the person who configures the collection at theTivoli Enterprise Portal chooses TEMS for Collection Location, these agent data setsare not used. You might run out of storage for short-term history, depending onpersistent data store collection at the Tivoli Enterprise Monitoring Server. If youperform this procedure, configure historical collection to Collect at Agent.

Do these steps to configure a persistent data store for the NetView agent.1. From the Configure NetView for z/OS Agent V6.2.0 panel, select 5 and press

Enter. The Specify Persistent Datastore Values panel is displayed as shown inFigure 63.

2. Specify the values for allocating the persistent data store and then press Enter.The Configure Persistent Datastore panel is displayed as shown in Figure 64on page 185.

--------------------- SPECIFY PERSISTENT DATASTORE VALUES ---------------------

The following values are used to allocate and maintain PersistentDatastore for standalone Agents. For efficiency, use the samemaintenance procedure prefix for all your runtime environments (RTEs).

Datastore high-level prefix: NETVIEW.EMAMVS23.BCRTEM23

Maintenance procedure prefix ==> KPDPROCAllocation volume ==> xxxxxxAllocation unit ==> 3390Allocation STORCLAS ==>Allocation MGMTCLAS ==>


Figure 63. Specify persistent data store values panel


||||||||||||||||||||

||

||

|

|

||

|

|||

||||||||

|

||||

||||

3. To modify and review the data store specification, enter 1. The PersistentDatastore Specifications panel is displayed as shown in Figure 65.

4. Review the values on this panel, change them as necessary, and then pressEnter.

5. Press F3 to return to the Configure Persistent Datastore panel.6. From the Configure Persistent Datastore panel, select 2, and press Enter to

create or edit parameters used on the persistent data store maintenance jobcard. The job card is used by the following persistent data store maintenancejobs:v KPDPROCC member in the RKANSAM data setv KPDPROC1 member in the RKANSAMU data set

7. Edit the job statement and make changes that are necessary for yourenvironment.

8. Press Enter to return to the Configure Persistent Datastore panel.9. From the Configure Persistent Datastore panel, select 3 and press Enter.

Information about a simplified PDS maintenance procedure is displayed.10. Press Enter to review the job that creates the runtime members.11. Review and update the JCL as needed for your environment, and submit the

job.12. Verify that the job completes and check the return code.

v If the job completes successfully, the return code is 0 or 4 (COPYUSRJ step).Press F3 to return to the Configure Persistent Datastore panel.




* Note: The initial PDS maintenance jobcard defaults to the jobcardset on the Set up work environment option. This jobcard isshared by all products that configured historical collectionwithin this RTE=BCRTEM23. Change to a generic jobcard, asnecessary.

F1=Help F3=Back

Figure 64. Configure persistent data store for the monitoring agent



Datastore high-level qualifier: NETVIEW.EMAMVS23.BCRTEM23

Group -Datasets in Group- Volser/ Storclas/ -Est Cyl- -Maintenance-Name Lowlev Count Unit Mgmtclas Space Backup Export Extract-------------------------------------------------------------------------------KNA RKNAHIS 3 xxxxxx ________ 140_ N N N

3390____ ________F1=Help F3=Back



||||||||||||||||||||||

||||||||||||||||||

|||

||

|

||||||

||

|

||

|

||

|

||

v If the return code is not 0 or 4, check the job log to diagnose errors and runthe job again.

13. On the Configure Persistent Datastore panel, select 4 and press Enter toreview the job that allocates the persistent data store.

14. Review and update the JCL as needed for your environment, and submit thejob.

15. Verify that the job completes and then check the return code.v If the job completes successfully, the return code is 0. Press F3 to return to

the Configure Persistent Datastore panel.v If the return code is not 0, check the job log to diagnose errors and run the

job again.16. Press F3 multiple times until you return to the Runtime Environments panel.


Loading the runtime librariesFollow these steps to load the runtime libraries for the monitoring server:1. From the Runtime Environments panel, enter L in the Action field next to the

BCRTEM23 FULL RTE.2. Review the JCL and make any changes necessary for your environment, and

then submit the jobs.3. Verify that the jobs complete and check the return codes.v If both jobs complete successfully with return code is 0. Exit the

configuration tool.v If either job ends with a return code other than 0, check the job log to

diagnose errors and then run the job again.

Completing the configuration on the backup controllerTo complete the configuration:v APF-authorize your librariesv Authorize the KPDDSCO progamv Copy the started task procedures to your procedure library

The configuration tool is not used to perform these steps.

APF-authorizing your libraries

Some of the libraries created by the configuration tool must be APF-authorized.Ensure that the following libraries are added to the list of APF-authorized libraries:v RKANMOD for the BCRTEM23 RTEv RKANMODL for the BCRTEM23 RTEv RKANMODU for the BCRTEM23 RTEv Any other runtime libraries that are concatenated in the STEPLIB DDNAME and

in the RKANMODL DDNAME of the CANSNA and CANSDSST started tasks

For information about APF-authorizing these data sets, see IBM Tivoli NetView forz/OS Installation: Getting Started.

Authorizing the KPDDSCO program

Persistent data store maintenance uses the KPDDSCO program. This program mustrun as an authorized program under TSO.


||

||

||

|

||

||

|

||

||

||

||

|

||

||

||

|

|

|

|

|

||

|

|

|

||

||

|

||

To authorize the KPDDSCO program, update the IKJTSOxx member in theSYS1.PARMLIB data set. For information about authorizing this program, see IBMTivoli NetView for z/OS Installation: Getting Started.

You can refresh the IKJTSOnn member by issuing the following SET command:T IKJTSO=nn

Copying the started task procedures to your procedure library

You used the configuration tool to create started task procedures in theRKANSAMU data set. To complete the configuration, do these steps:1. Copy the Tivoli Enterprise Monitoring Server started task (CANSDSST) from

the RKANSAMU data set to your PROCLIB data set.2. Copy the started task (CANSNA) from the RKANSAMU data set to your

PROCLIB data set.3. The started task procedures include a SYSTCPD DD statement that is

commented out. Tivoli Management Services requires that host names beresolvable by TCP/IP. If your environment does not include a domain nameservice, uncomment this DD statement and modify it to comply with yourenvironment.

4. Copy the persistent data store maintenance procedure (KPDPROC1) from theRKANSAMU data sets to your PROCLIB data set.

You can now start the monitoring server and the NetView agent, for example:s cansdssts cansna

Loading agent data files and configuring the portal server in aWindows environment

The NetView agent data files are found on the IBM Tivoli NetView for z/OSEnterprise Management Agent data files CD. Do these steps to install the files.1. Log on to Windows using an ID with administrator authority.2. Close any running applications.3. Insert the Tivoli NetView for z/OS Enterprise Management Agent DVD into

your DVD drive.v Installation begins automatically.v If the installation process does not start, run setup.exe from the Windows

directory of the installation CD. If setup.exe initialization fails, you mightnot have enough free disk space to extract the setup files.

4. From the Tivoli NetView for z/OS Enterprise Management Agent installationWelcome window, click Next. The Install Prerequisites window is displayed.

5. From the Install Prerequisites window, click Next. The Software LicenseAgreement is displayed.

6. Read and accept the software license agreement. Click Accept to display theSelect Features window.

7. Under Tivoli Enterprise Monitoring Services, select Tivoli Enterprise PortalServer and TEP Desktop Client.

8. Click Next. The Start Copying Files window is displayed.9. Click Next. When the files have been copied, the Setup Type window is

displayed.


|||

|

|

|

||

||

||

|||||

||

|

||

|

||

10. Ensure that Install Application Support Files for a Local/Remove TivoliEnterprise Monitoring Server, Configure Tivoli Enterprise Portal andLaunch Manage Tivoli Enterprise Monitoring Services are selected, and thenclick Next.

11. In the remaining windows in the installation wizard, you are prompted toprovide information specific to your environment.

12. When the installation wizard is finished, the InstallShield Wizard Completewindow is displayed. Make sure that the Display the Readme file checkboxis selected. Click Finish to exit the wizard.

13. Review the readme file and then close the window.14. When the installation process completes, the Manage Tivoli Enterprise

Monitoring Services window is displayed.If the Manage Tivoli Enterprise Monitoring Services window is not displayed,you can open it by clicking Start > Programs > IBM Tivoli Monitoring>Manage Tivoli Monitoring Services.

15. If your hub Tivoli Enterprise Monitoring Server does not have theself-describing agent function enabled, you must manually add the applicationsupport to the hub monitoring server:a. Right-click Tivoli Enterprise Monitoring Server, select Advanced, then

select Add TEMS application support.b. In the Add Application Support to the TEMS dialog, select On a different

computer, then click OK.c. Click OK on the reminder window to ensure that the monitoring server is

configured and running.d. In the Non-Resident TEMS Connection dialog, enter the monitoring server

name in the TEMS Name field. Ensure that the IP.PIPE protocol and HubTEMS type are selected, then click OK.

e. In the next Non-Resident TEMS Connection dialog, enter the host name oraddress of the hub monitoring server, then click OK.

f. In the Select the Application Support to Add to the TEMS panel, select allinstances of the component. Ensure that the New Distribution List setting isselected, then click OK.

g. Review the results in the Application Support Addition Complete dialog toensure that the application support was successfully added to the hubmonitoring server.

h. Recycle the hub monitoring server.


16. Review the portal server Status field. If the server is not already started,right-click Tivoli Enterprise Portal Server and then click Start.

17. To log on to Tivoli Enterprise Portal, right-click Tivoli Enterprise PortalBrowser and then click Start. The default user ID is sysadmin.


Loading agent data files and configuring the portal server inthe Linux and AIX environments

To complete this process, the components on which you are to install support mustbe in the same directory structure as defined by the $install_dir environmentvariable or the value of the -h flag when using the install.sh installation script.


||||

|||

||

||

|

Do these steps to install the agent data files:1. Stop the portal server by entering the following command from the

$install_dir/bin directory:./itmcmd agent stop cq

2. Run the following command from the installation media:./install.sh -h $install_dir

$install_dir is the home directory for the IBM Tivoli Monitoring products.3. When you are prompted for the IBM Tivoli Monitoring home directory, do

one of the following steps:v Press Enter to accept the default directory (/opt/IBM/ITM).v Enter the full path to the installation directory that you used.

4. When you are prompted for an installation option, enter 1 as shown inFigure 10 on page 48.

5. Review the license agreement and enter 1 to accept the terms of theagreement.

6. A list of currently installed products is displayed followed by a numbered listof categories for which product packages are available. Enter the number thatcorresponds to the Tivoli Enterprise Portal Browser Client support.

7. At the prompt, enter y to confirm the request.8. When the next list of the components to install is displayed, enter the number

that corresponds to the NetView for z/OS Enterprise Management Agent.9. At the prompt, enter y to confirm the installation. The installation begins.

10. Install the agent data files for each IBM Tivoli Monitoring component that ison the server. For example, you might want to load support for the TivoliEnterprise Portal server and client.a. Select the number corresponding to the component for which you want

support.b. At the prompt, enter 1 for Yes to confirm the request.c. Select the number corresponding to NetView for z/OS Enterprise

Management Agent.d. At the prompt, enter 1 for Yes to confirm the request.e. If you have additional components, enter 1 for Yes and repeat these steps

for the next component.11. After all of the components are installed, you are prompted whether you want

to install additional products or product support packages. Enter n.12. To configure the portal server with the new agent information, enter the

following command from the $install_dir/bin directory:./itmcmd config -A cq

Select one of the following:

1) Install products to the local host.2) Install products to depot for remote deployment (requires TEMS).3) Install TEMS support for remote seeding4) Exit install.

Please enter a valid number: 1

Figure 66. Installation option


|||

||

13. Complete the configuration as prompted. For information about configuringthe Tivoli Enterprise Portal Server, see the IBM Tivoli Monitoring: Installationand Setup Guide.

14. If your hub monitoring server resides on a different server, and does not havethe self-describing agent function enabled, you must manually add theapplication support to the hub monitoring server:a. Start the Manage Tivoli Enterprise Monitoring Services application by

entering the following command from the $install_dir/bin directory:./itmcmd manage

Usage Note: The Manage Tivoli Enterprise Monitoring Services applicationrequires an X server.

b. On the Manage Tivoli Enterprise Monitoring Services window, selectActions, and then select Install Product Support.

c. In the Add TEMS Application Support dialog, select On a differentcomputer, then click OK.

d. Click OK on the reminder window to ensure that the monitoring server isconfigured and running.

e. In the Non-Resident TEMS Connection dialog, enter the monitoring servername in the TEMS Name field. Ensure that the IP.PIPE protocol and HubTEMS type are selected, then click OK.

f. In the next Non-Resident TEMS Connection dialog, enter the host name orIP address of the hub monitoring server, then click OK.

g. In the Install Product Support dialog, select all instances of the component.Make sure that the NONE option is selected, then click INSTALL.

h. Review the results in the Messages section of the Manage Tivoli EnterpriseMonitoring Services window to ensure that the application support wassuccessfully added to the hub monitoring server.

i. Recycle the hub monitoring server.


15. Start the portal server from your UNIX or Linux command window.16. To log on to Tivoli Enterprise Portal, follow these steps:

a. On Windows computer, open a browser window.b. Enter the following web address:

http://hostname:1920

where hostname is the host name or IP address of the portal server todisplay the service index.

c. Click on the IBM Tivoli Enterprise Portal Web Client entry to display thelogon window.

d. Enter your user ID and password.The default user ID is sysadmin.


Historical data collection and reportingSome of the workspaces for the GDPS Active/Active Continuous Availabilitysolution support historical data collection. For information about configuring


||

|

|

|

|

historical data collection, see IBM Tivoli NetView for z/OS Installation: Configuring theNetView Enterprise Management Agent and the IBM Tivoli Monitoring: Tivoli EnterprisePortal User's Guide.

The NetView agent provides predefined historical reports at the Tivoli EnterprisePortal. For information on predefined historical reports for the solution that areavailable from the portal, see IBM Tivoli NetView for z/OS Installation: Configuringthe NetView Enterprise Management Agent.

Creating a custom navigator viewThe Tivoli Enterprise Portal displays physical and custom navigator views. TheNavigator physical view (default view) shows the enterprise as a physical mappingof platforms, systems, agents, and monitored resources. A custom navigator viewcan be created to show a logical hierarchy. For example, a custom navigator viewcan represent the enterprise, sites, workloads, and other managed resources.

To create a custom navigator view that displays the GDPS Active/ActiveContinuous Availability solution workspaces, follow these steps:1. Log on to the Tivoli Enterprise Portal client with a user ID that has Modify

permission for the Custom Navigator Views feature.

2. In the Navigator toolbar, click the Edit Navigator View icon ( ). The EditView window is displayed as shown in Figure 11 on page 50.

Notice in the right panel that the Navigator physical view is the source view.The custom navigator view or the most recently opened navigator view is thetarget view in the left panel.

3. To edit the target view, click the Create New Navigator View icon ( ). TheCreate New Navigator View window is displayed as shown in Figure 12 onpage 51.

Figure 67. Edit View window


4. Enter the Navigator View Identity (for example, My Active/Active Sites) andoptionally the description, and click OK. The Navigator view name isdisplayed as Enterprise in Figure 13 on page 51.

If you receive a duplicate names message that the name exists, enter adifferent name. Because Navigator views are assigned to user IDs, you mightnot be able to see Navigator views that other users created.

5. To assign managed systems to a Navigator item, right-click the MyActive/Active Sites item, and click Properties. The Navigator Item Propertieswindow is displayed as shown in Figure 14 on page 52.

Figure 68. Create New Navigator View window

Figure 69. Edit Navigator View window with new view name


|

|||

||

6. To assign managed system groups to the Navigator item as dynamic members(child items), click the Dynamic items tab. When managed systems are addedor removed from the managed system groups, the Navigator item and theitems that it contains are updated automatically. Notice in Figure 14 on page52 that Available Members displays the managed system groups that can beassigned as dynamic members of the Navigator item.

7. To add a managed system group for the GDPS Active/Active ContinuousAvailability solution, select *ZNETVIEW_ACTIVEACTIVE in the Available

Members list and click the Left Arrow icon ( ). The updates are shownin Figure 15 on page 53.

Figure 70. Navigator Item Properties window


|

|||

8. Click the Options icon ( ) to display the Assigned member options window.9. Customize the view by assigning member options to filter out branch-level or

host-level items from the view. To assign member options, check Includeattribute-level items of managed systems as shown in Figure 16 on page 53.

10. Click OK to exit the Assigned member options window.11. Click OK to exit the Navigator Item Properties window.12. Click Close to exit the Edit Navigator View window.

13. Click the Navigator update pending icon ( ) in the Navigator toolbar torefresh the Navigator view.

14. Click the My Active/Active Sites view from the list of available Navigatorviews as shown in Figure 17 on page 54.

Figure 71. Navigator Item Properties window (assigned members)

Figure 72. Assigned member options


|||

The customized navigator view is displayed as shown in Figure 18 on page54.

Figure 73. List of available Navigator views

Figure 74. Customized Navigator view for My Active/Active Sites


|

|||

|

|||

|||


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Web


sites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Programming InterfacesThis publication primarily documents information that is NOT intended to be usedas Programming Interfaces of Tivoli NetView for z/OS. This publication alsodocuments intended Programming Interfaces that allow the customer to writeprograms to obtain the services of Tivoli NetView for z/OS. This information isidentified where it occurs, either by an introductory statement to a chapter orsection or by the following marking:Programming Interface informationEnd of Programming Interface information

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at http://www.ibm.com/legal/copytrade.shtml .

Adobe and Acrobat and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.


http://www.ibm.com/legal/copytrade.shtml

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other product and service names might be trademarks of IBM or other companies.

Privacy policy considerationsIBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, See IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details thesection entitled “Cookies, Web Beacons and Other Technologies” and the “IBMSoftware Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.

Notices 199

http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy


Index

Special characters-h option 47, 188$install_dir 47, 188$install_dir environment variable 47, 188

Numerics4700 support facility

enabling 96

Aaccessibility xiiiACTACT.BKTEMS.Enable statement 67ACTACT.BKTEMS.procStr statement 68ACTACT.DB2INT statement 17, 69ACTACT.DB2PATH statement 17ACTACT.DB2PATH.APPx statement 70ACTACT.DB2PATH.CAPx statement 70ACTACT.IMSINT statement 17, 71ACTACT.IMSPATH statement 18ACTACT.IMSPATH.APPx statement 72ACTACT.IMSPATH.CAPx statement 72ACTACT.LIFEINT statement 73ACTACT.MASTER.DELAY 15ACTACT.MASTER.DELAY statement 13, 74ACTACT.PriCont.System statement 68ACTACT.VSAMINT statement 18, 75ACTACT.VSAMPATH statement 18ACTACT.VSAMPATH.APPx statement 75ACTACT.VSAMPATH.CAPx statement 76Active/Active enterprise master NetView 12Active/Active Sites solution

controllers 80enabling 94location of NetView program 79master program 84

ACTVCTL command 55alerts

AA_replication_heartbeat 61CNMSTLIF 11

alias keyword, RMTALIAS statement 90AON

enabling 95IDS support 95SNA feature 95SNA X.25 support 95TCP/IP feature 95

AON/SNA feature 95APF-authorizing your libraries 171Application Management Instrumentation

enabling 95AQN001I 113AQN002I 113AQN003I 114AQN004E 114AQN006I 114AQN007I 114AQN008I 115AQN009I 115

AQN010I 115AQN011I 115AQN012I 116AQN013I 116AQN014E 116AQN015E 116AQN016A 116AQN017I 117AQN018I 117AQN019E 117AQN020I 118AQN021I 118AQN022I 118AQN023I 118AQN024I 119AQN025I 119AQN026I 120AQN027I 121AQN028I 122AQN029I 122AQN030I 122AQN031I 124AQN032I 125AQN033I 126AQN034I 127AQN035I 129AQN036I 130AQN037I 130AQN038I 130AQN039I 131AQN040I 131AQN041I 131AQN042I 132AQN043I 132AQN044I 132AQN045I 133AQN046I 134AQN047I 134AQN048I 135AQN049I 135AQN050I 136AQN051I 137AQN052 138AQNCAT 8AQNCAT member 21AQNCMD 8AQNOPF 8AQNOPF member 20AQNSACTA 8AQNSACTA member 4AQNSAF 8AQNSAF member 20AQNSAF sample 21AQS.NETMGMT.DISPLAY 11authorization, password 19AUTOACTA autotask 20AUTOACTn autotask 20AUTOADAT autotask 20AUTOAEVT autotask 20automating

EIF events 59


automationGDPS Active/Active Continuous Availability solution 8

automation table 4autotask statement 85AUTOTASK statement 77autotasks 20, 77

Bbackup controller 172backup controller, moving 63BNH803I 139BNH804I 139BNH805I 140BNH881I 143BNH900I 143BNH901I 144BNH902I 144BNH903I 144BNH904I 144BNH905I 144BNH906I 144BNH907I 145BNH908I 145BNH909I 145BNH910I 145BNH911I 146books

see publications ix

CCanzlog

message suppression 16class definition statements 19CMDDEF statements

GDPS Active/Active Continuous Availability solution 8CNMSAF2 sample 21CNMSCAT2 member 21CNMSTACT 8CNMSTLIF 8CNMSTLIF member 9CNMSTREP 8CNMSTREP member 17CNMSTYLE member 8CNMSTYLE sample

ACTACT.BKTEMS.procStr statement 68ACTACT.DB2INT statement 69ACTACT.DB2PATH.APPx statement 70ACTACT.DB2PATH.CAPx statement 70ACTACT.IMSINT statement 71ACTACT.IMSPATH.APPx statement 72ACTACT.IMSPATH.CAPx statement 72ACTACT.LIFEINT statement 73ACTACT.MASTER.DELAY statement 74ACTACT.PriCont.System statement 68ACTACT.VSAMINT statement 75ACTACT.VSAMPATH.APPx statement 75ACTACT.VSAMPATH.CAPx statement 76AUTOTASK statement 77EMAAUTO statement 78ENT.ACTIVEACTIVE.ROLE statement 79ENT.ALT.CONTROLLER statement 80ENT.CONNCHECK.INT statement 81ENT.SYN statement 81ENT.SYSTEMS.name statement 82

CNMSTYLE sample (continued)ENT.TYPE statement 84function.autotask statement 85NACMD.ROWSxxx statement 86RMTALIAS statement 89RMTINIT.IP statement 91RMTSYN statement 92TOWER statement 94XCF.RANK statement 98

collecting data 55command authorization 20

GDPS Active/Active Continuous Availability solution 8command authorization table 21commands

itmcmd 48, 189configuration

APF-authorizing your libraries 171completing outside the configuration tool 171, 186

APF-authorizing your libraries 171copying the started task procedures to you procedure

library 172configuring a hub Tivoli Enterprise Monitoring

Server 157, 175configuring the persistent data store for the monitoring

agent 169, 184configuring the persistent data store for Tivoli Enterprise

Monitoring Server 162copying the started task procedures to your procedure

library 172creating runtime members for the monitoring agent 168,

183creating runtime members for Tivoli Enterprise Monitoring

Server 162preparing your work environment 151specifying agent address space parameters 165, 180specifying communication protocols for the monitoring

agent 168, 180specifying communication protocols for Tivoli Enterprise

Monitoring Server 160, 176specifying configuration values for Tivoli Enterprise

Monitoring Server 158, 175specifying self-describing agent parameters 161

configuration tool 149accessing the runtime environments panel 154, 172display requirements 150help 150overview 150panels

allocate persistent data store panel 162configure NetView for z/OS 164, 178configure persistent data store 169, 184configure the TEMS for the selected runtime

environment 158persistent data store specifications 162, 170, 185product selection menu 154runtime environments 155specify agent address space parameters 165, 180specify communication protocols 161specify configuration parameters 164, 179specify configuration values 158specify persistent data store values for the monitoring

agent 169, 184PF keys 150scenario 154setting up and using 150starting 150usage notes 150


configuringIBM Tivoli Monitoring environment 23NetView program 7

controller systems 63conventions

typeface xivcopying the started task procedures to you procedure

library 172custom navigator view 50, 191customized navigator view 50, 191

Ddata

monitoring 57sampling interval 56starting collection 55statistics 55stopping collection 57

data collection 55Lifeline Advisor component 10replication component 17stopping 19

data collection statistics 55DB2 data 95delay interval 15directory names, notation xvdisaster recovery 1DISCOVERY

INTERFACES subtower 95HIPERSOCKETS subtower 95, 97OSA subtower 95, 97

TELNET subtower 95DISCOVERY support 95domain keyword, RMTSYN statement 92domains

changing addresses 81DSI031I 146DSIOPF member 20DVIPA

DVCONN subtower 95DVROUT subtower 95DVTAD subtower 96

DVIPA support 95

Eeducation

see Tivoli technical training xiiiEIF events 59EMAAUTO statement 16, 78EMAAUTOM autotask 16ENT.ACTIVEACTIVE.ROLE statement 13, 79ENT.ALT.CONTROLLER statement 13, 80ENT.CONNCHECK statement 14ENT.CONNCHECK.INT statement 81ENT.SYN statement 14, 81ENT.SYSTEMS

targets 15ENT.SYSTEMS statement 14ENT.SYSTEMS.name statement 82ENT.TYPE statement 14, 84enterprise

sysplex entry point 82enterprise master 12

moving 63

enterprise master NetView programActive/Active 12type 12

environment variables$install_dir 47, 188

environment variables, notation xvevents

hardware monitor 60processing 59

Ffilters 61function.autotask statement 85function.autotask.ACTDATA statement 17function.autotask.ACTDATA=AUTOADAT statement 14function.autotask.ACTTSK4 statement 18

GGDPS Active/Active Continuous Availability solution

ACTACT.BKTEMS.procStr statement 68ACTACT.PriCont.System statement 68AQNCAT sample 8AQNCMD sample 8AQNOPF sample 8AQNSACTA sample 8AQNSAF sample 8automation 8CNMSTACT sample 8CNMSTLIF sample 8CNMSTREP sample 8command authorization 8command definitions 8ENT.CONNCHECK.INT statement 81ENT.SYN statement 81operator definitions 8RACF definitions 8

graphicsenabling 96

Hhardware monitor

alerts 60enabling 96filters 61

historical data collection 50, 190hub monitoring server

installing support on 47, 188Linux on System z 154

IIMS data 95IMS replication 1, 3information, monitoring 3INIT.EMAAUTO statement 16, 86installation

Tivoli Management Services components 149installing

NetView agent 154NetView program 7

Intrusion Detection Services 95

Index 203

IP addressesprimary and secondary 15

IP management 96IP_host keyword, RMTSYN statement 92IPMGT

ACTMON subtower 96IDS subtower 96

IPV4 keyword, RMTSYN statement 92IPV6 keyword, RMTSYN statement 92itmcmd command 48, 189

Kkeywords

alias, RMTALIAS statement 90domain, RMTSYN statement 92IP_host, RMTSYN statement 92IPV4, RMTSYN statement 92IPV6, RMTSYN statement 92netid, RMTSYN statement 92SNA, RMTSYN statement 93

KPDPROC1 member 163, 170, 178, 185KPDPROCC member 163, 170, 178, 185

LLIFELINE

Active/Active Sites solution 94Lifeline Advisor 1, 3Lifeline Advisor data

access 11Lifeline Advisor monitoring 7, 9Lifeline Advisor monitoring data 55

Mmanuals

see publications ixmessage suppression 16monitoring data 55, 57monitoring information 3monitoring server

configuration 23self-describing agent parameters 161

MSUSEG 60MultiSystem Manager

enabling 96MVS command management

enabling 96

NNACMD.ROWSxxx statement 86navigator view, customized 50, 191netid keyword, RMTSYN statement 92NetView

V5R4samples 7

NetView agent, starting 15, 16NetView for z/OS Enterprise Management Agent

configuringcreating runtime members 168, 183registering with the local TEMS 164specifying agent address space parameters 165, 180specifying configuration parameters 164

NetView for z/OS Enterprise Management Agent (continued)configuring the persistent data store 169, 184EMAAUTO statement 78loading data files 46, 187NACMD.ROWSxxx statement 86specifying communication protocols 168, 180starting 86

notationenvironment variables xvpath names xvtypeface xv

Oonline publications

accessing xiioperator definitions

GDPS Active/Active Continuous Availability solution 8overview 1

Ppacket trace data

enabling collection 96PARMGEN

scenario 29password authorization 19path names, notation xvpersistent data store

configuring for a hub Tivoli Enterprise MonitoringServer 162

completing 163, 178database allocation job 163, 178maintenance job card 163runtime members 163, 178specifications 162

configuring for the monitoring agent 169, 184disk space requirements 169, 184monitoring agent

database allocation job 171, 186maintenance job card 170, 185runtime members 170, 185

polling intervaldelay 74

primary controller 15system name 68

production system information 13protocols

IP.PIPE 161specifying communications protocols for the monitoring

agent 168, 180specifying communications protocols for Tivoli Enterprise

Monitoring Server 160, 176publications

accessing online xiiNetView for z/OS ixordering xii

QQ replication 3


RRACF definitions

GDPS Active/Active Continuous Availability solution 8recommended configuration

creating a base runtime environment 155, 172registering the monitoring agent with the local Tivoli

Enterprise Monitoring Server 164remote

communications 89, 92replication 1REPLICATION

Active/Active Sites solution 94replication events 16replication monitoring 7, 17replication monitoring data 55

stopping 57replication server data

access 18RKANSAM data set 163, 170, 178, 185RKANSAMU data set 163, 170, 178, 185RMTALIAS statement 14, 89RMTCMD communication 12, 19RMTINIT.IP statement 91RMTSYM statement 14RMTSYN statement 92RTE

creating and configuring 30runtime environments

accessing from the configuration tool 154, 172building the libraries 157creating a base runtime environment 155, 172

runtime librariesloading 171, 186

runtime members 168, 183Tivoli Enterprise Monitoring Server 162

Ssample configuration

configuring a hub Tivoli Enterprise MonitoringServer 157, 175

samplesV5R4 7

sampling interval 56security 19

replication server data 18seed data 47, 188service xiiiservice management connect xiiisession monitor

enabling 96SETPROG APF example 171SMC xiiiSMP/E installation

NetView agent 154NetView program 7

SNA 161SNA keyword, RMTSYN statement 93starting

NetView agent 15, 16Tivoli Enterprise Monitoring Server 15, 16

statistics, data collection 55support xiiisysplex

entry point 82

sysplex masterconnectivity checks 81

SYSTCPD 172System Automation for z/OS 96

TTCP/IP connection data

enabling collection 96TCP/IP feature 95TCPIPCOLLECT 96

PKTS subtower 97TCPCONN subtower 97

TEMAACTIVEACTIVE subtower 97CONINACT subtower 97CONNACT subtower 97DVCONN subtower 97DVDEF subtower 97DVROUT subtower 97DVTAD subtower 97HEALTH subtower 97SESSACT subtower 97SYSPLEX subtower 97TELNET subtower 98

Tivolitraining, technical xiiiuser groups xiii

Tivoli Enterprise Monitoring Serverconfiguring a hub

configuring the persistent data store 162, 177creating runtime members 162, 177specifying configuration values 158, 175specifying TEMS communication protocols 160, 176

Tivoli Enterprise Monitoring Server, starting 15, 16Tivoli Enterprise Portal

installing 149Tivoli Enterprise Portal Server

installing 149Tivoli Enterprise Portal user interface 3Tivoli Management Services

installing components 149Tivoli NetView for z/OS Enterprise Management Agent 97Tivoli Software Information Center xiiTOWER statement 94training, Tivoli technical xiiitypeface conventions xiv

UUNIX, adding application data to a hub monitoring

server 47, 188user groups

NetView, on Yahoo xivTivoli xiii

Vvariables, notation for xvview, customized navigator 50, 191VSAM data 95VSAM replication 3

Index 205

WWeb Services Gateway function

enabling 96Web Services server

enabling 96workload

configuration 1workspaces

installing 46, 187

XXCF events 16XCF group 12XCF.RANK statement 14, 18, 98

YYahoo user group, NetView xiv


IBM®

Printed in USA

SC14-7477-03

Documents

Installation: Configuring the GDPS Active/Active …...NetV iew pr ogram and the NetV iew for z/OS Enterprise Management Agent for the GDPS Active/Active Continuous A vailability solution