OSI/MHS Management Programming Manual

Common Definitions
OSI/MHS Management Programming Manual424824-001
4-6
Object Format
single object; LISTOBJECTS accepts either a single object name or an object-name
template (wildcard name) that specifies a set of objects. This token is required in all
OSI/MHS commands except GETVERSION and LISTOBJECTS. Most OSI/MHS
commands allow multiple occurrences of this token, so that a single command can
operate on several objects.
In responses, one ZCOM-TKN-OBJNAME token is returned for each object about
which the command is to return information.
ZCOM-TKN-OBJTYPE
is a token returned in responses to identify the object type of one or more
ZCOM-TKN-OBJNAME tokens. Each command lists the values that can be
assigned to ZCOM-TKN-OBJTYPE for that command.
Object Format
The object types that OSI/MHS supports are listed in Table 4-11, along with the object
name format for each type. The syntax of the name format is described in detail below
the table, followed by a definition of each object.
psystem
is a valid node name. It is the name of the node in which the MHS manager resides.
Table 4-11. OSI/MHS Object Types and Name Formats
Object Type Name Format
APPL [ \psystem. ]$proc.#applname
CLASS [ \psystem. ]$proc.#class
CUG [ \psystem. ]$proc.#cug
CUGMEMBER [ \psystem. ]$proc.#cug.cugmember
DLIST [ \psystem. ]$proc.#dlist
DLISTMEMBER [ \psystem. ]$proc.#dlist.dlistmember
ENTRY [ \psystem. ]$proc.#entry
GATEWAY [ \psystem. ]$proc.#gateway
GROUP [ \psystem. ]$proc.#class.[\gsystem.]group
MON [ \psystem. ]$proc
MTA [ \psystem. ]$proc.#mta
null [ \psystem. ]$proc
PROCESS [ \psystem. ]$proc.#[\gsystem.]pname
ROUTE [ \psystem. ]$proc.#mta.route
SUBSYS [ \psystem. ]$proc.#subsys