ttist25
asked on
Delete jobs from output queue in ISPF
Hello - I've submitted some jobs that are stuck in the output queue. I can see these jobs by typing st and hitting enter.
The jobs show as:
JOB USERID#(JOBnnnn) ON OUTPUT QUEUE
how can I kill one of these jobs?
TIA
The jobs show as:
JOB USERID#(JOBnnnn) ON OUTPUT QUEUE
how can I kill one of these jobs?
TIA
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
DA (Display Active) shows processes (batch jobs, started tasks, or TSO sessions) that are active, that is running.
ST (STatus) shows processes that are either active or have ended and have output on the spool.
P will cancel a process that is running and purge the output.
PO will purge the output only, the process has to have already ended.
The advantage of PO over P, is that you will not accidentally cancel a process that is still running.
You can typically only get rid of output for processes that have ended.
You can cancel a process or purge output for a process that was submitted by somebody else if system security has been setup to allow it. Most sites will typically restrict this, so you may not be able to.
ST (STatus) shows processes that are either active or have ended and have output on the spool.
P will cancel a process that is running and purge the output.
PO will purge the output only, the process has to have already ended.
The advantage of PO over P, is that you will not accidentally cancel a process that is still running.
You can typically only get rid of output for processes that have ended.
You can cancel a process or purge output for a process that was submitted by somebody else if system security has been setup to allow it. Most sites will typically restrict this, so you may not be able to.
ASKER
Thanks again.
ASKER
First - THANK YOU. I'm such a mainframe noob that it's not even remotely funny. It's so difficult to find answers re: mainframe environment. It's nice to know you are there.
I did some reading last night and I think I did this in a test environment inside SDSF. I was initially running "st" from ISPF command shell and trying to kill my job there. Doh.
Last night I went into my test environment, went to SDSF, entered DA, found my user, and placed a "p" in front of it and it killed the user process (or job - still shaky on the terminology).
If I do the same thing from SDSF (except typing ST instead of DA) will I be able to see and kill my job?
What is the benefit of PO over p?
Also, I'm submitting the job (it compiles code) under another userid - will I still be able to kill that job even though I'm not logged in as that user?
Thanks again!