This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
So, in configuring a Maximo install to use JMS queues, we ran into a weird configuration step.
In the 7.6 Install guide for Websphere, page 67, step 10a, you are directed to assign as the destination for CQINERRBD... CQINERRBD!
Does that make sense to anyone? Wouldn't this lead to a loop?
-C
The manual set-up steps have been like that for a long time and does lead to messages being processed over and over until the queue fills up.
I have never agreed with that approach but rather used the logic if the transaction failed five times on cqin queue and then a further five times on cqinerr queue (with a 30 second mdbdelay) the chances are, it would never succeed. I always set the error destination for CQINERRBD to NONE.
Jim
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: 14 October 2016 18:37
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] CQINERR?
So, in configuring a Maximo install to use JMS queues, we ran into a weird configuration step.
In the 7.6 Install guide for Websphere, page 67, step 10a, you are directed to assign as the destination for CQINERRBD... CQINERRBD!
Does that make sense to anyone? Wouldn't this lead to a loop?
-C
As Jim says the standard advice will create a loop.
Jim and I have discussed this offline before and the best solution is as Jim says to set this to NONE and be vigilant about handling messages that have failed.
When I have queried the standard advice with IBM staff it is clear that they are working on the assumption that every message will go through if it is submitted enough times...
There are some cases where that works e.g. GL accounts arriving before the GL account components, but in those cases the interface design often hasn't considered timing e.g. the need for GL account components to be submitted first or read more frequently.
Unfortunately there are real world situations where this isn't the case e.g. someone submits workorder related records after a workorder has been closed by someone else.
Those messages will never get automatically processed.
I see this every so often with the customers I support.
best regards,
Mark
Thank you both, this does clarify the IBM rationale for us, as well as validate what we've heard elsewhere.
-C