Joined: 17 Jan 2006 Posts: 28 Location: Montreal Canada
PROBLEM SOLVED!!
Before I explain please note that I did not send messages directly to the TXQ but throught a remote queue and we do have a DEADQ designated.
After much frustration I got the z/OS Sys Admins to start/stop the receiver end of the channel. Coincidentally I start a 2nd channel initiator. Unfortunately I didn't do a test betweent the 2 changes to see which one resolved the issue. A little asleep at the switch I guess. However my z/OS compatriots claim the receiver channel start/stop was tried earlier to no avail. I am somewhat convinced that the receiver channel was still holding on to a process thread and wouldn't release it. I recall this being a classic problem. It this was not the case then the original channel initiator was up the snuff. Anyway, the channel is now starting automatically.
I most appreciate all the timely input from all of you. Without that input I would still be chasing ghosts. Cheers, BB. _________________ Software Specialist
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum