Permanent input and output data sets

In the Datasets panel, you can view, modify, copy, and delete the names of these data sets. For details about using this panel, see Defining-permanent-data-sets.

UIE does not check for the existence of input data sets, which enables you to run UIE and generate JCL on a system that is different from the system on which the job is executed. However, if at execution time, one of the input data sets is not found, the UIE job abends.

How UIE handles permanent data sets

UIE does not check for the existence of permanent data sets.

Instead, the standard routine IEFBR14 is added to the JCL to specify all the output data sets with default or user-modified DCB and SPACE parameters and the value DISP=(MOD,CATLG). As a result, if a data set is not cataloged, it is allocated to a default volume and then cataloged.

UIE assumes that INPUT SMF and subsystem data always exists and is cataloged. However, in those rare situations when a necessary data set is not cataloged , or you are not satisfied with the default permanent output data set allocation parameters, you can change them as follows:

1. Type an S in the command column next to the data set whose parameters you want to change.
2. Open the Dataset Specifications panel.
3. Specify a new unit type, volume serial number, and other parameter values.

If you specify a particular volume serial number for an OUTPUT data set, but the data set does not exist on this volume, you need to either pre-allocate the data set manually or to change the DISP=(MOD,CATLG) to DISP=(NEW,CATLG) in the generated JCL. This step is necessary because z/OS handles DISP=(MOD,CATLG) when the particular volume is specified in a very special way, that is, the data set is catalogued, but not created physically on the volume. We recommend that you allocate the data set manually using DCB parameters created in the JCL prior to running the UIE job.

UIE uses the following types of data sets:

• SMF file—Contains the SMF and RMF records.

  To process several SMF files in a single job, you can concatenate several files in a single DD statement. Type R in the command column next to the first SMF file in the Datasets panel and press Enter. Type over the new file name with the name of the second SMF file.

  To input multiple SMF files that have dissimilar attributes, edit the generated JCL and place the file in separate DDs. For SMF data, use DDnames: SMF, SMF1, SMF2, ..., up to SMF9.

• MVCICS file—Contains BMC AMI Ops Monitor for CICS data. 

  To process several BMC AMI Ops Monitor for CICS files in a single job, you can concatenate several files in a single DD statement.
  To input multiple BMC AMI Ops Monitor for CICS files that have dissimilar attributes, edit the generated JCL and place the file in separate DDs. For BMC AMI Ops Monitor for CICS data, use DDnames: MVCICS, MVCICS1, MVCICS2, ..., up to MVCICS9.

• MVDB2 file—Contains BMC AMI Ops Monitor for Db2 data.

  To process several BMC AMI Ops Monitor for Db2 files in a single job, you can concatenate several files in a single DD statement.
  To input multiple BMC AMI Ops Monitor for Db2 files that have dissimilar attributes, edit the generated JCL and place the file in separate DDs. For BMC AMI Ops Monitor for Db2 data, use DDnames: MVDB2, MVDB21, MVDB22, ..., up to MVDB29.

• MVIMS file—Contains BMC AMI Ops Monitor for IMS Offline data. 

  To process several BMC AMI Ops Monitor for IMS Offline files in a single job, you can concatenate several files in a single DD statement.
  To input multiple BMC AMI Ops Monitor for IMS Offline files that have dissimilar attributes, edit the generated JCL and place the file in separate DDs. For BMC AMI Ops Monitor for IMS Offline data, use DDnames: MVIMS, MVIMS1, MVIMS2, ..., up to MVIMS9.

• TMON file—Contains TMON for CICS data.

  To process several TMON files in a single job, you can concatenate several files in a single DD statement.
  To input multiple TMON files that have dissimilar attributes, edit the generated JCL and place the file in separate DDs. For TMON data, use DDnames: TMON, TMON1, TMON2, up to TMON9.

• DCOLLECT file—Contains DASD volume free/used space data.

  TEMPFILE causes an IDCAMS step to be generated in the JCL, which writes DCOLLECT data to a temp file for later processing by UIE. NULLFILE eliminates this step. UIE treats any other data set name as an existing file. UIE opens and reads it.

• IMS Monitor file—Contains IMS Monitor data. 

  Specify the DDname, z/OS system ID, and subsystem ID in an APPLCONTROL command. For more information, see APPLCONTROL.

• Summary Report—Contains a summary of what happened during the UIE job run. You can specify this data set to be any of the following items:

  • A sequential data set
  • A member of a PDS (the member name should be in parenthesis)

  • SYSOUT= x, where x is a single-character output class, or an asterisk (*).

    You can add the form ID to this format where SYSOUT=(x, yyyy), using yyyy for the form ID.

  When you use this format for the data set name, the Summary Report is routed into a specified output class.

  The Summary Report contains the following information:

  • All UIE commands used in the job.
  • Error messages immediately following any command for which there was a syntax error. In most cases, the error message provides the correct syntax for the command.
  • Error messages at the end of the report for those errors that can be detected only after the command file is read.
  • Counts of found and selected records of each type and subtype, total by system ID.
  • A list of discovered subsystems (CICS, Db2, IMS, MQ) and the record types processed and selected for each subsystem.
  • A list of discovered servers and the record types processed and selected for WAS.
  • A list of discovered systems and partitions (for each modeling interval).

  • A detail application report, if requested.

    If errors are found in the command file itself, processing stops at the end of the command file. If any errors are encountered during the UIE job run, that is, any error messages at all appear in the Summary Report, then the XML model is either not created or is unusable and inaccurate.

• Debug Report—Contains warning messages, traces, all error messages sent to the Summary Report and other information that can help BMC Support diagnose a problem. (Normally, you should not have to look at the Debug Report.)

  You can send the Debug Report to either a data set or an output class (where it will be discarded after a certain time).

  Specify the data set name as one of the following types:

  • A sequential data set name.
  • A PDS (member name should be in parentheses).

  • SYSOUT= x, where x is a single-character output class, or an asterisk (*).

    You can add the form ID to this format where SYSOUT=(x, yyyy), using yyyy for the form ID.

  When you use this format for the data set name, the Debug Report is routed into a specified output class.

  If you are using an output class for both the Summary Report and the Debug Report, it is strongly recommended that you use different output classes for these two reports.

  Warning

  You cannot send the Summary Report and the Debug Report to the same sequential data set or to a member of the same PDS.

• Command file—Use to keep commands generated from parameters or commands specified in the various UIE panels separate from the JCL statements.

  If you specify the keyword SYSIN in the Datasets panel, an additional step is added to the generated JCL job that copies the commands from the input stream into a temporary data set. If you specify a command file name, the commands are copied into that data set.

• Targets file—A list of the BMC Performance Predictor for Mainframes machines that receive the XML formatted data file from this UIE job.

  NULLFILE as a data set name eliminates the push step from the generated UIE JCL. This file is maintained by the BMC Performance Predictor for Mainframes Data Subscription process.

• XML model file—This file must be a PDS. The member name must be no longer than five characters. 

  UIE creates one member for each defined interval in the specified PDS (in addition to the member specified on the Datasets panel) for which performance data of at least one system was found. These members have the following names:

  xxxxx001, xxxxx002, … xxxxx00 n

  xxxxx is a member name specified by the user.

  Member xxxxx itself contains summarized information for the data transfer service to ensure the delivery of all XML model data to the Windows Console.

• Visualizer file—This file can be a sequential data set or a PDS. 

  If used as a PDS, only one member is created in the file. This file contains information for Visualizer for all intervals and all systems processed by UIE.