Allow Subprocedure Exported Name to appear on the EXPORT keyword of DCL-PROC

When building RPG IV modules, the export name of Subprocedures must appear on the Prototype's EXTPROC keyword. If there is NO prototype, it may appear on the DCL-PI's EXTPROC keyword. However, if there is no Parameter List, often the DCL-PI does not exist. The Prototype only exists so caller's can access the subprocedure in "this" linked module or *SRVPGM.

 When I build code, I create the *MODULE object and include the /INCLUDE of the prototype to verify that it is in sync with the subprocedure implementation. 

However, if I specify EXTPROC('myFoo') on the prototype and on the implementation I get a compiler error. 

This moves the naming of the subprocedure (as exported away from the implementation. 

I want an "export as" capability on the implementation body and the intuitive place it should go is on the EXPORT keyword. 

Right now I have to depend on the Prototype being specified and /INCLUDE'd into the implementation source, or use EXTPROC on the DCL-PI which may not exist. 

One centralized way to specify the name while developing code, vs the external way (using the Prototype and the EXTPROC) is needed.

  // SRCMBR(MYPROTOS)
  dcl-pr MYFUNC EXTPROC('sendCGIHeader');
  
  // SRCMBR(CGIHELPERS)
  
   dcl-proc sendCGIHeader EXPORT('sendCGIHeader');
   
    // body of implementation goes here.
   end-proc;