Select application for the add command that modifies the addresses
of a session control application.
Select proxy for the add commands that modify the application
and source end users attributes of a session control proxy.
1 – application
Modifies the Addresses attribute of the specified Session Control
Application instance to include at least the specified object name(s)
and/or number(s).
add [node node-id] session control -
application application-name -
addresses {object-name-or-number[,object-name-or-number...]}
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.
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:
add session control application mail addresses {number=27}
add session control application task addresses {name=task}
2 – proxy (Tru64 UNIX)
The add command can be used to modify the following attributes
of a session control proxy: application, or source end users.
2.1 – application
add [node node-id] session control proxy name -
application {simplename[,simplename...]}
Application
Default: None Value: Set of simple-name
Set of application identifiers, one of which must match the
application requested. If this attribute value is null, any
requested application will match.
2.2 – source_end_users
add [node node-id] session control proxy name -
source end users {record[,record...]}
Source End Users
Default: None Value: Set of record
Set of remote end users for whom this proxy entry applies. An
unspecified end user implies all end users on the node specified
in the same record. The record format has two fields: node which
has a data type of fullname, and end user which has a data type
of enduserspecification.