|
View previous topic :: View next topic
|
| Author |
Message |
yogalakshmi
New User
Joined: 20 Sep 2007
Posts: 17
Location: cheenai
|
|
|
|
| hi...i gave NOLIMIT for time parameter in job card while submiting the jcl for a cobol program...and i think that job is getting executed infinitely due to some error in the coding..when will it come to end..is there any way to cancel a job submitted ? |
|
| Back to top |
|
 |
murmohk1
Senior Member
.jpg)
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Yogalakshmi,
| Quote: |
| executed infinitely due to some error in the coding..when will it come to end..is there any way to cancel a job submitted ? |
Your query has the answer. Cancel the job manually, if you have authorization. Or ask your OPs team to do it for you. |
|
| Back to top |
|
|
yogalakshmi
New User
Joined: 20 Sep 2007
Posts: 17
Location: cheenai
|
|
|
|
hi,
sorry i am new to this...how to cancel the job manually or how to check whether i have authorization for doing this.. |
|
| Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
| Quote: |
| how to cancel the job manually or how to check whether i have authorization for doing this.. |
In the spool, place 'C' on the left of the job and hit ENTER. Like -
| Code: |
| C SORTJCL JOBxxxxx RACFIDxx 1 CC 0000 PRINT J 605 |
|
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
A mild suggestion....
review Your standards and practices,
usually the "TIME=NOLIMIT" or "TIME=1440"
are not allowed on the testing environment,
they are allowed in production only after a thorough system test
regards
e.s |
|
| Back to top |
|
|
guptae
Moderator
Joined: 14 Oct 2005
Posts: 1208
Location: Bangalore,India
|
|
| Back to top |
|
|
yogalakshmi
New User
Joined: 20 Sep 2007
Posts: 17
Location: cheenai
|
|
|
|
hi murmohk1,
I will try to cancel the job..i can do it only on wed as today and tom are holiday in my office..thanks a lot..it was really useful |
|
| Back to top |
|
|
yogalakshmi
New User
Joined: 20 Sep 2007
Posts: 17
Location: cheenai
|
|
|
|
| THANKS TO ALL OF YOU.. |
|
| Back to top |
|
|
0d311
Guest
|
|
|
|
| yogalakshmi wrote: |
hi murmohk1,
I will try to cancel the job..i can do it only on wed as today and tom are holiday in my office..thanks a lot..it was really useful |
Hmmm... If that job still runs for 2 days, I wonder how much CPU time was wasted... 
 |
|
| Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
0d311,
| Quote: |
| Hmmm... If that job still runs for 2 days, I wonder how much CPU time was wasted... |
In such a scenario, OPs wont allow to run that long. Unless intimated beforehand NOT to cancel the job.
Morevoer, the original post says - due to some error in the coding. I assume this is a test environment (without testing they would not have moved to prod). |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
| Quote: |
Hmmm... If that job still runs for 2 days, I wonder how much CPU time was wasted... |
call the helpdesk (If available ) to cancel the job. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi,
For test JOBs you SUBmit, please avoid using NOLIMIT or 1440 for TIME parameter in future. It's not advisable. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| For test JOBs you SUBmit, please avoid using NOLIMIT or 1440 for TIME parameter in future. It's not advisable. |
Anuj has provided good guidance.
My suggestion is somewhat stronger:
Never use NOLIMIT or 1440 for TIME parameter.
By some means, you need to get the job canceled. Someone is available to deal with system problems. As suggested, call the help desk. If there is none, call operations or your manager. |
|
| Back to top |
|
|
yogalakshmi
New User
Joined: 20 Sep 2007
Posts: 17
Location: cheenai
|
|
|
|
hi all,
OPs had already cancelled the job.It abended with s222. But it had taken more cpu time  As we are just trainees we were not aware of that...thanks for the guidance. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| But it had taken more cpu time |
Do not feel too badly - if your system was well configured, your job would have been "flushed" automatically when the 1440 was detected. |
|
| Back to top |
|
|
|
|
