RE: Statically binding multiple MAIN modules with display files

[Scott Mildenberger <scottmildenberger@xxxxxxxxx>]

--- Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
> > From: Joel Cochran
> > 
> > By enclosing these in procedures, they become very modular:
> > 
> > <psuedo-code>
> > /free
> >   if sflOption = 2 ;
> >     invoiceUpdateScreen( myKeyValue );
> >   elseif sflOption = 3 ;
> >     invoiceCopyScreen( myKeyValue );
> >   elseif sflOption = 4 ;
> >     invoiceDeleteScreen( myKeyValue );
> >   elseif sflOption = 5 ;
> >     invoiceDisplayScreen( myKeyValue );
> >   endif ;
> > /end-free
> > </psudoe-code>
> 
> Sure, but you could do that just as easily with a prototype
> with EXTPGM,
> couldn't you?


Exactly, this is how my dynamic calls look because I do
prototype them with EXTPGM.  I actually use the prototype in the
program itself by using conditional compilation directives. 
Then if you want to dynamic call a program using prototype you
just do the following to get the prototype:

      /define PROTOTYPE_ONLY
      /copy qrpglesrc,frselcomp
      /copy qrpglesrc,frselmfg
      /copy qrpglesrc,frselwork
      /copy qrpglesrc,frwrkexcl
      /copy qrpglesrc,frwrkmodl
      /copy qrpglesrc,frwrksegs
      /undefine PROTOTYPE_ONLY
 

Scott Mildenberger



__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus