RE: Difference bet. Primary and Full procedural file.

What is it you are suggesting here?  Are we speaking of RPG or of SQL?  If
you are hiring a programmer with RPG skills and then ask him to maintain SQL
programs aren't you shooting yourself in the foot?


-----------------------------------------------
Booth@MartinVT.com
http://www.MartinVT.com
-----------------------------------------------
-------Original Message-------

From: rpg400-l@midrange.com
Date: Wednesday, May 22, 2002 15:03:19
To: 'rpg400-l@midrange.com'
Subject: RE: Difference bet. Primary and Full procedural file.

reply to the sarcasism --

EVAL STRSQL SORT3, SORT2, SORT1, SORT0 +
FROM ' + #WRKLIBR + '/RCB650V'

If one of our programmers cannot look at this line and see what file the
records are coming from then they also should spend some time learning SQL.

Ron

-----Original Message-----
From: Douglas Handy [mailto:dhandy1@bellsouth.net]
Sent: Wednesday, May 22, 2002 1:52 PM
To: rpg400-l@midrange.com
Subject: Re: Difference bet. Primary and Full procedural file.


Ron,

>Yes Doug you are right I have not posted alternative code. However, when

>nearly all my programs are done with SQLRPGLE,


Fine. Then post a sample program in SQLRPGLE which shows how you perform
heading and total level calculations and printing.

SQL is great for many things -- although I have my beefs with the current
precompiler -- so I don't care if you post SQL or REXX if you think it is
more
readable and easier to maintain.

The goal is for programs which are easy to maintain. If it is faster to
code
and / or executes faster too, that is an added bonus. I've shown you what I
consider to be the easiest to maintain, and it also happens to be very fast
to
code and performs well to boot.

All I'm asking is for you do to the same -- show me what you consider to be
the
right way to do this simple, common task.

>I don't even have an F spec for my primary files.


<sarcasm *on>

What? You mean - gasp - that you are asking the compiler to do something
for
you like opening files and reading records when you are not explicitly
coding
the operations? How is the poor maintenance programmer supposed to know
what is
going on?

<sarcasm *off>