Return codes

FATS Return Codes

FATS will set the following completion or return codes:

0 Normal completion. No serious errors.

12 Serious errors have occurred and the RETCODE option has been specified (user abend U0888 is issued otherwise).

FATAR/FATSCOPY Return Codes

FATAR and FATSCOPY will set the following completion or return codes. Note that FATAR only sets return codes 4 and 8 if the SETNZRC operand is specified. If it is omitted, FATAR will set return code 0 for those conditions.

0 Normal completion. No serious errors.

4 Unusual conditions occurred, including: unable to load PRINT or ASCII translate table, EOD (end of data) mark encountered, FATSCOPY called for a new output tape during LASTAPE processing. However, the function ran to completion.

8 Unusual conditions occurred, including: missing DD statements, TAPEIN block count incorrect, VBS spanning error, unable to deblock/reblock, control statement not referenced, unable to catalog or rename output data set, tape management errors and other conditions. The function may not have completed; check the messages.

12 Serious errors have occurred and the RETCODE option has been specified (user abend U0200 or U0888 is issued otherwise). FATSCOPY will also set return code 12 if dynamic allocation or OPEN of an input tape fails.

68 One of the FATSCOPY interface modules is out of sync. This will usually occur if FATSCOPY loads a back-level version of FATRMM, FATTMS, FATCTT, FATZARA, or FATTLMS. If you recently installed a new release of FATSCOPY , verify that FATSCOPYisn't picking up a back level version of one of these modules from the linklist.

ABEND codes

FATS, FATAR, FATSCOPY , and FATAUDIT may issue the following user and system abend codes. Most abends will be accompanied by an explanatory message.

S0C3 A S0C3 abend in FATS, FATAR, or FATSCOPY occurs when an unexpected condition occurs to create a dump to help debug the problem. Save the dump and contact BMC support for assistance.

U0001 FATSCOPY was unable to obtain the amount of storage required for its internal tables. Add REGION=0M to your JOB or STEP statement and rerun the job. Contact BMC support Support for assistance if the problem persists.

U0047 The FATS, FATAR, or FATSCOPY program is not authorized. Refer to message FATS112 FATS MUST BE IN AN AUTHORIZED LIBRARY. PROGRAM TERMINATED.

U0100 For FATAR, the TAPEIN DD statement is missing, TAPEIN or TAPEOUT is not assigned to a tape unit, or an open failure on TAPEIN or TAPEOUT. For FATSCOPY , only 1 volume was selected for copying and an open error occurred when FATSCOPY tried to open the volume.

U0200 (FATAR only) Unrecoverable I/O error on TAPEOUT. If the RETCODE parameter is specified, a return code of 12 is issued instead of this abend.

U0300 (FATSCOPY and FATAUDIT only) No data sets were selected. This abend may occur if the input contains more than 1 file and MULTIFILE=YES wasn't specified on the COPY statement. It may also occur if all of the data sets that would have been selected were marked as Offsite. Check the information under the REASON heading in the Data Set Selection Report for the reason that a data set was not selected. Some of the REASON indicators are:

• 
  
  • NOTMINFO – No tape management information for volume.
  • INV DSN – Invalid data set name.
  • MISMATCH – The data set name and location recorded in tape management does not match the name and location recorded in the system catalog.
  • MULTIFIL – The data set was on a multifile volume and MULTIFILE=NO was used.
  • EXCLUDED – The data set matched one of the criteria on an EXCLUDE statement.
  • EDM – The data set is controlled by an external data manager.
  • DUPLICAT – The data set was already selected by a previous SELECT statement. This can occur when a data set is on a multivolume set, and SELECT ALLDSN statements have been used for more than one volume in the set.

U0401 Open error or I/O error on SYSIN.

U0402 Open error or I/O error on a PRINT data set.

U0403 The PARM passed to FATAUDIT was invalid.

U0404 FATAUDIT was unable to connect to the specified logger stream name. Check that the name is correct.

U0405 FATAUDIT was unable to read any data from the specified log stream. The stream may be empty.

U0406 FATAUDIT encountered an error reading data from the specified log stream.

U0407 FATAUDIT encountered an error processing the records from a log stream data block.

U0408 FATAUDIT was unable to properly disconnect from the log stream.

U0409 FATAUDIT was unable to connect to the log stream in write mode when PURGE was used.

U0410 FATAUDIT was unable to purge the log stream.

U0411 FATAUDIT was unable to open the AUDITOUT data set.

U0412 FATAUDIT was used with an empty Audit data set as input.

U0414 The MERGE keyword was used in a FATAUDIT job without specifying an AUDITOUT DD statement.

U0415 A FATAUDIT job step used both an AUDIT DD and a LOG= value.

U0416 A FATAUDIT job step used both a SYSIN DD and an EXEC PARM.

U0417 A FATAUDIT job did not have an AUDIT DD or LOG= PARM.

U0502 Error in FATS, FATAR, FATSCOPY, or FATAUDIT control statements.

U0888 Major errors on tape. For FATS, any condition causing abnormal completion of a FATS function (indicated by ABNORM in the FATS summary report). For FATAR and FATSCOPY, unrecoverable I/O errors on TAPEIN other than data checks, or MAXERR= or MAXTERR= values exceeded. If the RETCODE parameter is specified, a return code of 12 is issued instead of this abend.

U0913 FATS Security for FATS or FATAR (FATAR Security) has been implemented and the user did not have authority to perform the requested function.

Console Messages

The following write-to-operator (WTO) and write-to-operator-with-reply (WTOR) messages may be issued by FATS, FATAR, or FATSCOPY. They will be written to route code 3 (tape pool console).

FATSW01 REQUEST TO LABEL TAPE ON UNIT uuuu REPLY WITH SERIAL NUMBER

Reason: The OPERATOR parameter has been specified or the SAVLAB function found that the tape was not a labeled tape.

Action: Respond with a 1-to-6 character volume serial. FATS will left justify it, blank fill it, and label the tape on tape unit uuuu”.

FATSW02 REPLY EOJ/KEOJ/Kuuuu TO TERMINATE

Reason: FATS will always issue this WTOR at the start of every FATS run to allow the operator to control and terminate FATS.

Action: It will not be necessary to reply to this message unless:

1. MULT was specified without MAXVOLN=;
2. It is desired to terminate FATS before its normal termination; or
3. A particular tape must be halted. Valid responses are:

EOJ -- FATS will terminate after all tapes that are currently in progress have completed. Any pending tape mounts must be satisfied.

KEOJ -- FATS will halt all tapes in progress, cancel any pending mounts, and terminate with a U0888 abend or return code 12.

Kuuuu -- Where uuuu is the 3 or 4-digit address of a tape drive allocated to FATS. Any mount or tape in progress on that drive will be halted. If appropriate, another tape may be requested on the drive. Other drives allocated to FATS will not be affected. If uuuu is not a drive in use by FATS, it will be ignored. The FATSW02 message will be reissued.

FATSW03 FATS ANALYSIS OF TAPE ON UNIT=uuuu VOL=vvvvvv PERM ERRORS=ppppp TEMP ERRORS=ttttt

Reason: The WTO parameter has been specified. This message will be issued at the end of processing for each tape, giving unit uuuu , volume serial vvvvvv , and the total number of permanent and temporary errors ( ppppp and ttttt ). If a tape has major errors causing it to be halted prematurely, ppppp will be MAJOR .

FATSW04 MOUNT NEXT TAPE ON UNIT=uuuu VOL=vvvvvv

Reason: Issued by FATS to request mounting of another tape on tape unit uuuu . The volume serial vvvvvv may be an explicit serial or SCRTCH as appropriate.

Action: Mount the requested tape on unit uuuu .

FATSW05 FATS HAS STOPPED ON DATA CHECK ON UNIT=uuuu REPLY CONT, TERM, NOSTOP

Reason: The STOP or STOPNUM= parameters have been specified and a permanent data check has occurred. FATS stops to allow visual inspection of the tape at the point of the error.

Action: Inspect the tape on tape unit uuuu , if desired, re-ready the tape, and reply:

 CONT -- To continue certifying/verifying, stopping again on the next data check.

 TERM -- To terminate processing of the tape.

 NOSTOP -- To continue certifying/verifying without stopping on further data checks.

Note that if you remove the tape from the READY state to inspect it, you will probably be unable to re-ready it at the same spot and be forced to reply TERM .

FATSW06 PLEASE CLEAN UNIT=uuuu THEN (RE)MOUNT VOL=vvvvvv

Reason: The MAXCLEAN= or ERRCLEAN= parameters were specified. If MAXCLEAN=n then n tapes have been processed on unit uuuu since the last cleaning. If ERRCLEAN=n then more than n errors have occurred on unit uuuu (the message will say REMOUNT).

Action: Clean tape unit uuuu and mount or remount the specified volume vvvvvv .

FATSW07 INVALID RESPONSE TO TERMINATE MESSAGE -- RE-ENTER

Reason: The response to message FATSW02 was not EOJ , KEOJ , or Kuuuu . FATSW02 will be reissued.

Action: Reply with a valid response for message FATSW02.

FATSW08 VOL=vvvvvv MOUNTED,DSN=d...d,EXPDT=yydd, UNIT=uuuu REQUIRES VOL=xxxxxx-REPLY IGNORE, UNLOAD, TERM, SKIP UNIT=uuuu DSN NOT EXPIRED -- REPLY IGNORE, TERM, SKIP

Reason: The VALIDATE= parameter was specified to validate input and/or output labeled tapes with LABEL=(,BLP). Either the wrong volume was mounted or the expiration date on an output volume was not reached. In the first line of the message, uuuu is the tape unit, vvvvvv is the actual volume mounted, d...d is the data set name read from the tape, and yyddd is the expiration date. One of the next two formats of the message will be issued ( xxxxxx is the volume expected).

Action: Reply with:
IGNORE -- To ignore the error and accept the volume mounted.
UNLOAD -- To unload the volume and request mounting of another tape.
TERM -- To terminate FATS or FATAR.
SKIP -- To terminate this volume and go on to the next (FATS only).

FATSW11 FATAR FILE ffff OPERATION UNIT=uuuu,VOL=vvvvvv,BLOCKS=bbbbbb,PERMERRS=ppppp,TEMP ERRS=ttttt

Reason: The WTO parameter has been specified. The message will be issued at the end of processing each input file, giving file number ffff , unit uuuu , volume serial vvvvvv , input block count bbbbbb , and the total number of permanent and temporary errors ( ppppp and ttttt ) in that file. Operation will be ANALYZED ON (if TAPEOUT absent), COPIED FROM (if TAPEOUT present), or VERIFIED ON (if verifying TAPEOUT)

Action: None

FATSW12 FATAR FILE ffff OPERATION UNIT=uuuu,VOL=vvvvvv REPLY CONT, TERM, OR NOSTOP

Reason: The STOP parameter has been specified. The message will be issued at the end of processing each input file, giving file number ffff , unit uuuu , and volume serial vvvvvv. Operation will be ANALYZED ON (if TAPEOUT is absent), or COPIED FROM (if TAPEOUT present).

Action: Reply with:

CONT -- To continue with the next input file, stopping again at the end of that file
TERM -- To terminate processing of TAPEIN
NOSTOP -- To continue with the next file without stopping at the end of further files

FATSW13 REPLY IS: TEXT

Reason: Automatic reply to tape management message.

FATSW14 INVALID MODIFY COMMAND GIVEN: text....

Reason: Text was specified in MODIFY (F) id,text operator command. id is the FATS jobname for which the MODIFY command was intended. text is either QUIT or Kuuuu to terminate FATS when current tapes are done or to immediately terminate processing for tape unit uuuu .

Action: None. Command is ignored.

FATSW15 NO DSNTABLE DD. RESTART WILL FAIL. DO YOU WANT TO END JOB? YES/NO

Reason: The operator entered an f jobname,stop console command to stop the FATSCOPY job when it finishes copying the current data set. FATSCOPY requires a DSNTABLE DD in the JCL to create the data set needed to restart the job.

Action: A reply of 'YES' will stop the job, which will need to be restarted from the beginning. A reply of 'NO' will allow the job to continue until it finishes copying all of the remaining data sets. It is recommended to have a reply of 'NO'.

FATSW16 OPEN OF AUDIT DATA SET FAILED. DO YOU WANT TO CONTINUE? REPLY YES/NO

Reason: An AUDIT DD was found in the JCL, but FATSCOPY was unable to open the data set.

Action: A reply of 'YES' will allow the job to continue, but no audit records will be generated. A reply of 'NO' will end the job. It is recommended to have a reply of 'NO'.

FATSW17 FATSCOPY ABEND RECOVERY: STARTING FATSCOPY ABEND RECOVERY: ENDING

Reason: The operator entered a c jobname console command to stop the FATSCOPY job, or a FATSCOPY abend occurred. These messages indicate that the FATSCOPYroutine to process the interruption was executed. If you specified a DSNTABLE DD statement in the job, these messages should be accompanied by a FATSW18 message.

Action: Do not enter a CANCEL command while the recovery routine is running.

FATSW18 FATSCOPY ABEND RECOVERY: DSNTABLE DATASET WRITTEN

Reason: The operator entered an c jobname console command to stop the FATSCOPY job, or a FATSCOPY abend occurred. A DSNTABLE DD was present in the JCL, so FATSCOPY was able to create the data set needed to restart the job from the point where the job was interrupted. A FATS189 print message will also be issued.

FATSW19 **WARNING** NO AUDITOUT DD USED. LOGSTREAM DATA WILL *NOT* BE WRITTEN TO DISK.

Reason: The PURGE parameter was used in a FATAUDIT job, but no AUDITOUT DD statement was used. Information in the audit log stream created after the last time an AUDITOUT was written will be lost if the log stream purge is done.

FATSW20 **WARNING** PURGE PARM USED. ==>THIS WILL EMPT Y THE CONTENTS FROM THE LOG STREAM DATA SET<==DO YOU WANT TO PURGE THE LOG STREAM? REPLY YES/NO

Reason: The PURGE parameter was used in a FATAUDIT job. The operator must confirm that a purge is to be done. A purge permanently empties the audit information in the log stream. If an AUDITOUT DD statement is used, the data from the log stream will be written to the AUDITOUT dataset before the purge is done.

Action: Reply YES or NO.

FATSW21 PURGE PARAMETER WILL BE IGNORED.

Reason: The operator replied NO to the FATSW20 message.

Action: The log stream data will not be purged.

FATSW22 FATSCOPY UNABLE TO ESTABLISH ESTAE ROUTINE

Reason: FATSCOPY could not activate its error recovery routine.

Action: If an operator CANCEL is issued or an abend occurs, FATSCOPY will not be able to save the DSNTABLE data set which is normally used to restart an interrupted job.

FATSW99 SHOULD DUMP BE TAKEN? YES/NO

Reason: DUMP=ASK was specified on the FATAR or FATSCOPY statement and an ABEND that normally does not generate a dump was generated.

Action: The operator can reply YES or NO to indicate if an ABEND dump should be taken. A SYSUDUMP or SYSABEND DD statement must be present in the step JCL.

Print Messages

FATS, FATAR, and FATSCOPY may issue the following messages to their data sets (SYSPRINT or SYSPRINx).

FATS001 TAPEIN DD STATEMENT MISSING

Reason: The DD statement for TAPEIN is missing from the job step JCL.

Action: FATAR is terminated with a U0100 abend. Correct the JCL and resubmit the job.

FATS002 TAPEIN DEVICE IS NOT A TAPE UNIT

Reason: The DD statement for TAPEIN does not reference a supported tape unit type.

Action: FATAR is terminated with a U0100 abend. Correct the JCL and resubmit the job.

FATS003 TAPEIN COULD NOT BE OPENED

Reason: The open of the input tape on TAPEIN failed.

Action: Program FATAR is terminated with a U0100 abend. Check the printout for operating system messages indicating the cause.

FATS005 TAPEOUT DEVICE IS NOT A TAPE UNIT

Reason: The DD statement for TAPEOUT does not reference a supported tape unit type.

Action: FATAR is terminated with a U0100 abend. Correct the JCL and resubmit the job.

FATS006 TAPEOUT COULD NOT BE OPENED

Reason: The open of the output tape on TAPEOUT failed.

Action: FATAR is terminated with a U0100 abend. Check the printout for operating system messages indicating the cause.

FATS010 CONTROL CARD ERROR -- REASON x

Reason: A syntax or usage error has been detected in the control statement printed immediately preceding the message. Only one FATS010 message will be printed for each input statement (multiple errors will not be diagnosed). x is a character indicating the type of error detected:

1 – Open failed for the control statement data set (SYSIN or SYSINx).

2 – Control statement is completely blank.

3 – An invalid operation keyword was found on the control statement.

4 – More than one ANALYZE/COPY/SIM control statement was found.

5 – The control statement required at least one keyword parameter but did not contain one.

6 – A specific keyword parameter was required on the control statement but was not found; a required parenthesis was missing; a keyword was misspelled; or there is no tape management information because the tape management interface was not installed with FATZAPOP (refer to Activating the Tape Management Interface).

7 – An ANALYZE/COPY/SIM control statement was required, but not found.

8 – T= on TABLE statement in error. Letter previously used.

9 – A numeric value for a keyword parameter exceeds the allowed maximum for that keyword.

A – A value for a keyword parameter was zero or non-numeric.

B – Continuation card required but not found.

C – B= keyword in error. Block range specified but not in ascending order.

D – D=, V=, or S= keyword in error. Length of data is more than 256 bytes or characters.

E – D=, V=, or S= keyword in error. Data field must contain at least 1 byte or character. F – ENDAFTER=
keyword error.

G– Control statement table is too small to contain all information from the control statements present.
Increase the table size via the EXEC JCL statement PARM field.

H– Error in X' or C’ data: no closing apostrophe, invalid hex digits, or an odd number of hex digits.

J– Invalid data string. Must start with X ' or C'

K– Error in T= keyword. On SCAN statement, must be A-Z and defined in a previous table statement (except
for P and Z). On table statement, must be A-O or Q-Y and not previously used.

L– EXITNAME was not found, or length of EXITNAME is zero.

M– Data set name specified by NEWN= on a RENAME statement is invalid.

N– Data set name mask specified by NEWI= or CATDSN= on a SELECT, EXCLUDE or RENAME statement is
invalid.

O– Invalid mask on SELECT statement or in HSMxxxMASK= operands.

P– Invalid volume list or mask; invalid range; conflicting selection parameters (such as DSN= and CATDSN=); or SELECT CATDSN and SELECT ALLDSN statements both present.

Q– Invalid value for ABRINDEX= operand.

R – Invalid value for OPCAP= operand.

S– Conflicting operands on the COPY statement.

T– Invalid esoteric name specified in the VIRTUNIT= or UNITIN= operands.

U– Conflicting RENAME statements: more than one RENAME applies to the same file; or RENAME specified when image copy requested.

V– LASTAPE data set name invalid.

W– Invalid keyword specified on EXCLUDE. EXCLUDE accepts only CATDSN, DSN, VOL, and DEVTYPE operands.

X – EXLASTPGM=, EXLASTJOB=, or THRESHOLD= specified, but is not valid for the tape management
system in use.

Y– Invalid value specified in the GROUPBY= operand.

Z– Invalid value specified in the VIRTTYPE= operand, or PHYSVOL= or ALLPHYS= has been specified without also specifying VIRTTYPE=.

Action: FATAR/FATSCOPY /FATAUDIT will abend with a U0502 abend code after all control statements have been scanned.

FATS011 **INVALID CONTINUATION CARD

Reason: FATSCOPY detected an invalid continuation on an input statement.

Action: FATSCOPY will abend with a U0502 abend code. Correct the errors and re-execute.

FATS013 ONE OR MORE ERRORS DETECTED -- FATAR TERMINATED

Reason: Message FATS010 was issued for one or more control statement errors.

Action: FATAR will abend with a U0502 abend code. Correct the errors and re-execute.

FATS014 NO CONTROL CARD DATASET. DEFAULTS ASSUMED

Reason: No SYSIN DD statement for control statement input was present in the job step JCL; if FATAR was invoked by FATS, no SYSINx DD was present.

Action: All defaults are assumed for all ANALYZE statement parameters. If FATAR was invoked by FATS, any FATAR parameters specified in FATS statements will override these defaults.

FATS016 ANALYSIS TERMINATED DUE TO MAJOR ERROR

Reason: An unrecoverable hardware error has occurred on the input tape drive or channel. Preceding messages will give details of the error.

Action: FATAR is terminated with a U0888 abend or return code of 12. Contact BMC support if you need assistance in determining the cause.

FATS016 **COPY TERMINATED DUE TO MAJOR ERROR VOL=volser DSN=dsn

Reason: An unrecoverable hardware error has occurred on the input tape drive or channel. Preceding messages will give details of the error.

Action: FATSCOPY will terminate the current data set and select the next input data set.

FATS017 MAXIMUM ERRORS EXCEEDED -- FATAR TERMINATED

Reason: The number of unrecoverable data checks exceeded the MAXERR= parameter, or the number of recoverable data checks exceeded the MAXTERR= parameter.

Action: FATAR is terminated with a U0888 abend or return code of 12.

FATS017 MAXIMUM ERRORS EXCEEDED VOL=volser DSN=dsn COPY TERMINATED

Reason: The number of unrecoverable data checks exceeded the MAXERR= parameter, or the number of recoverable data checks exceeded the MAXTERR= parameter.

Action: FATSCOPY will terminate the current data set and select the next input data set.

FATS019 pgmname MUST BE IN AN AUTHORIZED LIBRARY. PROGRAM TERMINATED

Reason: FATAR and FATSCOPY must be executed as APF authorized programs. Either the program library containing FATAR or FATSCOPY was not marked as an APF authorized library on your z/OS system, or your STEPLIB or JOBLIB DD statement has nonauthorized libraries concatenated to the FATAR/FATSCOPY program library, or FATAR/FATSCOPY has been relinked as nonauthorized (AC=0).

Action: FATAR or FATSCOPY will terminate with a U0047 ABEND.

FATS020 ANALYSIS TERMINATED AT TAPEMARK SEQUENCE

Reason: If labels are being processed by FATAR, two consecutive tape marks were read after a label file. If labels are not processed and NUMFILES=0 was specified or defaulted, two consecutive tape marks were read.

Action: Processing of the input tape is completed.

FATS020 **COPY COMPLETE. ALL VOLUMES PROCESSED

Reason: All of the volumes and data sets selected for copying have been processed. A zero return code indicates that FATSCOPY has copied all of the data sets, cataloged the output data sets, updated tape management and expired the inputs, if necessary. A non-zero condition code indicates errors occurred during the copy process, that may have resulted in some data sets not being copied, cataloged, or updated in tape management.

Action: Processing of the input data sets is completed.

FATS021 ANALYSIS TERMINATED BY EOV LABELS DETECTED IN LABELS=NO MODE

Reason: If labels are not being processed and NUMFILES=0 was specified or defaulted, FATAR has detected what appear to be IBM or ANSI EOV labels.

Action: Processing of the input tape is completed.

FATS022 ANALYSIS TERMINATED AFTER SPECIFIED NUMBER OF FILES

Reason: NUMFILES=n was specified, and n logical files have been read.

Action: Processing of the input tape is completed.

FATS023 ANALYSIS TERMINATED BY ENDAFTER OPTION

Reason: The file and block specified by the ENDAFTER= parameter was read.

Action: Processing of the input tape is completed.

FATS024 ANALYSIS TERMINATED BY LOGICAL END OF FILE

Reason: FATAR attempted to switch to a new input tape volume (due to EOV labels being read, or reaching end-of-file in LABELS=OS mode), but no more volumes were given.

Action: Processing of the input tape is completed.

FATS025 ANALYSIS TERMINATED BY OPERATOR REQUEST

Reason: The operator replied TERM to the FATSW12 message or FATSW08 message.

Action: Processing of the input tape is halted.

FATS026 TAPEIN DATA SUCCESSFULLY COPIED TO TAPEOUT VOLUME VVVVVV

Reason: The TAPEOUT DD statement was present, and reading of TAPEIN data completed successfully. All input data not DROPPED has been written to TAPEOUT. The last (or only) volume of TAPEOUT was "vvvvvv”.

Action: None.

FATS027 UNLABELED TAPEOUT REQUIRED MORE THAN ONE VOLUME -- VERIFY CANCELLED

Reason: TAPEOUT is an unlabeled tape (LABEL=(,NL) or (,BLP)), the VERIFY parameter was specified, and TAPEOUT overflowed to more than one volume.

Action: FATAR cannot verify multi-volume unlabeled tapes. The VERIFY will not be performed.

FATS028 ANALYSIS TERMINATED DUE TO INVALID LABEL

Reason: Labels were being processed on TAPEIN, but a valid IBM standard or ISO/ANSI or user label was not read when one was expected.

Action: The invalid data will be printed, and FATAR will be terminated with a U0888 abend or return code 12

FATS030 EOT ON TAPEOUT BUT VOLUME SWITCH NOT ALLOWED -- FATAR TERMINATED

Reason: Labels are being processed on TAPEIN, the current file being copied contains user labels, and the SUPULAB parameter (suppress user labels) was not specified. User labels may be required with the EOV (end-of-volume) and header labels written when the file crosses volumes, but FATAR has no way to generate user labels acceptable to the user application.

Action: FATAR is terminated with a U0888 abend or return code 12.

FATS033 PERMANENT I/O ERROR ON TAPEOUT -- function TERMINATED

Reason: “function” may be FATAR or FATSCOPY, both of which use standard system error recovery on TAPEOUT. An uncorrectable I/O error occurred; messages will follow to detail the error that occurred.

Action: The function will be terminated with a U0200 abend or return code 12. Consult the messages and operating system messages for details of the error. Errors may be avoided by cleaning the TAPEOUT tape drive, and using an output tape certified by FATS or other means.

FATS034 NOISE BLOCK HAS BEEN READ VOL=volser DSN=dsn

Reason: A data check block too small to be considered a valid data block has been read; this will not occur on tape cartridge drives. The volume and dsn are displayed only by FATSCOPY.

Action: No recovery attempts will be made. The block will be immediately flagged as a permanent data check.

FATS035 INCOMPATIBLE TAPE FORMAT. DSN=dsname, VOL=volser

Reason: The tape drive has reported that it is not capable of reading the input tape. This may occur when a tape written in a certain format (such as 3490E or encrypted format) is mounted on a drive that is not capable of reading that format. This error may also be caused by an uninitialized tape. The volume and dsn are displayed only by FATSCOPY.

Action: FATAR will terminate with a U0888 abend. FATSCOPY will continue with the next input data set. Determine the actual format of the tape, and change the TAPEIN DD statement to allocate an appropriate tape drive.

FATS036 BLOCK GREATER THAN nnnnnn BYTES READ -- FATAR TERMINATED

Reason: A tape block longer than nnnnnn bytes (as specified by the BLKSIZE= parameter, default 64K) has been read. This form of the FATS036 message is produced only if an output tape is being written, i.e., a TAPEOUT DD statement is present.

Action: FATAR is terminated with a U0888 abend.

FATS036 ** WARNING ** BLOCK GREATER THAN nnnnnn BYTES READ -- BYTE COUNTS WILL BE INCORRECT

Reason: A tape block longer than nnnnnn bytes (as specified by the BLKSIZE= parameter, default 64K) has been read. This form of the FATS036 message is produced when no output tape (TAPEOUT DD statement) is present.

Action: The excess data is discarded, and FATAR continues with the next block. However, byte counts printed will not include the excess bytes.

FATS037 TAPE LABELS IN ISO/ANSI FORMAT -- TRANSLATED TO EBCDIC

Reason: FATAR has detected that the labels on TAPEIN are in ISO/ANSI format ( ANSI labels ).

Action: The labels will be translated to EBCDIC for printing or processing. Also, the associated data file is assumed to be in ISCII/ASCII and will be translated to EBCDIC.

FATS038 DATA FILE IN ISCII/ASCII -- TRANSLATED TO EBCDIC

Reason: The current data file is assumed to be in ISCII or ASCII code. This occurs when DCB=OPTCD=Q is specified on the TAPEIN DD card, or when ISO/ANSI labels were detected on TAPEIN by FATAR.

Action: All data blocks in the file will be translated to EBCDIC for printing and processing.

FATS039 **WARNING** BLOCK LENGTH GREATER THAN BLOCKSIZE OF bbbbbb DSN=dsname, VOL=volser

Reason: A block was read whose length is greater than the blocksize bbbbbb of the current file (extracted from the header labels of the file, or given on the TAPEIN DD statement if labels are not processed). The volume and dsn are displayed only by FATSCOPY.

Action: None. Unless dropped or modified, the block will be written to TAPEOUT as read. For FATSCOPY customers, if you want to force FATSCOPY to abend when this message is issued, apply custom zap C-49.0088.

FATS040 TAPEIN IS NOT LABELED -- LABELS=NO ASSUMED

Reason: The LABELS=YES parameter was specified or defaulted, but FATAR did not find valid IBM or ISO/ANSI labels in the first file read.

Action: FATAR will proceed as if LABELS=NO were specified.

FATS042 TAPEIN TRAILER BLOCK COUNT OF bbbbbb IS INCORRECT

Reason: The EOF1 or EOV1 trailer label on a labeled TAPEIN file contained a block count bbbbbb that did not match the number of blocks actually read from the file by FATAR. The actual block count is found in the end of file message preceding this message.

Action: None.

FATS044 END OF OUTPUT TAPE vvvvvv AFTER nnnnnnnnnn BLOCKS -- NEW VOLUME REQUESTED

Reason: The end-of-tape reflector (tape indicate) was detected on TAPEOUT volume "vvvvvv” after the “nnnnnnnnnn”th block of the file being copied was written to the output tape.

Action: EOV labels are written on vvvvvv (if labeled), and a new output volume is requested.

FATS046 * * I/O ERROR--> ECB=eeeeeeee ECB rc description

Reason: This is the first of several messages issued as the result of a non-data check error on TAPEIN or any error on TAPEOUT. For diagnostic purposes it includes the event control block (ECB, 4 bytes) in hexadecimal along with the description associated with the ECB reason code (1st byte of ECB).

Action: Other messages will indicate whether FATAR can continue or must terminate, depending on the nature of the error. Appropriate manufacturer's space should be consulted to determine the cause of the error. Contact BMC support if you need assistance.

FATS047 * * I/O ERROR--> CSW=wwwwwwww wwwwwwww csw status desc

Reason: This is one of several messages issued as the result of a non-data check error on TAPEIN or any error on TAPEOUT. For diagnostic purposes it includes the channel- status word. (CSW, 8 bytes) in hexadecimal along with the description associated with the unit and channel status bytes of the CSW (bytes 4 and 5).

Action: See message FATS046.

FATS048 * * I/O ERROR--> CCW=cccccccc cccccccc ccw channel cmd

Reason: This is one of several messages issued as the result of a non-data check error on TAPEIN or any error on TAPEOUT. For diagnostic purposes it includes the channel- command word (CCW, 8 bytes) in hexadecimal along with the channel command associated with the command code byte of the CCW (byte 0).

Action: See message FATS046.

FATS049 * * I/O ERROR--> SENSE ssss EXTENDED SENSE ee...ee error description

Reason: This is one of several messages issued as the result of a non-data check error on TAPEIN or any error on TAPEOUT. For diagnostic purposes it includes the sense bytes (ssss, 2 bytes) in hexadecimal. If available, the extended sense (up to 32 bytes) is displayed. If FATAR or FATSCOPYcan determine the cause from the sense and extended sense, a text description of the error is displayed.

Action: See message FATS046.

FATS050 * * I/O ERROR OCCURRED DSN=dsname,VOL=volser

Reason: This is one of several messages issued as the result of a non-data check error on TAPEIN or any error on TAPEOUT. For diagnostic purposes it includes identifying information for the data set being processed when the error occurred.

Action: See message FATS046.

FATS051 RECORD rr BYTE bb LENGTH ll INVALID xxxx DATA FIELD

Reason: A SCAN statement has detected data that does not meet the user-specified criteria. rr is the record number within the current block ( RECORD rr will not appear if deblocking is not being done). bb is the location of the invalid field within the indicated record or block (relative to 1). ll is the length of the field. xxxx will be ZONED , PACKED or TYPE t (where t is a table ID).

Action: None.

FATS052 SCAN FIELD NOT IN RECORD -- SCAN TERMINATED FOR THIS RECORD

Reason: A SCAN statement applied to a block or record, but the location to be scanned (P= parameter) was beyond the end of the block/record.

Action: SCAN not performed. Check the SCAN parameters.

FATS053 BLOCK LENGTH ZERO -- BLOCK NOT KEPT

Reason: A KEEP statement applied to an input block, but the length of the data read was zero (probably due to a data check).

Action: The block will not be written to TAPEOUT.

FATS054 BLOCK LENGTH CHANGED WHILE IN LOGICAL RECORD MODE -- DEBLOCKING TERMINATED

Reason: FATAR was deblocking input blocks into individual records, but a KEEP statement changed the length of a block.

Action: The block will not be deblocked.

FATS055 **WARNING** MORE THAN 1 VOLUME IN SET. VOL=volser. CAT=RECAT WILL BE IGNORED.

Reason: FATAR IMAGE copy was specified with CAT=RECAT, and the input data set is on more than one volume.

Action: The data set will not be recataloged.

FATS055 **WARNING** TAPE MANAGEMENT NOT ACTIVE. CAT=RECAT WILL BE IGNORED.

Reason: FATAR IMAGE copy was specified with CAT=RECAT, and there is no active tape management system.

Action: The data set will not be re-cataloged.

FATS056 RECORD TOO SHORT--NO DATA REPLACED

Reason: A record or block is too short to contain the data specified on a REPLACE statement.

Action: REPLACE not performed. Check the REPLACE parameters.

FATS057 DATA RECOVERED -- BLOCK NOT MODIFIED

Reason: A Modification/Scan statement with the DCK parameter applied to a data block, but the block did not have a permanent data check.

Action: The Modification or SCAN will not be performed.

FATS058 RECORD nnnnn HAS BEEN DROPPED

Reason: In response to a DROP statement with a record number indicated, record nnnnn has been deleted from the current block.

Action: The block will be compressed to eliminate the deleted record. If the record format is variable, the block length will be updated.

FATS061 RECFM/LRECL NOT GIVEN -- FILE ASSUMED UNBLOCKED

Reason: The record format (RECFM) and logical record length (LRECL) for the current file are not available from either the TAPEIN DD statement or TAPEIN header labels.

Action: FATAR is unable to deblock the current file into logical records and will treat each block as a single record. If deblocking is desired, specify RECFM and LRECL on TAPEIN and re-execute FATAR.

FATS062 DEBLOCKING ANSI SPANNED RECORDS NOT SUPPORTED -- UNBLOCKED ASSUMED FOR THIS FILE

Reason: The TAPEIN DD statement or TAPEIN header labels specifies ANSI variable-length spanned records (record format DS or DBS). FATAR does not support deblocking of ANSI spanned records.

Action: Unblocked (record format U) assumed.

FATS063 BLOCK INVALID FOR RECFM/LRECL IN USE--DEBLOCKING TERMINATED

Reason: Blocks in the current file were being deblocked into logical records, but the current block cannot be deblocked using the record format and logical record length provided by the TAPEIN DD statement or TAPEIN header labels. For fixed length records, the block is not an exact multiple of the record length. For variable length records, the record descriptor words (RDW) may be invalid or indicate a length greater than the block size.

Action: The current block will be treated as unblocked. If the record format and length given are correct, the block is invalidly formatted; if not, specify the correct RECFM and LRECL on TAPEIN and re-execute FATAR.

FATS064 FILE NOT ELIGIBLE FOR REBLOCKING -- REBLOCKING SUPPRESSED FOR THIS FILE

Reason: REBLOCK= was specified, but the current file cannot be reblocked for one of the following reasons.

1. The record format is not fixed or variable.

2. The record format is variable spanned.

3. The blocksize is zero.

4. The logical record length is zero (if the record format is FB or VB).

5. The blocksize is greater than the MAXRBLK= parameter, if specified.

6. The blocksize of the input data set is equal to the blocksize requested on the REBLOCK operand. The output data set will not be reblocked.

7. The output blocksize is less than the input blocksize.

Action: The file will be copied without reblocking.

FATS065 RECORD LENGTH TOO LARGE FOR REBLOCKING -- REBLOCKING SUPPRESSED FOR THIS FILE

Reason: REBLOCK= was specified, but the logical record length of the current file is larger than the specified reblocking block size.

Action: The file will be copied without reblocking.

FATS066 THIS FILE WILL BE REBLOCKED TO A BLOCKSIZE OF nnnnn

Reason: REBLOCK= was specified, and the current file can be reblocked. The new block size nnnnn will be equal to the reblocking block size for variable length files, or the next lower multiple of the record length for fixed length files

Action: The file will be copied and reblocked.

FATS067 INPUT DEBLOCKING ERROR WHILE REBLOCKING -- FATAR TERMINATED

Reason: REBLOCK= was specified, and the current file was being reblocked, but an error occurred extracting logical records from the current input block; message FATS063 will precede this message.

Action: Since the labels on the output tape reflect the new blocksize, FATAR will be terminated with a U0888 abend or return code of 12. Specify the correct RECFM and LRECL on TAPEIN and re-execute FATAR.

FATS068 INPUT RECORD TOO LARGE WHILE REBLOCKING -- FATAR TERMINATED

Reason: REBLOCK= was specified, and the current file was being reblocked, but an input logical record was larger than the output reblocking blocksize.

Action: Since the labels on the output tape reflect the new blocksize, FATAR will be terminated with a U0888 abend or return code of 12. Specify a larger value for REBLOCK= and re- execute FATAR.

FATS069 RECORD nnnnn SPANNING ERROR -- xxxxx OF SEGMENT MISSING

Reason: The TAPEIN JCL or tape labels specifies variable spanned records for the current file, and FATAR has detected an incomplete spanned record. xxxxx will be START if the end of a record was found without a corresponding beginning, or END if a new record was found before a previous spanned record was complete. nnnnn is the record number within the current block where the error was found. If xxxxx is END , the error is probably actually in the preceding block(s).

Action: An additional FATAR run may be required to print the appropriate blocks and determine which records are truly in error. Another run using FATAR REPLACE statements to fix the spanning flags, or DROP statements to delete the partial records, may be used to fix the tape.

FATS070 CONTROL CARD TABLE SIZE IS n BYTES

Reason: This message is always printed to document n , the size of the FATAR control statement storage table. This size defaults to 32768 but can be increased by the SIZE= parameter in the FATAR EXEC JCL statement PARM=.

Action: If this FATAR execution receives message FATS010 reason G, increase the table size.

FATS071 TAPE BUFFER SIZE IS nnnnnn BYTES

Reason: This message is always printed to document the size of the FATAR/FATSCOPY TAPEIN read buffer. The default size is 262144 or 256K bytes but can be reduced by use of the BLKSIZE= parameter.

Action: Any blocks on TAPEIN exceeding nnnnnn +1 in length will cause an error. If FATAR is creating an output tape, it will terminate, otherwise it will continue (see message FATS036).

FATS072 TAPEIN DATA WILL BE COPIED TO TAPEOUT

Reason: The TAPEOUT DD statement is present.

Action: All files and data on TAPEIN will be copied to TAPEOUT unless DROPPED by data checks or FATAR control statements.

FATS073 **WARNING** BACKUP OF ARCHIVE CONTROL FILE HAS SAME NAME AS ARCHIVE CONTROL FILE. OUTPUT DATA SET NOT CATALOGED.

Reason: .ARCBACKUP=DSF was specified without a corresponding ARCB1DSN= keyword.

When ARCB1DSN isn't specified, FATSCOPY creates the data set name for the backup of the Archive Control file by replacing the '.ARCHIVE' qualifier in the Archive Control File data set name with a '.ARCBKUP' qualifier. If FATSCOPY doesn't find a '.ARCHIVE' qualifier, it creates the backup with the same data set name as the Archive Control File and the output data set will not be cataloged.

Action: A return code '8' will be issued.

FATS074 ** WARNING ** CONTROL CARD NUMBER n WAS NEVER REFERENCED OR REPLACE- VERIFY NEVER SATISFIED

Reason: This message is issued at FATAR/FATSCOPY termination to warn of control statements that have never been acted upon. Either the file number or block number referenced on the statement was never encountered on TAPEIN, or, for a REPLACE statement with a V= or S= parameter, the VERIFY or SCAN never caused any data to be replaced.

Action: Review the control statements to be sure that they were coded correctly. Review the FATAR/FATSCOPY output to be sure that the desired files and blocks were processed.

FATS075 SPECIAL EXPIRATION OF yydd1 DETECTED, TAPEOUT EXPDT=yydd2

Reason: FATAR read labels containing an expiration date yydd1 recognized as having a special purpose, i.e., 98000 or 99000.

Action: If copying to TAPEOUT, the output file will have expiration yydd2 (98000 is normally changed to 00000, but some tape management systems will change this to a default retention).

FATS076 TAPE MANAGEMENT text

Reason: Displays information about the FATAR Tape Management interface. If no supported tape management system was detected or an interface error occurred, this is indicated. Otherwise it will identify the type and level of the tape management system, and information about the input tape extracted from that TMS.

Action: None, unless an error occurs. If necessary, contact BMC support.

FATS077 EOT ON TAPEOUT BUT FATAR WILL ATTEMPT TO WRITE nnn MORE BLOCKS

Reason: During an image copy (LABELS=NO), FATAR detected the logical End-of-Tape (EOT) on the output tape, and EOTBLOCKS= was specified or defaulted.

Action: Since an image copy must put all the input data on a single output volume, FATAR will attempt to write nnn additional blocks beyond logical EOT.

FATS078 EOT ON TAPEOUT, FATAR WROTE nnn MORE BLOCKS BUT COPY NOT COMPLETE

Reason: During an image copy using LABELS=NO, FATAR wrote extra blocks beyond logical EOT, but the allowable block count was reached before all input data was copied.

Action: Since an image copy must put all the input data on a single output volume, this copy is not complete. If nnn is less than 999, you can attempt to complete it by increasing the EOTBLOCKS= value, or using a longer output tape.

FATS079 PHYSICAL EOT ON TAPEOUT AFTER nnn EXTRA BLOCKS WRITTEN, COPY INCOMPLETE

Reason: During an image copy using LABELS=IMAGE, FATAR wrote extra blocks beyond logical EOT, but physical EOT was detected before all input data was copied.

Action: Since an image copy must put all the input data on a single output volume, this copy is not complete. You can attempt to complete it by using a longer output tape.

FATS080 UNABLE TO LOAD CHARTAB=table PRINT TRANSLATE TABLE, DEFAULT FATCHRTB WILL BE USED.

Reason: CHARTAB= was specified with the name of a load module containing an alternate print table, but FATAR was unable to successfully LOAD that module.

Action: Check the job log for IBM messages indicating why the module could not be loaded.
For this run the standard FATAR translate table was used.

FATS081 TAPE LABELS IN ISO/ANSI FORMAT - TRANSLATED TO EBCDIC FOR PRINTING ONLY

Reason: ANSI labels were detected on the input tape. They are translated to EBCDIC for printing purposes only.

FATS082 READ BUFFER NOT AVAILABLE - USE DUMP=YES OPTION

Reason: This is an internal error. Contact BMC support for assistance.

FATS083 **WARNING** tapedd REWOUND TO LOAD POINT FOR IMAGE COPY

Reason: An image copy was requested (LABELS=IMAGE for FATAR, IMAGE for FATSCOPY), but tapedd (TAPEIN or TAPEOUT) was not positioned at the load point. For both FATAR and FATSCOPY, this could be because a value greater than 1 was specified in the LABEL= parameter on the DD statement in the JCL. For FATSCOPY only, LABEL=(,SL) was specified (or defaulted) on the TAPEOUT DD.

Action: The tape was rewound to the load point (beginning of the tape) to copy the entire tape, including the volume and header labels for the first file.

FATS084 **WARNING** MORE THAN ONE INPUT VOLUME FOUND DURING IMAGE COPY. COPY STOPPED AT END OF FIRST VOLUME

Reason: An image copy was requested (LABELS=IMAGE) but the TAPEIN JCL specified more than one volume serial. Image copy can process only one volume at a time.

Action: The additional volume serials were ignored. If they must also be copied, you must submit separate LABELS=IMAGE steps for each one.

FATS085 **WARNING** NUMFILES SET TO 0 FOR IMAGE COPY

Reason: An image copy was requested (LABELS=IMAGE) but NUMFILES= (NF=) was specified with a value other than 0.

Action: Since image copy must copy the entire tape, NUMFILES=0 was forced.

FATS086 **WARNING** NO TAPEOUT DD FOUND WHEN LABELS=IMAGE SPECIFIED

Reason: An image copy was requested (LABELS=IMAGE) but no TAPEOUT DD was provided to specify the output tape.

Action: Processing will continue, allowing you to dry run the image copy, but the step must be rerun with a TAPEOUT DD statement to actually copy the tape.

FATS087 **WARNING** CATALOG OF OUTPUT TAPE FAILED. COMP=comp DSN=dsn

Reason: Cataloging of the indicated output data set was requested by the CAT=YES or CAT=RECAT parameters, but the attempt to catalog the indicated data set failed. comp is the return code from CAMLST CATALOG, which will usually be 0008. For CAT=YES this may indicate that the output data set name is already cataloged.

Another common cause is attempting to catalog into the master catalog, usually because you have used a output data set name that is not assigned to a user catalog. FATAR or FATSCOPY will complete processing, but the indicated output data set names will not be cataloged.

Action: You can catalog the output data set name manually without rerunning the job, using the IDCAMS statement DEFINE NONVSAM. If you want to recatalog the output name to the output tape, rerun the step using CAT=RECAT instead of CAT=YES. If the output name is not valid, use the RENAME statement to change the name to one that can be cataloged.

FATS088 **WARNING** CATALOGING REQUESTED BUT FULL NAME NOT AVAILABLE. DSN=dsn

Reason: Cataloging of the indicated output data set was requested by the CAT=YES or CAT=RECAT parameters, but was not attempted because FATAR does not know the full 44-character name of the data set. IBM records only the last 17 characters of the original data set name in the tape labels, which is not valid for cataloging. FATAR can attempt cataloging if:

— the FATAR tape management interface is enabled and has provided the full data set name from tape management records

— the name in the labels is 16 characters or less

— you have provided the output data set name on a RENAME statement with the NEWN= parameter.FATAR will complete processing but the indicate output data set names will not be cataloged.

Action: You can rerun the FATAR step providing RENAME statements with NEWN= to provide the output data set name. If the tape is recorded in your tape management system but you have not enabled the FATAR tape management interface, you can do so (see Activating the Tape Management Interface).

FATS089 **WARNING** NEWI= SPECIFIED BUT FULL NAME NOT AVAILABLE. NEWI=mask

Reason: A RENAME statement with the NEWI= operand applies to this file, but the full data set name of the input data set was not available. The full name is available if the original name is 16 characters long or less, if the full name was provided on the TAPEIN DD statement, or if you have enabled the FATAR tape management interface.

Action: The output file will be created with the truncated name derived from the input tape labels. You may want to rerun the copy specifying a full output data set name with NEWN= instead of NEWI=.

FATS090 **WARNING** NEWI= RESULTED IN INVALID OUTPUT DATASET NAME. NEWI=mask, DSN=dsn VOL=volser

Reason: A RENAME statement with the NEWI= operand applies to this file, but when the mask was applied to the input data set name, it resulted in an output data set name that does not meet IBM standards. The volume and dsn are displayed only by FATSCOPY.

Action: The output data set will be created with the input data set name, ignoring the RENAME statement. You may want to rerun the copy specifying a NEWI= which results in a valid name. If running FATAR, specify a NEWN= to provide a complete output name.

FATS091 **WARNING** NEXTVOL=TMS SPECIFIED BUT TMS INFORMATION NOT AVAILABLE.

Reason: NEXTVOL=TMS was specified, requesting that FATAR get information about the additional input tape volumes related to the first input tape from the FATAR tape management interface, but no tape management information was available for this tape. Either the tape management interface is not enabled (see Activating the Tape Management Interface) or the input tape is not recorded in the tape management database.

Action: If additional volume serials were specified on the TAPEIN DD statement, they will be mounted. Otherwise, FATAR will terminate normally at the end of the input tape.

FATS092 OUTPUT DATASET RENAMED TO DSN=dsname

Reason: A RENAME statement was supplied that applies to this file. The actual name of the output data set is displayed.

FATS093 OUTPUT DATASET RENAMED AND CATALOGED. FILE=ffff,UNIT=xxxxxxxx,DSN=dsname

Reason: A RENAME statement was supplied that applies to this tape file and CAT= was also specified. The actual name of the output data set is displayed; this data set was cataloged with the file number and device type (in hex) shown.

FATS094 **WARNING** CATALOGING REQUESTED BUT NEW NAME WAS NOT SPECIFIED.

Reason: CAT= was specified, requesting that this output data set be cataloged, but the full name of the input data set was not available and no RENAME NEWN= was provided with an output data set name. The full name is available if the original name is 16 characters long or less, if the full name was provided on the TAPEIN DD statement, or if you have enabled the FATAR tape management interface.

Action: The output file will be created with the truncated name derived from the input tape labels but this name was not cataloged.

FATS095 OUTPUT DATASET CATALOGED. FILE=ffff,UNIT=xxxxxxxx,DSN=dsname

Reason: CAT= was specified, requesting that this output data set be cataloged, and the current output data set was cataloged with the file number and device type (in hex) shown.

FATS096 END OF DATA MARK ENCOUNTERED. BLOCK ID=xxxxxxxx. VOL=volser DSN=dsn

Reason: FATAR or FATSCOPY encountered an End-of-Data (EOD) hardware mark on an input tape. An EOD mark is written on every cartridge (except 3480-format) after the trailer labels of the last file on the tape, so this indicates that your FATAR options requested FATAR to read beyond that last file. xxxxxxxx is the hardware block ID of the EOD mark. The volume and dsn are displayed only by FATSCOPY.

Action: FATAR will attempt to position past the EOD mark and continue. However, the results may vary depending on the type of tape and the vendor of the hardware; sometimes it may be unable to move past the EOD and other times it may need to skip over some data past the EOD. FATSCOPY will stop processing the current file and proceed to the next data set.

FATS097 LABELS=ONLY SPECIFIED. DATA FILE WILL BE SKIPPED.

Reason: LABELS=ONLY was specified on the ANALYZE/COPY statement. FATAR will read and format tape labels, but will use a Forward Space File CCW to rapidly skip over data files. No meaningful statistics about the contents of the data files will be printed.

FATS098 LABELS=ONLY SPECIFIED. NO TOTALS WILL BE PRODUCED FOR THIS RUN.

Reason: LABELS=ONLY was specified on the ANALYZE/COPY statement. FATAR will read and format tape labels, but will use a Forward Space File CCW to rapidly skip over data files. FATAR totals are meaningless without information about the data files, so they are not printed.

FATS099 NEAR RELATIVE DATA LOCATION nnn - error description

Reason: An error occurred while parsing a control statement. The approximate location of the error was position nnn, counting the first position as 000. The failing statement is normally printed immediately above.

Action: Correct the error described in “error description” and re-submit the job.

FATS100 (INSTRUCTION LINE)

Reason: If PARM=I is present on the FATS EXEC JCL statement, this message will be printed repeatedly on SYSPRINT with the internal FATS instructions.

FATS101 **PHYSICAL VOLUME=volser CONTAINED NO LOGICAL VOLUMES.

Reason: PHYSVOL= was specified on a SELECT statement, but a check of the Virtual Tape Server found no logical volumes associated with the physical volume.

Action: FATSCOPY will set a return code '8' to indicate that an error occurred. FATSCOPY will continue to parsecontrol statements and will process any volumes that matched other SELECT statements.

FATS102 CONTROL CARD ERROR -- REASON=x

Reason: A syntax or usage error has been detected in the control statement printed immediately preceding the message. Only one FATS102 message will be printed for each input statement; multiple errors on a statement will not be diagnosed. x is a letter or number indicating the type of error detected:

1. An option parameter is not followed by a blank or comma.

2. Operation keyword is invalid, or the tape number in parentheses is not 1 through 9.

3. Tape number has been previously used on another operation statement.

4. An option parameter is invalid.

5. Error in the MODE= parameter. Value is not 2 hexadecimal digits or is not one of the valid values.

6. Error in the RETRY= parameter. Must be RETRY=h or RETRY=(l,h). h must be 1 to 99. l must be 0 to h .

7. Error in the numeric value of a keyword parameter. Invalid numeric digits.

8. Error in the BPI= parameter, BPI=0.

9. Error in the LABEL= parameter, invalid characters in the label value.

A. Expected continuation statement not received (previous statement ended in a comma).

B. No ending apostrophe in OWNERID= parameter.

C. Error in the THRESHOLD= parameter, greater than 32767.

D. Label operation statement missing LABEL= or VOL= parameter.

E. Error in the BLKSIZE= parameter; it must be less than 65536 and more than twice the tape density (BPI), except for cartridges.

F. Error in VOL= parameter. Volume serial longer than 6 characters.

G. Error in VOL= parameter. More than 682 volume serials specified.

H. VOL= parameter-specified on a default statement.

I. VOLINCR= parameter-specific without VOL= parameter.

J. Blank control statement.

K. Error in VOLINCR= parameter. The last volume serial in the VOL= parameter could not be incremented due to insufficient trailing numeric digits.

L. Error in ENDAFTER= parameter.

M. Invalid numeric value for keyword. Value was zero or greater than 32767.

N.An option parameter was specified that is invalid for the control statement on which it was found. For example, MODIFY=YES was specified on a read statement, but it is only valid on a DEFAULT statement.

Action: FATS will abend with a U0502 abend code after all control statements have been scanned.

FATS103 **TAPESUMM DD STATEMENT MISSING. ADD TAPESUMM DD TO JCL AND RERUN JOB.

Reason: FATSCOPY requires a TAPESUMM DD.

Action: FATSCOPY will abend with a U0888. Add a TAPESUMM DD to your JCL and rerun the job.

FATS104 ONE OR MORE ERRORS DETECTED -- FATS TERMINATED

Reason: Message FATS102 was issued for one or more control statement errors.

Action: FATS will abend with a U0502 abend code. Correct the errors and re-execute.

FATS105 NO INPUT CARDS -- FATS TERMINATED

Reason: No control statements other than DEFAULT and comments were present in the input. At least one operation statement must be present.

Action: FATS will abend with a U0502 abend code.

FATS106 DD=SYSPRINx MISSING -- REQUIRED FOR ANALYZE

Reason: An ANALYZE(x) control statement was present but no corresponding SYSPRINx DD statement was found. FATAR cannot write its messages to SYSPRINT when invoked from FATS.

Action: FATS will abend with a U0502 abend code.

FATS107 A line of the detail report indicating label status

FATS108 NO SUMMPRT DD PROVIDED-SUMMARY REPORT WILL GO TO SYSPRINT

Reason: The SUMMPRT DD statement is not present.

Action: FATS will write summary report data to SYSPRINx if present for TAPEx or to SYSPRINT

FATS109 FATS BYPASSED DD=TAPEx REASON=MISSING DD STATEMENT DEVICE NOT A TAPE

Reason: FATS was unable to process an operation statement because the associated DD statement TAPEx was not provided or did not allocate a tape device.

Action: Other operation statements (if present) will be processed. Check the TAPEx DD statement.

FATS110 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason: FATS has read the control statement printed as part of this message.

Action: FATS will parse the control statement.

FATS111 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason: FATS has parsed all of the control statements and merged the information for each with the defaults. This table represents the processing to be done for each of the 1 to 9 functions specified.

Action: FATS will perform the requested functions.

FATS112 FATS MUST BE IN AN AUTHORIZED LIBRARY. PROGRAM TERMINATED.

Reason: FATS must be executed as an APF authorized program. Either the program library containing FATS was not marked as an APF authorized library on your z/OS system, or your STEPLIB or JOBLIB DD statement has nonauthorized libraries concatenated to the FATS program library, or FATS has been relinked as nonauthorized (AC=0).

Action: FATS will terminate with a U0047 ABEND.

FATS113 PROGRAM TERMINATED. USER NOT AUTHORIZED TO PERFORM FUNCTION=func

Reason: Your installation has protected certain functions and options of FATS and FATAR through your security system. You are not authorized to use the function or option func .

Action: The program will terminate with a U0913 abend. If you require the failing function or option, contact your security administrator. Refer to FATS Security and FATAR FATAR Security for information on the security options.

FATS114 PROGRAM TERMINATED. USER NOT AUTHORIZED TO READ DSN=dsname

Reason: Your security system has indicated that you are not authorized to read a file on the input tape with data set name dsname.

Action: The program will terminate with a U0913 abend. If you require access to this data set, contact your security administrator. Refer to FATAR Security for information on the FATAR data set security.

FATS115 UNLABELED TAPE USED AS INPUT WHEN LABELS=ONLY WAS SPECIFIED. RUN TERMINATED.

Reason: LABELS=ONLY is supported only on a labeled tape.

Action: The program will terminate.

FATS116 UNABLE TO ACCESS DATA PAST END-OF-DATA MARK. RUN TERMINATED.

Reason: All cartridge tapes (except 3480) put a hardware EOD (End-of-Data) mark after the last block or tape mark written to the tape. This message indicates that FATAR was unable to position past the EOD mark. This can occur when:
—LABELS=EOD was specified, to recover data past the EOD
—LABELS=NO and NUMFILES=n was used to request processing past the EOD.

Action: The program will terminate with a U0888 abend.

FATS117 ANALYSIS TERMINATED AT END-OF-DATA MARK

Reason: On a cartridge tape (except for 3480), FATAR encountered a EOD (End-of-Data) mark that follows a tape mark.

Action: Processing of the input tape is completed.

FATS117 COPY TERMINATED AT END-OF-DATA MARK DSN=dsname, VOL=volser

Reason: FATSCOPY encountered an end-of-data mark when copying a data set. Output data set will not be cataloged or updated with tape management information from the input data set. If TMSINPUT=SCRATCH was specified, the input will not be expired.

Action: FATSCOPY will continue with the next data set.

FATS118 UNABLE TO LOAD name ASCII TRANSLATE TABLE. DEFAULT IBM TABLE WILL BE USED

Reason: The ASCII=name operand was specified, but a load module called name could not be successfully loaded, so the default IBM ASCII translate table was used.

Action: Make sure that the load module name of the ASCII translate table was properly specified, and that it is in a load module library accessible by this FATAR step.

FATS120 **DSN=dsname ON VOLUME=volser WAS SELECTED FOR COPYING.

Reason: FATSCOPY selected the indicated data set on the indicated tape volume from the system catalog for copying.

FATS121 **NO DATA SETS WERE SELECTED FOR COPYING. JOB TERMINATED.

Reason: The SELECT/EXCLUDE statements specified for FATSCOPY did not result in any data sets being selected.

Action: If the statements were specified incorrectly, correct and re-submit. If data sets should have been selected, check the statements carefully for errors; if necessary, contact BMC support for assistance.

When the FATS121 message is issued, the FATSCOPY job normally terminates with a U0300 abend and produces a dump. To terminate with a return code of 12 instead, and no dump, use the RETCODE parameter. To terminate with a a return code of 0 instead, and no dump, use SELTERR=NO.

FATS122 **FATSCOPY SIMULATE SUCCESSFULLY COMPLETED. nnnn DATA SETS WERE SELECTED FOR COPYING.

Reason: FATSCOPY was executed with a SIM (SIMULATE) statement. If it had been executed with a COPY statement, nnnn data sets would have been copied. The selected data sets are listed in the SELRPT and COPYRPT reports.

FATS123 **LOAD OF RMM API FAILED. DSN=dsname VOL=volser WILL NOT BE EXPIRED.

Reason: Your tape management system is apparently DFSMSrmm (RMM) but the RMM Application Program Interface (API) could not be used by FATSCOPY to expire the data set.

Action: Contact BMC support for assistance.

FATS124 **SELRPT DD STATEMENT MISSING. ADD SELRPT DD TO JCL AND RERUN JOB

Reason: You omitted the required SELRPT DD statement in a FATSCOPY step. The step will end with a U0888 abend.

Action: Add the SELRPT DD to your step; it is usually a SYSOUT=* data set.

FATS125 **COPYRPT DD STATEMENT MISSING. ADD COPYRPT DD TO JCL AND RERUN JOB

Reason: You omitted the required COPYRPT DD statement in a FATSCOPY step. The step will end with U0888.

Action: Add the COPYRPT DD to your step; it is usually a SYSOUT=* data set.

FATS126 **MAXIMUM NUMBER OF INPUT TAPE FILES EXCEEDED. SELECT STATEMENT NOT PROCESSED.

Reason: The preceding SELECT statement was ignored because the maximum number of files to be copied in this FATSCOPY step been exceeded. For CATDSN, the limit is specified by MAXTOTFILE=. For ALLDSN, the limit is 65,535.

Action: Include the SELECT statement(s) in another FATSCOPY step to copy those data sets, or specify a larger value for MAXTOTFILE=.

FATS127 **NO TMS INFORMATION FOUND. TMS INFO WILL NOT BE COPIED DSN=dsname VOL=volser

Reason: The indicated data set was selected from your system catalogs by FATSCOPY, but no tape management information was found for the data set.

Action: The data set will be copied but no TMS information will be updated for this data set.

FATS128 **RMM API LOAD FAILED. DATA FOR DSN=dsname VOL=volser WILL NOT BE COPIED

Reason: Your tape management system is apparently DFSMSrmm (RMM) but the RMM Application Program Interface (API) could not be used by FATSCOPY.

Action: Contact for assistance.

FATS129 **DYNAMIC ALLOCATION FAILED FOR VOL=volser DEVTYPE=devtype. RC=rrrr, REAS=cccc0000

Reason: FATSCOPY issued a dynamic allocation for an input tape file to copy on the volume serial and tape device type shown, but the allocation failed with the indicated return code and reason code.

Action: The tape file will be bypassed; serious errors may cause the step to abend. For z/OS, 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. Frequently encountered cccc values include:

0210 - requested data set not available (e.g., another job had the tape file allocated with DISP=OLD).

021C - invalid unit name used (e.g., FATSCOPY is trying to allocate a 3480 on a system without 3480s).

0220 - requested volume not available (e.g., another job is using a tape volume required by FATSCOPY).

039C - requested device type and volume are incompatible. This may occur if the data set is cataloged to a device type that does not match the volume it is located on.

Specifying UNITIN= on the COPY statement may resolve this problem.

FATS130 **DYNAMIC DEALLOCATION FAILED FOR VOL=volser DEVTYPE=devtype. RC=rrrr, REAS=cccc

Reason: FATSCOPY issued a dynamic de-allocation for an input tape file to copy on the volume serial and tape device type shown, but the de-allocation failed with the indicated return code and reason code.

Action: FATSCOPY will terminate. For OS/390, 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.

FATS131 **EXPIRATION DATE FOR INPUT VOLUME=volser HAS BEEN CHANGED: date

Reason: The user specified TMSINPUT=SCRATCH; the expiration date for the volume has been changed to the indicated date so that the volume will expire on that date and be scratched when tape management runs.

FATS132 **TAPE MGMT INFO FOR DSN=dsname ON VOL=output WAS COPIED FROM VOL=input

Reason: FATSCOPY has copied the appropriate information, such as expiration date, creating job, etc. from the tape management record for the input volume to the tape management record for the output volume.

FATS133 **EXPIRATION DATE FOR DSN=dsname,VOL=volume CHANGED TO date

Reason: FATSCOPY  has changed the expiration date for the output data set on the indicated output volume to the date specified. This is the latest date for any data set on the volume. This message is issued for CA 1 and TLMS, and also for RMM if RMM data set expiration support is available (message FATS165 is issued if it is not available).

FATS134 **UNABLE TO CHANGE EXPIRATION DATE FOR OUTPUT VOLUME=volser RC=return code, REASON=reason code

Reason: FATSCOPY’s attempt to update the tape management expiration date for the output volume failed.

FATS135 **UNABLE TO EXPIRE INPUT type=name RC=return code,REASON=reason code

Reason: FATSCOPY tried to expire the input volume (type=”VOLUME”) or data set (type=”DATASET”) but was unable to do so.

FATS135 **UNABLE TO RESET KEEP DATE FOR INPUT CONTROL DATA SET, VOLUME=volser, REASON=reason code

Reason: TMSINPUT=SCRATCH was specified, but FATSCOPY was unable to change the expiration date for the TLMS control data set on the input volume.

FATS136 **UNABLE TO DELETE RMM DATASET INFO FOR OUTPUT DSN=dsname VOLUME=volser

Reason: While copying a data set, FATSCOPY reached the end of tape on the OUTPUT. At the time it reached end of tape, the number of bytes written to TAPEOUT was less than the value specified in the LASTFILE= parameter. FATSCOPY attempted to delete the tape management information for the output data set, but failed to do so.

FATS137 **NO TMS INFO FOR DSN=dsname. UNABLE TO EXPIRE INPUT VOL=volser

Reason: FATSCOPYcopied a cataloged data set that had no corresponding tape management information. FATSCOPY will be unable to update the tape management information for the output data set.

FATS138 **FATSCOPY UNABLE TO CHANGE EXPIRATION FOR VOLUME=input volser. ALL DATA SETS ON xxxxxx NOT SELECTED FOR COPYING

Reason: TMSINPUT=SCRATCH was specified, but some of the files on the volume or tape set were not copied. ”xxxxxx” will be “INPUT” if the identified volume was a multi-file tape or “MVOL SET” if the volume is part of a multi-volume, multi-file tape set.

Action: FATSCOPY updated the expiration dates of the copied files, but could not update the expiration date of the volume(s) because some unexpired files still remained on those tapes. A return code of 4 will be issued.

FATS139 **RMM UPDATE FAILED. VOLUME=volser DSN=dsname RC=return code,REAS=reason code

Reason: TMSDATA=COPY was specified, but FATSCOPY’s attempt to update the tape management information for the volume failed. The displayed return and reason codes are the hex values returned by RMM.

FATS139 **ZARA UPDATE FAILED. VOLUME=volser,DSN=dsname,REAS=reason

Reason: An update to the Zara data base failed. The reason code displayed in the message is the return code issued by the Zara API. The reason codes are documented in the APIREASN field in the ZARAPLST DSECT, which can be found in the ASG-Zara User’s space in the Zara Application Program Interface.

Action: FATSCOPY will issue a non-zero return code for the data set and continue processing any remaining data sets.

FATS140 **COPY FUNCTION SPECIFIED BUT NO TAPEOUT DD FOUND. JOB TERMINATED.

Reason: The COPY statement requires a TAPEOUT DD statement.

FATS141 **TMS NOT ACTIVE. TMS DATA WILL NOT BE COPIED. DSN=dsname,VOL=volser

Reason: The tape management system expected was not active, so FATSCOPY will not attempt to copy tape management data relating to the data sets it is copying.

FATS142 **ERROR OCCURRED READING TMC FOR xxxxxx VOL=volser. TMS DATA WILL NOT BE COPIED.

Reason: An error occurred while reading tape management data for the input tape (xxxxxx=INPUT) or the output tape (xxxxxx=OUTPUT). The tape management data for the file being copied will not be updated on the output tape's records.

FATS142 **ERROR OCCURRED READING VMF FOR OUTPUT VOL=volser. UNABLE TO OBTAIN BLOCK INFO.

Reason: An error occurred while reading TLMS block count information for the output volume. Block and byte count totals for the output tape will not be correct in the summary reports.

FATS143 **ERROR OCCURRED UPDATING TMC FOR DSN=dsname VOL=volser

Reason: An error occurred while updating tape management data for the output data set. The tape management data for the file being copied will not be updated on the output tape's records.

FATS143 **ERROR OCCURRED UPDATING VMF FOR DSN=dsname VOL=volser REASON=xxxxxxxx

Reason: An error occurred while updating the TLMS Volume Master File for the output data set. The tape management data for the file being copied will not be updated on the output tape's records. xxxxxxxx is the TLMS error message code.

FATS144 **ERROR OCCURRED DEQUEUING TMC FOR DSN=dsname VOL=volser

Reason: An error occurred while updating tape management data for the output data set. The tape management data for the file being copied will not be updated on the output tape's records.

FATS145 **DSN=dsname ON VOL=volser BYPASSED - MISSING VOLS OF MULTI-VOL DSN.

Reason: When processing a data set that had met all the selection criteria, FATSCOPY determined that some volumes of a multi-volume set had not met the selection criteria. FATSCOPY will not copy the data set.

FATS146 **UNSUPPORTED TAPE MGMT SYSTEM. UNABLE TO UPDATE TAPE MANAGEMENT INFORMATION

Reason: TMSDATA=COPY or TMSINPUT=SCRATCH was specified, but FATSCOPY didn't find CA 1, Control-M/Tape, TLMS, Zara, or RMM, the only tape management systems currently supported.

FATS147 **TAPE MOTION I/O ERROR

Reason: An I/O error occurred while FATSCOPY was reading an input tape. FATSCOPY was unable to reposition the tape to retry the I/O that had the error.

Action: FATSCOPY will terminate with a U0888 abend.

FATS148 **TMC OPEN FAILED. TMS DATA CAN NOT BE COPIED. DSN=dsname,VOL=volser

Reason: An error occurred when FATSCOPY tried to open the TMC to obtain tape management information for the input volume to update tape management information for the output volume. The TMS information will not be copied to the output.

FATS148 **TMC OPEN FAILED. DATA SET WILL NOT BE EXPIRED. DSN=dsname,VOL=volser

Reason: An error occurred when FATSCOPY tried to open the TMC to expire the input data set.

FATS148 **VMF OPEN FAILED. UNABLE TO UPDATE TLMS INFO FOR DSN=dsname,VOL=volser

Reason: An error occurred when FATSCOPY tried to open the Volume Master file to expire an input data set or update the TLMS information for an output data set.

FATS148 **VMF OPEN FAILED. UNABLE TO OBTAIN BLOCK INFO FOR REPORT.

Reason: An error occurred when FATSCOPY tried to open the TLMS Volume Master file to read block or byte count information for the output file summary reports.

FATS149 **TMS ERROR CODES: RC=return code,REAS=reason code,SEC RC=security return code, SEC REAS=security reason code

Reason: Issued after an error reading, updating, or dequeuing the TMC occurs. Contains CA 1 abend codes, reason codes, and security return and reason codes.

FATS150 **TMS NOT ACTIVE. INPUT TAPE WILL NOT BE EXPIRED. VOL=volser

Reason: TMSINPUT=SCRATCH was specified, but TMS was not active.

FATS150 **TMS NOT ACTIVE. INPUT DSN=dsname, VOL=volser WILL NOT BE EXPIRED.

Reason: TMSINPUT=SCRATCH was specified, but TMS was not active.

FATS151 **ERROR OCCURRED xxxxxxx TMC FOR INPUT VOL=volser. TAPE WILL NOT BE EXPIRED.

Reason: An error occurred when FATSCOPY tried to obtain the expiration date for the input volume prior to changing the expiration date to the current date (xxxxxxx = READING) or when FATSCOPY tried to update TMS with the new expiration date (xxxxxxx = WRITING). The expiration date will not be changed.

FATS151 **ERROR UPDATING TAPE MGT. DSN=dsname VOL=volser WILL NOT BE EXPIRED.

Reason: TMSINPUT=SCRATCH was specified, but an error occurred when FATSCOPY tried to update TMS with the new expiration date. The expiration date will not be changed for this data set.

FATS151 **TLMS ERROR – UNABLE TO EXPIRE DSN=dsname VOL=volser REASON=code

Reason: TMSINPUT=SCRATCH was specified, but an error occurred when FATSCOPY tried to update TLMS with the new expiration date. The expiration date will not be changed for this data set.

FATS151 ** ZARA ERROR – UNABLE TO EXPIRE DSN=dsname VOL=volser REASON=reason

Reason: A FATSCOPY call to the Zara API to expire an input data set failed. The reason code displayed in the message is the return code issued by the Zara API. The reason codes are documented in the APIREASN field in the ZARAPLST DSECT, which can be found in the ASG-Zara User’s Guide in the Zara Application Program Interface in Chapter 12.

Action: FATSCOPY  will issue a non-zero return code for the data set and continue copying any remaining data sets.

FATS151 ** CONTROL-M/TAPE ERROR - UNABLE TO EXPIRE DSN=dsname VOL=volser REASON=reason

Reason: TMSINPUT=SCRATCH was specified, but an error occurred when FATSCOPY tried to update Control-M/Tape with the new expiration date. The expiration date will not be changed for this data set.

Action: FATSCOPY will issue a non-zero return code for the data set and continue copying any remaining data sets.

FATS152 **EOT ON TAPEOUT BEFORE LASTFILE VALUE REACHED. DSN=outdsn,VOL=outvol

Reason: The physical end-of-tape was reached before FATSCOPY copied the number of bytes specified in the LASTFILE= keyword. FATSCOPY will call for a new output tape, determine which tape the input file started on, and begin copying the input file from the beginning. If tape management is active, FATSCOPY will expire the partially copied data set on the output tape.

FATS153 **PARTIALLY COPIED DSN=outdsn ON OUTPUT VOL=outvol WAS DELETED **PARTIALLY COPIED DSN=outdsn ON OUTPUT VOL=outvol WAS EXPIRED

Reason: FATSCOPY successfully deleted (RMM) or expired (CA 1, Control-M/Tape, TLMS, and Zara) the partially copied data set on the output tape in tape management.

FATS154 **NO ACTIVE TAPE MANAGEMENT. DSN=outdsn, VOL=outvol WILL NOT BE EXPIRED.

Reason: FATSCOPY attempted to expire a data set in tape management that had been partially copied, but tape management system was not active.

FATS155 **UNABLE TO FIT DSN=outdsn ON ONE VOLUME. LASTFILE= VALUE WILL BE IGNORED.

Reason: After calling for a new output volume for a data set that wouldn’t fit on the output volume, FATSCOPY again arrived at the end of the output tape without exceeding the LASTFILE= amount. FATSCOPY will call for a new output without starting to copy the input from the beginning.

FATS156 **EXPIRATION DATE FOR DSN=ipdsn, VOL=ipvol WAS SET TO DATE=expirationdate

Reason: After copying a data set, FATSCOPY expired the input data set because TMSINPUT=SCRATCH was specified. The indicated data set and volume were set to the indicated expiration date.

FATS157 **EXPIRATION DATE FOR INPUT VOLUME=volser WAS RESET TO DATE=date

Reason: When FATSCOPY has copied the first data set (if the tape management system is CA 1) or the control data set (if the tape management system is TLMS) on a volume or multivolume set containing multiple files, FATSCOPY will reset the expiration date for the volume to the highest expiration date of any unexpired data set on the volume / multivolume set. If it copies any other files after copying the first file, FATSCOPY will again reset the volume to the highest expiration date of any remaining data sets. If all the data sets on the volume are successfully copied, FATSCOPY will expire the volume at that time.

FATS158 **ERROR READING TMC. DSN=dsname, VOL=volser WILL NOT BE EXPIRED.

Reason: OPEN of the CA 1 TMC for update by FATSCOPY failed and it will not be able to expire the data set. This message will be followed by a FATS149 containing the error codes returned by TMS for the failed OPEN. This may be due to security checks in CA 1; check the CA 1 documentation for information on security protection of the TMC and the YSVCUNCD resource.

FATS159 **NO DATASETS COPIED DURING FATSCOPY RUN. CHECK LISTING FOR ERROR MESSAGES.

Reason: FATSCOPY ended with no data sets being copied, even though data sets were selected for copying. The SYSPRINT or ERRPRRPT report will contain error messages to show why no data sets were copied.

FATS160 **OPEN FAILED FOR DSN=dsn,VOL=volser,ABEND=abend code

Reason: FATSCOPY tried to open an input data set, but the open failed with the ABEND code shown. The joblog may contain IBM messages providing more detail on the error.

Action: The input data set will be skipped and FATSCOPY will continue to copy other data sets, if any are left.

FATS161 **EXPIRATION FOR DSN=dsn,VOL=volser WILL BE RESET BY RMM HOUSEKEEPING.

Reason: While attempting to update the RMM expiration date for a data set it just copied, FATSCOPY found that the data set’s expiration was controlled by a RMM Vital Record Specification. The next time RMM housekeeping runs, RMM will set the expiration for the output data set according to the VRS.

FATS162 **MAXIMUM NUMBER OF FILES SELECTED FOR COPYING. CATALOG SEARCH STOPPED.

Reason: While searching the catalog for data sets to copy, FATSCOPY exceeded the maximum number of data sets specified by the MAXTOTFILE= operand (default: 1000).

Action: FATSCOPY will stop selecting data sets and will process the data sets it has selected. Rer FATSCOPYto select the remaining data sets, and increase MAXTOTFILE= if needed.

FATS163 **CATALOGING BYPASSED FOR UNCATALOGED INPUT DATA SET, DSN=dsname

Reason: CAT=ONLY was specified (or defaulted in FATSCOPY ) and an input data set was not cataloged. This could mean that the input data set was not in the catalog at all, or that it was cataloged but it pointed to a volume or file number different from the input data set.

Action: The output file will not be cataloged. A return code based on the value specified or defaulted for NOTCATRC= (0, 4, or 8) will be issued.

FATS164 **JOB TERMINATED DUE TO RMM READ OR UPDATE FAILURE.

Reason: An update or read of RMM tape management information occurred, and RMMFAIL=STOP had been specified.

FATS165 **LAST USED INFO FOR VOLUME=oooooo COPIED FROM VOLUME=iiiiii

Reason: TMSDATA=COPY was specified, so FATSCOPY copied the tape management information about the last use of the input tape iiiiii to the output tape oooooo

FATS166 **EXPIRATION DATE FOR OUTPUT VOLUME=outvol HAS BEEN SET TO expirationdate|VITAL RECORD

Reason: Documents the expiration date that has been assigned to the indicated output volume. If the tape management system is RMM and one of the input data sets had a VITAL RECORD expiration, the message will show VITAL RECORD. If the tape management system is TLMS, this message is issued when the expiration date of the control data set (by default, data set #1) has been set on the output volume.

FATS167 **SELECT ALLDSN SPECIFIED BUT NO TAPE MANAGEMENT INFO FOR VOLUME=volser. VOLUME BYPASSED.

Reason: A SELECT ALLDSN statement was used to select an input tape, but no tape management information was found for the indicated volume.

Action: The volume is bypassed. If there are no more SELECT statements or they all fail the same way, the step will end with a U0300 ABEND.

FATS168 **ALL DATA SETS ON VOL=input volser COPIED. VOLUME RELEASED.

Reason: RMM was the active tape management system, the input volume had a RMM Vital Record Retention and all data sets on the indicated input volume have been copied. TMSINPUT=SCRATCH was specified.

Action: RMM is notified to release the input tape.

FATS169 **RELEASE FOR VOL=input volser FAILED. RC=return code, REAS=reason code

Reason: RMM was the active tape management system, the input volume had a RMM Vital Record Retention and all data sets on the indicated input volume have been copied. TMSINPUT=SCRATCH was specified, but an error occurred when RMM was notified to release the tape.

Action: The input tape is not released. You may need to release it manually.

FATS170 **LASTAPE DATA SET CATALOGED. VOL=volser,DSN=dsname

Reason: LASTAPE= was specified. At the end of the FATSCOPYstep, the data set name specified was created as an empty file and cataloged to the volume shown.

FATS170 **ARCHIVE CONTROL FILE BACKUP CATALOGED. VOL=volser,DSN=dsname

Reason: ARCBACKUP=DSF was specified. At the end of the FATSCOPY step, a backup of the Archive Control File was created and cataloged to the volume shown using the data set name specified by the ARCB1DSN= parameter (or the default).

FATS171 **EXPDTGROUP VALUE SET TO 999 FOR LASTAPE PROCESSING.

Reason: FATSCOPY normally groups data sets by expiration date. When LASTAPE= is specified, EXPDTGROUP will be set to 999.

Action: Data sets will be not be grouped by expiration date.

FATS172 **reason. UNABLE TO DETERMINE IF LASTAPE VOLUME EXCEEDS THRESHOLD.

Reason: LASTAPE= was specified with THRESHOLD=, but FATSCOPY was unable to determine if the percentage used of the output tape exceeded the specified threshold. “reason” may be:

NO ACTIVE TAPE MANAGEMENT – No tape management system was active.

UNSUPPORTED TAPE MANAGEMENT – THRESHOLD is not supported with the active tape management system.

TMC OPEN FAILED – Open of the CA 1 TMC failed; message FATS149 follows.

Action: No threshold checking is done. FATSCOPY will continue to add files to the tape. A return code of 8 will be set.

FATS173 **TMS REQUEST FOR LASTAPE VOLUME volser FAILED. THRESHOLD PROCESING BYPASSED.

Reason: LASTAPE= was specified with THRESHOLD=, but the LASTAPE data set was cataloged to a tape not under CA 1 control.

Action: No threshold checking is done. FATSCOPY will continue to add files to the tape.

FATS174 **LASTAPE VOLUME volser EXCEEDED THRESHOLD. NEW OUTPUT VOLUME WILL BE CREATED.

Reason: LASTAPE= was specified with THRESHOLD=, and the current output volume exceeded the threshold percentage in use.

Action: FATSCOPY will mount a fresh scratch tape.

FATS175 **LOAD OF RMM API FAILED. THRESHOLD PROCESSING BYPASSED.

Reason: LASTAPE= was specified with THRESHOLD=, and the current output volume was under DFSMSrmm control but the RMM API module could not be loaded.

Action: No threshold checking is done. FATSCOPY will continue to add files to the tape.

FATS176 **DEVTYPE=COPYCROS SPECIFIED, BUT NO COPYCROS DEVICES MATCHED VIRTUNIT=TYPE.

Reason: FATSCOPY was unable to locate any CopyCross devices that matched the specified type.

Action: The step will abend with U0502.

FATS177 **UNEXPECTED LOAD POINT WHILE COPYING DSN=dsname, VOL=volser

Reason: When copying a data set, FATSCOPY read the data set, but the input volume had been repositioned to the beginning of the volume. The output data set will not be cataloged or be updated with information for the input data set.

Action: A return code of 12 is set for the current data set.

FATS178 **UNABLE TO OBTAIN STORAGE REQUIRED FOR xxxx. JOB TERMINATED. XXXX will be one of: TAPE BUFFERS, SELECTION TABLE, PROCESSING TABLE

Reason: FATSCOPY was unable to obtain the storage needed for tape buffers. Make sure that you specified REGION=0M on the EXEC statement. Specify BUFNO= to reduce the number of buffers acquired.

Action: The step will abend with U0888.

FATS179 **UNABLE TO OBTAIN STORAGE REQUIRED FOR REBLOCKING DATA SETS. JOB TERMINATED.

Reason: FATSCOPY  was unable to obtain the storage needed for reblocking buffers. Make sure that you specified REGION=0M on the EXEC statement. Specify BUFNO= to reduce the number of buffers acquired.

Action: The step will abend with U0888.

FATS180 **UNABLE TO CREATE LASTAPE DSN DUE TO INVALID CHARACTERS IN DSN. JOB TERMINATED.

Reason: After processing all the data sets selected for copying, FATSCOPY tried to create the LASTAPE file on the output tape but the LASTAPE data set name was invalid.

Action: The step will abend with S0C3. Contact BMC support for assistance.

FATS181 **UNABLE TO OBTAIN ELIGIBLE DEVICE FOR ALLOCATING TAPEIN USING nnnnnn. RC=rtncode, REASON=rsncode

Reason: FATSCOPY was unable to find a unit for mounting the input tape using either the UNITIN= value, the VIRTUNIT value, or the UCB address.

Action: If VIRTUNIT was specified, the step will abend with U0502. Otherwise, the tape is bypassed.

FATS182 **VERSION 5.4/70 OR HIGHER OF FDRABR REQUIRED FOR COPYING ABR ARCHIVE DATA SETS.

Reason: FATSCOPY  supports copying ABR Archive and Application Backup data sets only if version 5.4/70 or above of FDRABR is available. ABRARC=YES was specified, but a supported level of FDRABR could not be loaded from the linklist, STEPLIB, or JOBLIB.

Action: FATSCOPY  will set a non-zero return code, and will not select any ABR Archive or Application backups for copying.

FATS183 **SERIOUS ERROR OCCURRED OBTAINING JFCB EXTENSIONS FOR TAPEOUT.

Reason: FATSCOPY  clears the TAPEOUT JFCB and JFCB extensions after each data set copy, but a pointer to a JFCB extension was invalid.

Action: The step will abend with U0888.

FATS184 **LOGIC ERROR OCCURRED DURING LASTFILE PROCESSING. JOB TERMINATED.

Reason: FATSCOPY  was unable to determine the correct volume to use to create the LASTAPE data set.

Action: The step will abend with U0888.

FATS185 **LOGIC ERROR OCCURRED READING TAPE MGMT INFO FOR DSN=dsname, VOL=volser

Reason: When attempting to update the output volume with information from the input tape, FATSCOPY was unable to find the correct data set entry for either the input or output data set.

Action: A return code 8 will be set for the failing data set but it will be copied. You may need to update the TMS information manually.

FATS186 **UNABLE TO EXPIRE INPUT DSN=dsname, VOL=volser DUE TO FATSCOPY LOGIC ERROR.

Reason: A logic error occurred that prevented FATSCOPY from determining if the input data set could be expired.

Action: A return code 8 will be set for the failing data set but it will be copied. You may need to expire the data set manually.

FATS187 **LOGIC ERROR OCCURRED DURING THRESHOLD PROCESSING. UNABLE TO DETERMINE IF LASTAPE VOLUME EXCEEDS THRESHOLD.

Reason: A logic error prevented FATSCOPY from determining the percentage of the last output tape currently in use. Data sets will continue to be added to the tape.

Action: A return code 8 will be set.

FATS188 **NOT ENOUGH STORAGE FOR FATSCOPY PROCESSING TABLE.

Reason: The internal data set table used by FATSCOPY was not large enough to contain entries for all the selected data sets.

Action: The job will abend with a U0888. Increase the MAXTOTFILE= value to a higher number, or modify your SELECT statement(s) to select fewer data sets.

FATS189 **RESTART DATA SET CREATED. DSN=dsname'

Reason: FATSCOPY created or updated an existing data set that can be used as input to a subsequent FATSCOPY job.

Action: Job will complete with a zero condition code.

FATS190 **DSNTABLE DD REQUIRED FOR CREATING CHECKPOINT DATA SET OR RESTARTING JOB. JOB TERMINATED.

Reason: The CHECKPT or RESTART keyword was specified, but a DSNTABLE DD with the name of the data set to use to create the checkpoint data set or restart the job wasn't included in the JCL.

Action: The job will be terminated with a return code '12'. Add a DSNTABLE DD to the JCL and resubmit the job.

FATS191 ** COPY STOPPED BY OPERATOR. nnnnn FILES REMAIN TO BE COPIED.

Reason: The CHECKPT keyword was specified and an operator issued a STOP command to end a FATSCOPY job. nnnnn indicates the number of files that remained to be copied.

Action: The job will end when it finishes copying the current data set. A checkpoint data set will be created so that the job can be restarted at a later time.

FATS192 **OPEN OF AUDIT DATA SET FAILED. JOB CANCELLED BY OPERATOR.

Reason: An AUDITRPT was present in the JCL, but FATSCOPY failed to open the data set, and the operator replied 'NO' to the FATSW16 message issued to the console.

Action: The job will abend with a U0888.

FATS193 **UNRECOVERABLE READ ERROR. DSN=dsname,VOL=volser.

Reason: A read error occurred on an input tape that FATSCOPY  was unable to recover from.

Action: FATSCOPY  will issue a U0888 for the data set it was copying when the I/O error occurred and continue copying any remaining data sets.

FATS194 **HSM NOT ACTIVE. UNABLE TO RECYCLE VOLUME=volser

Reason: HSMML2=YES was specified, but HSM was not active when FATSCOPY issued a request to HSM to recycle a Migration Level 2 data set.

Action: FATSCOPY  will set a return code '12' for the current data set and continue with the next data set to be copied.

FATS195 **TAPE MANAGEMENT INFORMATION FOR OUTPUT VOLUME=volser WAS SET BY HSM RECYCLE.

Reason: An HSM Migration Level 2 volume was successfully recycled as the result of a recycle request issued by FATSCOPY.  All the tape management information for the output volume was set by HSM.

Action: A return code '0' will be set for the data set.

FATS196 **EXPIRATION DATE FOR OUTPUT VOLUME=volser WAS SET BY HSM RECYCLE.

Reason: An HSM Migration Level 2 volume was successfully recycled as the result of a recycle request issued by FATSCOPY. HSM has set the appropriate expiration date for the output volume.

Action: A return code '0' will be set for the data set.

FATS197 **UNABLE TO OBTAIN STORAGE REQUIRED FOR ARCHIVE TABLE. JOB TERMINATED.

Reason: A FATSCOPYRESTART job where ABR Archive or Application Backup files had been selected in the DSNTABLE data set was unable to obtain the storage needed to perform updates to the Archive Control File.

Action: The job is terminated with a U0888 abend. Increase the REGION size, or code REGION=0M on the EXEC statement.

FATS198 **OUTPUT CREATION DATE RESET AFTER COPY. DSN=dsname,VOL=volser

Reason: When FATSCOPYis copying a data set under TMS Catalog Control that requires more than 1 output volume, FATSCOPYtemporarily sets the creation date for the output to the current date to prevent the output from being expired prematurely by CA 1 housekeeping before FATSCOPY catalogs it. This message is issued to indicate that FATSCOPY has successfully cataloged the output data set and copied the creation date from the input data to the output data set.

FATS199 **RMM UPDATE FAILED BECAUSE RMM HOUSEKEEPING WAS ACTIVE. FATSCOPY JOB TERMINATED.

Reason: An update to RMM failed because RMM housekeeping was running; the job was terminated based on the value specified for the RMMFAIL= parameter.

Action: Job will be terminated immediately with a non-zero return code.

FATS201 TAPEx MAJOR ERROR ON TAPE ANALYZE TERMINATED FOR VOL=vvvvvv

Reason: The first form of the message will be issued whenever unrecoverable I/O errors (other than data checks) occur on the indicated tape drive; it will be followed by message FATS202. The second form of the message appears when a threshold of major errors is exceeded or when the error is too severe to continue (such as equipment check or intervention required).

Action: If the second form of the message is issued, further processing of the tape volume vvvvvv is halted, and FATS will eventually abend with a U0888 abend code to indicate that major errors occurred.

FATS202 IOB SENSE ECB CSW CCW ADDRESS DCB FAILING CCW data corresponding to the above labels FULL SENSE=ff....ff

Reason: This message is issued after message FATS201 when major I/O errors occur. At least the first two lines will be printed, the first containing the titles shown and the second the corresponding diagnostic data in hexadecimal. If the complete sense data produced by the device is available, it will be printed in the third line.

Action: Major errors may indicate severe problems with the tape being processed or problems with the tape unit being used. Appropriate manufacturer's manuals should be consulted to determine the cause of the error. Contact BMC support if you need assistance.

FATS203 A line of the detail report indicating a tape mark read.

FATS204 A line of the detail report indicating a data check.

FATS205 A line of the detail report indicating PRINT threshold met.

FATS206 A line of the detail report showing the compaction achieved for the current line.

FATS207 A line of the detail report indicating operator cancelled, maximum errors exceeded, end-of- tape (tape indicate), or other errors that prevented FATS from completing successfully.

FATS208 A line of the detail report indicating cleaning action.

FATS209 A line of the detail report indicating that an IDRC compacted file was sensed.

FATS210 FATS OPEN/CLOSE SUBTASK ABEND ON DD=TAPEx COMP CODE = Ssss Uuuuu

Reason: The FATS sub-task that handles OPEN, CLOSE, and FATAR has abended with a system (sss) or user (uuuu) abend.

Action: Use of the tape drive on TAPEx will be terminated. If no other TAPEx DD statements are active, FATS will terminate.

FATS211 OPERATOR CANCELLED ANALYSIS ON DD=TAPEn

Reason: Processing of this tape was cancelled by the operator by a reply of KEOJ or Kuuu to the FATSW02 console message, or TERM or SKIP to the FATSW08 console message.

FATS212 TAPEx BLP OR NL NOT ALLOWED FOR ENCRYPTED TAPES. VOL=volser WILL NOT BE ERASED.

Reason: An ERASE operation was requested and NL or BLP was specified on the TAPEx DD, but FATS does not support the use of NL or BLP for encrypted drives. Refer to the Erasing Tapes for the guidelines to follow when erasing encrypted tapes.

FATS213 TAPEx FILE NUMBER GREATER THAN 1 REQUIRED FOR ENCRYPTED TAPES. VOL=volser WILL NOT BE ERASED.

Reason: An ERASE RESIDUAL operation was requested and SL or AL was specified on the TAPEx DD. FATS requires a file sequence number greater than 1 when erasing residual data from encrypted tapes. Refer to Erasing Encrypted Tapes for the guidelines to follow when erasing residual data from encrypted tapes.

FATS214 TAPEx BLP FORCED FOR RESIDUAL ERASE.

Reason: ERASE RESIDUAL was specified, but the LABEL= parameter on the corresponding TAPEx DD contained a value other than BLP. BLP was forced to prevent the tape from being overwritten by the OPEN routines.

FATS215 **RMM UPDATE RETRIED nnn TIMES FOR DSN=dsname ON VOL=volser

Reason: RMMFAIL= RETRY was specified; an attempt to update the RMM information for a data set failed and was retried “nnn” times without success.

Action: The FATSCOPY job will abend.

FATS216 DISP=(,KEEP) REQUIRED ON TAPEOUT DD

Reason: When using TLMS, the TAPEOUT DD statement must contain DISP=(NEW,KEEP) (or DISP=(OLD,KEEP) when appending to an existing volume).

Action: The FATSCOPY  job will terminate with a U100 abend. Add DISP=(NEW,KEEP) if writing to a new scratch tape; add DISP=(OLD,KEEP) if adding files to a non-scratch volume.

FATS217 NO PHYSICAL VOLUMES FOUND FOR LOGICAL VOLUME volser

Reason: The ALLPHYS keyword was used, but the specified logical volume was not found on any physical volume in your virtual tape system.

Action: The FATSCOPY  job will terminate with a U300 abend. Be sure to specify a correct value for VIRTTYPE=, and a valid logical (not physical) volser as a parameter for the ALLPHYS= keyword.

FATS250 **NOT ENOUGH STORAGE FOR TLMS UPDATE WORK AREA.

Reason: FATSCOPY  could not obtain the storage it needed to perform the update of the output file’s information in TLMS.

Action: The file(s) will be copied, but the tape management information will not be copied from the input file to the output file. A FATS148 message will also be issued. Rerun the job using REGION=0M.

FATS251 **tapemgt INFORMATION UPDATED AFTER IMAGE COPY FOR VOLUME=volser

Reason: FATSCOPY has done a successful image copy of the volume and updated tape management information for the volume. The sequence in the list is arbitrary and can be changed for consistency if desired; we often list RMM first since it is the most-commonly-used tape management system: CA-1, CTLT, RMM, TLMS, or ZARA will be substituted for tapemgt in the message text.

Action: For RMM, the following fields have been updated in the volume record: assigned date, assigned time, vendor, compaction, location, volume capacity, storage group, media name, recording format, last read date (set from input volume before copying), last write date (set from input volume before copying), key label 1 and 2, and key encoding 1 and 2.

For CA 1, the following fields have been updated in the volume record: recording technique, last used unit address, temporary and permanent read and write errors since initialized, temporary and permanent read and write errors since last cleaning, date of last cleaning, use count at last cleaning, vendor name, encryption key index, percentage of volume in use, compression ratio, SMS management class, robotic device indicator, last used date (set from input volume before copying, and selected flags.

For TLMS, the following fields have been updated in the volume record: purchase date, tape type, manufacturer, length, out-of-service information, stacking status, box/cabinet ID, cleaning date and counts, read and write error counts, certification date and counts, location, move date, density, and auto tape library name.

FATS252 **VOLUME=volser MOVED TO STORAGE GROUP storgrp.

Reason: After updating the RMM information after a successful image copy of a volume in one storage group to a volume in another storage group, FATSCOPY issued an RMM command to move the volume to the new storage group. The TCDB has also been updated with a volume entry in the new storage group.

FATS253 **tapemgt INFORMATION UPDATED AFTER IMAGE COPY FOR DATA SET=dsname VOL=volser

Reason: After a successful image copy of a data set, FATSCOPY has updated tape management fields for the data set. The sequence in the list is arbitrary and can be changed for consistency if desired; we often list RMM first since it is the most-commonly-used tape management system: CA-1, CTLT, RMM, TLMS, or ZARA will be substituted for tapemgt in the message text.

Action: For RMM, the following fields have been updated in the Data Set Record: last read date (set from input volume before copying), last write date (set from input volume before copying), and storage class.

For TLMS, the following fields (all set from the input volume before copying ) have been updated in the Data Set Record: last used job, last used date, and last used unit.

FATS254 **reason CA-1 UPDATE AFTER IMAGE COPY FOR VOLUME=volser FAILED.

Reason: reason will be either CA-1 NOT ACTIVE or TMC OPEN FAILED. A FATS149 message showing the CA 1 reason codes will follow the FATS254 message.

Action: FATSCOPY will set a return code '8' for the failed update and continue copying the next volume. The volume record in CA 1 needs to be manually updated.

FATS255 **CONTROL CARD ERROR – REASON x

Reason: A syntax or usage error has been detected in the control statement printed immediately preceding the message. Only one FATS255 message will be printed for each input statement (multiple errors will not be diagnosed). x is a character indicating the type of error detected:

2 – SELECT CATDSN specified with IMAGE keyword.

3 – RENAME statement specified with IMAGE keyword.

4 – A TMSIN value was not set by the FATZAPOP installation program or an invalid combination of TMSIN and TMSOUT values has been specified.

5 – NUMVOLS= specified, but the volser specified on the SELECT ALLDSN statement contained no numeric characters.

6 – NUMVOLS= specified with SELECT CATDSN.

7 – Conflicting FILESEQ= or DSSIZE= keywords specified on a SELECT statement.

8 – Invalid value specified with the LOGERROR= keyword. Valid values are CONTINUE and ABEND.

9 – PUNCH specified with SELECT CATDSN. A – Invalid TMSINPUT= value specified.

B – Tape management interface not installed (see Activating the Tape Management Interface), and TMSIN= not specified on the COPY/SIM statement.

Action: FATSCOPY will abend with a U0502 abend code after all control statements have been scanned.

FATS256 **EOT ON TAPEOUT DURING IMAGE COPY, DSN=dsname VOL=volser. COPY TERMINATED.

Reason: When doing an image copy of a volume, FATSCOPY reached the physical end of the output volume before copying all the data from the input volume.

Action: FATSCOPY will stop copying the input volume. If the input volume is part of a multi- volume set, FATSCOPY will skip any other volumes in the set, and continue copying any other volumes that remain. The job will abend with a U0888 after all the available volumes have been copied..

FATS257 **VOLUME=volser NOT MOVED. ALREADY IN CORRECT STORAGE GROUP.

Reason: After updating the RMM volume record following an image copy, FATSCOPY determined the input volume and the output volume were in the same storage group and no updates were necessary.

FATS258 **WARNING** FOLLOWING OPTIONS CHANGED FOR IMAGE COPY:

Reason: IMAGE was specified, but some of the options in the FATSCOPY Option Table or values specified on keywords are not allowed for image copies.

Action: FATSCOPY will print a line following the FATS258 message for each of the options/keywords that were changed because IMAGE was specified.

FATS259 **UNABLE TO UPDATE TLMS INFO FOR VOLUME=volser AFTER IMAGE COPY. CODE=cccccccc, RC=rrrrrrrr

Reason: FATSCOPY performed an image copy for the specified volume, but was unable to update device-specific TLMS information for the volume to show that it now resides on a different device. cccccccc and rrrrrrr can be used to diagnose the cause of the problem.

Action: FATSCOPY will set a return code '8' for the failed update and continue copying the next volume. The volume record in TLMS needs to be manually updated. Contact BMC support for assistance in determining the cause of the update failure.

FATS260 **RECATALOG OF DATA SET FAILED. COMP=comp,DSN=dsname

Reason: During an image copy, FATSCOPY catalogs each copied file to the new output device. When an image copy of a volume fails, FATSCOPY recatalogs all copied files on that volume (or in that multivolume set) back to the original input device since the output tape may not be usable.

Action: The specified data set was not successfully recataloged. comp is the return code from CAMLST CATALOG. You will need to use IDCAMS to catalog the data set to the original input device.

FATS261 **INPUT DATA SET RECATALOGED AFTER FAILED IMAGE COPY. DSN=dsname

Reason: During an image copy, FATSCOPY  catalogs each copied file to the new output device. When an image copy of a volume fails, FATSCOPY recatalogs all copied files on that volume (or in that multivolume set) back to the original input device since the output tape may not be usable.

Action: The specified data set was successfully recataloged.

FATS262 **VOLUME volser BYPASSED FOR IMAGE COPY. NOT ALL DATA SETS SELECTED.

Reason: One or more data sets on the specified volume did not meet the selection criteria. An image copy requires that all data sets on a volume be copied.

Action: The specified volume will not be copied. This message will be repeated for each volume in a multivolume set.

FATS263 **FATSCOPY IMAGE COPY NOT SUPPORTED FOR OUTPUT DEVICE TYPE=xxxxxxxx. JOB TERMINATED.

Reason: An image copy was attempted using an output device which is not supported for image copies. xxxxxxxx is either a hex device type printed as characters, or a text string describing the device.

Action: FATSCOPY will terminate with a U0888 abend.

FATS264 **EXPDT=98000 NOT ALLOWED ON TAPEOUT DD FOR FATSCOPY IMAGE COPIES. EXPDT VALUE IGNORED.

Reason: EXPDT=98000 was specified on the TAPEOUT DD when the IMAGE keyword was specified.

Action: FATSCOPY  will ignore the expiration date specified on the TAPEOUT DD and assign the output expiration using the expiration date for the input volume from tape management, or the current date + 2 if the expiration date has passed.

FATS265 ** CATALOG OF OUTPUT FAILED. DSN=dsname INPUT WILL NOT BE SCRATCHED.

Reason: Cataloging of an output data set failed, and TMSINPUT=SCRCOND was used.

Action: FATSCOPY has not reset the expiration date of the corresponding input data set. A return code 8 is issued.

FATS266 **SYSTEM LOGGER FUNCTION FAILED. RETCODE=retcode, REAS=reascode, FUNCTION=xxxxxxx ….

Reason: An attempt to use the system logger to write an audit record encountered an error.

Action: Be sure that a valid system logger file name has been specified in the AUDITLOG= parameter on the COPY statement, or in the AUDITLOG= value set in the FATSCOPYGlobal Options Table by the FATZAPOP utility program. The job will continue if LOGERROR=CONTINUE was specified; otherwise it will terminate. If a system logger file is not available for FATSCOPY, you can use an AUDIT DD statement to record audit information.

FATS267 **LOGERROR=CONTINUE SPECIFIED. JOB WILL CONTINUE WITHOUT PRODUCING AUDIT RECORDS.

Reason: A system logger error occurred while writing an audit record, and LOGERROR=CONTINUE was specified.

Action: The job continues, but audit records for data sets copied during the job will be missing or incomplete.

FATS268 **LOGERROR=CONTINUE SPECIFIED. UNABLE TO DISCONNECT FROM LOGSTREAM AT END OF JOB.

Reason: An error occurred when attempting to disconnect from the system logger at the end of the copy job.

Action: Contact BMC Support for assistance.

FATS269 **NO AUDIT RECORDS FOR DSN=dsname VOL=volser DUE TO SYSTEM LOGGER ERROR.

Reason: The data set dsname was copied, but no audit record was produced for this data set due to an error writing to the system logger.

Action: The job will continue copying data sets, but may not produce any audit records for the data sets it copies.

FATS270 **TCDB UPDATE FAILED FOR VOLUME=volser. RC=rtncode

Reason: FATSCOPY attempted to update the TCDB after doing an Image Copy, but the update failed. The control statements used to update the TCDB and the error messages issued by Catalog Management will be printed after the FATS270 message.

Action: The job will abend with a U0888. Contact BMC support for assistance.

FATS271 **OPEN OF SYSPRINT DATA SET FAILED. UNABLE TO PRINT CONTROL STATEMENTS AND ERROR MESSAGES.

Reason: FATSCOPY attempted to open the data set that contained the control statements used to update the TCDB and the error messages issued by Catalog Management, but the open of the data set failed.

Action: Control statements and error messages will not be printed. The job will abend with a U0888.

FATS272 **WARNING : UNABLE TO OVERRIDE RMF RETENTION FOR VOLUME=volser. VOLUME MAY NOT BE SCRATCHED. REASON=tlmscode

Reason: TMSINPUT=SCRATCH was used with a volume which had a TLMS RMF retention, and the installation default MANUAL=NO prevents FATSCOPY from overriding the RMF retention to set an explicit expiration date. Depending on the nature of the RMF rule that applies to the volume, the volume may or may not be scratched. tlmscode is an error code from TLMS.

Action: Verify if the volume is scratched after the next run of TLMS maintenance.

FATS273 **LOAD OF FATZARA TAPE MANAGEMENT INTERFACE MODULE FAILED.

Reason: FATSCOPY didn’t find the FATZARA load module in the STEPLIB, JOBLIB, or linklist libraries.

Action: Job will abend with a U0888.

FATS274 **FATSCOPY AND FATZARA MODULE VERSIONS NOT IN SYNC.

Reason: The version of FATZARA loaded from the JOBLIB, STEPLIB, or linklist library didn’t correspond to the version of FATSCOPY that was executing.

Action: Job will abend with a U0888.

FATS275 **INVALID OPTION ON COPY STATEMENT WHEN RESTART SPECIFIED.

Reason: An option on the COPY statement conflicts with RESTART. This includes specifying IMAGE when the DSNTABLE data set was created using SELECT CATDSN, or not specifying IMAGE when the DSNTABLE data set was created by a job where IMAGE was specified.

Action: Job will abend with a U0888.

FATS276 ** NO RECORDS MATCHED SELECTION CRITERIA. AUDIT REPORT WILL NOT BE PRODUCED.

Reason: Keywords were specified to limit the records to be selected by FATAUDIT, but no records matched the selection criteria.

Action: Job will abend with a U0300.

FATS277 ** AUDIT DATA SET CONTAINS NO DATA. REPORT WILL NOT BE PRODUCED.

Reason: An empty Audit data set was used as input to FATAUDIT.

Action: Job will abend with a U0412.

FATS278 ** MERGE SPECIFIED BUT NO AUDITOUT DD FOUND IN JCL.

Reason: FATAUDIT requires an AUDITOUT DD statement when the MERGE keyword is specified.

Action: Job will abend with a U0414.

FATS279 ** BLOCKSIZE FOR OUTPUT DATA SET CHANGED TO 262144. DSN=dsn

Reason: FATSCOPY selected a data set for copying with an undefined record format and a BLKSIZE=0 or another invalid block size in tape management. To prevent data truncation, FATSCOPY copied the data set as if it contained blocks larger than 64K.

Action: FATSCOPY will set a return code '4' for the data set.

FATS280 **LOAD OF CONTROL-M/TAPE TAPE MANAGEMENT INTERFACE MODULE FAILED.

Reason: FATSCOPY didn't find the FATCTT load module in the STEPLIB, JOBLIB, or linklist libraries.

Action: Job will abend with a U0888.

FATS281 **FATSCOPY AND FATCTT MODULE VERSIONS NOT IN SYNC.

Reason: The version of FATCTT loaded from the JOBLIB, STEPLIB, or linklist library didn't correspond to the version of FATSCOPY that was executing.

Action: Job will abend with a U0888.

FATS285 **DSNTABLE DD IS REQUIRED IN JCLMASK WHEN CHECKPT OR RESTART USED. JOB TERMINATED.

Reason: The CHECKPT or RESTART keyword was used in the FATSCOPY control statements, along with the PUNCH keyword, but there was no DSNTABLE DD statement specified in the JCLMASK data set.

Action: The job is terminated. Add a DSNTABLE DD statement to the JCLMASK data set.

FATS286 **PUNCH DATA SET datasetname IS NOT A PDS/PDSE. JOB TERMINATED.

Reason: The data set specified in the PUNCH DD statement is not a partitioned data set.

Action: The job is terminated. Rerun the job using an existing partitioned data set, or change the PUNCH DD statement to allocate a new data set using DSNTYPE=LIBRARY or DSNTYPE=PDS.

FATS287 **UNABLE TO OPEN|CLOSE MEMBER membername IN LIBRARY libraryname

Reason: FATSCOPY was unable to open or close the specified member for output when PUNCH was specified.

Action: The job is terminated. Rerun the job. If the problem persists, contact BMC support for assistance.

FATS288 **WARNING** ONLY nnn VOLSERS GENERATED FOR COMBINATION OF VOL=volser AND NUMVOLS= nnnnn

Reason: The NUMVOLS= value is too large for the specified VOL= value when PUNCH was specified. FATSCOPY generated SELECT statements until it could no longer increment the VOL= value.

Action: A return code 4 is issued; FATSCOPY continues with the next SELECT statement.

FATS289 **UNABLE TO OBTAIN STORAGE FOR PUNCH ROUTINE. NO MEMBERS WILL BE WRITTEN TO LIBRARY.

Reason: An error occurred obtaining storage needed for PUNCH processing.

Action: The job is terminated. Rerun the job using REGION=0M.

FATS290 **PUNCH ROUTINE UNABLE TO OPEN SYSIN. NO MEMBERS WILL BE WRITTEN TO LIBRARY.

Reason: An error occurred reading the FATSCOPYcontrol statements when PUNCH was used.

Action: The job is terminated. Rerun the job. If the problem persists, contact BMC support for assistance.

FATS291 **NO JCLMASK DD FOUND. ONLY FATSCOPY CONTROL STATEMENTS WILL BE WRITTEN TO LIBRARY.

Reason: The PUNCH keyword was used, but no JCLMASK DD statement was used.

Action: Verify that //JCLMASK was specified correctly. If none is used, FATSCOPY will write members to the punch library containing only the generated FATSCOPY control statements. You will have to add JCL to each to use them to run FATSCOPY jobs.

FATS292 **PUNCH KEYWORD SPECIFIED, BUT NO PUNCH DD FOUND. JOB TERMINATED.

Reason: The PUNCH keyword was specified on the COPY/SIM statement, but the required PUNCH DD statement was not found.

Action: The job is terminated. Rerun the job using a PUNCH DD statement to specify the PDS or PDSE into which FATSCOPY should write members containing the job streams generated by PUNCH processing.

FATS293 **TOO MANY CONTROL STATEMENTS SPECIFIED. UNABLE CREATE PUNCH DATA SET MEMBERS.

Reason: More than 2048 control statements and continuation statements were specified in a PUNCH job.

Action: The job is terminated. Break the PUNCH job into smaller jobs using fewer control statements.

FATS294 **SUBSTITUTION ERROR AT POSITION column IN JCLMASK RECORD NUMBER linenumber. NO MEMBERS WILL BE GENERATED.

Reason: A “<” was found in a non-comment statement in the JCLMASK data set, but the following characters did not match one of the allowed substitution variables (<RUNDATE>, <RUNTIME>, <VOLSER>, <$$CNT1>, <$$CNT2>, <$$CNT3> or <$$CNT4>).

Action: The job is terminated without generating any job streams in the punch library.

FATS295 **TOO MANY STATEMENTS IN JCLMASK DATASET. NO MEMBERS WILL BE GENERATED.

Reason: More than 255 statements were found in the JCLMASK data set when using PUNCH.

Action: The job is terminated. Reduce the number of JCL statements in the JCLMASK data set.

FATS296 **SYSIN STATEMENT FOUND IN JCLMASK DATASET. STATEMENT WILL BE IGNORED.

Reason: A SYSIN DD statement referencing a sequential data set was found in the JCLMASK data set when using PUNCH.

Action: This DD statement is ignored. FATSCOPY will insert a //SYSIN DD * statement in each job saved into the punch library.

FATS297 **WARNING** UNABLE TO OPEN LIBRARY libraryname

Reason: FATSCOPY was unable to open the specified punch library.

Action: The job is terminated. Rerun the job. If the problem persists, contact BMC support for assistance.

FATS298 **WARNING** UNABLE TO GENERATE MEMBER NAME FOR VOLUME volser. NO SELECT STMT WILL BE GENERATED FOR THIS VOLSER.

Reason: FATSCOPY attempted to generate a member name for a punch library member, using “F” + volser + an alphabetic suffix character, but the library already contains members using this volser with all suffix characters A-Z.

Action: No SELECT ALLDSN statement will be created using the specified volser. FATSCOPY will proceed to generate a SELECT ALLDSN statement for the next volser, if any.

FATS299 MEMBER membername WRITTEN TO LIBRARY libraryname

Reason: FATSCOPY created a job stream in a new member in the library specified in the PUNCH DD statement.

FATS300 A line of the summary report giving DD name, tape unit address, volume serial, operation performed, termination status, tape length, and data check summary by retry count.

FATS301 END OF REPORT

Reason: Printed at the end of all detail and summary reports.

FATS345 FILTER ERROR REASON=reason -- ENTRY=entry

Reason: The SELECT CATDSN=filter was used to select entries from the system catalogs, and an error occurred. entry indicates the catalog name or the catalog entry on which the error occurred. reason indicates the error:

1 -- NO CATALOGED ENTRIES FOUND -- the filter did not select any entries from the catalogs.

2 -- CATLG ERROR COMP=cccc CODE=reason -- The IBM catalog SVC returned return code xxxx" with reason code "reason”. These codes can be found under message IDC3009I in IBM message manuals.

3 -- CATLG NAME FPL ADDR MISSING -- internal error.

4 -- CATLG VOLSER FPL ADDR MISSING -- internal error.

5 -- CATLG VOLSER 0 OR MORE THAN 20 -- a catalog entry was selected that had either 0 volsers or more than 20 volsers in a CVOL (SYSCTLG) catalog.

7 -- CATLG ENTYPE FPL ADDR MISSING -- internal error.

A -- NAME LAST CHARACTER HIGH VALUES -- internal error.

D -- CANNOT END IN A PERIOD -- The filter cannot end in a period. Refer to Data Set Name Filters (Masks) for filter rules.

E -- INVALID GENERATION NUMBER -- The filter ends in an invalid GDG relative generation number.

F -- SEQUENCE ERROR IN CATALOG -- A VSAM sequence error was encountered reading an ICF catalog, indicating a structural error in the catalog.

G -- ALL ENTRIES EXCLUDED OR DUPS -- all catalog entries selected by this filter were discarded because:
—they were excluded by a preceding EXCLUDE statement
 —they were previously selected by a preceding SELECT CATDSN= statement
 —none were found on the specified VOL or DEVTYPE

J -- INSUFFICIENT STORAGE – the REGION size was not large enough. Increase the REGION (using REGION=0M is recommended) and resubmit.

Action: Serious errors will cause a U0502 ABEND.

FATS346 FILTER SELECTED nnnnn ENTRIES IN sssss.ss SECONDS

Reason: This describes the number of entries selected by the SELECT CATDSN=filter, and the elapsed time in seconds required to complete the search.

FATS347 BVIR VOLUME STATUS: bvir message BVIR VOLUME STATUS: TS7700 LEVEL BELOW VERSION 8

Reason: VIRTZSTD was specified on the COPY statement, but no compression information could be retrieved from the output tape device. Either the device is below version 8, or an error message bvir message was issued by the device.

Action: Verify that the DATACLAS on the TAPEOUT DD statement specifies a data class that will be allocated to an IBM TS7700 virtual tape device that is at version 8 or higher.

FATS348 BVIR VOLUME MAP: bvir message

Reason: PHYSVOL or ALLPHYS was used, but FATSCOPYwas unable to retrieve physical volume mapping from the device specified on the MAPTAPE DD statement. bvir message is information returned by the tape device.

Action: Verify that the input device is a tape-backed TS7700 virtual tape system.

FATS400 program/function -- VER v.r/mmt -- COMPUWARE DATE=yyyy.ddd TIME=hh.mm.ss PAGE nnnn

Reason: General page header message for FATZAPOP programs. The time is not reported by all programs.

FATS401 PARAM DATA -- * parm-field-data *

Reason: Displays the program control information specified in the ‘PARM=’ field of the EXEC statement.

FATS402 INVALID CONTINUATION

Reason: The last FATZAPOP control statement ended in a comma, but there was no next statement or it was not a proper continuation statement.

Action: Correct and resubmit job.

FATS405 MAXIMUM CONTINUATION COUNT OF nnnn EXCEEDED -- COMMAND FLUSHED

Reason: A FATZAPOP control statement used too many continuation statements.

Action: Combine multiple operands onto one line to reduce the number of continuations.

FATS407 type ERROR -- action

Reason: An error was encountered during the processing of FATZAPOP control statements.

This is always proceeded by one or more messages that define and delimit the error(s). “type” will be either PARAMETER FIELD or CONTROL STATEMENT.
The “action” is one of the following:

 JOB TERMINATED – Processing will stop after the first error has been encountered.

 SKIPPING FOR COMMAND – Processing will continue for all command statements found within the SYSIN data set.

 RE-ENTER COMMAND OR END – Message for a user that has SYSIN data set assigned to a TSO terminal. Re-enter command in error or ‘END’ to complete the processing.

Action: Correct and resubmit job.

FATS408 NO CONTROL STATEMENTS WERE FOUND -- JOB TERMINATED

Reason: The SYSIN data set is empty, or contained only comment statements ('*’ in column 1). The first control statement can also be supplied by the EXEC statement PARM= option. There are other forms of this message that indicate that statements required for a certain function were not found.

Action: Correct and resubmit job.

FATS418 COMMAND PROCESSING DETECTED ERROR--action

Reason: An error was encountered during the processing of a FATZAPOP statement. This is always proceeded by one or more messages that define the error. “action” will be one of:

 SKIPPING FOR COMMAND – processing will continue for all command statements found within the SYSIN data set.

 REVERTING TO SYSIN – the error occurred when reading from an alternate command input source. Processing will continue for commands in the SYSIN data set.

 RE-ENTER COMMAND OR END – message for user that has SYSIN data set assigned to a TSO terminal. Re-enter command in error or ‘END’ to complete the processing.

Action: Correct and resubmit job.

FATS465 UNABLE TO OPEN DDNAME=ddname--reason

Reason: An error occurred trying to open “ddname”, for the “reason” displayed.

Action: Check the joblog for IBM OPEN messages. In some cases, the DDname is not required so the message is simply informational. If the DDname is required for the operation being attempted, correct and resubmit the job.

FATS471 DDNAME=ddname I/O ERROR--SYNAD=synadtext

Reason: A permanent I/O error was detected on the data set referenced by “ddname”. The IBM macro SYNADAF was invoked to format the cause of the error; the text returned is “synadtext”.

Action: Examine the SYNADAF text to determine the cause of the error. Check the joblog for IBM I/O error messages. For additional assistance, please contact BMC support.

FATS484 INTERNAL LOGIC ERROR--JOB TERMINATED

Reason: The program has encountered an illogical condition.

Action: Call technical assistance after obtaining a storage dump.

FATS491 function FUNCTION STARTED--hh.mm.ss

Reason: Identifies type of FATZAPOP function and time the function started.

FATS492 function FUNCTION ENDED--hh.mm.ss CONDITION CODE-nnnn

Reason: Identifies type of FATZAPOP function and time the function ended. The return code is printed if nonzero.

FATS493 function--BYPASSED--PRIOR FUNCTION TERMINATED WITH KEYWORD OR COMMAND DETECTED ERROR

Reason: A previous command on which this function may be dependent encountered serious errors.

Action: Correct the condition and re-execute.

FATS496 MODULE modname NOT USABLE WITH RELEASE/SYNC LEVEL nnn PROGRAMS - EXECUTION TERMINATED

Reason: The main FATZAPOP program determined that a subprogram was not at a compatible level, probably because different versions of the FATSCOPY program library are being used.

Action: Contact BMC Support for assistance.

FATS497 program ABNORMALLY TERMINATED DUE TO KEYWORD/COMMAND DETECTED ERRORS

Reason: “program” did not complete normally.

FATS498 program PROCESSING COMPLETED WITH ERRORS

Reason: “program” completed the required processing but non-terminating errors were encountered.

Action: Check the output, correct and rerun or restart as appropriate.

FATS499 program PROCESSING COMPLETED

Reason: “program” completed the required processing successfully.

FATS530 member NOT FOUND--ddname=dsname

Reason: FATZAPOP issued a BLDL for the module “member” in the library “dsname” specified on the DD statement “ddname”, but the module was not found. The module is required.

Action: Verify that the data set name specified on the DD statement was the correct one. If incorrect, change and resubmit the job. If the data set name is correct, check to see if all the installation steps required were done (FATS/FATAR/FATSCOPY Installation). Contact BMC Support for technical assistance..

FATS531 MODULE member CONTAINS NO TEXT RECORDS – ddname=dsname

Reason: Program attempted to read module “member” in the library “dsname” specified on the DD statement “ddname”, but no text records were found. The module is required.

Action: See message FATS530.

FATS532 MODULE member I/O ERROR READING--ddname=dsname

Reason: Program attempted to read module “member” in the library "dsname specified on the DD statement “ddname”, but an I/O error occurred. The module is required.

Action: Other messages may be displayed to further define the I/O error. Check the joblog for IBM error messages. Contact BMC support for technical assistance.

FATS533 MODULE mmmmmmmm I/O ERROR WRITING--ddname=dsname

Reason: Program attempted to update module “mmmmmmmm” in the library “dsname” specified on the DD statement “ddname”, but an I/O error occurred. The update was not completed, but the module might be partially updated. This is a serious error that may result in the load module library becoming unusable.

Action: Other messages may be displayed to further define the I/O error. Check the joblog for IBM error messages. Contact BMC support for technical assistance.

FATS534 ddname OPEN FAILURE--AVAILABLE COMMANDS: HELP, END

Reason: The required library on DD statement “ddname” could not be opened. Commands that access modules in that library cannot be executed.

Action: Check the joblog for IBM OPEN error messages. Correct the error and rerun.

FATS535 mmmmmmmm READ UNSUCCESSFUL--function BYPASSED

Reason: Program attempted to read a member from a library or a data set but the read was not successful. “mmmmmmmm” can be:

 module MODULE – if the error occurred trying to read a load module.

 MEMBER – if the error occurred trying to read another kind of member.

 DATA SET – if the error occurred trying to read a sequential data set or member.

Action: See message FATS530.

FATS538 MODULE member WRONG VER/LEVEL--ddname=dsname

Reason: Program read module “member” in the library “dsname” specified on the DD statement “ddname”, but the module loaded is not at the same level as the calling program.

Action: Verify that the data set name specified on the DD statement was the correct one. If incorrect, change and resubmit the job. If the data set name is correct, check to see if all the installation steps required were done (FATS/FATAR/FATSCOPY Installation). Contact BMC support for technical assistance..

FATS539 MODULE member function--ddname=dsname

Reason: The module “member” in the library “dsname” specified on the DD statement “ddname” has been successfully processed. “function” indicates what operation was done.

FATS540 operand CONTAINS INVALID CHARACTERS--ZAP REJECTED

Reason: The value specified for “operand” contained one or more characters that were not A-Z, 0-9, $#@.

Action: Correct the value and resubmit the job.

FATS542 operand CONTAINS INVALID INDEX STRUCTURE--ZAP REJECTED

Reason: The value specified for “operand” contains two (2) or more consecutive periods (..) in violation of MVS data set naming conventions.

Action: Correct the error and resubmit the job.

FATS543 operand DOES NOT CONTAIN CHARACTER STRING rrrrrrr--ZAP REJECTED

Reason: The value specified for “operand” does not contain the character string “rrrrrrr” as an index level.

Action: Provide a proper data set name and resubmit the job.

FATS544 operand REJECTED--EXCEEDS MODIFIABLE PORTION OF FATOPT

Reason: The length of the value specified for “operand” taken in conjunction with the offset operand exceeds the modifiable portion of FATOPT.

Action: Contact BMC Support for assistance.

FATS545 VERIFY FAILED--CHAR/HEX PRINT FORCED

Reason: The VERIFY of existing contents failed. A character/hex print of the module FATOPT is produced. Always proceeded by message FATS544.

FATS516 function REGISTERS -- R0=xxxxxxxx R1=xxxxxxxx R15=xxxxxxxx

Reason: “function” may be:

–CAMLST – A CAMLST request for a CATALOG operation or a SCRATCH failed.

–CATLG or CATALOG – A request to catalog a data set failed.

–LOCATE – A LOCATE request to read a catalog record failed.

–OBTAIN – An OBTAIN request to read a DSCB from the VTOC failed.

–RENAME – A request to RENAME a data set failed.

–SCRATCH – A SCRATCH request to delete a data set failed.

–UNCATLG – A request to uncatalog a data set failed. The contents of registers 0, 1, and 15 are displayed in hex; R15 will contain the return code but the other registers may have additional diagnostic data. The failing operation may be further described in a preceding message. The return codes are documented in the IBM manual DFSMSdfp Advanced Services, or under message IDC3009I in the System Messages manual.

Action: Check the return codes and take corrective action or call BMC Support for assistance.

FATS541 ALLINDX CREATES name NAME GT nn CHARACTERS--ZAP REJECTED

Reason: The value specified for the operand ALLINDX, when used to replace the first index of the option “name”, creates a character string longer than the limit “nn”.

Action: Shorten the value of ALLINDX by specifying fewer characters and resubmit the job. Some options may have already been changed before the message is issued.

FATS550 ERRORS ENCOUNTERED DURING EXECUTION--REWRITE CANCELLED

Reason: One or more modules from the SYSLIB data set have been updated and were scheduled to be rewritten to the SYSLIB data set. However, previous commands failed to complete successfully so the updates were discarded and the modules were not modified.

Action: Correct the error conditions documented by the error messages and resubmit the job.

FATS569 WARNING -- option NOT CATALOGED--DSN=dsname

Reason: The FATSCOPY Global Options Table was updated with a new data set name. The new data set name was not in the system catalogs and may not exist.

Action: This is only a warning message. The data set name listed has become the new name of the indicated default.

FATS800 LOGGER errortype ERROR. RC=retcode, REAS=reascode

Reason: FATAUDIT encountered an error communicating with the system logger while attempting to access the audit log stream. errortype will be one of the following: CONNECT, START, READCURSOR, DEBLOCKING, DISCONNECT, RECONNECT,or PURGE. This will be accompanied by a U04nn abend.

Action: Contact BMC Support for assistance.

FATS804 INVALID LOG STREAM NAME = streamname

Reason: FATAUDIT could not open a system logger log stream with the specified stream name. This will be accompanied by a U0404 abend.

Action: Verify that the streamname value matches the name used to start the FATSCOPY audit log stream.

FATS805 EMPTY INPUT LOG STREAM = streamname

Reason: FATAUDIT did not find any data in the specified log stream. A FATAUDIT PURGE may have been done without any subsequent copy jobs writing to the log stream. This will be accompanied by a U0805 abend.

FATS900 **NO MATCH IN OPTION TABLE FOR CURRENT UNEXCLUDE. DSN/MASK=dsname

Reason: An UNEXLUDE parameter was specified for the FATZAPOP utility, but there was no matching EXCLUDE saved in the FATSCOPY Option Table for that data set name or mask.

Action: FATZAPOP will set a return code '8' to indicate that an error occurred.

FATS901 **NO SPACE IN OPTION TABLE TO ADD CURRENT ENTRY. DSN/MASK= dsname

Reason: The FATSCOPY Option Table can save up to 20 global EXCLUDE entries. An EXCLUDE parameter was specified for the FATZAPOP utility, but there is no more space available to save it in the Option Table.

Action: FATZAPOP will set a return code '12' to indicate that an error occurred.

FATS902 **DUPLICATE EXCLUDE ENTRY IN TABLE. DSN/MASK= dsname

Reason: An EXCLUDE parameter was specified for the FATZAPOP utility, but there is already an entry for that DSN/mask in the FATSCOPY Option Table. A new entry will not be created in the table.

Action: FATZAPOP will set a return code '12' to indicate that an error occurred.

FATS action messages

The ACTION column of the FATS detail report will contain one of the following messages:

3480 FORMAT FILE SENSED

The current file is a normal 3480 file.

3480XF FORMAT FILE SENSED

The current file is an IDRC compacted 3480 file.

3490E FORMAT FILE SENSED

The current file is a 3490E format file that may or may not be IDRC compacted.

3590 FORMAT FILE SENSED

The current file is a 3590 (Magstar) format file that may or may not be IDRC compacted.

DATA COMPACTED BY XX%

The current file was IDRC compacted by the indicated amount.

TAPE INDICATE

The logical end of tape (end-of-tape reflector or cartridge logical end-of-tape) has been detected by a FATS WRITE operation.

PERM DATA CHECK

An error has been retried until the retry level defining a permanent error (RETRY= parameter) has been reached.

PERM DATA CHECK CNTL

An error was encountered while repositioning the tape for data check retry. No further retries are done. This may indicate serious problems with the tape or drive.

TEMP DATA CHECK

An error has been retried and was successful before the permanent error retry level was reached.

TAPE MARK

A tape mark (end of file) was read during a FATS read operation.

LABEL SAVED

The volume serial was read from the tape and labels were successfully rewritten (the SAVLAB function).

LABEL NOT SAVED

The SAVLAB function was attempted, but labels did not exist or could not be read.

LABEL WRITTEN

Labels with the specified volume serial number have been written to the tape.

LABEL NOT WRITTEN

Labels could not be written due to I/O errors.

TEMP DATA CHK LABEL

Temporary I/O errors were encountered when writing labels but the labels were written successfully.

PERM DATA CHK LABEL

Permanent I/O errors were encountered when writing or saving labels. The labels were not written.

MAX ERROR EXCEEDED

The length in inches of a contiguous data check has exceeded the MAXCERR= parameter specified. Processing of this tape will be terminated.

PRINT THRESHOLD MET

The number of errors printed for this tape exceeds the THRESHOLD= parameter specified. No more errors will be printed in the detail report, but processing will continue.

OPERATOR CANCELLED

Processing of this tape was cancelled by the operator by a reply of KEOJ or Kuuu to the FATSW02 console message or TERM or SKIP to the FATSW08 console message.

OPEN ERROR OR NO DD

Errors occurred opening this tape. Processing of all tapes on this tape unit will be halted.

CLEAN ACTION REQUEST

The number of errors on this tape exceeds the ERRCLEAN= parameter. The operator is requested to clean the tape drive and remount the same tape.