It's odd that server folk are less vigilant than the mainframe folk. You'd think the maintainers of the less reliable and proven platform would *more* vigilant if anything, but I guess one can never tell.
But back to the point... do they have channel triggering configured correctly? I've encountered a few situations where it hasn't been, and channels have timed out, never to be automatically restarted. Ian -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Larry Murray Sent: Tuesday, 18 November 2003 10:35 To: [EMAIL PROTECTED] Subject: arrival time of last message Good evening folks...... We are having an issue with some servers that send messages to MQ on the mainframe. MQ, as always, is working perfectly....but evey now and then one of the servers just stops sending messages. The server folks are less vigilant than the mainframe guys. Usually we see that a server is no longer sending messages beause because the CICS transactions triggered as a result of the arrival of a message stops. So..........I am looking for a method that I can employ to query MQ as to the last time a message arrived on a queue. The messages are not persistent. When CICS executes the triggered transaction, the message goes away. Is there a time stamp some placein the queue stats that a program can access that will give a dte/time stamp of the last message that hit the queue? Thanks...Larry Larry Murray Putnam Investments Tech Services 1-617-760-3270 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 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
