ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/ovrtapf.htm

1248 lines
62 KiB
HTML

<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Override with Tape File (OVRTAPF)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="OVRTAPF.Top_Of_Page"></a>
<h2>Override with Tape File (OVRTAPF)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#OVRTAPF.PARAMETERS.TABLE">Parameters</a><br>
<a href="#OVRTAPF.COMMAND.EXAMPLES">Examples</a><br>
<a href="#OVRTAPF.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="OVRTAPF"></a>
<p>The Override with Tape File (OVRTAPF) command is used to (1) override (replace) a file named in a program, (2) override certain attributes of a file that are used by a program, or (3) override the file named in a program and override certain attributes of the file processed. Parameters overridden by this command are specified in the file description, in the program, or in other called file override commands.
</p>
<p>If a file named in the program is overridden, the name of that file is specified in the FILE parameter and the name of the overriding file is specified in the TOFILE parameter. The OVRTAPF command can also specify parameters to override values contained in the file description of the overriding file. If the file named in the program is not replaced, but certain parameters of the file are overridden, the name of the file is specified in the FILE parameter and *FILE is specified in the TOFILE parameter. The parameters overridden are then specified by the other parameters of the OVRTAPF command. Parameters that are not specified do not affect the parameters specified in the file description, in the program, or in other called file override commands.
</p>
<p>More information on overriding files is in the Files and file systems topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter, the Application Display Programming book, SC41-5715, and the Basic Printing information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</p>
<p>
<b>Note: </b>Using this command does not cause a file to be overridden immediately. Information provided on this command is stored until the file is used, at which time the file is overridden.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="OVRTAPF.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.FILE"><b>FILE</b></a></td>
<td valign="top">File being overridden</td>
<td valign="top"><i>Name</i></td>
<td valign="top">Required, Positional 1</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#OVRTAPF.TOFILE"><b>TOFILE</b></a></td>
<td valign="top">Overriding to tape file</td>
<td valign="top">Single values: <b><u>*FILE</u></b><br>Other values: <i>Qualified object name</i></td>
<td valign="top" rowspan="3">Optional, Positional 2</td>
</tr>
<tr>
<td valign="top">Qualifier 1: Overriding to tape file</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top"><a href="#OVRTAPF.DEV"><b>DEV</b></a></td>
<td valign="top">Device</td>
<td valign="top">Values (up to 4 repetitions): <i>Name</i></td>
<td valign="top">Optional, Positional 3</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.VOL"><b>VOL</b></a></td>
<td valign="top">Volume identifier</td>
<td valign="top">Single values: *NONE<br>Other values (up to 50 repetitions): <i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#OVRTAPF.REELS"><b>REELS</b></a></td>
<td valign="top">Tape reels specifications</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Label processing type</td>
<td valign="top">
*SL, *NL, *NS, *BLP, *LTM</td>
</tr>
<tr>
<td valign="top">Element 2: Number of reels</td>
<td valign="top">
1-255</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.SEQNBR"><b>SEQNBR</b></a></td>
<td valign="top">Sequence number</td>
<td valign="top">1-16777215, *END, *NEXT</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.LABEL"><b>LABEL</b></a></td>
<td valign="top">File label</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.RCDLEN"><b>RCDLEN</b></a></td>
<td valign="top">Record length</td>
<td valign="top"><i>Integer</i>, *CALC</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.BLKLEN"><b>BLKLEN</b></a></td>
<td valign="top">Block length</td>
<td valign="top">1-524288, *CALC</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.BUFOFSET"><b>BUFOFSET</b></a></td>
<td valign="top">Buffer offset</td>
<td valign="top"><i>Integer</i>, *BLKDSC</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.RCDBLKFMT"><b>RCDBLKFMT</b></a></td>
<td valign="top">Record block format</td>
<td valign="top">*F, *FB, *V, *VB, *D, *DB, *VS, *VBS, *U</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#OVRTAPF.EXTEND"><b>EXTEND</b></a></td>
<td valign="top">Extend</td>
<td valign="top">Single values: *NO<br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Extend file</td>
<td valign="top">
*YES</td>
</tr>
<tr>
<td valign="top">Element 2: Check file</td>
<td valign="top">
<b><u>*NOCHECK</u></b>, *CHECK</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.DENSITY"><b>DENSITY</b></a></td>
<td valign="top">Tape density</td>
<td valign="top"><i>Character value</i>, *DEVTYPE, *CTGTYPE, *FMT3480, *FMT3490E, *FMT3570, *FMT3570E, *FMT3590, *FMT3590E, *QIC120, *QIC525, *QIC1000, *QIC2GB, *QIC2DC, *QIC4GB, *QIC4DC, *QIC3040, *QIC5010, *MLR3, *SLR60, *SLR100, *FMT2GB, *FMT5GB, *FMT7GB, *FMT20GB, *FMT60GB, *ULTRIUM1, 1600, 3200, 6250</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.COMPACT"><b>COMPACT</b></a></td>
<td valign="top">Data compaction</td>
<td valign="top">*DEVD, *NO</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.CODE"><b>CODE</b></a></td>
<td valign="top">Code</td>
<td valign="top">*EBCDIC, *ASCII</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.CRTDATE"><b>CRTDATE</b></a></td>
<td valign="top">Creation date</td>
<td valign="top"><i>Date</i>, *NONE</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.EXPDATE"><b>EXPDATE</b></a></td>
<td valign="top">File expiration date</td>
<td valign="top"><i>Date</i>, *NONE, *PERM</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.ENDOPT"><b>ENDOPT</b></a></td>
<td valign="top">End of tape option</td>
<td valign="top">*REWIND, *LEAVE, *UNLOAD</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#OVRTAPF.USRLBLPGM"><b>USRLBLPGM</b></a></td>
<td valign="top">User label program</td>
<td valign="top">Single values: *NONE<br>Other values: <i>Qualified object name</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Qualifier 1: User label program</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top" rowspan="3"><a href="#OVRTAPF.TBL"><b>TBL</b></a></td>
<td valign="top">Conversion table</td>
<td valign="top">Single values: *DFT, *NONE, *CCSID<br>Other values: <i>Qualified object name</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Qualifier 1: Conversion table</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top"><a href="#OVRTAPF.FROMCCSID"><b>FROMCCSID</b></a></td>
<td valign="top">From CCSID</td>
<td valign="top">1-65533</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.TOCCSID"><b>TOCCSID</b></a></td>
<td valign="top">To CCSID</td>
<td valign="top">1-65533</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.IGCDTA"><b>IGCDTA</b></a></td>
<td valign="top">User specified DBCS data</td>
<td valign="top">*NO, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.WAITFILE"><b>WAITFILE</b></a></td>
<td valign="top">Maximum file wait time</td>
<td valign="top"><i>Integer</i>, *IMMED, *CLS</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.SECURE"><b>SECURE</b></a></td>
<td valign="top">Secure from other overrides</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.OVRSCOPE"><b>OVRSCOPE</b></a></td>
<td valign="top">Override scope</td>
<td valign="top"><b><u>*ACTGRPDFN</u></b>, *CALLLVL, *JOB</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.SHARE"><b>SHARE</b></a></td>
<td valign="top">Share open data path</td>
<td valign="top">*NO, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRTAPF.OPNSCOPE"><b>OPNSCOPE</b></a></td>
<td valign="top">Open scope</td>
<td valign="top">*ACTGRPDFN, *JOB</td>
<td valign="top">Optional</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="OVRTAPF.FILE"></a>
<h3>File being overridden (FILE)</h3>
<p>Specifies the file being used by the program to which this override command is applied. The specified file must be a tape device file when *FILE is specified in the <b>Overriding to tape file (TOFILE)</b> parameter. Otherwise, any device file or database file name can be specified.
</p>
<p>This is a required parameter.
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the file.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.TOFILE"></a>
<h3>Overriding to tape file (TOFILE)</h3>
<p>Specifies the tape file that is used instead of the file specified in the <b>File being overridden (FILE)</b> parameter; or, if *FILE is specified, specifies that certain attributes are overridden by parameters specified in this command. The parameters specified on this command override the other values specified in the tape device file or in the program.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*FILE</u></b></dt>
<dd>The tape device file named on the FILE parameter has some of its parameters overridden by values specified in this command.
</dd>
</dl>
<p><b>Qualifier 1: Overriding to tape file</b>
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the tape device file that is used instead of the overridden file.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is used to locate the tape device file. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the library where the tape device file is located.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.DEV"></a>
<h3>Device (DEV)</h3>
<p>Specifies the names of up to four tape devices, one virtual tape device, or one media library device that are used with the tape device file to perform input/output operations. A media library device is a tape storage device that contains one or more tape drives, tape cartridges, and a part (carriage and picker assembly) for moving tape media between the cartridge storage slots and the tape drives. The order in which the device names are specified here is the order in which tapes placed in the devices are processed. Specify the device names (no more than four) that override the device names specified in the program or in the tape device file. When the number of volumes processed exceeds the number of devices in the DEV list, the devices are used in the same order as specified, wrapping around to the first device as needed.
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the tape device or media library device.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.VOL"></a>
<h3>Volume identifier (VOL)</h3>
<p>Specifies one or more volume identifiers of the tapes that are used by the tape device file. The tapes (volumes) must be written on the devices in the same order as their identifiers are specified here, and in the same order as the device names are specified on the <b>Device (DEV)</b> parameter. If the tape file is opened for read backward, the volume identifiers in the list are processed from last to first, while the devices in the device list are used in first to last order.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*NONE</b></dt>
<dd>No tape volume identifiers are specified for this file. They are supplied before the device file is opened, either in a CHGTAPF or in another Override with Tape File (OVRTAPF) command. If no volume identifiers are specified before the device file is opened, no volume checking is performed beyond verifying that the correct label type volume is put on the device, and no volume names are provided in operator messages.
</dd>
</dl>
<p><b>Other values (up to 50 repetitions)</b>
</p>
<dl>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the identifiers of one or more volumes in the order in which they are placed on the device. Each volume identifier contains a maximum of 6 alphanumeric characters. Use a blank as a separator character when listing multiple identifiers. Up to 50 volume identifiers can be specified. These identifiers are used in messages sent to the operator during processing. The maximum number of reels processed for an *NL, *NS, *BLP, or *LTM input file is determined by the number of volume identifiers in the list.
<p>
<b>Note: </b>If the VOL parameter value used for the file specifies a list of identifiers rather than VOL(*NONE), the number-of-reels part of the REELS parameter is ignored regardless of where it is specified. A description of how the parameter values for the file are determined when overrides are used, the high-level language interface, and the device file when the file is opened is in the Files and file systems topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter. To ensure that the number-of-reels part of the REELS parameter is used (rather than a VOL identifier list) to control the volumes processed by the tape device file, specify VOL(*NONE) in the same command in which the REELS parameter is specified.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.REELS"></a>
<h3>Tape reels specifications (REELS)</h3>
<p>Specifies the type of labeling that is used on the tape reels, and the maximum number of reels processed if there is no list of volume identifiers specified on the <b>Volume identifier (VOL)</b> parameter and this device file is used with either *NL, *LTM, *NS, or *BLP input files. When the number of reels is specified, the volume identifiers of any labeled volumes placed in the tape device are ignored; instead, the order in which the reels are used must be checked by the operator.
</p>
<p>The maximum number of reels specification (the second part of this parameter) is not a limiting value for standard-label input files or output files. For a standard-label input file, the data file labels limit the number of volumes processed by indicating end of file. For an output file, the maximum number of reels value is ignored; the system requests that additional volumes be placed in the device until the file is closed.
</p>
<p>The system checks the first record following the load point on the tape to see (1) whether it has exactly 80 bytes for EBCDIC or at least 80 bytes for ASCII and (2) whether the first 4 bytes contain the values VOL and 1. If so, the reel contains a standard-label tape. *SL and *BLP files require standard-label tape volumes. *NL, *NS, and *LTM tape files cannot process standard-label volumes.
</p>
<p>
<b>Note: </b>The values *SL, *NL, and *LTM can be specified if the device file is used for either reading or writing on tapes. The values *NS and *BLP are valid only if the device file is used to read tapes.
</p>
<p>This parameter overrides the values specified in the device file, in the program, or in other called OVRTAPF commands.
</p>
<p><b>Element 1: Label processing type</b>
</p>
<dl>
<dt><b>*SL</b></dt>
<dd>The volumes have standard labels. If a list of volume identifiers is specified (with the VOL parameter), the system checks that the correct tape volumes are on the device in the specified sequence.
<ul>
<li>If no volume identifier list is given and the file is opened for <i>output</i>, any standard-label volumes may be installed on the device.
</li>
<li>If no volume identifier list is given and the file is opened for <i>input</i>, the first volume may have any volume identifier, but if the file is continued, the system requires the correct continuation volumes to be processed (verified by checking the data file labels). For an input file, the end-of-file message is sent to the program being used when the labels on the last volume processed indicate that it is the last volume for the data file.
</li>
</ul>
</dd>
<dt><b>*NL</b></dt>
<dd>The volumes are not labeled. On a nonlabeled volume, tape marks are used to indicate the end of each data file and the end of the volume. For an <i>input</i> file, the end-of-file message is sent to the program when the number of volumes specified in the volume list have been processed, or, if no list of volume identifiers is provided, when the number of reels specified in the REELS parameter are processed.
</dd>
<dt><b>*NS</b></dt>
<dd>The volumes have nonstandard labels. Each volume must start with some kind of label information, optionally preceded by a tape marker and always followed by a tape marker. This nonstandard label information is ignored. The system spaces forward to a point beyond the tape marker that follows the nonstandard labels and positions the tape at the file's data. Each reel must have a tape marker at the end of the file's data. Information beyond this ending tape marker is ignored. Only a single data file can exist on a nonstandard tape. Standard-label volumes <i>cannot</i> be processed by using the *NS label processing.
<p>For an <i>input</i> file, the end-of-file message is sent to the program using the file when the number of volumes specified in the volume list have been processed, or, if no list of volume identifiers is provided, when the number of reels specified in the REELS parameter are processed.
</p>
</dd>
<dt><b>*BLP</b></dt>
<dd>Standard-label processing is bypassed. Each reel <i>must</i> have standard labels. Although each reel is checked for a standard volume label and each file must have at least one standard header label (HDR1) and one standard trailer label (EOV1 or EOF1), most other label information (such as the data file record length or block length) is ignored. The sequence number of each file on the volume is determined only by the number of tape markers between it and the start of tape (in contrast to *SL processing in which the file sequence number stored in the header and trailer labels of each file are used to locate a data file).
<p>Most of the information in the data file trailer label is ignored, but if an end-of-file (EOF) trailer label is found, the end-of-file message is sent to the program using the tape file. If no end-of-file trailer label is encountered by the time the specified number of volumes or reels have been processed (volume identifier list and REELS parameter), the end-of-file message is immediately sent to the program using the tape file. Bypass label processing can be used when the user does not know the name of the file used or when some file label information is incorrect.
</p>
</dd>
<dt><b>*LTM</b></dt>
<dd>The volumes have no labels but do have a single leading tape marker before the first data file. REELS(*LTM) is processed the same as REELS(*NL) except that when SEQNBR(1) is specified for an output file to create the first data file on the tape, a leading tape marker is written at the start of the tape before the first data block.
</dd>
</dl>
<p><b>Element 2: Number of reels</b>
</p>
<dl>
<dt><b><i>1-255</i></b></dt>
<dd>Specify the maximum number of reels that are processed for an *NL, *LTM, *NS, or *BLP input tape operation when there is no list of volume identifiers used on the <b>Volume identifier (VOL)</b> parameter. If the next reel is not on the device when the end of the currently-processing tape is reached, a message is sent to the operator requesting that the next tape be installed on the next tape device. The number-of-reels value is ignored for a standard label (*SL) processing file, or for any output file.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.SEQNBR"></a>
<h3>Sequence number (SEQNBR)</h3>
<p>Specifies the sequence number of the data file on the tape that is processed.
</p>
<ul>
<li>When standard-label tapes are used, the four-position file sequence number is read from the first header label of the data file.
</li>
<li>When bypass label processing is used, or when standard-label tapes are not used, the system counts the tape marks from the beginning of the tape to locate the data file with the correct sequence number.
</li>
<li>When multiple file, multiple volume tapes are processed using *SL on the <b>Tape reels specifications (REELS)</b> parameter, the file sequence numbers continue consecutively through all of the volumes; each new data file has a sequence number that is one greater than the previous file, regardless of which volume contains the file.
</li>
</ul>
<dl>
<dt><b><i>1-16777215</i></b></dt>
<dd>Specify the file sequence number that overrides the sequence number specified in the program or device file.
</dd>
<dt><b>*END</b></dt>
<dd>The file sequence number is added to the end of the tape.
<p>An error message is shown on the display when a tape device file is used to read from a tape and the *END special value is specified in the tape device file.
</p>
</dd>
<dt><b>*NEXT</b></dt>
<dd>The next file on the tape is processed. If the tape is currently positioned before the first file, the first file on the tape is processed. This value can only be specified in tape files that are used to read from tape. An error message is issued when a tape file is used to write to a tape and *NEXT is specified in the tape file.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.LABEL"></a>
<h3>File label (LABEL)</h3>
<p>Specifies the identifier of the data file that is processed by this tape device file. A label identifier is <i>required</i> for a standard label output file, but is <i>optional</i> for an input file.
</p>
<p>If a data file identifier is specified for any type of label processing other than *SL, it is ignored.
</p>
<dl>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the tape data file identifier.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.RCDLEN"></a>
<h3>Record length (RCDLEN)</h3>
<p>Specifies (in bytes) the length of the records that are contained in the data file that is processed with this device file. The system always uses the record length and block length specified in the data file labels for any standard label input file or output file with *YES specified in the <b>Extend file (EXTEND)</b> parameter, if a second header label (HDR2) is found on the tape and *BLP label processing is not specified. This parameter overrides the value specified in the device file, in the program, or in other called OVRTAPF commands.
</p>
<dl>
<dt><b>*CALC</b></dt>
<dd>No record length is specified for the data file processed. If *CALC is specified, the system attempts to calculate an appropriate record length when the file is opened. *CALC is used for tapes that are not labeled or when there is no HDR2 label if a value other than *CALC is specified in the <b>Block length (BLKLEN)</b> parameter for the file, and if the <b>Record block format (RCDBLKFMT)</b> parameter does not specify spanned or blocked records. In this case, the system calculates an appropriate record length from the block length, record block format, and buffer offset (for an ASCII file) specified for the file. In any other case, the actual record length must be specified by a Change Tape File (CHGTAPF) command or Override with Tape File (OVRTAPF) command, or in the high-level language program that opens the device file.
</dd>
<dt><b><i>integer</i></b></dt>
<dd>Specify a value ranging from 1 through 32767 that specifies the length of each record in the data file. The minimum and maximum record lengths that are allowed for a file are dependent on the record block format, block length, buffer offset (for an ASCII file), and recording code.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.BLKLEN"></a>
<h3>Block length (BLKLEN)</h3>
<p>Specifies (in bytes) the maximum length of the data blocks transferred to or from the tape for input or output operations. The system always uses the block length and record length specified in the data file labels for any standard label input file or output file with *YES specified in the <b>Extend file (EXTEND)</b> parameter, if a second header label (HDR2) is found on the tape and *BLP label processing has not been specified.
</p>
<p>This parameter overrides the value specified in the device file, in the program, or in other OVRTAPF commands.
</p>
<dl>
<dt><b>*CALC</b></dt>
<dd>No block length is specified for the data file processed. If *CALC is specified, the system attempts to calculate an appropriate block length when the file is opened. *CALC can be used for tapes that are not labeled or when there is no HDR2 label if a value other than *CALC is specified in the <b>Record length (RCDLEN)</b> parameter for the file, and if the <b>Record block format (RCDBLKFMT)</b> parameter does not specify spanned or blocked records. In this case, the system calculates an appropriate block length from the record length, record block format, and buffer offset (for an ASCII file) specified for the file. In any other case, the actual block length must be specified by a Change Tape File (CHGTAPF) command or Override with Tape File (OVRTAPF) command, or in the high-level language program that opens the device file.
</dd>
<dt><b><i>1-524288</i></b></dt>
<dd>Specify the maximum length, in bytes, of each block in the data file to be processed. The minimum block length that can be successfully processed is determined by the tape device hardware and AS/400 system machine support functions.
<p>The maximum block length is always 524288 bytes for an input file, but is limited to 9999 bytes if block descriptors must be created for an ASCII output file.
</p>
<p>The following table shows the minimum and maximum block length values allowed for an output file:
</p>
<p>
<pre>
<b>CODE BUFOFSET MIN BLKLEN MAX BLKLEN</b>
------- --------- ---------- ----------
*EBCDIC Ignored 18 524288
*ASCII 0 18 524288
*ASCII *BLKDSC 18 9999
</pre>
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.BUFOFSET"></a>
<h3>Buffer offset (BUFOFSET)</h3>
<p>Specifies the buffer offset value for the start of the first record in each block in the tape data file. A buffer offset value is used for any record block format ASCII file, and is ignored for an EBCDIC tape file. The system always uses the buffer offset specified in the data file labels for any standard label input file or output file with *YES specified in the <b>Extend file (EXTEND)</b> parameter, if a value is contained in the second header label (HDR2) on the tape, and *BLP label processing is not specified.
</p>
<p>The buffer offset parameter specifies the length of any information that precedes the first record in the block. For record block formats *D, *DB, *VS, and *VBS, each record or record segment is preceded by a descriptor that indicates the length of the record or segment. A buffer offset value is used to indicate that there is information ahead of the descriptor word for the first record in each block, or ahead of the data of the first fixed-length record or undefined format record in each block.
</p>
<p>This parameter is not needed for a standard-labeled file that is processed for input if the tape includes a second file header label (HDR2) that contains the buffer offset value. A buffer offset must be provided by the Create Tape File (CRTTAPF) command, Change Tape File (CHGTAPF) command, or Override with Tape File (OVRTAPF) command, or by the file labels for an input file that contains any information (such as a block descriptor) ahead of the first record in each block. If you do not specify a buffer offset when a tape file is created, it is not necessary to specify an offset value when the file is read.
</p>
<p>The only buffer offset values allowed for an output file are zero and *BLKDSC. An existing standard-labeled data file with a buffer offset value in the HDR2 label is extended only if the offset value is either 0 or 4. An offset value of 0 in the HDR2 label adds data blocks with no buffer offset. *BLKDSC must be specified to extend an existing tape data file that contains an offset value of 4 in the HDR2 label.
</p>
<p>This parameter overrides the value specified in the device file, in the program, or in other called OVRTAPF commands.
</p>
<dl>
<dt><b>*BLKDSC</b></dt>
<dd>Block descriptors that are 4 bytes in length are created in any tape file that is created using this device file. Any input file read using this device file assumes 4 bytes of buffer offset information preceding the first record in each data block. This value is valid only for a record block format *D or *DB file. The contents of the buffer offset information of each output data block when BUFOFSET(*BLKDSC) is specified is the actual length of the data block, expressed in zoned decimal format.
</dd>
<dt><b><i>integer</i></b></dt>
<dd>Specify a value ranging from zero through 99 that specifies the length of the buffer offset information that precedes the first record in each data block.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.RCDBLKFMT"></a>
<h3>Record block format (RCDBLKFMT)</h3>
<p>Specifies the type of format blocking attribute of records in the tape data file being processed.
</p>
<p>Record block format *V and *VB records can be processed only for an EBCDIC file; *D and *DB records can be processed only for an ASCII file. If a standard-label tape (label type *SL or *BLP) is being processed and an inconsistent record block format is specified for the volume code, the correct record type is assumed (V or D) for the volume code and a warning message is sent to the program that opens the file. If the record type and code are inconsistent for a nonlabeled volume (label type *NL, *LTM, or *NS), an error message is sent and the file is <i>not</i> opened, because there are no labels to verify the correct volume code.
</p>
<p>If a valid record length, block length, and buffer offset value (for an ASCII file) are specified for fixed-length records but the block attribute is incorrect, the correct block attribute is assumed (changing record block format *F to *FB or record block format *FB to *F), and a warning message is sent to the program that opens the file.
</p>
<p>If a block length is specified that is longer than required to process a maximum length record, then record block format *V, *D, or *VS is changed to *VB, *DB, or *VBS and a warning message is sent to the program that opens the file.
</p>
<p>
<b>Note: </b>When BUFOFSET(*BLKDSC) is specified for the file, a value of 4 should be used for the BUFOFSET part of any BLKLEN calculations, unless existing file labels on the tape specify a different value.
</p>
<p>This parameter overrides the value specified in the device file, in the program, or in other called OVRTAPF commands.
</p>
<dl>
<dt><b>*F</b></dt>
<dd>Fixed length, deblocked, unspanned records in either EBCDIC or ASCII code are processed. The system may change this record block format to *FB, based on other file parameters.
</dd>
<dt><b>*FB</b></dt>
<dd>Fixed length, blocked, unspanned records in either EBCDIC or ASCII code are processed. The system may change this record block format to *F, based on other file parameters.
</dd>
<dt><b>*V</b></dt>
<dd>Variable length, deblocked, records in EBCDIC type V format are processed. The system may change this record block format to *VB, *D, or *DB, based on other file parameters.
</dd>
<dt><b>*VB</b></dt>
<dd>Variable length, blocked, unspanned records in EBCDIC type V formats are processed. The system may change this record block format to *DB, based on the volume code.
</dd>
<dt><b>*D</b></dt>
<dd>Variable length, deblocked, unspanned records in ASCII type D formats are processed. The system may change this record block format to *DB, *V, or *VB, based on other file parameters.
</dd>
<dt><b>*DB</b></dt>
<dd>Variable length, blocked, unspanned records in ASCII type D formats are processed. The system may change this record block format to *VB, based on the volume code.
</dd>
<dt><b>*VS</b></dt>
<dd>Variable length, deblocked, spanned records in either EBCDIC or ASCII code are processed. The system may change this record block format to *VBS, based on other file parameters. The representation of spanned records on the tape is different for EBCDIC and ASCII files, but the system selects the correct format based on the file code.
</dd>
<dt><b>*VBS</b></dt>
<dd>Variable length, blocked, spanned records in either EBCDIC or ASCII code are processed. The representation of spanned records on the tape is different for EBCDIC and ASCII files, but the system selects the correct format based on the file code.
</dd>
<dt><b>*U</b></dt>
<dd>Undefined format records in either EBCDIC or ASCII code are processed. Records are processed as variable length records, where each record written or read is in a separate tape block.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.EXTEND"></a>
<h3>Extend file (EXTEND)</h3>
<p>Specifies, for output operations to tape, whether new records are added to the end of a data file that is currently on the tape. The specific data file is identified by the <b>Sequence number (SEQNBR)</b> parameter and, for a standard-label file, by the <b>File label (LABEL)</b> parameter. If the data file is extended, it becomes the last file on the tape volume. Any data files that follow this data file are overwritten as the specified file is extended.
</p>
<p>This parameter overrides the extend value specified in the device file, in the program, or in other called OVRTAPF commands.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*NO</b></dt>
<dd>Records are not added to the end of the specified data file. Regardless of whether there is already a data file with the specified sequence number on the tape, a new data file is created that overwrites an existing data file and any files that follow it.
</dd>
</dl>
<p><b>Element 1: Extend file</b>
</p>
<dl>
<dt><b>*YES</b></dt>
<dd>New records are added to the end of the specified data file.
</dd>
</dl>
<p><b>Element 2: Check file</b>
</p>
<dl>
<dt><b><u>*NOCHECK</u></b></dt>
<dd>The file is extended without being checked to determine whether it is active.
</dd>
<dt><b>*CHECK</b></dt>
<dd>Before the file is extended, it is checked to determine whether it is active.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.DENSITY"></a>
<h3>Tape density (DENSITY)</h3>
<p>Specifies the density of the data that is written on the tape volume when this device file is created. This parameter is used only for tape files being written to tape; it is ignored for tape files being read from the tape (in the case of files being read from tape, the density on the tape is used).
</p>
<p>The density of a standard-label volume is specified on the INZTAP command, which initializes tapes as standard-label volumes by writing volume labels on them. If the density specified on this parameter is different than the density of a standard-labeled tape, the tape must be reinitialized to the specified density.
</p>
<dl>
<dt><b>*DEVTYPE</b></dt>
<dd>The highest capacity density or format supported by the tape device will be used.
</dd>
</dl>
<dl>
<dt><b></b></dt>
<dd>
<dl>
<dt><b>Device</b></dt>
<dd><b> Highest capacity density or format
</b></dd>
<dt><b>3480</b></dt>
<dd>*FMT3480
</dd>
<dt><b>3490E</b></dt>
<dd>*FMT3490E
</dd>
<dt><b>3570-Bxx</b></dt>
<dd>*FMT3570
</dd>
<dt><b>3570-Cxx</b></dt>
<dd>*FMT3570E
</dd>
<dt><b>3580-001</b></dt>
<dd>*ULTRIUM1
</dd>
<dt><b>3580-002</b></dt>
<dd>*ULTRIUM2
</dd>
<dt><b>3580-003</b></dt>
<dd>*ULTRIUM3
</dd>
<dt><b>3590-Bxx</b></dt>
<dd>*FMT3590
</dd>
<dt><b>3590-Exx</b></dt>
<dd>*FMT3590E
</dd>
<dt><b>3590-Hxx</b></dt>
<dd>*FMT3590H
</dd>
<dt><b>3592-J1A</b></dt>
<dd>*FMT3592A1
</dd>
<dt><b>4685-001</b></dt>
<dd>*VXA2
</dd>
<dt><b>6335</b></dt>
<dd>*QIC3040
</dd>
<dt><b>6343</b></dt>
<dd>*QIC1000
</dd>
<dt><b>6344</b></dt>
<dd>*QIC2GB
</dd>
<dt><b>6348</b></dt>
<dd>*QIC1000
</dd>
<dt><b>6349</b></dt>
<dd>*QIC2GB
</dd>
<dt><b>6368</b></dt>
<dd>*QIC1000
</dd>
<dt><b>6369</b></dt>
<dd>*QIC2GB
</dd>
<dt><b>6379</b></dt>
<dd>*QIC1000
</dd>
<dt><b>6380</b></dt>
<dd>*QIC2GB
</dd>
<dt><b>6381</b></dt>
<dd>*QIC2DC
</dd>
<dt><b>6382</b></dt>
<dd>*QIC4DC
</dd>
<dt><b>6383</b></dt>
<dd>*QIC5010
</dd>
<dt><b>6384</b></dt>
<dd>*SLR60
</dd>
<dt><b>6385</b></dt>
<dd>*QIC5010
</dd>
<dt><b>6386</b></dt>
<dd>*MLR3
</dd>
<dt><b>6387</b></dt>
<dd>*SLR100
</dd>
<dt><b>6390</b></dt>
<dd>*FMT7GB
</dd>
<dt><b>63B0</b></dt>
<dd>*VRT256K
</dd>
<dt><b>7207-122</b></dt>
<dd>*QIC4DC
</dd>
<dt><b>7208-002</b></dt>
<dd>*FMT2GB
</dd>
<dt><b>7208-012</b></dt>
<dd>*FMT5GB
</dd>
<dt><b>7208-222</b></dt>
<dd>*FMT7GB
</dd>
<dt><b>7208-342</b></dt>
<dd>*FMT20GB
</dd>
<dt><b>7208-345</b></dt>
<dd>*FMT60GB
</dd>
<dt><b>9348</b></dt>
<dd>6250
</dd>
</dl>
</dd>
<dt><b>*CTGTYPE</b></dt>
<dd>The highest capacity density or format supported by the device for the mounted cartridge type will be used. If the device does not support special cartridge type information, *DEVTYPE is used.
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the density or format to use.
<dl>
<dt><b>1600</b></dt>
<dd>The data density on the tape volume is 1,600 bits per inch, which is used for 1/2 inch reel tapes.
</dd>
<dt><b>3200</b></dt>
<dd>The data density on the tape volume is 3,200 bits per inch, which is used for 1/2 inch reel tapes.
</dd>
<dt><b>6250</b></dt>
<dd>The data density on the tape volume is 6,250 bits per inch, which is used for 1/2 inch reel tapes.
</dd>
<dt><b>*FMT3480</b></dt>
<dd>The format of this tape is FMT3480. The data density on this tape volume is formatted to support a 3480 device. This density is used for 1/2 inch cartridge tapes.
</dd>
<dt><b>*FMT3490E</b></dt>
<dd>The format of this tape is FMT3490E. The data density on this tape volume is formatted to support a 3490E device. This density is used for 1/2 inch cartridge tapes.
</dd>
<dt><b>*FMT3570</b></dt>
<dd>The format of this tape is FMT3570. The data format is written on the tape volume with a 3570 device.
</dd>
<dt><b>*FMT3570E</b></dt>
<dd>The format of this tape is FMT3570E. The data format is written on the tape volume with a 3570E device.
</dd>
<dt><b>*FMT3590</b></dt>
<dd>The format of this tape is FMT3590. The data format is written on the tape volume with a 3590 device. This density is used for 1/2 inch cartridge tapes.
</dd>
<dt><b>*FMT3590E</b></dt>
<dd>The format of this tape is FMT3590E. The data format is written on the tape volume with a 3590E device. This density is used for 1/2 inch cartridge tapes.
</dd>
<dt><b>*FMT3590H</b></dt>
<dd>The format of this tape is FMT3590H. The data format is written on the tape volume with a 3590H device. This density is used for 1/2 inch cartridge tapes.
</dd>
<dt><b>*FMT3592A1</b></dt>
<dd>The format of this tape is FMT3592A1. The data format is written on the tape volume with a 3592 device. This density is used for 1/2 inch cartridge tapes.
</dd>
<dt><b>*QIC120</b></dt>
<dd>The format of this tape is QIC120, which is used for 1/4 inch cartridge tapes that can hold 120 megabytes of data.
</dd>
<dt><b>*QIC525</b></dt>
<dd>The format of this tape is QIC525, which is used for 1/4 inch cartridge tapes that can hold 525 megabytes of data.
</dd>
<dt><b>*QIC1000</b></dt>
<dd>The format of this tape is QIC1000, which is used for 1/4 inch cartridge tapes that can hold 1200 megabytes of data.
</dd>
<dt><b>*QIC2GB</b></dt>
<dd>The format of this tape is QIC2GB. It is used by 1/4 inch tape devices which can store 2.5 gigabytes of data on a standard length QIC2GB cartridge.
</dd>
<dt><b>*QIC2DC</b></dt>
<dd>The format of this tape is QIC2DC. It is used to write compacted data to a 1/4 inch cartridge that supports the QIC2GB format.
</dd>
<dt><b>*QIC4GB</b></dt>
<dd>The format of this tape is QIC4GB. It is used by 1/4 inch tape devices which can store 4 gigabytes of data on a standard length QIC4GB cartridge.
</dd>
<dt><b>*QIC4DC</b></dt>
<dd>The format of this tape is QIC4DC. It is used to write compacted data to a 1/4 inch cartridge that supports the QIC4GB format.
</dd>
<dt><b>*QIC3040</b></dt>
<dd>The format of this tape is QIC3040, which is used for 1/4 inch minicartridge tapes that can hold 840 megabytes of data.
</dd>
<dt><b>*QIC5010</b></dt>
<dd>The format of this tape is QIC5010, which is used for 1/4 inch cartridge tapes that can hold 13.5 gigabytes of data.
</dd>
<dt><b>*MLR3</b></dt>
<dd>The format of this tape is MLR3. It is used by 1/4 inch tape devices which can store 25 gigabytes of data on a standard length MLR3 cartridge.
</dd>
<dt><b>*SLR60</b></dt>
<dd>The format of this tape is SLR60. It is used by 1/4 inch tape devices which can typically store 60 gigabytes of compacted data on a standard length SLR60 cartridge.
</dd>
<dt><b>*SLR100</b></dt>
<dd>The format of this tape is SLR100. It is used by 1/4 inch tape devices which can typically store 100 gigabytes of compacted data on a standard length SLR100 cartridge.
</dd>
<dt><b>*FMT2GB</b></dt>
<dd>The format of this tape is FMT2GB, which is used for 8 millimeter cartridge tapes that can hold 2 gigabytes of data.
</dd>
<dt><b>*FMT5GB</b></dt>
<dd>The format of this tape is FMT5GB, which is used for 8 millimeter cartridge tapes that can hold 5 gigabytes of data.
</dd>
<dt><b>*FMT7GB</b></dt>
<dd>The format of this tape is FMT7GB, which is used for 8 millimeter cartridge tapes that can hold 7 gigabytes of data.
</dd>
<dt><b>*FMT20GB</b></dt>
<dd>The format of this tape is FMT20GB. It is used by 8 millimeter tape devices that can store 20 gigabytes of data on a standard length cartridge.
</dd>
<dt><b>*FMT60GB</b></dt>
<dd>The format of this tape is FMT60GB. It is used by 8 millimeter tape devices that can store 60 gigabytes of data on a standard length cartridge.
</dd>
<dt><b>*ULTRIUM1</b></dt>
<dd>The format of this tape is ULTRIUM1. It is used by 1/2 inch cartridge tape devices that can store 100 gigabytes of data on a standard length cartridge.
</dd>
<dt><b>*ULTRIUM2</b></dt>
<dd>The format of this tape is ULTRIUM2. It is used by 1/2 inch cartridge tape devices that can store 200 gigabytes of data on a standard length cartridge.
</dd>
<dt><b>*ULTRIUM3</b></dt>
<dd>The format of this tape is ULTRIUM3. It is used by 1/2 inch cartridge tape devices that can store 400 gigabytes of data on a standard length cartridge.
</dd>
<dt><b>*VRT32K</b></dt>
<dd>The format of the volume is VRT32K. It is used to write data to a virtual volume using a maximum data block size of 32KB. Volumes written using this format can be duplicated to all supported tape devices.
</dd>
<dt><b>*VRT64K</b></dt>
<dd>The format of the volume is VRT64K. It is used to write data to a virtual volume using a maximum data block size of 64KB. Volumes written using this format can only be duplicated to tape devices that support a maximum block size of 64KB or greater.
</dd>
<dt><b>*VRT240K</b></dt>
<dd>The format of the volume is VRT240K. It is used to write data to a virtual volume using a maximum data block size of 240KB. Volumes written using this format can only be duplicated to tape devices that support a maximum block size of 240KB or greater.
</dd>
<dt><b>*VRT256K</b></dt>
<dd>The format of the volume is VRT256K. It is used to write data to a virtual volume using a maximum data block size of 256KB. Volumes written using this format can only be duplicated to tape devices that support a maximum block size of 256KB or greater.
</dd>
<dt><b>*VXA1</b></dt>
<dd>The format of this tape is VXA1. It is used by VXA cartridge tape devices that can store 33 gigabytes of data on a standard length cartridge.
</dd>
<dt><b>*VXA2</b></dt>
<dd>The format of this tape is VXA2. It is used by VXA cartridge tape devices that can store 80 gigabytes of data on a standard length cartridge.
</dd>
</dl>
<p>
<b>Note: </b>Self-configured tape devices may define additional valid values for the density parameter. Use iSeries Navigator (Configuration and Service) (Hardware) (Tape Devices) (Tape Libraries) (Tape Resources) (Properties) or (Configuration and Service)(Hardware) (Tape Devices) (Stand-Alone Devices) (Properties) to find additional valid density values for a specific device, or use the F4=Prompt key on the "Tape density" field of the CL command to see a list of all valid density values for the attached tape devices.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.COMPACT"></a>
<h3>Data compaction (COMPACT)</h3>
<p>Specifies whether device data compaction is performed. If the tape devices being used do not support data compaction, this parameter will be ignored when the file is opened.
</p>
<p>This parameter overrides the value specified in the device file, in the program or in other called OVRTAPF commands.
</p>
<dl>
<dt><b>*DEVD</b></dt>
<dd>Device data compaction is performed if the devices being used support data compaction.
</dd>
<dt><b>*NO</b></dt>
<dd>Device data compaction is not performed.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.CODE"></a>
<h3>Code (CODE)</h3>
<p>Specifies the type of character code that is used by the tape device file when the system is reading or writing tape data.
</p>
<dl>
<dt><b>*EBCDIC</b></dt>
<dd>The EBCDIC character code is used with this tape device file.
</dd>
</dl>
<dl>
<dt><b>*ASCII</b></dt>
<dd>The ASCII character code is used.
</dd>
</dl>
<p>
<b>Note: </b>For standard labeled (*SL) tapes the CODE parameter is used to determine how the labels are processed. For all label types the TBL, FROMCCSID, and TOCCSID parameters control what conversion, if any, is used for the data portion of the files.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.CRTDATE"></a>
<h3>Creation date (CRTDATE)</h3>
<p>Specifies, for tape input data files and for tape output for which *YES is specified in the <b>Extend file (EXTEND)</b> parameter, the date when the data file was written to tape. The creation date of the data file is stored in file labels on the tape. If a creation date is specified for any type of label processing other than *SL, it is ignored.
</p>
<p>This parameter overrides the value specified in the program, device file, or in other called OVRTAPF commands.
</p>
<dl>
<dt><b>*NONE</b></dt>
<dd>The creation date of the data file is not checked.
</dd>
<dt><b><i>date</i></b></dt>
<dd>Specify the creation date of the data file. The date must be specified in job-date format.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.EXPDATE"></a>
<h3>File expiration date (EXPDATE)</h3>
<p>Specifies, for tape output data files, the expiration date of the data file used by this device file. The data file expiration date is stored in file labels on the tape. If an expiration date is specified for any type of label processing other than *SL, it is ignored. If a date is specified, the data file is protected and cannot be overwritten until the specified expiration date.
</p>
<p>This parameter overrides the value specified in the program, device file, or in other called OVRTAPF commands.
</p>
<dl>
<dt><b>*NONE</b></dt>
<dd>No expiration date for the data file is specified; the file is not protected. An expiration date is written in the data file labels so the file can be used as a scratch data file.
</dd>
<dt><b>*PERM</b></dt>
<dd>The data file is protected permanently. The date written in the tape data file is 999999.
</dd>
<dt><b><i>date</i></b></dt>
<dd>Specify the date on which the data file expires. The date must be specified in job-date format.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.ENDOPT"></a>
<h3>End of tape option (ENDOPT)</h3>
<p>Specifies the operation that is automatically performed on the tape volume after the operation ends. If more than one volume is included, this parameter applies only to the last tape volume used; all other tape volumes are rewound and unloaded when the end of the tape is reached.
</p>
<dl>
<dt><b>*REWIND</b></dt>
<dd>The tape is rewound, but not unloaded.
</dd>
</dl>
<dl>
<dt><b>*UNLOAD</b></dt>
<dd>The tape is automatically rewound and unloaded after the operation ends.
</dd>
</dl>
<dl>
<dt><b>*LEAVE</b></dt>
<dd>The tape does not rewind or unload after the operation ends. It remains at the current position on the tape drive.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.USRLBLPGM"></a>
<h3>User label program (USRLBLPGM)</h3>
<p>Specifies that a program processes user header and trailer labels on a standard-labeled tape. This parameter is valid only when *SL is specified in the <b>Tape reels specifications (REELS)</b> parameter.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*NONE</b></dt>
<dd>Only standard label processing is used. No program is called to process user labels.
</dd>
</dl>
<p><b>Qualifier 1: User label program</b>
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the program that is called to process user labels.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is used to locate the program. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the library where the program is located.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.TBL"></a>
<h3>Conversion table (TBL)</h3>
<p>Specifies the qualified name of a conversion table to be used for single-byte conversion of input files or output files. The specified conversion is only used for the data portion of the files. When the specified code is *ASCII (CODE parameter) any labels will be converted between ISO/ASCII 8-Bit code and EBCDIC. When the specified code is *EBCDIC (CODE parameter) the labels, if any, are not converted.
</p>
<p>
<b>Note: </b>See system supplied conversion tables QSYS/QASCII and QSYS/QEBCDIC for an example of the conversion used to translate between ISO/ASCII 8-Bit code and EBCDIC.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*DFT</b></dt>
<dd>When the specified code is *ASCII (CODE parameter) the data and labels will be converted between ISO/ASCII 8-bit code and EBCDIC. When the specified code is *EBCDIC (CODE parameter) the data and labels will not be converted.
</dd>
<dt><b>*NONE</b></dt>
<dd>The data will not be converted.
</dd>
<dt><b>*CCSID</b></dt>
<dd>The CCSID parameters are used to generate a conversion table to use for converting the data portion of the files.
</dd>
</dl>
<p><b>Qualifier 1: Conversion table</b>
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of a conversion table to be used for conversion of the data between single-byte character sets.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is used to locate the program. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the library to be searched.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.FROMCCSID"></a>
<h3>From CCSID (FROMCCSID)</h3>
<p>Specifies a single-byte CCSID used for the input data. The input data is the data read from the tape for input operations, or read from a file for output operations.
</p>
<dl>
<dt><b><i>1-65533</i></b></dt>
<dd>The requested CCSID value is used. The value is validated to ensure that a single-byte CCSID is specified.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.TOCCSID"></a>
<h3>To CCSID (TOCCSID)</h3>
<p>Specifies the single-byte CCSID used for the output data. The output data is the data written to the tape for output operations, or written to a file for input operations.
</p>
<dl>
<dt><b><i>1-65533</i></b></dt>
<dd>The requested CCSID value is used. The value is validated to ensure that a single-byte CCSID is specified.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.IGCDTA"></a>
<h3>User specified DBCS data (IGCDTA)</h3>
<p>Specifies whether the file processes double-byte character set (DBCS) data.
</p>
<dl>
<dt><b>*YES</b></dt>
<dd>For program described files, indicates that the file is used to process DBCS data. For field level files, the fields that are defined with the ALTTYP keyword are changed from ALPHA fields or character fields to DBCS fields.
</dd>
<dt><b>*NO</b></dt>
<dd>For program described files, indicates that the file is not used to process DBCS data. For field level files, the fields that are defined with the ALTTYP keyword remain ALPHA fields or character fields. The file attribute remains at whatever it was set to when the file was created.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.WAITFILE"></a>
<h3>Maximum file wait time (WAITFILE)</h3>
<p>Specifies the number of seconds that the program waits for the file resources to be allocated when the file is opened, or the device or session resources to be allocated when an acquire operation is performed to the file. If the file resources cannot be allocated in the specified wait time, an error message is sent to the program.
</p>
<dl>
<dt><b>*IMMED</b></dt>
<dd>The program does not wait. Immediate allocation of file resources is required.
</dd>
</dl>
<dl>
<dt><b>*CLS</b></dt>
<dd>The default wait time specified in the class description is used as the wait time for the file resources to be allocated.
</dd>
<dt><b><i>integer</i></b></dt>
<dd>Specify the number of seconds that the program waits for the file resources to be allocated to the tape file when the file is opened, or the wait time for the device allocated when an acquire operation is performed to the file. Valid values range from 1 through 32767 seconds.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.SECURE"></a>
<h3>Secure from other overrides (SECURE)</h3>
<p>Specifies whether this file is safe from the effects of file override commands started in previously called programs.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>This file is not protected from other file overrides; its values are overridden by the effects of any file override commands started in previously called programs.
</dd>
<dt><b>*YES</b></dt>
<dd>This file is protected from the effects of any file override commands started in previously called programs.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.OVRSCOPE"></a>
<h3>Override scope (OVRSCOPE)</h3>
<p>Specifies the extent of influence (scope) of the override.
</p>
<dl>
<dt><b><u>*ACTGRPDFN</u></b></dt>
<dd>The scope of the override is determined by the activation group of the program that calls this command. When the activation group is the default activation group, the scope equals the call level of the calling program. When the activation group is not the default activation group, the scope equals the activation group of the calling program.
</dd>
<dt><b>*CALLLVL</b></dt>
<dd>The scope of the override is determined by the current call level. All open operations done at a call level that is the same as or higher than the current call level are influenced by this override.
</dd>
<dt><b>*JOB</b></dt>
<dd>The scope of the override is the job in which the override occurs.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.SHARE"></a>
<h3>Share open data path (SHARE)</h3>
<p>Specifies whether the open data path (ODP) is shared with other programs in the same routing step. When an ODP is shared, the programs accessing the file share facilities such as the file status and the buffer.
</p>
<dl>
<dt><b>*NO</b></dt>
<dd>An ODP created for this file open operation is not shared. Every time a program opens the file, a new ODP to the file is created and started.
</dd>
<dt><b>*YES</b></dt>
<dd>If the file is opened more than once, the same ODP is shared with each program in the routing step that also specifies *YES for this parameter when it opens the file. This includes multiple open operations in the same program.
<p>
<b>Note: </b>When SHARE(*YES) is specified and control is passed to a program, a read operation in that program retrieves the next input record. A write operation produces the next output record.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRTAPF.OPNSCOPE"></a>
<h3>Open scope (OPNSCOPE)</h3>
<p>Specifies the extent of influence (scope) of the open operation.
</p>
<dl>
<dt><b>*ACTGRPDFN</b></dt>
<dd>The scope of the open operation is determined by the activation group of the program that called the OVRTAPF command processing program. If the activation group is the default activation group, the scope is the call level of the caller. If the activation group is a non-default activation group, the scope is the activation group of the caller.
</dd>
<dt><b>*JOB</b></dt>
<dd>The scope of the open operation is the job in which the open operation occurs.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="OVRTAPF.COMMAND.EXAMPLES">Examples</a> </h3>
<p><b>Example 1: Overriding a File</b>
</p>
<p>
<pre>
OVRTAPF FILE(OUT) VOL(DPT706) LABEL(STATUSR)
</pre>
</p>
<p>This command overrides a file named OUT in the program using the data file STATUSR on tape volume DPT706.
</p>
<p><b>Example 2: Allowing DBCS Data</b>
</p>
<p>
<pre>
OVRTAPF FILE(IGCLIB/IGCTAP) IGCDTA(*YES)
</pre>
</p>
<p>This command overrides the tape device file named IGCTAP, which is stored in the library IGCLIB, so the file may contain double-byte character set data.
</p>
<p><b>Example 3: Using Data Density of 1600 Bits Per Inch</b>
</p>
<p>
<pre>
OVRTAPF FILE(OUT) DENSITY(1600)
</pre>
</p>
<p>This command overrides a file named OUT to use a data density of 1600 bits per inch when writing to the tape volume.
</p>
<p><b>Example 4: Using a Conversion Table to Process a Tape with EBCDIC Labels.</b>
</p>
<p>
<pre>
OVRTAPF FILE(FILE1) REELS(*SL) CODE(*EBCDIC)
TBL(LIB1/TABLE1)
</pre>
</p>
<p>This command overides a tape device file named FILE1 to specify that a conversion table named LIB1/TABLE1 is to be used to convert all data read from, or written to, the tape volume.
</p>
<p><b>Example 5: Using Specified CCSIDs to Process a Non-labeled Tape.</b>
</p>
<p>
<pre>
OVRTAPF FILE(FILE2) REELS(*NL) TBL(*CCSID)
FROMCCSID(819) TOCCSID(37)
</pre>
</p>
<p>This command overides a tape device file named FILE2 to specify that any data read from, or written to, the tape volume is to be converted from CCSID 819 to CCSID 37.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="OVRTAPF.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF180C</b></dt>
<dd>Function &amp;1 not allowed.
</dd>
<dt><b>CPF1892</b></dt>
<dd>Function &amp;1 not allowed.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRTAPF.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>