× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Until now to test the number of parameter in a procedure i always use the %parms bif , but in some example i see the use of the procedure ceedod

CEEDOD retrieves the operational descriptor of a parameter. This can tell you the data type of the parameter and the length of the parameter. This is ONLY valid if an operational descriptor was used (OPDESC has to be specified on the prototype)

CEETSTA tests to see whether a parameter was passed with the *OMIT keyword. This is only useful if you have options(*omit) specified on the prototype. In RPG, you can also check this with the %addr() BIF.

%PARMS checks HOW MANY parameters were passed. It's commonly used to check for options(*nopass) parameters.

All 3 of these are very different things that are used for different purposes.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.