DOCSLIB.ORG

The SAS System Under Windows 3.0 and OS/2.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The SAS System Under Windows 3.0 and OS/2.0 224 Host systems and Environments THE SAS SYSTEM UNDER WINDOWS 3.0 AND OS/2 2.0 Wanda Thomas SAS Support Staff Bureau of the Census ABSTRACT the benchmarks was an 80386/33 IBM clone with an 80387 math co-processor, 8 MB of RAM and a 728K disk Microsoft WINDOWS 3.0 and OS/2 2.0 offer cache. The operating environments and SAS software alternatives to running the SAS system on the PC had the following specifications: platform. Microsoft WINDOWS, a DOS-based environment, features multitasking, virtual memory IBM OS/2 2.0 capabBities, and other enhancements to conventional OS/2'S version of the WiNDOWS environment DOS processing. OS/2 2.0, another operating Microsoft WINDOWS 3.0 system, can process DOS, WINDOWS, and OS/2 SAS 6.06 for OS/2 applications. OS/2 also offers some major SAS 6.07 Experimental Release for WINDOWS 3.0 technological breakthroughs for PC-based processing including 32-bit addressing and a flat memory model The benchmark programs listed below consisted of a that can provide users with more power and flexibility series of 12 DATA and PROC steps: than what is available under DOS. The SAS Support Staff conducted benchmarks on Base SAS software 1. DATA STEP - (Create 10,000 Records) that U1ustrate SAS performance under these environments. 2. PROC SORT -- (Sort Ail Records by 2 Variables) BACKGROUND 3. PROC FREQ .- (All Records) The ability of the SAS system to take advantage of the new technology proves to be a definite plus for the 4. PROC TABULATE - (All Records) SAS programmer. Because the DOS operating system has inherent limitations (640K of conventional 5. PROC SUMMARY - (All Records) memory, unprotected mode processing, single­ tasking, and complicated concepts for using extended 6. PROC SUMMARY -- (With WHERE Statement) and/or expanded memory), running SAS programs under DOS can be a frustrating experience for power 7. DATA STEP EXTRACT - (With WHERE SAS users. Typically, the SAS system running under Statement) the traditional DOS operating system requires expanded memory to run memory-intensive SAS 8. DATA STEP EXTRACT - (With IF Statement) applications. Even in this case, only a few SAS executable files are moved into expanded memory, 9. DATA STEP EXTRACT - (With Compound freeing up more of conventional memory to hold SAS WHERE Statement) data files and other executables. 10. PROC RANK - (All Records) THE BENCHMARKS 11. PROC TRANSPOSE - (One Variable, All Benchmarks were run under three environments: Records) WINDOWS 3.0, OS/2 2.0, and the WINDOWS environment within OS/2 2.0 (Note: From this point on 12. PROC UNIVARIATE - (Ten Variables, All any reference to OS/2 denotes version 2.0 of the Records) operating system.) The computer used to conduct NESUG '92 Proceedings Host systems and Environments 225 The initial DATA step created a SAS data set of 10,000 observations with 110 variables of both numeric and character type. The subsequent DATA and PROC ~a step--Creat. Ail Re<:ord. steps processed data from this initial data set. The timings are recorded as total job completion time (wall ~========~-----------,--,,. time). The first graph (Figure 1) shows the completion times for executing all the programs in the ,. benchmark for each operating environment. ,,,. s,nc:hmark Summary--All steps - - '"'" Figure 2 ,... Some of the individual job steps showed more drastic differences in processing times. One of these was a .... PROC SORT on the 10,000 observations on two variables (Figure 3). SAS running under DOS WINDOWS Figure 1 Proc Sort on 2 Variables As Figure 1 shows, the bottom bar (SAS 6.07 ~.-____________________-.mDm Experimental Release for WINDOWS 3.0 running under its native WINDOWS environment) lagged "/2 217 behind the WINDOWS environment under OS/2 running the same version of SAS by approximately 25 percent. (Note: The native WINDOWS environment runs on top of the DOS operating system.) SAS for -- ''''' WINDOWS under OS/2 completed the benchmark programs in 1600 seconds, which still traUs SAS 6.06 for the OS/2 operating system running under OS/2, by about 35 percent. Figure 3 The original benchmark plan was to include SAS running under the traditional DOS operating system. But, because of the memory limitations encountered completed the sort in 1233 seconds; OS/2's WINDOWS the entire benchmark programs could not be completed it in only 793 seconds, a fraction of the time it completed in this environment. Consequently, only took the other two environments. Generally, I/O the first step of the benchmarks (DATA STEP - Create operations showed marginal differences under all three 10,000 Records) was run separately and compared to environments; however, memory-intensive applications the other environments. Where the other such as a sort is where performance is substantially environments completed this step with relatively small increased. This gain in performance can be attributed to differences in completion time, traditional DOS took two of OS/2's most formidable features: a flat memory more than twice the time it took for the other three model and a 32-bit addressing scheme. Unlike DOS, or environments (Figure 2). WINDOWS, which are both designed around a segmented memory model, OS 12's flat memory technology eliminates NESUG '92 Proceedings 226 Host Systems and Environments the need for distinctions between conventional process. The OS/2 operating system takes up about 31 memory, extended memory, and expanded memory. MB of disk space and requires at least an 80386 com­ Instead, it sees the total memory installed on your PC puter. Base SAS for OS/2 uses approximately 14 MB of as one linear memory resource entity and makes it disk space. The WINDOWS environment takes up about available to your applications. This coupled with a 32- 6 MB of disk space and Base SAS for WINDOWS requires bit addressing scheme (DOS and WINDOWS use 16- approximately 23 MB. bit addressing) results in faster, more efficient execution of Instructions. Another PROC step that illustrates this scenario is the PROC SUMMARY using ACKNOWLEDGEMENTS a WHERE statement that selects 600 observations from the initial 10,000 (Figure 4). OS/2 2.0 is a registered trademark of IBM. WINDOWS 3.0 is a registered trademark of Microsoft Corporation. Base SAS is a registered trademark of SAS Institute, Cary, NC. Proc Summary using Whel'll! Stoteme'nt .. " - Figure 4 Here, SAS under OS/2 and OS/2'S WINDOWS environment completed the procedure in more than twice the time it took either of the other two environments. CONCLUSION The results of the benchmarks will hopefully provide a general comparison of SAS performance under three distinct environments and some direction as to which environment will offer power SAS users the resources needed to process larger-scale SAS applications on a desktop computer. Additional performance issues that could be Investigated are I/O performance benchmarks using OS/2's High Performance File System (HPFS), and the 32-bit version of the SAS system for OS/2 which Is designed to take full advantage of 32-bit data processing on the PC platform. Space is another factor to consider in the selection NESUG '92 Proceedings .
Load more

Recommended publications
  • Software Requirements Specification
    Software Requirements Specification for Connectome Version 3.0 Prepared by: 1. Jon Schuck 2. Kennan Meyer 3. Nate Bender 4. Sheik Hassan 5. Khaled Alhendi 6. Bairavi Venkatesh 7. Kevin Garrone Senior Design Project Advisor: Mr. Jeff Salvage Fall 2016 to Spring 2017 1 Table of Contents Revision History.............................................................................................................................. 4 1. Introduction ............................................................................................................................. 5 1.1. Purpose ............................................................................................................................. 5 1.2. Overview .......................................................................................................................... 5 1.3. Product Scope ................................................................................................................... 6 1.3.1. In Scope .................................................................................................................... 6 1.3.2. Out of Scope ............................................................................................................. 7 1.4. Definitions ........................................................................................................................ 7 2. Overall Description ................................................................................................................. 9 2.1. Hardware Functions
    [Show full text]
  • Guidelines for Tools Development and Operating Environments
    Managing social, behavioral and economic data and metadata Guidelines for Tools Development and Operating Environments Author/Maintainer Pascal Heus, Open Data Foundation Contributors Jack Gager(Metadata Technology), Jannick Jensen (Danish Data Archive), Herve Lhours (UKDA) Version 2010-08-03 Table of Contents Overview....................................................................................................................................................2 Product Development.................................................................................................................................3 Environment.......................................................................................................................................... 3 Collaborative environment.................................................................................................................... 4 Licensing............................................................................................................................................... 5 Products Guide...........................................................................................................................................8 Overview............................................................................................................................................... 8 Web server software.............................................................................................................................. 8 Rich client Platforms...........................................................................................................................10
    [Show full text]
  • Standard Operating Environment Guideline
    STANDARD This guideline outlines the scope OPERATING and approach to the Computer Desktop Standard Operating ENVIRONMENT Environment (SOE) implemented by GUIDELINE Massey University. This guideline is intended to apply to computers and devices owned by Massey University and supported by Information Technology Services. Standard Operating Environment Guideline Purpose Massey University Information Technology Services (ITS) support a Standard Operating Environment (SOE) for desktop and notebook computers. The SOE is designed to ensure that the large number of desktop and notebook computers provide the necessary functionality to staff and students; can be loaded with a standard software image, maintained, updated, audited and repaired by ITS staff in a manner that improves availability and reliability, with a minimum disruption to staff and students; and at a cost that is appropriate to the University. The delivery of the Standard Operating Environment (SOE) to client computers is achieved through automated deployment and management tools. The expanded use of automation tools across all levels of ITS infrastructure, systems and services is designed to minimise support costs. The maintenance of desktop computers is most efficiently managed and delivered through the deployment of operating systems, software applications, patches and updates via online desktop management applications and tools. As part of its objective to provide cost effective and efficient management of ICT resources, Information Technology Services (ITS) maintains a Standard
    [Show full text]
  • Information Systems
    Information Systems IS100 Introduction to Computer Applications Cr-4 IS130 Desktop Publishing for Business Cr-3 and Concepts This course introduces the principles of desktop publishing in a This course satisfies the IS101 Computers and Society requirement business environment. Professional quality business documents are for students with little or no prior computer experience. It focuses on designed and produced that combine text, graphics, illustrations, and providing a solid foundation in basic computer skills and terminology, photographs in documents such as letterheads, business cards, flyers, and an understanding of how computer technology works. Experience brochures, promotional documents, and newsletters. is provided with a variety of microcomputer software applications, including word processing, electronic spreadsheets, and graphics, file IS200 Spreadsheet Concepts and Cr-3 management, and integrated software. Concepts and terms focus on Applications preparing for a technology oriented society and using the computer as This course expands the knowledge of those already familiar with the a tool for productivity, research and communication. basic elements of electronic spreadsheets. It examines the various uses for a spreadsheet in business. Intermediate and advanced spreadsheet IS101 Computers and Society Cr-3 techniques are examined, including the power of functions, formatting, This course provides knowledge of relevant computer skills and a solid analytical graphics, and macros. Prerequisites: IS101 Computers and foundation in the terminology and concepts of computer technology. Society or IS100 Introduction to Computers and Society. Experience is provided with a variety of microcomputer software applications, including word processing, electronic spreadsheets, IS201 Principles of Computer Security Cr-3 graphics, file management, and integrated software. Concepts and This course provides a comprehensive view of the field of computer terms focus on preparing for a technologically oriented society and network security.
    [Show full text]
  • Software Requirements Specification to Distribute Manufacturing Data
    NIST Advanced Manufacturing Series 300-2 Software Requirements Specification to Distribute Manufacturing Data Thomas Hedberg, Jr. Moneer Helu Marcus Newrock This publication is available free of charge from: https://doi.org/10.6028/NIST.AMS.300-2 NIST Advanced Manufacturing Series 300-2 Software Requirements Specification to Distribute Manufacturing Data Thomas Hedberg, Jr. Moneer Helu Systems Integration Division Engineering Laboratory Marcus Newrock Office of Data and Informatics Material Measurement Laboratory This publication is available free of charge from: https://doi.org/10.6028/NIST.AMS.300-2 December 2017 U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology SRS to Distribute Manufacturing Data Hedberg, Helu, and Newrock ______________________________________________________________________________________________________ Contents 1 Introduction 1 1.1 Purpose ...................................... 1 1.2 Disclaimer ..................................... 1 This publication is available free of charge from: https://doi.org/10.6028/NIST.AMS.300-2 1.3 Scope ....................................... 1 1.4 Acronyms and abbreviations ........................... 1 1.5 Verbal Forms ................................... 3 1.5.1 Must .................................... 3 1.5.2 Should ................................... 3 1.5.3 May .................................... 3 1.6 References ....................................
    [Show full text]
  • HP-UX 11I V3 Overview
    QuickSpecs HP-UX 11i v3 Overview HP-UX 11i v3 QuickSpecs for HP-UX 11i v3 describes the features and functionality delivered by the HP-UX 11i v3 operating environments and related software, plus considerations for a successful, optimized HP-UX deployment. Mission-critical applications are at the core of your company´s ability to compete effectively in today's always-on world. As such, the infrastructure powering these applications plays a crucial role in your business success. An essential part of this infrastructure is the operating environment, and when it comes to your vital workloads, you need an operating system with the right capabilities to support them, so you can maximize uptime and minimize business risk. HP-UX 11i v3 is designed to deliver an available, efficient and proven infrastructure demanded for mission-critical computing. It integrates proven UNIX® functionality with advances in high availability, security, virtualization, workload management and instant-capacity-on-demand. And it maximizes flexibility while reducing risk and delivering compelling value. HP-UX 11i v3: • Provides a proven operating environment delivering a highly resilient UNIX platform that ensures your mission-critical applications are always-on and secure without compromise • Offers the stability required to power the processes vital to your enterprise and the core mission critical applications that support them • Is managed seamlessly within your infrastructure. Delivers built-in integration of virtualization and management software to optimize IT infrastructure dynamically Features and functionality described in this HP-UX 11i v3 QuickSpecs includes HP-UX 11i v3 2021 update release. Update releases to HP-UX 11i v3 deliver significant benefits and functionality.
    [Show full text]
  • Computing :: Operatingsystems :: DOS Beyond 640K 2Nd
    DOS® Beyond 640K 2nd Edition DOS® Beyond 640K 2nd Edition James S. Forney Windcrest®/McGraw-Hill SECOND EDITION FIRST PRINTING © 1992 by James S. Forney. First Edition © 1989 by James S. Forney. Published by Windcrest Books, an imprint of TAB Books. TAB Books is a division of McGraw-Hill, Inc. The name "Windcrest" is a registered trademark of TAB Books. Printed in the United States of America. All rights reserved. The publisher takes no responsibility for the use of any of the materials or methods described in this book, nor for the products thereof. Library of Congress Cataloging-in-Publication Data Forney, James. DOS beyond 640K / by James S. Forney. - 2nd ed. p. cm. Rev. ed. of: MS-DOS beyond 640K. Includes index. ISBN 0-8306-9717-9 ISBN 0-8306-3744-3 (pbk.) 1. Operating systems (Computers) 2. MS-DOS (Computer file) 3. PC -DOS (Computer file) 4. Random access memory. I. Forney, James. MS-DOS beyond 640K. II. Title. QA76.76.063F644 1991 0058.4'3--dc20 91-24629 CIP TAB Books offers software for sale. For information and a catalog, please contact TAB Software Department, Blue Ridge Summit, PA 17294-0850. Acquisitions Editor: Stephen Moore Production: Katherine G. Brown Book Design: Jaclyn J. Boone Cover: Sandra Blair Design, Harrisburg, PA WTl To Sheila Contents Preface Xlll Acknowledgments xv Introduction xvii Chapter 1. The unexpanded system 1 Physical limits of the system 2 The physical machine 5 Life beyond 640K 7 The operating system 10 Evolution: a two-way street 12 What else is in there? 13 Out of hiding 13 Chapter 2.
    [Show full text]
  • Common Operating Environment – the Journey of Smart It Interoperability for Enterprise
    COMMON OPERATING ENVIRONMENT – THE JOURNEY OF SMART IT INTEROPERABILITY FOR ENTERPRISE LIM Tze Kwang Terence, HO Hao Xiang, TAN Kim Hong ABSTRACT The computing environment is constantly changing, triggered by Operating System and software patches, hardware driver updates, introduction of new device models and new IT systems. The Common Operating Environment (COE) comprises the client configuration, hardware, enterprise IT systems and back-end infrastructure. COE testing and certification is essential to maintain the interoperability, stability and security posture of the environment, leading to increased user productivity, reduced IT support cost and improved IT systems usability. This article describes DSTA’s journey in managing and transforming the COE. It expounds on the current landscape, processes and challenges involved, including increasing system vulnerabilities and patches, speed of testing and deployment, as well as improving the realism of test environments. The article also elucidates DSTA’s continuous efforts in introducing automation tools and technologies, undertaking smart optimisation of processes and transforming the operations model from a task-centric to a service-centric one. Keywords: COE, testing, certification, usability, automation INTRODUCTION With the increase in cyber threats and patches, regular feature upgrades and specific user demands, the COE is enhanced and refreshed constantly. Measures could include regular The Common Operating Environment (COE) comprises Operating System (OS) patches, software updates,
    [Show full text]
  • Clearpath® Application Integration Services for Clearpath® OS 2200 and Microsoft® Windows® Applications
    ClearPath® Application Integration Services For ClearPath® OS 2200 and Microsoft® Windows® Applications Product Information Sheet Product Overview Leverage the ClearPath Forward High-Speed Interconnect When a distributed application using ClearPath Application The process of developing a mission-critical application Integration Services is deployed on a fabric-enabled ClearPath leveraging resources from multiple operating environments Forward® system, it can take advantage of the high-speed presents a unique set of organizational and technical interconnect between the Microsoft Windows and ClearPath challenges. Examples range from skills availability for the OS 2200 environments within the ClearPath Forward system. various operating environments to dealing with different data formats. Transparent Application Deployment Flexibility The ClearPath® Application Integration Services product You have the flexibility to deploy distributed applications using is designed to make it easier for you to develop mission- ClearPath Application Integration Services on fabric-enabled critical cross-platform applications. ClearPath Forward system, on other ClearPath servers as well as on Windows servers and PCs. When the high-speed Reduce the Cost of Developing Distributed Applications interconnect is not available, TCP/IP networking is used for ClearPath Application Integration Services provides APIs that the connection. applications running in one operating environment can use to access resources such as files or applications in another General Features operating environment. For example a Windows application Services for Windows-Based Applications can access an ClearPath OS 2200 TIP transaction. Another ClearPath Application Integration Services provide APIs that example is to enable a ClearPath OS 2200 application to call enable Windows-based applications to access OS 2200-based out external web service in Windows.
    [Show full text]
  • Microsoft Windows Resource
    Appendix D Articles This appendix contains technical articles on these topics: • Microsoft Windows for Pens • Quarterdeck’s QEMM –386 and Windows 3.1 • PC-NFS and Windows 3.1 • FastDisk: An Introduction to 32–Bit Access Contents of this appendix Windows for Pens.............................................................................................506 Why Pens?.................................................................................................506 Technical Highlights .................................................................................508 The Internal Architecture of Pen for Windows..........................................509 RC Manager ..............................................................................................510 Pen for Windows Support Resources ........................................................511 Quarterdeck’s QEMM –386 and Windows 3.1 ..................................................515 QEMM –386 Features for Windows ...........................................................515 Troubleshooting for QEMM -386 ...............................................................516 Getting Additional Help ............................................................................518 PC-NFS and Windows 3.1.................................................................................519 Installation Tips.........................................................................................519 Using PC-NFS With Windows ...................................................................519
    [Show full text]
  • Standard Operating Environment "Unix*" Operating System
    BEU SYSTEM PRACTICES SECTION 007-204-1 01 AT & TCo Standard Issue 1, July 1983 STANDARD OPERATING ENVIRONMENT "UNIX*" OPERATING SYSTEM CONTENTS PAGE ing System, such as full-scale transaction process­ ing (eg, data-base recovery, message recovery, 1. GENERAL transaction performance monitoring), are exempt­ ed. However, the developers of such systems are 2. EFFECTIVE DATE 2 encouraged to build upon the applicable portions of the UNIX System. 3. SOFTWARE ENVIRONMENT 2 (b) The system is developed to be operated by a 4. HARDWARE ENVIRONMENT 2 BOC in its local environment or by several BOCs in a regional environment. 5. OAT A COMMUNICATIONS ENVIRONMENT 2 1.04 This BSP is not binding on project groups which have completed preliminary design be­ 6. DELETED OR SUPERSEDED COMPONt:NTS 3 fore the instruction's publication date. It is intended, however, that major redesigns of existing systems (ie, changes to the system architecture or operating 1. GENERAL system software) comply with this SOE where possi­ ble. Normal generic releases of existing systems are 1.01 This Bell System Practice (BSP) describes the excluded. Standard Operating Environment (SOE) for computers utilizing the UNIX Operating System. The 1.05 The long range objective is to separate the SOE functions as an interface between the users of UNIX Operating System from application centrally developed systems (generally the Bell Oper­ code. This will ease the transition to new releases of ating Companies [BOCs]) and the designers of the the operating system for both the developers and the systems. The existence of a standard interface lowers users and allow the applications to upgrade to the the cost of designing, installing, and maintaining current release specified in the SOE.
    [Show full text]
  • Memory Management
    University of Mississippi eGrove American Institute of Certified Public Guides, Handbooks and Manuals Accountants (AICPA) Historical Collection 1993 Memory management American Institute of Certified Public Accountants. Information echnologyT Division Follow this and additional works at: https://egrove.olemiss.edu/aicpa_guides Part of the Accounting Commons, and the Taxation Commons Recommended Citation American Institute of Certified Public Accountants. Information echnologyT Division, "Memory management" (1993). Guides, Handbooks and Manuals. 486. https://egrove.olemiss.edu/aicpa_guides/486 This Book is brought to you for free and open access by the American Institute of Certified Public Accountants (AICPA) Historical Collection at eGrove. It has been accepted for inclusion in Guides, Handbooks and Manuals by an authorized administrator of eGrove. For more information, please contact [email protected]. INFORMATION TECHNOLOGY DIVISION BULLETIN AICPA American Institute of Certified Public Accountants TECHNOLOGY Notice to Readers This technology bulletin is the first in a series of bulletins that provide accountants with information about a particular technology. These bulletins are issued by the AICPA Information Technology Division for the benefit of Information Technology Section Members. This bulletin does not establish standards or preferred practice; it represents the opinion of the author and does not necessarily reflect the policies of the AICPA or the Information Technology Division. The Information Technology Division expresses its appreciation to the author of this technology bulletin, Liz O’Dell. She is employed by Crowe, Chizek and Company in South Bend, Indiana, as a manager of firmwide microcomputer operations, supporting both hardware and software applications. Liz is an Indiana University graduate with an associate’s degree in computer information systems and a bachelor’s degree in business management.
    [Show full text]