show [node node-id] session control -
application object-name-or-object-number attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
You can identify an application with an object name or an object
number. Usually, applications are identified by network object
number 0, but you can optionally assign it a nonzero object number,
in the range from 128 to 255. A nonzero object number can be
specified without an application name. Object numbers 1 through
127 are reserved for use by HP. Specific network services
are identified by nonzero object numbers; for example, 27
represents the mail utility.
Examples:
show session control application * name, addresses
show session control application 26 all
1 – Characteristics
o addresses
Default: Empty set Value: Set of end-user specifications
A set of end-user specifications, any one of which, when
specified in the destination name field of an incoming connection
request, causes applications defined by this entity to be
invoked.
An end-user specification can be either a name or a number.
Usually, applications are identified by network object
number 0, but you can optionally assign it a nonzero object number,
in the range from 128 to 255. A nonzero object number can be
specified without an application name. Object numbers 1 through
127 are reserved for use by HP. Specific network services
are identified by nonzero object numbers; for example, 27
represents the mail utility.
For example, the task application uses the address set {name=task},
and the mail application uses the address set {number=27}.
o accept mode (Tru64 UNIX)
Default: Immediate Value: Immediate or deferred
If accept mode is immediate, then session control will
automatically accept the connection before activating the
end user. If accept mode is deferred, then it is up to the
program to accept or reject the connection.
o allow decnet-internet gateway access (Tru64 UNIX)
Default: False Value: True or false
If true, this application supports gateway access. If the user
name supplied by the incoming connect request contains a @ or
!, the application spawner starts up the application under the
session control DECnet-Internet Gateway user.
o client
Data type: Entity name
Identifies the name of the local user that will be activated
upon receipt of a connect request containing a destination name
matching one of the values in the destination names attribute.
o data abstraction (Tru64 UNIX)
Default: Message Value: Message or stream
Type of data transfer interface the application will be using;
message type or stream type. The message data abstraction is
identical to the Sequenced-packet socket concept of the Phase IV
session control. When writing applications, you should use the
same data abstraction as that used by the program to which you
connect.
Table Data Abstraction Type Comparison compares Message and
Stream data abstractions.
Table 1-1 Data Abstraction Type Comparison
Message Type Stream Type
Preserves message Does not preserve message boundaries
boundaries
HP DECnet-Plus Commonly used for Tru64 UNIX applications
for OpenVMS default
abstraction
Not available on Available on TCP/IP
TCP/IP
Supported by XTI Supported by XTI
o image name
Default: No image name Value: File specification
File name of a program to be invoked upon receipt of a connection
request containing an address that matches one of the values
contained in the set described by the addresses characteristic.
o incoming alias (Tru64 UNIX)
Specifies how a particular application responds to incoming
connect requests directed to the alias node address. If False,
the application does not allow a specified application to receive
incoming connect requests that have been directed to the alias
node address.
o incoming osi tsel (OpenVMS)
Default: none Value: hex-string
A TSEL is a string of hex digits, the length of that string should
be an even number between 2 and 64, inclusive.
The TSEL this image will accept connections for. This is similar
to the destination names attribute. However, applications using
this access point for in-connection matching do not use DNA
Session Control protocol.
o incoming proxy
Default: True Value: True or false
Specifies whether to honor incoming proxy requests. If this
attribute is set to false, requests to invoke proxies on
incoming requests are ignored. The setting of this characteristic
overrides the setting of the session control incoming proxy
characteristic for the specified application.
o maximum instances (Tru64 UNIX)
Default: 0
Maximum number of simultaneous instances of this application
allowed. If a connect request comes in for this application
while the maximum number of instances exist, the connect request
will be rejected with ObjectTooBusy. A value of 0 indicates no
maximum.
o network priority (OpenVMS)
Default: 0 Value: 0-255
When operating over CLNS, indicates network priority encoded in
NPDU header for all transmitted packets. It may be used by
intermediate systems to assign the packets to queues of appropriate
priority.
o node synonym
Default: False Value: True or false
Default form in which the remote node name is passed to the
application.
false The full node name is used.
true The node synonym is used; if no synonym is available, the
full name is used.
o outgoing alias (OpenVMS)
Default: True Value: True or false
Specifies whether a particular object uses the alias node
identifier in its outgoing connect requests. If false,
the specified object is not allowed to use the alias node
address in its outgoing connect requests.
o outgoingalias name (OpenVMS)
Default: None Value: fullname
Specifies which alias name a particular object uses in its
outgoing connect requests when multiple aliases are in use.
If you do not set an application outgoingalias name and the
application has the outgoing alias set to true, the alias
name for which you set the alias port outgoing default true
is used for outgoing connect requests.
If you define application outgoingalias name, this supersedes
the setting of alias port outgoing default. So if the
application outgoing alias attribute is then set to false to
disable the application outgoingalias name, the local node
name is used.
If neither alias port going default nor application
outgoingalias name is set, the first alias created is used as
the default for the system. If this alias is not enabled,
the local node name is used.
o outgoing proxy (OpenVMS)
Default: True Value: True or false
Default action to execute when user does not explicitly
specify whether or not to invoke a proxy.
o programming interface (Tru64 UNIX)
Default: Phase IV Value: Phase IV or Phase V
Programming interface used by the DECnet application (socket
interface).
o user name
Default: None Data type: Latin1String
Identifies the default account under which the application is to
run. For OpenVMS, if null then system defaults are used to select
the user.
2 – Counters
o access control violations (Tru64 UNIX)
Number of connect requests for this application entity for which
access could not be granted.
o creation time
Time the entity was created.
o resource failures (Tru64 UNIX)
Number of times a connect request for this application was
rejected due to a resource failure. Resource failures include
ObjectTooBusy (for example, due to Maximum Instances reached)
and File is nonexistent or not executable.
o total invocations (Tru64 UNIX)
Number of instances of this application entity that have been
invoked.
3 – Identifier
o name
Simple name assigned to the application when it is created.
4 – Status
o active instances (Tru64 UNIX)
Number of active instances of this application that are currently
running.
o last request (Tru64 UNIX)
Time the last connect request for this application was received.
o process identifiers (Tru64 UNIX)
Specifies a set of processes that are active instances of the
specified application.
o uid
UID allocated upon creation of this application subentity
instance.