RE: Create a *LF over a specific *PF member

["jt" <jt@xxxxxx>]

Uhhhh...  Rob....  (You're one-a my FAVORite people, is why I "pick" on
you...:-)

I tend to agree with Alan, especially the part "I use them regularly still".
If you have re-create tools to deal with members, they are much easier to
deal with.  Wrote a recreate *PF utility, prior to CHGPF which helped speed
development considerably.  Always wanted a pre-compiler like Alan (and
Synon) has had, but never "got a round tuit".

All people, not just PAs, try to simplify things by reducing decisions to
simple maxims.  And these are largely based on one's predisposition...  This
can sometimes result in over-simplifications, but generally work out well.

I heard one such:  CLPs should be compiled *NEW, and RPGs should be compiled
*CALLER.  This CAN work, if the environment is set up that way.  (For
example, you decide you want each menu option to be run out of it's own
*ACTGRP, (I still dunno about /that/ one vs. everything in 1 *ACTGRP vs.
other alternatives) and all your menu options have front-end CLPs.)  Other
situations (I would say most) this doesn't work out so well...

| -----Original Message-----
| [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx

| Alan,
|
| You speak the gospel.
|
| Any reason not to use multiple members sounds great by me.  There's one
| more to add to my list.
|