RE: Old Rpg to RPG/ILE

Hi Buck,

Yes, I'm getting the drift from your comments - don't touch unless you need 
too. The old adage seems to work well here "If it isn't broke don't fix it". I 
think it fits well and as an advocate of easy life, I think, I will take your 
advice.

Thanks,
DaveH

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Buck
Sent: 27 October 2006 17:37
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Old Rpg to RPG/ILE

One predominant thing there are many sorts 

We kept all of ours (at a previous employer.)  We used to keep the sort 
specs in the OCL on a diskette (S/3).  The operator would edit those 
specs for include/omits (say for a customer listing whose phone numbers 
start with 011 44, ordered by city.) and submit the job from there.

When we converted that to S/38, we stored the OCL in a source member, 
wrote a PDM-like menu system that would let the operators edit the 
source or submit it (SBMDBJOB).  Upside was it was pretty a simple 
conversion from S/3 OCL to S/38 CL and the operator's run books didn't 
change.

As Jim said, it's about how much of your processes and programs you want 
to simply not touch.  I can guarantee you that some S/3 RPG II programs 
I wrote in 1978 are still running with sorts in front of them.  After 
all, how much advanced work is one going to put into an aged trial 
balance report?  If one wants to webify it, it's far more likely that 
one will write a new one rather than add U1 to make it emit HTML instead 
of QSYSPRT...

By letting the old stuff stay as-is, you have the time to focus on 
getting the new stuff written, in theory.
   --buck