|
View previous topic :: View next topic
|
| Author |
Message |
Anbutheone
New User
Joined: 08 Oct 2008
Posts: 15
Location: Bangalore
|
|
|
|
Hi,
We are facing issue with one of the SAS jobs. The error message we are getting is
.ERROR: Utility file write failed. Probable disk full condition.
There is backup job that runs during the same time. Even though I increase the work Space in SAS job and resubmit, it fails. However, if I run the SAS job after the backup job is completed it does not abend. It completes without any issue.
Please can you tell me what I need to do in order to increase the work area so the job does not abend with the disk full error. For the present situation I can have mutually exclusive condition with backup job but need to know how to increase the work space so the job wont fail. |
|
| Back to top |
|
 |
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
at a guess I would say when both jobs are running, the work file of both jobs are using the same dasd volume, but there is insufficient space for the work file to extend.
I would ensure sufficient primary space is allocated to fulfil the total space required.
Gerry |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Or, to schedule them to process at different times. |
|
| Back to top |
|
|
Anbutheone
New User
Joined: 08 Oct 2008
Posts: 15
Location: Bangalore
|
|
|
|
We tried increasing both primary and secondayr space. But still it was failing.
Now we are running at different times only. But we need to find a solution to run both jobs at the same time. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Then step one would be go talk with your storage buddies to find out which DASD pool is being used, and is there sufficient free space available to process both jobs at the same time. |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
can you tell what volume(s) the work files were written to ?
Gerry |
|
| Back to top |
|
|
Anbutheone
New User
Joined: 08 Oct 2008
Posts: 15
Location: Bangalore
|
|
|
|
| Actually this job was running fine with SAS 8 version. Now we migrated to SAS 9.1.3. Now only we are getting this error. |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
but running the jobs single stream works OK, so I'm not sure how migrating to SAS 9.1.3 affects it unless more space is consumed with the later release.
The problem still lies in not having sufficient space to satisfy both jobs.
If both SAS vesions are available you could run a test to see if more space is being used.
Gerry |
|
| Back to top |
|
|
Anbutheone
New User
Joined: 08 Oct 2008
Posts: 15
Location: Bangalore
|
|
|
|
Hi,
Yes it is using more virtual memory.
But we increased the space values of the work file. Still it is abending. What else we can do for this? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Have you looked at the SAS web site for information? A quick search with their error message found:
| Quote: |
Usage Note 14705: "ERROR: Utility file write failed. Probable disk full condition." in SAS 9.1 and above
When you receive the following ERROR in your SAS Log:
ERROR: Utility file write failed. Probable disk full condition.
you should check to see if you are coding the SAS System option UTILLOC.
If you are using the default which is UTILLOC=WORK, you need to either
increase your WORK space allocation or change the SAS System option
UTILLOC to reference a different location. See syntax below:
UTILLOC = "location" | ("location1", "location2", ...)
location can be one of the following:
an HFS directory in the UNIX System Services file system.
an ALLOC command that specifies the amount of space to be used for each
utility file.
In SAS 9.1 and above, you can include any of the following keywords
in your ALLOC command: TRACKS, CYL, BLOCK, SPACE, UCOUNT, VOL, UNIT,
STORCLAS, MGMTCLAS, and DATACLAS.
For additional information, refer to SAS Note 11174.
|
As expat said, first and foremost you need to contact your systems storage people for help. The specific volume(s) or storage pool used by SAS for WORK space depends on the way SAS was installed at your site. There is usually a WORK= parameter in the SAS procedure that specifies the amount of work space to allocate; this can be changed via JCL. You may also need to discuss the problem with your system SAS site representative, who may be able to change SAS options to fix your problem as well. |
|
| Back to top |
|
|
|
|
