In many instances, a job will produce exception messages inside a report, indicating that there are processing errors, but will not actually fail the job. Normally, these exceptions will not be noticed until the following day, when users receive reports or try to use online systems. This often means that the previous night's work must be redone, and that online systems are unavailable for users while corrective measures are being taken.
If other INCONTROL products are operational at your site, you can take advantage of their integrated architecture to perform some of the following actions, based on exception messages appearing in reports:
Assign a Remark to a Report
You can assign a remark to a report based on the appearance of a particular string, using parameter DO REMARK. The remark can be up to sixteen characters in length, and can be displayed in the Online Viewing facility and printed on the user's report.
ON CLASS = T EXTWTR DEST FORM
PRT COPIES LVL USER DEST MAX COPIES
PRINT/CDAM PARMS =
WHEN LINE 00003 - 00003 COL 00010 - 00032 PRINT REF NXT CT AND/OR
STRING = GENERAL LEDGER REPORT
DO USER = DVACP LVL LINE COL - S T
SYNONYM = CONCAT =
DO NAME = GEN LEDGE REP LINE COL
DO
WHEN LINE 00040 - 00040 COL 00032 - 00042 PRINT REF NXT CT AND/OR
STRING = UNBALANCED
DO USER = DVAC LVL LINE COL - S T
SYNONYM = CONCAT =
DO NAME = GEN LEDGE REP
DO REMARK = UNBAL
DO
In the above example, recipient DVACP receives the General Ledger report on a daily basis. If the string UNBALANCED appears in any pages in the specified location, a copy of those pages is allocated as a report to recipient DVAC, for analysis. The report is also assigned the remark UNBAL, which can be displayed online, attracting the user's attention to the exception report.
Parent Topic |