OSI/MHS Management Programming Manual

Introduction to Management Programming for
OSI/MHS
OSI/MHS Management Programming Manual—424824-001
1-13
ENTRY Object
ENTRY Object
The ENTRY object type inquires about OSI/MHS queues where messages may be
pending.
Three types are valid for the ENTRY object: #LINKRETRY, #ROUTERETRY, and
#DEFERRED.
•
#LINKRETRY describes the messages that are delayed for LINK-RETRY-DELAY
as part of the message retry scheme
•
#ROUTERETRY describes the messages that are delayed for time ROUTE-
RETRY-DELAY as part of the message retry scheme
•
#DEFERRED describes the messages that MS APPLs have requested to be deferred
before transmission
Examples of ENTRY object names include $ZMHS.#LINKRETRY,
ZMHS.#ROUTERETRY, and $ZMHS.#DEFERRED.
GATEWAY Object
The GATEWAY object type defines and controls the gateway attached to the OSI/MHS
subsystem. You can configure up to 16 GATEWAY objects for each OSI/MHS
subsystem. They may be of type P1-EXIT or normal. Only one P1-EXIT GATEWAY
object is allowed per OSI/MHS subsystem.
An example of a GATEWAY object name is $ZMHS.#TG.
GROUP Object
The GROUP object type identifies a group of related processes. You can use the
GROUP object to configure, stop, and start related processes. If you issue the START
command to a group, all processes in that group are started. Similarly, if you issue the
STOP command to a group, all processes in that group are stopped.
The GROUP object is in the GI class, the LO class, the MR class, the MS class, or the
RS class. Table 1-1 shows the process objects that each group and class controls.
Table 1-1. Process Objects in Each Group and Class
If the group is in this class...
Then the group controls and configures these
process objects...
GI class Gateway interface process (GIP)
LO class Local operations service (LO) process
MR class Store cleaner (SC) process
Reliable transfer service (RTS) process
Message relay process (MRP)
MS class Message store (MS) process
RS class Remote operations service (RS) process