|
You can set the block size when you open the file. Start looking in the UFCB flags then in one of those extensions hung off the UFCB. I don't need to pull out my data areas ... right? Richard Jackson mailto:richardjackson@richardjackson.net http://www.richardjacksonltd.com Voice: 1 (303) 808-8058 Fax: 1 (303) 663-4325 -|-----Original Message----- -|From: owner-mi400@midrange.com [mailto:owner-mi400@midrange.com]On -|Behalf Of Leif Svalgaard -|Sent: Saturday, October 07, 2000 5:38 PM -|To: MI400@midrange.com -|Subject: Re: buffering -| -| -|I would rather not use an OVRDBF to set the block size. Isn't there -|a way of setting that in the UFCB at open-time, maybe one of the -|options in the variable part? -| -|Your idea of copying the whole lot in one go looks good; will try -|that, once I can get it to read 128k in one go. -| -|----- Original Message ----- -|From: Richard Jackson <richardjackson@richardjackson.net> -|To: <MI400@midrange.com> -|Sent: Saturday, October 07, 2000 6:01 PM -|Subject: RE: buffering -| -| -|> I think that you could get it fast more quickly in C but there -|aren't any -|> facilities in C that you can't use in MI. I always found that -|writing IO -|in -|> MI to be a pain. However, I have a suggestion for you: -|> -|> When you execute the IO that pulls in the 128k block from the file, take -|the -|> address of the beginning of the block from the IO feedback area and just -|> copy the whole thing directly into the user space - in other -|words, don't -|> bother to read anything into a buffer, just copy it directly -|from the VMC -|> buffer. Is there something that will copy more than 32k at a -|time or are -|> you stuck with CPYBLA? If not, you have to make four operations. -|> -|> Richard Jackson -|> mailto:richardjackson@richardjackson.net -|> http://www.richardjacksonltd.com -|> Voice: 1 (303) 808-8058 -|> Fax: 1 (303) 663-4325 -|> -|> -|-----Original Message----- -|> -|From: owner-mi400@midrange.com [mailto:owner-mi400@midrange.com]On -|> -|Behalf Of Leif Svalgaard -|> -|Sent: Saturday, October 07, 2000 2:52 PM -|> -|To: MI400@midrange.com -|> -|Subject: Re: buffering -|> -| -|> -| -|> -|Thanks, Richard. -|> -|As always you come through with good stuff. -|> -| -|> -|Language: why, MI, of course. :-) -|> -| -|> -|> -|> -|> Are you using Dick's new sort APIs? -|> -| -|> -|No, a search for "Dick's new sort API" on IBM's sites -|> -|did not turn up anything. -|> -| -|> -| -|> -| -|> -| -|> -|+--- -|> -|| This is the MI Programmers Mailing List! -|> -|| To submit a new message, send your mail to MI400@midrange.com. -|> -|| To subscribe to this list send email to MI400-SUB@midrange.com. -|> -|| To unsubscribe from this list send email to -|MI400-UNSUB@midrange.com. -|> -|| Questions should be directed to the list owner/operator: -|> -|dr2@cssas400.com -|> -|+--- -|> -|> +--- -|> | This is the MI Programmers Mailing List! -|> | To submit a new message, send your mail to MI400@midrange.com. -|> | To subscribe to this list send email to MI400-SUB@midrange.com. -|> | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. -|> | Questions should be directed to the list owner/operator: -|dr2@cssas400.com -|> +--- -| -|+--- -|| This is the MI Programmers Mailing List! -|| To submit a new message, send your mail to MI400@midrange.com. -|| To subscribe to this list send email to MI400-SUB@midrange.com. -|| To unsubscribe from this list send email to MI400-UNSUB@midrange.com. -|| Questions should be directed to the list owner/operator: -|dr2@cssas400.com -|+--- +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.