30.01.2015 Views

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MESSAGES AND CODES<br />

<strong>FDR</strong>REORG MESSAGES (<strong>FDR</strong>RNN & <strong>FDR</strong>SNN) 100.7<br />

<strong>FDR</strong>R88** NON-GDGBASE CATALOG ENTRY EXISTS FOR DSN=dsname<br />

Reason: BACKUP=GDG was specified and the name generated by <strong>FDR</strong>REORG for the base<br />

Generation <strong>Data</strong> Group (GDG) is already in the catalog and is not a base Generation<br />

<strong>Data</strong> Group (GDG).<br />

Action: Remove the non-GDG entry from the catalog or use a different BACKUPGROUP or<br />

BACKUPINDEX.<br />

<strong>FDR</strong>R89** UNABLE TO DEFINE GDG-BASE -- R15=ccc, REASON IGG0CLxx rrr,DSN=dsname<br />

Reason: BACKUP=GDG was specified and an attempt to define the base Generation <strong>Data</strong><br />

Group (GDG) has failed. “ccc” is the catalog return code, “rrr” is the catalog reason<br />

code and IGG0CLxx is the IBM module reporting the error. The codes are<br />

documented under message IDC3009I in IBM message manuals.<br />

Action: Contact INNOVATION DATA PROCESSING for assistance.<br />

<strong>FDR</strong>R90** BACKUP DATA SET ALREADY CATALOGED -- DSN=dsname<br />

Reason: BACKUP=TEMP or BACKUP=PERM was specified and the backup data set name<br />

generated by <strong>FDR</strong>REORG is already cataloged.<br />

Action: Delete the catalog entry or use a different BACKUPGROUP or BACKUPINDEX.<br />

<strong>FDR</strong>R91** CATALOG ENTRY TYPE FOR LAST TAPE DSN IS NOT NON-VSAM -- DSN=dsname<br />

Reason: LASTAPE was specified but the catalog entry for the LASTAPE name was marked as<br />

VSAM.<br />

Action: After verifying that a data set name conflict does not exist between <strong>FDR</strong>REORG’s LASTAPE<br />

data set name and a valid data set on your system, delete the existing catalog entry.<br />

Contact INNOVATION DATA PROCESSING for assistance if necessary.<br />

<strong>FDR</strong>R92**<br />

Reason:<br />

Action:<br />

ERROR RESTORING OWNERID AND ATTRIBUTES -- R15=ccc, REASON IGG0CLxx<br />

rrr DSN=dsname<br />

A catalog error occurred while <strong>FDR</strong>REORG was attempting to restore the original<br />

OWNERID and attributes of a VSAM data set. “ccc” is the catalog return code, “rrr” is<br />

the catalog reason code, and IGG0CLxx is the IBM module reporting the error. The<br />

codes are documented under message IDC3009I in IBM message manuals.<br />

Contact INNOVATION DATA PROCESSING for assistance.<br />

<strong>FDR</strong>R93** ERROR EXTRACTING DYNALLOC MESSAGES -- R15=ccc<br />

Reason: A dynamic allocation error has occurred and an attempt to use the dynamic allocation<br />

error message interface has failed. “ccc” is the return code from the dynamic<br />

allocation message interface.<br />

Action: Contact INNOVATION DATA PROCESSING for assistance.<br />

<strong>FDR</strong>R94**<br />

Reason:<br />

Action:<br />

UNABLE TO ALLOCATE type DATA SET-COMP=cc,CODE=rrrr,INFO=iiii,DSN=dsname<br />

A dynamic allocation error has occurred while attempting to allocate data set “dsname”.<br />

“type” may be TARGET, INDEX, or BACKUP. “cc” is the dynamic allocation return<br />

code, “rrrr” is the reason code and “iiii” is the information code, all in hex.<br />

Refer to the IKJ message(s) that follows this message.<br />

<strong>FDR</strong>R96** UNABLE TO ALLOCATE VOLUME -- COMP=cc,CODE=rrrr,INFO=iiii,VOL=vvvvvv<br />

Reason: A dynamic allocation error has occurred while attempting to allocate volume “vvvvvv”.<br />

“cc” is the dynamic allocation return code, “rrrr” is the reason code and “iiii” is the<br />

information code, all in hex.<br />

Action: Refer to the IKJ message(s) that follows this message.<br />

CHAPTER 100 – PAGE 100-153 –

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

Saved successfully!

Ooh no, something went wrong!