|
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:
(pointer
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
error)fine.
- 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
wrote:
Jay
On Mon, Apr 10, 2023 at 11:32 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
(COBOL400-L) mailing list
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:
main-proc.
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
(COBOL400-L) mailing list
Why is that?
tia
jay
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
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)
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 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.