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-85 –<br />

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

<strong>FDR</strong>426 PROCESSING OF VOLUME vvvvvv COMPLETED<br />

Reason: The program has successfully completed processing for the disk volume “vvvvvv”.<br />

<strong>FDR</strong>427 WARNING ARCHIVE FILE SEARCH TERMINATED AT DATE=yyyy.ddd<br />

Reason: SDATE or SDAYS was specified on the PRINT ARCHIVE control statement. ABR has<br />

terminated the search at this archival date. If data sets were archived prior to this date<br />

they are not selected.<br />

<strong>FDR</strong>428<br />

Reason:<br />

Action:<br />

WARNING ONLY nn% OF ARCHIVE CONTROL FILE FREE--REORGANIZATION NEEDED<br />

During an Archive report, <strong>FDR</strong>ABRP or <strong>FDR</strong>EPORT detected that the Archive Control<br />

File is becoming full. The default value for the threshold of free space below that this<br />

message is produced is 10% of the file.<br />

Caution! Reorganize and/or enlarge the Archive control data set with <strong>FDR</strong>ARCH<br />

(Section 51.50 “Archive Maintenance Utility (<strong>FDR</strong>ARCH)”). You may change the<br />

threshold of free space below that this message is produced by using the REORG%<br />

operand of the PRINT ARCHIVE command.<br />

<strong>FDR</strong>429 WARNING nn DAYS SINCE VOLUME=vvvvvv PROCESSED BY ABR<br />

Reason: During a backup report, <strong>FDR</strong>ABRP or <strong>FDR</strong>EPORT detected that the disk volume<br />

“vvvvvv” has not been processed by ABR volume backups for “nn” days. The operand<br />

BKDAYS= specifies the period that invokes the message (default is 7 days). This<br />

message can occur for volumes that have been deleted from your system or are no<br />

longer being backed up by ABR.<br />

Action: If this message is unexpected, you should investigate why the volume is not included in your<br />

regular backups. You should probably arrange for a full-volume backup or incremental<br />

backup of the volume to be taken soon. If your full-volume backups are taken at intervals<br />

of more than one week, increase the values of BKDAYS=. For volumes that are no longer<br />

required to be backed up by ABR, the PURGE BACKUP command of program<br />

<strong>FDR</strong>ABRCM (see Section 50.53 “<strong>FDR</strong>ABRCM PURGE BACKUP Statement”) can be used<br />

to delete the entries from the ABR catalog.<br />

<strong>FDR</strong>430<br />

Reason:<br />

description--DSN=dsname<br />

User requested that a VSAM cluster to be marked (RESET) for archive or backup<br />

processing. Message is issued in two (2) lines. The first line of the message identifies the<br />

cluster name (ICF CLUSTER NAME) and the second line of the message identifies the<br />

name of the component that is marked as requested (MARKING COMPONENT).<br />

<strong>FDR</strong>433 MEMORY SPACE REQUEST FAILED BYTES REQUESTED--nnnnnnnn<br />

Reason: While processing VSAM records from the Archive file, a table of size “nnnnnnn” (bytes,<br />

in hex) was required but the GETMAIN for it failed.<br />

Action: Increase region size and rerun.<br />

<strong>FDR</strong>435 FILTER ERROR REASON=reason -- ENTRY=entry<br />

Reason: <strong>FDR</strong>$CATP, the Catalog Read Service used by <strong>FDR</strong>EPORT and other ABR programs,<br />

was invoked to extract information from the system catalogs, and an error occurred.<br />

“entry” indicates the catalog name or the catalog entry on which the error occurred.<br />

“reason” indicates the error:<br />

1 NO CATALOGED ENTRIES FOUND – The argument that was used failed<br />

to select any entries from the catalogs.<br />

2 CATALOG NOT FOUND BY OBTAIN – An OBTAIN SVC was issued to<br />

insure that a catalog was on a volume prior to allocation. The OBTAIN failed.<br />

5 USER REQUESTED BYPASS – The user requested that this catalog not<br />

be processed.<br />

7 REQUESTED ALIAS NOT FOUND – The alias requested was not found in<br />

the system alias table.

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

Saved successfully!

Ooh no, something went wrong!