More on RPG style

David F and Charles W,

You are right to define the Subprocedures high in the mainline section.

From an OOP style, which has more clarity. The purpose of MAIN is "to

introduce objects to each other"
So your style is correct to abstract the actions and sections into
smaller ones. You are introducing a high level object to other
high-level objects/actions, maybe even to the point of:

LoadSubfile()
GetSubFileChangesFromOptionField()
ProcessNewAddsUsingDetailScreen()
PrintAuditReportUponExit()

I tend to divide my code into subprocedures in a program just to

improve

readability, even when there is very little risk of that subprocedure
being called from anywhere else. Each subprocedure will correspond to

a

specific task executed by the program.

D doThis PR
D doThat PR
/FREE
IF not doThis ( )
RETURN
ENDIF;
IF NOT DoThat ( )
RETURN
ENDIF;

I've discovered that this style seems to annoy at least one programmer

Am I justified in coding in this way or am I wrongly using

subprocedures?