24 – x25 client (OpenVMS)
Transitions the x25 client entity, which describes the X.25
client interface in an accessing system, to the "on" state.
enable [node node-id] x25 client
24.1 – Exception Messages
o session control no resources
The Session Control module does not have sufficient resources to
handle the call.
o session control unavailable
The Session Control module either does not exist or is disabled.
25 – x25_protocol
The x25 protocol dte enable command starts the operation of the
specified DTE. When the procedure completes, the status attribute
state may be running, synchronizing, or unsynchronized.
enable [node node-id] x25 protocol dte dte-name
The enable command will fail if the inbound dte class, link
service provider, or x25 address characteristics are not set.
The command will also fail if:
o There is a mismatch between the protocol profile and the link
service provider profile.
o The link service provider either does not exist or is in use
by someone else.
o The link service provider does not provide a maximum data size
of the greater of 260, DTE maximum packet size +4.
Example:
enable x25 protocol dte dte-0
25.1 – Exception Messages
o incompatible data sizes
The level 2 link service provider has not been configured for a
sufficiently large data size. The level 2 link service data size
must be at least 260 and at least the DTE maximum packet size +4.
o incompatible profiles
There is a mismatch between the x25 protocol dte profile and the
link service provider profile.
o insufficient information
inbound dte class, link service provider or x25 address
characteristics necessary for the successful completion of the
operation has not been set.
o link service provider error
Level 2 link service provider has flagged an error.
o link service provider in use
Another network layer entity is already using the specified link
service provider.
o no such link service provider
The link service provider specified in the DTE does not exist.
26 – x25 relay (Alpha)
26.1 – client
Transitions the specified x25 relay client entity to the "on" state.
enable [node node-id] x25 relay client client-name
26.1.1 – Exception Messages
o filter in error
The filters specified in the filters characteristic cannot be
used for one of the following reasons:
filters in The named filters are already in use.
use
no such The named filters do not exist.
filters
o insufficient information
One or more characteristics have not been specified.
Arguments:
reason Indicates which characteristics have not been
specified.
DTE class The DTE class characteristic has not
been specified.
filters The filters characteristic has not
been specified.
26.2 – pvc
Transitions the specified x25 relay pvc entity to the "on" state.
enable [node node-id] x25 relay pvc pvc-name
26.2.1 – Exception Messages
o insufficient information
One or more characteristics have not been specified.
Arguments:
reason Indicates which characteristics have not been
specified.
local pvc The local pvc characteristic has not
been specified.
relayed The relayed pvc characteristic has not
pvc been specified.
remote DTE The remote DTE class characteristic has
class not been specified.
27 – x25_server
Transitions the x25 server entity to the "on" state. The X.25
Server serves X.25 clients on an accessing system by providing
X.25 access to systems that do not have a direct connection to
a PSDN.
enable [node node-id] x25 server
27.1 – Exception Messages
o session control no resources
The Session Control module does not have sufficient resources to
handle the call.
o session control unavailable
The Session Control module either does not exist or is disabled.
27.2 – client
Transitions the specified x25 server client entity to the "on"
state.
enable [node node-id] x25 server client simple-name
27.2.1 – Exception Messages
o filter in use
One or more of the specified filters is already being used by
another client.
o insufficient information
Before enabling the client you must ensure that the following
characteristics have been given values of: application, filters,
nodes.
o filter in error
One or more of the specified filters does not exist, or is in
use.
28 – xot (OpenVMS Alpha)
28.1 – sap
enable [node node-id] xot sap sap-name
Enables a Service Access Point (SAP) entity of the X.25 Over
TCP/IP (XOT) module. The sap-name is a simple name which
unqiuely identifies a particular SAP instance.
Before enabling a SAP entity, you should check the local ip
addresses of any existing SAP entities. The local ip address
of 0.0.0.0 specifies that the SAP may listen on any available
IP interface. This local ip address of 0.0.0.0 should only
be specified if a single SAP is in use.
Example:
show xot sap * - ! To see what ip interfaces the
local ip address, state ! existing SAPs listen to.
enable xot sap sap-1
28.1.1 – link
enable [node node-id] xot sap sap-name link link-name
Enables a XOT SAP LINK entity which represents a remote system
with which XOT is allowed to communicate. The sap-name and
link-name are simple names which uniquely identify particular
SAP and LINK instances.
In the case of an inbound XOT connection, there must be a LINK
entity with a matching remote IP address and remote port
number in order for XOT to accept the TCP/IP connection.
In the case of an outbound connection, the LINK entity
specifies the remote IP address and remote port number of the
system with which to attempt the TCP/IP connection.
Example:
enable xot sap sap-0 link link-0
28.1.1.1 – Exception messages
o remote address in use
Remote port number and remote IP address being used.