RE: Strange SQL dumps (again!)

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

I used to get this when I first used embedded SQL, due to the use of GROUP
BY summary functions.  I failed to explicitly declare the result field size
that SQL was supposed to return to my program.  My program was reading into
a DS, with the summary field being defined as 10,2.  SQL was actually
returning something like 20,6 which caused internal storage in my program to
get hosed.  ALWAYS define the result field size for derived fields in
SQL......  

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx
[mailto:oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, June 24, 2003 7:32 AM
To: Midrange Systems Technical Discussion
Subject: Re: Strange SQL dumps (again!)


Hi Peter,

>How I stop these SQL dumps?  We are starting to receive these and we do 
not know
>what to do...  What is strange is that we are in V5R2 and I saw on the 
archives
>that this problem came in V5R1.  We should be covered with the latest of 
the
>latest (we have just two weeks enjoying the new OS):

We also have these SQL dumps - mostly from remote machines with ODBC 
connection. 
As I am getting no other error reports from these machines (the 
applications seem
to be running), I'm just ignoring the dumps.

Funnily, mostly the dumps occur at application startup time. 

Regards,

Oliver
_______________________________________________
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.