USE PRINTER / PUNCH command - Revision history

JAL: /* Syntax */ add links

2017-10-17T23:05:54Z

Syntax: add links

← Older revision		Revision as of 23:05, 17 October 2017
Line 34:		Line 34:
	<var class="term">name</var> is the name of an output destination. Under z/OS and z/VM, the name can be 1 to 8 characters.</p>		<var class="term">name</var> is the name of an output destination. Under z/OS and z/VM, the name can be 1 to 8 characters.</p>
	<p>		<p>
	For the <var>PRINTER</var> and <var>PUNCH</var> forms of the <var>USE</var> command, options are defined in ~~the sections on the <var>~~DEFINE PRINTER~~</var>~~ and ~~<var>~~DEFINE PUNCH~~</var> commands~~.</p>		For the <var>PRINTER</var> and <var>PUNCH</var> forms of the <var>USE</var> command, options are those defined in [[DEFINE PRINTER command]] and [[DEFINE PUNCH command]].</p>

	===Syntax notes===		===Syntax notes===

JAL: add italics

2017-10-17T21:18:55Z

add italics

← Older revision		Revision as of 21:18, 17 October 2017
Line 142:		Line 142:
	<p>		<p>
	The <var>USE</var> command supports directed output under z/VSE/POWER. The syntax for this form of the <var>USE</var> command is as follows: </p>		The <var>USE</var> command supports directed output under z/VSE/POWER. The syntax for this form of the <var>USE</var> command is as follows: </p>
	<p class="code">USE [{PRINTER \| PUNCH}] [~~NAME~~] WITH ROUTER=POWER		<p class="code">USE [{PRINTER \| PUNCH}] [<var class="term">name</var>] WITH ROUTER=POWER
	[,option...]		[,<var class="term">option</var>...]
	</p>		</p>
	<p>		<p>
	Where </p>		Where: </p>
	<p>		<p>
	<var class="term">name</var> is the name of an output destination.</p>		<var class="term">name</var> is the name of an output destination.</p>

JAL: misc cleanup

2017-10-10T20:08:37Z

misc cleanup

Show changes

ELowell at 16:30, 22 March 2017

2017-03-22T16:30:24Z

← Older revision		Revision as of 16:30, 22 March 2017
Line 198:		Line 198:
	====Dynamically allocating output====		====Dynamically allocating output====
	<p>The USE command (and the DEFINE PRINTER command) support the dynamic allocation parameter, OUTPUT, to allow you to use special formatting options that are not supported directly on these <var class="product">Model 204</var> commands themselves. See the example and discussion in "Dynamically allocating output" in [[DEFINE PRINTER command]].</p>		<p>The USE command (and the DEFINE PRINTER command) support the dynamic allocation parameter, OUTPUT, to allow you to use special formatting options that are not supported directly on these <var class="product">Model 204</var> commands themselves. See the example and discussion in "Dynamically allocating output" in [[DEFINE PRINTER command]].</p>
	[[Category: ~~General user~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell at 20:53, 20 September 2016

2016-09-20T20:53:04Z

← Older revision		Revision as of 20:53, 20 September 2016
Line 8:		Line 8:
	<table>		<table>

	<tr> <th>		<tr class="head">
			<th>
	<p>Operating system </p>		<p>Operating system </p>
	</th> <th>		</th> <th>
Line 14:		Line 15:
	</th> </tr>		</th> </tr>

	<tr> <th>z/OS or z/VM </th> <td>Dynamically allocated printer or punch device</td> </tr>		<tr>
			<td>z/OS or z/VM </td> <td>Dynamically allocated printer or punch device</td> </tr>

	<tr~~> <th~~>		<tr>
	<p>z/OS or z/VSE with the CICS terminal interface </p>		<td>z/OS or z/VSE with the CICS terminal interface</td> <td>CICS printer</td> </tr>
	~~</th~~> <td>
	<p>CICS printer~~</p>~~
	</td> </tr>

	<tr~~> <th~~>		<tr class="head">
	<p>z/VSE/POWER</p>		<td>z/VSE/POWER</td> <td>Printer or punch device</td> </tr>
	~~</th~~> <td>
	<p>Printer or punch device~~</p>~~
	</td> </tr>

	</table>		</table>
	</dl>		</dl>
Line 79:		Line 74:
	<table>		<table>

	<tr> <th>		<tr class="head"> <th>Mode of operation</th> <th>Action</th> </tr>
	<p>Mode of operation ~~</p>~~
	</th> <th>
	<p> Action~~</p>~~
	</th> </tr>

	<tr> <~~th><var>~~		<tr> <td>WAITTIME greater than 0</td> <td>M204PSFS starts the printer transaction and waits a maximum of WAITTIME to determine if the printer is acquired for the printer task.
	<p>WAITTIME greater than 0 </p>
	~~</var></th~~> <td>
	<p>M204PSFS starts the printer transaction and waits a maximum of WAITTIME to determine if the printer is acquired for the printer task. ~~</p>~~
	<p>If the printer is acquired, M204PSFS writes all print data to a Temporary Storage queue. When the last data record is received, it "wakes" the printer task to print, and releases the terminal to the user. However, specifying &PRTWAIT=YES in CICFG forces the terminal user to wait for the physical end of printing before releasing the terminal. </p>		<p>If the printer is acquired, M204PSFS writes all print data to a Temporary Storage queue. When the last data record is received, it "wakes" the printer task to print, and releases the terminal to the user. However, specifying &PRTWAIT=YES in CICFG forces the terminal user to wait for the physical end of printing before releasing the terminal. </p>
	<p>If the printer is not acquired, a warning message is displayed and no printing is attempted.</p>		<p>If the printer is not acquired, a warning message is displayed and no printing is attempted.</p>
	</td> </tr>		</td> </tr>

	<tr> <~~th><var>~~		<tr> <td>WAITTIME less than or equal to 0</td> <td>Print data is placed in Temporary Storage and the printer task is queued, whether or not the printer is currently available.
	<p>WAITTIME less than or equal to 0 </p>
	~~</var></th~~> <td>
	<p>Print data is placed in Temporary Storage and the printer task is queued, whether or not the printer is currently available. ~~</p>~~
	<p>If the Temporary Storage queues are written to AUXILIARY storage, the print queues are recoverable, although not through a cold start. </p>		<p>If the Temporary Storage queues are written to AUXILIARY storage, the print queues are recoverable, although not through a cold start. </p>
	</td> </tr>		</td> </tr>

	</table>		</table>

	<p>For a USE PRINTER transaction in OBCIPR, a message is written to the CICS job log when the printing is completed. The message contains the printer's terminal ID and the Temporary Storage queue name. A message is written to the job log for any abend of the printer transaction.</p>		<p>For a USE PRINTER transaction in OBCIPR, a message is written to the CICS job log when the printing is completed. The message contains the printer's terminal ID and the Temporary Storage queue name. A message is written to the job log for any abend of the printer transaction.</p>
	<p>The IBM-supplied sample DCT is modified as follows: </p>		<p>The IBM-supplied sample DCT is modified as follows: </p>

ELowell: /* Referencing a previous definition */

2013-06-28T15:37:12Z

Referencing a previous definition

← Older revision		Revision as of 15:37, 28 June 2013
Line 132:		Line 132:
	<p>name is the name of an output destination.</p>		<p>name is the name of an output destination.</p>
	====Referencing a previous definition====		====Referencing a previous definition====
	<p>In the USE command the output destination and the characteristics of the output sent to it can be described either by referencing a previously defined destination or by ~~specifying the destination in the USE command itself. See the~~ [[USE_PRINTER_/_PUNCH_command#Defining_the_destination_in_the_USE_command\|~~USE PRINTER/PUNCH command, "Defining~~ the destination in the USE command"]] ~~section for details~~.</p>		<p>In the USE command the output destination and the characteristics of the output sent to it can be described either by referencing a previously defined destination or by [[USE_PRINTER_/_PUNCH_command#Defining_the_destination_in_the_USE_command\|specifying the destination in the USE command itself]].</p>
	<p>The system administrator can define an output destination and describe the characteristics (for example, output identifiers, number of copies, form name) of the output to be sent to it in a DEFINE PRINTER or DEFINE PUNCH command. (See [[DEFINE PRINTER command\|DEFINE PRINTER command]] and [[DEFINE PUNCH command\|DEFINE PUNCH command]] for a discussion of these two commands.) </p>		<p>The system administrator can define an output destination and describe the characteristics (for example, output identifiers, number of copies, form name) of the output to be sent to it in a DEFINE PRINTER or DEFINE PUNCH command. (See [[DEFINE PRINTER command\|DEFINE PRINTER command]] and [[DEFINE PUNCH command\|DEFINE PUNCH command]] for a discussion of these two commands.) </p>
	<p>By specifying the name of a previously defined destination in the USE command, you cause output to be sent to this destination. The output has the characteristics defined by the system manager.</p>		<p>By specifying the name of a previously defined destination in the USE command, you cause output to be sent to this destination. The output has the characteristics defined by the system manager.</p>

ELowell: /* Referencing a previous definition */

2013-06-28T15:35:42Z

Referencing a previous definition

← Older revision		Revision as of 15:35, 28 June 2013
Line 132:		Line 132:
	<p>name is the name of an output destination.</p>		<p>name is the name of an output destination.</p>
	====Referencing a previous definition====		====Referencing a previous definition====
	<p>In the USE command the output destination and the characteristics of the output sent to it can be described either by referencing a previously defined destination or by specifying the destination in the USE command itself. See "Defining the destination in the USE command" ~~later in this topic~~.</p>		<p>In the USE command the output destination and the characteristics of the output sent to it can be described either by referencing a previously defined destination or by specifying the destination in the USE command itself. See the [[USE_PRINTER_/_PUNCH_command#Defining_the_destination_in_the_USE_command\|USE PRINTER/PUNCH command, "Defining the destination in the USE command"]] section for details.</p>
	<p>The system administrator can define an output destination and describe the characteristics (for example, output identifiers, number of copies, form name) of the output to be sent to it in a DEFINE PRINTER or DEFINE PUNCH command. (See [[DEFINE PRINTER command\|DEFINE PRINTER command]] and [[DEFINE PUNCH command\|DEFINE PUNCH command]] for a discussion of these two commands.) </p>		<p>The system administrator can define an output destination and describe the characteristics (for example, output identifiers, number of copies, form name) of the output to be sent to it in a DEFINE PRINTER or DEFINE PUNCH command. (See [[DEFINE PRINTER command\|DEFINE PRINTER command]] and [[DEFINE PUNCH command\|DEFINE PUNCH command]] for a discussion of these two commands.) </p>
	<p>By specifying the name of a previously defined destination in the USE command, you cause output to be sent to this destination. The output has the characteristics defined by the system manager.</p>		<p>By specifying the name of a previously defined destination in the USE command, you cause output to be sent to this destination. The output has the characteristics defined by the system manager.</p>

ELowell: /* Referencing a previous definition */

2013-06-28T15:31:38Z

Referencing a previous definition

← Older revision		Revision as of 15:31, 28 June 2013
Line 133:		Line 133:
	====Referencing a previous definition====		====Referencing a previous definition====
	<p>In the USE command the output destination and the characteristics of the output sent to it can be described either by referencing a previously defined destination or by specifying the destination in the USE command itself. See "Defining the destination in the USE command" later in this topic.</p>		<p>In the USE command the output destination and the characteristics of the output sent to it can be described either by referencing a previously defined destination or by specifying the destination in the USE command itself. See "Defining the destination in the USE command" later in this topic.</p>
	<p>The system administrator can define an output destination and describe the characteristics (for example, output identifiers, number of copies, form name) of the output to be sent to it in a DEFINE PRINTER or DEFINE PUNCH command. (See [[DEFINE PRINTER command\|"DEFINE PRINTER~~: Defining the output destination"~~]] and [[DEFINE PUNCH command\|"DEFINE PUNCH~~: Defining the output destination"~~]] for a discussion of these two commands.) </p>		<p>The system administrator can define an output destination and describe the characteristics (for example, output identifiers, number of copies, form name) of the output to be sent to it in a DEFINE PRINTER or DEFINE PUNCH command. (See [[DEFINE PRINTER command\|DEFINE PRINTER command]] and [[DEFINE PUNCH command\|DEFINE PUNCH command]] for a discussion of these two commands.) </p>
	<p>By specifying the name of a previously defined destination in the USE command, you cause output to be sent to this destination. The output has the characteristics defined by the system manager.</p>		<p>By specifying the name of a previously defined destination in the USE command, you cause output to be sent to this destination. The output has the characteristics defined by the system manager.</p>
	<p>For example, if you specify: </p>		<p>For example, if you specify: </p>
Line 198:		Line 198:
	</p>		</p>
	<p>In this example, reports A and B are sent to JIM's reader.</p>		<p>In this example, reports A and B are sent to JIM's reader.</p>

	====USE output name====		====USE output name====
	<p>If the output name specified in the USE command does not match the name specified in the DEFINE PRINTER or DEFINE PUNCH definition, <var class="product">Model 204</var> assumes that the name represents a sequential output data set of the kind described in [[USE_command:_To_a_sequential_data_set\|"USE command: To a sequential data set"]]. </p>		<p>If the output name specified in the USE command does not match the name specified in the DEFINE PRINTER or DEFINE PUNCH definition, <var class="product">Model 204</var> assumes that the name represents a sequential output data set of the kind described in [[USE_command:_To_a_sequential_data_set\|"USE command: To a sequential data set"]]. </p>

ELowell: /* Dynamically allocating output */

2013-06-28T15:30:10Z

Dynamically allocating output

← Older revision		Revision as of 15:30, 28 June 2013
Line 211:		Line 211:
	<p><var class="product">Model 204</var> sends the output from this request to the virtual machine with the ID of JIM.</p>		<p><var class="product">Model 204</var> sends the output from this request to the virtual machine with the ID of JIM.</p>
	====Dynamically allocating output====		====Dynamically allocating output====
	<p>The USE command (and the DEFINE PRINTER command) support the dynamic allocation parameter, OUTPUT, to allow you to use special formatting options that are not supported directly on these <var class="product">Model 204</var> commands themselves. See the example and discussion in "Dynamically allocating output" in [[DEFINE PRINTER command~~\|DEFINE PRINTER: Defining the output destination~~]].</p>		<p>The USE command (and the DEFINE PRINTER command) support the dynamic allocation parameter, OUTPUT, to allow you to use special formatting options that are not supported directly on these <var class="product">Model 204</var> commands themselves. See the example and discussion in "Dynamically allocating output" in [[DEFINE PRINTER command]].</p>
	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* USE output name */

2013-06-28T15:29:14Z

USE output name

← Older revision		Revision as of 15:29, 28 June 2013
Line 199:		Line 199:
	<p>In this example, reports A and B are sent to JIM's reader.</p>		<p>In this example, reports A and B are sent to JIM's reader.</p>
	====USE output name====		====USE output name====
	<p>If the output name specified in the USE command does not match the name specified in the DEFINE PRINTER or DEFINE PUNCH definition, <var class="product">Model 204</var> assumes that the name represents a sequential output data set of the kind described in [[USE_command:_To_a_sequential_data_set\|"USE: To a sequential data set"]]. </p>		<p>If the output name specified in the USE command does not match the name specified in the DEFINE PRINTER or DEFINE PUNCH definition, <var class="product">Model 204</var> assumes that the name represents a sequential output data set of the kind described in [[USE_command:_To_a_sequential_data_set\|"USE command: To a sequential data set"]]. </p>
	<p>The specified output name must be of the form OUT<var class="term">xxxxx</var>. If a data set definition statement for the OUT<var class="term">xxxxx</var> name cannot be found in the Job Control Language or EXEC procedure for the run and OUT<var class="term">xxxxx</var> is not the name of a DEFINE DATASET definition, <var class="product">Model 204</var> displays a message that the data set does not exist.</p>		<p>The specified output name must be of the form OUT<var class="term">xxxxx</var>. If a data set definition statement for the OUT<var class="term">xxxxx</var> name cannot be found in the Job Control Language or EXEC procedure for the run and OUT<var class="term">xxxxx</var> is not the name of a DEFINE DATASET definition, <var class="product">Model 204</var> displays a message that the data set does not exist.</p>
	<p>If <var class="product">Model 204</var> is running with an external security interface, a USE command of the form USE OUT<var class="term">xxxxx</var> results in a check to determine whether you are authorized for the request. You must have the appropriate WRITE level privileges for the output data set. If you do not have this authority, the USE command fails, the attempt is logged as a security violation, and a <var class="product">Model 204</var> error message is displayed.</p>		<p>If <var class="product">Model 204</var> is running with an external security interface, a USE command of the form USE OUT<var class="term">xxxxx</var> results in a check to determine whether you are authorized for the request. You must have the appropriate WRITE level privileges for the output data set. If you do not have this authority, the USE command fails, the attempt is logged as a security violation, and a <var class="product">Model 204</var> error message is displayed.</p>