show [node node-id] osak -
application "presentation address" attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
Example:
show osak application *
show osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" all
show osak application * paddress, ae titles, template
1 – Characteristics
o ae titles
Default: None Value: See description
The application entity titles that map to this application's
presentation address.
o startup policy
Default: Existing Value: New or existing
Defines the startup policy for invocations of this application.
For Tru64 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.
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.
o template
Default: Default OSI Value: See description
transport template
The transport template used for inbound association requests.
For OpenVMS, you can modify this attribute using the
set command.
2 – Counters
o creation time
The time at which the application is created.
o invalid mode failure
The number of times that 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.
o resource failures
The number of times that an inbound connection request was
rejected due to insufficient system resources.
o total invocations
The number of times this application has been invoked.
3 – Identifier
o paddress
The presentation address of this OSAK application.
4 – Status
o active invocations
The number of existing invocations of this application.
o uid
Entity's unique identifier, which is generated when the entity is
created.
5 – invocation
show [node node-id] osak -
application "presentation address" -
invocation invocation-identifier attribute [,attribute...]
all [attributes]
all char (OpenVMS)
all counters
all identifiers
all status
Examples:
show osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" -
invocation * all
5.1 – Characteristic (OpenVMS)
o startup information
Invocation startup information that is system-specific. This
information is needed only for passive applications.
Refer to the following table for specific startup information:
Mandatory
Item Value Description
---------------------------------------------------------------
user name The username 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. HP
recommends that you use a command file for
this purpose.
Optional
Item Value Description
---------------------------------------------------------------
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}, The session version.
{2}, or
{1,2}
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"
5.2 – Counters
o creation time
Time at which this invocation was registered with OSAK.
o total associations
Number of associations set up to this invocation.
5.3 – Identifier
o ids
The identifier of the invocation. For OpenVMS, you cannot modify
this attribute.
5.4 – Status
o port list
A list of the OSAK ports referenced by this application
invocation entity.
o state
The state of the application invocation entity. For Tru64 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.
o uid
Entity's unique identifier, which is generated when the
entity is created.