|
>> Right. If you want to go strictly TCP/IP (drop twinax, drop AnyNet) you >> had to give up your nice Code/400 and go back to SEU. For YEARS. > >YEARS ? - Try days (or even hours!) - the version of Code/400 that GA'd at the >end of Feb (along with V4R2) supports TCP/IP connection. Where did you get the >idea that you'd have to wait for years ? In my haste, I'm sure this didn't come across properly. My previous employer has always had twinax-attached PC's. He looked at going TCP/IP a few years ago, but decided that too many things would break. One of those things was my lone copy of Flex/Edit. If we had been using Code/400 in 1994 and switched to LAN attached PC's, we *would have* lost the "native" connection to the AS/400. That (TCP/IP) connection wasn't restored until 1998. This would be a 3+ year gap in usability/availability, whatever. And, yes, I know full well that I could manually FTP my source around, but that sort of defeats the purpose of having an integrated development system. Buck Calabro +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.