×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

End of support

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC Discovery for z/OS 1.8 Open link .
BMC Discovery for z/OS 1.7 Customizing after installation

Modify parmlib member MDZTTD00

Modify member MDZTTD00 in UBBPARM so that BMC Discovery for z/OS will create Configuration Items (CIs) for unique address spaces (objects) that are found on your mainframe, in addition to the objects that are defined by default in this member. Comment out the default definitions for objects that you do not want to discover.

The XML data is case sensitive. For example, the XML tags <type> and </type> must be lowercase, and the data itself (for example, CICS) must be in uppercase. The type XML statement for CICS is coded as follows:

<type>CICS</type>

To add an object to this member that is unique to your site, define it by using the XML tags <object> and </object>. There should be an <object> statement and a </object> statement surrounding the definition of each object to be discovered. Create an object definition by using the object statements listed in Object statement definitions. 

Parameter member MDZTTD00 also allows you to define the scope of where address spaces are discovered. The scope is specified by what is contained within the <sysplex> and </sysplex> parameters. Possible values are YES or NO. YES means that the object can run on any z/OS image in a sysplex, and NO means that the object must run on that specific z/OS image or LPAR.

Default <sysplex> values for specific types of servers are listed in MDZTTD00 default values. The user can change the <sysplex> parameter value from YES to NO and vice versa and thus change the scope of where a specific object is discovered. However, changing the scope also changes the attributes of the class that are stored in the CMDB. One of the attributes that is changed is BMC_ComponentAliases, which is used in the Service Impact Manager (SIM) product to ensure that events impact the correct CIs in a service impact model.

If you change the <sysplex> value, therefore, you could affect whether events impact a CI or not, which could have serious operational ramifications. Here is an example of an IBM CICS region called BCVCD640 running on the sysplex BBPLEX01 with two different <sysplex> values and what the resulting BMC_ComponentAliases value would be:

Example 
<object>
 <type>CICS</type>
 <class>TRANSACTION</class>
 <sysplex>YES</sysplex>
 <vendor>IBM</vendor>
 <pgmid>DFHSIP</pgmid>
</object>

This code would result in a BMC_ComponentAliases value of CICS-BBPLEX01-BCVCD640.

Example 
<object>
 <type>CICS</type>
 <class>TRANSACTION</class>
 <sysplex>NO</sysplex>
 <vendor>IBM</vendor>
 <pgmid>DFHSIP</pgmid>
</object>

This code would result in a BMC_ComponentAliases value of CICS-BBPLEX01-SJSC-BCVCD640. 

The fact that the BMC_ComponentAliases value changes means that events trapped in the BMC Impact Integration for z/OS (BMC II for z/OS) product with existing rules and sent over to the Service Impact Manager (SIM) might no longer cause the correct CI in a SIM model to be impacted. In the rule that traps an event in BMC II for z/OS, you might need to modify the new Component Alias value on the BA or AE panel, if it is not being provided by the QCA.QSERVER.serverName variables provided by BMC Discovery for z/OS. If you change any of the default <sysplex> values in the MDZTTD00 member, you must also ensure that the Component Alias value is still valid in each rule for associated events that you are trapping in BMC II for z/OS.

Object statement definitions

Object statement

Description

<type></type>

Object (address space) type definition

The following types are reserved in the default object members:

IMSTM, CICS

IMS, DBCTL, DB2

WAS, WASAPPS, WASDMGR, WASNAGT

MVCAS, MVLAS, MVPAS, DZPAS, SSPAS, MVLOGGER, RTCS

TOM

MQS, IMSCONN

CICSGTWY

RACF, ACF2, TSS

VTAM, TCP, HTTP, NETVIEW

MVHTTP IRLM, CQS, DBRC, MIM

HSM

JES

You can specify any new type, and that type value will be included in the Discovery data. You cannot code the same type value twice.

<class></class>

Address space definition

Choose from the following set of classifications:

APPLICATION—for example, WAS

COMMUNICATION—for example, VTAM, TCP

DATABASE—for example, IMS, DBCTL, DB2, ADABAS

MESSAGE—for example, MQS

PRINT—for example, JES

RESOURCE—for example, IRLM, CQS, DBRC, MIM, SMS

SECURITY—for example, RACF, ACF2, TSS

TRANSACTION—for example, IMSTM, CICS

If the object you are defining does not clearly fit into any of these classes, define the class as APPLICATION.

<sysplex></sysplex>

Address space affinity definition

  • YES means the object can run on any z/OS image in the sysplex (a CICS region).
    If you specify this value, the server is associated with the sysplex and not the system. If the same server is discovered and has moved from one system to another, it is still treated as the same server.
  • NO means the object must run on that specific z/OS image or LPAR (JES2).
    If you specify this value, the server is treated as a new server if it moves from system to system. (The system name is added to the Configuration Item name.)

<vendor></vendor>

Name of the vendor that provides the software that runs in the address space

The vendor name is limited to 24 alphanumeric characters. An example is IBM.

<pgmid> </pgmid>2

Program name that is specified in the PGM= statement of the JCL for the object that you want to discover

The program name is a mask field that is used to specify which address spaces will generate an instance of this CI. The pgmid mask will be matched to the value specified in the PGM= statement of the JCL. The mask uses a question mark ( ? ) to represent any single character and an asterisk ( * ) to represent any number of characters. (For example IEB* is used for any program starting with the characters IEB, and ASMBLY?0 for a program such as ASMBLY10, ASMBLY20, ASMBLYA0, and so forth.

<cmdnm></cmdnm>2

USS command name, that executes as a process under USS, for the object you want to discover

The command name is a mask field that is used to specify which processes will generate an instance of this CI. The mask uses a question mark ( ? ) to represent any single character and an asterisk ( * ) to represent any number of characters. For example, the following cmdnm statement will discover all processes where the command name is "FTPD", "ftpd",  or "/usr/sbin/ftpd".

<cmdnm>FTPD</cmdnm>

Note

The USS command program name is upper-cased to avoid having multiple entries. If a mixed-case entry is still needed for the object you want to discover, see <parm> field.

<include></include>1

(Optional) Mask for the names of jobs or started tasks to be discovered

In this example, you do not want to create Configuration Items for any started task that is executing program MDZ9DZ00 unless the started task is named PRODPAS. Only the started task named PRODPAS will have a CI created for it:

<object> 
 <type>PAS</type> 
 <class>RESOURCE</class> 
 <vendor>BMC</vendor> 
 <pgmid>MDZ9DZ00</pgmid> 
 <include>PRODPAS</include> 
</object>

<exclude></exclude>1

(Optional) Mask for the names of jobs or started tasks that are not to be discovered

Normally, a Configuration Item is created for all CICS regions that are found. By adding the an exclude statement, you request that the started task named TESTCICS is not discovered:

<object>
  <type>CICS</type>
  <class>TRANSACTION</class>
  <vendor>IBM</vendor>
  <exclude>TESTCICS</exclude>
</object>

In the following example, you want to create Configuration Items for any started task that is executing program MDZ9DZ00; however you have decided not to discover the started task named TESTPAS. Any other started task that is executing program MDZ9DZ00 will have a CI created for it:

<object>
  <type>PAS</type>
  <class>RESOURCE</class>
  <vendor>BMC</vendor>
  <pgmid>MDZ9DZ00</pgmid>
  <exclude>TESTPAS</exclude>
</object>

<parm></parm>

(Optional) Mask for a command parameter used to start either a STC or USS process

You can specify more than one <parm></parm> sequence for a given object if you want to have multiple parms represent that object.

The mask special characters are:

  • ? = Any character
  • * = Any number of characters
  • Aa-Zz, 0-9 = Exact match

In the following example, the parm statement discovers all address spaces that have "MjeJvmTestSuit.jar" as part of its start command, such as "/shrd/java/J8.0_64/bin/java -jar /shrd/HOME/lib/MjeJvmTestSuit.jar".

<parm>MjeJvmTestSuit.jar</parm>

Note

The parm statement can match any part of the start command. It is built with the '*' mask special character for both the leading and trailing characters.

<subtask> </subtask>

(Optional) Mask for a subtask name that is specified executing under the job or started task name to be discovered. You can specify more than one <subtask></subtask> sequence for a given object so that you can have multiple subtasks represent a given object. The mask special characters are:

  • ? = Any character

  • * = Any number of characters
  • Aa-Zz, 0-9 = Exact match

In the following example, the subtask statement discovers all address spaces that have a subtask name that begins with "IWMWBBR".

<subtask>IWMWBBR*</subtask>
<addrtype></addrtype> 

The address space type of the object that identifies the type of work an address space contains

This object statement is optional.

For example, you can use STC for a Started Task address space:

<addrtype>STC</addrtype>

The following Address space types are available:                             
  • ASC - ASCH (APPC) Address Space User                             
  • BAT - Batch                                                      
  • OMV - OpenMVS Address Space User                                 
  • STC - Started Task                                               
  • TSO - TSO User                          

<dzs_parms></dzs_parms>

BMC Discovery for z/OS input parameters

<dzs_interval></dzs_interval> 

Defines the interval in minutes in which the discovery data collector runs

<dzs_min_age></dzs_min_age> 

Defines the minimum age in minutes in order for an address space to be discoverable

<dzs_max_swap></dzs_max_swap>

Defines the maximum number of address spaces which will be swapped in during a discovery run

<dzs_rexxout></dzs_rexxout>

Defines the data set name to be used to debug system REXX

<dzs_rexx></dzs_rexx>

Defines if system REXX programs can be executed during a discovery run

The default value is YES.

1.Within a single object, you can have multiple exclude or include statements, but not both.

2.Within a single object, you can have multiple pgmid or cmdnm statements, but not both.

MDZTTD00 default values

Server class

Object type

Vendor

Object description

Sysplex value

TRANSACTION

CICS

IBM

CICS region

YES

TRANSACTION

IMSTM

IBM

IMS Transaction Management

YES

DATABASE

IMS

IBM

IMS Database server

YES

DATABASE

DBCTL

IBM

DBCTL server

NO

DATABASE

DB2

IBM

DB2 server

YES

APPLICATION

WASAPPS

IBM

WebSphere Application Server

YES

APPLICATION

WASDMGR

IBM

WebSphere Deployment Manager

YES

APPLICATION

WASNAGT

IBM

WebSphere Node Agent

YES

APPLICATION

WAS

IBM

WebSphere Undetermined

YES

APPLICATION

MVCAS

BMC

MainView Coordinating Address Space

NO

APPLICATION

MVLAS

BMC

MainView Logon Address Space

NO

APPLICATION

DZPAS

BMC

Discovery Agent Address Space

NO

APPLICATION

MVPAS

BMC

MainView Product Address Space (MVI)

NO

APPLICATION

SSPAS

BMC

MainView Product Address Space (BBI2)

NO

APPLICATION

RTCS

BMC

Runtime Component System server

NO

APPLICATION

TOM

BMC

Total Object Management server

NO

APPLICATION

MVLOG

BMC

MainView Logger server

NO

APPLICATION

SYSLOG

IBM

SYSLOG server

NO

APPLICATION

MVTA

BMC

MainView Transaction Analyzer

NO

MESSAGE

MQS

IBM

Runtime Component System server

YES

MESSAGE

IMSCONN

IBM

IMS Connect server

YES

MESSAGE

CICSGTWY

IBM

CICS Transaction Gateway server

NO

SECURITY

RACF

IBM

RACF server

NO

SECURITY

ACF2

CA

ACF2 security server

NO

SECURITY

TSS

CA

TSS security server

NO

COMMUNICATION

VTAM

IBM

VTAM server

NO

COMMUNICATION

TCP

IBM

TCP/IP server

NO

COMMUNICATION

HTTP

IBM

HTTP server

YES

COMMUNICATION

NETVIEW

IBM

NETVIEW server

NO

COMMUNICATION

MVHTTP

BMC

MainView Host server

NO

RESOURCE

IRLM

IBM

IRLM server

NO

RESOURCE

CQS

IBM

CQS server

YES

RESOURCE

DBRC

IBM

DBRC server

YES

RESOURCE

INETD

IBM

INETD server

NO

RESOURCE

MIM

CA

MIM server

NO

RESOURCE

HSM

IBM

HSM server

NO

RESOURCE

USS

IBM

USS server

NO

PRINT

JES

IBM

JES server

NO

PRINT

INFOPRNT

IBM

INFOPRNT server

NO


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by Dana Thawkho on Jan 14, 2021
customization

Comments

Log in or register to comment.

Validate RTCS system resources
Integrating
© Copyright 2013 - 2022 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.