×
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.
Does any one have a better idea of how to determine beyond a shadow of
a doubt from within a program that it is running within the QSHELL
environment?
I have a program that can run normally via the CALL command or within
QSH via a symbolic link. I want the default output to be different
depending on where it is running. I do not want the user to have to do
anything special external to the program. It must be transparent.
My current thoughts are:
o getppid() to locate the parent process ID
o Qp0wGetJobID() to get qualified job name for the parent pid
o if parent job name is QZSHSH then running in QSHELL
I expect this will work as I want when the program is invoked from the
QSH command line but I think if it is used in a sequence of commands
via indirection (e.g., find -> grep -> mypgm -> something else) then I
think multiple jobs are spawned and the parent might not be QZSHSH.
Ideas?
Might be a few days before I get to address this issue again.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
