Did the problem arise for an exported procedure called by anothermodule?
I created RFE 117030 to address that problem.https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=117030
Briefly described the problem is that the compiler does not enforce a
prototype for exported procedures. That can lead to a situation where
procedure interface does not match the prototype (stored in a /copymember)
and where a caller, that relies on the prototype, passes the wrong<br />
parameters to the procedure.
It is really nice that we no longer have to include the prototype for
private procedures. But for exported procedures (Keyword: "export") the
compiler MUST enforce the presence of a prototype.
Just my 2 cents.