Action job output

Edit online

Review the types of output data sets that are produced by the KCIOMEGA program.

Configuration Manager writes job output for the KCIOMEGA actions to a number of output data sets. Output from invoked utilities is also generated, with each utility writing to its own output data set.
Note: KCIALPHA is an APF-authorized version of the KCIOMEGA program. The information in this topic also applies when using KCIALPHA.

The following table lists the output data sets that Configuration Manager generates and retains.

Table 1. Standard sysout data sets
Output data set Description
KCIPRINT KCIOMEGA program messages and messages about Configuration Manager processing
KCITRACE KCIOMEGA workflow trace output, used primarily by IBM Software Support for troubleshooting
KCIVARSO KCIVARS input that was used in the JCL
DSNPROUT Contents of the RTEDEF library used in the configuration. When the DEBUG action option is used, this data set contains the complete list of members in the RTEDEF library.
Note: The DEBUG action option should only be used under the guidance of IBM Software Support.
$VALRPT Parameter validation report
MIGRPT Output for the MIGRATE action
EXCLRPT List of members excluded (not replaced) in the runtime libraries during the GENERATE action
REPORT Products installed report. This report appears automatically in the job output for the CREATE, MIGRATE, and GENERATE actions and can also be generated using the KFJMAINT maintenance workflow by specifying ACTION REPORT.
$REPORT Output for the DEPLOY action
JESMSGLG, JESJCL and JESYSMSG Standard JES-produced output

In addition to the output data sets listed in Table 1, Configuration Manager also generates other output that it does not retain and deletes from the spool automatically.

If a Configuration Manager job fails, the DD statement that contains the error message is retained and printed.

Notes:
  • JES3 does not allow deleting DD output. If your site uses JES3, you might see additional output, which can be considerable.
  • With APAR OA65222, the DEBUG action option (OPTION DEBUG), is introduced. This option generates additional output that is otherwise suppressed by default. This option should only be used under the guidance of IBM Software Support. Prior to this enhancement, all generated output was retained and printed to the spool, which could result in hundreds of output data sets.

To review the Configuration Manager job output, use a tool such as SDSF to view the JES output data sets.

KCIPRINT sysout data set

The KCIPRINT output data set contains messages from the KCIOMEGA program interspersed with messages about Configuration Manager processing.

Here is an example KCIPRINT for a successful job:

Figure 1. Example KCIPRINT output data set for a successful Configuration Manager job
KFU00001I KCIOMEGA is starting; SYSPLEX=sysplex LPAR=lpar DATE=…
KFU00002I INVOKE processing is about to commence; MEMBER=KFJOMEGA
…
Workflow has completed successfully
KFU00004I KCIOMEGA is ending; RC=rc SYSPLEX=sysplex LPAR=lpar DATE=…
Parameter values used

The KCIPRINT sysout data set from a GENERATE action contains an ordered list of the RTEDEF library members that the action uses. For example:

01. Using parameters in rte_plib_hilev.RTEDEF(rte_name)
02. Using parameters in rte_plib_hilev.RTEDEF(KDS$PARM)
03. Using parameters in rte_plib_hilev.RTEDEF(GBL$PARM)
The corresponding KCITRACE sysout data set contains an alphabetical list of parameters and symbols (such as workflow variables) with their values. The list is preceded by the following heading: 
>Parameter and symbol values
Note to users with PARMGEN experience: The GENERATE action of Configuration Manager creates an rte_plib_hilev.rte_name.WCONFIG(rte_name) member that is similar to the member created by PARMGEN, with one key difference: the member created by Configuration Manager contains default parameter values; it does not reflect the values in your RTEDEF library members. To see the parameter values used by Configuration Manager, refer to the >Parameter and symbol values heading in the KCITRACE sysout data set. As such, the WCONFIG data sets as a whole should be considered as a black box.

KCITRACE sysout data set

The KCITRACE output data set contains the KCIPRINT contents, and, in addition, also includes the source of each workflow skeleton and additional messages.

KCITRACE records that start with two consecutive plus signs (++) show the previous record after variable substitution. For example:

//RTEDEF DD DSN=%RTEDEF_DSN%,PASS=YES    
++RTEDEF DD DSN=MYID.MONITORS.RTEDEF,PASS=YES

Renamed SYSPRINT sysout data sets

The KCIOMEGA program runs a workflow, such as the GENERATE action of Configuration Manager, that can invoke many programs, resulting in long job output listings. All of these programs run in the same job step as KCIOMEGA.

Many programs write to the ddname SYSPRINT. To avoid a job output listing with multiple SYSPRINT ddnames for the same step name, KCIOMEGA renames SYSPRINT sysout data sets to match the corresponding step name in the workflow skeleton shown in KCITRACE. This makes it easier to find the SYSPRINT for each step in the skeleton.

Parameter validation report ($VALRPT)

If the set of parameters that you specified in the RTEDEF library is invalid (for example, a required parameter is missing or a defined value is incorrect), then the sysout data sets include the parameter validation report ($VALRPT). If this report is generated, then review the report, correct the parameters, and resubmit the job.

If you are familiar with PARMGEN: The Configuration Manager parameter validation report contains the same information as the parameter validation report generated by PARMGEN, with the difference that you do not have to manually navigate to the data set and open it.

Products installed report (REPORT)

The products installed report provides information about the installation status and Configuration Manager support of products at your site. The report identifies the following products:
  • Products that are installed and supported by Configuration Manager
  • Products that are installed but not supported by Configuration Manager
  • Products that are not installed but supported by Configuration Manager
The report appears automatically in the job output for the CREATE, MIGRATE, and GENERATE actions. You can also generate the report using the KFJMAINT maintenance workflow by specifying ACTION REPORT. (No other option or parameter is required to run the KFJMAINT job with the REPORT action.)
Tip: By producing the report using KFJMAINT, you can verify that your product is supported by Configuration Manager before beginning the configuration process. For a complete list of supported products, see Products supported by Configuration Manager.

The report is printed to the job output identified by the REPORT DD statement.

The report lists the product code, the product version, and the product name. If the version is not supported in Configuration Manager, then an asterisk appears after the version and the comment (not supported) appears after the name. If the product is not installed, then N/A appears as the version and the comment (not installed) appears after the name.

The following figure shows an example of the products installed report:
Figure 2. Products installed report (REPORT)
+--------------------------------------------------------------------------------------------+
| Products installed in <data_set_name>                                                      |
+--------------------------------------------------------------------------------------------+
| Code | Version | Product name                                                              |
+--------------------------------------------------------------------------------------------+
| KM5    N/A       IBM Z OMEGAMON AI for z/OS (not installed)                                |
| KN3    5.1.0*    IBM OMEGAMON for Networks on z/OS (not supported)                         |
| KWO    5.6.0     IBM OMEGAMON Dashboard Edition on z/OS                                    |
| KS3    6.1.0     IBM Z OMEGAMON AI for Storage                                             |
| KC5    6.1.0     IBM Z OMEGAMON AI for CICS                                                |
| KGW    6.1.0     IBM Z OMEGAMON AI for CICS Transaction Gateway                            |
| KI5    5.5.0     IBM OMEGAMON for IMS on z/OS                                              |
| KJJ    6.1.0     IBM Z OMEGAMON AI for JVM                                                 |
| KD5    5.5.0     IBM OMEGAMON for Db2 Performance Expert on z/OS                           |
| KQI    7.5.0     IBM OMEGAMON for Messaging Integration Bus                                |
| KMQ    7.5.0     IBM OMEGAMON for Messaging on z/OS                                        |
| KYN    7.1.1     ITCAM for Application Diagnostics Agent                                   |
| KDS    6.3.0     Tivoli Enterprise Monitoring Server                                       |
| KOB    7.5.0     OMEGAMON Enhanced 3270 User Interface                                     |
| KNA    4.4.0*    IBM Z NetView Enterprise Management Agent (not supported)                 |
| KRN    2.6.0     IBM Tivoli Advanced Catalog Management for z/OS                           |
| KRH    2.6.0     IBM Tivoli Advanced Reporting and Management for KFSMShsm (not supported) |
| KRG    2.6.0     IBM Tivoli Advanced Audit for DFSMShsm                                    |
| KRJ    3.3.0     IBM Tivoli Advanced Allocation Management for z/OS                        |
| KRK    3.3.0     IBM Tivoli Automated Tape Allocation Manager for z/OS                     |
| KRV    2.4.0     IBM Tivoli Advanced Backup and Recovery for z/OS                          |
| KAY    1.1.0     IBM Z OMEGAMON Data Provider                                              |
+--------------------------------------------------------------------------------------------+