Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
IBM Systems Application Architecture
open-in-new
<h2 id="common-programming-interface-cpi">Common programming interface (CPI)</h2> <p>The Common Programming Interface attempted to standardize compilers and <a href="/facts/Application_programming_interface/GMlN4vUr">application programming interfaces</a> 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".<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> </p><p>CPI included a number of pieces:<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a>: pp.46–51 </p> <ul><li>Programming languages — <a href="/facts/PL%2fI/469mVYgd">PL/I</a>, <a href="/facts/COBOL/wVnhqs0k">COBOL</a>, <a href="/facts/Fortran/m1KqjcMU">Fortran</a>, <a href="/facts/C_(programming_language)/Ky2No763">C</a>, <a href="/facts/IBM_RPG/yNSN1Ga1">RPG</a> and <a href="/facts/REXX/hAzh6FeR">REXX</a></li> <li>Application generator — <a href="/facts/IBM_Cross_System_Product_(CSP)/MEVGKDEc">IBM Cross System Product (CSP)</a></li> <li>Communications — <a href="/facts/Common_Programming_Interface_for_Communications/LkFpbdKC">Common Programming Interface for Communications</a> (CPI-C)</li> <li>Database access — <a href="/facts/IBM_SQL%2fDS/Gz7fthd9">SQL</a></li> <li>Query interface — <a href="/facts/IBM_Query_Management_Facility/CpHHqPkj">QMF</a></li> <li>Presentation interface — the OS/2 <a href="/facts/Presentation_Manager/YT8RhzKU">Presentation Manager</a> was defined to be and when developed was a full implementation of the SAA presentation interface. <a href="/facts/IBM_Graphical_Data_Display_Manager_(GDDM)/nKGFLCd7">IBM Graphical Data Display Manager (GDDM)</a> provided compatible SAA graphics support for MVS and VM.</li> <li>Dialog interface — <a href="/facts/ISPF/l5cfE5U3">ISPF</a> represented the text mode dialog interface; OS/2 represented the full graphical interface.</li> <li>Resource Recovery — Common Programming Interface: Resource Recovery (CPI-RR)<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a></li></ul> <h2 id="common-user-access-cua">Common user access (CUA)</h2> <p class="note">Main article: <a href="/facts/IBM_Common_User_Access/4qhD1WvG">IBM Common User Access</a></p> <p>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."<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> </p><p>Because of hardware differences complete commonality was impossible to attain. IBM created two CUA standards, the <i>Basic Interface</i> for <a href="/facts/IBM_3270/QKeJWI7t">IBM 3270</a> and <a href="/facts/IBM_5250/eryQU4Bf">IBM 5250</a> terminals, and the <i>Advanced Interface</i> for so-called "intelligent workstations", or PCs. The keyboard was standardized to the Model M, 101 key, <a href="/facts/IBM_PC_keyboard/CrLJWRIg">"AT Enhanced" keyboard layout</a>.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a>: pp.39–40 </p> <h2 id="common-communications-services-ccs">Common communications services (CCS)</h2> <p>Common Communications Services defined the methods by which heterogeneous systems communicated. CCS depended on <a href="/facts/IBM_Advanced_Program-to-Program_Communication/WqwKJc10"><i>Advanced Program-to-Program Communications</i></a>, also known as APPC or <a href="/facts/IBM_LU6.2/MsvFIIpQ">LU6.2</a>, <a href="/facts/Systems_Network_Architecture/NlFaXaBC">Systems Network Architecture</a> (SNA) PU2.1 or <i>Low Entry Networking</i> for <a href="/facts/Peer-to-peer/wCCdPb0H">peer-to-peer</a> networking, and <i>SNA Management Services</i> for network control.<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a>: p.52 </p><p>Three types of data links were supported:<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a>: pp.56–58 </p> <ul><li><a href="/facts/Synchronous_Data_Link_Control/KoVGwb3j">Synchronous Data Link Control</a> (SDLC) high speed <a href="/facts/Wide_area_network/mAkW4gr3">wide area networks</a></li> <li><a href="/facts/X.25/yaGPqw2Y">X.25</a> packet-switched networks</li> <li><a href="/facts/Token_Ring/mfQj6GSx">Token Ring</a> <a href="/facts/Local_area_network/edUDxJ6J">local area networks</a> (LAN)</li></ul> <p>Application Services<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a>: pp.58–59 were provided by: </p> <ul><li>CCS supported <a href="/facts/IBM_3270/QKeJWI7t">IBM 3270</a> data streams, mainly for existing devices</li> <li><a href="/facts/Document_Content_Architecture/FKljqbyC">Document Content Architecture</a> specified a format for documents to be exchanged among different word processors and other software</li> <li><a href="/facts/IBM_Intelligent_Printer_Data_Stream_(IPDS)/lJyUwzEy">Intelligent Printer Data Stream (IPDS)</a> was a page description language like Xerox <a href="/facts/Interpress/gPUFTg17">Interpress</a> or Adobe <a href="/facts/PostScript/4EeEtnLv">PostScript</a></li> <li><a href="/facts/Snads/hbucAj2M">SNA Distribution Services (SNADS)</a> for <a href="/facts/Store_and_forward/zwM8Amlv">store and forward</a> document transmission</li> <li>Document Interchange Architecture (DIA) for electronic mail</li> <li><a href="/facts/Distributed_Data_Management_Architecture/xYrKQf4m">Distributed Data Management Architecture</a> (DDM) for file sharing and as the base architecture of DRDA</li> <li><a href="/facts/DRDA/VoETfLdB">Distributed Relational Database Architecture</a> (DRDA) for sharing relational databases</li></ul> <h2 id="common-applications">Common applications</h2> <p><a href="/facts/IBM_OfficeVision/V2YAc7F0">OfficeVision</a> 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.<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a>: p.60 </p> <h2 id="further-reading">Further reading</h2> <ul><li>Grochow, Jerrold M. (1991). <a href="https://books.google.com/books?id=vu1QAAAAMAAJ"><i>SAA: a guide to implementing IBM's systems application architecture</i></a>. Yourdon Press. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 9780137857593.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"IBM Archives: 1980s". IBM. 23 January 2003. Archived from the original on December 16, 2004. <a href="https://web.archive.org/web/20041216105801/http://www-03.ibm.com/ibm/history/history/year_1987.html" target="_blank">https://web.archive.org/web/20041216105801/http://www-03.ibm.com/ibm/history/history/year_1987.html</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>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. <a href="http://findarticles.com/p/articles/mi_m0SMG/is_n15_v9/ai_8048960/" target="_blank">http://findarticles.com/p/articles/mi_m0SMG/is_n15_v9/ai_8048960/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"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. <a href="https://archive.today/20130210202313/http://www.computerwoche.de/heftarchiv/1989/35/1151816/" target="_blank">https://archive.today/20130210202313/http://www.computerwoche.de/heftarchiv/1989/35/1151816/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>IBM Corporation (23 January 2003). "IBM Archives: 1987". Archived from the original on December 16, 2004. <a href="https://web.archive.org/web/20041216105801/http://www-03.ibm.com/ibm/history/history/year_1987.html" target="_blank">https://web.archive.org/web/20041216105801/http://www-03.ibm.com/ibm/history/history/year_1987.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8. <a href="0-201-51786-8" target="_blank">0-201-51786-8</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Cooper, Charles (November 2, 2001). "Gerstner's legacy and why it matters". ZDNet. Retrieved June 20, 2012. <a href="http://www.zdnetasia.com/gerstners-legacy-and-why-it-matters-38030327.htm" target="_blank">http://www.zdnetasia.com/gerstners-legacy-and-why-it-matters-38030327.htm</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>Perna, Janet. "SHARE 70: Session D010 - SAA Strategy Update: Application Software Support". Archived from the original on 2013-05-03. Retrieved June 18, 2012. <a href="https://archive.today/20130503091759/http://www.redbug.org/dba/sharerpt/share70/d010.html" target="_blank">https://archive.today/20130503091759/http://www.redbug.org/dba/sharerpt/share70/d010.html</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8. <a href="0-201-51786-8" target="_blank">0-201-51786-8</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"System Application Architecture: Common Programming Interface: Resource Recovery, SC31-6821-01". www.ibm.com. Retrieved 2020-11-10. <a href="https://www.ibm.com/support/knowledgecenter/SSB27U_6.4.0/com.ibm.zvm.v53.cn2v0/toc.htm" target="_blank">https://www.ibm.com/support/knowledgecenter/SSB27U_6.4.0/com.ibm.zvm.v53.cn2v0/toc.htm</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>Perna, Janet. "SHARE 70: Session D010 - SAA Strategy Update: Application Software Support". Archived from the original on 2013-05-03. Retrieved June 18, 2012. <a href="https://archive.today/20130503091759/http://www.redbug.org/dba/sharerpt/share70/d010.html" target="_blank">https://archive.today/20130503091759/http://www.redbug.org/dba/sharerpt/share70/d010.html</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8. <a href="0-201-51786-8" target="_blank">0-201-51786-8</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8. <a href="0-201-51786-8" target="_blank">0-201-51786-8</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8. <a href="0-201-51786-8" target="_blank">0-201-51786-8</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8. <a href="0-201-51786-8" target="_blank">0-201-51786-8</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>Linnell, Dennis (1990). The SAA Handbook. Addison-Wesley. ISBN 0-201-51786-8. <a href="0-201-51786-8" target="_blank">0-201-51786-8</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> </ol>