Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Job QP0ZSPWP
0 views
Skip to first unread message
Frank Pötzsch
Oct 30, 2000, 1:14:25 PM10/30/00
to
Hi,
does anyone know anything about the job QP0ZSPWP, it managed to overload my
hardisk in just an afternoon. I think, that it propably was startet by a
qshell command.
does anyone know anything about the job QP0ZSPWP, it managed to overload my
hardisk in just an afternoon. I think, that it propably was startet by a
qshell command.
With best regards
Frank Pötzsch
Michael Mundy
Oct 30, 2000, 7:10:51 PM10/30/00
to
The job name QP0ZSPWP can be used for all sorts of things. It is the default
name given to a job that is started with the spawn() API and spawn() is using
prestart jobs instead of batch immediate jobs. By default Qshell tells spawn()
to use prestart jobs.
name given to a job that is started with the spawn() API and spawn() is using
prestart jobs instead of batch immediate jobs. By default Qshell tells spawn()
to use prestart jobs.
The couple of times I have seen this the shell got caught in shell script
recursion. Usually somebody typed in the name of a file as a shell command.
The file was not a shell script but since the user had execute permission to
the file, the shell tried to interpret it as a shell script. This is normal
behavior for the shell. Then the file had its name in the file. The shell
thought it was a command to run and ran the file again. This goes on forever
...
To make matters worse, using F3 to end the shell session didn't end all of the
jobs that were started by the shell session. V4R4 PTF SF64154 and V4R5 PTF
SF64179 fix this problem.
Mike Mundy
0 new messages