g o Odd parity, data convert off, translate off OC Odd parity, data convert on, translate off OT Odd parity, data convert off, translate on
E Even parity, data convert off, translate off
ET Even parity, data convert off, translate on
1. Tape records written by the CMS TAPE DUMP command are 805 bytes
long. The first character is a binary 2 (X'02'), followed by the
characters CMS and an EBCDIC blank (X'40't, followed by 800 bytes
of file data packed without regard for logical record length. If a
null block is dumped, the character "0" replaces the blank after CMS. This causes subsequent loading of null blocks to be ignored.
In the final record, the character N replaces the blank after CMS, and the data area contains CMS file directory information.
2. If a tape file contains a large number of CMS files that vould not
fit on disk, the tape load operation may terminate if there is not
enough disk space to hold the files. To prevent this, when you
dump the files, separate logical files by tape marks, then forward
space to the appropriate file.
3. Because the CMS file directory is the last record of the file, the TAPE command creates a separate vorkfile so that backspacing and
rereading can be avoided when the disk file is built. If the load
criteria is not satisfied, the vorkfile is erased; if it is
satisfied, the workfile is renamed. This workfile is named TAPE CMSUT1, which may exist if a previous TAPE command has abnormally
terminated. If the work file is accidentally dumped to tape and
subsequently loaded, it appears on your disk as TAPE CMSUT2. 4. It is possible to run a tape off the reel in at least one
situation. If you specify EOF nand n is greater than the number
of tape marks on the tape, the tape will run off the reel.
5. The RUN option (rewind and unload) indicates completion before the
physical operation is completed. Thus, a subsequent operation to
the same physical device may encounter a device busy situation.
6. For more information on tape file handling, see the DMSTPE701I NULL FILE A final record was encountered and no prior records vere read in a TAPE LOAD operation. No file is created on disk. 190 IBM VM/370 CMS Command and Macro Reference

TAPE If the TERM option is in effect, the following is displayed at the
terminal depending on the operation specified: LOADING ••••• fn ft fm SKIPPING ••••• fn ft fm DU MPING ••••. fn ft fm SC ANN ING ••••• fn ft fm When a tape mark is encountered, the following is displayed at the
terminal if the TERM option is specified:
END-OF-FILE OR END-OF-TAPE DMSTPE002E FILE 'fn ft fm' NOT FOUND RC=28 DMSTPE003E INVALID OPTION 'option' RC=24 DMSTPE010E PREMATURE EOF ON FILE 'fn ft fm' RC=40 INVALID FUNCTION 'function' RC=24 DMSTPE017E INVALID DEVICE ADDRESS 'cuu' RC=24 DMSTPE023E NO FILETYPE SPECIFIED RC=24 DMSTPE027E INVALID DEVICE 'device name' RC=24 DMSTPE029E INVALID PARAMETER 'parameter' IN THE OPTION 'option' FIELD
RC=24 DMSTPE037E DISK 'mode! IS READ/ONLY RC=36 NO FILEID SPECIFIED RC=24 'TAPn(cuu)' IS FILE PROTECTED RC=36 NO FUNCTION SPECIFIED RC=24 INVALID MODE 'mode' RC=24 DMSTPE057E INVALID RECORD FORMAT RC=32 DMSTPE05SE END-OF-FILE OR END-OF-TAPE RC=40 DMSTPE070E INVALID PARAMETER 'parameter' RC=24 DMSTPE096E FILE 'fn ft' DATA BLOCK COUNT INCORRECT RC=32 DMSTPE104S ERROR 'nn' READING FILE 'fn ft fm' FROM DISK RC=100 DMSTPE105S ERROR 'nn' WRITING FILE 'fn ft fm' ON DISK RC=100 DMSTPE110S ERROR READING 'TAPn(cuu)' RC=100 DMSTPE111S ERROR WRITING 'TAPn(cuu)' RC=100 DMSTPE113S TAPn(cuu) NOT ATTACHED RC=100 DMSTPE115S {CONVERSION I {719} -TRACK I {SOO, 6250} BPI, TRANSLATION, DUAL DENSITY} FEATURE NOT SUPPORTED ON DEVICE 'cuu' RC=88 Section 2. Commands 191