Re: Multiple parms to procedures

Hans,

At 09:00 AM 7/17/98 -0400, you wrote:

>>I code I/O parms without the CONST/VALUE.  One per variable.  I use *OMIT
>>or *NOPASS if it might be useful to retrieve a subset of the values.  I
>>always test using CEETSTA API and not %ADDR because of the restrictions on
>>CONST/VALUE parms.
>
>Why complicate things by using an API?  A couple of comments:
>
>1) When using *OMIT, I don't see any reason to avoid using %ADDR to
>test if the parameter is omitted.  After all, OPTIONS(*OMIT) applies
>only to reference parameters where there is no problem using %ADDR.

>2) When using OPTIONS(*NOPASS), the better way to check what parms
>are missing is to use BIF %PARMS.  Note that if a parm is omitted
>using *OMIT, it is still considered a passed parameter by %PARMS.

 What are the guidelines / differences using *OMIT over *NOPASS?

 -mark

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---