RE: Suggestion: File to use when compile

["Denis Robitaille" <denis_robitaille@xxxxxxxxxxxx>]

When you specify  
    **#$%COM: USRPRF(*OWNER) TGTRLS(V4R5M0)
How does your utility program knows which CRT* command to use?

I have a similar utility but, in my case, I must put the complete CRT 
statement
ex: 
*%%% crtrpgmod             
*%%%   module(%libo/%obj)  
*%%%   srcfile(%libs/%fic) 
*%%%   srcmbr(%mbr)        
*%%%   DBGVIEW(*LIST)      
*%%%#                      
*%%% crtsrvpgm             
*%%%   srvpgm(%libo/%obj)  
*%%%   module(*srvpgm)     
*%%%   export(*all)        
*%%%   actgrp(*caller)     
*%%%&                                           

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 16:17:00 >>>
Depending on the particular devil you want to deal with...

Here's what I had before I developed my pre-compiler:

      * Prior to compiling this program, the following must
      * be performed in the job prior to compilation:
      *  CRTPF FILE(QTEMP/AR123W) SRCFILE(DRLLIB/QDDSSRC) SIZE(50000)
      * This program must be compiled with
      *  USRPRF(*OWNER) TGTRLS(V4R5M0)

I would have to *remember* to do the CRTPF prior to compiling, and I'd
have
to either compile the program interactively, or create a CL program
that did
the CRTPF QTEMP/AR123W and the compile together.  Bleahhh.

Now, with my pre-compiler:
      * Prior to compiling this program, the following must
      * be performed in the job prior to compilation:
      **#$%PRE: CRTPF FILE(QTEMP/AR123W) SRCFILE(DRLLIB/QDDSSRC)
SIZE(50000)
      * This program must be compiled with
      **#$%COM: USRPRF(*OWNER) TGTRLS(V4R5M0)

Piece of cake.  Instead of PDM option 14, I've defined Z1 and use it
for all
compiles, regardless of whether there are any pre-compiler directives
or
not.  The important thing is that one does not *need* to use my
pre-compiler, but they would still have to do the steps manually like I
did
before.

The only gotcha is that whoever compiles the source with PDM 14 has to
view
the source to determine whether there are any pre-compiler directives. 
It
would help that the first 20 lines of the source member are colorized,
blocked, blinking, etc. so that it STANDS OUT to the person who may
not
otherwise realize that there are special considerations needed to
compile.

Yeah, it would be better if IBM did this automagically.  And they may
choose
to do it for RPG, but what are the chances they would do it for every
type
of compile source?  "When Pigs Fly" comes to mind.  Til then, I'll
keep
using my utility.

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx / Scott Klement
> Sent: Wednesday, October 13, 2004 3:45 PM
>
> > And for that matter, it isn't rocket science for a home-grown
utility
> > to do it either, with the added bonus you can do it with any
source
> > type, not just RPG.  I did one many years ago which handles both
pre &
> > post compile commands (with either continuation or cancel when
errors
> > occur), compile overrides, etc.  And works with RPG, CL, DDS, etc.
>
> That's nice... but then outside consultants who work on our system
> wouldn't be familiar with them.  New programmers we hire wouldn't be
> familiar.  If I send my code to someone else (such as demonstrating
a
> technique in this e-mail forum) then they wouldn't be able to run
them
> without installing my special precompiler.
>
> Yes, I know... I can teach outside people about the utility. I can
teach
> new programmers. I can remove the precompile stuff before
distributing my
> code.
>
> But, if IBM included these things with the compilers, I wouldn't have
to.

--
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  ***