Re: *SRVPGM vs. dynamically CALLed *PGM from ILE COBOL...

[vhamberg@xxxxxxxxxxx]

Steve, that statement is patently untrue. One of our products is a *SRVPGM, and 
we have several examples of how to use it. Here is one:

At the very beginning you put the following extension:

PROCESS NOMONOPRC.      
IDENTIFICATION DIVISION.

That comes before PROGRAM-ID. The NOMONOPRC does something with whether you can 
use underscores - I'm not a COBOL developer but found this, so that we did not 
need a second *SRVPGM for just the COBOL calls.

To call a procedure in a *SRVPGM, you do something like this

CALL PROCEDURE "SQL_RUNSQLSEL"  
     USING BY VALUE SQL-SOCKET-B
                    SQL-SELECT-V
     RETURNING SQL-RETURN-B.    

That even includes a variable-length variable that I named SQL-SELECT-V - those 
are not as nice to work with as in RPG - more like C/C++ - but so it goes.

We have possibly 40 procedures in that *SRVPGM.

So you can't stand on that floor with no joists holding you up.

Vern

-------------- Original message -------------- 
From: "Steve Richter" stephenrichter@xxxxxxxxx 

-snip-
> The limitiation that I will stand by and that Michael should be aware 
> of is you effectively cant call into a SRVPGM from COBOL. Basically, 
> COBOL does not work with ILE. ( COBOL only sees one max 10 char 
> procedure in the SRVPGM ) The COBOL code I worked with had been 
> "modernized" from mainframe COBOL to call external programs and use 
> embedded SQL. 
>
> -Steve