05 Base Camper

Nonstop IRMQSCOL

Is the a way to limit the interval of of the IRMQSCOL . To prevent a request Less than one minute

Tags (2)
2 REPLIES 2

Re: Nonstop IRMQSCOL

Hi Garey, not that I am initially aware off the top of my head or doing some quick looking around. 

 

Can you describe the problem you are seeing and which Prognosis version and maybe there is another way we can tackle it?

 

I am sure you are aware fo these paramemters already in the configuration but none of these will have the exact result you are looking for.

 

MAXQMGR
Maximum number of queue manager instances, default = 1.

MAXQUEUE
Maximum number of queue instances to collect data on per interval, default = 100.

MAXMSG
Maximum number of message instances to collect data on per interval, default = 1000.

MAXCHAN
Maximum number of channel instances to collect data on per interval, default = 50.

MAXPROC
Maximum number of WebSphere MQ processes to collect data on per interval, default = 20.

MSGTIME
Maximum message wait time in seconds, default = 5. The default value should be accepted unless the MQ Server is extremely heavily loaded and 15603 Prognosis errors are occurring.

CMDTIME
Maximum time to wait on a reply queue message in seconds, default = 30.


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Sr. Services Solution Engineer, Payments & Infrastructure – MSci. PA, CISSP, ITIL.
Tags (1)
05 Base Camper

Re: Nonstop IRMQSCOL

It tured out to not bed a Prognosis issue but a MQ issue . Prognosis was only aggravating the issue.

Blog: What Optimal Transaction Performance Means

A number of our customers use Prognosis to monitor the health of their payment systems. As part of this, they monitor the transactions flowing through the system ...

Read blog
Top Liked Members