DEFINE REMOTE command
Summary
- Privileges
- User 0 or system manager
- Function
- Defines the remote partner node and associates it with the link specified in this command
Syntax
DEFINE REMOTE name WITH SCOPE=SYSTEM LINK=linkname REMOTEID=luname [LOGIN={TRUST | NOTRUST}] [GUESTUSER={ACCEPT | REJECT}]
Where:
name | 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. | ||||
---|---|---|---|---|---|
SCOPE=SYSTEM | indicates that the definition is available to all users of the Model 204 system for the entire run. | ||||
LINK | 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. It must not be the name of a link specified in a local non-CNOS processgroup definition. | ||||
REMOTEID | 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. | ||||
LOGIN | specifies whether a local server process requires a password from the remote client at OPEN FILE time. Valid values are TRUST and NOTRUST:
|
||||
GUESTUSER | specifies whether a trusted client with a user ID that is undefined in CCASTAT or in ACF2 can access the Model 204 SQL Server. The ACCEPT option allows an unknown user to access the SQL Server; REJECT, the default, does not. |
Example
DEFINE REMOTE RMT1 WITH - SCOPE=SYSTEM - LINK=LINK1 - REMOTEID=LU01 - LOGIN=NOTRUST
Usage notes
You can define multiple remotes with the same link.
For more information, see Horizon CNOS connections.