×
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.
Turnidge, Dave wrote:
SO, create your library that sits above QSYS. Ours is MUSER. Write a
program that
1) deletes the command from your library (MUSER),
2) copies the new command from QSYS to your library (MUSER). At this
time you can rename the command if you wish (for example WRKACTJOB to
WAJ). ...
The compiler commands should be copied from the QDEVTOOLS or QSQL,
rather than QSYS. The compiler commands in QSYS are "proxy" commands to
the QDEVTOOLS or QSQL commands; any change to a proxy command is
reflected in the original command, so changing the command default for
the QSYS command would result in a change for the QDEVTOOLS/QSQL one,
and all the others that are proxy to those commands. By copying your
command directly from QDEVTOOLS, you avoid the proxy commands. Use
DSPCMD to see if the command you want to copy is a proxy command; if it
is, copy the base command in the proxy chain.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rbam6/proxycmds.htm
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.
midrange.com
