STOP command: Making a file or group unavailable: Difference between revisions
m (Automatically generated page update) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 38: | Line 38: | ||
<p>The STOP command checks whether there is an active subsystem containing the named file or group as a required member. A file is checked for membership in all required groups. If the file or group is required by a subsystem, the STOP command is rejected with an error message. If the file or group is not required, it is marked unavailable for future use.</p> | <p>The STOP command checks whether there is an active subsystem containing the named file or group as a required member. A file is checked for membership in all required groups. If the file or group is required by a subsystem, the STOP command is rejected with an error message. If the file or group is not required, it is marked unavailable for future use.</p> | ||
<p><var class="product">Model 204</var> scans the list of active subsystems looking for optional uses of the file or group. All affected optional members are marked as no longer available for future use, although they may be currently in use by a subsystem user. When all subsystem users indicate that they are finished with an affected member (by closing the member), <var class="product">Model 204</var> discards all precompiled code referring to the member, and reclaims the pages in the temporary file. Further attempts by subsystem users to open the stopped member fails until a START command is executed. During this period, another copy of <var class="product">Model 204</var> can process the file or group. </p> | <p><var class="product">Model 204</var> scans the list of active subsystems looking for optional uses of the file or group. All affected optional members are marked as no longer available for future use, although they may be currently in use by a subsystem user. When all subsystem users indicate that they are finished with an affected member (by closing the member), <var class="product">Model 204</var> discards all precompiled code referring to the member, and reclaims the pages in the temporary file. Further attempts by subsystem users to open the stopped member fails until a START command is executed. During this period, another copy of <var class="product">Model 204</var> can process the file or group. </p> | ||
<p>In PQO, the affect of STOP FILE depends on whether it is issued on a server node or on a client node. For information about STOP FILE and STOP GROUP when remote files are affected, see the | <p>In PQO, the affect of STOP FILE depends on whether it is issued on a server node or on a client node. For information about STOP FILE and STOP GROUP when remote files are affected, see the [[PQO: Managing files and groups#Stopping and starting a remote file or scattered group|stopping and starting section in PQO]].</p> | ||
[[Category: System administrator commands]] | [[Category: System administrator commands]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
Latest revision as of 22:05, 7 April 2017
Summary
- Privileges
- System administrator
- Function
- Makes a file or permanent group unavailable for use
Syntax
STOP {FILE | [PERM] GROUP} name [AT location]
Where:
| name | is the name of a file or a group. |
|---|---|
| location |
|
Usage notes
The STOP command allows the system administrator to specify that a file or permanent group is unavailable to users. It prevents the opening of both subsystem and non-subsystem files or groups.
The STOP command causes subsequent opens of the file or group to fail. This command has no effect on a user who has the file or group open when the STOP is issued until the user closes the file or group and then attempts to reopen it. If you attempt to reopen a stopped file or group without first closing it, the reopen succeeds.
The STOP command checks whether there is an active subsystem containing the named file or group as a required member. A file is checked for membership in all required groups. If the file or group is required by a subsystem, the STOP command is rejected with an error message. If the file or group is not required, it is marked unavailable for future use.
Model 204 scans the list of active subsystems looking for optional uses of the file or group. All affected optional members are marked as no longer available for future use, although they may be currently in use by a subsystem user. When all subsystem users indicate that they are finished with an affected member (by closing the member), Model 204 discards all precompiled code referring to the member, and reclaims the pages in the temporary file. Further attempts by subsystem users to open the stopped member fails until a START command is executed. During this period, another copy of Model 204 can process the file or group.
In PQO, the affect of STOP FILE depends on whether it is issued on a server node or on a client node. For information about STOP FILE and STOP GROUP when remote files are affected, see the stopping and starting section in PQO.