RE: Missing parameter

There are times when it can be handy to test %Parms in a subprocedure
without optional parameters. Usually that sort of thing is done with

future

planning in mind.

Personally, I try to avoid that kind of thing ... as it can often be
misconstrued as an error (testing for number of parms when the number
of parms is fixed).

That is your prerogative, David. But define "Fixed."

You would not find the following acceptable?

// If more parameters have been added without checking here
// then abort
If %Parms > 5
sendEscape('USR4107': 'Too many parameters to myProc.'
+ ' Complete the maintenance.') ;
EndIF ;

That is one future-proofing approach that I find decidedly valid.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Behind every successful man stands a surprised mother-in-law."
-- Hubert Humphrey