|
Dare wrote: >I should have known with my 12 years on AS/400. >Could someone lecture me on SAA. What is it? How is it used? What are the >Pros and Cons? What happen to it? SAA stood for "Systems Application Architecture", and was meant to be a framework for developing (reasonably) portable applications on IBM systems. One of the things I did not throw out before our move to the new lab building in Markham was a copy of the "SAA Overview" book (5th edition, December 1990). I'm not sure if there ever was an official statement to the effect that SAA is dead, but basically I don't think anyone really cares anymore. In some ways, though, SAA is is still alive since some products (like RPG III and SQL) still include flagging of non-SAA elements. Was it ever really put into practice? I really don't know since that would require a case of successfully moving an application from one SAA platform to another with little effort. What were the pros and cons? The pro is that you can port an app relatively easily between different IBM platforms. There were a lot of cons: A lot of powerful platform specific functionality was missing from SAA, and so you really had to force yourself into using a narrow subset of the functionality available to you. Initially, AS/400 (and S/38) programmers were up in arms since there was very little in SAA that midrange programmer could use. Cheers! Hans Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.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.