RESET COMMAND command: Difference between revisions
m (misc formatting) |
|||
(2 intermediate revisions by 2 users not shown) | |||
Line 4: | Line 4: | ||
<dd>System manager | <dd>System manager | ||
<dt>Function | <dt>Function | ||
<dd>To control the USE data set support and the command privileges for each command or to reset the USE output flags and the command privilege flags in the command table entry. | <dd>To control the <var>USE</var> data set support and the command privileges for each command, or to reset the <var>USE</var> output flags and the command privilege flags in the command table entry. | ||
</dl> | </dl> | ||
==Syntax== | ==Syntax== | ||
<p class="syntax"><b>R</b>ESET COMMAND <i>command</i> | <p class="syntax"><b>R</b>ESET COMMAND <i>command</i> | ||
{USE=<u>RESPECT</u> | IGNORE | NOCLOSE | NOOPEN | NEVER} | {USE=<u>RESPECT</u> | IGNORE | NOCLOSE | NOOPEN | NEVER} | ||
{PRIVILEGE=FILEMGR | SYSADM | LOGONREQ | SYSMGR | {PRIVILEGE=FILEMGR | SYSADM | LOGONREQ | SYSMGR | NOPROC | NONE} | ||
</p> | </p> | ||
Where: | |||
<ul> | <ul> | ||
<li> | <li><var class="term">command</var> is any Model 204 command except: <var>BEGIN</var>, <var>MORE</var>, <var>EOD</var>, or <var>EOJ</var>. | ||
< | |||
</li> | </li> | ||
<li | <li><var>USE</var> output support options shown in the table below: | ||
<table> | <table> | ||
<caption> USE data set options for the RESET command</caption> | <caption> USE data set options for the RESET command</caption> | ||
<tr class="head"> | |||
<tr> <th | <th>Option</th> | ||
<th>Description</th> </tr> | |||
< | |||
</th> </tr> | |||
<tr> <th>< | <tr> <th nowrap><p><var>RESPECT</var></p></th> | ||
< | <td> | ||
</ | <p>Open <var>USE</var> output before the command is executed. If the command has produced any output, close the <var>USE</var> output after the command has executed. </p> | ||
<p>Open USE output before the command is executed. If the command has produced any output, close the USE output after the command has executed. </p> | <p><var>RESPECT</var> is the default option. </p></td> </tr> | ||
</td> </tr> | |||
<tr> <th><var> | <tr> <th><var><p>IGNORE</p></var></th> | ||
<p>IGNORE</p> | <td> | ||
</var></th> <td> | |||
<p>Do not open the USE output before the command is executed. Do not close the USE output after the command is executed. The output from the command does not go to the USE output unless the command is preceded by a USE command and then another command that has USE=NOCLOSE specified for it.</p> | <p>Do not open the USE output before the command is executed. Do not close the USE output after the command is executed. The output from the command does not go to the USE output unless the command is preceded by a USE command and then another command that has USE=NOCLOSE specified for it.</p> | ||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>NOCLOSE</p></var></th> | ||
<p>NOCLOSE</p> | <td> | ||
</var></th> <td> | |||
<p>Do not close the USE output after the command is executed. Multiple commands with USE=NOCLOSE can be used (with no other commands intervening) and the output from each subsequent command is appended and sent to the same USE data set.</p> | <p>Do not close the USE output after the command is executed. Multiple commands with USE=NOCLOSE can be used (with no other commands intervening) and the output from each subsequent command is appended and sent to the same USE data set.</p> | ||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>NOOPEN</p></var></th> | ||
<p>NOOPEN</p> | <td> | ||
</var></th> <td> | |||
<p>Do not open the USE output before the command is executed. If the command has produced any output, close the USE output after the command has executed.</p> | <p>Do not open the USE output before the command is executed. If the command has produced any output, close the USE output after the command has executed.</p> | ||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>NEVER</p></var></th> | ||
<p>NEVER</p> | <td> | ||
</var></th> <td> | |||
<p>Close the USE output before the command is executed. The output from the command goes to the usual output device.</p> | <p>Close the USE output before the command is executed. The output from the command goes to the usual output device.</p> | ||
</td> </tr> | </td> </tr> | ||
</table> | </table> | ||
</li> | </li> | ||
<li> | <li> | ||
<p>The following table lists the <var>PRIVILEGE</var> options for | <p>The following table lists the <var>PRIVILEGE</var> options for <var>RESET COMMAND</var>:</p> | ||
<table> | <table> | ||
<caption> PRIVILEGE options</caption> | <caption> PRIVILEGE options</caption> | ||
<tr> <th> | <tr class="head"> <th><p>Option</p></th> | ||
<p>Option</p> | <th><p>Description</p> | ||
</th> <th> | |||
<p>Description</p> | |||
</th> </tr> | </th> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>FILEMGR</p></var></th> | ||
<p>FILEMGR</p> | <td> | ||
</var></th> <td> | |||
<p>FILE MANAGER privilege for the current file or group is required to execute the command (file privileges from CCASTAT or APSY File/Group definition).</p> | <p>FILE MANAGER privilege for the current file or group is required to execute the command (file privileges from CCASTAT or APSY File/Group definition).</p> | ||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>SYSADM</p></var></th> | ||
<p>SYSADM</p> | <td> | ||
</var></th> <td> | |||
<p>SYSTEM ADMINISTRATOR privilege is required to execute the command (user privileges from CCASTAT or external security manager).</p> | <p>SYSTEM ADMINISTRATOR privilege is required to execute the command (user privileges from CCASTAT or external security manager).</p> | ||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>LOGONREQ</p></var></th> | ||
<p>LOGONREQ</p> | <td> | ||
</var></th> <td> | |||
<p>LOGON is required to execute the command (if SYSOPT=x'10').</p> | <p>LOGON is required to execute the command (if SYSOPT=x'10').</p> | ||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>SYSMGR</p></var></th> | ||
<p>SYSMGR</p> | <td> | ||
</var></th> <td> | <p>SYSTEM MANAGER privilege is required to execute the command (user privileges from CCASTAT or external security manager). This privilege can only be added to a command; it cannot be removed.</p> | ||
<p>SYSTEM MANAGER privilege is required to execute the command (user privileges from CCASTAT or external security manager).</p> | |||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>NOPROC</p></var></th> | ||
<p>NOPROC</p> | <td> | ||
</var></th> <td> | <p>The command is not permitted from a SOUL procedure.</p> | ||
<p>The command is not permitted from a | |||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>NONE</p></var></th> | ||
<p>NONE</p> | <td> | ||
</var></th> <td> | |||
<p>The command has no privilege requirements.</p> | <p>The command has no privilege requirements.</p> | ||
</td> </tr> | </td> </tr> | ||
</table></li> | |||
</table> | |||
< | <li> | ||
The next table lists the view-only <var>PRIVILEGE</var> options: | |||
<table> | <table> | ||
<caption>View-only PRIVILEGE options</caption> | <caption>View-only PRIVILEGE options</caption> | ||
<tr class="head"> <th><p>Option</p></th> | |||
<tr> <th> | <th><p>Default file...</p></th> </tr> | ||
<p>Option</p> | |||
</th> <th> | |||
<p>Default file...</p> | |||
</th> </tr> | |||
<tr> <th><var> | <tr> <th><var><p>DEFAULTFILE</p></var></th> | ||
<p>DEFAULTFILE</p> | <td><p>Or Group is required.</p> | ||
</var></th> <td> | |||
<p>Or Group is required.</p> | |||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>UPDATEFILE</p></var></th> | ||
<p>UPDATEFILE</p> | <td><p>Must have "Update" privilege.</p> | ||
</var></th> <td> | |||
<p>Must have "Update" privilege.</p> | |||
</td> </tr> | </td> </tr> | ||
<tr> <th><var> | <tr> <th><var><p>SINGLEFILE</p></var></th> | ||
<p>SINGLEFILE</p> | <td><p>Must be a "Single File", not a Group.</p> | ||
</var></th> <td> | |||
<p>Must be a "Single File", not a Group.</p> | |||
</td> </tr> | </td> </tr> | ||
</table> | </table> | ||
<p>You can specify a list of PRIVILEGE options by enclosing the list in parentheses and separating the options by commas.</p> | <p> | ||
</li> | You can specify a list of <var>PRIVILEGE</var> options by enclosing the list in parentheses and separating the options by commas.</p></li> | ||
</ul> | |||
==Usage== | ==Usage== | ||
< | <ul> | ||
< | <li>The <var>RESET COMMAND</var> command is not allowed for <var>BEGIN</var>, <var>MORE</var>, <var>EOD</var>, or <var>EOJ</var>. The command can be used only by the system manager. </li> | ||
< | |||
<li>The <var>RESET COMMAND</var> command cannot be used to remove the system manager privilege requirement from a command, but it can be used to add system manager privilege. Once system manager privilege has been added to a command, it remains in effect for the life of the Online. </li> | |||
<li>If the <code>USE=</code> or <code>PRIVILEGE=</code> option is left out, the value of either parameter is not changed. </li> | |||
</ul> | |||
====When USE=RESPECT is not the default==== | ====When USE=RESPECT is not the default==== | ||
<p> | <p> | ||
The following table lists commands that do not have <code>USE=RESPECT</code> as the default. None of these commands has <var>RESPECT</var> as the default setting, because many SOUL procedures have one or more of these commands between the <var>USE</var> command and the command that directs its output to the <var>USE</var> data set. These defaults allow existing SOUL procedures to be run without change.</p> | |||
<table> | <table> | ||
<caption>Commands that do not default to USE = RESPECT</caption> | <caption>Commands that do not default to USE = RESPECT</caption> | ||
<tr class="head"> <th><p>Command</p></th> | |||
<tr> <th> | <th><p>Default</p></th> </tr> | ||
<p>Command</p> | |||
</th> <th> | |||
<p>Default</p> | |||
</th> </tr> | |||
<tr> <th><var> | <tr> <th><var> | ||
Line 337: | Line 311: | ||
<p>USE=IGNORE</p> | <p>USE=IGNORE</p> | ||
</td> </tr> | </td> </tr> | ||
</table> | </table> | ||
====Reviewing USE= and PRIVILEGE= settings==== | ====Reviewing USE= and PRIVILEGE= settings==== | ||
<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 will be sent to the screen or the USE data set, you can issue a VIEW COMMAND command. For example | <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 will be sent to the screen or the USE data set, you can issue a <var>VIEW COMMAND</var> command. For example: </p> | |||
<p class="code">VIEW COMMAND SETGRC | <p class="code">VIEW COMMAND SETGRC | ||
</p> | </p> | ||
<p> | <p> | ||
<p class=" | This command might display the following result:</p> | ||
<p class="output">SETGRC COMMAND USE=IGNORE PRIVILEGE=(LOGONREQ) | |||
</p> | </p> | ||
[[Category: System manager commands]] | [[Category: System manager commands]] | ||
[[Category:Commands]] | [[Category:Commands]] |
Latest revision as of 18:29, 21 September 2017
Summary
- Privileges
- System manager
- Function
- To control the USE data set support and the command privileges for each command, or to reset the USE output flags and the command privilege flags in the command table entry.
Syntax
RESET COMMAND command {USE=RESPECT | IGNORE | NOCLOSE | NOOPEN | NEVER} {PRIVILEGE=FILEMGR | SYSADM | LOGONREQ | SYSMGR | NOPROC | NONE}
Where:
- command is any Model 204 command except: BEGIN, MORE, EOD, or EOJ.
- USE output support options shown in the table below:
USE data set options for the RESET command Option Description RESPECT
Open USE output before the command is executed. If the command has produced any output, close the USE output after the command has executed.
RESPECT is the default option.
IGNORE
Do not open the USE output before the command is executed. Do not close the USE output after the command is executed. The output from the command does not go to the USE output unless the command is preceded by a USE command and then another command that has USE=NOCLOSE specified for it.
NOCLOSE
Do not close the USE output after the command is executed. Multiple commands with USE=NOCLOSE can be used (with no other commands intervening) and the output from each subsequent command is appended and sent to the same USE data set.
NOOPEN
Do not open the USE output before the command is executed. If the command has produced any output, close the USE output after the command has executed.
NEVER
Close the USE output before the command is executed. The output from the command goes to the usual output device.
-
The following table lists the PRIVILEGE options for RESET COMMAND:
PRIVILEGE options Option
Description
FILEMGR
FILE MANAGER privilege for the current file or group is required to execute the command (file privileges from CCASTAT or APSY File/Group definition).
SYSADM
SYSTEM ADMINISTRATOR privilege is required to execute the command (user privileges from CCASTAT or external security manager).
LOGONREQ
LOGON is required to execute the command (if SYSOPT=x'10').
SYSMGR
SYSTEM MANAGER privilege is required to execute the command (user privileges from CCASTAT or external security manager). This privilege can only be added to a command; it cannot be removed.
NOPROC
The command is not permitted from a SOUL procedure.
NONE
The command has no privilege requirements.
-
The next table lists the view-only PRIVILEGE options:
View-only PRIVILEGE options Option
Default file...
DEFAULTFILE
Or Group is required.
UPDATEFILE
Must have "Update" privilege.
SINGLEFILE
Must be a "Single File", not a Group.
You can specify a list of PRIVILEGE options by enclosing the list in parentheses and separating the options by commas.
Usage
- The RESET COMMAND command is not allowed for BEGIN, MORE, EOD, or EOJ. The command can be used only by the system manager.
- The RESET COMMAND command cannot be used to remove the system manager privilege requirement from a command, but it can be used to add system manager privilege. Once system manager privilege has been added to a command, it remains in effect for the life of the Online.
- If the
USE=
orPRIVILEGE=
option is left out, the value of either parameter is not changed.
When USE=RESPECT is not the default
The following table lists commands that do not have USE=RESPECT
as the default. None of these commands has RESPECT as the default setting, because many SOUL procedures have one or more of these commands between the USE command and the command that directs its output to the USE data set. These defaults allow existing SOUL procedures to be run without change.
Command |
Default |
---|---|
*COMMENT |
USE=IGNORE |
*SLEEP |
USE=IGNORE |
B |
USE=IGNORE |
BEGIN |
USE=IGNORE |
CLOSE |
USE=IGNORE |
CREATE |
USE=IGNORE |
CREATEG |
USE=IGNORE |
DEFAULT |
USE=IGNORE |
DELETE |
USE=IGNORE |
EDIT |
USE=IGNORE |
EOD |
USE=NEVER |
EOJ |
USE=NEVER |
I |
USE=IGNORE |
IF |
USE=IGNORE |
IN |
USE=IGNORE |
INCLUDE |
USE=IGNORE |
MORE |
USE=IGNORE |
MSGCTL |
USE=IGNORE |
N |
USE=NOCLOSE |
NEW |
USE=NOCLOSE |
NP |
USE=NOCLOSE |
O |
USE=IGNORE |
OPEN |
USE=IGNORE |
OPENC |
USE=IGNORE |
R |
USE=IGNORE |
RESET |
USE=IGNORE |
SETGRC |
USE=IGNORE |
U |
USE=IGNORE |
USE |
USE=IGNORE |
UTABLE |
USE=IGNORE |
Reviewing USE= and PRIVILEGE= settings
If you want to see how the Model 204 command table settings are set to know whether the output from a command will be sent to the screen or the USE data set, you can issue a VIEW COMMAND command. For example:
VIEW COMMAND SETGRC
This command might display the following result:
SETGRC COMMAND USE=IGNORE PRIVILEGE=(LOGONREQ)