Re: SQL Connection Issue -- 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.

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 09/12/2017
02:23:46 PM:

<Dave>
... is there a different way that I
can assure that I am connected to the local database in our standard SQL

error utility in lieu of issuing the CONNECT RESET statement?
</Dave>

Why not running the log Utility in a named ACTGRP of its own?

OK, I've now tried that (and even commented out the CONNECT RESET
statement), but I'm still seeing the following error messages -- but at
least it is a different state code. I also ran it through debug and
confirmed that our standard SQL error utility program is running in its
own named activation group. This is failing on the first prepare of an
INSERT statement for the local database. So, it is pretty strange that
the state code says, "The CONNECT statement is invalid, because the
process is not in the connectable state." Now what?

SQL0900 Application process not in a connected state.
SQL0752 Connection cannot be changed. Reason code is 5.
SQL0003 An SQL prepare failed; state = 0A001

Sincerely,

Dave Clark

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.