|
Message: [SQL0455] Schema LTL400SAI3 for specific name not same as routine
schema QGPL.
The specific name for a procedure: When defining multiple procedures with
the
same name and schema (with different number of parameters), it is
recommended
that a specific name also be specified. The specific name can be used to
uniquely
identify the procedure when dropping, granting to, revoking from, or
commenting
on the procedure.
If specific-name is not specified, it is the same as the procedure name. If
a function
or procedure with that specific name already exists, a unique name is
generated
similar to the rules used to generate unique table names.
You can't have the procedure created in QGPL with a specific in another
schema...
Charles
On Wed, Oct 18, 2017 at 3:08 PM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:
I am trying to create procedure but the system rejects it. I cannotroutine
identify the problem
Create procedure QGPL.IAR500
(IN USER_ID CHAR(10),
IN PDate_From CHAR(08),
IN PDate_To CHAR(08),
OUT Error_Code CHAR(02),
OUT PERRMSG CHAR(100) )
EXTERNAL NAME myLib.IAC500
LANGUAGE RPGLE
SPECIFIC IAR500
NOT DETERMINISTIC
CALLED ON NULL INPUT
MODIFIES SQL DATA
PARAMETER STYLE GENERAL WITH NULLS
DYNAMIC RESULT SETS 1
;
The error is:
SQL State: 42882
Vendor Code: -455
Message: [SQL0455] Schema LTL400SAI3 for specific name not same as
schema QGPL. Cause . . . . . : The specific name schema LTL400SAI3IAR500.
specified on a CREATE PROCEDURE, DECLARE PROCEDURE, or CREATE FUNCTION
statement is not the same as schema QGPL for procedure or function
Recovery . . . : Specify the same schema for the specific name as forlist
the procedure or function name.
Error may be staring me in the face....
Darryl Freinkel
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.