×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Paul,
Did you notice this message?
SQL0204 30 MR016SP04 in THERRPLIB type *N not found.
Do you recognize that name "MR016SP04"? Is it in that library THERRPLIB?
HTH,
Mark
On Monday, February 22, 2021, 12:09:50 PM EST, 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.
As an Amazon Associate we earn from qualifying purchases.