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 />

CHAPTER 100 – PAGE 100-105 –<br />

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

<strong>FDR</strong>616 <strong>FDR</strong>ARCH ABNORMALLY TERMINATED. COMP CODE=Ssss Uuuuu<br />

Reason: <strong>FDR</strong>TCOPY invoked <strong>FDR</strong>ARCH to update the Archive Control File with information<br />

about copied Archive Backups, but <strong>FDR</strong>ARCH abnormally terminated. The<br />

termination code is either system ABEND “sss” or user ABEND/return “uuuu”.<br />

Action: Examine <strong>FDR</strong>ARCH messages on SYSPRINT to determine the cause. The Archive<br />

Control File update may have been partially or totally bypassed. If possible, correct<br />

the problem and re-execute the <strong>FDR</strong>TCOPY job. If not, contact INNOVATION DATA<br />

PROCESSING for technical assistance.<br />

U0012 indicates that <strong>FDR</strong>ARCH terminated with return code 12 due to some error; look<br />

for preceding <strong>FDR</strong>ARCH error messages.<br />

<strong>FDR</strong>618 PROCESSING VOLUME vvvvvv AS status<br />

Reason: <strong>FDR</strong>EPORT tried to bring the used portion of a VVDS into storage to satisfy VSAM<br />

report requests, but is unable to read the VVDS. An <strong>FDR</strong>63x message documenting<br />

the cause precedes this message.<br />

Action: If “status” is ICF=IGNORE, the VVDS is unusable and VSAM components are processed as<br />

if they were non-VSAM data sets. This may indicate a serious problem with this volume.<br />

If “status” is ICFSOURCE=LOCATE, catalog LOCATEs are used to get information on<br />

VSAM components and clusters instead of reading the VVDS directly. If no other<br />

errors occur, <strong>FDR</strong>EPORT runs successfully, but it runs longer.<br />

<strong>FDR</strong>619 MODULE c...c TOO LARGE TO PROCESS-SYSLIB=d...d<br />

Reason: <strong>FDR</strong>ZAPOP attempted to read the module c...c in the data set d...d referenced by<br />

SYSLIB. The module was required to support all processing functions but, due to the<br />

size of the module (or previously read modules), not enough buffer storage was<br />

available to complete the read. Because of user expansion of the protect, allocation,<br />

and/or unmovable tables, the storage buffer used by <strong>FDR</strong>ZAPOP to store tables has<br />

been exceeded.<br />

Action: Contact INNOVATION DATA PROCESSING for assistance in expanding the storage<br />

buffer used by <strong>FDR</strong>ZAPOP.<br />

<strong>FDR</strong>620 statement error<br />

Reason: In <strong>FDR</strong>TSEL, “statement” was in error. “error” can be COMMAND MISSING OR<br />

INVALID or COMMAND PREVIOUSLY SPECIFIED.<br />

Action: Correct the error and re-execute.<br />

<strong>FDR</strong>621<br />

Reason:<br />

<strong>FDR</strong>622<br />

Action:<br />

Reason:<br />

Action:<br />

SELECT COMMAND FUNCTION MISSING. MUST SPECIFY ARCHIVE, ARCEDIT, OR<br />

CATLG<br />

In <strong>FDR</strong>TSEL, the SELECT statement does not contain one of the required operands<br />

ARCHIVE, ARCEDIT, or CATLG.<br />

Correct the error and re-execute.<br />

SELECT COMMAND COPY= OR IFONLYCOPY= KEYWORD IS MISSING OR<br />

MISSPELLED<br />

In <strong>FDR</strong>TSEL, the SELECT statement does not contain one of the required COPY= or<br />

IFONLYCOPY= operands.<br />

Correct the error and re-execute.<br />

<strong>FDR</strong>623 REASON=reason<br />

Reason: This message documents various errors that prevent <strong>FDR</strong>TSEL from completing.<br />

“reason” may be:<br />

A operand IS INVALID WHEN SELECT COMMAND IS PRESENT – The<br />

indicated operand of the COPY or MOVE statement is invalid with a<br />

SELECT statement.

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

Saved successfully!

Ooh no, something went wrong!