Re: overriding IBM's options on PDM

I've always wanted to have the time to do my own, mainly because I wanted
to store all non-default compile parms in the source and retrieve them at
creation time.

it would be relatively simple to flag these parms with special characters
on the first line or two of the source and have the pre-compiler read them,
parse them and submit the command.

this would have been very helpful before the new 'H' spec keywords, but
would be even more helpful now, creating stepped objects like RPGSQL and
service programs, combined module programs, etc.

It always would be helpful for things like printer files with special size,
font, overlay, etc parms.

I wish that when IBM came out with ILE giving us binder source, they would
have just gone the extra mile and given us a 'make' source language or
utility, so this stuff could have been standardized.

oh well, maybe next release?  (not holding my breath)

rick

-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----

I have already created my own PDM option for compiles "M" for compile ("C"
is call). "14" is left as is. This accepts library, file, member, and
type. A CL program is called with all the compile commands defined. If
SRCTYP='CLP', CRTCLPGM...., etc. Target release, debug view, etc are
defined once so you should normally never have to prompt the "14" to
override things like target release and debug view. Actually, target
release is kept in a data area. All compile commands are prompted but you
shouldn't have to override normally. The reason for doing this is to allow
the program to be submitted from a command line as a command and prompted.
Just type COMPILE and press F4 and fill in your library, member, compile in
batch, etc. Okay, maybe you wouldn't want to compile straight from a
command line but this would take care of selecting the command based on
source type. I can share this program if you wish. Good luck!

Craig