FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
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>298 REQUIRED PARM parmname MISSING<br />
Reason: A required parameter was not found on a control statement.<br />
Action: Supply the missing parameter.<br />
<strong>FDR</strong>299 VOLUME vvvvvv NOT FOUND<br />
Reason: Volume “vvvvvv” specified in the VOL= parameter was not mounted.<br />
Action: Specify the correct volume and rerun the job.<br />
<strong>FDR</strong>301 program/function -- VER v.r/mmt -- INNOVATION DATA PROCESSING<br />
DATE=yyyy.ddd PAGE nnn<br />
Reason: This is the ABR page heading. See message <strong>FDR</strong>001 for details.<br />
<strong>FDR</strong>302<br />
Reason:<br />
CONTROL STATEMENT ERROR NEAR REL LOCATION nn -- REASON x -- JOB TERMINATED<br />
An error was encountered during the processing of a user-supplied control statement. If<br />
“NEAR REL LOCATION nn” appears, the keyword or operand causing the error is at<br />
or near column “nn” on the input statement.<br />
The error is defined by the reason code within the message. The failing statement is<br />
displayed immediately above.<br />
NOTE: The expression “SELECT statement” in the reason codes below refers to SELECT<br />
and EXCLUDE statements. For <strong>FDR</strong>ABR, it also refers to MOUNT, PROFILE,<br />
PROTECT, and ALLOCATE statements.<br />
The reason “x” can be:<br />
1 – A SELECT statement did not specify any operands. Control statement was<br />
blank after the command name.<br />
2 – Command name on the first control statement was incorrectly specified. For<br />
example, <strong>FDR</strong>DSF must start with a DUMP, RESTORE, or PRINT statement.<br />
See the section in this manual for the program you are executing for details.<br />
3 – Operand on the first control statement was incorrectly specified. (Valid<br />
operands are TYPE=DSF, RESERVE, etc.).<br />
4 – Operand did not end with a blank or comma.<br />
5 – SYSIN data set was empty.<br />
6 – Expected continuation statement was not found. The previous statement<br />
ended with a comma and a blank.<br />
7 – On the first control statement, invalid or incompatible operands were<br />
specified. (Examples: RESERVE was specified but TYPE= was omitted, or<br />
FROM/TO was specified and TYPE= followed it.)<br />
7 – The TYPE= operand was omitted on a command that requires it (such as<br />
PRINT or COPY).<br />
7 – A control statement after the first was not a SELECT statement. A SELECT<br />
statement contained an invalid keyword. (Valid keywords are DSN=, VOL=, etc.).<br />
8 – An operand on a SELECT statement specified a blank or comma after the equal sign.<br />
9 – On the control statement printed above, one of the options exceeded its<br />
maximum length. A data set name exceeded 44 characters. A volume serial<br />
number exceeded 6 characters. The TAPEDD= option exceeded one (1)<br />
character. The NOTIFY operand exceeded seven (7) characters. The DD=<br />
or NEWDD= operand exceeded eight (8) characters.<br />
B –<br />
C –<br />
D –<br />
E –<br />
The DD= or NEWDD= operand specified a DDname that did not appear in the JCL.<br />
Maximum number of SELECT statements was exceeded. The number of<br />
SELECT statements plus the number of commands in the PROTECT<br />
and/or ALLOCATE list was greater than the value specified in the<br />
MAXCARDS operand (default of 100 for ABR or 250 for <strong>FDR</strong>DSF).<br />
ADATE= operand did not specify numeric data.<br />
ADATE= operand is neither five digits (yyddd) nor seven digits (yyyyddd).<br />
CHAPTER 100 – PAGE 100-57 –
Change language