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



oh sorry Jon, no I'm not using the input parm... just wanted to POC an in
and out parm.

Jay

On Mon, Apr 10, 2023 at 1:08 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

funny you ask that and I'm not a cobol pgmr... I'm just trying to POC some
ILE things at the moment...

I did have this... but you see it is commented out because it seems it got
in the way at some point...is it important? :)

LINKAGE SECTION.
*01 INCOMING-PARM.
01 INCOMING-VALUE1 PIC X(5).
01 OUTGOING-VALUE1 PIC X(50).

Jay


On Mon, Apr 10, 2023 at 12:02 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

Your code sample does not use the input parm - are you suing it?

On Apr 10, 2023, at 11:50 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

thanks Jon... yes, no OPM is in play here.

I'd love to see if you can confirm this behavior or overcome it.
If you can confirm it, I'll get something to IBM.

thanks

Jay

On Mon, Apr 10, 2023 at 11:49 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

Sounds like it may be a problem for IBM to sort out.

As far as the run unit is concerned (and it could have an impact) ILE
COBOL run units map to the AG and - perhaps more importantly - the run
unit
cannot be shared by OPM and Ile COBOL.

STGMDL is, I suspect, a red herring.

So, if you use a named AG and BOTH the COBOL and the RPG run in that
AG I
would expect it to work. If I have time later I'll have a play but I'd
report it to IBM. At the very least if it is a limitation it should be
documented.


Jon P.

On Apr 10, 2023, at 11:32 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

Jon,

this is basically what I've narrowed it down to...

SQLCBLLE *PGM can do SQL no problem

A SQLRPGLE that calls *SRVPGM with SQLCBLLE *module cannot do SQL
(pointer
error)
- have not been able to find out why (run unit concept?)
- even when run under named actgrp and stgmdl(*snglvl)

A SQLRPGLE that calls *SRVPGM with SQLCBLLE *module without SQL works
fine.


Jay



On Mon, Apr 10, 2023 at 11:32 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

This would normally indicate that you didn't pass the required
number of
parameters - 2 in this case.

What does your call look like?


Jon P.

On Apr 10, 2023, at 8:43 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

I have a simple cobol sql pgm.

I have the following pieces...

WORKING-STORAGE SECTION.
01 WS-MESSAGE PIC X(50).

LINKAGE SECTION.
01 INCOMING-VALUE1 PIC X(5).
01 OUTGOING-VALUE1 PIC X(50).

**************************************************************
PROCEDURE DIVISION USING INCOMING-VALUE1, OUTGOING-VALUE1.
**************************************************************
main-proc.
exec sql
select 'Row count from CBL00000M_PGM1 SQL: ' concat
char(count(*))
into :ws-message
from xxx.zzz
end-exec.
move ws-message to outgoing-value1.
EXIT PROGRAM.

I am getting a pointer error when it tries to exec the sql under
main-proc.

Why is that?

tia

jay
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/cobol400-l.


--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/cobol400-l.


--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/cobol400-l.


--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/cobol400-l.


--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/cobol400-l.


--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/cobol400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.