Line occupied to specify that the rule
All keywords except are optional. Example rule from a rule table of the handler. This rule has, to take three attempts to persistent messages, the due inactivated- and1 calls were queued to the, at their Deliver destination queues. Handler 108 Series for Compaq OpenVMS Alpha, Version5 Release1 System Administration hospital queue management This section begins with a description of keywords for the Pattern Recognition be matched against the messages from the followed by a description of the keywords which determine how the Shouldhandler to process a matching message. This is the that is queue system monitor performed for each message in the, with the defined in this rule pattern matches. DISCARD The message is deleted from the. IGNORE The message remains in the. RETRY Thehandler retried, the message in its destination queue classified. Thehandler forwards the message to the queue continue, specified in the keyword Q.
APPLNAME PutApplNameThis is the name of the application that the- or1 call outputs, as in the field of the message descriptor of PutApplName Message in the indicated. APPLTYPE PutApplTypeThis is the value PutApplType, the message descriptor in the message is specified in hospital queue management DESTQ name of the queueThis is the name of the message queue to which the message addressed is. DESTQM queue manager is the name of the queue manager of the message queue to which the Message is directed. FEEDBACK FeedbackIf the value is set to for MsgType, describes feedback the type of report. It can be used symbolic names. Keywords for hospital queue management Pattern Recognition The keywords for pattern recognition, with which you specify the values, be set off against the messages from the, are hereinafter described. All key for pattern recognition are optional. APPLAT ApplentityDataThis is the value ApplentityData, the message descriptor of the Message is specified in the.
Customer Queuing Systems
You can, for example, use the symbolic name FBCOA to those messages to entity in the, for a confirmation of receipt in their Destination queue is requested. FORMAT FormatThis is the name that the sender of the message to describe the format the message data. MSGTYPE messageThis is the message type of the message in the. It can be used symbolic names. You can, for example, use the symbolic name MTREQUEST to those messages to entity in the, are required for the answers. Handler Chapter 8. Series queue handler for deliverable messages 109 PERSIST permanenceThis is the value for the permanence of the message.
The permanence of a Message specifies whether the message received at restart of the queue manager remains. It can be used symbolic names. You can, for example, use the symbolic name PERPERSISTENT to those To entity objects in the which are permanent. REASON codeThis is the reason code that describes why hospital queue management the message in thetas queued. It can be used symbolic names. You can, for example, use the symbolic name RCQFULL to those messages entity that were queued to the because their destination queues were full.
This is an intro
REPLYQ name of the queueThis is the name of the queue to answer messages, the is specified in the message descriptor of the message in the. REPLYQM queue manager nameThis is the name of the queue manager of the hospital queue management queue to be answered News, the message descriptor in the message in this specified. USER userThis is the user of the user who sent the message in thetas, as in the message specified. Keywords Thekeywords that allow you to specify how a matching Message is to be processed, are described.