Re: imbedded CL in RPG

[John P Carr <jpcarr@xxxxxxxxxxxx>]

Scott 

Now you are getting close to what I wanted from Toronto in the following.

        CL      BEGCL
CL      SNDPGMMSG XXXXXXXXXXXXX
CL      MONMSG(CPFXXXX)
CL              ENDCL

Since Hans was going to include a monitoring capability to RPG, 
I thought that they could purcolate the error up.  I wanted THEM
do something like what you described below.    The other various
ways of doing a prototyped QCMDEXEC doesn't handle the "True" 
CL message handling etc.  (As you stated)
Since Rochester will NEVER give us logic control in CL (subroutines, when,
if, dou, etc)
I thought this way I could kinda wrap RPG logic control statements "Around" 
my CL program elements.  
John Carr
-------------------------------------------
Scott Klement said;
<SNIP>
>How about having seperate sub-procedures for your CL commands, in
>other words, each subprocedure would need to be labelled as either
>RPG or CL.
>
>Then, a simple program... a "preprocessor" if you will...  could be
>written to do the following:
>          1) Seperate each CL "sub-procedure" into its own source
>                  member in a file in QTEMP.
>          2) Seperate the RPG source into its own source member
>                   in a file in QTEMP.
>          3) Compile each RPG & CL module (using CRTRPGMOD and
>                   CRTCLMOD) individually in QTEMP.
>          4) Finally, bind them all into a program.
>
>This would, effectively, allow you to run CL stuff in the same source
>member as your RPG program...  Since you can bind modules written in
>CL to modules written in RPG, this would give you very nearly the same
>performance and benefits of having the CL embedded.
>
>Without losing the convienience of having it all in one source member.
<SNIP>
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END