RE: New Cool stuff in V7

Thanks, Birgitta.
My standard generic test for SQL failure since moving to 7.1 is:
if (%subst(SQLSTATE : 1 : 2) <> '00'
and %subst(SQLSTATE : 1 : 2) <> '01');
// SQL failed
...
endif;

Not as elegant as a call to a more robust error handling module, but I have a WDSCi snippet that drops that in place where I tell it to. Now if IBM changes the rules on me again, I'll be revisiting a lot of code. It fixed the immediate problem.
-- Michael
~~~~~~~~~~~~~~~~~~

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Tuesday, June 18, 2013 1:24 AM
To: 'Midrange Systems Technical Discussion'
Subject: AW: New Cool stuff in V7

Michael,

about new warning-level SQLSTATE values. Prior to that, I had a

bunch

of

code that tested the first two characters of SQLSTATE for '00' as my
indication that all was cool.
It was always recommended by IBM not to check for SQLCODE = *Zeros and
SQLSTATE '00' solely. SQLCODE > *Zeros and <> 100 means Warning as well
as SQLSTATE class '01'. If a warning occurs the SQL statement is
executed and data returned successfully.
IMHO IBM may continue to add new warning stati.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars."
(Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What
is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Koester,
Michael
Gesendet: Monday, 17.6 2013 19:43
An: Midrange Systems Technical Discussion
Betreff: RE: New Cool stuff in V7

Jeff, there was one SQL issue that bit me when I'd missed the piece in
the MTU that mentioned about new warning-level SQLSTATE values. Prior
to that, I had a bunch of code that tested the first two characters of
SQLSTATE for '00' as my indication that all was cool. With the new
warnings (like for Select into where the receiving host variable was
shorter than the column) returning '01...', my programs would then take
a different path than before.
Oops -- had to scramble to fix those. Maybe this was fixed in v5.4 via
PTF since we moved to 7.1, and you've had a chance to go through that
already.

Otherwise, I had no other adverse impacts.
Enjoy!
-- Michael