VIEW COMMAND command - Revision history

ELowell at 16:29, 22 March 2017

2017-03-22T16:29:13Z

← Older revision		Revision as of 16:29, 22 March 2017
Line 39:		Line 39:
	</ol>		</ol>

	[[Category: ~~General user~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL: misc cleanup

2016-02-02T23:37:55Z

misc cleanup

← Older revision		Revision as of 23:37, 2 February 2016
Line 6:		Line 6:
	<dd>Displays the USE data set support and the command privileges for commands.		<dd>Displays the USE data set support and the command privileges for commands.
	</dl>		</dl>

	==Syntax==		==Syntax==
	<p class="syntax"><b>V</b>IEW COMMAND <i>command</i>		<p class="syntax"><b>V</b>IEW COMMAND <span class="term">command</span>
	</p>		</p>

	<b>~~Where:~~</b>		Where <var class="term">command</var> is any Model 204 command.
	~~command~~ is any ~~User Language~~ command
	==Usage==		==Usage==

	====Sending VIEW output to the USE data set====		====Sending VIEW output to the USE data set====
	<p>~~If you want to~~ see how the <var class="product">Model 204</var> ~~Command~~ table settings are set to know whether the output from a command is sent to the screen or the USE data set, you can issue a VIEW COMMAND command. If there is an open USE data set, ~~the~~ VIEW COMMAND ~~command~~ output is directed to it. For example:</p>		<p>
			To see how the <var class="product">Model 204</var> command table settings are set to know whether the output from a command is sent to the screen or the USE data set, you can issue a <var>VIEW COMMAND</var> command. If there is an open <var>USE</var> data set, <var>VIEW COMMAND</var> output is directed to it. For example:</p>
	<p class="code">VIEW COMMAND SETGRC		<p class="code">VIEW COMMAND SETGRC
	</p>		</p>
	<p>This command displays results similar to the following: </p>		<p>
	<p class="~~code~~">SETGRC COMMAND USE=IGNORE PRIVILEGE=(LOGONREQ)		This command displays results similar to the following: </p>
			<p class="output">SETGRC COMMAND USE=IGNORE PRIVILEGE=(LOGONREQ)
	</p>		</p>
	<p>This might cause a problem for any ~~User Language~~ procedure that has one or more commands between a USE command and the commands that ~~directs its~~ output to the USE data set. To solve this problem: </p>		<p>
			This might cause a problem for any SOUL procedure that has one or more commands between a <var>USE</var> command and the commands that direct output to the <var>USE</var> data set. To solve this problem: </p>
	<ol>		<ol>
	<li>		<li>
	<p>Issue a VIEW COMMAND ~~command~~ to view the flags in the command table that indicate which commands support USE output and to what extent.</p>		<p>
			Issue <var>VIEW COMMAND</var> to view the flags in the command table that indicate which commands support <var>USE</var> output and to what extent.</p>
	</li>		</li>

	<li>		<li>
	<p>If your are the system manager you can issue a RESET COMMAND ~~command~~ to update the flags.</p>		<p>If your are the system manager, you can issue <var>RESET COMMAND</var> to update the flags.</p>
			<p>
			Refer to [[RESET COMMAND command]] for a discussion of <var>RESET COMMAND</var> and how to direct the output.</p>
	</li>		</li>
	</ol>		</ol>
	~~<p>Please refer to [[RESET COMMAND command\|"RESET COMMAND: Control USE data set support"]] for a discussion of the RESET COMMAND command and how to direct the output.</p>~~
	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:05:37Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>Any user
<dt>Function
<dd>Displays the USE data set support and the command privileges for commands.
</dl>
==Syntax==
VIEW COMMAND command


Where:
command is any User Language command
==Usage==
====Sending VIEW output to the USE data set====
If you want to see how the <var class="product">Model 204</var> Command table settings are set to know whether the output from a command is sent to the screen or the USE data set, you can issue a VIEW COMMAND command. If there is an open USE data set, the VIEW COMMAND command output is directed to it. For example:
VIEW COMMAND SETGRC

This command displays results similar to the following: 
SETGRC COMMAND USE=IGNORE PRIVILEGE=(LOGONREQ)

This might cause a problem for any User Language procedure that has one or more commands between a USE command and the commands that directs its output to the USE data set. To solve this problem: 
<ol>
<li>
Issue a VIEW COMMAND command to view the flags in the command table that indicate which commands support USE output and to what extent.
</li>

<li>
If your are the system manager you can issue a RESET COMMAND command to update the flags.
</li>
</ol>
Please refer to [[RESET COMMAND command|"RESET COMMAND: Control USE data set support"]] for a discussion of the RESET COMMAND command and how to direct the output.
[[Category: General user commands]]
[[Category:Commands]]