Getting Started With the IBM Tivoli Discovery Library Adapter for z/os

Transcription

1 Getting Started With the IBM Tivoli Discovery Library Adapter for z/os December 2012 IBM Advanced Technical Skills Mike Bonett Executive I/T Specialist

2 Special Notices This document reflects the IBM Advanced Technical Skills understanding on many of the questions asked about the Discovery Library Adapter for z/os. It was produced and reviewed by the members of the IBM Advanced Technical Skills organization. This document is presented As- Is and IBM does not assume responsibility for the statements expressed herein. It reflects the opinions of the IBM Advanced Technical Skills organization. These opinions are based on hands on experiences with the IBM Tivoli Discovery Library Adapter for z/os. If you have questions about the contents of this document, please direct them to Mike Bonett Trademarks The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States and/or other countries: CICS, DB2, IBM, MQSeries, Parallel Sysplex, System z, WebSphere, z/os. zseries. A full list of U.S. trademarks owned by IBM may be found at Microsoft, Windows, Windows NT and the Windows logo are registered trademarks of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group. LINUX is a registered trademark of Linus Torvalds. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States and/or other countries. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. Other company, product and service names may be trademarks or service marks of others. Acknowledgements Many thanks to Art Eisenhour, IBM Advanced Technical Skills, for reviewing this paper and providing input. ( Page 2 of 21

3 What is the IBM Tivoli Discovery Library Adapter for z/os?... 4 Obtaining and Installing the z/os DLA... 5 Customizing the z/os DLA... 6 Discovery Execution Flow... 6 Viewing the z/os DLA Output using the IdML XML Viewer Summary ( Page 3 of 21

4 What is the IBM Tivoli Discovery Library Adapter for z/os? Knowing the components that are running on an operating system platform, along with the configuration and relationships among the components, is critical for efficient monitoring and management. For z/os, the ability to run many different types of workloads results in a complex set of components, configurations and relationships. Identifying what is configured, running, and the component relationships relationships both within the z/os environment and external to z/os must be performed to ensure both efficient service to applications supported by the components, and efficient application of service management to z/os. The IBM Tivoli Discovery Library Adapter for z/os (referred to in the rest of this paper as the z/os DLA) detects and discovers active z/os resources and their connections and relationships. The resources the z/os DLA discovers includes: - IP information (V4 and V6). - z/os information such as active PARMLIB members, IPL information, authorized programs, etc. - System z hardware information such as serial numbers, LPARs, and z/vm guest information. - CICS information - transactions, programs, files, etc. - DB/2 for z/os information databases, tablespaces, etc. - IMS information transactions, programs, databases, etc. - WebSphere information cell, node, configuration files, etc. - WebSphere MQ information queue managers, queues, channels, ports, etc. - Address space information type, dataset allocations, program name, TCP/UDP ports, etc. - DASD volume information. The z/os DLA creates XML files (also referred to as Books ) that can be used to understand the environment, or can be processed by products such as Tivoli Application Discovery and Dependency Manager (TADDM), which uses the z/os DLA in conjunction with distributed discoveries to show end-to-end application relationships among components. Tivoli Business Service Manager (TBSM), which uses the z/os DLA to identify z/os components that are part of defined services, and map incoming events from sources such as the IBM Tivoli Event Pump for z/os to these components to determine the impact on the services. Tivoli Change and Configuration Management Database (CCMDB), which is a representation of the Information Management Infrastructure Library (ITIL ) Configuration Management Database (CMDB), with the addition of change management information. The z/os DLA also provides the IdML XML Viewer to view the created files and understand the discovered components and relationships. The IdML XML Viewer runs on a Windows workstation. Examples of using this tool will be provided later in this paper. ( Page 4 of 21

5 Other products also provide Discovery Library Adapters related to the z/os environment. These include: - IBM Tivoli NetView for z/os, which focuses on network (SNA and IP) resource discovery. - IBM Tivoli System Automation for z/os, which discovers SA configuration data such as Subsystems (APLs), Application Groups (APGs), and Monitor Resources (MTRs). - IBM Tivoli Monitoring Services, which discovers resources from a OMEGAMON/ITCAM/Tivoli Enterprise Monitoring Agent (TEMA) perspective. - CICS, which discovers CICS information based on the CICSPlex Systems Manager configuration. This paper will not cover these other Discovery Library Adapters. However, these DLAs are useful in gaining more information from the z/os environment. The resources in the various DLAs are consolidated at the TBSM or TADDM level to connect together various representations of the same resource. The z/os DLA provides a fast, objective way to collect information on the active z/os resources. When the z/os DLA is executed on a regular basis, the discovered information can be used in a variety of ways. At the simplest level it can be used as a configuration or operation audit tool to verify that components are defined, configured, and being used as expected. The advanced uses of the z/os DLA involve the integration of its output into TBSM and TADDM to support end-to-end application and service monitoring, and the inclusion and maintenance of z/os information into the Change and Configuration Management Database (CCMDB) for clients pursuing an ITIL based Service Management strategy. Use of the z/os DLA is an easy way to start incorporating z/os configuration information into ITIL processes via the CCMDB. The z/os DLA is also used with the IBM Tivoli Event Pump for z/os. The Event Pump detects z/os events and forwards them to event managers such as Tivoli Enterprise Console and Netcool OMNIbus. The Event Pump maps the event contents so that events sent to TBSM via Netcool OMNIbus are properly matched with the z/os DLA discovered resources defined TBSM. Obtaining and Installing the z/os DLA The z/os DLA is packaged with TADDM, CCMDB, or TBSM for z/os. Licensing these products for usage with z/os is required to use its functions. As of this writing version 3.1 is available; the feature provides SMP/E FMID HIZD310. The z/os DLA Program Directory (publication GI ) is available from the IBM support website ( search on the publication number) and provides the SMP/E installation directions. After the installation steps are completed, the following target libraries are used for running the z/os DLA: - <HLQ>.SIZDEXEC - REXX programs used during the discovery process. ( Page 5 of 21

6 - <HLQ>.SIZDLOAD - Load modules used during the discovery process - <HLQ>.SIZDMAPS - Mapping information used when processing the discovered resources. - <HLQ>.SIZDMESG - Product message definitions called during discovery processing - <HLQ>.SIZDSAMP - Samples used as a base to configure discovery for the environment. Customizing the z/os DLA The SIZDSAMP partitioned dataset is the focus of customizing the z/os DLA to properly execute discovery and collect the desired data. The naming conventions for the dataset members are: - IZDJxxxx Jobs (or started tasks) to be submitted - IZDPxxxx JCL procedures called by the IDCJxxx members - IZDCxxxx sample discovery configuration and FTP members, used as input to the IDCJxxxx members, to define the scope and depth of discovery. Make a copy of the SIZDSAMP dataset and use the copy to perform the customization and execution of the z/os DLA. This preserves the relationships already defined in the JCL for finding JCL procedures and members, and prevents customization from being impacted by product maintenance. A partitioned dataset is required to hold the output of the z/os DLA execution (the XML files). It can be pre-allocated, or the discovery process will attempt to allocate it if it does not exist. Discovery Execution Flow The following is a high level diagram of the execution flow: ( Page 6 of 21

7 The details for each of the steps are as follows: 1. The IZDJRUN member of SIZDSAMP is submitted as a batch job (it can be modified to run as a started task, but it does not run for long, so leaving it as a job is easier). Running the job when the desired subsystems are running is best, as the z/os DLA will not discover inactive subsystems. Schedule the job to run on a regular interval (e.g. once a week), depending on the dynamic nature of the z/os environment and changes, to keep the discovery information up to date. The job requires the following parameters to be set in its JCL: - REGSIZE the address space memory size for execution. - IDMLDSN -the output dataset where this execution will place the discovered information. - PARMMEM - the member in SIZDSAMP containing the input parameters defining the type and scope of the discovery. - FTP- if the created XML file(s) will be sent to a TBSM or TADDM server (or any other staging location desired) via FTP. - FTPMEM - If the files will be sent via FTP, the member in SIZDSAMP containing the FTP connectivity information. The PARMMEM member contains the statements defining the type and scope of discovery: - The subsystems to be discovered. - The level of detail to be discovered for these subsystems. ( Page 7 of 21

8 The z/os Discovery Library Adapter Users Guide provides details on defining the discovery scope and depth by setting discovery and filter directives in this member. For discovery the key directive statements are BOOK, DISC, and FILT. There are additional directive statements for controlling FTP, Refresh, and debugging (SET), custom servers for use in TADDM (CUSTSRVR and CRITERIA), and files to associate with the discovered resources (FILES). To define which z/os information and subsystems are discovered, the BOOK statement is used: BOOK TYPE.ZOSBASE YES BOOK TYPE.ZOSTASK YES BOOK TYPE.IMS YES BOOK TYPE.DB2 YES BOOK TYPE.CICS YES BOOK TYPE.MQ YES BOOK TYPE.WEBSPHERE YES BOOK.TYPE ZOSALL NO In this example, separate books (XML files) will be created for ZOSBASE (System z hardware and z/os information), ZOSTASK (active started tasks) and active IMS, DB2, CICS, MQ, and WebSphere Subsystems. Individual XML files will be created for each type of subsystem e.g. if 2 CICS regions CICS31A and CICS31B are running while the z/os DLA is executing, a discovery XML file will be created for each region. If the ZOSALL BOOK statement were set to yes, all of the discovered subsystems would be put into a single XML book. The recommended practice for a single z/os DLA execution is to either discover the individual subsystems separately and set BOOK.TYPE ZOSALL to NO, or set the individual subsystems to NO and set BOOK.TYPE.ZOSALL to YES. For each subsystem type, the DISC and FILT directive statements provide further identification and filtering of what will be discovered. For example: - The specific started tasks names to discover. - The specific subsystems of a particular type to discover. - Within a specific subsystem, the type of resources discovered, and filtering to include or exclude resources based on naming conventions. In this example the following statements define a DB2 discovery: ( Page 8 of 21

9 * * DB2 Discovery * DISC DB2 YES * Discover DB2 DISC DB2.DSNA NO * Exclude the DSNA subsystem DISC DB2.DATABASE YES * Discover DB2 databases DISC DB2.TABLESPACE YES * Discover DB2 tablespaces FILT DB2.DATABASE_NAME.TST EXCLUDE FILT DB2.TABLESPACE_NAME.TST EXCLUDE From these statements, DB2 resources for active DB2 subsystems will be discovered except for subsystem DSNA, which will not be discovered. Within the discovered subsystem, databases and table spaces whose names begin with TST (the prefix on the FILT statements) will not be discovered. 2. The IZDPDISC is the procedure called by IZDJRUN. The IZDJRUN parameters are used within the three job steps in IZDPDISC. 3. The first step of IZDPDISC allocates the output dataset (the IDMLDSN value in the IZDJRUN parameters) where the XML files will be placed. If the dataset is already allocated (either pre-allocated or from previous runs), this step can be commented out. 4. The second step of IZDPDISC performs the discovery by invoking the programs (load modules and REXX routines) to query z/os and the various subsystems and gather the information. To properly discover resources, the following steps must be performed: - The SIZDLOAD dataset must be APF authorized. - The ID that runs the IZDJUN job must has Security Server (RACF) authorization to: Read PARMLIB, Issue MQ DISPLAY commands Read DB2 SYSIBM resources, and issue DB2 DISPLAY commands Read WebSphere Application Server configuration files Have an OMVS segment with authority to issue the netstat, host, and home commands - DB/2 subsystems to be discovered must have the DB2 REXX interface (DSNREXX) installed. - For multiple DB2 versions the SDSNLOAD library matching the DB2 version must be available via LNKLST or STEPLIB in the IZDPDISC proc. - For WebSphere MQ discovery the SCSQANLE AND SCSQAUTH libraries must be must be available via LNKLST or STEPLIB in the IZDPDISC proc. This step creates a set of XML files as partitioned dataset members, and are placed in the output dataset. The specific ones created are based on the BOOK definitions in the discovery input member. For multiple systems of the same type, a separate member is created and named to identify the subsystem. For example: ( Page 9 of 21

10 - CICS subsystem XML members are named after the region name. - DB2 Subsystem XML members are named aaaamstr, where aaaa is the DB2 subsystem name. - MQ XML members are named aaaamstr, where aaaa is the MQ Queue Manager name. - WebSphere Application Server members are named after the server instance short name. 5. If the FTP option was enabled in the IZDJRUN parameters, the third step of IZDPDISC calls the IZDPFTP proc to send the members to TBSM or TADDM. Both products have components that monitor a directory on the server for new XML files, and when new files arrive in the directory they are automatically processed. IZDPFTP will ftp the member and rename the files on the TBSM or TADDM server to match the required naming convention used by TBSM and TADDM for discovery files. The FTP step can be run separately, if desired. Member IZDJFTP in SIZDSAMP is also provided, to just ftp the existing members in the output dataset to TBSM or TADDM. Viewing the z/os DLA Output using the IdML XML Viewer The files created by the z/os DLA process are XML text files. The file contents conform to the Discovery Library IdML XML schema and Common Data Model (CDM). Appendix C of the IBM Tivoli z/os Discovery Library Adapter Users Guide and Reference provides extensive details on how z/os resources are mapped to classes in the CDM. The XML files define both resources and relationships. For example, the ZOSALL book contains all of the classes and relationships for all of the components. The following picture is a high level representation of that information: ( Page 10 of 21

11 Trying to look at these XML files as plain text to determine the classes and relationships is clearly an overwhelming task. The recommended method is to use the IdML XML Viewer. This available from the IBM Support Center, as the file idml_browse.hta. By downloading the created XML files to a Windows platform, the IdML XML Viewer can be used to examine the contents of the files. This section will walk through an example of using the Viewer. The output XML files must be downloaded (as text) files from the output dataset to a Windows platform. Place the idml_browse.hta file on the same platform and execute it. The initial menu appears: Use either the Browse button on the upper right, or select a folder to move to the location of the downloaded XML files: For this example the ZOSALL XML file is selected (since it contains all of the discovered subsystems) by either double clicking on the file name or (if using browse) selecting the file and using the SUBMIT button to open the file: ( Page 11 of 21

12 The Class Summary gives the type and number of resource classes discovered. Selecting any one of them will drill down to more detailed information. The MSS Details provides a summary of the CDM Schema information, the z/os DLA version, and the name and timestamp of the XML file. On the lower left of the screen, below the Class Summary, is the Link Summary, and below the Link Summary section links to browse/edit the XML file: ( Page 12 of 21

13 The Links Summary section shows the types of relationships among the resources that have been discovered (an example will be shown later in the paper). From the Class Summary section, more details of a resource class can be viewed. Selecting zos provides the following information: ( Page 13 of 21

14 ( Page 14 of 21

15 In addition to z/os configuration details, the lines with the light blue background identify the relationships between the z/os system and other resources. In the above picture there is a installedon link to a System z hardware class resource, and a hosteddependency link (resources that depend on this z/os resource) to MQ and DB2 subsystems (all of the hosteddependencies are not shown on this screen capture). If the WMQA-MVST-MQSubsystem link is selected, details on the configuration and relationships of that Queue Manager are displayed: ( Page 15 of 21

16 The zos DLA discovers relationships between different subsystems. For this Queue Manager it shows a relationship (a transactional dependency) with a CICS region (CICSTIV1-MVST- CICSRegion), as it has discovered that a CICS-MQ bridge is defined and exists between CICSTIV1 and the Queue Manager. Selecting the CICSRegion link provides us with details on the CICS Region configuration: ( Page 16 of 21

17 For this discovery individual CICS program and transaction classes were not created. This is usually a good idea the first time discovery is performed to just see what exists without creating an overwhelming amount of output. However, it still reports on the number of programs and ( Page 17 of 21

18 transactions found. The ZReport link on the left (under Class Summary) shows the reports generated for the various classes: This is a partial listing of the screen. The entire list shows the various reports than can be accessed. For example: - Address space dataset allocations - CICS SIT parameters, programs, transactions - DB2 Databases, tables spaces - Storage volumes - PARMLIB, APF, LINKLST, and exits: The CICS Transactions report shows the transactions for the selected CICS region: ( Page 18 of 21

19 The Address Space Allocations report shows the dataset allocations for an address space: ( Page 19 of 21

20 ( Page 20 of 21

21 The Storage Subsystems report shows basic details for each storage volume: Summary This paper is not meant to provide an exhaustive examination of the z/os DLA and the IdML files, but to provide enough information to understand their purpose and to begin using them. The z/os DLA discovers and consolidates a wealth of information about a z/os environment that is useful for configuration, operational, and auditing purposes. Integration with TBSM or TADDM increases its value, as this enables z/os resources to be related to resources outside of the z/os environment. This provides a starting point for end-to-end Service Management visualization, control, and automation activities. Further details beyond this white paper can be found in - IBM Tivoli Discovery Library Adapter for z/os Program Directory (GI ) - IBM Tivoli Discovery Library Adapter for z/os Users Guide and Reference (SC ) ( Page 21 of 21