We have an application running uner COM-PLETE for Natural / Adabas. On occasion something (abend) is happening and the application which was connected to MQ is no longer connected, however the queue the application was reading from is still left in an open state. MQ says the queue is still open from COM-PLETE, however when we look in COM-PLETE no connections exist. So MQ thinks COM-PLETE is connected, but it really isn't. So now nothing will trigger the queue because it is open for input. The only way to get rid of the connection is to bounce the queue manager. Bouncing COM-PLETE doesn't work because COM-PLETE doesn't think he is connected. So I have two questions, is there anyway in MQ for Z/OS to kill a specific thread that is open (any non published commands). Or is there a way to determine what the handle is, then try to write a program to use that handle and then close it and disconnect it?
Thanks, Gary =================== Gary Klos Online Systems - PSC United States Steel Corporation 412-433-1225 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
