RE: Running a remove stored proc from CL and RUNSQL -- MIDRANGE-L

Thanks for the response - it turns out to be my ignorance. Once I let the system create the sql package on the target machine all was well.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Niels Liisberg
Sent: Wednesday, February 24, 2021 5:20 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Running a remove stored proc from CL and RUNSQL

Maybe it is the 3-part notation in *SYS/*SQL that is the issue / difference:

I will stick to the dot notation which is more SQL'ish but i still use *SYS in the naming parameter since it supports both notation but allows you to use librarylist

RUNSQL SQL('call systemb.therrplib.MR016SP04 (''BK341RFL '', ''BKS2FIN
'', ''FN'', '' '', ''1'', ''THERRP'')') COMMIT(*NONE)
NAMING(*SYS) OPTION(*LIST)

On Mon, Feb 22, 2021 at 6:09 PM Therrien, Paul via MIDRANGE-L < midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I am on IBM I V7R3 on 2 separate machines (LPARs) and I am attempting
to run a stored procedure on system B from system A.

I can run this on a command line on system A:

RUNSQL SQL('call systemb/therrplib/MR016SP04 (''BK341RFL '',
''BKS2FIN

'', ''FN'', '' '', ''1'', ''THERRP'')') COMMIT(*NONE)
NAMING(*SYS) OPTION(*LIST)
This successfully runs the stored procedure on system B.

When I put this same command in a CLLE program the call to the stored
procedure fails.

Output from RUNSQL in CL program:

5770SS1 V7R3M0 160422 RUNSQL

Record *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6
...+... 7 ...+... 8
1 call systemb/therrplib/MR016SP04 ('BK341RFL ', 'BKS2FIN ',
'FN', '
1 ', '1', 'THERRP ')

* * * * * E N D O F S O U R C E
* *
* * *

5770SS1 V7R3M0 160422 RUNSQL
Record *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+...
MSG ID SEV RECORD TEXT
SQL0204 30 MR016SP04 in THERRPLIB type *N not found.

I am certain this situation just reflects my ignorance.
Any help appreciated.

--
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