Re[2]: RPG 400 code on the NET

     Frank,
     
     The best approach to sharing code is to copyleft it - check out the 
     GPL (Gnu Public License).  When you share your code, include a 
     reference to the GPL in it.  In this way you guarantee that the code 
     is free, that other people can use the code in any way that they see 
     fit, and that no-one can make any money from using your code.
     
     Exposing your coding techniques in public gives rise to a peer-review 
     process - if anybody has any comments to make, you can take them as 
     constructive criticism or ignore them, your choice.
     
     ____________
     Paul Cunnane
     The Learning Company
     


______________________________ Reply Separator _________________________________
Subject: Re: RPG 400 code on the NET
Author:  fkolmann@revlon.com.au at InterNet
Date:    15-09-99 12:20 pm


     
There was some discussion recently on submitting RPG code.
     
I would like to raise the following points.
     
What do you expect to see submitted?
     
Most RPG programmers get paid a reasonable wage and I doubt would be 
interested in
giving stuff away for free.
     
If one charges for code what are the support/warranty/legal implications 
if things
go wrong.
<snide remark> (None if you sell really big packages.) <end remark>
     
How I  include in the code the 'use at your own risk stuff'.   Is there 
a
guideline/cookbook for how to present it.
     
How should I submit the code. source only, AS400 save libraries, what 
are the
install instructions etc.
     
How do I expose my dirty linen (coding techniques) in public without 
making a
laughing stock of myself.
     
How do you control changes to the code or better yet get an 
internet-wide
collaboration going to really develop something and then get everyone to 
give their
work away for free.
     
Anyway, having said all that I got a small utility that I want to give 
away,( it was
what prompted the above).
     
The Small Utility.
     
To improve BPCS program performance SSA recommends that we do 
a.  Run STRDBMON on jobs to find recommended indexes
b.  Run PRTSQLINF on programs to get a history of SQL statement run by 
the program.
There are some utilities that can be purchased to help with the analysis 
but again price is an object.
I have cobbled up a small utility to help with PRTSQLINF.
It runs PRTSQLINF over up to 10 libraries and sends the printout to a db 
file then it scans the result looking for Arrival seq and created Access 
Paths and sends its output to another DB file SQLINFB. I then run a 
query over SQLINFB picking up those files with recent dates and long run 
times.
     
Frank
+---
| 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 
+---
+---
| 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
+---