FDR Console Messages and TSO Terminal Messages
The following write-to-operator (WTO), write-to-operator-with-reply (WTOR), and TSO messages are issued by FDR:
Number | Description |
---|---|
FDRW01 | CONFIRM REQUEST TO RESTORE UNIT=unit,VOL=vol, JOB=job Explanation: The job “job” wishes to do a full-volume restore or copy to the DASD device “unit” whose current volume serial is “vol”. This confirmation request can be suppressed by specifying the CONFMESS=NO operand on the RESTORE or COPY statement. Action: Reply “YES” – Operator approves request to restore. Reply “NO” – Operator does not approve the restore request; the restore is terminated. CONFIRM REQUEST TO RESTORE FROM UNIT=unit TO VOL=vol. REPLY YES OR NO. Explanation: This form of the FDRW01 message is issued by FDRINSTANT. A FlashCopy FRR restore is being requested to the volume serial “vol” from the offline unit address “unit”. This confirmation request can be suppressed by specifying the CONFMESS=NO operand on the RESTORE or COPY statement. Action: Reply “YES” – Operator approves request to restore. Reply “NO” – Operator does not approve the restore request; the restore is terminated. |
FDRW02 | CONFIRM REQUEST TO ABSOLUTE TRACK RESTORE UNIT=unit, VOL=vol,JOB=job Explanation: The job “job” wishes to do an absolute track restore to volume “vol” on the DASD device “unit”. Action: Reply “YES” – Operator approves request to restore. Reply “NO” – Operator does not approve the restore request; the restore is terminated. CONFIRM REQUEST TO CONTINUE BACKUP - PREVIOUS INSTANT BACKUP FOR vol WILL BE LOST. REPLY YES OR NO. Explanation: This form of FDRW02 is issued by FDRINSTANT. You have done a SNAP or SPLIT operation for volume “vol” but you have not yet executed the ABR DUMP with SNAP=USE or BCV=USE to move the backup to tape, and you are trying to execute another SNAP or SPLIT. If you specify the operand CONFMESS=NO on the SNAP or SPLIT statement, then FDR overlays backup image on DASD unconditionally, and issue message FDR230 with REASON=P. Action: Reply “YES” – Operator approves request to backup. The backup already on the SNAP target volume or BCV is lost. Reply “NO” – The backup is terminated. INSTANT BACKUP FOR vol ON SNAPUNIT=uuuu IS IN-USE. REPLY “RETRY” OR “CANCEL” Explanation: This form of FDRW02 is issued by FDRINSTANT. You have done a SNAP or SPLIT operation for volume “vol” but the ABR DUMP with SNAP=USE or BCV=USE to move the backup to tape or a restore job is still executing, and you are trying to execute another SNAP or SPLIT. Action: Reply “RETRY” – When you believe the backup is longer in use. If it is still busy, the message is reissued. Reply “CANCEL” – The backup is terminated. |
FDRW03 | dsn DATE PROTECTED--REPLY YES OR NO TO RESTORE VOL=vol Explanation: A data set restore has been requested for data set “dsn” on volume “vol”. The output data set is preallocated and has an expiration date that has not been reached. If you wish to suppress this message and automatically do the restore, specify EXPD=NONE on the RESTORE statement. Action: Reply “YES” – Operator approves request to restore. Reply “NO” – Operator does not approve the restore request; the restore is terminated |
FDRW04 | FULL VOLUME RESTORE COMPLETED - UNIT=uuuu SHOULD BE REMOUNTED ON OTHER SYSTEMS Explanation: A full volume restore was completed on the DASD device “uuuu” that is marked as “Shared DASD” in your I/O configuration. FDR has determined that the restore changed the volume serial and/or the VTOC location on the output volume. FDR has made the necessary changes on the system where the restore was run, but if other CPUs access the DASD, they do not know of this change and may not process this volume properly. Action: Normally all other systems should make this device offline prior to the restore, especially if the volume serial or VTOC changes. This message indicates that you may now remount the volume on the other systems; vary it OFFLINE if not already offline, then vary it ONLINE. |
FDRW05 | DISK UNIT=unit VOL=vol HAS BEEN RELABELED TO VOL=nvol Explanation: DASD device “unit” has been restored. Its original volume serial was “vol” but the restore has changed the volume serial to “nvol”. |
FDRW06 | DISK UNIT=unit VOL=vol NOW OFFLINE - DUPLICATE VOLSER Explanation: DASD device “unit” has been restored. The restore has changed the volume serial to “vol”, which matches the volume serial number of another online volume (probably the original volume). Action: FDR sets DASD device “unit” offline. |
FDRW10 | FDRDRP COULD USE ADDITIONAL type TAPE DRIVES; PLEASE VARY SOME ONLINE IF AVAILABLE. Explanation: A FDRDRP restore has not reached its limit of active tape drives (MAXTAPES=) but no additional drives of the needed type are online. Action: Vary one or more tape drives online. After a few moments, FDRDRP begins to use them. |
FDRW22 | DSN dsn PASSWORD PROTECTED Explanation: Data set “dsn” is password protected and is being backed up or restored. This refers to old OS password protection for non-VSAM data sets and VSAM password protection for VSAM. It does not refer to security systems like IBM RACF. Action: To continue processing the operator must reply to the appropriate z/OS password message. |
FDRW23 | DSN dsn DATE PROTECTED REPLY YES OR NO FOR ARCHIVE Explanation: Non-VSAM data set “dsn” was selected for Archive or Superscratch, but the data set has an expiration date that has not been reached. If you wish to suppress this message and automatically select the data set, specify EXPD=NONE on the DUMP statement. Action: Reply “YES” – Archive and/or scratch the data set. Reply “NO” – DO NOT select the data set. |
FDRW24 | FDRABR REQUEST FOR TAPES - vol... REPLY YES NO OR BYPASS Explanation: The OPERATOR operand was specified on a RESTORE statement. A restore of a data set was requested from the backup volumes “vol…”. Action: Reply “YES” – You have the volumes available. Reply “NO” – You do not have the volumes available, or do not wish to mount them at this time. The restore is canceled. Reply “BYPASS” – same as NO. |
FDRW25 | ABR REQUEST FOR TAPES(nn) vol... REPLY YES NO OR BYPASS(nn) Explanation: The OPERATOR operand was specified on a RESTORE statement for a full-volume ABR RESTORE. Message FDRW25 is repeated for each ABR Volume Backup that is used during the restore; each line shows the ABR Cycle number “nn” followed by the volume serials of the backups “vol…” required for that cycle. Action: Reply “YES” – All of the volumes are available. Reply “NO” – All or some volumes are not available. The restore request is canceled. Reply “BYPASS(nn)” – The tapes shown for cycle “nn” are not be used during the restore. “nn” may be any cycle that was listed, except cycle zero (the full volume backup). After a reply of “BYPASS(nn)”, the message is reissued so that additional backups can be bypassed. When all desired backups to be bypassed have been specified, reply “YES”. Data sets whose latest backup was on the cycles that you bypassed are probably not correctly restored. |
FDRW26 | INVALID RESPONSE REPLY YES NO OR BYPASS(nn) Explanation: The operator reply to message FDRW25 was invalid. Either, the operator reply was an invalid keyword, the cycle number was invalid or did not exist, or the cycle number was zero. Action: Give a proper response to the message. |
FDRW27 | REPLY WAIT, NOWAIT, OR RETRY FOR ENQ WAIT ON DSN=dsname Explanation: An FDR job specified DSNENQ=HAVE. Data set “dsname” is currently enqueued to another job. Action: Reply “WAIT” – FDR waits for the data set to become available. The job could time out if the enqueue is not released in a short time. Reply “NOWAIT” – FDR issues an FDR158 warning message for the data set.
Reply “RETRY” – FDR retries the enqueue. If it is still not available, message FDRW27 is re-issued. |
FDRW28 | FDR function WAITING ON TAPE VOL=vol REPLY NO TO CANCEL Explanation: An FDR restore process needs a tape that is being used by another job. Action: None necessary unless you want to cancel the restore function. |
FDRW30 | FDR ZEDC COMPRESSION ERROR. FPZ4ABC RC=X’rc’ RS=’rs’ Explanation: This message is issued when the return code returned from calling the FPZ4ABC zEDC compression service is non zero. The meanings of the return code and reason code combinations can be found in the z/OS MVS Programming: Callable Services for High-Level Languages manual. Common rc / rs combinations are: 00000008 / 00000000 No zEDC devices are available. 00000010 / 00001203 There are no zEDC devices available. Action: The z/OS DISPLAY command can be used to check zEDC availability: D PROD,REG,FEATURENAME(ZEDC) |
FDRW40 | MODULE modn INSTALLED AT addr -- VER v.r Explanation: The message is issued in response to a status request when the FDR operating system exit module “modn” is installed in the system. “addr” is the virtual storage location of that module. The version number of the module is also given. FDR GLOBAL OPTIONS LOADED AT hh:ss ON yy.ddd FROM VOL=vol DSN=loadlib Explanation: The message is issued when an FDR operating system exit is installed or in response to a status request. It shows the when the memory-resident copy of the FDR option table (FDROPT) was loaded and from which load library. |
FDRW41 | THE FDR SYSTEM MODULES ARE status -- VER nn type Explanation: This message is issued by FDRSTART or FDRSTATS when the FDR operating system exit modules are installed in the system. The “status” of the modules may be: ACTIVE On the first execution of FDRSTART or on executions of FDRSTATS; RE-ACTIVATED On executions of FDRSTART where an FDR operating system exit module was re-activated. REFRESHED On subsequent executions of FDRSTART where the copy of the FDR Global Options module in global storage was refreshed. This message includes the version “nn” and release level of the modules installed. “type” indicates: PROD For production exits. TEST For test exits (the JOBNAME= or JOBGROUP= that uses the test exists is also displayed). |
FDRW42 | THE FDR SYSTEM MODULES ARE status type Explanation: This message is issued by FDRPARE or FDRSTATS when the FDR operating system exit modules are disabled. This message is also issued by FDRSTART when activating or replacing the operating system exit modules. The “status” of the modules may be: NOT ACTIVE When the ABR operating system exit modules are not installed in the system. INACTIVE When the ABR operating system exit modules are installed in the system but are disabled, that is, not processing any requests. REPLACED When the ABR operating system exit modules have been replaced by running the FDRSTART program with the “REPLACE” parm. ACTIVE When the ABR operating system exit modules are installed. RE-ACTIVATED When the ABR operating system exit modules that were INACTIVE have been enabled so they process requests. DE-INSTALLED When the ABR operating system exit modules are removed. “type” indicates: PROD For production exits. TEST For test exits (the JOBNAME= or JOBGROUP= that uses the test exists is also displayed). |
FDRW44 | modn ESTAE RECOVERY ENTERED FOR ABEND Ssss Uuuuu AT OFFSET xxxx Explanation: This message is issued by “modn”, which can be FDRSTART, FDRSTATS, or FDRPARE, when an unexpected system “sss” or user “uuuu” abend occurs at displacement “xxxx” in the module. If the offset is not displayed, the abend did not occur within the FDRSTART module. Action: If the problem persists contact BMC Support for assistance. |
FDRW46 | modn FAILURE - REASON=nn Explanation: The execution of “modn”, which can be FDRSTART, FDRSTATS, or FDRPARE failed for one of the following reasons “nn”: 01 O. S. NOT MVS SP 1.2 OR HIGHER 02 INVALID INPUT PARAMETERS Check the PARM= specified. 03 UNABLE TO OBTAIN AUTHORIZATION Program library must be APF authorized. 04 FDRVECTB VECTOR TABLE IS INVALID Contact BMC Support for assistance. 05 SYSLIB DD MISSING OR OPEN ERROR Check the SYSLIB DD statement. 06 modn NOT FOUND IN SYSLIB The ABR exit “modn” was not found in the library pointed to by the SYSLIB DD statement. 07 modn MODULE LOAD ERROR: Ssss-rr Contact BMC Support for assistance. 08 ERROR MODIFYING THE SVC TABLE Contact BMC Support for assistance. 09 modn NOT FOUND The module “modn” was not found in the link pack area. Contact BMC Support for assistance. 10 modn NOT FOUND IN THE LINKLIST The ABR exit module “modn” was not found in an APF authorized link list (LNKLST) library. 11 modn - UNABLE TO DE-INSTALL Contact BMC Support for assistance. 12 modn CDE OR LPDE ABOVE 16M ERROR Contact BMC Support for assistance. 13 modn MODULE ABOVE 16M ERROR Contact BMC Support for assistance. 14 GETMAIN ERROR Increase the region in the step JCL. 15 modn HAS SMP INSTALLED IDP MODULE FDRSTART detected the presence of an ABR operating system exit installed via SMP in the named module. The ABR operating system exits that are SMP installed must be removed if they are to be dynamically installed. 16 UNABLE TO OBTAIN CMS LOCK Contact BMC Support for assistance. 17 FREEMAIN ERROR Contact BMC Support for assistance. 18 UNABLE TO OBTAIN LOCAL LOCK Contact BMC Support for assistance. 19 modn CDE NOT FOUND Contact BMC Support for assistance. 20 {ENQUEUE/DEQUEUE} ERROR ON IAM RESOURCE 21 {ENQUEUE/DEQUEUE} ERROR ON SYSZSVC Contact BMC Support for assistance. 22 INVALID VECTOR TABLE STATUS Contact BMC Support for assistance. 23 INVALID VECTOR TABLE CDE ADDRESS Contact BMC Support for assistance. 24 RC=xxxx FROM SVCUPDTE Contact BMC Support for assistance. 25 NO MODULES TO INSTALL - FDROPT The dynamic installation options that indicate which of the ABR operating system exits are to be installed specified that none of the exits is to be installed. These options (ABRLOC, ABRDSNF, ABRPRE, and IEBCOPY) are set in FDR Global Options, module FDROPT, using the ABR Install dialog (ISPF Panel A.I.4.11.1 – Set Dynamic Installation Exits). 26 FDR SYSTEM MODULES INSTALL CANCELLED This message is displayed when the console operator replies “NO” to the FDRW47 message. 27 modn AND IAMVECTB ARE OUT OF SYNCH 28 VECTOR TABLE CANNOT BE STOPPED 29 FDROPT MODULE LEVEL IS NOT HIGH ENOUGH The dynamic installation options are not present in the level of FDROPT that was loaded. 30 PARM (PROD OR TEST) NOT SPECIFIED 31 HIGHER LEVEL OF VIF ALREADY ACTIVE 32 modn ERROR Contact BMC Support for assistance. 33 modn ERROR Contact BMC Support for assistance. 34 SYSEVENT DONTSWAP ERROR Contact BMC Support for assistance. 35 PROGRAM LEVEL LOWER THAN VECTOR TABLE Contact BMC Support for assistance. 36 VECTOR TABLE TO BE REPLACED NOT FOUND Contact BMC Support for assistance. 37 TBL LEVEL NOT HIGH ENOUGH FOR REPLACE Contact BMC Support for assistance. 38 modn - CSVDYLPA RC=xxxx-xxxxxxxx Contact BMC Support for assistance. 39 modn NOT FOUND Contact BMC Support for assistance. 40 modn {ENQUEUE/DEQUEUE} ERROR ON SYSZCSV/ CSVDYLPA Contact BMC Support for assistance. 41 modn INSTALLING FDR019VM Contact BMC Support for assistance. 42 modn - CSVDYNEX RC=xxxx-xxxxxxxx Contact BMC Support for assistance. Action: If error cannot be determined, contact BMC Support for assistance. |
FDRW47 | CONFIRM REQUEST TO INSTALL THE FDR SYSTEM MODULES Explanation: This WTOR prompts the console operator to confirm installation of the FDR operating system exits. This message is issued unless the CONFINST option in FDR Global Options is set to NO. Action: Reply “YES” to proceed or “NO” to bypass the dynamic installation of the FDR operating system modules. |
FDRW48 | INVALID REPLY -- PLEASE REPLY YES OR NO INVALID REPLY -- PLEASE REPLY RETRY OR CANCEL Explanation: The reply to the previous message was invalid. Action: The message is reissued. Reply “YES”, “NO”, “RETRY”, or “CANCEL” as indicated in the message. |
FDRW49 | PLEASE ENTER THE FULLY QUALIFIED FDR libname DATA SET NAME Explanation: The TSO allocation CLIST ABRALLOC was unable to allocate one of the FDR ISPF libraries whose name is stored in the CLIST. “libname” indicates the library that was not found. Action: If the FDR ISPF library names have changed, please enter the correct data set name for the library. You should also update the ABRALLOC CLIST with the correct names (see FDR-Installation). |
FDRW50 | TSO RESTORE FAILURE -- DSN=dsn Explanation: The ABR Catalog Locate exit was attempting to restore the data set “dsn” in the foreground under TSO and the restore failed. This is accompanied by another message detailing the cause of the restore failure and either FDRW51 or FDRW52 if retry of failing TSO foreground restores is enabled. |
FDRW51 | RESTORE WILL BE ATTEMPTED IN THE BACKGROUND Explanation: See FDRW50. The installation has enabled retry of failing foreground recalls in the background (LXFGERR=BG), so the recall is attempted as a background task. |
FDRW52 | RESTORE REQUEST WILL BE PLACED INTO THE REMOTE QUEUE Explanation: See FDRW50. The installation has enabled retry of failing foreground recalls via the remote queue (LXFGERR=RQ), so the recall is added to the Archive Restore remote queue for later processing. |
FDRW53 | desc TASK LIMIT REACHED -- action Explanation: The installation has enabled options LXMAXSTC=nnn and/or LXMAXREC=nnn (ISPF panel A.I.4.11.3) to limit the number of auto recall started tasks or the total number of auto recall tasks or both. “desc” may be either “RECALL STARTED” or “TOTAL RECALL” depending on what limit was exceeded. “action” may be: REPLY ‘WAIT’ OR ‘CANCEL’ If the recall is for a TSO user. WILL WAIT For all other environments. Action: The TSO user can reply with “WAIT” to wait for the current recalls to drop below the limit or “CANCEL” to abort the recall. Non-TSO recalls automatically wait for the recalls to drop below the limit; the message is informative. |
FDRW54 | CVAF I/O ERROR SEARCHING THE VTOC OF DISK VOLUME vol Explanation: The ABR Catalog Locate exit issued a CVAF call to see if a data set marked as having been Archived by ABR actually exists on DASD volume “vol”. If the data set is on DASD, the restore is not necessary. The CVAF call failed with a return code of 16 (x'10'), indicating a permanent I/O error was encountered searching the VTOC. The VTOC of that volume may be damaged. Action: See IBM diagnosis manuals for recovery procedure. If unable to correct, contact BMC Support for assistance. |
FDRW55 | SYNCHRONOUS RESTORE SERVICE NOT ENABLED – NOWAIT SUBSTITUTED Explanation: A synchronous recall was requested, but this option has not been enabled in FDR Global Options. Action: To allow synchronous recalls, enable the LXSYNUSE option in the FDR Global Options panel (A.I.4.11.9). |
FDRW56 | SYNCHRONOUS RESTORE status Explanation: The ABR Catalog Locate exit has initiated a synchronous recall on behalf of a TSO user. This message reports the status of the recall. “status” may be: IS PROCEEDING – PLEASE BE PATIENT WITH ME The synchronous restore is still in process. This message is issued at five-second intervals up to four times. TIMED OUT The synchronous restore task failed after notifying the exit that the restore had started. CONVERTED TO ASYNCHRONOUS RESTORE VIA ATTENTION The user pressed the ATTN or PA1 key. Rather than canceling the restore the WAIT is canceled and the restore is allowed to proceed asynchronously (without impacting the terminal user). |
FDRW57 | UNCATALOGED FOR DELETE -- DSN=dsn Explanation: The ABR Catalog Locate exit detected a catalog DELETE request for a data set Archived for auto-recall. The DELETE is failed with a return code of 8 and reason code of 42 (record not found). However, the auto-recall catalog entry is removed (uncataloged). If the delete was issued by IDCAMS or TSO you may receive: IDC3009I ** VSAM CATALOG RETURN CODE IS 8 IDC0551I ** ENTRY dsn NOT DELETED Action: None, since the catalog entry has been removed. You may disregard the IDC messages. |
FDRW58 | DATA SET IN USE OR BEING RECALLED--RETRY ALLOCATION IN A FEW MINUTES Explanation: The ABR Catalog Locate exit issued an enqueue to see if the data set listed in the FDRW70 message was available for use. The enqueue showed that the data set was allocated to another job or user. The recall is terminated. Action: Retry the recall after allowing some time for the other task to free the data set. |
FDRW59 | ABR AUTO RECALL CANCELLED -- reason Explanation: The ABR Catalog Locate exit was entered because a catalog search (LOCATE) was issued for a data set that was Archived by ABR with the RECALL=YES operand. The exit failed trying to invoke ABR to recall the data set. “reason” is one of the following: ATTACH OF pgm FAILED--RC=nnn The exit attempted to ATTACH the program “pgm” but the ATTACH failed. The ATTACH return code from register 15 is printed (“nnn”). FDROPT LOAD FAILED -- R1=nnnn/R15=nn The exit attempted to LOAD FDROPT but it failed. The contents of the LOAD SVC return code registers 1 and 15 are printed, with register 1 showing the abend code that would have resulted if the FDROPT were executed as a processing program, that is: // EXEC PGM=FDROPT FDROPT VERSION nnnn NOT SUPPORTED “nnnn” is the version number of the FDR Global Options (FDROPT) that was found. It is not compatible with the version of the exit installed. SYSZTIOT ENQUEUE ERROR -- RC=nnn “nnn” is the return code from a failing enqueue SVC. ATTACH NOT ATTEMPTED--SP251 IN KEY 0 The exit needed to attach a module that is linked non-reentrant. It would be loaded into sub-pool 251. This sub-pool has been acquired in protect key zero (0). RESTORE INCOMPLETE -- WILL ISSUE U0026 ABEND The auto-recall did not complete successfully. The step terminates with an U0026 abend to prevent it from executing. RESTORE INCOMPLETE - RESULTS UNPREDICTABLE The auto-recall did not complete successfully, but the installation has set option LXERRPGM to NO so that the step attempts to execute. Because the archived data sets are not on DASD, the results are unpredictable. Common results are abend S213-04 or S737-04 but other failures are possible. The step may even complete successfully but you need to verify that it got the desired results. VOL vol – SMS ERROR – cccccccc/ssssssss During the auto-recall to the indicated volume “vol”, SMS returned a non-zero error. The error code “cccccccc” and reason code “ssssssss” are listed. GETMAIN FOR nnnnn BYTES FAILED Storage for “nnnnn” bytes for the work area used to create the restore data set name list could not be obtained by the recall task. Action: If unable to correct, contact BMC Support for assistance. |
FDRW60 | FDROPSPF VER x.x/xx - PROCESSING ERROR - PARM-LVL level Explanation: The FDR Install dialog CLIST invoked program FDROPSPF with an incompatible parameter level, indicating that the ddname allocations for the FDR CLIST library and the FDR program library point to libraries at different maintenance levels. On a re-install, the problem might be that the new FDR program library is not allocated to either ISPLLIB or STEPLIB ddnames, thus causing the prior level FDR programs to be loaded from the link list (LNKLST). Action: If the FDR libraries are allocated at TSO log in time by the log in PROC or log in CLIST, verify that all required ddnames are allocated, as documented in FDR Installation. If the FDR libraries are allocated by a local CLIST that uses the ISPF LIBDEF service, switch to use the ABRALLOC CLIST supplied by IDP, as documented in FDR-Installation. |
FDRW67 | ADDRESS SPACE CREATE RETURNED -- CODE=rc -- REASON=rs Explanation: The ABR CATALOG LOCATE exit attempted to start an address space to perform an automatic recall, but the ASCRE macro failed with return code rc and reason code rs. Action: Make sure that your installation has copied a cataloged procedure for job-level external recalls to your PROCLIB. The input for this procedure is supplied in member FDREXRCL in the Installation Control Library (ICL). The suggested name for this procedure in your PROCLIB is FDREXRCL. Make sure that your installation has specified the name of the procedure (FDREXRCL or other) in global option LXXRPROC on panel A.I.4.11.2 of the ABR ISPF dialog. If desired, contact BMC Support for assistance. While waiting for the problem to be resolved, you can restore the data set explicitly. You can do this with FDRSRS, ISPF option A.S.1, by specifying the dsname and SOURCE ===> ARCHIVE on the Data set Selection panel and then using the REST line command on the Data set List panel. Or, you can request the restore using the A.2 RESTORE panel. |
FDRW68 | PROCESSING RESTORES FOR JOBNAME=job Explanation: Informational message indicating that the external restore procedure is restoring data sets for the specified job “job”. |
FDRW69 | reason--DSN=dsn Explanation: The ABR Catalog Locate exit was attempting to reallocate a data set recalled by ABR at step initiation. Before the recall, the exit temporarily allocates the data set to a volume. If ABR recalls the data set to a different volume, then the exit must reallocate the data set; if it was part of a concatenation, it must re-concatenate all the data sets in the list. The attempt to reallocate or re-concatenate the data set failed for one of the following reasons: LOCATE FAIL-RC=nn A catalog LOCATE issued during reallocation failed with return code “nn”. DSNAME MISMATCH The data set name returned by LOCATE is not the name the exit was expecting. This may occur if the data set has an alias. NOT RESTORED ABR did not successfully restore the Archived data set. DEALLOCATE FAILED Dynamic deallocation of the ddname assigned to the data set failed with a return code other than zero. REALLOCATE FAILED Dynamic re-allocation of the ddname assigned to the data set failed with a non-zero return code. RECONCAT FAILED Dynamic re-concatenation of the ddname assigned to the data set failed with a non-zero return code. SWA RESCAN FAILED A scan of SWA (System Work Area) during re-allocation failed with a non-zero return code. CVAF FAIL - nn/mmm A CVAF call was issued to verify that a data set is on DASD, but it failed with return code “nn” and reason code “mmm”. DEVTYPE MISMATCH ABR recalled the data set to a different device type than the exit expected. VOLSER NOT FOUND ABR indicated that it recalled the data set to a specific volume serial, but the exit cannot find that volume serial number in any online UCB. TOO MANY DDNAMES The data set was referenced by more than 20 ddnames in this job step. The first 20 ddnames have been reallocated. ddn BYPASSED “ddn” is either JOBLIB or STEPLIB. It was not reallocated because it is currently OPEN. Action: Except for the NOT RESTORED reason, the required data sets have been recalled by ABR. You should be able to resubmit the job for successful execution. |
FDRW70 | |
FDRW71 | TYPE ’END’ TO BYPASS THE RESTORE OR PRESS ’ENTER’ TO CONTINUE Explanation: If option LXALTMSG=NO, this format of message FDRW71 is issued asking the user if the recall of the Archived data set should be done. If option LXFOREST=NO, the message is not issued and the recall automatically proceeds. FDRW71 is only issued to TSO users. Action: Press the ENTER key to recall the data set or type END to terminate the recall. TYPE ’YES’ TO PERMIT THE RESTORE OR PRESS ’ENTER’ TO BYPASS Explanation: If option LXALTMSG=YES, this format of message FDRW71 is issued asking the user if the recall of the Archived data set should be done. Unlike the standard FDRW71 message above, the user must positively request the recall. If option LXFOREST=NO, the message is not issued and the recall automatically proceeds. FDRW71 is only issued to TSO users. Action: Type “YES” to recall the data set or press the ENTER key to terminate the recall. TYPE ‘UC' TO UNCATALOG THE DATA SET Explanation: If option LXUNCAT=YES, this format of FDRW71 may also be issued, giving the user the option of uncataloging the data set instead of recalling it. FDRW71 is only issued to TSO users. Action: Type “UC” to uncatalog the data set without recalling it. The data set is no longer auto-recallable but it can still be restored manually. A new data set with the same name can be created. |
FDRW72 | restore-option--REPLY ‘xx’ Explanation: This message is issued one or more times to show the user a list of recall techniques (FOREGROUND, BACKGROUND, REMOTE QUEUE) available to TSO users, and the reply necessary to invoke each one (FG, BG, RQ). Option LXFDREST can be set to limit the user’s choices; only the recall techniques indicated are listed. If LXFDREST has been set to a single technique, message FDRW72 is not issued and that technique is automatically used. FDRW72 is only issued to TSO users. TO UNCATALOG DSNAME AND BYPASS AUTO RECALL – REPLY ‘UC’ Explanation: This message is issued when confirmation to bypass auto recall has been requested. Action: Type “UC” to uncatalog the data set without recalling it. The data set is longer auto-recallable, but can still be restored manually. A new data set with the same name can be created. |
FDRW73 | |
FDRW74 | ABR AUTO RECALL ABNORMALLY TERMINATED COMP CODE=00sssuuu Explanation: The ABR Catalog Locate exit was entered to recall an Archived data set, but ABR abnormally terminated trying to restore the data set. The completion code contains: sss Is the system abend code uuu Is the user abend code (in hex). FDRW74 is issued for batch jobs as well as online users. Action: If unable to correct, contact BMC Support for assistance. |
FDRW75 | RESTORE BYPASSED -- JOB job DATE: yyddd TIME: hhmmss DSN=dsn RESTORE BYPASSED -- DSN=dsn Explanation: Data set was scheduled for recall during step initiation but the recall was never attempted because the job step flushed, probably due to a JCL error. |
FDRW76 | DATA SET IS SCHEDULED TO BE RESTORED TO VOLUME SERIAL NUMBER vol Explanation: The data set listed in the FDRW70 message is scheduled to be restored to the DASD volume with serial “vol”. If option LXNEWVOL is set to NO, the message is not issued and the recall to the volume selected by the ABR Catalog Locate exit automatically proceeds. |
FDRW77 | TYPE NEW VOLUME SERIAL NUMBER AS XXXXXX OR PRESS ‘ENTER’ TO CONTINUE Explanation: This message is issued after message FDRW76 and asks the TSO user to either accept the target volume displayed in FDRW76 or designate a new target volume. If option LXNEWVOL is set to NO, the message is not issued and the recall to the volume selected by the ABR Catalog Locate exit automatically proceeds. Action: Press the ENTER key to accept the volume shown in FDRW76 or type in the volume serial of a target volume. |
FDRW78 | RESTORE recall-type--YOU WILL BE NOTIFIED UPON COMPLETION Explanation: The ABR Catalog Locate exit is recalling the data set named FDRW70 message. The user receives additional messages indicating the success or failure of the recall. The “recall-type” may be: START COMMAND ISSUED. An asynchronous (background) recall has been started. The TSO user can continue with other functions, and can use the recalled data set when additional messages are received indicating the recall is completed. STARTED IN FOREGROUND. A synchronous recall in the foreground has been started. The TSO user is unable to proceed until the recall is complete. STARTED SYNCHRONOUSLY. A synchronous recall using an external recall address space has been started. The TSO user is unable to proceed until the recall is complete; however, the user may convert the recall to an asynchronous recall by pressing the ATTN or PA1 keys. |
FDRW79 | function reason Explanation: The ABR Catalog Locate exit has determined that the recall of the data set named in the FDRW70 message cannot be done for one of the following reasons: If the “function” is “RESTORE”, then the “reason” can be: BYPASSED -- TSO RESTORE DISABLED Auto recall of Archived data sets is disabled for TSO users (option LXDFREST is set to NO). The message is not issued if option LXNOMSG is set to YES. BYPASSED -- DEFAULT RESTORE TYPE IN ERROR The user made an invalid reply to message FDRW73 and the default recall technique was improperly specified. The user is prompted for another technique. PROMPTED -- DEFAULT RESTORE TYPE IS DISABLED The default recall technique established for TSO users is disabled. If the “function” is “UNCATALOG”, then the “reason” can be: FAILED - R15=ffffffff R0=00000000 R1=11111111 The user replied UC to the FDRW73 message to uncatalog the data set without recalling it, but the uncatalog failed. The contents of registers 15 (return code), R0 (catalog return code) and R1 are shown. Action: Correct if this is an error in the setup of the RECALL exit. |
FDRW80 | CONFIRM REQUEST TO COMPAKT UNIT=unit, VOL=vol, JOB=job Explanation: COMPAKTOR job “job” is about to COMPAKT the volume “vol” on device “unit”. To suppress this message, specify CONFMESS=NO on the COMPAKT statement. Action: Reply “YES” if COMPAKTOR is to continue. Reply “NO” if the COMPAKTion is to be bypassed. CONFIRM REQUEST TO RECOVER VOL=vol FROM FAILED COMPAKTION - REPLY YES OR NO Explanation: A Fast COMPAKTion (CPK TYPE=FASTCPK) was in progress on the indicated DASD volume but that COMPAKTion did not complete for some reason, such as a system crash. This Fast COMPAKTion job automatically recovers from the failure if the operator gives permission. To suppress this message and proceed with the recovery automatically, specify RECOVERY=YES on the COMPAKT statement. Action: Reply “YES” to allow the recovery to proceed; reply “NO” to bypass the recovery at this time. |
FDRW81 | DETECTS UNIT=unit,VOL=vol IN USE nnn, REPLY ‘RETRY’ OR ‘EOJ’ Explanation: The count of open DCBs “nnn” against volume “vol” on device “unit” is checked by COMPAKTOR. If the count is greater than 1, indicating that COMPAKTOR is not the only user of the volume, this message is issued. This message is also issued if the volume contains an active paging data set, or is the system residence volume. The keyword ACTMESS=NO on the COMPAKT statement suppresses this message and proceeds with the COMPAKTion automatically. See Compacting-Active-Volumes. Action: If you know what job is using the device, reply “RETRY” after it ends. If you are not sure, the z/OS console command “D U,,ALLOC,unit,1” displays all jobs that have the DASD allocated (the number of allocations may differ from the number of open DCBs). If necessary, reply “EOJ” to terminate the COMPAKTOR job. Except for the SYSRES volume and paging volumes, you can also reply “IGNORE” to continue the COMPAKTion; however, you must have followed the rules for Compacting-Active-Volumes. |
FDRW82 | COMPAKTOR function status VOL=vol Explanation: If LOG=YES is specified on the COMPAKT statement, this message is issued to inform the operator of the progress of the COMPAKTOR job. “function” is either “REORGANIZATION” for TYPE=FASTCPK or CPK, “SPACE RELEASE” for TYPE=RLSE, or “RECOVERY” for recovery from a failed Fast COMPAKTion. “status” is “STARTED”, “SUCCESSFUL”, or “**FAILED**”. The “STARTED” message remains non-deletable on the console until the “SUCCESSFUL” message is issued so that the operator knows that the operation is still in progress. The “**FAILED**” is also non-deletable to force the operator to take action. Action: If the status is “**FAILED**”, check the output from the COMPAKTOR job. The volume should not be used until any problems are resolved (see COMPAKTOR Error Recovery ). |
FDRW88 | text Explanation: This message is issued by the FDRSPZAP program. The text indicates various FDRSPZAP information or errors. |
FDRW90 | DSN=dsn NOT CATALOGED. REASON CODE=rc ACQUIRED DSCB LIMIT EXCEEDED. REASON CODE=T GQSCAN FAILURE. REASON CODE=V Explanation: This message is issued by module FDRPRE00 (the ABR DADSM Pre-exit) when it fails to catalog a data set being scratched or renamed in the ABR scratch catalog. The exit tried to catalog a name consisting of “#.” followed by the user's “dsn”, in order to record the ABR backup information. A An I/O error occurred reading the VTOC of the volume containing the data set. B A catalog LOCATE on the ABR scratch catalog failed. This message also contains the VSAM catalog return and reason codes. Refer to message IDC3009I in the IBM System messages manual for the meaning of the codes. Common causes for this message are:
C A catalog update on the ABR scratch catalog failed. See reason code “B”. D The data set name being processed is all blanks. E The catalog LOCATE for the ABR Scratch catalog alias failed. The data set name displayed in the message contains the ABR scratch catalog alias name; it may have not been properly specified in the master catalog as an alias of the scratch catalog. G Error creating a GDG base in the ABR scratch catalog for recording a particular Generation Data Group (GDG) being scratched. See reason “B”. K The DADSM scratch or rename work area was not found. L RESERVE/DEQ failed on SYSVTOC. M An I/O error was reported by DADSM rename. N See message FDRW94. O The data set name being scratched or renamed was 43 or 44 characters long, so that the exit was unable to add the “#.” scratch prefix without exceeding the 44-character limit. Such data sets cannot be recorded in the scratch catalog. Set option PXERRLEN to “NO” to suppress this message (see PXERRLEN). P VTOC TTR conversion error. Q The value indicating the displacement in the DSCB for the recording of old backup information is different between the FDR Global Options and the ABR Model DSCB of the volume involved. R Unable to record DELETE VVR. S The current generation number in ABR Model DSCB is zero. T FDRPRE00 GETMAINs an area that is freed by FDRPOST0 (the DADSM post processing exit). The area was not freed. U Unable to enqueue on SYSZTIOT in a multi-tasking address space. V GQSCAN failure. W FDRPOST0 (DADSM post-processing exit) was not invoked during a scratch. Action: This message may be accompanied by an IEC331I message. If necessary, contact BMC Support for assistance. |
FDRW92 | MAXIMUM NUMBER OF ERRORS EXCEEDED LOG TERMINATED Explanation: FDRPRE00, the ABR DADSM Preprocessing exit, has issued 100 FDRW90 error messages since the last time the exit was installed (usually the last IPL). No further messages are issued until you do a reIPL or reinstall the exit. |
FDRW93 | FDR DATA SET NOT FOUND EXIT ABNORMALLY TERMINATED COMP CODE= cccccccc Explanation: The ABR Data Set Not Found (DSNF) exit was entered for a data set whose name is contained in the preceding FDR316 message. ABR failed to recall the data set from the ARCHIVE backup. Either the ABR return code (in hex) or the abend code is displayed in this message. If the first two characters of “cccccccc” are “0F”, then the ATTACH SVC for FDRABR failed, and the remaining digits contains the hexadecimal return code from the ATTACH SVC. Action: Contact BMC Support for assistance. FDR DATA SET NOT FOUND EXIT BYPASSED RECALL - DSNOTFND ENQ HELD BY INIT TCB Explanation: This form of the FDRW93 message is issued by the ABR Data Set Not Found (DSNF) exit because it was entered while an ABR recall was already in progress. This may occur because some program that was invoked during a recall referenced a data set that was not on DASD. Action: The program involved probably fails, which may cause the ABR recall to fail as well. If necessary, contact BMC Support for assistance. |
FDRW94 | FDRPRE00 ESTAE RECOVERY ENTERED FOR ABEND Ssss Uuuuu location Explanation: This message is issued by FDRPRE00 when an unexpected condition occurs while trying to record a scratched or renamed data set in the ABR Scratch catalog. It documents the system “sss” or user “uuuu” abend that occurred. “location” indicates where the error occurred, either an offset within FDRPRE00 or “IN NON-IDP EXIT” if the error occurred in another DADSM exit from another vendor (or locally-written). Action: Contact BMC Support for assistance. |
FDRW99 | IF function IS CANCELLED resource MAY BE CORRUPTED - REPLY options Explanation: A z/OS CANCEL (C) command was issued against an executing FDR program. Some FDR programs contain CANCEL protection since a resource may be corrupted if the CANCEL is allowed to take place. The programs are FDRREORG, FDRCPK, and FDRARCH. “function” may be: FDRREORG, FDRCPK, or the FDRARCH function being executed. “resource” may be “DATA SETS”, “VOLUMES”, “VOL=vol”, or “ARCHIVE”. “options” contains the reply options available for this message. Action: Depending on the available reply options displayed, the operator can reply: S Stop at the end of the current operation. FDR completes processing of the data sets (FDRREORG and FDRARCH) or volumes (FDRCPK) currently being processed and no new work is started. I Ignore the CANCEL command. The FDR job continues normally. C Accept the CANCEL. The FDR job is canceled and the indicated resource may be corrupted. This should only be done in emergency situations or when the FDR job appears to be hung (not doing any I/O or consuming any CPU time). Another form of the FDRW99 message is issued to confirm your response. |