Never ran across this error code before but here are various snippets of
what I found under GOOGLE...
MQFB_QUIT
Application should end.
This can be used by a workload scheduling program to control the number of
instances of an application program that are running. Sending an MQMT_REPORT
message with this feedback code to an instance of the application program
indicates to that instance that it should stop processing. However,
adherence to this convention is a matter for the application; it is not
enforced by the queue manager.
An example of a program that could use a feedback code is one that monitors
the work loads of other programs serving a queue. If there is more than one
instance of a program serving a queue, and the number of messages arriving
on the queue no longer justifies this, such a program could send a report
message (with the feedback code MQFB_QUIT) to one of the serving programs to
indicate that the program should terminate its activity. (A monitoring
program could use the MQINQ call to find out how many programs are serving a
queue.)
Applications should check feedback code on MQGETs.
MQSeries enables applications to communicate through the feedback code in
the message descriptor. This code can control applications. However, if
applications do not check the feedback code, then this feature is
unavailable. Applications should, after successfully receiving a message,
fall into a block of code where the message descriptor field FeedBack is
checked. Based on the value of the feedback field, additional processing may
be implemented. Examples include a product shipped MQFB_QUIT to signal to an
application to end gracefully, or perhaps application-defined codes to
enable or disable extra processing such as logging. See the Feedback field
described in Chapter 9, MQMD - Message descriptor for more information.
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Ruzi R
Sent: Tuesday, July 08, 2003 3:48 PM
To: [EMAIL PROTECTED]
Subject: Why Reason Code 256 in DLQ???
Hi all,
Platform is MQ 5.3 CSD3 for NT. I have 2 qmgrs (QM1
and QM2).
I made my target queue ( Q1, a local queue on QM2)
put_inhibited for testing purposes. When I send a
message from QM1 to that queue I expected for the
message to go to DLQ of QM2. And it did, of course :).
I also expected to see 2051 (MQRC_PUT_INHIBITED) in
the reason field of the DLH. But it has 256
(MQFB_QUIT) instead. Why MQFB_QUIT?
Thanks for any input, in advance...
Ruzi
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
___
This message was content-scanned by GatewayDefender
7/8/2003 - 4:59:52 PM - BB0408bfc5.0001.mml
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
