|
View previous topic :: View next topic
|
| Author |
Message |
rahul_jot
New User
Joined: 17 Aug 2005
Posts: 22
Location: Pune
|
|
|
|
I ran a Job to extract rows from a table using ADUUMAIN utility. The number of rows extracted was 7913961.
I was required to run the same Job again after some time. The data in the table didn't change also the query to extract data didn't change. I didn't make any changes to the Job (it is a production Job) But when I ran it second time it abended with SB37 for the output file. I increased the space for it but the Job abended again with same reason. I again increased the size again and then extract was successful. I found that the Job extracted same number of rows. Also the query used was same.
Any Idea why the space error came for the 2nd and 3rd time when there was no space error for the first time. The output file is defined in the Job as
//SYSREC DD DSN=TEMP.SPX1000.PROD.UNLOAD,
// DISP=(NEW,CATLG,CATLG),
// UNIT=TMPSTR,
// SPACE=(CYL,(50,50),RLSE) |
|
| Back to top |
|
 |
die7nadal
Active User
Joined: 23 Mar 2005
Posts: 156
|
|
|
|
It should not have been able to find the Cylinders in the first 5 volumes that it searched. But the volumes should have been available during the 4th run.
From QuickRef
| Code: |
To increase the Volume that it searches you should code, VOL=(,,,6)
You should code this parameter when an output data set will require more than 6 volumes. If the volume count is omitted or 1 through 5 is specified, the maximum allowed is 5 volumes. If 6 through 20 is specified, the maximum allowed is 20 volumes. If the specified is greater than 20, the maximum allowed is a multiple of 15 plus 5, up to 255.
|
|
|
| Back to top |
|
|
rahul_jot
New User
Joined: 17 Aug 2005
Posts: 22
Location: Pune
|
|
|
|
| Thank You!!! |
|
| Back to top |
|
|
|
|
