Running the SAS· System Under 386 Multitasking Software Julie Maddox, SAS Institute Inc., Cary, NC ABSTRACT The DESOview SETUP program lets you tell DESQview how you want your system CQrtfigured and how you would like the The ability to muttitask is fast becoming a necessity in the world DESOview system options set. The Performance Setup options of personal computers. The virtual mode of the 80386 mlcropro­ control the amount of processing time DESQv1ew allocates to the cessor has made multitasking viable. This paper discusses how foreground and background tasks. Since the task processing to run the SAS System for personal computers under OESOView time can be altered dynamically, it is probably best to accept 386. Microsoft" Windowsf386, PC-MOS®1386, and VMf386~ DESQview's default values for these options. Creating the DESQv!ew 386 Program Information File for the INTRODUCTION SAS System The fntef0 80386 microprocessor has opened up a whole new For DESOview to run SAS software or any other program, you W()rtd of computing power for those of us who are always trying must relay some basic information, such as the amount of mem­ to do several tasks at one time. The 386 processor supports mul­ ory to allocate and where the system files are located. This infor­ tiple virtual machines that' can run applications in a multitasking mation is communicated via the DESOview program information environment as if each task is running on its own BOB6 machine. file (OVP). Some of the options defined in this file depend on what Although only one application has control of the central process­ type of jobs you plan on submitting during the SAS session, For ing unit (CPU) at any given instant, the multitasking software example, if you want to run SAS/GRAPH® software or if you plan passes control back and forth between the different tasks such to download a file using the micro-to-host, link. then you have to that they all appear to be executing simultaneously. change some of the DVP options. Four of the most popular 386 multitasking environments include: The Change A Program menu is shown in Figure 1, with the typical OESQview 386 by Quarterdeck Office Systems, Microsoft Win­ options that should be set tor a base SAS session. The Memory dowsf386 by Microsoft Corporation, PC-MOS/386 by The Soft­ Size option specifies the minimum amount of memory the SAS ware Link, and VM/386 by Intelligent Graphics Corporation. System needs to come up in the interactive display manager DESOview 366 and Windowsl386 both allow you to display tasks mode. The Parameters field can be used to enter SAS configura­ in a windowed environmen~ while PC·MOS/386 and VM/386 will tion options, such as -EMS ALL, or to enter SAS program names display only one task on the screen at a time. All four of these you wish to run in batch mode. To help prevent lost clusters, dis-­ packages wiN allow applications to be executed in background able the Allow Close Window command. This way the SAS ses­ or in foreground. Thts paper discusses how to run the SAS\!) Sys­ sion must be terminated normally (thus SASUSER and SASWORK tem fQr personal computers in these four multitasking environ~ files are closed) before the window is closed. The DESQview 386 menis. program information file shown in Figure 1 is useful for running base SAS software, SAS/STAr." SASIFSP1' SAS/A~ and SAS/ETS® software. In order to run SAS/ASSIST"" software, you DESOVIEW 386 need to change tile Program Name field to either ASSIST.BAT or SASMOUSE.BAT depending on whether you want to use a DESOview 386 is a multitasking control program developed by mouse within SAS/ASSIST. Figure 2 displays the DVP file for Quarterdeck Office Systems. DESQview 386 consists of two sep-­ SAS/ASSIST running with a mouse, arate programs. OESOview Version 2,2 and the Quarterdeck Expanded Memory Manager - 386'" Version 4.2., Together these Configuring DESQview 386 to Run SASIGRAPH, SAS/IML, programs take advantage of the powerful features of the 80386 SAS/OC, and SAS/OR Software microprocessor to provide a polished multitasking environment. System requirements for running the SAS. System under To run SAS/GRAPH software, several options in the program OESOview 386 include information file need to be modified, Figure 3 displays the .. B03S6-based IBM® compatible personal computer DESQview information file needed to run SAS/GRAPH software. SAS/GRAPH usually tries to display graphics using the entire • 4 MB of Extended Memory screen. Setting the Virtualize text/graphics option tells OESQview to force SAS/GRAPH output to stay within the window borders. • Mouse (optional) To maximize performance on a EGA display adapter, disable the Share EGA when foreground/zoomed option. Thus, when the .. PC DOS or MS·DOS® Version 2.0 or later. SAS/GRAPH window is zoomed and executing in the foreground. all other background EGA graphics programs are temporarily Configuring DESQview 386 to Run with the SAS System suspended. Note: SAS/IML~ SASIQCf and SASIOR® software also display graphiCS information and thus should be configured Quarterdeck's Expanded Memory Manager (QEMM-386) can as described above for SAS/GRAPH, transform all extended memory into expanded memory. To enable aEMM~386 add a DEVICE- statement to your Configuring DESQview 386 to Run the Micro-to~Host Unk CONFIG.SYS file. This Is normally done automatically for you dur­ ing the QEMM-386 installation process. In addition, if you plan To execute the SAS micrcrto-host link under DESQview. modifi~ to use a mouse with OESQviaw, you need to add a OEVICE= cations need to be made in the DVP file. Also a DOS batch file statement to load your mouse driver. 537 is used to invoke the communications program and the SAS Sys­ • IBM compatible personal computer with an Intel 80386 tem. The DVP file for the micro-ta-host Imk is shown in FlQure processor or equipped with an Intel Inboard"" 386/AT 4. • 4 MB of Extended Memory The most critical setting in the DVP file for the micro-to-host link is disabling the Can be swapped out option. Communications pro­ • Microsoft Mouse (strongly recommended) grams must be managed at all times. Thus, they cannot be • PC DOS or MS-OOS Version 3.1 or later. swapped out of memory to disk. Otherwise data are lost, and the PC will probably lock up, requiring you to reboot the machine. Also, in order to run the micro-to-host link in the background, Configuring Windowsj386 to run the SAS System make sure that you do not have a mouse oonflgured to use the same port as the asynchronous communications line. Note that Windowsf386 allows each application to allocate up to 640k of a DOS batch file, such as the one shown below, is used to startup conventional memory. In addition, each application can access the communications program and then to invoke the SAS Sys~ expanded memory. All memory on your PC should be configured tem. as extended memory and any EMS device drivers in your CONFIG.SYS file should be removed. U you plan to use a mouse CD \ll:t.1NK with Windows/386, you need to add a DEVICE - statement that TTY loads your mouse driver. 'AS Finally. depending on the communication program being used, The WIN.JNI file contains settings for Windows/386 features. Sys­ you may need to increase the Memory Size option. tem settings such as c~or pr.eferences, mouse acceleration. and default fonts or printers can be changed using the Control Panel. The most notable windows configuration options are Multitasking and Performance Issues WINOOWM£MSIZ£ and £MMSIZE. The WlNDOWMEMSIZE tells Windows/386 the maximum amount of memory anyone applica:­ The SAS System for personal computers can be executed in tion can allocate. The EMMSIZE fixes the maximum amount of either foreground or background. In fact multiple SAS sessions extended memory that can be used as expanded memory at any can be run simultaneously. The only restriction is that each SAS one time. Set these two options as follows: session should have its own SASUSER and SASWORK subdirec­ tories. You can ensure this by invoking each SAS session from "'iw.:lrn_elll$i;$"'6~(j a different directory. or by inserting the ..sASUSER and emms.he= -sASWORK options in the Parameters field of the program infor­ mation fi1e. Also, you should not attempt to share SAS data sets Creating the Program Information File for the SAS System 'or catalogs. Unpredictable results, including data corruption. may occur. The program information file (Plf) contains information about how the SAS System wlll use system resources and memory. You As you start multitasking you will notlce a perfonnance degrada­ will probably want to have several different PIF files for running tion. DESQview atlows you to change the foreground task and the SAS System under different scenerios. For example, the PIF the system options dynamically. Ftgure 5 shows the performance fiie for running SAS/ASSIST software would be different from a options that can be modified in-stream. To increase the perfor­ SAS session executing the micro-ta-host link. mance of the foreground task. you should look at the Share CPU, Share EGA. and Allow swapping out options. If you disable 111. The Windows/aS6 Program Information Editor with the typical Share CPU option, then all other background tasks are sus~ settings necessary for a basic SAS session is shown in Figure ponded. Also, if you are working wi1l1 SAS/GRAPH software 6. The first four entries provide basic program information. The using an EGA adapter,.