USE command: Directing output: Difference between revisions
m (Automatically generated page update) |
m (add "See also" section) |
||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
===USE command capabilities=== | |||
<p>The capabilities available through USE depend upon the operating system under which <var class="product">Model 204</var> is running. The capabilities of the USE command are: </p> | <p>The capabilities available through USE depend upon the operating system under which <var class="product">Model 204</var> is running. The capabilities of the USE command are: </p> | ||
<ul> | <ul> | ||
Line 26: | Line 26: | ||
</li> | </li> | ||
</ul> | </ul> | ||
===Forms of the USE command=== | |||
<p>Information on each form of the USE command is provided in the sections that follow.</p> | <p>Information on each form of the USE command is provided in the sections that follow.</p> | ||
<p>The way in which <var class="product">Model 204</var> handles the name specified in a USE command is determined in a hierarchical manner.</p> | <p>The way in which <var class="product">Model 204</var> handles the name specified in a USE command is determined in a hierarchical manner.</p> | ||
<p>If the command takes the form: </p> | <p>If the command takes the form: </p> | ||
<p class="code"> | <p class="code"><b>U</b>SE <var class="term">name</var> | ||
</p> | </p> | ||
<p>where name does not begin with the prefix OUT, <var class="product">Model 204</var> searches in the following order: </p> | <p>where <var class="term">name</var> does not begin with the prefix OUT, <var class="product">Model 204</var> searches in the following order: </p> | ||
<ol> | <ol> | ||
<li> | <li> | ||
Line 43: | Line 44: | ||
</ol> | </ol> | ||
<p>If the command takes the form:</p> | <p>If the command takes the form:</p> | ||
<p class="code"> | <p class="code"><b>U</b>SE OUT<var class="term">xxxxx</var> | ||
</p> | </p> | ||
<p>where | <p>where OUT<var class="term">xxxxx</var> is a data set or device name beginning with the prefix OUT, then <var class="product">Model 204</var> searches in the following order: </p> | ||
<ol> | <ol> | ||
<li> | <li> | ||
Line 64: | Line 65: | ||
</ol> | </ol> | ||
<p>You can override forms of the USE command outlined above through a USE PRINTER or USE PUNCH command.</p> | <p>You can override forms of the USE command outlined above through a USE PRINTER or USE PUNCH command.</p> | ||
<p>The format of the USE command's output is affected by the settings of | ===USE command output=== | ||
<p>The format of the USE command's output is affected by the settings of these user parameters:</p> | |||
<table> | <table> | ||
<tr class="head"> <th> | |||
<tr> <th> | |||
<p>Parameter</p> | <p>Parameter</p> | ||
</th> <th> | </th> <th> | ||
Line 75: | Line 75: | ||
</th> </tr> | </th> </tr> | ||
<tr> <th><var> | <tr> <th><var>[[UDDCCC parameter|UDDCCC]]</var> | ||
</th> <td>Continuation character column on the alternate output | |||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var>[[UDDLPP parameter|UDDLPP]]</var></th> | ||
<td>Number of lines per page on the alternate output | |||
</var></th> <td | |||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var>[[UDDRFM parameter|UDDRFM]]</var></th> | ||
<td>Record format for the alternate output | |||
</var></th> <td | |||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var>[[MUDD parameter|MUDD]]</var></th> | ||
<td>Maximum number of lines on the alternate output | |||
</var></th> <td | </td> </tr> | ||
</td> </tr> | |||
</table> | </table> | ||
< | <p> | ||
When a USE command is executed, <var class="product">Model 204</var> opens the specified sequential device. It remains open until a command, such as BEGIN, MORE, or DISPLAY, causes data to be written on it. If other commands are issued before the command that produces output, the data set remains open until an output command is issued and the output is completed. </p> | |||
<p>Commands with the USE=RESPECT option close the USE output area and generate the following message whether or not output is generated: </p> | <p>Commands with the USE=RESPECT option close the USE output area and generate the following message whether or not output is generated: </p> | ||
<p class="code">M204.1327: NUMBER OF U DD LINES | <p class="code">M204.1327: NUMBER OF U DD LINES OUTPUT=<i>n</i> | ||
</p> | </p> | ||
<p>A new USE command must be issued for each new command that produces output. If USE has been issued and an output command is not received before another USE is issued, <var class="product">Model 204</var> automatically closes the first data set before opening the second.</p> | <p> | ||
A new USE command must be issued for each new command that produces output. If USE has been issued and an output command is not received before another USE is issued, <var class="product">Model 204</var> automatically closes the first data set before opening the second.</p> | |||
<p>If a User Language request ends with an END USE statement, the USE data set is left open after the request has been completed, allowing output from another request to be added to the original output. The output page number is not reset. If the USE keyword is not specified in the END statement, the USE command applies only to the first request or DISPLAY command following the USE command. </p> | <p>If a User Language request ends with an END USE statement, the USE data set is left open after the request has been completed, allowing output from another request to be added to the original output. The output page number is not reset. If the USE keyword is not specified in the END statement, the USE command applies only to the first request or DISPLAY command following the USE command. </p> | ||
<p>The USE command must be repeated before any other request whose output is to appear in the data set.</p> | <p>The USE command must be repeated before any other request whose output is to appear in the data set.</p> | ||
<p>If an I/O error is encountered in the USE data set, the request being run is canceled.</p> | <p>If an I/O error is encountered in the USE data set, the request being run is canceled.</p> | ||
<p>If two users attempt to write to the same data set, the second user sees messages stating that the data set is in use and that the output is set for routing to the normal device. The second user's output is not routed to the data set.</p> | <p>If two users attempt to write to the same data set, the second user sees messages stating that the data set is in use and that the output is set for routing to the normal device. The second user's output is not routed to the data set.</p> | ||
==See also== | |||
<ul> | |||
<li>[[USE command: To a sequential data set]] </li> | |||
</ul> | |||
[[Category:Commands]] | [[Category:Commands]] |
Latest revision as of 21:15, 16 January 2018
USE command capabilities
The capabilities available through USE depend upon the operating system under which Model 204 is running. The capabilities of the USE command are:
-
z/OS users can dynamically create printer and punch output and can submit jobs.
-
z/VM users running under z/VM or under a guest operating system can dynamically create both print and punch files using the z/VM spooling system.
-
z/VSE users can dynamically create printer and punch output and can submit jobs using POWER.
-
CICS users can print output on CICS printers.
-
All users can write output to sequential data sets.
-
USE support is at the command level. See RESET COMMAND: Control USE data set support for details.
Forms of the USE command
Information on each form of the USE command is provided in the sections that follow.
The way in which Model 204 handles the name specified in a USE command is determined in a hierarchical manner.
If the command takes the form:
USE name
where name does not begin with the prefix OUT, Model 204 searches in the following order:
-
Device specified by a DEFINE PRINTER command
-
Device specified by a DEFINE PUNCH command
If the command takes the form:
USE OUTxxxxx
where OUTxxxxx is a data set or device name beginning with the prefix OUT, then Model 204 searches in the following order:
-
Data set specified by a DEFINE DATASET command
-
Existing data set
-
Device specified by a DEFINE PRINTER command
-
Device specified by a DEFINE PUNCH command
You can override forms of the USE command outlined above through a USE PRINTER or USE PUNCH command.
USE command output
The format of the USE command's output is affected by the settings of these user parameters:
Parameter |
Meaning |
---|---|
UDDCCC | Continuation character column on the alternate output |
UDDLPP | Number of lines per page on the alternate output |
UDDRFM | Record format for the alternate output |
MUDD | Maximum number of lines on the alternate output |
When a USE command is executed, Model 204 opens the specified sequential device. It remains open until a command, such as BEGIN, MORE, or DISPLAY, causes data to be written on it. If other commands are issued before the command that produces output, the data set remains open until an output command is issued and the output is completed.
Commands with the USE=RESPECT option close the USE output area and generate the following message whether or not output is generated:
M204.1327: NUMBER OF U DD LINES OUTPUT=n
A new USE command must be issued for each new command that produces output. If USE has been issued and an output command is not received before another USE is issued, Model 204 automatically closes the first data set before opening the second.
If a User Language request ends with an END USE statement, the USE data set is left open after the request has been completed, allowing output from another request to be added to the original output. The output page number is not reset. If the USE keyword is not specified in the END statement, the USE command applies only to the first request or DISPLAY command following the USE command.
The USE command must be repeated before any other request whose output is to appear in the data set.
If an I/O error is encountered in the USE data set, the request being run is canceled.
If two users attempt to write to the same data set, the second user sees messages stating that the data set is in use and that the output is set for routing to the normal device. The second user's output is not routed to the data set.