Creating Configuration Items for unique address spaces

<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 to include the type value in the Discovery data. You cannot code the same type value twice.

<class>...</class> 

Address space definition

Choose from the following set of classes:

• 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.

<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>¹

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 specifies which address spaces should generate an instance of this CI. The pgmid mask is 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 use IEB* for any program starting with the characters IEB, and ASMBLY?0 for a program such as ASMBLY10, ASMBLY20, ASMBLYA0, and so forth.

 <cmdnm>...</cmdnm>²

<include>...</include>¹

<exclude>...</exclude>¹

<parm>...</parm> 

<subtask>...</subtask> 

<addrtype>...</addrtype> 

 <dzs_parms>...</dzs_parms>

(Optional) BMC Discovery for z/OS input parameters

<dzs_interval>...</dzs_interval> 

(Optional) Defines the interval in minutes within which the discovery data collector runs

<dzs_min_age>...</dzs_min_age> 

(Optional) Defines the minimum age in minutes for an address space to be discoverable

<dzs_max_swap>...</dzs_max_swap> 

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

(Optional) Defines the maximum number of 1,000 lines to read when processing an SDSF job log. Valid values are between 1 through 999999. The default value is 100, representing 100,000 lines.

<dzs_rexxout>...</dzs_rexxout> 

(Optional) Defines the data set name to be used to debug system REXX programs

<dzs_rexx>...</dzs_rexx> 

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

• NO—Default value for MVI Discovery (CAS)
• YES—Default value for BMC Discovery for z/OS (PAS)                                             

<xpgm>...</xpgm> 

(Optional) Extensible program statement that you can be use to further qualify or obtain information about an address space

You can specify more than one <xpgm>...</xpgm> sequence for a given object to combine multiple statements.

For more information, see Using-the-xpgm-object-statement.

(Optional) Specifies whether Db2 command can be processed during a discovery run. Valid values are YES and NO. The default value is NO for both MVI Discovery (CAS) and Discovery for z/OS (PAS). You can use this definition to process the Db2 command issued to retrieve the Db2 group name.

To use this definition, you must grant the MVI Discovery (CAS) and Discovery for z/OS(PAS) userid with the authority to run the Db2 command.

(Optional) Defines the prefix value for the issued Db2 command. The default value is -. To update the Db2 command prefix, set this parameter to a value as defined in the Db2 system. You can use this definition to process the Db2 command to retrieve the Db2 group name.                          

To use this definition, you must grant the MVI Discovery (CAS) and Discovery for z/OS (PAS) userid with the authority to run the Db2 command.