Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
When using the TEXT_FILE READ function in ALL-IN-1 2.4, is there a limit to the length of the record which can be read in? A customer is using TEXT_FILE READ with records which are 906 bytes long, but when he tries to use this, it comes back with an error: "%OA-I-TFOREAD, text file error reading file <file>, 899276 byte record too large for users buffer." It looks like some sort of overflow may have been hit, but I'm not sure what. Can anyone help? Steve.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
208.1 | Questions | SHALOT::NICODEM | Who told you I'm paranoid??? | Wed Mar 11 1992 13:31 | 7 |
If the records are just over 900 bytes long, and the error message indi- cates that it's trying to read something almost 900,000 bytes long, I'm wondering if you have a true sequential file. What is the record terminator? CR? Can you <LIST the file from ALL-IN-1? What type of file is it (e.g., ASCII, WPS-PLUS, DX, other...)? F | |||||
208.2 | There may be a limit | SHALOT::WARFORD | Richard Warford @OPA DTN 393-7495 | Wed Mar 11 1992 18:37 | 8 |
In the first versions of V2, the text DSABs were limited in size. I think it was 256 characters, then it expanded to 512. Not sure what the current size is.... But I would tend to agree with Frank. Sounds like its not really a normal sequential file. Rick |