EOJ Report

CA Endevor/DB produces an End-of-Job (EOJ) report every time it is run. This report describes the commands that were entered and whether the commands were performed or failed.

The EOJ Report records every type of command (for example, ADD ENTITY, MODIFY ENTITY, and so on) that was entered for this particular batch job. Each line of the report reflects the number of commands read, per type, and the number of commands within that type that failed processing. Note the following EOJ report, which was produced for a test batch run.

COMMAND        READ    FAILED

ADD    CCID    0000005 0000001
MODIFY ENTITY  0000004 0000001
ADD    USER    0000001 0000000
SIGNOUT        0000001 0000000
UNKNOWN        0000001 0000001

TOTAL          0000012 0000003

NDVRMISB: EO99 PROCESSING TERMINATED WITH ERRORS

Each line reflects the command type, number of records read for the command type, and number of records for the command type which failed. Statistics are produced only for those command types which are processed. In the top line of the report, for example, you can see that CA Endevor/DB read 5 ADD CCID command records and that one of them failed. This means that only four ADD CCID commands were processed in the batch run. Similarly, looking at the second line, you can see that CA Endevor/DB read 4 MODIFY ENTITY commands and one of them failed. In this case, only three MODIFY ENTITY commands were processed. If there are no failures, the FAILED values will be all zeroes.

Note that the UNKNOWN command line lists the number of commands received that CA Endevor/DB could not identify. The parser looks for certain 'key' words when recording each command. If the parser does not recognize a command, for whatever reason (such as a misspelling), the information is recorded as an UNKNOWN command and is considered failed.

The total number of commands read and failed appears at the end of the report.