RE: ODBC/QZDASOINIT Messages -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: ODBC/QZDASOINIT Messages
From: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
Date: Fri, 2 Mar 2007 14:05:35 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I'm hoping that changing the msgq delivery to *BREAK will force the

msgw. 

But as far as the System I is concerned, it's not stalled. So there's no
error to report, hence, no MSGW. You need the PC side to report the hang
to the System I if you want to see it there.

-Walden

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: ODBC/QZDASOINIT Messages , fbocch2595
RE: ODBC/QZDASOINIT Messages , Gary Monnier

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.