I know of the "Unsupported Client" for MQ Series.  So far is sounds like
this is vulnerable to any networked or system problems between the 3K and
the system with the "Running" Queue Manager.

I insist on a Sore and Forward solution that regardless of network problems
(internal to the 3K in NS or the remote MQ server or the LAN) the submission
of a message will not fail and kill the sending program.

At this point, I am still going to require I build a Store and Forward front
end on the 3K.

To my point of view, that's as unsupported as it gets.

I'm not wild about having to learn how to make NT or UX systems as reliable
as a 3K, but it looks like that's what I'll have to do, directly or
indirectly.

I will NOT continue to depend on HP's NRJE/SNA implementation if there is
any way around it.  MQ and U.S. Customs are now providing an option.  One
way or the other I WILL dump NRJE.  There are other business reasons
compelling this change as well, but they pale in my mind to the problems we
have with NRJE.

That aside, I still can't stand that there are parts of the OS still in
classic mode, specially parts of the file system.  Circular flies
specifically are incredibly useful.  They are so painfully slow I can't
stand it.  If I copy them to a non-circular file (pegging the CPU with
classic FCOPY and Circular file access), and search the non-circular file,
the search part is blindingly fast.

<end rant>