DEFINE REMOTE command - Revision history

ELowell: /* Usage notes */

2017-04-06T21:42:06Z

Usage notes

← Older revision		Revision as of 21:42, 6 April 2017
Line 73:		Line 73:
	<p>You can define multiple remotes with the same link. </p>		<p>You can define multiple remotes with the same link. </p>
	<p>For more information, see [[Horizon CNOS connections]].</p>		<p>For more information, see [[Horizon CNOS connections]].</p>

			<p>For general syntax and usage notes that apply to all forms of the <var>DEFINE</var> command, see <var>[[DEFINE command]]</var>.</p>

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

ELowell: /* Syntax */

2016-02-04T20:57:51Z

Syntax

← Older revision		Revision as of 20:57, 4 February 2016
Line 29:		Line 29:
	<tr>		<tr>
	<th><var>LINK</var></th>		<th><var>LINK</var></th>
	<td> specifies the name of the link with which this remote is associated. This name must be the same as the link name specified on a local DEFINE LINK command. <~~var~~>It must not be the name of a link specified in a local non-CNOS processgroup definition.</~~var~~></td>		<td> specifies the name of the link with which this remote is associated. This name must be the same as the link name specified on a local DEFINE LINK command.
			<p class="note"><b>Note:</b> It must not be the name of a link specified in a local non-CNOS processgroup definition.</p></td>
	</tr>		</tr>

Line 61:		Line 62:

	</table>		</table>

	==Example==		==Example==
	<p class="code">DEFINE REMOTE RMT1 WITH -		<p class="code">DEFINE REMOTE RMT1 WITH -

ELowell: /* Usage notes */

2016-02-04T20:55:21Z

Usage notes

← Older revision		Revision as of 20:55, 4 February 2016
Line 70:		Line 70:
	==Usage notes==		==Usage notes==
	<p>You can define multiple remotes with the same link. </p>		<p>You can define multiple remotes with the same link. </p>
	<p>For more information ~~about~~ Horizon CNOS connections~~, see the <var>Model 204 Horizon: Intersystem Processing Guide</var>~~.</p>		<p>For more information, see [[Horizon CNOS connections]].</p>

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

Alex: Automatically generated page update

2013-02-28T01:04:49Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>User 0 or system manager
<dt>Function
<dd>Defines the remote partner node and associates it with the link specified in this command
</dl>
==Syntax==
<p class="syntax">DEFINE REMOTE name WITH
SCOPE=SYSTEM
LINK=linkname
REMOTEID=luname
[LOGIN={TRUST | NOTRUST}]
[GUESTUSER={ACCEPT | REJECT}]
</p>

<b>Where:</b>
<table>
<tr>
<th>name</th>
<td> is the locally known name for this entity. It is used on DEFINE SESSIONGROUP commands to refer to this remote. The length of the name must be eight characters or less. ALL is a reserved word and cannot be used. </td>
</tr>

<tr>
<th><var>SCOPE=SYSTEM</var></th>
<td> indicates that the definition is available to all users of the <var class="product">Model 204</var> system for the entire run. </td>
</tr>

<tr>
<th><var>LINK</var></th>
<td> specifies the name of the link with which this remote is associated. This name must be the same as the link name specified on a local DEFINE LINK command. <var>It must not be the name of a link specified in a local non-CNOS processgroup definition.</var></td>
</tr>

<tr>
<th><var>REMOTEID</var></th>
<td> is the name of the LU at the remote node to which the CNOS link is connected. This name is the SNA Communications Server APPL definition name (applid value) of the remote node. This REMOTEID value must match the LOCALID value specified on the DEFINE LINK command at the remote node. </td>
</tr>

<tr>
<th><var>LOGIN</var></th>
<td> specifies whether a local server process requires a password from the remote client at OPEN FILE time. Valid values are TRUST and NOTRUST:
<table>
<tr>
<th><var>TRUST</var></th>
<td> specifies that the local system manager trusts the remote system to verify a user ID shipped in an inbound conversation request. Such a user is logged in without a password by the server process and assigned privileges from either CCASTAT or an external security package. </td>
</tr>

<tr>
<th><var>NOTRUST</var></th>
<td> specifies that a valid password must be present in the inbound conversation request. NOTRUST is the default. </td>
</tr>

</table>
</td>
</tr>

<tr>
<th><var>GUESTUSER</var></th>
<td> specifies whether a trusted client with a user ID that is undefined in CCASTAT or in ACF2 can access the <var class="product">Model 204</var> SQL Server. The ACCEPT option allows an unknown user to access the SQL Server; REJECT, the default, does not.</td>
</tr>

</table>
==Example==
<p class="code">DEFINE REMOTE RMT1 WITH -
SCOPE=SYSTEM -
LINK=LINK1 -
REMOTEID=LU01 -
LOGIN=NOTRUST
</p>
==Usage notes==
<p>You can define multiple remotes with the same link. </p>
<p>For more information about Horizon CNOS connections, see the <var>Model 204 Horizon: Intersystem Processing Guide</var>.</p>
[[Category: System manager commands]]
[[Category:Commands]]