[RPGNext] Encapsulating file access in Service Programs

["Richard Rothe" <RichardRothe@xxxxxxxxxxxxxxxxx>]

Title: Message

I am beginning to encapsulate file access in a "Service Orirtented Architecuture" as described in a previous post by Aaron Bartell.  It is working very well.

 

What is the preferred method of providing a return code of the file operation to the calling program ?  Should I provide a return code on every procedure that I write ?

Or, just provide a procedure to determine the status separately ?  Like PartIsFound for determining if a part is in the Item Master. 

 

Also, I've seen where others have standardized on always passing data back using the Procudure interface and never parameters claiming that the parameters should only be used for input to the procedure.  If multiple fields need to be returned, a data structure is used.