|
View previous topic :: View next topic
|
| Author |
Message |
vkrishnakumar85
New User
Joined: 11 Dec 2008
Posts: 4
Location: india
|
|
|
|
Hi all,
For purging a job i tried giving the options C and P umpteen times .. but they cudn help much. i am unable to purge my job. when we give DA in the spool, it shows the active jobs/users and the amount of CPU time it utilizes. my job is kinda in sleep mode. it is using 0 cpu time and still is running. the worst thing is that it has kept the files locked. kdinly tell me if ther is some other way to cancel my job.
regards,
KK. |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello and welcome to the forum,
When you have a question it is best to start a new topic for your question rather than reply to a topic that has been inactive for almost a year.
I've created a new topic. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Suggest you talk with the production support, scheduling, or computer operations people. They can cancel the job.
How long has it been "asleep"? If you job needs a very large file that has been migrated, it may take a while to recall the file.
Might there be an outstanding console message waiting on some operator reply? |
|
| Back to top |
|
|
vkrishnakumar85
New User
Joined: 11 Dec 2008
Posts: 4
Location: india
|
|
|
|
Hey Hi Scherrer,
Got it resolved. Contacted the System Support team and they purged me job. Thanks a lot for your suggestion.
KK. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Up through z/OS 1.8 or 1.9, if a job is running as DISCRETIONARY in Workload Manager, and the job is not getting CPU time due to higher priority workloads running, and the job is canceled, the cancel command would not take effect until the job started getting CPU time. This was changed in either z/OS 1.10 or 1.9 to allow the cancel command to take effect even if the job isn't getting CPU time.
If this is the case, you need to get the operators or system support group to change the service class of the job to one that gets CPU time -- at which point the job will be immediately canceled (the cancel command is still in effect, just delayed until the job can be canceled). So contacting the systems support group is the correct action in such a case. |
|
| Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007
Posts: 131
Location: At Desk
|
|
|
|
Thank you Robert.
Detailed explanation would be certainly helpful  |
|
| Back to top |
|
|
|
|
