|
Sorry.
Here's the SQL source...
DROP PROCEDURE QGPL/LICKTYSPLT;
CREATE PROCEDURE QGPL/LICKTYSPLT (
IN USERID CHAR(10),
IN ACCESSCODE CHAR(80),
OUT PGMTYPE NUMERIC(1,0),
OUT RETURN NUMERIC(2,0) )
LANGUAGE RPGLE
SPECIFIC QGPL/LICKTYSPLT
NOT DETERMINISTIC
READS SQL DATA
EXTERNAL NAME 'LS/LICKTYSPLT'
PARAMETER STYLE GENERAL ;
And here's the error...
SQL0204 20 1 Position 1 LICKTYSPLT in QGPL type *N not found.
SQL0104 30 5 Position 21 Token ( was not valid. Valid tokens: ) ,
.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Thursday, September 29, 2022 10:54 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: What's wrong here?
This is a text only list.
Therefore we don't see the sql statement nor the message.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
tgarvey@xxxxxxxxxx
Sent: Thursday, September 29, 2022 11:37 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: What's wrong here?
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
Hi,
We have an SQL statement that is run by an RUNSQLSTM at our client's IBM i
servers. It runs fine on 4 out of 6 of their servers. The failures say it's
a syntax error.
Here's the SQL source.
And here's the error.
I'm at a loss what's wrong here. It works on 4 out of 6 servers, all at v7r2
and all at same PTF level, and it works here on v5r4, v7r1, and v7r3.
Here's the RUNSQLSTM in use.
RUNSQLSTM SRCFILE(INSTFRLIB/QSQLTXT) +
SRCMBR(LICKTYSPLT) COMMIT(*NONE) +
ERRLVL(20) DBGVIEW(*LIST) +
CLOSQLCSR(*ENDMOD) USRPRF(*OWNER) +
DYNUSRPRF(*OWNER)
Any suggestions will be gratefully received.
Kind Regards,
Thomas Garvey
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.