You *might* encounter an RNQ0222. It's not guaranteed... it depends on
what happens to be in memory at the spot where the parameter address
would be. Most of the time, that memory would contain an invalid
pointer, and therefore you'd get an RNQ0222. But, if by chance it
happens to be a valid pointer, you'll simply access an unexpected area
The only correct way to handle "*nopass" parameters is to check %parms.
On 4/17/2012 9:16 AM, David Gibbs wrote:
You'll encounter an RNQ0222 error if you try to access a parameter
that is unpassed within the called program.
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact