REP5ALL activates KSL program REPLOGAL. This program prints all the log messages for a specified date. The report’s output indicates which jobs did not yet execute.

The following code shows an example of a KSL Log Report:

//STEP1 EXEC CTMRKSL

TRACE OFF

MAXCOMMAND999999

CALLMEM  REPLGMSG  FROMDATE  TODATE   JOB511I NULL  NULL  NULL

END

//STEP2 EXEC CTMRKSL

TRACE OFF

MAXCOMMAND999999

CALLMEM  REPLGMSG  FROMDATE  TODATE   CTM659I FRM467I SEL208I  NULL

END

REP5MSGD activates KSL program REPLGMSG. This program prints only relevant log messages for a specific time span. A maximum of four messages can be specified as input parameters. This report must be generate in two steps.

In the STEP1 and STEP2 set the following parameters:

• FROMDATE – Date from which data is extracted, in format (ddmmyy or mmddyy) used at your site.
• TODATE – Date to which data is still relevant, in format (ddmmyy or mmddyy) used at your site.

The most practical value for parameter FROM DATE depends on the value of parameter MAXWAIT (for example, if most production jobs do not have a MAXWAIT parameter of more than seven days, parameter FROMDATE must not exceed seven days),

STEP1 prints a list of all the jobs placed on the Active Jobs file (message: JOB511).

STEP2 prints a list of all the jobs that ended OK, were discarded (MAXWAIT exceeded), were held, or were deleted by online users.

By manually combining these two reports, an accurate list of all jobs that must be scheduled and executed can be compiled. This method is complex, error prone, and does not determine the exact order of scheduling.Use this method only if there is no alternative (that is, no other way exists to restore the Active Jobs file).

REP5EXP activates KSL program REPLOGEX. This program can help trace problematic jobs (for example, jobs ending in abends, and so on). Priorities can then be better defined and reasonable throughput maintained.