First thing what is commit level now?
-Matt
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Thursday, September 6, 2018 4:55 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Is the table created or not?
I am at my wits' end. Within a large application, I've got some SQL which creates a table (which will be used for output later) by selecting columns from another table (which serves as a kind of data dictionary of all possible columns).
This has been working for years, and now when I make some changes to the application, it doesn't work anymore.
We don't have journaling, so the SQL always gives me
SQLState: 01567, Error code: 7905
Table MYFILE in MYLIB created but was not journaled.
But that has always been the case; the application would simply carry on despite the lack of journaling, and make use of MYLIB/MYFILE just fine.
However, with my recent changes, the table doesn't even seem to be created. I get the same message (that it's created but not journaled), yet the table's not there.
Maybe more precisely, the *file* is not there. Immediately after attempting to create the table, I check for existence of the file object, and the result is negative. But I can still query the table with SQL to get a row count (which will be zero). A table that doesn't exist shouldn't be able to be queried at all.
I know I haven't given many details and no code at all, but it's in iSeriesPython. I guess I'm mainly wondering if anyone's ever encountered anything like this before, or has any ideas of what to look for.
Oh, I should mention that when I pull the suspect code out of the application and into a testing stub, or into STRSQL, it works fine.
And as I said, it's still working in the current version of the application, just not in my new, modified version.
John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=ohA0pm19uBMXBUeBnfg7AF-r-EfoRV2jF1UsUvlDvYk&s=s-puiDao0GzcDVky5SAkwmJLHQ6GtR_GlDYkzlpI6II&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_midrange-2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=ohA0pm19uBMXBUeBnfg7AF-r-EfoRV2jF1UsUvlDvYk&s=WVpDTxzXBmX_ihlMXI0zDGQj-TdqI1BtO33Sy2IyBlQ&e=.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://urldefense.proofpoint.com/v2/url?u=http-3A__amzn.to_2dEadiD&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=ohA0pm19uBMXBUeBnfg7AF-r-EfoRV2jF1UsUvlDvYk&s=AyqjGoZ7pdQq5GandFvQ5G0obkVpjmKv1h4sARUkoag&e=
midrange.com
