The first thing you should do is make a calculation of what the file size should be: xsize * ysize * zsize * tsize * esize * number-of-variables * 4 (bytes) If your file has some z-varying variables and some non-z-varying variables of if your data is sequential this calculation is a little trickier, but you get the idea. Code: //R010 EXEC PGM=SORT //SORTIN DD DSN=AAAA.BBBB.CCCC(MYREXX), // DISP=SHR //SORTOUT DD DSN=AAAA.BBBB.CCCC.MYREXX.PS, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(10,1),RLSE) // DCB=(LRECL=80,RECFM=FB) //SYSOUT DD SYSOUT=* //SYSIN DD * SORT FIELDS=COPY OUTREC FIELDS=(2,80) /* If you are able to successfully download your REXX member into the PS, then you can save it into a different PDS. I'm running a script locally (i.e. It happened on "mature" script i.e. check over here
Faced same problem and solution worked. manoharsoft replied Jun 24, 2010 Hi, An I/O Error can occur for the following reasons 1. The table contains 234,773,795 rows. 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 to use at least once in our careers. http://ibmmainframes.com/about12578.html
All rights reserved. If the file read command returns an error, you get the message that tells you how many bytes it was trying to read from the file (in this case 1144) and the offset it was using (in this case -2129859208, which isn't right and looks like some kind of precision error). 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 me Hide my online status this session Communities Base SAS Programming Register · Sign In · Help DATA Step, Macro, Functions and more Join Now CommunityCategoryBoardLibraryUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. 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 file WORK.MG WARNING: Variable cDvlpmnt already exists on file WORK.MG ERROR: An I/O error has occured on file DAT.MBASE100618.DATA NOTE: Table WORK.MG created, with 0 rows and 32 columns 21 quit; NOTE: The SAS System stopped processing this step because of errors NOTE: PROCEDURES SQL used (Total process time): real time 2:11.05 cpu time 6.14 seconds Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving...
If your file size doesn't match, then figure out where you went wrong in describing the grid or in creating your file. Document information More support for: z/OS family Software version: 310 Operating system(s): z/OS Reference #: PI25182 Modified date: 2014-11-04 Site availability Site assistance Contact and feedback Need support? on my computer) to populate a dataset. I'm assuming here the original data was not RECFM VB.
zLog Portal Board index Information Board is disabled for maintenance and will be unavailable for some time. Also, it would have been helpful in the beginning to share the SAS log error / diagnostic messages and also your SAS code (a LIBNAME statement maybe)? If it was, about the only way to determine a compatible LRECL and BLKSIZE is to find the largest BLKSIZE and then try an LRECL of that value minus 4. Delete _TD data sets from the "C:\TEMP\SAS Temporary Files\_TD.." before running your program having cartesian joins.
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 the "source file" you wish to read. https://communities.sas.com/t5/Base-SAS-Programming/Possible-reasons-for-I-O-error/td-p/121861 Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 09-18-2012 04:14 AM I would say, I/O error can be very vague.It would be of great help if you could post the error, and give us some details about the table you are trying to process and the type o data manipulation.Could be a corrupted data set, as Astounding said.Could be the WORK library running out of space. Pls try and tell us what happens. Until you fix the LRECL and BLKSIZE values to something that is consistent with the old data you will continue to get I/O errors as either the physical blocks in the PDS will be longer than the current BLKSIZE or the physical blocks will not be a multiple of the current LRECL, or both.
Back to top akhil2490BeginnerJoined: 13 Apr 2007Posts: 1Topics: 0 Posted: Mon Jun 01, 2009 5:21 am Post subject: Looking into archives always helps. check my blog Once you know the correct BLKSIZE and LRECL, use PDS85 commands to set correct values, or JCL techniques previously mentioned in this thread to set those values. Pls help me. After an attempt to rerun the script, it was successful.
But, the full run is not successful. And now when I came outside the data set and tried again accessing the data set it goes in the member list, but when I tried browsing or viewing or editing the members, it shows "I/O error reading data" on the top right of the screen like the one below. Thanks in advance, Lukianova Ann. _______________________________________________ gradsusr mailing list gradsusr at gradsusr.org
Message 7 of 10 (4,671 Views) Reply 0 Likes Geraldo Occasional Contributor Posts: 11 Re: Possible reasons for I/O error? And don't forget that the WORK library is normally shared between all SAS processes running in the machine.Cheers from Portugal.Daniel Santos @ www.cgd.pt Message 9 of 10 (4,671 Views) Reply 3 Likes msg Contributor Posts: 21 Re: Possible reasons for I/O error? Data never sleeps View solution in original post Message 2 of 10 (8,887 Views) Reply 0 Likes All Replies Solution 09-14-2012 06:55 AM LinusH Respected Advisor Posts: 4,522 Re: Possible reasons for I/O error?
Is there a way of fixing it? PDSes are especially strange because the data set has an LRECL, but if you were to use IEBGENER against the PDS as a whole (no member name), you'd read the directory which is always F 256. I checked the SAS Work directory and we have enough space.I re-ran the program but the same error appeared. Pls help me.
Its been so long since I had to do it I forgot the detail. The admin suggested that there was another memory intensive app sharing the server which might have used up resources. The code has been split into simple steps and currently being tested in Data step. have a peek at these guys Check data set block sizes." Now I do not know how to get my stuffs out of this PDS as SDSF has changed the LRECL and BLKSIZE of my original data set.
Subscribe You can track all active APARs for this component.