|
<snip> >use internally defined output and input specs, >with an edit code, and write it out to a disk file >and read the record back in. Used to use this >technique all the time on the S/36 with direct files. >Input is character, output is numeric. Man, that brings back memories! What was that, a one-record file where the I/O never touched the disk? And when we migrated those apps to the AS/400, performance went down the toilet! The other performance killer was the AS/400's inability to block Update files, something that the S/36 did very well. I had never gotten a satisfactory answer to why the AS/400 could not handle that. Yes, I had gotten answers, but none were satisfactory. But I'll save that for another thread. Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.