Are you sure that STRDBG was not execute without parameters before?
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 Dennis Lovelady
Gesendet: Thursday, 13. May 2010 18:55
An: 'Midrange Systems Technical Discussion'
Betreff: Reason(s) for SQL generating debugging messages
Hi, Folks:
What would be the reason that an embedded SQL (RPG ILE) program on V5R3
would be generating SQL debug messages when it's not being debugged?
I'm trying to determine why the joblogs are so large for a number of
programs, most of which involve imbedded SQL, and one factor that I'm seeing
is that there are significant numbers of CPI434B, CPI4339,CPI434A, CPI432D
(et cetera) in the job log. I am accustomed to seeing these when debugging
an RPG SQL module, but not when the program is run without debug, and
certainly not in a batch environment.
What might we have done to cause this, and how might we stop it at V5R3?
Dennis E. Lovelady
AIM/Skype: delovelady MSN: fastcounter@xxxxxxxxxxxx
<
http://www.linkedin.com/in/dennislovelady>
www.linkedin.com/in/dennislovelady --
Time is nature's way of keeping everything from happening at once.
midrange.com
