application, which becomes active only when your OpenVMS system receives an OSI call for that particular application invocation. Example: create osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" - invocation [AP_Invocation = -1, AE_Invocation = -1] 2 osi_transport Creates the OSI Transport module. Refer to HELP ENTITY OSI_TRANSPORT for information concerning this entity and its subentities. create [node node-id] osi transport Select application for information on creating osi transport application subentities on OpenVMS. Select template for information on creating osi transport templates. 3 Exception_Messages o already exists An osi transport entity already exists. 3 application_(OpenVMS) Creates an instance of the osi transport application entity. That instance is identified by the simplename application-name. create [node node-id] osi transport - application application-name An OSI Transport Application stores information about an end user that is activated for receipt of an incoming connection request when the request contains that end user's name in its Destination Name field. Example: create osi transport application osit$ivp 3 template Creates a instance of an osi transport template entity, identified by the simplename used in place of template-id. create [node node-id] osi transport template template-id An OSI Transport Template entity provides a collection of characteristics that supply default values for certain parameters that influence the operation of a port on a transport connection. One template, with the reserved template-id of "default", is automatically created when the osi transport entity is created. This template is used by default when a user does not specify a template-id in a call to establish a connection. The default template is deleted automatically when the osi transport entity is deleted. Similarly, the initial values of the attributes in a template are the same as the current values in the default template. Example: create osi transport template osit$rfc1006plus 4 Exception_Messages o already exists An osi transport template entity by that instance name already exists. 2 routing Creates the routing entity. For information about the Routing entity and its subentities, refer to HELP ENTITY ROUTING. create [node node-id] routing type routing-type The Type argument is required. It determines the value of the type characteristic attribute. These are the possible routing-type values: endnode The node is an end system. L1router The node is a level 1 router. L2router The node is a level 2 router. Example: create routing type endnode Select circuit for information on creating routing circuit, routing circuit adjacency, and routing circuit reachable address subentities. Select egp_group for information on creating routing egp group and routing egp group egp neighbor subentities. Select permitted_neighbor for information on creating routing permitted neighbor subentities. 3 Exception_Messages o already exists A routing entity already exists. o invalid router type The type argument specifies an invalid router type on the create command. 3 circuit Creates an instance of a routing circuit entity which represents a data link to another node, specified by the simple name circuit-name. create [node node-id] routing circuit circuit-name - type circuit-type The Type argument is required. Possible circuit-type values are: csma-cd - a broadcast circuit ddcmp - a DDCMP circuit fddi - an FDDI large packet circuit hdlc - an HDLC circuit x25 da - a dynamically allocated X.25 circuit x25 permanent - an X.25 permanent virtual circuit x25 static incoming - a static incoming X.25 circuit x25 static outgoing - a static outgoing X.25 circuit On OpenVMS for FDDI routing circuits, the type should only be fddi if large packet support is in use, otherwise the type should be csma-cd. Examples: create routing circuit fddi-1 type csma-cd create routing circuit fddi-1 type fddi ! for large packet support Select adjacency for information on creating routing circuit adjacency subentities. Select reachable_address for information on creating routing circuit reachable address subentities. 4 Exception_Messages o invalid circuit type The specified circuit type is invalid. Argument: reason Reason why the circuit type is invalid. 1 A dynamically allocated X.25 circuit type is not permitted for a level 1 router. o maximum circuits exceeded An attempt has been made to create more than the maximum number of circuits allowed. 4 adjacency Creates an instance of a routing circuit adjacency. An adjacency describes a neighboring node that is accessible through a particular circuit. This create command is allowed only if the circuit is a csma-cd circuit and the type is L1router or L2router. create [node node-id] routing circuit circuit-name - adjacency adjacency-name, - endnode ids {id[,id...]}, - LAN address LAN-address [,data format string] The required Endnode IDs argument is a set of source system IDs. The required LAN Address argument is the Data Link address from which the adjacency receives end system hellos. The optional Data Format argument is the format of the reachable address. 4 reachable_address Creates a routing circuit reachable address entity instance which contains information about a manually entered address prefix accessible over that circuit. It exists only on L2 routers and end nodes. create [node node-id] routing circuit circuit-name - reachable address simple-name - address prefix address-prefix On an end system, the type may be "outbound" or (for a broadcast circuit only) "filter". A reachable address of type outbound behaves in a way similar to that on an L2 router except that the routing information is used to control the operation of the ES cache. A reachable address of type filter (for the broadcast circuit only) specifies the permitted LAN addresses of routers on the LAN that will be used by the reverse path cache algorithm. To switch between outbound and filter types, the reachable address must first be disabled. For either outbound or filter type, the mapping attribute should be set to manual because the default is X.121. The address prefix argument is required. It specifies the address prefix to which this reachable address corresponds. Example: create routing circuit csmacd-1 reachable address to-bulean - address prefix 49::4 5 Exception_Messages o address prefix not unique A reachable address already exists with the specified address prefix. o invalid address prefix Specified address prefix has more than two digits, and does not correspond to a valid AFI. o non DA circuit A reachable address on an endnode can only be created on a DA circuit. 3 egp_group Creates a routing egp group defining a set of systems in the same autonomous system with which this sytem may exchange EGP messages. create [node node-id] routing egp group group-name This entity is supported only on Level 2 routers that support dual routing (and, in particular, the EGP routing protocol). 4 egp_neighbor Creates a routing egp group egp neighbor entity which defines one of the systems in the same autonomous group defined by the owning egp group entity. create [node node-id] routing egp group group-name egp neighbor - neighbor-name ip address ip-address This entity is supported only on Level 2 routers that support dual routing (and, in particular, the EGP routing protocol). 5 Exception_Messages o duplicate ip address An EGP neighbor with this IP address already exists in this EGP group. 3 permitted_neighbor Creates a routing permitted neighbor entity instance which represents a neighboring node on a nonbroadcast circuit that is permitted to connect to this node. Neighbor-name is a simple name. ID is the node ID of a potential neighbor node. create [node node-id] routing - permitted neighbor neighbor-name - id node-id Examples: create routing permitted neighbor nashua_decnet-osi - id 08-00-2b-12-34-56 create routing permitted neighbor nashua_phase_iv - id aa-00-04-00-12-34 4 Exception_Messages o duplicate node id A routing permitted neighbor entity with the specified node ID already exists. Argument: name The name of the permitted neighbor that already has this node ID. o permitted neighbor already exists A routing permitted neighbor entity with the specified name already exists. 2 session_control Creates the Session Control module. For information about this entity and its subentities, refer to HELP ENTITY SESSION_CONTROL. create [node node-id] session control Select application for information on creating session control application subentities. Select proxy for information on creating session control proxy subentities on Tru64 UNIX. Select transport_service for information on creating session control transport service subentities. 3 Exception_Messages o already exists A session control entity already exists. 3 application Creates a session control application entity instance which stores information about an end user that this activated for receipt of an incoming connection request when the request contains that end user's name in its destination name field. Application-name is the simple name assigned to the application when it is created. create [node node-id] session control application application-name Example: create session control application task 4 Exception_Messages o already exists An instance of a session control application entity by that name already exists. 3 proxy_(Tru64_UNIX) create [node node-id] session control proxy name Name is the simple name assigned to a particular entity instance. The name is the management identifier for the proxy database entry and is kept unique among the entries in this database maintained by Session Control. 4 Exception_Messages o already exists A session control proxy entity already exists. 3 transport_service Creates an instance of a session control transport service entity which stores information about modules in the Transport layer that support Session Control. create [node node-id] session control - transport service transport-name - protocol protocol-id [,tsel hex-string] The Protocol argument is required. It specifies the transport protocol to be used by this transport service: '04'H This transport service uses the NSP transport protocol. '05'H This transport service uses version 1 of the OSI transport protocol. The optional TSEL argument is only applicable for the OSI transport. Examples: create session control transport service nsp protocol %X04 create session control transport service osi protocol %X05 4 tsel The Transport Selector is used by the OSI Transport Module to bind incoming connection requests to session control. The default value is the hexadecimal representation of "DEC0". This argument is not applicable for NSP transport. Example: create session control - transport service osi protocol %X05, tsel %DEC0 4 Exception_Messages o already exists This session control transport service entity already exists. o duplicate protocol The session control transport service entity fails on creation because the protocol already exists. o protocol not supported The session control transport service entity fails on creation because the protocol is not supported by this module. 2 token_ring_(Tru64_UNIX) Creates the Token Ring module. For information about this entity and its subentities, refer to HELP ENTITY TOKEN_RING. create [node node-id] token ring Select station for information on creating token ring station and token ring station fa map subentities. 3 Exception_Messages o already exists A token ring entity already exists. 3 station Creates an instance of a token ring station. create [node node-id] token ring station station-name - communication port device-name [,mode loopback-or-normal] [,transparent source routing enabled] The Communication Port is required. It specifies a Tru64 UNIX device name to assign to this station. The name must be in the format ddn, where dd is the device name prefix and n is the device number. Device device-name DETRA tra0 Select FA_map for information on creating token ring station fa map subentities. 4 FA_map create [node node-id] token ring station station-name - FA map famap-id 5 Exception_Messages o already exists An FA map entity with the same identifier already exists. 4 mode The mode in which this station will be enabled. Can be either normal (default) or loopback. 4 transparent_source_routing Indicates whether the transparent source routing functionality will or will not be enabled. The default is enabled. This value cannot be disabled. 4 Exception_Messages o already exists A token ring station entity already exists. o communication port in use A communication port is already reserved by another entity. o invalid communication port Cannot run Token Ring data link on this communication port. 2 x25_access Creates the X.25 Access module on the system. The Maximum Active Ports argument is optional. It specifies the maximum number of ports that can be created on this system. create [node node-id] x25 access [maximum active ports integer] For more information about the X.25 Access entity and its subentities, refer to HELP ENTITY X25_ACCESS. 3 application Creates an X.25 Access Application entity instance which defines an application to be executed for an incoming call. create [node node-id] x25 access application application-name Examples: create x25 access application X29_LOGIN create X25 access application X25_MAIL create X25 access application APPLICATION_0 3 dte_class Creates an X25 access dte class entity which defines a named class of DTEs which is a group of local DTEs or a group of DTEs on a remote gateway system. create [node node-id] x25 access dte class class-name - type local-or-remote [,profile profile-name] (Tru64 UNIX) Type is a required argument. Profile is an optional Tru64 UNIX argument used to supply default values for the X.121 mapping attribute in this entity. Examples: create x25 access dte class dte-0 type local create x25 access dte class AUSTPAC type local create x25 access dte class REMOTE-CLASS-0 type remote 3 filter Creates an X.25 access filter entity which defines the criteria by which the destination of an incoming call is determined. create [node node-id] x25 access filter filter-name Example: create x25 access filter FILTER_0 3 reachable_address Creates an X.25 access reachable address entity which maps a destination network service access point (NSAP) address in an outgoing call to a DTE class/DTE address pair. create [node node-id] x25 access - reachable address address-name - address prefix address-prefix The Address Prefix argument is required. It is the leading substring of an NSAP address associated with this reachable address entity. Example: create x25 access reachable address x121 address prefix 37 4 Exception_Messages o address prefix not unique A reachable address with the specified prefix already exists. 3 security_dte_class Creates an X.25 access security dte class entity which is used to control inbound and outbound calls. create [node node-id] x25 access - security dte class class-name 4 remote_dte Creates an X.25 access security dte class remote dte instance which is a collection of access control attributes that control inbound calls from and outbound calls to a set of remote DTEs. create [node node-id] x25 access - security dte class class-name - remote dte dte-name - remote address prefix dte-address-prefix The Remote Address Prefix argument is required. It is a leading substring of a DTE address associated with this remote address entity. Wildcards can be used in the address prefix. Example: create x25 access - security dte class Default remote dte remdte-0 - remote address prefix 9876* 3 security_filter Creates an X.25 access security filter entity which is a collection of access control attributes that control access to one or more filters. create [node node-id] x25 access security filter filter-name Example: create x25 access security filter APPL_APPLICATION_0 3 template Creates an X.25 access template entity which is used to supply default values for call parameters when an outgoing call is made. Values in a template can be overridden by user-supplied values. create [node node-id] x25 access template template-name Example: create x25 access template TEMPLATE-0 2 x25_client_(OpenVMS) Creates an X.25 client module which describes the X.25 client interface in an accessing system, through which X.25 clients gain access to a PSDN via an X.25 server in a gateway system. For information about the X25 Client entity, refer to HELP ENTITY X25_CLIENT. create [node node-id] x25 client [maximum session connections integer] [,incoming session template simple-name] The Maximum Session Connections and Incoming Session Template arguments are optional. 3 maximum_session_connections Maximum number of concurrent Session Control connections that can be supported by the X.25 Client module. This argument determines the value of the maximum session connections characteristic. If not specified, the implementation-specific default value of the characteristic maximum session connections is used. 3 incoming_session_template The Session Control template specified for an open/incoming connection at the end-user Session Control interface. 2 x25_protocol Creates the X.25 Protocol module which operates the packet level protocol interface to a PSDN, as defined by the CCITT and ISO. create [node node-id] x25 protocol For information about the X25 Protocol entity and its subentities, refer to HELP ENTITY X25_PROTOCOL. Select dte for information on creating x25 protocol dte and x25 protocol dte pvc subentities. Select group for information on creating x25 protocol groups. 3 dte Creates an X.25 protocol dte entity which describes a local DTE. create [node node-id] x25 protocol dte dte-name - profile profile-name [,maximum active circuits integer] The Profile argument is required. It is the name of the profile that supplies subscription details of the PSDN to which the DTE is connected. The Maximum Active Circuits argument is optional. It specifies the number of virtual circuits that can be active at any time on the DTE for SVCs and PVCs (OpenVMS). Example: create x25 protocol dte dte-1 profile "ISO8881" 4 pvc Creates an X.25 protocol dte pvc entity which describes a permanent virtual circuit (PVC). create [node node-id] x25 protocol dte dte-name - pvc pvc-name - channel integer [,packet size integer] [,window size integer] The Channel argument is required. It is the concatenated logical channel group and logical channel number for the PVC, and it should be a unique value among PVCs on this DTE. These channel numbers must not be present in the incoming list or outgoing list of the parent DTE. Packet Size and Window Size are optional arguments. Example: create x25 protocol dte dte-0 pvc PVC-0 channel 5 5 packet_size Packet size, in octets, for the PVC. This argument determines the value of the packet size characteristic. This value should be within the maximum and minimum packet size specifier by the parent DTE. 5 window_size Window size for the PVC. This argument determines the value of the window size characteristic. This value should be within the maximum and minimum window size specifier by the parent DTE. 5 Exception_Messages o name not unique The PVC entity is not unique at the gateway system. 3 group Creates an X.25 protocol group entity which specifies a number of DTEs that make up a closed user group (CUG). create [node node-id] x25 protocol group group-name Example: create x25 protocol group GROUP-0 2 x25_relay_(Alpha) Creates an X.25 relay entity which accepts an incoming call from one client and redirects it to another client. For information about the X25 Relay entity and its subentities, refer to HELP ENTITY X25_RELAY. create [node node-id] x25 relay [maximum active connections integer] The Maximum Active Connections argument is optional. It specifies the maximum number of active connections supported. 3 client Creates an X.25 relay client which provides a set of default values to be used to set up a relay between an incoming call and an outgoing call. create [node node-id] x25 relay client client-name 3 pvc Creates an X.25 relay pvc entity which provides a set of default values to be used to establish a connection to a client over a permanent virtual circuit (PVC). create [node node-id] x25 relay pvc pvc-name - type local-or-remote The Type argument is required, either local or remote. Example: create x25 relay pvc pvc-0 type local 2 x25_server Creates X.25 server module which represents the X.25 server that runs on a gateway system. The X.25 server serves X.25 clients on accessing systems, providing X.25 access to systems that do not have a direct connection to a PSDN. For information about the X25 Server entity and its subentities, refer to HELP ENTITY X25_SERVER. create [node node-id] x25 server [maximum session connections number] [,incoming session template simple-name] (Tru64 UNIX) The Maximum Session Connections optional argument that specifies the number of incoming and outgoing connections that may be supported concurrently. Incoming Session Template is an optional argument for Tru64 UNIX that specifies the Session Control template used to filter incoming session control connection requests. 3 client Creates an x25 server client entity which provides a set of default values to be used to establish a Session Control connection with an X.25 client when an incoming call arrives for that client. You should create an x25 server client entity for each X.25 client with which the gateway system is associated. create [node node-id] x25 server client simple-name 3 security_nodes Creates an x25 server security nodes entity which defines a set of rights identifiers associated with calls issued by the X.25 Server module (on behalf of the X.25 Client module at an accessing system) to the X.25 Access module at the gateway system. These rights identifiers are used when making access control checks on the DTE class specified when a call is made. create [node node-id] x25 server security nodes simple-name 2 xot_(OpenVMS_Alpha) Creates the X.25 Over TCP/IP (XOT) module. create [node node-id] xot 3 sap create [node node-id] xot sap sap-name Creates a Service Access Point (SAP) entity which specifies the point at which the XOT entity gains access to the TCP/IP environment for the purposes of listening for inbound XOT connections. The sap-name is a simple name that uniquely identifies a particular SAP instance. By default a XOT SAP is created with the local ip address of 0.0.0.0, which indicates that the SAP will listen on any available IP interface, for example: create xot sap sap-0 enable xot sap sap-0 Or you may choose to create one or more SAP entities to listen on specific IP interfaces, as in: create xot sap sap-0 set xot sap sap-0 - local ip address 123.23.49.235 enable xot sap sap-0 create xot sap sap-1 set xot sap sap-1 - local ip address 123.23.49.236 enable xot sap sap-1 However, if multiple SAP entities are created, then none of them can use the local ip address of 0.0.0.0. 4 link create [node node-id] xot sap sap-name link link-name Creates a 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. To set up a XOT link, you must first create a SAP. A SAP is required so that a number of XOT links can use a single RFC1613 port. Example: create xot sap sap-0 enable xot sap sap-0 create xot sap sap-0 link link-0 set xot sap sap-0 link link-0 - remote ip addr 124.24.256.78 enable xot sap sap-0 link link-0 5 Exception_messages o Already exists The link entity by this name already exists. 4 Exception_messages o Already exists A SAP entity by this name already exists.