Re: [COBOL4000L] sqlcblle - pointer error on select into? -- COBOL400-L

Thanks Michael,

I have successfully been able to do the following...

1.) code 2 different COBOL programs (I'll refer to as procedures going
forward), into a single SQLCBLLE source member.
2.) when compiled, it produces 2 *MODULE objects.
3.) put these *MODULES into a *SRVPGM
4.) from an SQLRPGLE pgm I can call either procedure via the *SRVPGM.

All good so far and fairly close to how it is done in RPGLE.. .BUT what you
say about managing multiple COBOL pgms in a single source member is ringing
true.
I'm now getting sql precompile issues which seem silly. (first procedure
compiles fine... the 2nd procedure fails even though it has the same EXEC
SQL statement in it as the first)... certain sql precompile vars such as
sql-00003 is not defined... ?

Jay

On Wed, Apr 12, 2023 at 9:30 AM Michael Quigley <MichaelQuigley@xxxxxxxxxx>
wrote:

Frist, we're primarily a COBOL shop and I do this stuff all the time. So
yes, what you're trying is definitely possible. But there's something very
off here with the information you've supplied.

(Keeping in mind, as Jon pointed out, that you can't really create
multiple procedures in a single module in COBOL.)

Look at the call stack you've included:

------Activation Group------ Control
Program Name Number Boundary
QCMD QSYS *DFTACTGRP 0000000000000001 Yes
QUICMENU QSYS *DFTACTGRP 0000000000000001 No
QUIMNDRV QSYS *DFTACTGRP 0000000000000001 No
QUIMGFLW QSYS *DFTACTGRP 0000000000000001 No
QUICMD QSYS *DFTACTGRP 0000000000000001 No
QUOCPP QPDA *DFTACTGRP 0000000000000001 No
QUOMAIN QPDA *DFTACTGRP 0000000000000001 No
QUOCMD QSYS *DFTACTGRP 0000000000000001 No
CBLTEST JVAUGHN CBL 0000000000000034 Yes
CBLTEST JVAUGHN CBL 0000000000000034 No
CBL00000S JVAUGHN CBL 0000000000000034 No

From the command line, you show calling a program named CBLTEST. The first
entry should be the primary-entry-point of a COBOL program, then comes the
main procedure of that program. Then I would expect to see the COBOL
module/procedure name somewhere in the stack after the call to the CBL0000S
service program. This would indicate that you're not really in the module
yet. But there's more missing---

Here are the create statements I found in what you've posted:

CRTSQLCBLI OBJ(JVAUGHN/CBL00000M)

That will create a program called COBOL *program* named CBL00000M (unless
you're specifying OBJTYPE(*MODULE) somewhere).

CRTSRVPGM SRVPGM(JVAUGHN/CBL00000S)
MODULE(JVAUGHN/CBL00000M JVAUGHN/CBL00001M)
EXPORT(*SRCFILE)
SRCFILE(JVAUGHN/COBOL)
SRCMBR(CBL00000B)
ACTGRP(*CALLER)

So I don't see any modules created--just a service program using unknown
modules. (They must be from an earlier compile???)

Then the RPG source you've shown is irrelevant--it's not in the call
stack. So this must be where you're trying to test the call procedure
differently. (Don't forget to specify "call procedure" in COBOL if you want
to call a procedure in a service program or another procedure/module in the
same COBOL program. "call *pgmname" will call a *PGM object, not a
procedure/module in a service program.)

It's been a while since I did multiple modules in a single source member
(design wise it may make sense, but practically it can be a real nightmare
trying to work with and maintain it), but I'm not sure if you can reference
the 2nd or later modules outside of the primary one. Maybe you can if the
END PROGRAM comes before the next IDENTIFICATION DIVISION--like I said,
it's been a while.

Michael Quigley
Computer Services
The Way international
www.TheWay.org

-----Original Message-----
message: 4
date: Tue, 11 Apr 2023 12:37:19 -0400
from: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
subject: Re: [COBOL400-L] sqlcblle - pointer error on select into?

complete module source... (just ran this and got the error)...

*//////////////////////////////////////////////////////////////
* COBOL EXPORTABLE PROGRAM 1
*//////////////////////////////////////////////////////////////

PROCESS OPTIONS.
PROCESS NOMONOPRC.
IDENTIFICATION DIVISION.
PROGRAM-ID. CBL00000M.

**********************************************************
****

**********************************************************
****
ENVIRONMENT DIVISION.

**********************************************************
****
CONFIGURATION SECTION.
SPECIAL-NAMES.

**********************************************************
****
DATA DIVISION.

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

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

exec sql
set option
commit = *NONE,
closqlcsr = *ENDMOD,
datfmt = *ISO
end-exec.

exec sql
include sqlca
end-exec.

**********************************************************
****
PROCEDURE DIVISION USING INCOMING-VALUE1
OUTGOING-VALUE1.

**********************************************************
****

exec sql
select "SQL row count from CBL00000M SQL: " concat
char(count(*))
into :WS-MESSAGE
from lib.file
end-exec.
move ws-message to outgoing-value1.
* MOVE "SUCCESSFUL CALL TO CBL00000S/CBL00000m COBOL Proc"
* TO OUTGOING-VALUE1.

END PROGRAM CBL00000M.

*//////////////////////////////////////////////////////////////
* COBOL EXPORTABLE PROGRAM 2
*//////////////////////////////////////////////////////////////

PROCESS NOMONOPRC.
IDENTIFICATION DIVISION.
PROGRAM-ID. CBL00001M.

**********************************************************
****

**********************************************************
****
ENVIRONMENT DIVISION.

**********************************************************
****
CONFIGURATION SECTION.
SPECIAL-NAMES.

**********************************************************
****
DATA DIVISION.

**********************************************************
****
WORKING-STORAGE SECTION.
01 WS-WINDOWMESSAGE PIC X(10000).
01 WS-RETURNACTION PIC X(6).

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

**********************************************************
****
PROCEDURE DIVISION USING INCOMING-VALUE1, OUTGOING-VALUE1.

**********************************************************
****

MOVE "SUCCESSFUL CALL TO CBL00000S/CBL00001m COBOL Proc"
TO OUTGOING-VALUE1.

END PROGRAM CBL00001M.

Module creation...
CRTSQLCBLI OBJ(JVAUGHN/CBL00000M) over my source.

srvpgm creation...
CRTSRVPGM SRVPGM(JVAUGHN/CBL00000S)
MODULE(JVAUGHN/CBL00000M JVAUGHN/CBL00001M)
EXPORT(*SRCFILE)
SRCFILE(JVAUGHN/COBOL)
SRCMBR(CBL00000B)
ACTGRP(*CALLER)

My sqlrpgle *PGM...
ctl-opt debug option(*nodebugio)
dftactgrp(*no) actgrp('CBL')
bnddir('CBL');

dcl-s g_pgm1Rtn char(50) inz;

dcl-pr cbl00000m extproc('CBL00000M');
i_parm1 char(5) const;
o_parm1 char(50);
end-pr;

cbl00000m('test1'
:g_pgm1Rtn);

The call stack at run time and when I get the pointer error...

------Activation Group------ Control
Program Name Number Boundary
QCMD QSYS *DFTACTGRP 0000000000000001 Yes
QUICMENU QSYS *DFTACTGRP 0000000000000001 No
QUIMNDRV QSYS *DFTACTGRP 0000000000000001 No
QUIMGFLW QSYS *DFTACTGRP 0000000000000001 No
QUICMD QSYS *DFTACTGRP 0000000000000001 No
QUOCPP QPDA *DFTACTGRP 0000000000000001 No
QUOMAIN QPDA *DFTACTGRP 0000000000000001 No
QUOCMD QSYS *DFTACTGRP 0000000000000001 No
CBLTEST JVAUGHN CBL 0000000000000034 Yes
CBLTEST JVAUGHN CBL 0000000000000034 No
CBL00000S JVAUGHN CBL 0000000000000034 No

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