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



Henrik wrote:

> Is there a way to code varying number of list
> elements in a single CLP command?

Not that I've discovered. I've always gone the QCMDEXC or QCAPCMD route.

> CPYF FROMFILE(&FILEA) TOFILE(&FILEB) FROMMBR(&FROMMBR)
> TOMBR(&TOMEMBER). This works fine even if the value of
> &FROMMBR is '*N' - indicating that no specific value
> is given for FROMMBR()

This is slightly different from using *N in a list. In this case *N is used
as a place holder for a positional parameter. Although in your example you
have specified the keywords you could have written it as

CPYF &FILEA &FILEB &FROMMBR &TOMEMBER

In this case a blank value of &FROMMBR would not do, so *N can be used. *N
cannot be used in a simple list, but can be used in a mixed list as a place
holder separating parameters of unlike values. It seems the design logic is
that place holders are not needed in simple lists as all the values are
alike. However, they are needed for positional parameters and mixed lists.
This is slightly unfortunate as "not needed" is not necessarily the same
thing as "not useful").

Dave...
               _________  ,___o
             __________   _\ <;_
           ___________   (_)/ (_)       http://www.twickenhamcc.co.uk
=======================================================
The opinions expressed in this communication are my own and do not
necessarily reflect those of my employer.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.