RE: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's the d ifference!!!)

I don't have a problem with seperating DDS source from language 
source.  But one potentially dangerous issue is the separation 
of language source.  Instead of QCLSRC, QRPGSRC, QRPGLESRC, QCBLSRC 
and what not, why not put them into all one source library called 
QPGMSRC?  Many shops do something silly like putting the object 
type into the object name.  For example the following names
ORD500C = *PGM type CLP
BPCSJOBD = *JOBD
XYZDTA = *DTAARA
Which really looks silly from the IFS
/QSYS.LIB/MYLIB.LIB/BPCSJOBD.JOBD
/QSYS.LIB/MYLIB.LIB/XYZDTA.DTAARA

Getting back to my point...

The danger I feel that gets resolved from QPGMSRC versus QCLSRC, 
QRPGSRC... is that you reduce the chance of having a program name 
used for two different languages in the same library.  Programmer 
does a CVTRPGSRC of PROGRAMA from QRPGSRC to QRPGLESRC and forgets 
to delete the member out of QRPGSRC.  Dinosaur programmer comes 
along and edits PROGRAMA in QRPGSRC (what other life is there?).  
He doesn't get any of the changes from QRPGLESRC and wonders why 
the program doesn't work.

One habit I've gotten into is to make the *PGM name not match the 
source name.  Especially for multiple module *PGM's.  If someone
doesn't know that PROGRAMA is made up of modules PROGRAMA and PROGRAMB
then they will simply do a CRTBNDRPG on PROGRAMA, (or at least try).
When they should be doing a CRTRPGMOD on PROGRAMA and then a UPDPGM on
PROGRAMA.

Oh my lord!  If someone deletes PROGRAMA *PGM how will they know 
how to recreate it?  How will they know what modules are in it?  Egads!
Well, for one thing you implement change management software like we
are doing with Turnover.  For another, you backup.  Then you can
restore the object and analyze that.






DBale@lear.com on 04/19/2000 01:54:05 PM
Please respond to RPG400-L@midrange.com@Internet
To:     RPG400-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        RE: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's the 
d ifference!!!)

One other thing that goes along with my previous positions on external
printer file definitions:  One of the biggest pains in the rear is having
RPG source in one source file, CL in another, and PRTF / DSPF in another.
This is still the shop standards in all of the clients I have been in.  JBA
even goes to further extremes, but that's another flame war.  This QRPGSRC,
QDDSSRC, QCLSRC stuff is carryover crap from the S/38 days of the programmer
menu, before IBM gave us PDM.  I have one source file in my development
library.  WRKMBRPDM QSRC AR123* shows RPG member AR123R, CLP member AR123C,
DSPF member AR123DF, and PRTF member AR123PF all together on one screen.
Note that I still keep database PF & LF definitions in a separate source
file.  I am currently working on a WRKMBRPDM-like utility that disregards
the library & file selection, i.e., think of a WRKMBRPDM AR123*, and it will
show _all_ source members beginning with AR123 in any source file in any
library.  It's mostly done, but I'm working on the PDM-like user options and
the underlying outfile update function.
ame


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---