FDR V54L78 - Innovation Data Processing

More documents

Recommendations

Info

MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 Action: HAS INSUFFICIENT SPACE nnnnnn TRACKS – The data set is too small to hold all of the tracks to be restored. “nnnnnn” is the size of the pre-allocated data set. The next FDR111 message shows the number of tracks to be restored “tttttt”. This can also occur for data sets allocated by FDR if the CYL= or TRK= operands specified a size too small for the active tracks of the data set, or when DATA=ALL is specified with the RLSE or %FREE= operands. IS UNMOVABLE – The input data set is flagged as unmovable, which usually means that it contains location-dependent data and cannot be restored to different track addresses. The additional FDR111 messages show the extents that the data set occupied on the original volume; it must be restored to the same track addresses. IS TOO LARGE – A VSAM index component was larger than the index on the backup. It must be the same size. The data set is not restored. Scratch the pre-allocated data set. In most cases, simply re-run the restore and FDR allocates the data set properly. In some cases you may need to pre-allocate the data set with the allocations shown (for example, FDR cannot allocate an unmovable data set with more than three extents). If you get this message for a data set allocated by FDR (not pre-allocated), a possible cause is that the space request was reduced by STOPX37, ACC/SRS, or other space recovery software package. The installation must code the rules for such software so that allocations requested by programs whose names start with “FDR” are not altered. If desired, contact INNOVATION DATA PROCESSING for assistance. FDR120 INVALID DEVICE TYPE OR VTOC TOO LARGE INVALID DEVICE TYPE – FDR TERMINATED Reason: The disk device type is not one supported by this version of FDR or for ABR the VTOC may contain too many entries for an internal table. Action: An U0103 ABEND follows. Contact INNOVATION DATA PROCESSING for assistance. FDR121 Reason: ALTERNATE ERROR REASON=n ON TRACK CYL/HEAD=cccchhhh ASSIGNED TO PRIME CYL/HEAD=cccchhhh PRIME R0=cccchhhh FDR detected an error or unusual condition with the alternate track assignments on the disk volume being processed. The message displays the cylinder and head number of the failing alternate track in hex. “ASSIGNED TO PRIME” is printed if FDR can determine the prime track; it displays the cylinder and head of the prime track and the count field of record 0 (R0) on the prime track (the latter should point to the alternate track. This message is only produced when you are taking a backup to a sequential disk data set (such as Archiving to disk) or when you specify BUFNO=nn. The reason code “n” can be: 1 – I/O error occurred reading this alternate track. If the IOB in the mini-dump starts with “46008000”, the volume has no alternate tracks (this occurs with some disk subsystems and with VM mini-volumes). As long as there are no alternate tracks assigned on the volume, this message can be ignored. 2 – This alternate track is flagged as a defective alternate. FDR bypasses it. No corrective action is required. 3 – The alternate track is assigned to a prime track. The alternate home address does not have the flag byte set indicating that this is an alternate track. 4 – I/O error occurred reading the prime track assigned to this alternate. 5 – The prime track's home address flag byte did not indicate that this is a defective track. CHAPTER 100 – PAGE 100-22 –
MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 Action: 6 – The prime track's record zero (R0) did not point back to this alternate track. (PRIME R0=) contains data read. If the PRIME R0 points to another alternate track, this track has had an alternate assigned to it multiple times. NOTE: In many cases (especially reason 1), this message is informative and does not indicate an error unless other disk errors occur; in this case, the message does not set a non-zero return code or cause an ABEND. FDR continues, bypassing this alternate. If the prime data track is to be dumped, FDR may issue additional error messages. FDR121 REASON=1 can usually be ignored. Contact INNOVATION DATA PROCESSING for assistance. FDR122n statistics Reason: FDR displays status information at the successful termination of a backup or restore subtask. A second FDR122 is printed displaying the values under each header. The character “n” after the FDR122 indicates the format of the backup and is “N” (New) format or “S” (Split) format. These headers appear above the statistics values (some values are displayed only for backups, not for restores): BYTES – Number of bytes of data dumped to tape or read from tape (for DSF, all bytes read even if not restored.) DSK TRK – Number of disk tracks accessed to perform this function. T BLKS – Number of tape blocks written or read. On COPY this is an internal number of blocks passed from the dump task to the restore task. RESTART – Internal field. STIMERS – Internal number of STIMER commands issued. ERRS – Using BUFNO=MAX, this is the number of tracks in error. ACT DSK – Actual number of disk tracks dumped or copied. For FDRCOPY, it is the number of tracks read, which is not necessarily the number of tracks written. LOW – If not BUFNO=MAX, this is the lowest number of STIMERS issued on one cylinder. If BUFNO=MAX, this is the number of retries on tracks with data checks. Unless an FDR129 error message is displayed, the retries were successful. HGH – If not BUFNO=MAX, this is the highest number of STIMERS issued on one cylinder. If BUFNO=MAX, this is the number of count fields encountered with a CCHH that did not match the track it resides on; this is normal on a VM mini-disk but may indicate errors on other volumes. DEXCP – The number of disk EXCPs issued by this subtask to dump or restore this volume. This number may be less than number of EXCPs recorded by SMF. For FDRCOPY, this is the total of EXCPs on the input disk plus the number of tracks written to output disks; if FDRINSTANT is used to copy data sets (with FlashCopy, SnapShot, or TimeFinder), the output disk count does not represent actual EXCPs. NUMDS – Number of data sets processed in this backup. If an ABR incremental backup, this value includes the backup of the ABR Model DSCB. COMP KBYTE – The number of kilobytes (kB) (1024 bytes) the data was compressed by FDR software compression (COMPRESS=). This field is not displayed if software compression was not requested (FDR cannot display the results of hardware compression, e.g., IDRC)). It is displayed only for backups. NOTE: In the above two-line version of FDR122, some of the fields, particularly the byte counts are inadequate for large disk such as 3390-9 and larger; values printed are internally truncated and not usable for such disks. This FDR122 format is used only for backups that do not specify RTC=YES. The following multi-line format, used for RTC=YES backups and all restores, properly displays all statistics. CHAPTER 100 – PAGE 100-23 –
Page 1 and 2: MESSAGES AND CODES INTRODUCTION TO
Page 3 and 4: MESSAGES AND CODES FDR CONSOLE MESS
Page 17 and 18: MESSAGES AND CODES MESSAGES FROM FD
Page 19 and 20: FDR020 Reason: Action: MESSAGES AND
Page 21: MESSAGES AND CODES MESSAGES FROM FD
Page 27 and 28: MESSAGES AND CODES CHAPTER 100 - PA
Page 59 and 60: MESSAGES AND CODES CHAPTER 100 - PA
Page 73 and 74:
MESSAGES AND CODES MESSAGES FROM FD
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
MESSAGES AND CODES CHAPTER 100 - PA
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
FDR547 Reason: Action: MESSAGES AND
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
FDR939 Reason: MESSAGES AND CODES T
Page 123 and 124:
MESSAGES AND CODES MESSAGES FROM SA
Page 125 and 126:
100.6 COMPAKTOR MESSAGES (CPKNNNXX)
Page 127 and 128:
CHAPTER 100 - PAGE 100-127 - MESSAG
Page 129 and 130:
MESSAGES AND CODES COMPAKTOR MESSAG
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
CPK526E MESSAGES AND CODES COMPAKTO
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
MESSAGES AND CODES FDRREORG MESSAGE
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
MESSAGES AND CODES ABEND CODES 100.
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
100.9 WAIT STATE CODES FROM SAR WAI
show all

FDR V54L78 - Innovation Data Processing

Create successful ePaper yourself

Delete template?

Save as template?