×
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.
You aren't very clear on what is meant by "interactive mode". Do you
mean that you're running something like the following from a CL program
an in interactive job?
STRQSH CMD('db2 something something')
If so, then all you have to do is set QIBM_QSH_CMD_OUTPUT to NONE prior
to the STRQSH.
ADDENVVAR ENVVAR(QIBM_QSH_CMD_OUTPUT) +
VALUE(NONE) REPLACE(*YES)
STRQSH CMD('db2 something something')
If by "interactive mode" you really mean that the user is running STRQSH
interactively and keying commands into the command-line, then the only
way I know to suppress output is to have the user type the appropriate
commands to redirect the output to /dev/null
If neither of this is what you meant by "interactive mode" then please
clarify what you meant...
Jeff Young wrote:
When using the db2 function to run an sql command from QSH, is there
any way I can suppress the terminal session when in interactive mode?
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
