Re: Re[2]: CALLB vs.CALLP

["Mark Walter" <mwalter@xxxxxxxxxx>]

Thanks to all for your input to this thread. It was more than enough
information to get me going. I read the new Redbook as well and it was
awesome.

Thanks again,

Mark
-----Original Message-----
From: eric.delong@pmsi-services.com <eric.delong@pmsi-services.com>
To: RPG400-L@midrange.com <RPG400-L@midrange.com>
Date: Friday, March 31, 2000 4:33 PM
Subject: Re[2]: CALLB vs.CALLP


>
>     Alternative....... Use C function "system" which executes in the
>     same call level as the invoking program. The prototypes for this
>     have been delivered to the list several times. I am starting to use
>     this all the time. Better yet, it requires nothing but the command
>     string to be passed, and you can get the error message id if the
>     command fails with a simple include of a C runtime variable.
>
>     eric.delong@pmsi-services.com
>
>
>______________________________ Reply Separator
_________________________________
>Subject: RE: CALLB vs.CALLP
>Author:  <RPG400-L@midrange.com> at INET_WACO
>Date:    3/31/00 1:06 PM
>
>
>
>The problem I always have with using a subprocedure as a wrapper for
>QCMDEXC is the call level.   When I do an OVRDBF or similar command
>via my subprocedure, it doesn't work because its at a different call
>level.
>
>Sure, I could do OVRSCOPE(*JOB)  but thats not a very elegant solution!
>
>So, I usually do a prototype with a CONST parameter for the command and
>the length.  Then I can do something like this:
>
>C               callp     Cmd('OVRDBF FILE(FILEONE) TOFILE(FILETWO)': 200)
>
>I would certainly PREFER to not pass the length -- but havent found a good
>way.   What am I missing?
>
>
>
>
>On Fri, 31 Mar 2000, Stone, Brad V (TC) wrote:
>
>> I never understood this example, and I've seen it from a lot of people.
If
>> you're making a subprocedure, prototype it so you only send the command.
>> Not the length.  You can define the length as %size(Command) in the
>> Subprocedure.
>>
>> Then, you only need to do..
>>
>> CALLP          #QcmdExc('CLRPFM FILE1')
>>
>> Much easier.  And only 2 more seconds of setup.
>>
>> Other times you will definatly want to do this when making wrappers for
>> APIs.  Sometimes they have a lot of parms you don't need to pass.  The
>> command length on QCMDEXC is one of them.
>>
>> Brad
>
>+---
>| 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
>+---
>
>
>
>+---
>| 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
>+---
>

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