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




Simon Coulter wrote:

On 23/05/2009, at 9:28 AM, James H. H. Lampert wrote:

Well, at this point,

UPDATEFOO SOURCELIB(FOO_TEST) TARGETLIB(FOO_PROD)
or
UPDATEFOO SOURCELIB(FOO_TEST) PRODLIB(FOO_PROD)
or
UPDATEFOO FROMLIB(FOO_TEST) TOLIB(FOO_PROD)

would be close enough for jazz, and conceptually, it's really
neither a
"copy" nor a "merge", although certainly closer to the former than the
latter, as we are applying an updated format to the target/production
library.

If you settle for FROMLIB and TOLIB (which would be desired for
consistency) then you should use the order from and to.

This is what I would expect and so has nearly everyone else weighing in.

You're doing CL, so do what the other CL commands do. Note that the
emphasis is _commands_, by the way, not CL program statements. In CL,
the usual convention is FROM followed by TO whether it is files or
libraries.

Think of what is done at the command line, not deep inside of CL
programs. Your proper audience is a system operator who may or may not
be a programmer, not a CL programmer. This is true no matter how your
shop is structured. Truth is, you'll quickly find that you and everyone
else want FROM then TO, even if they are proficient in CL, RPG, COBOL,
C++, Java, and Perl. You will all still expect it, because the rest of
the command line CL works that way.



Larry Loen
www.applicationperformancegroup.com





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.