I/o Error Reading Data
topic :: View next topic Author Message amit4u79BeginnerJoined: 24 Oct 2005Posts: 107Topics: 35Location: Singapore Posted: Thu Dec 22, 2005 5:42 am Post subject: I/O Error during read of a PDS !! Hi Gurus, I have run into an issue which is never heard of by me. I actually had coded a REXX code to run SDSF. Say the rexx was coded in data set 'AAAA.BBBB.CCCC(MYREXX)' and within the rexx I had coded "Alloc DD(ISFOUT) DSN('AAAA.BBBB.CCCC(SDSFOU1)') Shr Reuse". When I ran the REXX thru TSO, my data set which was of LRECL 80 FB got converted into FBA 133. 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. Menu Functions Confirm Utilities Help ------------------------------------------------------------------------------ VIEW AOAJI.TEST.REXX I/O error reading data Command ===> Scroll ===> CSR Name Prompt Size Created Changed ID V AVDTST 65 2005/12/12 2005/12/12 10:12:16 AOAJI _________ DAJWRK 111 2005/11/21 2005/12/12 10:11:23 AOAJI _________ OPCAJCL 10 2005/11/21 2005/11/25 13:39:04 AOAJI _________ OPCRPT 232 2005/11/21 2005/12/14 11:54:44 AOAJI _________ SDSFIN 11 2005/12/12 2005/12/22 18:01:16 AOAJI _________ SDSFOUT 17 2005/12/12 2005/12/22 18:05:44 AOAJI I cannot even HRECOVER as it shows "ARC1007I RECOVER REQUEST 00179459 SENT TO DFSMSHSM" "ARC1001I AOAJI.TEST.REXX RECOVER FAILED, RC=0028, REAS=0000 ARC1128I BACKUP/DUMP COPY DOES NOT EXIST" which is fine as there is no backup copy on ny tape. Is it possible I would be able to retrieve back the stuffs I have lost. As i have a production move after 1 week and I have 4 REXXs for the production move. If I am not able to get it back, I am gone. Pls help me. Thanks, Amit Joshi._________________I did not fail; I have found 10,000 ways that would not work - Albert Einstein. Back to top PhantomData Mgmt ModeratorJoined: 07 Jan 2003Posts: 1056Topics: 91Location: The Blue Planet Posted: Thu Dec 22, 2005 5:53 am Post subject: amit4u79, Try this untested code. Code: //R010 EXEC PGM=SORT //SORTIN DD DSN=AAAA.BBBB.CCCC(
zOS Discussion A website for and by Mainframe Users. zLog Portal Board index Information Board http://www.mvsforums.com/helpboards/viewtopic.php?t=5508&sid=d0ba2e644dac89a663c2c19b950815dc is disabled for maintenance and will be unavailable for some time. Thanks for the patience. In case you’ve any concern, please write to http://www.zmainframes.com/viewtopic.php?t=1201 zOSHelpForums@gmail.com. Thanks. zLog Portal Board index Contact us Delete all board cookies About Us Privacy Policy All times are UTC+05:30 1,368,177 Page visits Copyright © 2013 - 2016. All rights reserved. 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
read error on data file Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] The "Low level I/O error" message usually means your flat binary file is the wrong http://gradsusr.org/pipermail/gradsusr/2016-February/039417.html size. GrADS makes a calculation of where to offset the pointer -- i.e. how many bytes deep into the file it needs to go to read the desired grid. 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 i/o error some kind of precision error). 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. If your file size doesn't match, then figure out where you went i/o error reading wrong in describing the grid or in creating your file. If it does match, then the file may be corrputed somewhere. 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 mark, then you probably have a precision issue. GrADS 2.0.2 should easily be able to read a big binary file, but it may depend on the system you're using to read it. --Jennifer On Feb 1, 2016, at 7:50 AM, Anna Lukianova