Re: RPG Standards?

You @#$%^&*!!!!!  Why did you want to flood my email with this holy war?  
Oh well, let me chuck in my spear...

Avoid OPNQRYF.  Use SQL instead.

Keep the field names the same in all files.  ITEMNBR should be the same in 
the item master and the order entry file.  Makes it easier to scan and to 
use IBM's database cross reference files.  You can use the RPG RENAME on the 
Fspec to differentiate if necessary.

Use RPG ILE instead of RPG III  or II

Use procedures instead of subroutines as much as possible.  If reasonable put 
the subroutine into the service program.  Document the service program in Notes 
to the point that someone need not look at the code to use the subroutine.

Agree on standards for common reports.  Meaning include the following:  Program 
name, Company name, page number, user id, report desc, date, and time.  Set 
where to place them.  Keep standards for 80 and 132 column reports.

Use externally defined files.

Any many others.  I just wanted to include the ones to vex the most people 
first.






CBeck@good-sam.com on 12/16/99 11:00:46 AM
Please respond to RPG400-L@midrange.com@Internet
To:     Rpg400-l@midrange.com@Internet
cc:      
Fax to: 
Subject:        RPG Standards?

Does anyone have a list of naming standards, or just programing standards that 
they use for RPG?
I am trying to set up a list of standards to follow.  Any help would be greatly 
appreciated.


Thanks,
Chris

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