You are here: Job and Form Set Rules Reference > JDT Rules Reference > ErrorHandler

ErrorHandler

Use this job level rule to send transactions to the manual batch when specified field errors occur. This lets normal processing continue if errors occur.

Syntax

;ErrorHandler;;;

Use the following INI option to identify the field errors which cause a transaction to be sent to the manual batch:

< Error2Manual >

(CurrentError) = (NextError1),..,(NextErrorN),(M)

Parameter	Description
CurrentError	The error that just occurred.
NextError1	The error caused by the CurrentError failure. This continues through the list of errors until the last one.
M	This tells the system to send the transaction to the manual batch.

Errors

Here is a sample set of error messages which would appear if a field error occurred:

Error	Description
DM10513	Error in SetAddr(): Empty RuleParms for SetAddr.
DM12051	Error in RPProcessOneField(): Unable to <SETADDR>().
DM12048	Error in RPProcessFields(): Unable to RPProcessOneField(pRPS) <ADDR3>. Processing will NOT continue for image <q1addr>. See INI group:< GenDataStopOn > option: FieldErrors.
DM12083	Error in RPProcessOneImage(): Unable to RPProcessFields(pRPS).
DM12074	Error in RPProcessImages(): Unable to RPProcessOneImage(pRPS) <q1addr>. Skipping the rest of the Images for this form. See INI group:< GenDataStopOn > option:ImageErrors.

Example

Here is an example of the FSISYS.INI file:

< Error2Manual >

10513 = 12051, 12048, 12083, 12074

< GenDataStopOn >

FieldErrors = No

Add this rule to the < Base Rules > section in the AFGJOB.JDT file:

;ErrorHandler;;;

If field error DM10513 occurs, it will cause these errors: DM12051, DM12048, DM1283, and DM12074. This function sends these transactions to the manual batch for user-entry, continues processing, and then creates a blank field in the NAFILE.DAT file.

Open table of contents