Taking Advantage of the SAS System on Windows NT
Total Page:16
File Type:pdf, Size:1020Kb
Taking advantage of the SAS System on Windows NT Mark W. Cates, SAS Institute Inc., Cary, NC ABSTRACT Unless specified, all the SAS System products and features are provided on both Windows NT Windows NT is fast becoming the universal Workstation and Windows NT Server. This desktop client operating system as well as an paper assumes the current release of Windows important file and compute server for mission NT is Version 4.0. For brevity, the abbreviation critical applications. This paper presents a NT will be used for Windows NT. discussion of the state of Windows NT and how the SAS System Release 6.12 for Windows takes advantage and integrates with the operating Windows Family - Single Executable Image system. Areas such as the user interface, OLE and Web integration are presented. Data access Windows NT is now in its full 3rd generation, and Microsoft BackOffice integration, and with the release of Windows NT Workstation hardware considerations are also presented. 4.0 and Windows NT Server 4.0. NT Workstation and NT Server share the same microkernel, and is portable to several RISC INTRODUCTION platforms, including DEC Alpha AXP, and the PowerPC Prep Platforms. The MIPS chip Microsoft Windows NT sales grew dramatically is no longer supported by Windows NT. The in 1996, as many corporations which have been majority of NT installations still run on the Intel investigating Windows NT have now begun to Pentium® and Pentium Pro® processor. The deploy Windows NT for the client desktop. SAS System Release 6.12 only supports the Intel Many of these deployments were replacing platform, and the Pentium Pro processor is ® Windows 3.1 and Windows 95 . Also, highly recommended. At this writing, the Windows NT Server is making major inroads market demand for the SAS System for NT on for mission critical file and compute servers. RISC platforms has not been great enough to Just what does Windows NT provide that is so warrant a production release. Please contact appealing to corporations? And, how does the your SAS Institute sales representative if you are SAS System integrate with Windows NT? This interested in using SAS for Windows NT on a paper presents the current state of the SAS RISC platform. System for Windows NT. It introduces the basic system features of Windows NT as well as some Although this paper focuses on Windows NT, it of the more advanced features of Windows NT. is important to note that the SAS System for At each point, features and products of the SAS Windows Release 6.12, supports the Windows System that integrate well with Windows NT are family of operating systems with a single presented. A brief overview of Windows NT executable image. There is a single CD that Server is discussed within the context of SAS supports all three Windows operating systems Institute’s plan for continued support. The Windows NT (workstation and server), paper concludes with hardware considerations Windows 95, and Windows 3.1 using Win32s. for the SAS System on Windows NT and a However, the product has run time checks for glimpse of future directions for Windows NT Windows NT to take advantage of NT specific and the SAS System. APIs (application programming interfaces). Microsoft’s strategy is to have a family of Note: Throughout the paper, unless otherwise Windows offering from the low end Windows specified, the term Windows NT generally refers 3.1, to the entry level business environment to the code base and feature set that is Windows 95, through the high end power user represented in both product offerings, Windows and server platforms with Windows NT. NT Workstation and Windows NT Server. Applications should be able to run across all of 1 these environments unmodified. Now, this programmatically send a simple email message strategy is being narrowed to Windows 95 and from within a Data Step or SCL program, Windows NT Workstation and Windows NT without requiring a user interface. Server, with the demise of Win32s. Development at SAS Institute focuses on Print Preview for all display manager and graph Windows NT. The SAS System release is later windows is a new feature provided in Release tested on Windows 95 and Windows 3.1 with 6.12. This allows for the printed output to first Win32s for compatibility. Future releases of be reviewed before printing. the SAS System will only support Windows NT and Windows 95. ActiveX Support User Interface - Windows 95 Explorer Shell There has been much confusion over the Windows NT 4.0 has released the Windows 95 difference between OLE and ActiveX. Mostly Explorer shell as the default user interface shell. the confusion has been caused by a name game This means that the user interface between the and marketing push by Microsoft. ActiveX is highly popular Windows 95 and Windows NT, the new generic name for OLE, and OLE is now and the newly released Windows CE®, is the specific acronym for what it should be, that largely the same. This user interface is of Object Linking and Embedding. Much of the commonly believed to have become the defacto confusion has happened because new OLE standard for client workstations. Also provided technology is now being released named as on NT is the Windows 95 Start menu, wizards, ActiveX and there really was never a previous my computer, network neighborhood, recycle OLE name for the technology. For example, bin, interactive help, and other Windows 95 consider ActiveX scripting, where there was applets. never previously an OLE scripting model. In general, ActiveX includes objects, controls, It is important for applications to follow the user documents, and various scripting models. OLE interface guidelines provided by Windows, and has not fundamentally changed; it has just been the SAS System is no exception. The SAS renamed as ActiveX. System is a native Windows NT application. Developers at SAS Institute have paid special Support for ActiveX continues strong in Release attention to Windows 95 user interface 6.12. This includes Object Linking and guidelines outlined in Microsoft’s Windows User Embedding support in SAS/AF and SAS/EIS. Interface Handbook in designing the SAS These SAS products can function as an OLE System user interface. Container and host any ActiveX object. Visual editing, drag and drop, and OLE automation is Additionally, Windows NT supports messaging supported. OLE automation server support was through Microsoft Exchange. NT provides for provided experimentally in Release 6.11 and has an email client named the Inbox, and Microsoft now been fully tested as a production feature in Office97 provides for a Personal Information Release 6.12. This provides for the ability to Manager named Outlook that combines email program the SAS System and access the full inbox, scheduling, and contacts. Through functionality of the SAS System from products support of Microsoft Messaging API (MAPI), such as Microsoft’s Visual Basic, PowerSoft’s the SAS System integrates nicely with the Inbox PowerBuilder, or any OLE automation and Outlook, allowing email messages controller. For example, from a Visual Basic containing rich text and attachments to be program, any SAS procedure or Data Step created and mailed by the SAS System. The statements and DM commands may be SAS System uses the email user interface submitted to the SAS System and the results consistent with the mail program installed. The may be brought back into the Visual Basic messaging APIs supported are MAPI and VIM. program, including text and graphic reports. Please see “OLE and the SAS System for Also provided as a new feature in Release 6.12 Windows Release 6.12” in these proceedings for is the SMNP email access method. This a complete description of ActiveX (OLE) experimental feature makes it much easier to support in Release 6.12. 2 DCOM Support • The FTP access method allows for accessing remote files, directory listings, ActiveX is built on top of a systems and accessing anonymous FTP sites from infrastructure named Component Object Model within the SAS System. (COM). COM provides the software architecture for software components or objects • The TCP/IP socket access method can be to communicate with each other. COM is used to establish peer-to-peer connections limited to coordinating objects all executing on with a remote program. In this way, a the same local workstation. However, now remote program can be set up to provided in Windows NT 4.0 is production communicate with the SAS System. support of Distributed COM referred to as DCOM. DCOM allows for the invocation and • The URL access method allows a SAS coordination of objects across networks. With program to access remote files using the DCOM provided in Windows NT 4.0, the SAS universal resource locator protocol. (Of System can now access objects that are course this is a standard protocol used on remotable across the network. DCOM has now the world wide web.) provided the beginning infrastructure for powerful distributed computing. SAS Release Several new tools are available and can be 6.12 provides support for DCOM in the SAS downloaded from the SAS Institute home page OLE Automation Server. under the Research and Development section. ( http://www.sas.com ) WEB Integration • The HTML Output Formatter is a tool to save output from any SAS procedure to an As Microsoft positions Windows NT to be a HTML file, making the static pages of the premier web client and server, the SAS System data immediately available for users to also is adding features aimed at the web. The access from their web browsers. SAS toolbar now sports a new tool that provides for the invocation of the current web browser.