VIEW COMMAND command: Difference between revisions
m (Automatically generated page update) |
m (misc cleanup) |
||
| 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 < | <p class="syntax"><b>V</b>IEW COMMAND <span class="term">command</span> | ||
</p> | </p> | ||
< | Where <var class="term">command</var> is any Model 204 command. | ||
==Usage== | ==Usage== | ||
====Sending VIEW output to the USE data set==== | ====Sending VIEW output to the USE data set==== | ||
<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=" | 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 | <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 | <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 | <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> | |||
[[Category: General user commands]] | [[Category: General user commands]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
Revision as of 23:37, 2 February 2016
Summary
- Privileges
- Any user
- Function
- Displays the USE data set support and the command privileges for commands.
Syntax
VIEW COMMAND command
Where command is any Model 204 command.
Usage
Sending VIEW output to the USE data set
To see how the Model 204 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, VIEW 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 SOUL procedure that has one or more commands between a USE command and the commands that direct output to the USE data set. To solve this problem:
-
Issue VIEW COMMAND to view the flags in the command table that indicate which commands support USE output and to what extent.
-
If your are the system manager, you can issue RESET COMMAND to update the flags.
Refer to RESET COMMAND command for a discussion of RESET COMMAND and how to direct the output.