Batch interface

Edit online

The JCL to run IBM Z® Monitoring Configuration Manager is simple and concise. You specify an action, the name of the runtime environment on which you want to perform that action, and the high-level qualifiers of the data sets for that runtime environment.

JCL

Figure 1. JCL to run Monitoring Configuration Manager

//UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
/*JOBPARM SYSAFF=<lpar>
//S1       EXEC PGM=KCIOMEGA,REGION=0M,DYNAMNBR=256
//STEPLIB  DD DISP=SHR,DSN=<tlib_hlq>.TKANMOD
//KCIFLOW  DD DISP=SHR,DSN=<tlib_hlq>.TKANCUS(KFJOMEGA)
//KCIVARS  DD *
*
*                                        
*<action> SELECT FROM:
* CREATE|DISCOVER|GENERATE|DELETE|MIGRATE|PACKAGE|DEPLOY
*                
ACTION            <action> 
OPTION            <option>
RTE_NAME          <rte_name>
RTE_PLIB_HILEV    <rte_plib_hilev>
/*

Similar JCL is supplied in the KFJJMCM member of the TKANSAM target library.

KCIOMEGA is the program that runs Monitoring Configuration Manager. The KCIFLOW data set provides input to KCIOMEGA. That is all you need to know about the KCIOMEGA program and the KCIFLOW data set to run Monitoring Configuration Manager. If you want to know more, see KCIOMEGA workflows.

Replace the placeholders in the JCL with appropriate values:

<lpar>

Run Monitoring Configuration Manager actions on the LPAR where you will start the runtime environment.

For example, if your site uses JES2, insert a SYSAFF job parameter after the JOB statement to ensure that the job runs on that LPAR.

<tlib_hlq>

The high-level qualifiers of the target libraries.

<action>

One of the Monitoring Configuration Manager actions.

You can abbreviate actions to their first three characters: CRE, DIS, GEN, DEL, MIG, PAC, and DEP.

<option>

One or more compatible Monitoring Configuration Manager options. Multiple options must be specified by a comma with no spaces.

<rte_name>

Runtime environment name, 1 - 8 characters.

Monitoring Configuration Manager uses this name for various purposes, including:

MVS™ member names
MVS data set name qualifiers
z/OS® UNIX® System Services directory name, all uppercase

<rte_plib_hilev>

The high-level qualifiers of the runtime environment definition library:

rte_plib_hilev.RTEDEF

Monitoring Configuration Manager uses the values of RTE_NAME and RTE_PLIB_HILEV to set the default value of other parameters, such as RTE_HILEV and RTE_VSAM_HILEV, that are used for data set names. To avoid exceeding the z/OS 44-character limit for data set names, the combined length of RTE_NAME and RTE_PLIB_HILEV should not exceed 28 characters. For example, if RTE_NAME is 8 characters, then RTE_PLIB_HILEV should not exceed 20 characters.

RTE_NAME and RTE_PLIB_HILEV parameters versus the values in KCIVARS

The CREATE action uses the RTE_NAME and RTE_PLIB_HILEV values that you specify in the KCIVARS input data set as the initial values of the RTE_NAME and RTE_PLIB_HILEV parameters in the rte_plib_hilev.RTEDEF(rte_name) member. At that point in time, the values of the RTE_NAME and RTE_PLIB_HILEV parameters in the RTEDEF(rte_name) member match the values that you specified in KCIVARS.

However, you might edit the values of the RTE_NAME and RTE_PLIB_HILEV parameters in the RTEDEF(rte_name) member so they no longer match the values that you specified in KCIVARS.

For subsequent actions, the RTE_NAME and RTE_PLIB_HILEV values that you specify in KCIVARS are used only to locate the rte_plib_hilev.RTEDEF(rte_name) member. The action uses the RTE_NAME and RTE_PLIB_HILEV parameters in that RTEDEF library.

Contents of the KCIVARS input data set

The contents of the KCIVARS data set are case-sensitive: you must specify the variable names and their values exactly as described.

KCIVARS can contain comment lines and inline comments:

Comment lines begin with an asterisk (*) in column 1.
```
* Comment line
```
Inline comments begin with an asterisk after a variable value.
```
RTE_NAME MYRTE * Inline comment
```