BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
gskn
Obsidian | Level 7

Hi 

 

we are getting below error for PROC REPORT step. 

 

ERROR: Out of space writing to file SYS000XX

 

I tried to increase work space but failed with same error. 

 

can anyone help with error. 

1 ACCEPTED SOLUTION

Accepted Solutions
gskn
Obsidian | Level 7

The issue is now resolved.
We added option FILESPPRI and FILESPSEC and it worked.

 

 

 

View solution in original post

10 REPLIES 10
Kurt_Bremser
Super User

Monitor the work location while the step is running, to see if you actually write data there.

 

Check if there are quotas for the user running the step that are encountered before the filesystem as such runs out of space

 

Some systems impose a 2GB limits on filesize as default when a new user is created; less probable reason for your problem IMO, but nevertheless ...

 

If that does not give you a clue, post the proc report code and some information about the dataset you run it from (involved variables - type and size, number of records)

ballardw
Super User

How many records do you think you are writing to your output?

Are you sure that you want Proc Report? Report generally means "read by humans" somewhere along the line and running out of space infiles tends to make me think that you may be writting something bigger than most people want to read.

 

You may want to show the code and messages from the Log. Paste into a code box opened with the Forum {i} icon.

gskn
Obsidian | Level 7

it is PROC REPORT and ODS PDF (writing a report in PDF). 

 

Is there any difference in SAS 9.2 vs SAS 9.4 (with respect to options like STYLE= etc  for ODS and options like HEADSKIP, SPACING=1 for proc report). 

 

We recently moved to SAS 9.4. 

jberkes
Calcite | Level 5

I'm having the same problem and here is my code

                                          
 DATA   DETAIL;                           
 INFILE DETAIL;                           
   DROP BEGDATE FUNCDT BILLDTEN;          
                                          
       INPUT @1  ROLLUP      $5.          
              @7  BEGDATE     $10.        
             @18  DETAIL      $8.         
             @27  FUNC        $4.         
             @32  FUNCDT      $10.        
             @75  BILLIND     $1.         
             @77  BILLDTST    $10.        
             @88  BILLDTEN    $10.        
             @99  UNITS       14.5        
               @99  UNITSX    $CHAR14.    
             @115  DESC        $35.       
             @150  TYPE        $1.        
               ;                          

 IF FUNC ~= 'MB10' THEN DELETE;
 RUN;                          
 ODS PDF FILE='PSXXXX.PDF'; 

 PROC REPORT DATA=DETAIL;          
RUN;                              
ODS PDF CLOSE;        

 

the detail is 139,448 rows and the result set is 36,677 rows.   Granted, that's too many for a report but I'd like to know if there is solution to the out of space error.             

Kurt_Bremser
Super User

I ran a similar experiment and the result looked like this:

NOTE: The data set WORK.TEST has 58407 observations and 9 variables.
NOTE: DATA statement used (Total process time):
      real time           0.19 seconds
      cpu time            0.06 seconds
      

33         
34         ods pdf file='$HOME/test.pdf';
NOTE: Writing ODS PDF output to DISK destination "/home/XXXX/test.pdf", printer "PDF".
35         proc report data=test;
36         run;

NOTE: There were 58407 observations read from the data set WORK.TEST.
NOTE: The PROCEDURE REPORT printed pages 1-2124.
NOTE: PROZEDUR REPORT used (Total process time):
      real time           1:13.75
      cpu time            38.56 seconds
      

37         ods pdf close;
NOTE: ODS PDF printed 1426 pages to /home/XXXX/test.pdf.

No issues.

Peak usage of WORK throughout the process was ~30 MB.

 

What operating system(s) are your SAS installations running on?

jberkes
Calcite | Level 5

MVS SAS 9.4 

 

Z/OS   V02R01M00

 

Since yours worked I'll try a few things with mine to see if I can get it working

 

Thanks

Jim

Kurt_Bremser
Super User

OK, that explains the SYS000XX file name. That is a generic temporary file name typical for mainframe operations. It might be that this file is created in a place on z/OS (apart from your WORK) where space is actually very low.

Have a talk with the z/OS operators, so they monitor your SAS job to determine where you are running out of space.

gskn
Obsidian | Level 7

The issue is now resolved.
We added option FILESPPRI and FILESPSEC and it worked.

 

 

 

jberkes
Calcite | Level 5

FILESPPRI=1000   solved my error

 

Thanks for the help

Jim

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

How to Concatenate Values

Learn how use the CAT functions in SAS to join values from multiple variables into a single value.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 10 replies
  • 8394 views
  • 1 like
  • 4 in conversation