|
View previous topic :: View next topic
|
| Author |
Message |
praveena avaluru
New User
Joined: 29 Sep 2010
Posts: 9
Location: bangalore
|
|
|
|
Hi all
The Job Failing with S322 even though TIME=1440 is mentioned in the job as will as the proc step which is running long.
Please let me know what will be the issue.
Regrads
Praveena |
|
| Back to top |
|
 |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
probably wrong CLASS.
most sites with any sense at all,
either (being nice) ignore time=1440
or (being instructive) cancel the job automatically.
| praveena avaluru wrote: |
| Please let me know what will be the issue. |
The issue is that you need to speak with your operations people
and determine which CLASS to use for a long running job. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Please let me know what will be the issue |
Do not use time=1440 for your personally submitted jobs - ever.
Well-managed systems will not allow this - usually by terminating the job before execution even begins.
You need to determine why this process runs so long (or if it is in a perpetual loop) and correct the process. |
|
| Back to top |
|
|
Kausar.S
New User
Joined: 01 Oct 2010
Posts: 4
Location: Mysore
|
|
|
|
Hi praveena,
You try to check which step(program) in your proc is taking more execution time.
Analyze the program to see whether you can improve the performance to run the job successfully. |
|
| Back to top |
|
|
Kavitha SG
New User
Joined: 18 Feb 2011
Posts: 9
Location: Chennai
|
|
|
|
Hi Praveena..
Have you resolved this problem? If so let me know what you did to solve this.. I am also facing the same error. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
You tell us that you have the same problem.
What have YOU researched to resolve this yourself.
What are the standards regarding the use of the TIME= parameter at YOUR site - who did YOU ask to find this out. Some sites will ignore this parameter if coded. Did you ask. |
|
| Back to top |
|
|
|
|
