RE: "Real ILE" ( tangent from RPGIII compiler vs. Visual Basic)

Imagine a Domino workflow database.  You create a new document on a new 
subprocedure.

First you document the input, output, and show a sample of how it's used. 
Maybe even document, briefly, how it derives the output (maybe not - the 
documentation for READ doesn't).  Remember, this documentation is for the 
developer using the subprocedure - not for the developer writing the 
subprocedure.  We'll call this the 'Draft phase'.

Next you send it on to the 'Approval' phase.  They either reject it, or 
send it on to the 'Development' phase.  From there it goes on to the 
'Testing' phase.  Then it goes on to the 'Production' phase.  Then it goes 
on to the 'Education' phase.  This is where you show the rest of the 
department how to use it.  Finally it gets completed.  Now they can scan 
this documentation database for your subprocedures.

We actually purchased an extensive Domino Workflow application called EtQ 
on the request of our manufacturing quality department to help with ISO 
audits, etc.  It's got the flexibility to tailor custom workflows like 
this without any additional coding.  Some might think it a bit salty, but 
it's a darn good application.

Another technique is RPGDOC.  I heard of someone working on a RPGDOC to 
work like JAVADOC.  But I must be googling wrong because I can't find it.

Rob Berendt