JAL: misc formatting

2017-09-21T18:29:30Z

misc formatting

JDamon: Added commands that cannot be changed. Added note about SYSMGR which can only be added, not removed.

2017-09-20T19:58:48Z

Added commands that cannot be changed. Added note about SYSMGR which can only be added, not removed.

← Older revision		Revision as of 19:58, 20 September 2017
Line 16:		Line 16:
	<ul>		<ul>
	<li>		<li>
	<p>command is any User Language command.</p>		<p>command is any User Language command except: BEGIN, MORE, EOD or EOJ.</p>
	</li>		</li>

Line 95:		Line 95:
	<p>SYSMGR</p>		<p>SYSMGR</p>
	</var></th> <td>		</var></th> <td>
	<p>SYSTEM MANAGER privilege is required to execute the command (user privileges from CCASTAT or external security manager).</p>		<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>
	</td> </tr>		</td> </tr>

Line 143:		Line 143:
	</li>		</li>
	</ul>		</ul>

	==Usage==		==Usage==
	<p>The RESET COMMAND command is not allowed for BEGIN, MORE, EOD, or EOJ. The command can be used only by the system manager. </p>		<p>The RESET COMMAND command is not allowed for BEGIN, MORE, EOD, or EOJ. The command can be used only by the system manager. </p>

ELowell: /* When USE=RESPECT is not the default */

2013-06-27T21:01:36Z

When USE=RESPECT is not the default

← Older revision		Revision as of 21:01, 27 June 2013
Line 148:		Line 148:
	<p>If the USE= or PRIVILEGE= option is left out, the value of either parameter is not changed. </p>		<p>If the USE= or PRIVILEGE= option is left out, the value of either parameter is not changed. </p>
	====When USE=RESPECT is not the default====		====When USE=RESPECT is not the default====
	<p>~~Table 2-35~~ lists commands that do not have USE = RESPECT as the default. None of these commands has RESPECT as the default setting, because many User Language 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 User Language procedures to be run without change.</p>		<p>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 User Language 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 User Language 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>
Line 339:		Line 339:

	</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>		<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>

Dme: /* Reviewing USE= and PRIVILEGE= settings */

2013-03-21T12:49:14Z

Reviewing USE= and PRIVILEGE= settings

← Older revision		Revision as of 12:49, 21 March 2013
Line 344:		Line 344:
	</p>		</p>
	<p>Might display the following results:</p>		<p>Might display the following results:</p>
	<p class="code">SETGRC COMMAND USE=IGNORE ~~PRIVILEDGE~~=(LOGONREQ)		<p class="code">SETGRC COMMAND USE=IGNORE PRIVILEGE=(LOGONREQ)
	</p>		</p>
	[[Category: System manager commands]]		[[Category: System manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:05:23Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>System manager
<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.
</dl>
==Syntax==
RESET COMMAND command
{USE=RESPECT | IGNORE | NOCLOSE | NOOPEN | NEVER}
{PRIVILEGE=FILEMGR | SYSADM | LOGONREQ | SYSMGR
| NOPROC | NONE}


Where:
<ul>
<li>
command is any User Language command.
</li>

<li>
<var>USE</var> output support options shown in the table below.
<table>
<caption> USE data set options for the RESET command</caption>

<tr> <th>
Option
</th> <th>
Description
</th> </tr>

<tr> <th><var>
RESPECT (default)
</var></th> <td>
Open USE output before the command is executed. If the command has produced any output, close the USE output after the command has executed. 
</td> </tr>

<tr> <th><var>
IGNORE
</var></th> <td>
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.
</td> </tr>

<tr> <th><var>
NOCLOSE
</var></th> <td>
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.
</td> </tr>

<tr> <th><var>
NOOPEN
</var></th> <td>
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.
</td> </tr>

<tr> <th><var>
NEVER
</var></th> <td>
Close the USE output before the command is executed. The output from the command goes to the usual output device.
</td> </tr>

</table>
</li>

<li>
The following table lists the <var>PRIVILEGE</var> options for the RESET COMMAND command.
<table>
<caption> PRIVILEGE options</caption>

<tr> <th>
Option
</th> <th>
Description
</th> </tr>

<tr> <th><var>
FILEMGR
</var></th> <td>
FILE MANAGER privilege for the current file or group is required to execute the command (file privileges from CCASTAT or APSY File/Group definition).
</td> </tr>

<tr> <th><var>
SYSADM
</var></th> <td>
SYSTEM ADMINISTRATOR privilege is required to execute the command (user privileges from CCASTAT or external security manager).
</td> </tr>

<tr> <th><var>
LOGONREQ
</var></th> <td>
LOGON is required to execute the command (if SYSOPT=x'10').
</td> </tr>

<tr> <th><var>
SYSMGR
</var></th> <td>
SYSTEM MANAGER privilege is required to execute the command (user privileges from CCASTAT or external security manager).
</td> </tr>

<tr> <th><var>
NOPROC
</var></th> <td>
The command is not permitted from a User Language Procedure.
</td> </tr>

<tr> <th><var>
NONE
</var></th> <td>
The command has no privilege requirements.
</td> </tr>

</table>
The next table lists the view-only PRIVILEGE options.
<table>
<caption>View-only PRIVILEGE options</caption>

<tr> <th>
Option
</th> <th>
Default file...
</th> </tr>

<tr> <th><var>
DEFAULTFILE
</var></th> <td>
Or Group is required.
</td> </tr>

<tr> <th><var>
UPDATEFILE
</var></th> <td>
Must have "Update" privilege.
</td> </tr>

<tr> <th><var>
SINGLEFILE
</var></th> <td>
Must be a "Single File", not a Group.
</td> </tr>

</table>
You can specify a list of PRIVILEGE options by enclosing the list in parentheses and separating the options by commas.
</li>
</ul>
==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= or PRIVILEGE= option is left out, the value of either parameter is not changed. 
====When USE=RESPECT is not the default====
Table 2-35 lists commands that do not have USE = RESPECT as the default. None of these commands has RESPECT as the default setting, because many User Language 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 User Language procedures to be run without change.
<table>
<caption>Commands that do not default to USE = RESPECT</caption>

<tr> <th>
Command
</th> <th>
Default
</th> </tr>

<tr> <th><var>
*COMMENT
</var></th> <td>
USE=IGNORE
</td> </tr>

<tr> <th><var>
*SLEEP
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
B
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
BEGIN
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
CLOSE
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
CREATE
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
CREATEG
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
DEFAULT
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
DELETE
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
EDIT
</var></th> <td>
USE=IGNORE
</td> </tr>

<tr> <th><var>
EOD
</var></th> <td>
USE=NEVER 
</td> </tr>

<tr> <th><var>
EOJ
</var></th> <td>
USE=NEVER 
</td> </tr>

<tr> <th><var>
I
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
IF
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
IN
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
INCLUDE
</var></th> <td>
USE=IGNORE
</td> </tr>

<tr> <th><var>
MORE
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
MSGCTL
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
N
</var></th> <td>
USE=NOCLOSE 
</td> </tr>

<tr> <th><var>
NEW
</var></th> <td>
USE=NOCLOSE 
</td> </tr>

<tr> <th><var>
NP
</var></th> <td>
USE=NOCLOSE 
</td> </tr>

<tr> <th><var>
O
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
OPEN
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
OPENC
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
R
</var></th> <td>
USE=IGNORE
</td> </tr>

<tr> <th><var>
RESET
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
SETGRC
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
U
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
USE
</var></th> <td>
USE=IGNORE 
</td> </tr>

<tr> <th><var>
UTABLE
</var></th> <td>
USE=IGNORE
</td> </tr>

</table>
====Reviewing USE= and PRIVILEGE= settings====
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, 
VIEW COMMAND SETGRC

Might display the following results:
SETGRC COMMAND USE=IGNORE PRIVILEDGE=(LOGONREQ)

[[Category: System manager commands]]
[[Category:Commands]]

RESET COMMAND command - Revision history

JAL: misc formatting

JDamon: Added commands that cannot be changed. Added note about SYSMGR which can only be added, not removed.

ELowell: /* When USE=RESPECT is not the default */

Dme: /* Reviewing USE= and PRIVILEGE= settings */

Alex: Automatically generated page update