![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Figure 19-1 shows the hierarchical relationship of the entities that make up the OSAK module.
Figure 19-1 Hierarchy of OSAK Module Entities
delete
Deletes an osak entity and reclaims the resources associated with it. The entity must be in the NotAvailable state before it can be deleted.disable
Puts the osak entity in the NotAvailable state in which it does not accept any more inbound or outbound association requests, and existing associations are aborted. If the osak entity is already in the NotAvailable state, the command has no effect.enable
Starts operation of the services provided by the osak entity. If the osak entity is already operational, the command has no effect. On completion of the command, the state of the entity is operational. You should not issue this command when the osak entity is in the shutting state.
disconnect timer (OpenVMS)
Length of time that the OSAK software waits when it expects the remote peer to disconnect a transport connection. If the timer expires and the remote peer has not disconnected the connection, the OSAK software disconnects the connection. You can modify this attribute using the set command.
Default: 30 seconds Value: Time in seconds protocol versions
Specifies the ACSE, presentation and session protocol versions being used by the osak entity.
Default: {ACSE = {1}, presentation = {1}, session = {1,2} } Value: Set of protocol versions The full range of possible sets of values is:
- {ACSE = {1}, presentation = {1}, session = {1,2} }
- {ACSE = {1}, presentation = {1}, session = {1} }
- {ACSE = {1}, presentation = {1}, session = {2} }
You cannot modify this attribute.
aborts received
Number of aborts received by this osak entity since its creation.aborts sent
Number of aborts sent by this osak entity since its creation.connects accepted
Number of connection requests accepted by this osak entity since its creation.connects initiated
Number of connection requests initiated by this osak entity since its creation.connects rejected
Number of connection requests rejected by this osak entity since its creation.creation time
Time at which the osak entity was created, in binary absolute time format.releases received
Number of release requests received by this osak entity since its creation.releases sent
Number of release requests sent by this osak entity since its creation.unknown ae-titles
Number of connection requests received that contain an unknown application-entity title. This counter is incremented each time an unknown ae-title event occurs.unknown invocations
Number of connection requests received that contain an unknown invocation identifier. This counter is incremented each time an unknown invocations event occurs.unknown paddresses
Number of connection requests received that contain an unknown presentation address. This counter is incremented each time an unknown paddress event occurs.
state
State of the osak entity. The value is one of the following:
noinbound osak entity cannot receive inbound association requests notavailable osak entity is not available operational osak entity is enabled and operational shutting osak entity is shutting down uid
Entity's unique identifier, which is generated when the entity is created.
unknown ae title
Generated when an inbound association request specifies an unknown application-entity title. Increments the unknown ae-titles counter.Arguments:
ae title The unknown application entity title. unknown invocation
Generated when an inbound association request specifies an unknown application-process invocation identifier or an unknown application-entity invocation identifier. Increments the unknown invocations counter.Arguments:
invocation The unknown application-process or application-entity invocation identifier. unknown paddress
Generated when an inbound association request specifies an unknown presentation address. Increments the unknown paddresses counter.Arguments:
paddress The unknown presentation address.
For create:
entity exists
An osak entity already exists.For delete and enable:
sub entity exists
Cannot delete while subentities exist.wrong state
The osak entity is in the wrong state for the command you have tried to use on it. The text accompanying the exception message specifies which command has failed. For Digital UNIX, the only possible wrong state is NotAvailable.
For OpenVMS, an osak application entity has zero or more application-entity invocations, each represented by an osak application invocation entity (see Section 19.3). In addition to recording information about the name and address of an application, it also records information that controls the way in which inbound association requests for that application are handled by the OSAK software.
For OpenVMS, you should create an osak application and an
osak application invocation for each passive application that
you want to run, identifying the application by its presentation
address. Also, an osak application entity is created
automatically for an active application and deleted at the end of the
connection.
create [node node-id] osak application
"presentation address"
(OpenVMS)
delete [node node-id] osak application
"presentation address"
(OpenVMS)
show [node node-id] osak application
"presentation address" [all [attributes] | all characteristics
| all counters | all identifiers | all status ]
ae titles
The application-entity titles that map to this application's presentation address in Form 2 (object identifier) format. If the application entity titles are in Form 1 (directory name) format, they are not displayed. A null object identifier is displayed instead (ObjectIdentifier= "").
Default: None Value: See description startup policy
Defines the startup policy for invocations of this application. For Digital UNIX, the value is always existing. This indicates that a listener process must exist for an inbound connection to be processed. No new process is started up when an inbound connection arrives.
Default: Existing Value: New or existing For OpenVMS, the value is one of the following:
new Indicates that, when no process is available to handle an inbound connection, a new process is started up. existing Indicates that one process handles all inbound connections. No new process is started up if the existing process is busy when an inbound connection arrives. For OpenVMS, you can modify this attribute using the set command.
template
The transport template used for inbound association requests. For OpenVMS, you can modify this attribute using the set command.
Default: Default OSI transport template Value: See description
creation time
The time at which the application is created.invalid mode failure
The number of times an inbound connection request is rejected because of a mismatch of modes. This counter is incremented each time an invalid mode event occurs.The possible modes are normal and X.410-1984. An application is running in normal mode if it uses the upper layers of the OSI stack. An application is running in X.410-1984 mode if it does not use the upper layers of the OSI stack.
resource failures
The number of times an inbound connection request was rejected due to insufficient system resources.total invocations
The number of times this application has been invoked.
paddress
The presentation address of this OSAK application.
active invocations
The number of existing invocations of this application.uid
Entity's unique identifier, which is generated when the entity is created.
invalid mode
Generated when an inbound connection request is rejected due to a mismatch of modes. Increments the invalid mode failures counter.
For delete:
wrong state
Disable the osak application before trying to delete it.
For Digital UNIX, an osak application invocation entity is created each time an OSI application that is running over the OSAK software opens an initiator or a responder. You can use only the show command with the osak application invocation entity on Digital UNIX systems, and you cannot modify any of the attributes.
For OpenVMS, an osak application invocation entity can be created in two ways:
The create command creates a passive application,
which becomes active only when your OpenVMS system receives an OSI call
for that particular application invocation.
create [node node-id] osak application
"presentation address" invocation "invocation
identifier"
(OpenVMS)
delete [node node-id] osak application
"presentation address" invocation "invocation
identifier"
(OpenVMS)
show [node node-id] osak application
"presentation address" invocation "invocation
identifier" [all [attributes] | all characteristics (OpenVMS) |
all counters | all identifiers | all status ]
startup information
Invocation startup information that is system-specific. This information is needed only for passive applications.You can modify the startup information attribute using the set command. You can specify the items in any order. Note that when you modify this attribute, any item for which you do not specify a value is set to its default, not to its previous value. For example, you could set up non-default values for all four items in this attribute using the following NCL command:
set [node "node-id"] osak application "presentation address" invocation "invocation identifier" startup policy "password=password, username=username, file=file name, sversion=sversion"If you then decide to change the value of the password, but to keep the non-default values of the other items, you should use the following command:
set [node "node-id"] osak application "presentation address" invocation "invocation identifier" startup policy "password=new password, username=username file=file name, sversion=sversion"Refer to the following table for specific startup information: .
Item Value Description Mandatory user name The user name of the process that will respond to connect requests received by this application. file pathname The name of the file to run to start up the named application. The file is a command file or an executable image that is run each time a passive process starts. Digital recommends that you use a command file for this purpose. Optional account name The account that is to start the process. max resp integer The highest permissible number of responders, for an application with the new setting for startup policy password password The user's password. sversion {1}, {2}, or {1,2} The session version.
creation time
Time at which this invocation was registered with OSAK.total associations
Number of associations set up to this invocation.
ids
The identifier of the invocation. For OpenVMS, you cannot modify this attribute.
port list
A list of the OSAK ports referenced by this application invocation entity.state
The state of the application invocation entity. For Digital UNIX, the value is always active.For OpenVMS, the value is one of the following:
active An active application invocation is using an active process. passive A passive application invocation is waiting for inbound connection requests on its presentation address. uid
Entity's unique identifier, which is generated when the entity is created.
For delete:
wrong state
You cannot delete an osak application invocation entity when it still has open ports.
You can use only the show command with the osak port
entity. You cannot modify any of the attributes.
show [node node-id] osak port
"port_identifier" [all [attributes] | all characteristics |
all counters | all identifiers | all status ]
template
The name of the transport template used when establishing an association.
Default: Default OSI transport template Value: See description
creation time
Time at which the association was set up, in binary absolute time format.
name
Simple name assigned to the port when it is created.
application context
Name of the application context for this association.connection state
Specifies the state of an association. This status attribute can have one of the following values:
awaiting_associate_confirm A port entity is in this state when waiting for confirmation of an association from a remote peer entity. awaiting_associate_response A port entity is in this state when waiting for a response from the user application to an association request. awaiting_inbound_connection A port entity is in this state when waiting for an association indication from a remote peer entity. awaiting_redirection A port entity is in this state when an application has opened a new port to which the association is to be redirected. connected A port entity is in this state when an association is set up and data exchange is taking place. not_connected A port entity is in this state either after the port is opened but before an association request is received from a remote peer entity, or after an association is closed down but before the port is closed. disconnected A port entity is in this state when the local application has sent a request to release the association, but the remote peer entity has not sent a response. redirected A port entity is in this state after an association has been redirected to another process. direction
Specifies whether an association is inbound (the port was opened by a responder) or outbound (the port was opened by an initiator).invocation
UID of the invocation that opened this port.local ae title
Local application-entity title in Form 2 (object identifier) format. If the local ae title is in Form 1 (directory name) format, it is not displayed. A null object identifier is displayed instead (ObjectIdentifier= "").local ae invocation id
Local application-entity invocation identifier.local ap invocation id
Local application-process invocation identifier.local paddress
Local presentation address.owner id
Process id of the OSAK application.remote ae title
Remote application-entity title in Form 2 (object identifier) format. If the remote ae title is in Form 1 (directory name) format, it is not dosplayed. A null object identifier is displayed instead (ObjectIdentifier= "").remote ae invocation id
Remote application-entity invocation identifier.remote ap invocation id
Remote application-process invocation identifier.remote paddress
Remote presentation address.uid
Entity's unique identifier, which is generated when the entity is created.
This chapter describes all of the commands you can use to manage the entities that constitute the OSI transport module. This module implements the OSI Connection-Oriented Transport Protocol specification (International Standard ISO 8073); and for Digital UNIX, the Connectionless-Mode Transport Service Protocol (International Standard ISO 8602). These protocols implement the OSI Reference Model Transport layer 4. For OpenVMS, this module also implements RFC 1006 and RFC 1859. These protocols, as well as the NSP protocol, implement the transport protocols in the Digital Network Architecture (DNA).
Figure 20-1 shows the hierarchical relationship of the entities that constitute the OSI transport module.
Figure 20-1 Hierarchy of OSI Transport Module Entities
The following sections further describe the OSI transport protocol and OSI transport service. For more information, refer to the DECnet-Plus for OpenVMS Introduction and User's Guide.
The OSI transport protocol permits communication between DECnet-Plus systems and other vendors' systems that also implement the OSI transport protocol.
The OSI transport protocol conforms to the ISO 8072 Service Definition and the ISO 8073 Protocol Standard. They define OSI transport protocol classes 0, 2 and 4 (TP 0, TP 2, and TP 4).
This protocol can use two types of ISO Network service:
The OSI transport conforms to the RFC 1006 Standard and to the RFC 1859. They define how to implement ISO 8073 Transport Class 0 on top of TCP (RFC 1006) and how to implement ISO 8073 Transport Class 2 Non-Use of Explicit Flow Control on top of TCP (RFC 1859). RFC 1006 and RFC 1859 use a CONS connection over TCP to provide network service.
Table 20-1 describes these classes, their functions, and which network service can be used.
| Protocol Class | Functions | Network Service |
|---|---|---|
| TP 0 | Provides a basic transport service. | CONS and RFC 1006 |
| TP 2 | Provides all functions of TP 0. Provides multiplexing of more than one transport connection over a network connection or TCP connection. Provides flow control over CONS. | CONS and RFC 1859 |
| TP 4 | Provides all functions of TP 2. Provides error detection and recovery. | CONS and CLNS |
Some other differences are that:
When a transport user sets up a transport connection, a preferred protocol class for the connection is specified in the connection request. The responding transport user must either agree to this protocol class, or suggest an alternative protocol class that is acceptable to the initiating user. If no such agreement is possible, the transport connection cannot be set up.
An OSI transport connection is an end-to-end connection. It is a reliable two-way, data-transfer path between two OSI transport users. An OSI transport connection has three phases:
You can set up OSI transport connections:
NCL_PROFILE_017.HTML OSSG Documentation 2-DEC-1996 12:48:15.05
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.