RE: RPG instruction

Just off the top of my head, not necessarily in this order of importance.  More to follow ...........

1.  Analysis, analysis, analysis, analysis.....  Converting the problem to a specific syntax is simple
     once you know the majority of the what, when, where, why, who, how, etc
2.  Know your tool set.  Attempt to be familiar with all the options available to you.  Know when and
     why to use a data queue versus a user index versus a logical file, etc
3.  Build applications for maintainability
     A. Top down logic (IE, the 'just' or 'logic' of the program is mainline, the work to accomplish this
          follows)
     B. Readablility
     C. Well documented/self documenting
     D. Reusable code (modules, subprocedures, subroutines, /COPY'ed code, etc)
     E. Standard program structure

Hope this helps .................

-----Original Message-----
From:   JoJo [SMTP:jojo@pulse.net]
Sent:   Tuesday, July 18, 2000 12:24 PM
To:     RPG400-L@midrange.com
Subject:        RPG instruction

I am an RPG instructor and would appreciate input from the "field". 
 
We teach RPG in two parts - the first semester we teach RPG/400 and the second semester we teach RPG-IV.  During the first semester, we also hit some of the high points of RPG-II.  I teach the RPG/400 class.

 
Are there some hot topics you would like to see covered to better prepare students for the "real world"?
 
I programmed for many years, but am just teaching now and I depend on my contacts in the trenches to help me construct my lesson plans to meet the needs and demands of this dynamic field.

 
Thanks so much.
 
Pam D