Re: SQL Code 0842, SQL State 8002 -- MIDRANGE-L

Subject: Re: SQL Code 0842, SQL State 8002
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Wed, 22 Oct 2014 09:33:34 -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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 22-Oct-2014 08:44 -0500, Michael Ryan wrote:

<<SNIP>> I believe that I need to try my CONNECT TO <remoteRDB>, and
if I receive a -0842 SQL code as a result, use the SET CONNECTION
<remoteRDB> statement. Is that correct?

That is probably the most likely scenario, as a reflection of the most likely coding and [probably static] RDB configuration. IIRC, that is always what my code did. However I can imagine code that might not do that, for example if the code is just acquiring several connections, perhaps even some that may already exist, but connections for which the actual SET CONNECTION is postponed until needed; in that scenario the -842 can be viewed as merely an FYI, so effectively just ignored.

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.