IBM Systems Application Architecture

Systems Application Architecture (SAA), introduced in 1987,[1] is a set of standards for computer software developed by IBM. The SAA initiative was started in 1987 under the leadership of Earl Wheeler, the "Father of SAA".[2] The intent was to implement SAA in IBM operating systems including MVS, OS/400 and OS/2. AIX, IBM's version of the UNIX operating system, was not a target of SAA, but does have interoperability with the SAA family.

SAA did not define new standards, but selected from among IBM's existing guidelines and software. IBM also purchased some third party software from developers such as Bachman Information Systems, Index Technology, Inc., and KnowledgeWare, Inc.[3] These were intended to be implemented uniformly across all SAA compliant environments.

The standard was "designed to make application programs look and work in the same manner across the entire range of the company's personal computing systems, midrange processors and System/370 processors."[4]

SAA was labeled "complex, obscure, and potentially difficult to learn."[5]:p.xi Under Lou Gerstner IBM later quietly discontinued use of the "SAA" umbrella. By 2001, SAA was being spoken of in the past tense.[6] However many of the individual components of SAA are still in use as of 2014.

Common programming interface (CPI)

The Common Programming Interface attempted to standardize compilers and application programming interfaces among all systems participating in SAA, with the objective of providing "a common programming interface for the entire IBM computer product line - PCs, System/3x, System/370. This implies that under SAA, a program written for any IBM machine will run on any other".[7]

CPI included a number of pieces:[5]:pp.46–51

  • Programming languages — PL/I, COBOL, Fortran, C, RPG and REXX
  • Application generator — IBM Cross System Product (CSP)
  • Database access — SQL
  • Query interface — QMF
  • Presentation interface — the OS/2 Presentation Manager was defined to be and when developed was a full implementation of the SAA presentation interface. IBM Graphical Data Display Manager (GDDM) provided compatible SAA graphics support for MVS and VM.
  • Dialog interface — ISPF represented the text mode dialog interface; OS/2 represented the full graphical interface.

Common user access (CUA)
Main article: IBM Common User Access

Common User Access aimed at providing "a common user interface for the entire IBM product line. A user who sits down at a PC should see the same menus, keyboards and procedures that he would at a 3270 terminal."[7]

Because of hardware differences complete commonality was impossible to attain. IBM created two CUA standards, the Basic Interface for IBM 3270 and IBM 5250 terminals, and the Advanced Interface for so-called "intelligent workstations", or PCs. The keyboard was standardized to the Model M, 101 key, "AT Enhanced" keyboard layout.[5]:pp.39–40

Common communications services (CCS)

Common Communications Services defined the methods by which heterogeneous systems communicated. CCS depended on Advanced Program-to-Program Communications, also known as APPC or LU6.2, Systems Network Architecture (SNA) PU2.1 or Low Entry Networking for peer to peer networking, and SNA Management Services for network control.[5]:p.52

Three types of data links were supported:[5]:pp.56–58

Application Services[5]:pp.58–59 were provided by:

Common applications

OfficeVision was the SAA-compliant successor to PROFS and AS/400 Office for "office automation". The AD/Cycle family of development tools was intended to simplify the development of SAA applications.[5]:p.60

gollark: Well, they seemingly won't.
gollark: Too bad, they are to.
gollark: So you could turn it on for network-facing services or something.
gollark: People seem to *not* resolve it well at the language level. It'd be good if it was switchable per-process.
gollark: HelloBoiVM?

References
  1. "IBM Archives: 1980s". IBM. IBM.
  2. Bride, Ed; Desmond, John (Dec 1989). "Wheeler: father of SAA - IBM VP and General manager of programming Systems Division Earl Wheeler; Systems Application Architecture - interview". Software Magazine. Retrieved June 20, 2012.
  3. "IBM kauft sich für SAA Software-Know-how ein". Computerwoche. 1989-08-25. Archived from the original on 2013-02-10. Retrieved June 21, 2012.
  4. IBM Corporation. "IBM Archives: 1987".
  5. Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8.
  6. Cooper, Charles (November 2, 2001). "Gerstner's legacy and why it matters". ZDNet. Retrieved June 20, 2012.
  7. Perna, Janet. "SHARE 70: Session D010 - SAA Strategy Update: Application Software Support". Archived from the original on 2013-05-03. Retrieved June 18, 2012.

Further reading
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.