Re: MCH3402 on CEETRC

LFord@xxxxxxxxxxxxxxxxxx wrote:
> 
> The suggestion of passing the *OMIT resolves the problem.  Very
> interesting.  Thank you so much for the suggestion!
> 

Lori, glad that helped.  If you have other programs that call CEE APIs,
its worth checking that they pass all the parameters.

The problem with not passing the parameters is that you don't always get
a nice noisy exception to tell you there's something wrong.  It's a
matter of chance as to what the API happens to find where the parameter
should be.  a) If there isn't a pointer there, it will think you passed
*OMIT and it will be fine.  b) if there _is_ a pointer there, and it
doesn't happen to be "important", the API might write something to it,
and nothing noticeably bad would happen.  c) If there is a pointer
there, and it does happen to be important, something bad might happen
that you don't notice until much later, long after you could connect it
with your API call.  

And it can vary from day to day and job to job what the API happens to
find there; a program with a bad CEE call might run apparently fine for
years, and then suddenly start causing problems.