FDRREORG Messages (FDRRnn & FDRSnn)

FDRR00

statistics

Explanation: Provides statistics about the current FDRREORG step, such as number of volumes processed, number of data sets processed, number of PDS tracks reclaimed, and so on.

FDRR01

ALL PROCESSING INITIATED FOR VOLUME GROUP volg, VOLUMES PROCESSED=nnnn,VOLUMES EXCLUDED=nnnn, DUPLICATE VOLUMES BYPASSED=nnnn

Explanation: A SELECT statement selected an SMS storage group with STORGRP=. This message shows the volumes in that group that were processed, excluded, or duplicates of volumes already in FDRREORG's volume list.

FDRR02

PROCESSING COMPLETED FOR VOLUME vol -- CODE=cccc statistics

PROCESSING COMPLETED FOR DATA SET dsn -- CODE=cccc

Explanation: “cccc” indicates the completion code for processing on a given DASD volume or data set. Additional statistics are displayed.

FDRR04**

ALL SUBTASKS HAVE ABENDED -- PROCESSING TERMINATED

Explanation: All internal FDRREORG subtasks have abended.

Action: Refer to the FDRR03** messages that were issued for each subtask abend.

FDRR05**

STOPTIME IS LESS THAN CURRENT TIME -- PROCESSING TERMINATED

Explanation: The STOPTIME= operand specifies a time that is less than the current.

Action: Provide an acceptable STOPTIME= value and rerun the job.

FDRR06**

STOPTIME PROVIDES LESS THAN 1 MINUTE OF RUNTIME -- PROCESSING TERMINATED

Explanation: The STOPTIME= operand must allow for at least one minute of runtime.

Action: Provide an acceptable STOPTIME= value and rerun the job.

FDRR07**

VALID SELECT STATEMENT NOT FOUND -- PROCESSING TERMINATED

Explanation: A REORG or SIMULATE statement was specified without a required SELECT statement.

Action: Provide at least one SELECT statement and rerun the job.

FDRR08**

ALLDSN REQUIRED IF A DSN LIST IS NOT PROVIDED -- PROCESSING TERMINATED

Explanation: The SELECT statement did not contain either a CATDSN= or DSN= operand.

Action: To process all data sets selected by the flagged SELECT statement, include ALLDSN to indicate that this is your true intention. Otherwise, add CATDSN= or DSN=.

FDRR09**

VOLUME LIST NOT PROVIDED -- PROCESSING TERMINATED

Explanation: The VOL= operand is required unless CATDSN= is used to select data sets.

Action: Provide the VOL= operand or use CATDSN= instead of DSN=.

FDRR10*

VOLUME vol DOES NOT HAVE A VTOC -- VOLUME BYPASSED

Explanation: The volume does not have a usable VTOC.

Action: If this is not a VM volume, the indicated volume is probably damaged and needs to be restored.

FDRR11*

RUNTIME/STOPTIME REACHED -- NO NEW WORK WILL BE STARTED

Explanation: The limit specified by the user has been reached.

Action: FDRREORG completes all active processing and processes the next REORG or SIMULATE statement.

FDRR12*

OPERATOR STOP COMMAND ISSUED -- NO NEW WORK WILL BE STARTED

Explanation: The operator issued a STOP (P) command for the FDRREORG job.

Action: FDRREORG completes all active reorganizations and terminates.

FDRR13**

FDRR14**

FDRR15**

FDRR16**

UNIT NAME unit NOT DEFINED TO SYSTEM

Explanation: A unit name provided by operands such as BACKUPUNIT= is not defined in the current I/O configuration.

Action: Correct the unit name and rerun the job. If you have POOLDASD from BMC and are using undefined unit names to control pooling, change the POOLDASD option to YES in the FDRREORG option table.

FDRR17**

FDRR18**

FDRR19**

UNIT NAME unit CONTAINS INVALID DEVICE TYPES

Explanation: A unit name provided by operands such as BACKUPUNIT= contains devices that can not be used by FDRREORG.

Action: Provide a unit name that references TAPE or DASD and rerun the job.

FDRR20**

UNIT NAME unit CONTAINS A MIXTURE OF DEVICE CLASSES

Explanation: A unit name provided by operands such as BACKUPUNIT= contains a mixture of device types, such as TAPE and DASD.

Action: Provide a unit name that refers to TAPE or DASD devices, but not both, and rerun the job.

FDRR21**

FDRR22**

UNABLE TO CREATE SMS MANAGED BACKUP DATA SETS -- SMS NOT ACTIVE

Explanation: SMS is not active and the user included operands that indicated that data sets that are dynamically allocated by FDRREORG are to be managed by SMS.

Action: Activate SMS or switch to unit name allocations.

FDRR23**

FDRR24**

FDRR25**

CLASS smsclas NOT DEFINED TO SMS

Explanation: The SMS class name provided by the user is not defined to SMS.

Action: Provide a valid class name and rerun the job.

FDRR26**

NOREORG LIST INVALID IN MODULE FDRNORG

Explanation: The permanent exclude list that is defined by the NOREORG statements contained in the module FDRNORG is not in a valid format.

Action: This module must be maintained by running FDRREOZO to add and delete the NOREORG statements.

FDRR27**

INVALID HEADER IN MODULE FDRNORG

Explanation: The permanent exclude list that is defined by the NOREORG statements contained in the module FDRNORG is not in a valid format.

Action: This module must be maintained by running FDRREOZO to add and delete the NOREORG statements.

FDRR28**

FDRR29**

INVALID NOREORG LIST KEYWORDS IN MODULE FDRNORG

Explanation: The permanent exclude list that is defined by the NOREORG statements contained in the module FDRNORG is not in a valid format.

Action: This module must be maintained by running FDRREOZO to add and delete the NOREORG statements.

function STARTED DSN=dsn BKUP=bkdsname

Explanation: Indicates that the indicated FDRREORG “function” has started. This message is only issued for PDS data sets if members are actually moved. If “function” is BLDAIX, the message has BASE= basecluster in place of BKUP= bkdsn.

FDRR31

function ENDED DSN=dsn BKUP=bkdsn

Explanation: Indicates the completion of the REORG function for a data set. See message FDRR30.

FDRR32

function PROCESSING TERMINATED

Explanation: The indicated FDRREORG function has been terminated due to errors.

Action: Refer to the preceding error messages.

FDRR33**

function FAILED -- CODE=ccccc,DSN=dsn

Explanation: The indicated FDRREORG function has failed due to a system or user abend.

Action: Consult IBM manuals to identify the proper action for a system abend. Refer to ABEND-Codes for user abends issued by FDRREORG.

FDRR34*

NO DATA SETS FOUND IN CATALOG

Explanation: The CATDSN= operand was specified and no data sets matching the user specified data set names or filters were found.

Action:  If there are additional SELECT statements they are processed and the REORG or SIMULATE function is performed provided the additional SELECT statements do not encounter the same error. If this is the only SELECT statement, processing is terminated.

FDRR35**

FDRR36

DATA SET QUALIFIES FOR REORGANIZATION -- DSN=dsn

Explanation: The data set has met the requirements specified by the user for reorganization and is processed.

FDRR37**

FDRR38*

UNABLE TO PERFORM LAST TAPE PROCESSING

Explanation: Due to the error described by the preceding message, LASTAPE processing is not possible.

Action: Correct the error described by the preceding and rerun the job.

FDRR40**

VOLUME PROCESSING TERMINATED

Explanation: Due to the error described by the preceding message, volume processing is terminating.

Action: Correct the error described by the preceding and rerun the job.

FDRR41**

ENVIRONMENTAL ERRORS LIMIT REACHED

Explanation: The number of errors specified by the MAXENVERR= operand has been reached.

Action: FDRREORG completes all active work and terminates.

FDRR42**

SYSTEM ABEND LIMIT REACHED

Explanation: The number of errors specified by the MAXSYSERR= operand has been reached.

Action: FDRREORG completes all active work and terminates.

FDRR43**

FDRR44*

ALL RETRY ATTEMPTS FAILED FOR DSN=dsn

Explanation: A value other than NONE was specified for the DSNRETRY= operand and FDRREORG was unable to allocate the indicated data set before processing completed.

Action: Rerun the job when the indicated data sets are not in use by another job.

FDRR45

LASTAPE NOT REQUIRED -- NEXT FILE FOR THIS TASK WILL HAVE FILESEQ=1

Explanation: Last tape processing was requested but the next backup data set is the first data set on a new tape volume. Since a new volume is used for the next execution, a LASTAPE catalog entry is not created.

FDRR46**

FDRR47**

FDRR48**

DATA SET BYPASSED

Explanation: Due to the error indicated by the preceding message, FDRREORG has bypassed the data set.

Action: Correct the error described by the preceding and rerun the job.

FDRR49**

FDRR50**

VTOC OPEN FAILED

Explanation: An OPEN has failed for the VTOC.

Action: Refer to IBM IEC nnn message in the job log.

FDRR51**

VVDS OPEN FAILED -- R15=ccc,CODE=rrr,DSN=dsn

Explanation: An OPEN has failed for the VVDS. “ccc” is the VSAM OPEN return code and “rrr” is the reason code from the ACB. This may indicate that the VVDS is damaged.

Action: Refer to the IBM manual Macro Instructions for Data Sets for a description of the VSAM OPEN return and reason codes. You may want to run an IDCAMS DIAGNOSE on the failing VVDS.

FDRR52**

OPEN FAILED FOR TARGET DATA SET -- R15=ccc,CODE=rrr, DSN=dsn

Explanation: An OPEN has failed for cluster “dsn”. “ccc” is the VSAM OPEN return code and “rrr” is the reason code from the ACB. This may indicate that the cluster is damaged.

Action: Refer to the IBM manual “Macro Instructions for Data Sets” for a description of the VSAM OPEN return and reason codes.

FDRR53**

OPEN FAILED FOR BACKUP DATA SET -- DSN=dsn

Explanation: An OPEN has failed for the non-VSAM data set “dsn”.

Action: Refer to IBM IEC nnn message in the job log.

FDRR54**

CLOSE FAILED FOR TARGET DATA SET -- R15=ccc,CODE=rrr, DSN=dsn

Explanation: A CLOSE has failed for cluster “dsn”. “ccc” is the VSAM OPEN return code and “rrr” is the reason code from the ACB.

Action: Refer to the IBM manual Macro Instructions for Data Sets for a description of the VSAM CLOSE return and reason codes.

FDRR55**

FDRR56**

VVDS GET FAILED -- R15=ccc,CODE=rrr

Explanation: An error occurred while reading the VVDS. “ccc” is the VSAM GET return code and “rrr” is the reason code from the ACB.

Action: Refer to the IBM manual “Macro Instructions for Data Sets” for a description of the VSAM GET return and reason codes.

FDRR57**

VVDS READ FAILED -- RC=ccc,RBA=xxxxxxxx,VOL=vol, DSN=dsn

Explanation: A read request to the VVDS manager has failed. “cccc” is the catalog reason code from the VVDS manager and “xxxxxxxx” is the RBA (Relative Byte Address) of the record being read.

Action: Refer to the IBM message manual for message IDC3009I, return code 50 and reason code “cccc”.

FDRR58**

VVDS UPDATE FAILED -- RC=ccc,RBA=xxxxxxxx,VOL=vol, DSN=dsn

Explanation: An update request to the VVDS manager has failed. “cccc” is the catalog reason code from the VVDS manager and “xxxxxxxx” is the Relative Byte Address (RBA) of the record being updated.

Action: Refer to the IBM message manual for message IDC3009I, return code 50 and reason code “cccc”.

FDRR59**

UNABLE TO ALLOCATE VVDS ON VOLUME vol

Explanation: Dynamic allocation of the VVDS has failed.

Action: Refer to the dynamic allocation failure message that follows this message.

FDRR60**

DATA SET HAS MOVED FROM VOLUME vol TO VOLUME vol -- DSN=dsn

Explanation: A VSAM data set on the retry queue is not on the volume it was on when it was selected.

Action: The data set is removed from the retry queue and bypassed.

DATA SET IS NO LONGER ON VOLUME vol -- DSN=dsn

Explanation: An IAM data set or PDS on the retry queue is no longer on the indicated volume. The data set has either been moved or deleted.

Action: The data set is removed from the retry queue and bypassed.

RETRY DATA SET IS EMPTY -- DSN=dsn

Explanation: A data set on the retry queue has become available but is now empty. The indicated data set has probably been deleted and redefined.

Action: The data set is removed from the retry queue and bypassed.

VOLUMES HAVE CHANGED FOR DSN=dsne

Explanation: An IAM data set or PDS on the retry queue has become available and the first volume of the data set has changed. The indicated data set has probably been deleted and redefined.

Action: The data set is removed from the retry queue and bypassed.

DATA SET NO LONGER QUALIFIES FOR RE-ORGANIZATION -- DSN=dsn

Explanation: A data set on the retry queue has become available but no longer meets the selection criteria that caused it to be selected. The indicated data set has probably been reloaded or compressed by another job.

Action: The data set is removed from the retry queue and bypassed.

FDRR66*

DATA SET REMOVED FROM RETRY QUEUE

Explanation: Issued after an FDRR61*, FDRR62*, FDRR63*, FDRR64*, or FDRR65* message.

FDRR67**

FDRREORG WILL RETRY REORG LATER -- DSN=dsn

Explanation: A data set selected for reorganization is in use by another job and the SELECT statement that selected the data set specified a DSNRETRY= operand either RETRY, ENQ, or WAIT.

Action: The data set is added to the retry queue.

FDRR68*

MAXENQ LIMIT REACHED -- WILL ENQ LATER -- DSN=dsn

Explanation: A data set selected for reorganization is in use by another job and the SELECT statement that selected the data set specified a DSNRETRY= operand either ENQ or WAIT. An enqueue was not issued because the maximum number of outstanding enqueue’s as specified by the MAXENQ= operand have already been issued.

Action: The data set is added to the retry queue as if the RETRY option was specified. An enqueue is issued when the count of outstanding enqueue’s falls below the value specified by MAXENQ=.

FDRR69**

IAM 6.1 LEVEL 08 OR HIGHER IS EITHER INACTIVE OR NOT INSTALLED -- PROCESSING OF IAM DATA SETS DISABLED

Explanation: The DSTYPE= operand specified IAM or ALL and a data set that appeared to be an IAM data set was encountered. An attempt to obtain information about the possible IAM data set using IAM’s catalog interface indicated that IAM’s catalog interface is not active.

Action: If IAM is installed, VIF must be active and it must be IAM 6.1 Level 08 or higher to reorganize IAM data sets. If IAM is not installed, do not use DSTYPE=ALL or DSTYPE=IAM.

FDRR70**

DATA SET HAS MORE THAN 16 EXTENTS -- DSN=dsn

Explanation: The Format 1 DSCB for a partitioned data set has an extent count that exceeds 16.

Action:  The Format 1 DSCB for the indicated data set is invalid and the data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors.

FDRR71**

FORMAT 3 DSCB POINTER MISSING -- DSN=dsn

Explanation: The Format 1 DSCB for a partitioned data set indicated that the data set is in more than three extents that requires that a Format 3 DSCB exist to describe the additional extents. The Format 3 pointer in the Format 1 DSCB however is zero.

Action:  The Format 1 DSCB for the indicated data set is invalid and the data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors.

FDRR72**

ERROR READING FORMAT 3 DSCB -- R15=ccc,DSN=dsn

Explanation: An attempt was made to read the Format 3 DSCB for the indicated partitioned data set but it failed. “ccc” is the return code from the OBTAIN SVC.

Action: The Format 1 DSCB for the indicated data set is invalid or the VTOC has been damaged. The data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors.

FDRR73**

FORMAT 3 DSCB NOT RETURNED BY OBTAIN -- DSN=dsn

Explanation: An attempt was made to read the Format 3 DSCB for the indicated partitioned data set and the data return by OBTAIN was not a valid Format 3.

Action: Probable system error or VTOC damage. The data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors.

FDRR74**

MISSING EXTENT DESCRIPTORS -- DSN=dsn

Explanation: A required extent descriptor for a partitioned data set in either a Format 1 or Format 3 DSCB was null.

Action: Probable system error or VTOC damage. The data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors.

FDRR75**

EXTENTS OUT OF SEQUENCE -- DSN=dsn

Explanation: While validating a partitioned data set’s extent descriptor in the Format 1 or Format 3 DSCBs, an extent sequence number was encountered that was not in the proper sequence.

Action: Probable system error or VTOC damage. The data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors.

FDRR76**

INVALID FLAGS IN EXTENT DESCRIPTOR -- DSN=dsn

Explanation: While validating a partitioned data set’s extent descriptor in the Format 1 or Format 3 DSCBs, an invalid extent descriptor flag was encountered.

Action: Probable system error or VTOC damage. The data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors.

FDRR77**

INVALID CYLINDER/TRACK ADDRESS -- DSN=dsn

Explanation: While validating a partitioned data set’s extent descriptor in the Format 1 or Format 3 DSCBs, a cylinder or track address was encountered that is not valid for the device.

Action: Probable system error or VTOC damage. The data set is bypassed. If you are licensed for COMPAKTOR, you can run a CPK MAP on the volume to identify all VTOC errors. See message CPK512I for a possible cause of this error.

FDRR78**

FORMAT 1 DSCB MISSING FOR DSN=dsn

Explanation: The Format 1 DSCB for the indicated VSAM data component could not be found.

Action: Probable system error or VTOC damage. The data set is bypassed.

FDRR79**

FDRR80**

UNABLE TO FIND type ASSOCIATION FOR DSN=dsn

Explanation: The association list for a VSAM cluster did not contain an entry for a required component type (DATA or INDEX).

Action: Probable catalog damage. Use an IDCAMS or TSO LISTCAT statement to verify the catalog entry for the indicated cluster. You may need to execute an IDCAMS DIAGNOSE on the catalog to identify the problem.

FDRR81**

FDRR82**

FDRR83**

FDRR84**

FDRR85**

FDRR86**

FDRR87**

FDRR88**

NON-GDGBASE CATALOG ENTRY EXISTS FOR DSN=dsn

Explanation: BACKUP=GDG was specified and the name generated by FDRREORG for the base Generation Data Group (GDG) is already in the catalog and is not a base Generation Data Group (GDG).

Action: Remove the non-GDG entry from the catalog or use a different BACKUPGROUP= or BACKUPINDEX=.

FDRR89**

FDRR90**

BACKUP DATA SET ALREADY CATALOGED -- DSN=dsn

Explanation: BACKUP=TEMP or BACKUP=PERM was specified and the backup data set name generated by FDRREORG is already cataloged.

Action: Delete the catalog entry or use a different BACKUPGROUP= or BACKUPINDEX=.

FDRR91**

FDRR92**

FDRR93**

UNABLE TO ALLOCATE type DATA SET-COMP=cc,CODE=rrrr, INFO=iiii,DSN=dsn

Explanation: A dynamic allocation error has occurred while attempting to allocate data set “dsn”. “type” may be TARGET, INDEX, or BACKUP. “cc” is the dynamic allocation return code, “rrrr” is the reason code and “iiii” is the information code, all in hex.

Action: Refer to the IKJ messages that follows this message.

FDRR96**

UNABLE TO ALLOCATE VOLUME -- COMP=cc,CODE=rrrr,INFO=iiii, VOL=vol

Explanation: A dynamic allocation error has occurred while attempting to allocate volume “vol”. “ cc ” is the dynamic allocation return code, “rrrr” is the reason code and “iiii” is the information code, all in hex.

Action: Refer to the IKJ messages that follows this message.

FDRR97**

DYNAMIC DEALLOCATION ERROR -- COMP=cc,CODE=rrrr, INFO=iiii,DDNAME=ddn

Explanation: A dynamic allocation error has occurred while attempting to deallocate “ddn”. “cc” is the dynamic allocation return code, “rrrr” is the reason code, and “iiii” is the information code, all in hex.

Action: Refer to the IKJ messages that follows this message.

FDRR98**

ENQ FAILED FOR IAM DATA SET -- DSN=dsn

Explanation: FDRREORG was unable to obtain the IAMENQ for the indicated data set because it is in use by another job.

Action: The data set is bypassed.

FDRR99**

ERROR GENERATING DSNAME FOR BACKUP DATA SET

Explanation: After applying the pattern as specified by the BACKUPINDEX= operand to the target data set name, an invalid data set name was detected.

Action: The data set name generated was probably longer than 44 characters. Simplify the BACKUPINDEX= and rerun the job.

FDRS01**

FDRS02**

DATA SET NAME TOO LONG TO BE A GDG-BASE -- DSN=dsn

Explanation: BACKUP=GDG was specified and the name of the Generation Data Group (GDG) is longer than 35 characters.

Action: Alter or use the BACKUPINDEX= pattern to generate a shorter name.

FDRS03**

FDRS04**

FDRS05**

FDRS06**

UNSUPPORTED DEVICE FOR BACKUP DATA SET -- DEVICE CLASS=cc, DEVICE TYPE=tt

Explanation: The BACKUPUNIT= specified does refer to a DASD or tape device.

Action: Specify a valid BACKUPUNIT= and rerun the job.

FDRS07**

TARGET DATA SET NOT EMPTY -- DSN=dsn

Explanation: A RECOVER statement was executed and the indicated data set has already been reloaded.

Action: The data set is bypassed.

FDRS08**

RE-USE TERMINATED

Explanation: An attempt to dynamically reuse a VSAM data or index component has been terminated due to the error described by the preceding message.

Action: Refer to the preceding message.

FDRS09**

REORGCKP DD REQUIRED FOR RECOVERY -- PROCESSING TERMINATED

Explanation: A RECOVER statement was executed without the JOBNAME= operand and a REORGCKP DD statement was not found.

Action: Provide the REORGCKP DD statement. If checkpoint processing is not required, use the NOCKPT keyword.

FDRS10**

REORGLOG DD REQUIRED FOR RECOVERY -- PROCESSING TERMINATED

Explanation: A RECOVER statement was executed without the JOBNAME keyword and a REORGLOG DD statement was not found.

Action: Provide the REORGLOG DD statement. If log file processing is not required, use the NOLOG keyword.

FDRS11**

RECOVERY TERMINATED

Explanation:  A RECOVER statement has failed due to the errors described by the preceding message.

Action: Refer to the preceding message.

FDRS12**

DATA SET TYPE HAS CHANGED FROM OLD TYPE TO NEW TYPE

Explanation: A RECOVER statement was executed and the data set type has changed since FDRREORG backed up the data set.

Action: The data set is not recovered.

FDRS13**

TARGET DATA SET IS NOT A VSAM KSDS -- DSN=dsn

Explanation: A RECOVER statement was executed and a target VSAM cluster is no longer a KSDS.

Action: The data set is not recovered.

FDRS14**

TARGET DATA SET IS NOT A IAM FILE -- DSN=dsn

Explanation: A RECOVER statement was executed and an IAM data set is no longer in IAM format.

Action: The data set is not recovered.

FDRS15

type FILE ALLOCATED -- DSN=dsn

Explanation: Documents the recovery checkpoint or log data set allocated.

FDRS16**

type FILE ALLOCATED ON UNSUPPORTED DEVICE

Explanation: The device allocated for the recovery checkpoint or log data set was not DASD.

Action: Specify a unit name that refers to DASD.

FDRS17*

type FILE DOES NOT EXIST FOR THIS JOB

Explanation: A RECOVER statement was executed with the JOBNAME operand but the required checkpoint or log data set does not exist.

Action: Probably none. FDRREORG deletes the checkpoint or log file if they do not contain an entry for a data set that requires recovery.

FDRS18**

RECOVERY NOT POSSIBLE -- A VALID CHECKPOINT OR LOG FILE COULD NOT BE FOUND

Explanation: A RECOVER statement was executed with the JOBNAME operand and FDRREORG could not find a checkpoint or log data set in the catalog.

Action: Verify that the specified job name is correct.

FDRS19*

type1 FILE IS OLDER THAN type2 AND WILL NOT BE USED

Explanation: A RECOVER statement was executed with the JOBNAME keyword and FDRREORG found a checkpoint and a log file in the catalog. After inspecting the date and time stamps, FDRREORG determined that both files are not from the same job.

Action: FDRREORG uses the most current file only.

FDRS20**

RACF INFORMATION DOES NOT EXIST -- UNABLE TO SUBSTITUTE racfdata

Explanation: &RACFUID ( USER ID ) or &RACFGID ( GROUP ID ) was used with the BACKUPGROUP, BACKUPINDEX, CKPTPREFIX, LASTAPEPREFIX, or LOGPREFIX keywords and the user id or group id was missing from the ACEE control block.

Action: If you do not have a security system such as IBM RACF installed, you may be able to use this feature if you are running z/OS by providing a USER or GROUP parameter on the JOB card. If you do have a security system, then a system error has probably occurred. Have the system security administrator or system programmer check that the appropriate user and group information is being provided.

FDRS21**

type=UNIT NOT VALID -- operand IS NULL

Explanation: The operand BACKUPALLOC=UNIT, CKPTALLOC=UNIT, or LOGALLOC=UNIT requested dynamic allocation of a data set, but the associated UNIT operand (BACKUPUNIT=, CKPTUNIT=, or LOGUNIT=) was not specified and defaulted to NULL.

Action: Set a default value for the appropriate UNIT operand in the FDRREORG option table by running the FDRREOZO option table change utility, or specify a value at run time.

FDRS22**

type =SMS NOT VALID -- operand IS NULL

Explanation: The operand BACKUPALLOC=SMS, CKPTALLOC=SMS, or LOGALLOC=SMS requested dynamic allocation of an SMS-managed data set, but the associated STORCLAS operand (BACKUPSTORCLASS=, CKPTSTORCLASS=, or LOGSTORCLASS=) was not specified and defaulted to NULL.

Action: Set a default value for the appropriate STORCLAS keyword in the FDRREORG option table by running the FDRREOZO option table change utility, or specify a value at run time.

FDRS23**

BACKUPSTRING REQUIRES AN OLD AND NEW STRING -- SPECIFY BACKUPSTRING=(OLDSTR,NEWSTR)

Explanation: The BACKUPSTRING= operand was coded incorrectly.

Action: Correct the error and rerun the job.

FDRS24**

REORG OR SIMULATE COMMAND MUST PRECEED statement

Explanation: A SELECT or EXCLUDE statement was encountered before a REORG or SIMULATE statement.

Action: SELECT and EXCLUDE statements must follow a REORG or SIMULATE statement. Correct the error and rerun the job.

FDRS25**

RECOVER COMMAND NOT SUPPORTED AFTER A REORG OR SIMULATE COMMAND

Explanation: Because of the basic differences in how the checkpoint and log files are used by a REORG and RECOVER function, it is not possible to perform both functions in a single execution.

Action: Run the RECOVER function as a separate job or job step.

FDRS26**

REORG OR SIMULATE COMMAND NOT SUPPORTED AFTER A RECOVER COMMAND

Explanation: Because of the basic differences in how the checkpoint and log files are used by a REORG and RECOVER function, it is not possible to perform both functions in a single execution.

Action: Run the REORG or SIMULATE function as a separate job or job step.

FDRS27*

PDS BYPASSED DUE TO UPDATEDPDS=NO -- DSN=dsn

Explanation: The UPDATEDPDS= option was specified or defaulted to NO and a partitioned data set was selected for compression that did not have a current backup (the update indicator in the data sets Format 1 DSCB was set).

Action: The data set is bypassed.

FDRS28**

type FILE NOT ALLOCATED ON A CYLINDER BOUNDARY

Explanation: The checkpoint and log files are dynamically allocated by FDRREORG as 1 cylinder data sets. However, after dynamically allocating either file, FDRREORG detected that they were not allocated on a cylinder boundary.

Action: Because of the additional overhead required to manage these files across cylinder boundaries, FDRREORG terminates. The most probable cause for this error is a user allocation exit, or allocation control system, changing the allocation to a track allocation. You must allow the FDRREORG checkpoint and log file to be allocated as 1 cylinder data sets.

FDRS29*

CLUSTER OR AIX BYPASSED -- CAN NOT BE REUSED -- DSN=dsn

CLUSTER OR AIX CAN NOT BE REUSED BUT WILL BE BACKED UP -- DSN=dsn

Explanation: A VSAM KSDS or AIX was selected for reorganization and could not be reused. If a data set is not defined with the REUSE attribute, it can only be dynamically reused if it is a single volume data set with no related Alternate Indexes (AIXs) and not defined with keyranges. If VSAMDEFINE=IFREQ is specified or defaulted, VSAM KSDS data sets that are non-RLS and do not have RACF discrete profiles, VSAM passwords or keyranges are deleted and re-defined by FDRREORG.

Action: If the ALWAYSBACKUP option is not specified, you receive the first form of this message and the data set is bypassed. If the ALWAYSBACKUP= option is specified, the data set is backed up but not reorganized.

FDRS30*

function NOT POSSIBLE -- DATA SET IN USE -- DSN=dsn

Explanation: A partitioned data set selected for compression or simulated compression was in use by another job or user.

Action: The data set is bypassed. If PDSDISP= was specified or defaulted to OLD, then any attempt at compression or simulated compression fails if any allocations exist for the data set. If PDSDISP= was specified as SHR, then some other user has it allocated exclusive with DISP=OLD.

FDRS31*

DATA SET HAS NEVER BEEN UPDATED -- BYPASSED -- DSN=dsn

Explanation: A VSAM or IAM data set was selected for reorganization that had no adds, deletes, or updates, and the NOUPDATES= option was specified or defaulted to NO.

Action:  To avoid reorganizing data sets that do not require reorganization, the data set is bypassed.

FDRS32*

DATA SET HAS NOT BEEN LOADED -- BYPASSED -- DSN=dsn

Explanation: A VSAM or IAM data set was selected for reorganization but the data set has been defined and never loaded.

Action: The data set is bypassed.

FDRS33*

UPDATE INHIBIT FLAG IS ON -- DATA SET BYPASSED -- DSN=dsn

UPDATE INHIBIT FLAG IS ON -- DATA SET WILL BE BACKED UP ONLY -- DSN=dsn

Explanation: A VSAM data set was selected for reorganization and the data set’s update inhibit flag is on.

Action: If the ALWAYSBACKUP= option is not specified, you receive the first form of this message and the data set is bypassed. If the ALWAYSBACKUP= option is specified, you receive the second form of this message and the data set is backed up but not reorganized. It is possible to receive this message if another FDRREORG is running and is processing this data set. FDRREORG sets the update inhibit flag to prevent the data set from being updated while it is being reorganized. If another FDRREORG is not running, then the update inhibit flag was probably set manually with an IDCAMS ALTER statement. The update inhibit flag has to be reset with IDCAMS before FDRREORG reorganizes this data set.

FDRS34*

CLUSTER IS AN ESDS - WILL BE BACKED UP BUT NOT REORGANIZED - DSN=dsn

Explanation: The ALWAYSBACKUP= option was specified or defaulted to “YES” and an ESDS (sequential) cluster was selected.

Action: The ESDS is backed up.

FDRS35**

BACKUP DATA SET WOULD BE CATALOGED IN THE MASTER CATALOG -- BACKUP DSN=dsn

Explanation: The ALIASCHECK= option is specified or defaulted to “YES” and a catalog alias does not exist to point the generated backup data set name to a user catalog.

Action: Backup processing is terminated.

FDRS36**

BACKUP=TEMP NOT ALLOWED WITH ALWAYSBACKUP OR NOREORG

Explanation: The intent of the ALWAYSBACKUP= or NOREORG options is to ensure that backups always exist for any data sets selected.

Action: Processing is terminated.

FDRS37**

RETRY ALREADY PENDING FOR THIS DSN ON ANOTHER VOLUME -- DSN=dsn

Explanation: DSNRETRY= was specified as enqueue or WAIT and a previous request for the same partitioned data set name had already been issued from another volume. Because the system does not manage SYSDSN enqueues on a volume basis, it is not possible to have more than one pending request.

Action: The data set is bypassed.

FDRS38**

ERROR ALLOCATING VOLUMES FOR DEFINE -- DSN=dsn

Explanation: An error occurred while allocating the volumes required to redefine a VSAM data set.

Action: Refer to the IKJ messages that follow this message and take the appropriate action. The RECOVER statement has to be used to complete processing for the indicated data set. If there is a problem with the volumes required to successfully redefine the data set, the data set should be defined before using the RECOVER statement.

FDRS39**

VOLUME vol NOT MOUNTED -- DEFINE TERMINATED -- DSN=dsn

Explanation: A volume required to redefine a VSAM data set is no longer online.

Action: Use the RECOVER statement to complete processing for the indicated data set when the required volumes are available. If there is a problem with the volumes required to successfully redefine the data set, the data set should be defined before using the RECOVER statement.

FDRS40**

FDRS41**

RECORDS READ LESS THAN NUMBER OF RECORDS IN STATISTICS BLOCK -- DSN=dsn RECORDS READ=n,RECORDS EXPECTED=m

Explanation: To prevent reloading a damaged file, FDRREORG compares the number of records read during the backup ( n ) with the number of records contained in the catalog statistics block ( m ) for an IAM or VSAM data set. If the number of records read is less than the number of records in the statistics block, FDRREORG does not reload the data set.

Action:  Research all activity against the indicated data set. If a system failure occurred while records were being deleted, it is possible that the statistics block was not updated to reflect the deleted records. If the data set is not damaged, FDRREORG can be forced to reorganize these data sets by specifying NORCOUNTERR on the REORG statement.

FDRS43**

UNEXPECTED DEVICE FOR BACKUP DATA SET -- DEVICE CLASS=cc, DEVICE TYPE=tt

Explanation: The POOLDASD option in the FDRREORG option table has been set to “YES” and an undefined unit name is used for allocation. The device allocated is not DASD.

Action: FDRREORG processing is terminated.

FDRS44**

UNABLE TO REDEFINE SMS MANAGED CLUSTER -- SMS NOT ACTIVE

Explanation: An attempt was made to redefine an SMS-managed cluster and SMS is not active.

Action: Activate SMS and rerun the job.

FDRS45*

DATA SET IS EMPTY AND WILL NOT BE REORGANIZED -- DSN=dsn

Explanation: A previously loaded VSAM cluster or IAM data set no longer has any records.

Action: The data set is bypassed.

FDRS46**

NO DATA SETS SELECTED

Explanation: No data sets matched the provided selection criteria.

Action: Check the SELECT/EXCLUDE statements and rerun the job.

FDRS47**

FDRS48**

REVERTING TO ORIGINAL DEFINE -- DSN=dsn

Explanation: An error occurred while attempting to redefine a VSAM cluster and operands were specified to change the original definition.

Action: FDRREORG reverts to the parameters used for the original define. Review and correct the requested changes and rerun the job to implement the desired changes.

FDRS49**

PRI=nnnnnn,SEC=nnnnnn,BLKSIZE=nnnnn,…

Explanation: Issued after message  FDRR94**  to list the parameters used for the failed dynamic allocation.

Action: Refer to the IKJ messages preceding this message.

FDRS50**

NONUNIQUE KEY DETECTED FOR UNIQUEKEY AIX -- DSN=dsn

Explanation: Multiple occurrences of the same alternate key have been detected for an Alternate Index defined with the UNIQUEKEY attribute.

Action: The alternate index build is terminated. This message is equivalent to the IDC1645I message issued by the BLDINDEX statement of IDCAMS.

FDRS52**

ALTERNATE INDEX HAS MORE THAN 3 PATHS -- DSN=dsn

Explanation: FDRREORG does not support Alternate Index (AIX) data sets with more than 3 PATHs.

Action: The base cluster and all related objects are bypassed.

FDRS53**

EXCESS PRIME KEYS DETECTED DURING BLDAIX -- DSN=dsn

Explanation: The maximum record size of an Alternate Index (AIX) was not large enough to contain all of the alternate keys.

Action:  The alternate index is created with only the alternate keys that would fit. This message is equivalent to the  IDC1646I  message issued by the BLDINDEX statement of IDCAMS.

FDRS54**

AIX IN USE DSN=aixcluster  BASE=basecluster

Explanation: A VSAM KSDS with an alternate index (AIX) has been selected for reorganization and the alternate index is in use.

Action: The data set is bypassed.

statistics

Explanation: Informational message for IAM and VSAM data sets. This message is issued if RECORDCOUNTS=YES has been set in the FDRREORG option table.

FDRS56**

DUPLICATE KEY AT RECORD nnnnnnnnnn - DSN=dsn

Explanation: During backup of a KSDS or IAM data set, a duplicate key was found in record “nnnnnnnnnn” (decimal).

Action:  The backup is terminated. You may need to reload the cluster or use other tools to fix the error.

FDRS57**

KEY SEQUENCE ERROR AT RECORD nnnnnnnnnn  -- DSN=dsn

Explanation: During backup of a KSDS or IAM data set, an out-of-order key was found in record “nnnnnnnnnn” (decimal).

Action:  The backup is terminated. You may need to reload the cluster or use other tools to fix the error.

FDRS58*

>4GIG KSDS CAN NOT BE REORGANIZED WITH THIS VERSION OF DF/SMS-- DSN=dsn

Explanation: During backup of a KSDS, FDRREORG detected that the cluster was defined as an “over 4 gigabyte” cluster on an SMS-managed cluster, but the level of the IBM DFSMSdfp component installed does not support such clusters.

Action: The backup is terminated. Rerun on a system that includes DFSMSdfp V1R3 or above (all z/OS systems include V1R3 or above).

FDRS59*

SINGLE VOLUME DATA SET BYPASSED BECAUSE MODE=PARALLEL -- DSN=dsn

Explanation: Parallel backups were requested so single volume data sets are bypassed.

FDRS60*

MULTI VOLUME DATA SET BYPASSED BECAUSE MODE=SINGLE -- DSN=dsn

Explanation: Parallel backups were requested so single volume data sets are bypassed.

FDRS61**

type POINT FAILED -- R15=ccc,BACKUP=n,DSN=dsn

Explanation: During backup of a KSDS or IAM data set, a VSAM or IAM POINT failed with return code “ccc”.

Action: The backup is terminated. You may need to reload the cluster or use other tools to fix the error.

FDRS62**

type READ FAILED -- R15=ccc,CODE=rrr,RBA=xxxxxxxx, DSN=dsn

Explanation: During backup of a KSDS or IAM data set, a read for a DATA or INDEX record failed with return code “ccc” and reason code “rrr” on the record at Relative Byte Address (RBA) “xxxxxxxx”.

Action: The backup is terminated. Refer to the IBM manual Macro Instructions for Data Sets for a description of the VSAM return and reason codes. You may need to reload the cluster or use other tools to fix the error.

CAN NOT DEFINE CLUSTER WITH IMBEDDED INDEX IN EXTENDED FORMAT -- DSN=dsn

Explanation: The cluster has the IMBED option but the SMS data class assigned requests extended format (EF). IMBED cannot be used with extended format.

Action: The cluster is allocated in non-extended format with the IMBED option. If you want to use extended format, specify the CONVERTINDEX operand and the cluster is allocated in extended format with the NOIMBED option.

FDRS64**

BACKUP=GDG NOT SUPPORTED FOR PARALLEL BACKUPS

Explanation: MODE=PARALLEL was specified and GDG backups cannot be used.

Action: The backup is terminated.

FDRS65**

LASTAPE NOT SUPPORTED FOR PARALLEL BACKUPS

Explanation: MODE=PARALLEL was specified and the LASTAPE option cannot be used.

Action: The backup is terminated.

FDRS66**

? CHARACTER NOT FOUND IN BACKUP GROUP, INDEX, OR STRING - REQUIRED FOR PARALLEL BACKUPS

Explanation: MODE=PARALLEL was specified and BACKUPGROUP=, BACKUPINDEX=, or BACKUPSTRING= operand must contain a “?” to indicate where FDRREORG is to substitute the unique backup character.

Action: The backup is terminated.

FDRS67**

FDRS68*

DATA SET TOO SMALL FOR MODE=PARALLEL - BYPASSED -- DSN=dsn

Explanation: MODE=PARALLEL was specified but the data set is too small to be eligible for parallel processing.

Action: The data set is bypassed.

FDRS69*

IAM DATA SET CAN NOT BE PROCESSED IN PARALLEL MODE - BYPASSED -- DSN=dsn

Explanation: MODE=PARALLEL was specified but the data set is IAM.

Action: The data set is bypassed.

FDRS70*

IAM DATA SET CAN NOT BE REDEFINED -- DSN=dsn

Explanation: IAMDEFINE=YES was specified or default, but an IAM data set cannot be redefined. This may occur if you are running a level of IAM less than V6.3 or are reorganizing a data set that was created with a level of IAM less than V6.3. Other causes are possible.

Action: The data set is bypassed.

FDRS71**

FDRS72**

FDRS73

REORG FORCED BY IAM -- DSN=dsn

Explanation: IAM has recommended that an IAM data set be reorganized.

Action: Other conditional reorganization operands are ignored; the data set is reorganized.

FDRS74**

INCOMPLETE IAM INFO BLOCK - CAN NOT RECOVER FROM OUT OF SPACE -- DSN=dsn

Explanation: An IAM data set does not have the information required to extend the data set.

Action: You may need to predefine the IAM data set and manually reload it from the backup created by FDRREORG.

FDRS75**

IAM HAS BEEN DEACTIVATED - CAN NOT DEFINE IAM FILE -- DSN=dsn

Explanation: IAM is not active.

Action: Activate IAM and rerun the job.

FDRS76**

FDRS77**

FDRS78*

FDRS79**

FDRS80**

FDRS98

DATA SET HAS nnnnnn MEMBERS nnnnnn DIRECTORY BLOCKS USED nnnnnn BLOCKS UNUSED

Explanation: FDRCOPY REORG is executed with the LIST=YES operand or REORG is invoked by the IEBCOPY interface and LIST=NO is not specified. The message gives PDS directory statistics.

FDRS99

MEMBER member status

Explanation: FDRCOPY REORG was executed with the LIST=YES operand or REORG was invoked by the IEBCOPY interface and LIST=NO was not specified. The message shows the status of each member in the PDS. “status” can be:

WAS MOVED

The member was relocated during compression.

IN PLACE

The member did not need to be moved.

IS ALIAS

Member aliases are automatically updated when the prime member is moved.