Re: Do I have to recreate the SQLPKG, and why?

[rob@xxxxxxxxx]

A workaround might be to have Turnover do a "Post Run" command to create 
the package.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Kurt Anderson" <kjanderson@xxxxxxxxxxxxx> 
Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx
02/02/2005 01:50 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Do I have to recreate the SQLPKG, and why?






I have a SQLRPG program that has to access files created by a software
vendor which reside on a separate box.  We do have DDMs for those files,
but not with a key I need.  So I did a little research and found that I
could create a SQL Package which would allow me to perform embedded SQL
statements across systems.
 
>From what I've found, I need to have the SQLPKG reside on the system my
program is using SQL to get to.  It seems that I must recreate the
SQLPKG any time the object that references it is recompiled.  This
wasn't so bad originally, but as time goes on, if any of our database
files change that this program uses, Turnover (our change management
software) will recompile the program, but the SQLPKG remains as it was.
When this happens, and someone calls the program, they get a
data-decimal error.  Once I recreate the SQLPKG the error goes away.
 
Is there a compile parameter I can specify that would prevent this error
from occurring?
Why is this error occurring?  (Ok, I understand that a numeric field has
non-numeric data in it... but what is causing that?)
 
Thanks,
 
Kurt Anderson
Application Developer
Highsmith Inc.
W5527 State Road 106, P.O. Box 800
Fort Atkinson, WI 53538-0800
TEL (920) 563-9571  FAX (920) 563-7395
EMAIL kjanderson@xxxxxxxxxxxxx
 
-- 
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.