JAL: /* Usage notes */

2014-02-18T16:18:02Z

Usage notes

← Older revision		Revision as of 16:18, 18 February 2014
Line 44:		Line 44:
	<p>You can disable a subsystem file to keep the file itself, or the subsystem to which it belongs, inaccessible for a short period of time, without shutting down the subsystem by using the DISABLE SUBSYSTEM command.</p>		<p>You can disable a subsystem file to keep the file itself, or the subsystem to which it belongs, inaccessible for a short period of time, without shutting down the subsystem by using the DISABLE SUBSYSTEM command.</p>
	<p>The consequence of disabling a subsystem file depends on whether the file is an optional or mandatory group member:</p>		<p>The consequence of disabling a subsystem file depends on whether the file is an optional or mandatory group member:</p>
	<table>
			<table>
			<tr class="head"> <th>If you disable...</th>
			<th>Consequences</th> </tr>

	<tr> <~~th>~~		<tr> <td>Mandatory file</td>
	~~<p>If you disable...</p>~~		<td>You effectively disable the subsystem, because users attempting to access the disabled file cannot access the subsystem. </td> </tr>
	~~</th> <th>~~
	~~<p>Consequences</p>~~
	~~</th> </tr>~~

	~~<tr> <th><var>~~
	<p>Mandatory file </p>
	~~</var></th>~~ <td>You effectively disable the subsystem, because users attempting to access the disabled file cannot access the subsystem. </td> </tr>

	<tr> <~~th><var>~~		<tr> <td>Optional file</td>
	<p>Optional file </p>		<td>Users can log in to the subsystem, but cannot access the disabled file. </td> </tr>
	~~</var></th>~~ <td>Users can log in to the subsystem, but cannot access the disabled file. </td> </tr>

	</table>		</table>

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

Alex: Automatically generated page update

2013-02-28T01:04:53Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>System manager
<dt>Function
<dd>Makes unavailable a remote file or scattered group that belongs to a local Parallel Query Option/204 subsystem
</dl>
==Syntax==
DISABLE SUBSYSTEM subsysname
{[FILE filename | GROUP grpname] AT location}


Where:
<table>
<tr>
<th>subsysname</th>
<td> is the name of the client subsystem.</td>
</tr>

<tr>
<th>filename</th>
<td> is the name of a remote file. You cannot specify local files.</td>
</tr>

<tr>
<th>grpname</th>
<td> is the name of a scattered group. You cannot specify non scattered groups.</td>
</tr>

<tr>
<th>location</th>
<td> must match the value of a symbolic destination name specified in the DESTINATION parameter of a local CCAD2C process definition.</td>
</tr>

</table>
===Syntax notes===
location is required. You cannot specify local files.
==Example==
DISABLE SUBSYS PQODENV FILE VEHICLES AT DENVER

==Usage notes==
If a file or group is marked "enabled" to a client subsystem, a user can open the file or group. To make a file or group inaccessible, you must issue DISABLE SUBSYSTEM for the file or group. 
If a file or group is disabled because of a communications problem and the problem is resolved, the file or group remains disabled until you explicitly enable it.
You can disable a subsystem file to keep the file itself, or the subsystem to which it belongs, inaccessible for a short period of time, without shutting down the subsystem by using the DISABLE SUBSYSTEM command.
The consequence of disabling a subsystem file depends on whether the file is an optional or mandatory group member:
<table>

<tr> <th>
If you disable...
</th> <th>
Consequences
</th> </tr>

<tr> <th><var>
Mandatory file 
</var></th> <td>You effectively disable the subsystem, because users attempting to access the disabled file cannot access the subsystem. </td> </tr>

<tr> <th><var>
Optional file 
</var></th> <td>Users can log in to the subsystem, but cannot access the disabled file. </td> </tr>

</table>
[[Category: System manager commands]]
[[Category:Commands]]

DISABLE command - Revision history

JAL: /* Usage notes */

Alex: Automatically generated page update