PQO: Scattered APSY subsystems - Revision history

JAL: minor formatting

2018-08-08T01:13:48Z

minor formatting

← Older revision		Revision as of 01:13, 8 August 2018
Line 154:		Line 154:
	<th>Meaning</th>		<th>Meaning</th>
	</tr>		</tr>

	<tr>		<tr>
	<td>Full trust</td>		<td>Full trust</td>
	<td>Only the subsystem name, location, and status (active or suspended) appear on the service node's definition, which you create on the Subsystem Trust screen.</td>		<td>Only the subsystem name, location, and status (active or suspended) appear on the service node's definition, which you create on the Subsystem Trust screen.</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Partial trust</td>		<td>Partial trust</td>
Line 167:		Line 169:
	</td>		</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Restricted trust</td>		<td nowrap>Restricted trust</td>
	<td>For a subsystem with restricted trust, the subsystem service definition is based on entries you make on these five screens:		<td>For a subsystem with restricted trust, the subsystem service definition is based on entries you make on these five screens:
	<ul>		<ul>
Line 179:		Line 182:
	<p>		<p>
	The client subsystem's access is determined by the SCLASS, user, and file privileges that you specify on these screens. For a subsystem that has restricted trust, you <var class="term">do not</var> make any entries on the Subsystem Trust screen. You can specify full or partial trust, <var class="term">or specify </var>restricted trust.</p>		The client subsystem's access is determined by the SCLASS, user, and file privileges that you specify on these screens. For a subsystem that has restricted trust, you <var class="term">do not</var> make any entries on the Subsystem Trust screen. You can specify full or partial trust, <var class="term">or specify </var>restricted trust.</p>
	</td>		</td></tr>
	</tr>
	<tr>		<tr><td><p>No trust</p></td>
	<td>		<td><p>On the service node, if there is neither a subsystem service definition nor a trust definition for the client subsystem. The client subsystem cannot access any files on the service node <var class="term">as subsystem files</var>.</p>
	<p>No trust</p>
	</td>
	<td>
	<p>
	On the service node, if there is neither a subsystem service definition nor a trust definition for the client subsystem. The client subsystem cannot access any files on the service node <var class="term">as subsystem files</var>.</p>
	<p>		<p>
	However, the files on the service node can be accessed from within a client subsystem as individual, nonsubsystem files, if the following criteria are met:</p>		However, the files on the service node can be accessed from within a client subsystem as individual, nonsubsystem files, if the following criteria are met:</p>
Line 193:		Line 191:
	<li>PQO is installed at both sites, and there are link, processgroup, and process definitions connecting the client node to the service node.</li>		<li>PQO is installed at both sites, and there are link, processgroup, and process definitions connecting the client node to the service node.</li>
	<li>Horizon Interface is installed at both sites, and there are link, processgroup, and process definitions connecting the client node to the service node.</li>		<li>Horizon Interface is installed at both sites, and there are link, processgroup, and process definitions connecting the client node to the service node.</li>
	<li>OPENCTL parameter setting allows remote access for any given file (with a setting of `08,' `04,' or `02'). For information about the OPENCTL parameter, see [[PQO: Managing files and groups#Allowing access to remote files\|Allowing access to remote files]] and [[OPENCTL parameter]].</li>		<li>OPENCTL parameter setting allows remote access for any given file (with a setting of '08,' '04,' or '02'). For information about the OPENCTL parameter, see [[PQO: Managing files and groups#Allowing access to remote files\|Allowing access to remote files]] and [[OPENCTL parameter]].</li>
	</ul>		</ul>
	</td>		</td></tr>
	</tr>
	</table>		</table>
	<p>		<p>
Line 211:		Line 208:
	<td>Subsystem Trust screen</td>		<td>Subsystem Trust screen</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Restricted trust</td>		<td>Restricted trust</td>
Line 241:		Line 239:
	<p>		<p>
	If all remote file references on the client node are to manual members, the service subsystem is not started until the first manual member is opened. If any remote files need to be opened automatically on the server node, then the following message is written to the server node audit trail for each service subsystem that is successfully started:</p>		If all remote file references on the client node are to manual members, the service subsystem is not started until the first manual member is opened. If any remote files need to be opened automatically on the server node, then the following message is written to the server node audit trail for each service subsystem that is successfully started:</p>
	<p class="code">M204.2330: ~~SUBSYSTEM~~ <var class="term">subsysname</var> ~~FROM~~ <var class="term">location</var> ~~STARTED~~</p>		<p class="code">M204.2330: Subsystem <var class="term">subsysname</var> from <var class="term">location</var> started </p>

	====CREATE GROUP command must precede the START command====		====CREATE GROUP command must precede the START command====

JAL: /* Overview */ typo

2016-04-27T16:07:20Z

Overview: typo

← Older revision		Revision as of 16:07, 27 April 2016
Line 4:		Line 4:
	With Parallel Query Option/204, application subsystem definitions and requests can refer to remote files or scattered groups. </p>		With Parallel Query Option/204, application subsystem definitions and requests can refer to remote files or scattered groups. </p>
	<p>		<p>
	This ~~chapter~~ explains how to manage, run, and maintain client and service subsystems that run under the Application Subsystem Facility (APSY). Emphasis is on features and concepts that are specific to Parallel Query Option/204. Basic knowledge of Model 204 subsystem management is assumed.</p>		This page explains how to manage, run, and maintain client and service subsystems that run under the Application Subsystem Facility (APSY). Emphasis is on features and concepts that are specific to Parallel Query Option/204. Basic knowledge of Model 204 subsystem management is assumed.</p>

	==Required system parameters==		==Required system parameters==

ELowell: /* Subsystem Class Users screen (client definition) */

2016-01-14T20:48:07Z

Subsystem Class Users screen (client definition)

← Older revision		Revision as of 20:48, 14 January 2016
Line 599:		Line 599:

	<p class="caption" style="width:468px">Subsystem Class Users screen</p>		<p class="caption" style="width:468px">Subsystem Class Users screen</p>
	<p class="figure">[[File:PQO_ch6_12.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_12.gif]] </p>

	<p>		<p>

ELowell: /* Subsystem Classes screen (client definition) */

2016-01-14T20:47:52Z

Subsystem Classes screen (client definition)

← Older revision		Revision as of 20:47, 14 January 2016
Line 591:		Line 591:

	<p class="caption" style="width:468px">Subsystem Classes screen</p>		<p class="caption" style="width:468px">Subsystem Classes screen</p>
	<p class="figure">[[File:PQO_ch6_11.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_11.gif]] </p>

	<p>		<p>

ELowell: /* Operational Parameters screen (client definition) */

2016-01-14T20:47:36Z

Operational Parameters screen (client definition)

← Older revision		Revision as of 20:47, 14 January 2016
Line 552:		Line 552:

	<p class="caption" style="width:468px">Operational Parameters screen</p>		<p class="caption" style="width:468px">Operational Parameters screen</p>
	<p class="figure">[[File:PQO_ch6_10.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_10.gif]] </p>

	<p>		<p>

ELowell: /* Subsystem File Use screen (client definition) */

2016-01-14T20:47:24Z

Subsystem File Use screen (client definition)

← Older revision		Revision as of 20:47, 14 January 2016
Line 538:		Line 538:

	<p class="caption" style="width:468px">Subsystem File Use screen</p>		<p class="caption" style="width:468px">Subsystem File Use screen</p>
	<p class="figure">[[File:PQO_ch6_9.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_9.gif]] </p>

	<p>		<p>

ELowell: /* Subsystem Activity screen (client definition) */

2016-01-14T20:47:14Z

Subsystem Activity screen (client definition)

← Older revision		Revision as of 20:47, 14 January 2016
Line 526:		Line 526:

	<p class="caption" style="width:468px">Subsystem Activity screen</p>		<p class="caption" style="width:468px">Subsystem Activity screen</p>
	<p class="figure">[[File:PQO_ch6_8.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_8.gif]] </p>

	<p>		<p>

ELowell: /* Subsystem Class Users screen (service definition) */

2016-01-14T20:46:59Z

Subsystem Class Users screen (service definition)

← Older revision		Revision as of 20:46, 14 January 2016
Line 506:		Line 506:

	<p class="caption" style="width:468px">Subsystem Class Users screen</p>		<p class="caption" style="width:468px">Subsystem Class Users screen</p>
	<p class="figure">[[File:PQO_ch6_7.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_7.gif]] </p>

	<p>		<p>

ELowell: /* Subsystem Classes screen (service definition) */

2016-01-14T20:46:47Z

Subsystem Classes screen (service definition)

← Older revision		Revision as of 20:46, 14 January 2016
Line 494:		Line 494:

	<p class="caption" style="width:468px">Subsystem Classes screen</p>		<p class="caption" style="width:468px">Subsystem Classes screen</p>
	<p class="figure">[[File:PQO_ch6_6.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_6.gif]] </p>

	<p>		<p>
Line 501:		Line 501:
	The Location field is protected from input because there is no remote access on the server node. The files shown here, CLIENTS and PRODUCTS, are local (they reside on the service node).</p>		The Location field is protected from input because there is no remote access on the server node. The files shown here, CLIENTS and PRODUCTS, are local (they reside on the service node).</p>
	<p>		<p>
	Parts of this screen pertaining to procedure files are masked, because PQO does not support remote procedure files. </p>		Parts of this screen pertaining to procedure files are masked, because PQO does not support remote procedure files.</p>

	===Subsystem Class Users screen (service definition)===		===Subsystem Class Users screen (service definition)===

ELowell: /* Operational Parameters screen (service definition) */

2016-01-14T20:46:27Z

Operational Parameters screen (service definition)

← Older revision		Revision as of 20:46, 14 January 2016
Line 480:		Line 480:

	<p class="caption" style="width:468px">Operational Parameters screen</p>		<p class="caption" style="width:468px">Operational Parameters screen</p>
	<p class="figure">[[File:PQO_ch6_5.gif~~\|468px~~]] </p>		<p class="figure">[[File:PQO_ch6_5.gif]] </p>

	<p>		<p>