× 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.


  1.  Home
  2. MIDRANGE-L
  3. January 2018

Re: Checking for missing parameters in CL

My 2¢: I would never test a parameter value for *LE *blanks to determine
whether that parameter had, in fact, been passed. If "%ADDR" (or, in the
future, "%PARMS *LE %PARMNUM()") does the trick, you shouldn't even need to
test for blanks.

- Dan

On Wed, Jan 31, 2018 at 1:27 PM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

Interesting you should find that. I decided to create an RFE
which outlines the exact syntax I wished for in CL/ILE language syntax.

IF COND(%PARMS *LT %PARMNUM(&OPTRUN) +
*OR %ADDR(&OPTRUN) = *NULL +
*OR &OPTRUN *LE *BLANKS) THEN(DO) /* NOT PASSED? */
ENDDO
ELSE CMD(DO) /* KEEP DFLT, ELSE */
CHGVAR VAR(&RUNOPT) VALUE(&OPTRUN) /* REPLACE DEFAULT */
ENDDO


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.