Re: Problem with ODBC connection. -- 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: Problem with ODBC connection.
From: rob@xxxxxxxxx
Date: Tue, 10 Jan 2006 09:24:46 -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>

The following link shows that 42977 pretty much matches the "User XYZ..." 
message
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzatd/rzatdfinder.htm

However it did show me that sql state 42977 is the same as sql code 7022. 
Which can be found by 
DSPMSGD RANGE(SQL7022) MSGF(QSQLMSG)

Now, knowing how IBM loves to obfuscate, if you search for MSGSQL7022 at
http://www-912.ibm.com/a_dir/as4ptf.nsf/as4ptfhome
you'll find about a bazillion ptf's for this message for V5R2.  Good luck.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

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.