OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-44
ENTRY Objects
manager-process
is the name you have given the MHS manager process (the MON object). This
name must be a letter followed by zero through three alphanumeric characters.
entry
is the name that distinguishes this ENTRY object from all the other objects in this
OSI/MHS subsystem, and in particular from the other ENTRY objects. The
distinguishing names for the ENTRY objects are:
DEFERRED for the deferred message queue
LINKRETRY for the link-retry message queue
ROUTERETRY for the route-retry message queue
For example, if your MHS manager process is called $MHS1, you can use the object
name $MHS1.#LINKRETRY to inquire about the link-retry message queue of this
OSI/MHS subsystem.
SCF Commands for ENTRY Objects
You can direct either of the following SCF commands to the OSI/MHS ENTRY object
specified or assumed in the command. These commands are nonsensitive.
Example of Commands for ENTRY Objects
This example illustrates how you use the nonsensitive STATUS command to obtain
information about an OSI/MHS delayed-message queue:
STATUS ENTRY $ZMHS.#LINKRETRY
STATUS ENTRY $ZMHS.#LINKRETRY, DETAIL
NAMES Displays the names of the ENTRY objects in an OSI/MHS subsystem.
The qualifying names at the ENTRY level are always DEFERRED,
LINKRETRY, and ROUTERETRY.
The NAMES command can include the SUB option, but the option has no
effect.
STATUS Displays the status of the queue represented by the specified ENTRY
object. For each message on the queue, STATUS displays:
•
The PDU (protocol data unit) ID of the message
•
The time the next action will be taken on the message (for instance,
when the next attempt to establish a link will be)
•
The time when the PDU entered the subsystem (from a UA or an
adjacent MTA)
•
The transmission priority of the message