Re: passing param to CL

I've never used it,  but from what I understand the  H ActGrp(*NEW)and
using the QCMDEXC would do the trick for you.

Wait nevermind, I have used the H ActGrp(*NEW) which allowed me to call a
procedure within itself, making recursive.

Michael Schutte
Work 614-492-7419
email  michael_schutte@xxxxxxxxxxxx


                                                                           
             steema@diskhaven.                                             
             com                                                           
             Sent by:                                                   To 
             midrange-l-bounce         "Midrange Systems Technical         
             s@xxxxxxxxxxxx            Discussion"                         
                                       <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
             03/20/2006 04:54                                              
             PM                                                    Subject 
                                       Re: passing param to CL             
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




I could do the QCMDEXC, I hadn't thought of it that way. let that go and
finish off the job.
If I use Qtemp there is no problem w/ mixing up the users. I simply have
to pass to the final RPG program which user_special_name it needs.


> I'm a little confused?!?  Are you concerned that multiple users can
choose
> the same splf but choose two different things?
>
> Would this HSPEC do the trick in the RPGLE program?
>
> H ActGrp(*NEW)
>
> or
>
> H ActGrp(*CALLER)
>
>
>
> Instead of calling a CL to execute a CL, why not use QCMDEXC in the RPG
> program?
>
> Just some thoughts, maybe I'm in left field here.
>
> Michael Schutte
> Work 614-492-7419
> email  michael_schutte@xxxxxxxxxxxx
>
>
>
>              steema@diskhaven.
>              com
>              Sent by:
To
>              midrange-l-bounce         "Midrange Systems Technical
>              s@xxxxxxxxxxxx            Discussion"
>                                        <midrange-l@xxxxxxxxxxxx>
>
cc
>              03/20/2006 04:41
>              PM
Subject
>                                        Re: passing param to CL
>
>              Please respond to
>              Midrange Systems
>                  Technical
>                 Discussion
>              <midrange-l@midra
>                  nge.com>
>
>
>
>
>
>
> Please bear in mind that multiple users will be using this program.
> It will allow them to get PDF's sent to themselves or overseas.
>>
>> I am trying to see the best way to do something. I could use a data area
>> or a small output file.
>>
>> We have users who can get reports emailed to them. If you change the
>> USRDATA area and OUTQ on the OVRPRTF, it's done.
>>
>> The name used on the USRDATA is not the same as the profile. This has to
>> be retrieved from a Control file that is very large.
>>
>> I thought of reading this file in the CL but it would likely take time.
>>
>> I can get this info from the prev. RPG program veryu simply. What would
> be
>> the mechanics of getting this back to the CL?
>>
>> Thanks,
>> Steve
>> --
>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>> list
>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>> To subscribe, unsubscribe, or change list options,
>> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>> or email: MIDRANGE-L-request@xxxxxxxxxxxx
>> Before posting, please take a moment to review the archives
>> at http://archive.midrange.com/midrange-l.
>>
>>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.