Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Log Master for Db2 13.1.

Running Log Master jobs


To run a 

Log Master

 batch job, use the same procedures that you use to run standard JCL jobs.

The following table shows the requirements for running a Log Master job:

Requirement

Description

Reference

Authorization

To run a Log Master job, you must have the proper authorization.

Starting a job

Specify the module ALPMAIN on the EXEC statement of your JCL. You must also specify some required parameters and some DD statements.

Displaying the status of a job

Log Master does not require special commands or procedures to monitor a Log Master job. Use the standard operating system commands to monitor the job’s progress.

n/a

Restarting a job

You can rerun or re-execute Log Master jobs, but you cannot restart them.

Log Master supports a type of processing referred to as ongoing processing. Use this type of job to repeatedly run the same set of log processing. Log Master saves information about each run of the job in the Repository, and succeeding jobs can begin processing where the previous job ended. Log Master supports the RERUN and USE keywords to re-execute previous runs of ongoing jobs.

See the ONGOING HANDLE handleID entry in LOGSCAN-statement

Terminating a job

Log Master does not require special commands or procedures to terminate a Log Master job. Use the standard operating system commands to cancel the job if necessary.

n/a


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*