We have encountered an unexpected behaviour of a SRVRCONN channel on OS/390.
The channel has a security channel exit applied at the 390 end and at the client end. If the client end security exit returns with MQCXP.ExitResponse set to MQXCC_CLOSE_CHANNEL, then the channel is dropped (as expected) but the channel instance with the IP address of the client and the channel instance with no IP address at the 390 end both go into STOPPED status. This means that any further connection attempts by the client fail (I think with a 2059, but I can't remember for sure - it may have been a 2009 or something else). The only way we were able to resolve this was to delete and redefine the SRVRCONN channel which is not exactly a suitable approach when many clients are connecting to the same SRVRCONN channel. Does anyone have any suggestions as to: a) Whether this is "correct" behaviour? b) Whether there is a way to resolve the STOPPED state without using the delete and redefine? Regards, David C. Partridge Security and MQ Products Manager Primeur Group Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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