LOCATION parameter: Difference between revisions
(Automatically generated page update) |
|||
Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V3.2</var> or earlier | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The locally known name of a node (copy of <var class="product">Model 204</var>) in a Parallel Query Option/204 (PQO) network </p> | <p>The locally known name of a node (copy of <var class="product">Model 204</var>) in a Parallel Query Option/204 (PQO) network </p> |
Revision as of 15:46, 2 December 2014
D204 location
Summary
- Default value
- None
- Parameter type
- System
- Where set
- On User 0's parameter line
- Related products
- All
- Introduced
- Model 204 V3.2 or earlier
Description
The locally known name of a node (copy of Model 204) in a Parallel Query Option/204 (PQO) network
The LOCATION parameter is specific to PQO users. It is required for both clients and servers. The LOCATION value must be unique and from one to eight characters in length.
The LOCATION parameter is used internally, is displayed to identify client users when a service thread issues a LOGWHO command, and is used with BUMP SUBSYSTEM, MONITOR SUBSYSTEM, and STOP SUBSYSTEM to identify a service subsystem by its associated client.
The LOCATION parameter value does not have to match the value specified for any DEFINE FILE command LOCATION parameter or for any remote file specification (filename AT location).
LOCATION is viewable with VIEW but is not resettable.