Specifying JOB EXEC and DD statements

JCL to execute a Log Analyzer job includes a JOB statement, an EXEC statement, and various DD statements. The following generic JCL example runs a Log Analyzer job:

JOB statement

Provide a JOB statement that conforms to the standards of your environment.

EXEC statement

Provide an EXEC statement that specifies LUIMAIN as the program name.

The recommended region size is 0 MB. If your environment does not allow the specification of REGION=0M, specify the largest region size that is allowed.

Important

A Log Analyzer job can consume a large amount of system resources. To prevent resource contention that can affect production workloads, consider executing the Log Analyzer job on a non-production system or implementing workload management parameters, dispatch priorities, or both, to prevent over-consumption of resources.

For more information, see Troubleshooting analysis jobs.

STEPLIB DD statement

Provide a STEPLIB DD statement that includes the following modules in the data set concatenation, or ensure that the modules are available in the JOBLIB or LNKLST concatenation:

Load modules for executing Log Analyzer processes

Product authorization module for Log Analyzer. This module contains the CPU authorization password that permits execution of an analysis job on a CPU. This module typically is located in the same library as Log Analyzer load modules. For information about valid passwords, see CPU authorization passwords for Log Analyzer.
Load modules for executing product authorization processes. These load modules are distributed in FMID BBAPW32 and typically are located in the BBLINK library after installation.
Load modules for executing the standard BMC application programming interface (API) for DBRC Log Analyzer calls these load modules, including module BMCDBRC0, during analysis jobs that access the IMS RECON (when the ANALYZE statement includes the RECON keyword). These load modules are distributed in FMID XICO120 and typically are located in the ICOLIB library after a non-merged installation or in the IMLIB library after a merged installation.
IMS dynamic allocation (MDA) members for allocating RECON data sets. These members are required if you want Log Analyzer to discover and allocate RECON data sets automatically. Otherwise, they are optional.

SYSMDUMP DD statement

You can provide a SYSMDUMP DD statement to define a standard SYSMDUMP data set.

SYSOUT DD statement

Provide a SYSOUT DD statement to contain an 'echo' of the control statements that are used to execute the job and any error and informational messages that are issued during processing. This statement is usually specified to allocate a SYSOUT=* data set.

Important

If you have requested a batch report by specifying a keyword on the REPORTS control statement, Log Analyzer writes the report to a dynamically allocated output data set. The ddname of this data set is the same as the keyword.

LUITRACE DD statement

At the request of BMC Customer Support, provide an LUITRACE DD statement to contain trace data from the Log Analyzer job. This statement is usually specified as a SYSOUT=* data set. If this statement is present, the Log Analyzer job can generate a potentially large amount of output.

SYSIN DD statement

Provide a SYSIN DD statement to contain statements that control the Log Analyzer job.

You can specify this statement to specify an in-stream data set (SYSIN DD *), a standalone sequential data set, or a member of a partitioned data set. If you allocate the data set to DASD, the record format (RECFM) must be fixed blocked (FB), and the logical record length (LRECL) must be 80 bytes.

For information about how to specify control statements in the SYSIN data set, see Specifying control statements.