30.01.2015 Views

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MESSAGES AND CODES<br />

MESSAGES FROM <strong>FDR</strong>, DSF, AND ABR (<strong>FDR</strong>NNN) 100.3<br />

<strong>FDR</strong>557 operand/OFFSET DO NOT CORRESPOND--SUBCOMMAND IGNORED<br />

Reason: The user specified an unequal number of “operand” and OFFSET operands.<br />

Action: Correct the error and resubmit the job.<br />

<strong>FDR</strong>558<br />

Reason:<br />

Action:<br />

FIELD NAME fieldname NOT ELIGIBLE AS SORT CONTROL -- SUBCOMMAND IGNORED<br />

“fieldname” cannot be used as a sort field.<br />

Remove the offending field name from the sort field selection list and resubmit the job.<br />

<strong>FDR</strong>559 FIELD NAME fieldname reason<br />

Reason: “fieldname” was not properly specified for “reason”. In most cases, the field name is<br />

ignored but the program continues.<br />

Action: Remove the offending field name from the report field selection list and resubmit the job.<br />

<strong>FDR</strong>560<br />

Reason:<br />

<strong>FDR</strong>561<br />

Action:<br />

Reason:<br />

Action:<br />

INPUT ARCHIVE OPEN/VALIDATION ERRORS--MERGE SUBCOMMAND CANCELLED<br />

While opening input files for an Archive Control File MERGE, <strong>FDR</strong>ARCH discovered<br />

errors either opening or validating the names or contents of one or more of the input<br />

ARCHIVE files. Other messages define the exact errors.<br />

See the action for the other error messages.<br />

FIELD NAME fieldname REJECTED FOR SORT/BREAK - MULTIPLE RECORD<br />

FORMATS NOT PERMITTED.<br />

“fieldname” was rejected on a SORT or BREAK statement because it comes from a<br />

different source than other field names already specified.<br />

Correct the error and resubmit the job.<br />

<strong>FDR</strong>562 FIELD NAME ffffffff IS AN UNDEFINED USER FIELD – SUBCOMMAND IGNORED<br />

Reason: <strong>FDR</strong>EPORT has nine pre-defined user fields that must be activated and redefined prior<br />

to use. This field has not been activated.<br />

Action: Display the HELP for the ACTIVATE command using this control statement:<br />

HELP CO(ACTIVATE).<br />

<strong>FDR</strong>563<br />

Reason:<br />

Action:<br />

<strong>FDR</strong>564<br />

Reason:<br />

RECORDS VALUE OF nnnnnnn EXCEEDS CALCULATED MAXIMUM VALUE OF nnnnnnnn<br />

The value specified for RECS= is too large. It is followed by message <strong>FDR</strong>564.<br />

Reduce RECS= and rerun.<br />

VARIABLES ARE: DEVICE=uuuuuuu BLOCKING FACTOR=n RECORDS PER<br />

BLOCK=nnnnn<br />

These are the variables that go into the calculated maximum RECS= displayed in the<br />

<strong>FDR</strong>563 message.<br />

<strong>FDR</strong>567 OBSOLETE OPERAND operand SPECIFIED--CONVERTED TO newoperand<br />

Reason: User specified “operand” that is obsolete. Rather than bypass the command, the<br />

operand was converted internally to a currently supported operand “newoperand” that<br />

performs the same function.<br />

Action: For future use, you should convert the job to use the new operand.<br />

<strong>FDR</strong>568 REQUIRED OPERAND operand MISSING -- status<br />

NO OPERANDS SPECIFIED FOR operand COMMAND -- status<br />

Reason: “operand” is required but was not provided (it may list more than one operand). “status”<br />

lists the action taken. If “status” ends in “IGNORED”, then it identifies another operand<br />

that was ignored. If it ends in “ASSUMED”, it displays assumed defaults.<br />

Action: If necessary, correct the statement and resubmit the job.<br />

CHAPTER 100 – PAGE 100-100 –

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!