RE: Suggestion: File to use when compile

["Denis Robitaille" <denis_robitaille@xxxxxxxxxxxx>]

Good question, I will expand.

My utility program has the following parameters:
- source member name to compile
- qualified file name where the source member is located
- qualified name of the object to create
- wheter or not we want to be prompted for each command (no by
default)
- wheter to execute the commands in batch or interactive (batch by
default)

The first 3 parameters are filled in automatically by PDM (using &n, &l
&o &f ...)

If we want to change some parameter at compile time without changing
the source members, instead of pressing enter in PDM, we press F4. Then
we specify YES for the prompt command parameter. One limitation is that
if we want to do this, we must also choose to run interactively, so we
choose interactive for the last parameter. Then we press enter.

What happen next is that after assembling a command, and befor
executing it, I prefix the command with a "?" and pass it to QCMDCHK. So
the command, with all the ovverride extracted from the source included,
is shown and the user can change any parameters he wants. They get
syntax checked and are executed as desired. The process is repeted for
each command and that is why it must run interactively.

But if we dont want to override the parameters as put in the source,
then we just press enter and away it goes.

If interested, I have posted some year back the source on the list. It
must be in the archive.

On another notes, some mentioned that this is partly supported ih H
spec and that they prefer to wait for full support for this by IBM. I
agree that it would be best if the support for this came directly from
IBM. I wrote this utility almost 10 years ago, so at the time, there was
not much in the H spec. When IBM will provide something equivalent, we
will probably drop the usage of this utility. But in the mean time, it
has done wonders and we had exaclty 0 incident of the kind "DLTLIB" in
the instructions. The fact that all programs starts from predefined
templates does help.

I hope this help make thigs clearer.

Denis Robitaille
Directeur services technique TI
819 363 6130

SUPPORT
Jour (EST) Daytime : 819-363-6134
En-dehors des heures (EST) After hour : 819-363-6158
Network Status : 819-363-6157

>>> dbale@xxxxxxxxxxxxx 2004-10-13 17:11:50 >>>
> As for overiding some parameter when compiling, our utility allows
it.
> Instead of pressing enter, we press F4 and answer YES to a show
command
> prompt and we can then change it for this time only without having
to
> change the source.

How do you do this when you're doing both a CRTRPGMOD & CRTSRVPGM in
the
same source?

Do the prompts show the overridden parameters as they're coded in the
source
member?

db

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx / Denis Robitaille
> Sent: Wednesday, October 13, 2004 4:58 PM
>
> We have been using this kind of stuff (compiling instructions in the
> source read by a utility program) for close to 10 years. It is used
on a
> daily basis by over 60 programmers (some hold, some new, some
> contractor, some student ...). The advantages far outweigh the
problem.
> Now nobody forget to specify CPI(15) on a printer file or an
override
> before a compile anymore.
>
> As for overiding some parameter when compiling, our utility allows
it.
> Instead of pressing enter, we press F4 and answer YES to a show
command
> prompt and we can then change it for this time only without having
to
> change the source.
>
> In fact, we dont use option 14 of PDM anymore (we now use the home
made
> CP instead)
>
> Denis Robitaille

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l 
or email: RPG400-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders  ***