This chapter lists messages preceded by the characters CAG.
This section contains the following topics:
The CAG error messages follow.
Reason:
The load program has detected a field error in the record to be added, in field l xxx xxx. This error can occur when adding any type record.
For fields that do not require a value, blanks are acceptable as field input for numeric or alphanumeric fields. If numeric, the field must be completely blank.
A field error occurs when:
Action:
Correct the field value. Examples of field errors follow.
|
Field |
Record Type |
Specific Error |
|---|---|---|
|
REPORT NAME |
1 or 3 |
First character of REPORT NAME is neither alphabetic nor a special character. |
|
PAGE DEFN FLAG |
4 |
FLAG is not valid. Valid values are blank, Y, S, and E. |
|
PAGE DEFN LINE |
4 |
LINE is not valid. The field must be numeric. |
|
PAGE DEFN COL |
4 |
COLUMN is not valid. The field must be numeric. |
|
PAGE DEFN TEST |
4 |
TEST is not valid. Valid values are EQ, GT, GE, NE, LT, and LE. |
|
PAGES MAILDROP MAX |
5 |
MAX NUMBER OF PAGES is not valid. The field must be numeric. This field is required to add a MAILDROP record. |
|
TIME |
5 |
MAX TIME is not valid. The field must be numeric. This field is required to add a MAILDROP record. |
|
JDE ID |
7 |
JDE ID field is blank. This is a required field. |
Reason:
Occurs when adding record Type 1. The REPORT NAME and JOBNAME combination already exists on the database. Duplicates are not allowed.
Action:
Check the fields and enter the correct values.
Reason:
Occurs when adding record Type 2. The RECIPIENT already exists on the database. Duplicates are not allowed.
Action:
Check the field and enter the correct value.
Reason:
Occurs when adding record Type 3. The prerequisite REPORT and JOB NAME base record Type 1 is not on the database.
Action:
Add the Type 1 record to the database.
Reason:
Occurs when adding record Type 3. The prerequisite RECIPIENT base record Type 2 is not on the database.
Action:
Add the Type 2 record to the database.
Reason:
Occurs when adding record Type 4. The prerequisite RECIPIENT base record Type 2 is not on the database.
Action:
Add the Type 2 record to the database.
Reason:
Occurs when adding record Type 5. The prerequisite REPORT RECIPIENT record Type 3 is not on the database.
Action:
Add the Type 3 record to the database.
Reason:
Occurs when adding record Type 5. This MAILDROP record already exists on the database. Duplicates are not allowed.
Action:
Check the field and enter the correct value.
Reason:
Occurs when adding record Type 7. The prerequisite RECIPIENT base record Type 2 is not on the database.
Action:
Add the Type 2 record to the database.
Reason:
Occurs when adding record Type 7. The prerequisite REPORT RECIPIENT records Type 3 is not on the database.
Action:
Add the Type 3 record to the database.
Reason:
Occurs when adding record Types 8 or 9. The prerequisite RECIPIENT base record Type 2 is not on the database.
Action:
Add the Type 2 record to the database.
Reason:
Occurs when adding record Types 8 or 9. The prerequisite REPORT RECIPIENT record Type 3 is not on the database.
Action:
Add the Type 3 record to the database.
Reason:
Occurs when adding record Types 8 or 9. The prerequisite DJDE record Type 7 is not on the database.
Action:
Add the Type 7 record to the database.
Reason:
Occurs when adding record Type 6. The prerequisite MAILDROP record Type 5 is not on the database.
Action:
Add the Type 5 record to the database.
Reason:
Occurs when adding record Types 5 or 6. The SYSGEN required after database initialization was not performed.
Action:
See the CA Dispatch Reference Guide.
Reason:
Occurs when the Type field (position 1) does not contain a valid value.
Action:
Use a valid value for Type.
Reason:
Occurs when adding record Type 3. REPORT RECIPIENT record to be added already exists on the database. Since the DUPLICATE FLAG value is not Y on the input record, the record cannot be loaded (user choice).
Action:
None.
Reason:
Occurs when adding record Type 7. The REPORT RECIPIENT already has DJDE characteristics. A DJDE record cannot be added.
Action:
Check the fields and enter the correct values.
Reason:
Occurs when adding record Type 8. The REPORT RECIPIENT already has DJDE extension characteristics. A DJDE extension record cannot be added.
Action:
Check the fields and enter the correct values.
Reason:
Occurs when adding record Type 9. The prerequisite DJDE extension record Type 8 is not on the database.
Action:
Add the Type 8 record to the database.
Reason:
Occurs when adding record Type 4. The prerequisite BASE REPORT record Type 1 is not on the database.
Action:
Add the Type 1 record to the database.
Reason:
Occurs when adding record Type 7. The prerequisite BASE REPORT record Type 1 is not on the database.
Action:
Add the Type 1 record to the database.
Reason:
Occurs when adding record Type 8 or 9. The prerequisite BASE REPORT record Type 1 is not on the database.
Action:
Add the Type 1 record to the database.
Reason:
Occurs when modifying any record with l xxxx xxxx as the record name. The target record specified in the input record was not found.
Action:
Check the validity of the modification record.
Reason:
Occurs when unloading any record with l xxxx xxxx as the record name. The target record or mask specification in the input record was not found on the database.
Action:
Check the validity of the unload record.
Reason:
Occurs when deleting any record with l xxxx xxxx as the record name. The target record or mask specification in the input record was not found on the database.
Action:
Check the validity of the delete record.
Reason:
Occurs when the function field (position 1) does not contain a valid value.
Action:
Check the validity of position 1 of the record.
Reason:
Occurs when a Type C record (report message definition, part 2) is encountered that does not immediately follow its corresponding Type B record (part 1).
Action:
Enter the co-requisite records together.
Reason:
Occurs when a Type E record (SYSGEN message definition, part 2) is encountered that does not immediately follow its corresponding Type D record (part 1).
Action:
Enter the co-requisite records together.
Reason:
Occurs when a sequence number is not the next number in sequence for a duplicated recipient in a report/job definition. Example: Two recipients exist and an attempt is made to add number 4. Number 3 must be added next.
Action:
Correct the invalid field (report, job, recipient or sequence number).
Reason:
Occurs when adding record Type J. This ARCH REPORT DEFINITION record already exists on the database. Duplicates are not allowed.
Action:
Check the fields and enter the correct values.
Reason:
Occurs when deleting record Type J. This ARCH REPORT DEFINITION record cannot be deleted because individual archive report entries for the base definition still exist on the database.
Action:
Check the fields and enter the correct values.
Reason:
Occurs when adding record Types K, L or M. The prerequisite RECIPIENT base record Type 2 is not on the database.
Action:
Add the Type 2 record to the database.
Reason:
Occurs when adding record Types K, L or M. The prerequisite REPORT RECIPIENT record Type 3 is not on the database.
Action:
Add the Type 3 record to the database.
Reason:
Occurs when adding record Types K, L or M. The prerequisite DJDE record Type 7 is not on the database.
Action:
Add the Type 7 record to the database.
Reason:
Occurs when adding record Type K. The REPORT RECIPIENT already has DJDE free-form characteristics. A DJDE free-form record cannot be added.
Action:
Check the fields and enter the correct values.
Reason:
Occurs when adding record Type L or M. The prerequisite DJDE free-form record Type K is not on the database.
Action:
Add the Type K record to the database.
Reason:
Occurs when adding record Type K, L or M. The prerequisite BASE REPORT record Type 1 is not on the database.
Action:
Add the Type 1 record to the database.
|
Copyright © 2011 CA.
All rights reserved.
|
|