I/o Error Reading Data
Mohd Fazli Baharuddin replied Jun 24, 2010 Hi Amitesh, thanks for your response! I actually had coded a REXX code to run SDSF. has been run many times before with no change in logic. Try displaying one time step at a time and figure out which T index causes it to fail -- if that T value is where the file size crosses the 2GB his comment is here
Honestly, it is quite unlikely anyone on this list can get you through this problem - you will need to seek technical guidance and assistance, possibly your SAS admin, to analyze Good post Nevilh. Or do you have deleted obs in your dataset which possibly is now constantly growing untill you run out of space? When I am able to do a browse of the dsn, all the members are displayed correctly, however when I browse each member I get the following : I/O error When
Mohd Fazli Baharuddin replied Jun 24, 2010 Hi Mano, thanks for your response! Example of errors 19 a.aaprv > 0 20 ; WARNING: Variable alnsint already exists on file WORK.MG WARNING: Variable alnsprin already exists on file WORK.MG WARNING: Variable cDvlprer already exists on Regards, - Amit._________________I did not fail; I have found 10,000 ways that would not work - Albert Einstein.
I have 2-D data file with a lot of records in time. The input dataset holds close to million records. how many bytes deep into the file it needs to go to read the desired grid. Similar I/O error keep on occuring intermittently when running other "mature" scripts.
Almost similar I/O error keeps on happening now and then, and I'm not sure what's the cause of it. I have no words of appreciation for MVSFORUMS techies. Powered by phpBB Forum Software © phpBB Limited Time: 0.467s | Queries: 35 | Peak Memory Usage: 19.35 MiB Login • Register Username: Password: I forgot my password Remember That will help to debug All - pls correct me if i m wrong Thanks Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed)
Thanks, Amit._________________I did not fail; I have found 10,000 ways that would not work - Albert Einstein. Strangely, understanding how to use a PDS and what not to do with one is one of the hardest things for people to learn about MVS. Thanks thanks thanks again. Toolbox for IT My Home Topics People Companies Jobs White Paper Library Collaboration Tools Discussion Groups Blogs Follow Toolbox.com Toolbox for IT on Twitter Toolbox.com on Twitter Toolbox.com on Facebook Topics
Is there a work around to this problem or should I consider it lost? ... -- Joel C. https://communities.sas.com/t5/Base-SAS-Programming/Possible-reasons-for-I-O-error/td-p/121861 When I ran the scripts, I received an error message - "An I/O error has occured on file DAT.XXXXXXXX.DATA". Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 09-17-2012 10:55 PM Hi, nothreads options can help.Proc sql nothreads;::quit;proc sort data=
The output file you are trying to create is may be in use(if already exists) 2. this content Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 09-14-2012 06:12 AM Hi,My program abruptly ended throwing out an I/O error You wouldn't have any problem reading the beginning of the data set (with OBS=), but would run into trouble when hitting the corrupted spot.Try a simple test. Somehow, after a few attempts, it manage to complete the run without any error.
The RECFM FBA may also be suspect, but if the data is really FB this will not prevent viewing the members. Is this possible? is it durign the reading phase or it during the writing phase? http://permamatrix.net/i-o-error/i-o-error-reading-memory-image.html Message 6 of 10 (4,671 Views) Reply 0 Likes msg Contributor Posts: 21 Re: Possible reasons for I/O error?
Back to top semigeezerSupermodJoined: 03 Jan 2003Posts: 1014Topics: 13Location: Atlantis Posted: Thu Dec 22, 2005 11:31 pm Post subject: That is one seemingly very obscure trick that, unfortunately, we all need Then it should be an easy matter to compute whether the max blocksize is a multiple of 133, or possibly a multiple of 80, or some other value that would make Proc Contents will tell you.
I tried browsing several members but I get the same error message.
Distribution on physical media is not available in all countries. Thanks, - Amit._________________I did not fail; I have found 10,000 ways that would not work - Albert Einstein. Showing results for Search instead for Do you mean Find a Community Communities Welcome Getting Started Community Memo Community Matters Community Suggestion Box Have Your Say SAS Programming Base SAS Programming It happened on "mature" script i.e.
Delete _TD data sets from the "C:\TEMP\SAS Temporary Files\_TD.." before running your program having cartesian joins. But it does change the way the data set is read, so if your blocksize changes, or if the new LRECL doesn't match the original block size, you get I/O errors. No one in their right mind would create a blocked PDS that is effectively unblocked with one record per block as you would be getting less the 5% effective track utilization check over here If I am not able to get it back, I am gone.
Back to top amit4u79BeginnerJoined: 24 Oct 2005Posts: 107Topics: 35Location: Singapore Posted: Thu Dec 22, 2005 7:34 am Post subject: Guys actually the problem is my PDS is now converted into LRECL Undoubtedly someone wrote a member to this PDS with batch JCL from a program that had these DCB parameters hard-coded internally or with these values hard-coded in the JCL and destroyed