|
> -----Original Message----- > From: rob@dekko.com > > 1) I don't take grief. I see a problem - I report it. > 2) Maybe we push the envelope a little harder. More data, different > applications, more sql. I don't take grief, either. I just don't seem to run into the problems you do. And I was the Manager of Architecture for the world's largest AS/400 software company - we pushed the envelope, too. BPCS, AS/SET and AS/NET definitely used some of the more advanced features of the AS/400, but that was a while ago. Since then, I've never had a problem other than one time getting TCP/IP to work (which turned out to be a firewall configuration error, not the AS/400's fault), and one time the machine threw a disk drive and kept trying to tell me for nearly a month until I finally looked at the QSYSOPR message queue. I called IBM and they had replaced the drive within one day (4 business hours). Then again, I don't do a lot of SQL, so that may be a difference. > But heck, I can remember when the AS/400 > RPG had a > one file limitation. Uhm. When was this? Don't seem to remember that. We ported BPCS from a S/38 to a Silverlake (pre-release AS/400) and I don't rememeber that particular shortcoming - it would have played havoc with BPCS, I can assure you <grin>.
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.