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



While I can remember the more common parameters (given a chance I can create a CPYF with fromfile, tofile, members, etc. (and a CRTFILE(*YES) now and then) without prompting. But in a CL program I usually let the prompter format things.

I've heard this is good practice, just in case IBM re-arranges a parameter on you.

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Tuesday, March 06, 2018 3:14 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: qsh from cl

On Tue, Mar 6, 2018 at 2:54 PM, Roger Harman <roger.harman@xxxxxxxxxxx> wrote:
Am I the only one using ||, |<, etc for CL instead of the verbose option?

Not the only one, but I think most people probably don't do enough CL
programming to really keep in mind what those mean. There may also be
some traditionalists who always use *GT and *LE and so forth, and then
for consistency also use *CAT.

Personally, I find that the names for all the parameters are
maddeningly verbose, far more verbose (and far more maddening) than
*CAT and friends. I'm pretty aggressive about omitting parameter names
when I can.

John Y.


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