SECURE command: File: Difference between revisions
m (Automatically generated page update) |
|||
| Line 14: | Line 14: | ||
<p>The SECURE command secures the <var class="product">Model 204</var> file that is currently open. A special field in the password table serves as the key for securing files. SECURE processing copies this key into the open file. Then the secured file is opened and the password table key is compared with the file's copy. The file is accessible only if the two keys match.</p> | <p>The SECURE command secures the <var class="product">Model 204</var> file that is currently open. A special field in the password table serves as the key for securing files. SECURE processing copies this key into the open file. Then the secured file is opened and the password table key is compared with the file's copy. The file is accessible only if the two keys match.</p> | ||
<p>The LOGKEY command can be used by the system manager to change the password table from its initial setting. </p> | <p>The LOGKEY command can be used by the system manager to change the password table from its initial setting. </p> | ||
<p>When it processes SECURE, <var class="product">Model 204</var> ends any current User Language update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command is processing an update unit that cannot be backed out, the SECURE command is included in that update unit. For more information about <var class="product">Model 204</var> update units, see | <p>When it processes SECURE, <var class="product">Model 204</var> ends any current User Language update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command is processing an update unit that cannot be backed out, the SECURE command is included in that update unit. For more information about <var class="product">Model 204</var> update units, see [[File integrity and recovery#Update units and transactions|Update units and transactions]].</p> | ||
<p>To use the SECURE command you must have update authority to the selected file. If the file is open for read-only access, the SECURE command is rejected with the following message: </p> | <p>To use the SECURE command you must have update authority to the selected file. If the file is open for read-only access, the SECURE command is rejected with the following message: </p> | ||
<p class="code">M204.1036: UPDATES NOT PERMITTED. | <p class="code">M204.1036: UPDATES NOT PERMITTED. | ||
Revision as of 21:00, 6 August 2015
Summary
- Privileges
- File manager
- Function
- Secures the currently open Model 204 file
Syntax
SECURE
Syntax notes
SECURE must be issued in file context, that is, the current default must be a file, not a group.
Usage notes
The SECURE command secures the Model 204 file that is currently open. A special field in the password table serves as the key for securing files. SECURE processing copies this key into the open file. Then the secured file is opened and the password table key is compared with the file's copy. The file is accessible only if the two keys match.
The LOGKEY command can be used by the system manager to change the password table from its initial setting.
When it processes SECURE, Model 204 ends any current User Language update unit and begins a non-backoutable update unit. If a Model 204 command is processing an update unit that cannot be backed out, the SECURE command is included in that update unit. For more information about Model 204 update units, see Update units and transactions.
To use the SECURE command you must have update authority to the selected file. If the file is open for read-only access, the SECURE command is rejected with the following message:
M204.1036: UPDATES NOT PERMITTED.