FDR V54L78 - Innovation Data Processing

More documents

Recommendations

Info

MESSAGES AND CODES COMPAKTOR MESSAGES (CPKNNNXX) 100.6 Action: RECOVERY LOG FULL – The FASTCPK recovery log is full. More tracks were moved than can be recorded in the recovery log. Remove operands that cause many tracks to be moved (such as SIZEKEEP=0, OBJECT=MINEXTS, DATA=ALL, and POS=) and rerun. Can occur if the volume has few free space areas before COMPAKTion; you can add CPKFREEX=nn to avoid COMPAKTing such volumes. FASTCPK will go into recovery and return the volume to its previous state. INSUFFICIENT FREE STORAGE TRACKS - VOLUME NOT CHANGED – There are too few unallocated tracks on the volume for FASTCPK to successfully operate. The U0888 ABEND can be suppressed for this “reason” by adding UNABLE=IGNORE on the CPK statement. NO FREE DSCB FOR RECOVERY LOG - VOLUME NOT CHANGED – There are no free Format 0 DSCBs in the VTOC. FASTCPK requires at least one free DSCB for its recovery log. The U0888 ABEND can be suppressed for this “reason” by adding UNABLE=IGNORE on the CPK statement. NO FREE TRACK FOR RECOVERY LOG - VOLUME NOT CHANGED – There is no track on the volume that will be in free space both before and after the FASTCPK. FASTCPK requires at least one such track for its recovery log. The U0888 ABEND can be suppressed for this “reason” by adding UNABLE=IGNORE on the CPK statement. ALGORITHMS FAILED - VOLUME NOT CHANGED – None of the internal repositioning algorithms used by COMPAKTOR was able to develop a new layout for the volume. This usually occurs when you use POS= to position data sets or have a large number of unmovable or active data sets and COMPAKTOR was unable to find a location for a large data set. Reduce the number of POS= operands and rerun. The U0888 ABEND can be suppressed for this “reason” by adding UNABLE=IGNORE on the CPK statement. INSUFFICIENT STORAGE - VOLUME NOT CHANGED – The region was insufficient for FASTCPK. Increase the region size. I/O ERROR - VOLUME NOT CHANGED – An I/O error occurred on the output volume during initialization. I/O ERROR WRITING RECOVERY LOG - VOLUME NOT CHANGED – An I/O error occurred formatting the FASTCPK recovery log. NON-STANDARD DATA SET NAME - VOLUME NOT CHANGED – The VTOC of the volume contains a data set with a non-standard data set name, such as imbedded blanks or non-standard characters. FASTCPK cannot handle such data sets. An U0888 ABEND or non-zero return code will be issued at step end to call attention to the error. Except for RECOVERY LOG FULL, the volume has not been changed; if you can correct the error, rerun the job. For RECOVERY LOG FULL, COMPAKTOR reverses the tracks already moved, returning the volume to its original state. If the recovery fails, contact INNOVATION DATA PROCESSING for assistance. CPK555E VTOC TOO SMALL TO HOLD ALL DSCBS. INCREASE VTOC SIZE AND RETRY. Reason: On a COMPAKT-from-backup, you changed the size of the VTOC (SELECT ***VTOC,SIZE=nnn), but it is now too small for all the DSCBs that must be restored into it. Action: Reason: Action: Consult the summary map output by COMPAKTOR to determine the minimum VTOC size you require. Correct control statement in error and rerun. Unless you are sure that no new data sets are allocated on this volume, you should leave a generous amount of free space in the VTOC. VTOC SIZE OVERRIDE MUST BE RUN UNDER FDRPAS VTOC SIZE OVERRIDE NOT SPECIFIED UNDER FDRPAS The parameters passed to COMPAKTOR from the EXPANDVTOC keyword in FDRPAS were overridden by the user. Remove the COMPAKTOR overrides so the parameters specified by FDRPAS are used. CHAPTER 100 – PAGE 100-138 –
MESSAGES AND CODES COMPAKTOR MESSAGES (CPKNNNXX) 100.6 VTOC SIZE OVERRIDE IGNORED - NOT LARGER THAN nnnnnn TRACKS Reason: The parameters passed to COMPAKTOR from the EXPANDVTOC keyword in FDRPAS were too small. Action: Increase the number of tracks to expand the VTOC. CPK556W UNABLE TO IMPROVE VOLUME BY function Reason: COMPAKTOR cannot improve the volume by COMPAKTING or RELEASE. Perhaps it was recently COMPAKTed. For TYPE=RLSE, no space could be released. Action: An U0888 ABEND or non-zero return code may be issued at step end to call attention to the warning; if you do not want the ABEND/code, specify UNABLE=IGNORE on the CPK statement. Since no changes have been made to the volume, COMPAKTOR does not produce the “after” map. If COMPAKTing, the volume is not COMPAKTed, but a SIMULATION is done instead. If you wish to force COMPAKTOR to COMPAKT the volume specify any positioning statement. CPK557E UNABLE TO ALLOCATE SEQUENCED SET CONTAINING DATA SET -- dsname THE SEQUENCED SET IS PROBABLY TOO LARGE. Reason: After allocating all unmovable data sets and the VTOC, COMPAKTOR tried to allocate space for the sequenced set containing the named data set. It was unable to do this, because it could not find a single contiguous area large enough to hold the entire sequenced set. Action: Remove some data sets from the sequenced set and rerun. CPK558I COMPAKTOR WILL NOW DO AN FDR RESTORE OF THE VOLUME. Reason: COMPAKTOR restores the volume. CPK559W function BYPASSED DUE TO VOLUME reason Reason: COMPAKTION, RELEASE, or SIMULATION was bypassed on this volume because: NOT EXCEEDING CONDITIONAL COMPAKTION OPTIONS – One or more of the operands CPKFREEX, CPKDSNMX, CPKMULTX, or MINRLSE were specified, but none of the specified values were exceeded on the volume BEING EXCLUDED – The volume was named in an EXCLUDE entry in the COMPAKTOR Unmovable Table. Action: The volume is not COMPAKTed. CPK560W CPK DID NOT FIND REQUESTED VOL/STORGRP=name Reason: The VOL= or STORGRP= operands were specified, requesting dynamic allocation of the volume or SMS storage groups named. Either the storage group is not defined to SMS, or the volumes in the storage group or the volumes specified by VOL= were not mounted on any online disk device. Action: COMPAKTOR proceeds to the next requested volume, if any. If the volume serial or storage group name was misspelled or inaccurate, correct it and rerun COMPAKTOR. However, after processing all properly specified volumes, COMPAKTOR ends with an error U0888 unless SELTERR=NO was coded. CPK561E Reason: Action: DISK DYNAMIC ALLOCATION ERROR VOL=vvvvvv UNIT=uuuu COMP=comp CODE=code A dynamic allocation of disk volume “vvvvvv” on device “uuuu” failed with completion code “comp” and reason code “code”. These codes are documented in the IBM manual Authorized Assembler Services Guide. They can also be found in Appendix A of the ISPF online HELP. COMPAKTOR proceeds to the next requested volume, if any. CHAPTER 100 – PAGE 100-139 –
Page 1 and 2:
MESSAGES AND CODES INTRODUCTION TO
Page 3 and 4:
MESSAGES AND CODES FDR CONSOLE MESS
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
MESSAGES AND CODES MESSAGES FROM FD
Page 19 and 20:
FDR020 Reason: Action: MESSAGES AND
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
MESSAGES AND CODES CHAPTER 100 - PA
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88: MESSAGES AND CODES MESSAGES FROM FD
Page 95 and 96: MESSAGES AND CODES CHAPTER 100 - PA
Page 99 and 100: FDR547 Reason: Action: MESSAGES AND
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 135 and 136: CPK526E MESSAGES AND CODES COMPAKTO
Page 137: MESSAGES AND CODES COMPAKTOR MESSAG
Page 145 and 146: MESSAGES AND CODES FDRREORG MESSAGE
Page 163 and 164: MESSAGES AND CODES ABEND CODES 100.
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?