×
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.
*NLVLIB and *SYSTEM are supported command library qualifications.
The can even be typed on a command line. However the change to the OS
is not relevant for normal use, since user default qualification is by
*LIBL; i.e. unspecified [aka unqualified] command requests search for
the *CMD in *LIBL. As a user, if I type WRKQRY, it searches for the
WRKQRY *CMD [or proxy command] in *LIBL. It is on IBM menus and within
programs where the command invocations are since qualified to prevent
non-system command usages; and the /replace command/ ¿QCARPLCM? or
whatever the API is to explicitly allow redirecting the IBM qualified
command requests.
Thus what Jerry is doing is fine for user command requests at a
command line [and in REXX, CL, CLP, and other functions]. A copied
*proxy* command however, is not the same. Be sure to *correct* any
scenario that currently is just a simple CRTDUPOBJ & customize; i.e. the
customized command for CHGCMDDFT will be the original, *not* the
duplicate.... which may be both highly undesirable *and* not achieve any
desirable results.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: DAILY changes to your System Values and IBM commands, (continued)
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.