Two thoughts...
1) That appears to be a SERIOUS (it said so) DASD error. I suspect that the DASD may have been failing and it kept trying to write it. I would have your operations folks look at that. May need to back up/reload to a different pack.
2) My first thought was "when was the last time a RUNSTATS was run on that table?" But the first thought is likely the cause of the problem.
job is running too long
Re: job is running too long
by BrantleyL1 » Wed Oct 26, 2011 2:01 am
- BrantleyL1
- Posts: 1
- Joined: Wed Oct 26, 2011 1:54 am
- Has thanked: 0 time
- Been thanked: 0 time
-
- Related topics
- Replies
- Views
- Last post
-
- How to determine long running DB2 threads thru JCL
by Avinash Kumar » Fri Sep 08, 2017 4:43 pm - 2 Replies
- 2213 Views
- Last post by Avinash Kumar
Tue Sep 12, 2017 4:44 pm
- How to determine long running DB2 threads thru JCL
-
- Job is taking too long
by abhi.d.leo » Fri May 13, 2011 10:53 am - 6 Replies
- 2353 Views
- Last post by abhi.d.leo
Mon May 16, 2011 3:48 pm
- Job is taking too long
-
- Accomodating Long message into column
1, 2by coldplay1991 » Fri Dec 09, 2011 1:54 am - 14 Replies
- 3874 Views
- Last post by Akatsukami
Tue Dec 13, 2011 3:04 am
- Accomodating Long message into column
-
- Program running in loop.
by XY09 » Fri Jul 16, 2010 9:15 am - 4 Replies
- 2190 Views
- Last post by dick scherrer
Mon Jul 19, 2010 11:27 pm
- Program running in loop.
-
- getting -140 when running DB2 query in rexx
by prachikhanna » Fri Dec 10, 2010 5:18 pm - 8 Replies
- 3351 Views
- Last post by prachikhanna
Wed Dec 15, 2010 4:59 pm
- getting -140 when running DB2 query in rexx