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

575 lines
25 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<!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 Display File (OVRDSPF)</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="OVRDSPF.Top_Of_Page"></a>
<h2>Override with Display File (OVRDSPF)</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="#OVRDSPF.PARAMETERS.TABLE">Parameters</a><br>
<a href="#OVRDSPF.COMMAND.EXAMPLES">Examples</a><br>
<a href="#OVRDSPF.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="OVRDSPF"></a>
<p>The Override with Display File (OVRDSPF) command is used to: (1) override (replace) the file named in the program, (2) override certain parameters of a file that are used by the program, or (3) override the file named in the program <i>and</i> override certain parameters 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 (the file being processed) is specified in the TOFILE parameter. The OVRDSPF command also specifies 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 OVRDSPF command. Parameters that are not specified do not affect parameters specified in the file description, in the program, or in other called file override commands.
</p>
<p>More information on override files is in the Application Display Programming book, SC41-5715.
</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="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="OVRDSPF.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="#OVRDSPF.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="#OVRDSPF.TOFILE"><b>TOFILE</b></a></td>
<td valign="top">Overriding to display 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 display 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="#OVRDSPF.DEV"><b>DEV</b></a></td>
<td valign="top">Device</td>
<td valign="top">Values (up to 50 repetitions): <i>Name</i>, *REQUESTER</td>
<td valign="top">Optional, Positional 3</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#OVRDSPF.CHRID"><b>CHRID</b></a></td>
<td valign="top">Character identifier</td>
<td valign="top">Single values: *DEVD, *SYSVAL, *JOBCCSID, *CHRIDCTL<br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Graphic character set</td>
<td valign="top">
<i>Integer</i></td>
</tr>
<tr>
<td valign="top">Element 2: Code page</td>
<td valign="top">
<i>Integer</i></td>
</tr>
<tr>
<td valign="top"><a href="#OVRDSPF.DECFMT"><b>DECFMT</b></a></td>
<td valign="top">Decimal format</td>
<td valign="top">*FILE, *JOB</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRDSPF.SFLENDTXT"><b>SFLENDTXT</b></a></td>
<td valign="top">SFLEND text</td>
<td valign="top">*MSG, *FILE</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRDSPF.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="#OVRDSPF.IGCEXNCHR"><b>IGCEXNCHR</b></a></td>
<td valign="top">DBCS extension characters</td>
<td valign="top">*YES, *NO</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRDSPF.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="#OVRDSPF.WAITRCD"><b>WAITRCD</b></a></td>
<td valign="top">Maximum record wait time</td>
<td valign="top">1-32767, *NOMAX, *IMMED</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRDSPF.LVLCHK"><b>LVLCHK</b></a></td>
<td valign="top">Record format level check</td>
<td valign="top">*NO</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRDSPF.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="#OVRDSPF.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" rowspan="3"><a href="#OVRDSPF.DTAQ"><b>DTAQ</b></a></td>
<td valign="top">Data queue</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: Data queue</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="#OVRDSPF.SHARE"><b>SHARE</b></a></td>
<td valign="top">Share open data path</td>
<td valign="top">*YES, *NO</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#OVRDSPF.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="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="OVRDSPF.FILE"></a>
<h3>File being overridden (FILE)</h3>
<p>Specifies the file in the using program to which this override command is applied. The specified file must be a display device file when *FILE is specified in the <b>Overriding to display 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="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.TOFILE"></a>
<h3>Overriding to display file (TOFILE)</h3>
<p>Specifies the display 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 same parameters specified in the display device file, in the program, or in other called (OVRDSPF) commands.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*FILE</u></b></dt>
<dd>The display device file named in the FILE parameter has some of its parameters overridden by values specified in this command.
</dd>
</dl>
<p><b>Qualifier 1: Overriding to display file</b>
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the display 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 device file. If no current library entry exists in the library list, QGPL is used.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the library where the device file is located.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.DEV"></a>
<h3>Device (DEV)</h3>
<p>Specifies the names of one or more display devices that are used with the display device file. This parameter overrides the device names specified in the device file, in the program, or in other called Override with Display File (OVRDSPF) commands. The device name specified in the IBM-supplied display device file is *REQUESTER.
</p>
<p>This parameter overrides the device names specified in the device file, in the program, or in other called OVRDSPF commands.
</p>
<dl>
<dt><b><u>*REQUESTER</u></b></dt>
<dd>The display device from which the program is called is the device assigned to the file when the file is opened.
</dd>
</dl>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the names of one or more display devices that are used with this device file to pass data records between the users of the devices and the system. Each device name must already be known on the system (in a device description) before this device file is created. *REQUESTER can be specified as one of the names.
<p>A maximum of 50 device names (including *REQUESTER, if it is specified) can be specified in this command, but the total number cannot exceed the number specified on the <b>Maximum devices (MAXDEV)</b> parameter when the file is opened.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.CHRID"></a>
<h3>Character identifier (CHRID)</h3>
<p>Specifies the character identifier (graphic character set and code page) for the file. When a display file that was created with the CHRID DDS keyword is used with a work station device, the system translates data sent to and received from the device (as necessary) to ensure that the correct characters are displayed, and the correct hexadecimal byte values are returned to the application program. More information about display file CHRID processing and the translation tables that are used to convert data sent to and received from the display are in the Application Display Programming book, SC41-5715.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*DEVD</b></dt>
<dd>The CHRID value specified in the device description of the work station on which the application is running is used. The *DEVD value means no translation is necessary because the file has the same character identifier as the work station. For a list of valid values, see the CHRID parameter of the Create Device Description Display (CRTDEVDSP) command.
</dd>
<dt><b>*SYSVAL</b></dt>
<dd>The CHRID value specified for the system on which the application is running is used. Translation may be necessary depending on the character identifier of the work station.
</dd>
<dt><b>*JOBCCSID</b></dt>
<dd>The character data is changed from the device CHRID to the CCSID (coded character set identifier) of the job on display file input, and from the CCSID of the job to the device CHRID on display file output. The character data is converted, if necessary, from the device CCSID (coded character set identifier) of the job during input, and from the CCSID of the job to the device CHRID on output.
<p>
<b>Note: </b>This value is not allowed if the file was created on a system at an earlier release level than V2R3M0.
</p>
</dd>
<dt><b>*CHRIDCTL</b></dt>
<dd>The system checks the CHRIDCTL job definition attribute to determine whether to use *JOBCCSID or *DEVD on the CHRID command parameter for this file.
</dd>
</dl>
<p><b>Element 1: Graphic character set</b>
</p>
<dl>
<dt><b><i>integer</i></b></dt>
<dd>Specify the graphic character set value that matches the attributes of the display device. Valid values range from 1 through 32,767.
</dd>
</dl>
<p><b>Element 2: Code page</b>
</p>
<dl>
<dt><b><i>integer</i></b></dt>
<dd>Specify the code page value that matches the attributes of the display device. Valid values range from 1 through 32,767.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.DECFMT"></a>
<h3>Decimal format (DECFMT)</h3>
<p>Specifies which decimal format value is used when editing numeric fields with the EDTCDE DDS keyword. The decimal format value determines the use of commas and periods for the decimal position and three digit positional separators on edited fields.
</p>
<dl>
<dt><b>*FILE</b></dt>
<dd>Use the decimal format value stored with the file when the file was created.
</dd>
<dt><b>*JOB</b></dt>
<dd>Use the decimal format value from the DECFMT job attribute when the file is opened.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.SFLENDTXT"></a>
<h3>SFLEND text (SFLENDTXT)</h3>
<p>Specifies where the 'More...' and 'Bottom' text is retrieved from when displaying a subfile. The 'More...' and 'Bottom' text is displayed in a subfile when the SFLEND(*MORE) DDS keyword is specified on the subfile control record.
</p>
<dl>
<dt><b>*MSG</b></dt>
<dd>Use the 'More...' and 'Bottom' text retrieved from messages CPX6AB1 and CPX6AB2 which exist in the current active language of the system when the file is opened.
</dd>
<dt><b>*FILE</b></dt>
<dd>Use the 'More...' and 'Bottom' text that is stored in the file during file creation. This text was retrieved from messages CPX6AB1 and CPX6AB2 which exist in the active language of the system when the file was created.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.IGCDTA"></a>
<h3>User specified DBCS data (IGCDTA)</h3>
<p>Specifies, for program-described files, whether the file processes double-byte character set (DBCS) data. Specifies, for externally described files, the DBCS attributes of the file.
</p>
<p>For program-described files:
</p>
<dl>
<dt><b>*NO</b></dt>
<dd>The file does not process double-byte character set (DBCS) data.
</dd>
</dl>
<dl>
<dt><b>*YES</b></dt>
<dd>The file processes double-byte character set (DBCS) data.
</dd>
</dl>
<p>For DDS files:
</p>
<dl>
<dt><b>*NO</b></dt>
<dd>The only DBCS attributes of the file are those defined in the DDS.
</dd>
<dt><b>*YES</b></dt>
<dd>DBCS attributes in addition to those defined in the DDS, include (1) putting the DDS keyword for alternative data type (IGCALTTYP) into effect, and (2) identifying DBCS attributes of fields or messages not identified in the DDS.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.IGCEXNCHR"></a>
<h3>DBCS extension characters (IGCEXNCHR)</h3>
<p>Specifies whether the system processes double-byte character set (DBCS) extension characters.
</p>
<dl>
<dt><b>*YES</b></dt>
<dd>The system processes DBCS extension characters.
</dd>
<dt><b>*NO</b></dt>
<dd>The system does not process DBCS extension characters; it displays them as undefined characters.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.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>
<p>More information on this parameter is in the CL concepts and reference topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter, Appendix A.
</p>
<p>
<b>Note: </b>An immediate allocation of the device by the device resource is required when an acquire operation is performed to the file.
</p>
<p>This parameter overrides the wait time specified in the device file, in the program, or in other called OVRDSPF commands.
</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 allocation of the file resources.
</dd>
<dt><b><i>integer</i></b></dt>
<dd>Specify the number of seconds that the program waits for the allocation of the file resources. Valid values range from 1 through 32767 seconds.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.WAITRCD"></a>
<h3>Maximum record wait time (WAITRCD)</h3>
<p>Specifies the number of seconds the program waits for the completion of a read-from-invited-program-devices operation to a multiple device file in an HLL program. More information on how to determine when a file is considered a multiple device file is in the appropriate HLL reference manual. The program performing the read operation waits for input from all invited devices currently acquired by the file. If a record is not returned from an invited device within the specified amount of time, a notify message is sent to the program. This parameter has no effect on an input operation directed to one device.
</p>
<p>This parameter is also used to specify the number of seconds that a CL program waits to complete a WAIT command. If a record is not returned from any of the devices that should return a record, the CL program is sent an escape message.
</p>
<p>This parameter overrides the wait record value specified in the device file, in the program, or in other called OVRDSPF commands.
</p>
<dl>
<dt><b>*NOMAX</b></dt>
<dd>There is no limit on the amount of time the program waits for completion of a read-from-invited-program-device operation for the file.
</dd>
</dl>
<dl>
<dt><b>*IMMED</b></dt>
<dd>The program does not wait. If a record is not available when the read-from-invited-devices operation is done, a notify message is sent to the program.
</dd>
</dl>
<dl>
<dt><b><i>1-32767</i></b></dt>
<dd>Specify the number of seconds that the program waits for the completion of the read-from-invited-program-device operations.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.LVLCHK"></a>
<h3>Record format level check (LVLCHK)</h3>
<p>Specifies whether the level identifiers of the record formats in this device file are checked when the file is opened by a program. For this check, which is done when the file is opened, the system compares the record format identifiers of each record format used by the program with the corresponding identifiers in the device file. Because the same record format name can exist in more than one file, each record format is given a unique internal system identifier when the format is created.
</p>
<p>Level checking cannot be done unless the program contains the record format identifiers. This command cannot override level checking from *NO to *YES.
</p>
<dl>
<dt><b>*NO</b></dt>
<dd>The level identifiers are not checked when the file is opened.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.SECURE"></a>
<h3>Secure from other overrides (SECURE)</h3>
<p>Specifies whether this file is safe from the effects of previous call level file override commands.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>This file is not protected from other file overrides. Its values can be overridden by the effects of previous call level file override commands.
</dd>
<dt><b>*YES</b></dt>
<dd>This file is protected from the effects of previous call level file override commands.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.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="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.DTAQ"></a>
<h3>Data queue (DTAQ)</h3>
<p>Specifies the data queue that receives an entry from the system when a data-available event is signaled from an invited display device. The data queue need not exist when the display file is created since the name specified on this parameter is not evaluated until the file is used. More information on the data queue function is in the CL information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*NONE</b></dt>
<dd>No data queue is specified.
</dd>
</dl>
<p><b>Qualifier 1: Data queue</b>
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the data queue on which entries are placed.
</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 is used to locate the data queue. If no library is specified as the current library, QGPL is used.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the library where the data queue is located.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.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>
<p>More information on shared database files is in the Database information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
</p>
<p>This parameter overrides the value specified in the device file, in the program, or in other called OVRDSPF commands.
</p>
<dl>
<dt><b>*NO</b></dt>
<dd>The ODP is not shared with other programs in the routing step. A new ODP for the file is created and used every time a program opens the file.
</dd>
</dl>
<dl>
<dt><b>*YES</b></dt>
<dd>The same ODP is shared with each program in the job that also specifies *YES when it opens the file.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="OVRDSPF.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 OVRDSPF 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="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="OVRDSPF.COMMAND.EXAMPLES">Examples</a> </h3>
<p>
<pre>
OVRDSPF FILE(DISPLAY75) WAITFILE(30)
</pre>
</p>
<p>This command overrides the file wait time value specified in the DISPLAY75 device file description, in the program, or in other called OVRDSPF commands. The program in which this command occurs waits up to 30 seconds (if necessary) to allocate the required file resources to the file named DISPLAY75.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="OVRDSPF.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF1892</b></dt>
<dd>Function &amp;1 not allowed.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#OVRDSPF.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>