SAS Software for Learning Community

Welcome to the exclusive online community for all SAS learners.
BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
PhilMStudy2020
Fluorite | Level 6

I have tried using numerous videos, texts and search features here and cannot find out what the issue is with uploading my csv file into enterprise miner. I cannot run the file in SAS Studio without receiving a series of error codes and do not know where to go to find help due to being on the academic on demand version.

ERROR: Error opening file. File =/saswork/SAS_work88EA0000D2CA_odaws04-usw2/#LN00047. System Error Code = 122.
ERROR: Invalid open mode.
ERROR: No body file. HTML5(WEB) output will not be created.
ERROR: Error opening file. File =/saswork/SAS_work88EA0000D2CA_odaws04-usw2/#LN00056. System Error Code = 122.
ERROR: Invalid open mode.
ERROR: Invalid open mode.
ERROR: An I/O error has occurred on file on WORK.CFPBCOMPLAITS.DATA
ERROR: Unix errno = 122
data cfpbcomplaints;
72 infile '/home/u42939927/CFPB/CFPB Test.csv' dlm=',' firstobs=2;
73 input Date_received$ Product $ Sub_product $ Issue $ Sub_issue$ Consumer_complaint_narrative $
73 ! Company_public_response $ Company $ State $ ZIP_code $ Tags $ Consumer_consent_provided? $ Submitted_via $
73 ! Date_sent_to_company $ Company_response_to_consumer $ Timely_response? $ Consumer_disputed? $ ComplaintID $;
74 RUN;
 
ERROR: An I/O error has occurred on file WORK.CFPBCOMPLAINTS.DATA.
ERROR: UNIX errno = 122.
NOTE: The SAS System stopped processing this step because of errors.
WARNING: The data set WORK.CFPBCOMPLAINTS was only partially opened and will not be saved.
NOTE: DATA statement used (Total process time):
real time 0.00 seconds
user cpu time 0.00 seconds
system cpu time 0.00 seconds
memory 470.40k
OS Memory 21160.00k
Timestamp 03/02/2020 05:09:17 PM
Step Count 31 Switch Count 0
Page Faults 0
Page Reclaims 44
Page Swaps 0
Voluntary Context Switches 0
Involuntary Context Switches 0
Block Input Operations 0
Block Output Operations 0
 
 
75
76
77
78 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
89
 
 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Kurt_Bremser
Super User

WORK is a directory SAS creates as soon as a SAS process is started (in your case, it was SAS_work88EA0000D2CA_odaws04-usw2 in /saswork); this directory is used for all kinds of temporary storage (e.g. a HTML file for sending back to the client for display, like your file /saswork/SAS_work88EA0000D2CA_odaws04-usw2/#LN00047). This directory is deleted when a SAS session terminates gracefully, a crash or a forced kill can prevent this, leading to remnants of previous sessions cluttering up the WORK location; therefore my reference to cleanutil.

Most importantly, a library reference named WORK is created for your SAS session there, where datasets like WORK.CFPBCOMPLAITS are stored.

So you should go check for your quota allowance in /saswork on the SAS server, and have your SAS admin check if remnants of crashed SAS sessions are eating into your quota.

If all this does not lead to a solution, you need to check why you need so much space, and eventually ask for more if your project really demands it.

View solution in original post

6 REPLIES 6
PhilMStudy2020
Fluorite | Level 6

The file itself us under 300MB, is this a SAS or hardware issue?

Kurt_Bremser
Super User

You have exceeded the quota set by the system administrator. This is neither a hardware nor a SAS issue. Clean up your WORK. In case this does not immediately fix it, have the system administrator run the cleanwork utility.

PhilMStudy2020
Fluorite | Level 6

Had to work yesterday and am carrying a 19 hour semester load, sorry for not replying sooner.

is WORK the same as workspace in each project folder? Or is a command I need to run?

I am either poor at searching for it or there isn't much help in the community on how this is done.

My Quota in the control center implies I have 5 GB of space and am under 600MB

Kurt_Bremser
Super User

WORK is a directory SAS creates as soon as a SAS process is started (in your case, it was SAS_work88EA0000D2CA_odaws04-usw2 in /saswork); this directory is used for all kinds of temporary storage (e.g. a HTML file for sending back to the client for display, like your file /saswork/SAS_work88EA0000D2CA_odaws04-usw2/#LN00047). This directory is deleted when a SAS session terminates gracefully, a crash or a forced kill can prevent this, leading to remnants of previous sessions cluttering up the WORK location; therefore my reference to cleanutil.

Most importantly, a library reference named WORK is created for your SAS session there, where datasets like WORK.CFPBCOMPLAITS are stored.

So you should go check for your quota allowance in /saswork on the SAS server, and have your SAS admin check if remnants of crashed SAS sessions are eating into your quota.

If all this does not lead to a solution, you need to check why you need so much space, and eventually ask for more if your project really demands it.

PhilMStudy2020
Fluorite | Level 6

I think I figured it out, WORK file in Library. I cleaned up everything from there and the file folder drop down but the large file still bogs down the system too much and ultimately comes back with a "selected file does not exist" when I try to import it in studio.

I think I am just going to break it down into more manageable chunks and try that route.

I appreciate the help

sas-innovate-white.png

Our biggest data and AI event of the year.

Don’t miss the livestream kicking off May 7. It’s free. It’s easy. And it’s the best seat in the house.

Join us virtually with our complimentary SAS Innovate Digital Pass. Watch live or on-demand in multiple languages, with translations available to help you get the most out of every session.

 

Register now!

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 6 replies
  • 6327 views
  • 2 likes
  • 2 in conversation