Re: overriding IBM's options on PDM

Vern,
yeah, it's doable.  Though, I think more trouble than it's worth.

I like using one pre-processor job that handles all crt* commands based on
member type.  it does make it tough to remember what pdm option you should
use, but for only about a week.

rick
-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
Right, Rick, and this goes with what others have said. But I was thinking,
in response to this, that the individual commands could be modified - the
ones he needs, and then PDM would call them instead. Messy, as you say, but
doable, I think. It's no different, is it, from putting copies above the
shipped commands with different defaults?

Vern

At 05:04 PM 10/9/2003 -0500, you wrote:

>Vern,
>
>at first, I was thinking he could do something like that, up until i
>started thinking of all that option 14 does: crtbndrpg, crtrpgpgm,
>crtclpgm, crtpf, crtlf, crtdspf, crt??? depending on member type, the list
>goes on and on....
>
>that could get pretty hairy, doncha think?
>
>rick
>
>-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
>
>Put a command above QSYS in the system portion of library list, same name
>as what 14 calls, same parameters? That uses your program?
>
>Was this possible before V5R2? I didn't know about it if it were.
>
>HTH
>
> Vern


_______________________________________________
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.