|
Replacing the CREATE OR REPLACE TABLE with DROP TABLE & CREATE TABLE did
the trick. I have to assume that some of the secret sauce in the OR
REPLACE was the culprit. C'est la vie!
Thanks, everyone!
date: Mon, 11 Nov 2024 13:05:57 -0600--
from: Justin Taylor <jtaylor.0ab@xxxxxxxxx>
subject: Re: What causes "Database connection started" (CPF9160)
I do not, but the *PGM that calls my *PGM does a CREATE ALIAS.
I've replicated the error. My CREATE OR REPLACE TABLE QTEMP... returns
SQLSTATE 58004. I changed my program to check for that, do a CONNECT
RESET, and try the CREATE again. Unfortunately, that didn't make a
difference.
My priority is to be able to recover. Any suggestions?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
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.