We have an NT to MVS and MVS to NT channel receiver and channel sender on our MVS queue manager. The sender is defined as a connection via LU6.2. Recently we have had the line get dropped and the MVS log displays that the sender has LU6.2 connection problems and the channel goes into abnormal termination. Nothing unusually with this.
Our problem is reestablishing this connection. When the physical line is repaired, the Administrator claims he has to recycle the Queue Manager for the LU6.2 connection to work. I know for the TCP connections that are defined, we just "stop and start" the channel (usually on both sides) and we are successful. But I am not sure why the Administrator claims lack of success with the "stop and start". I want to point out that we are still running 1.2 on MVS and that is why the manual "stop and starts" for the TCP connections (Eventually we will get into the 21st century). Is there a reason why a channel "stop and start" for the LU6.2 doesn't work the same? Do we really have to bring down the Queue Manager to get it to function? TIA Walt Childson 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
