REPLACE parameter on CRTSQLPKG is defaulted to *YES, so it should get
overlaid each time you create it. Or you can add REPLACE(*YES) to your
compile script so you don't have to depend on the command default.
Elvis
-----Original Message-----
Subject: RE: Remote call
That did it.
I added the CRTSQLPKG as part of the post compile steps into our change
management system.
If I had to make yet one more mod I'd be sorely tempted to add a CRTSQLPKG
after getting that sql state inline to the program. Followed by yet one
more try.
Haven't done the DLTSQLPKG. Am I leaving multiple versions laying around
or do they get overlaid?
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/19/2004 11:45 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc
Fax to
Subject
RE: Remote call
Rob,
I took a look at the description of the SQL0818 via DSPMSGD. It looks
like
an SQL package issue.
Perhaps DLTSQPPKG followed by CRTSQLPKG?
Message ID . . . . . . . . . : SQL0818
Message file . . . . . . . . : QSQLMSG
Library . . . . . . . . . : QSYS
Message . . . . : Consistency tokens do not match.
Cause . . . . . : Package &3 in &4 on application server &5 cannot be
run
with the current application program because either the application
program
has been recompiled without rebuilding the package or the package has
been
restored from a back level version.
Recovery . . . : Rebuild the package by using the CRTSQLPKG command or
by
using a CRTSQLxxx command specifying the correct relational database.
Otherwise, restore the package from a version which matches the
application
program being run.
-----Original Message-----
Subject: SQL: Remote call
I have a program named GDSSYS001 on system GDISYS. It calls program
GDSSYS002 on system GDI using the following:
C/EXEC SQL
C+ CONNECT TO :Systemname
C/END-EXEC
...
C/EXEC SQL
C+ CALL ROUTINES/GDSSYS002 (:SysAsp, :PctSysAsp, :PctPerm, :PctTemp)
C/END-EXEC
When it does so, I get:
sqlcod= -818, sqlstt= 51003
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/info/rzala/rzal
afinder.htm
What is the best way to resolve this?
Rob Berendt
--
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.
--
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.
