;... _... name; tsoge. scr purpose: Startup a TSO SAS session. notes: Assumes the TSO session has been logged on manually.

Size: px

Start display at page:

Download ";... _... name; tsoge. scr purpose: Startup a TSO SAS session. notes: Assumes the TSO session has been logged on manually."

Sharleen Harrison
5 years ago
Views:

1 AUTOMATING THE PROCESS OF DOWNLOADING SAS DATA SETS TO THE PC Bruce Nawrocki, GE Capital Mortgage Insurance Introduction The [nfonn.tion Center at GE Capital Mortgage Insurance supports about 50 people who use SAS sofnvare on an IBM 3084 mainframe and personal computers~ Most people have an IRMA card and terminal emulation softw'are in their PC. These SAS users often want to download small SAS data sets from the mainframe to their PC. Once the data is on their PC in a SAS data set, they may also want to move the data into other software packages, such as a spreadsheet or database, for further data manipulation. The SAS micro to host link gives the SAS user the ability to download mainframe data to the PC. Although the downloading procedure is fairly straightforward, it involves many steps. Downloading requires that the user be familiar with a variety of mainframe and PC software, not to mention all the different error messages they may see. fn addition, most PC users don't download data very often.~ perhaps once or twice a month. For someone who downloads data On a regular but infrequent basis, these steps can be difficult to remember. These people wanted to automate the entire downloading process, so they wouldn't have to memorize a complex series of steps. Nonnally. a user would have to manually perform each of the following steps; 1) Logon to the mainframe 2) Start up SAS software on the PC 3) Start up the SAS micro to host link 4) Submit the SAS statements required to allocate the necessary mainframe files 5) Submit the PROC DOWNLOAD statements to download the mainframe SAS data set to the PC 6) Sign off from the SAS micro to host link 7) Run the DBF or DIF procedure to create a.dbf or.dif file from the downloaded SAS data set 8) Exit SAS software on the PC, starr up the database or spreadsheet program and load the.dbf or.dlf file. To help speed up the learning curve and make things easier for casual users. I wrote several SAS programs that help to automate both the tasks of downloading [he data and moving it into a.dip or.dbf file. The steps were automated through the use of a couple of DOS batch files and a SAS program which incorporates the SAS macro language. Program listings are included at the end of this paper. Batch Flies The AUTOEXEC.BAT file on the user's PC was modified to automatically load the tenrunal emulation software in resident mode. In our case, we use an IRMA card and emulation software, but this could work with any terminal emulation software. We did have to be careful about memory limitations, however. Resident software may not leave enough memoty for SAS software on the PC to work properly. We were lucky that the IRMA resident software could co exist with SAS software within the 640K memory limitation. Other emulation software, such as IBM's, may require you to have a PC with Expanded Memory. A menu system was set up with batch files that would change the directory to the correct one and then run the SAS software. An AUTOEXEC.SAS file was installed in that directoty which included the following lines: OPTIONS REMOTE=IRMA; LIBNAME PERM '.'; FILENAME RLINK 'TSOGE.SCR1; The first line above notifies the SAS system that the PC is using an IRMA card for transferring data to and from the mainframe. The second line sets up a libref called PERM that points to the current directoty. This libref is used when moving the SAS data set from the mainframe to the PC. The last line names the script file that contains commands to sign on and off from the mainframe portion of the micro to host link. TSOGE.SCR contains the following text (which is a modification of the TSO.SCR file supplied with SAS software for personal computers). I didn't include commands to automatically signon to TSO because I assumed people would already be in TSO. ;... _... name; tsoge. scr purpose: Startup a TSO SAS session. notes: Assumes the TSO session has been logged on manually.... _...._.... _... _... ; log 'NOTE: TSO program running... please wait.'; MODEL 2: if signoff goto signoff; type '-x' enter; waitfor "READY': atready, 20 seconds; 1650

2 echo on; gotq timeout; atready: type "sas options('remote-pclink maero')" enter; wa1tfor 'IN PROGRESS': progress, 30 seconds; type enter: waitfor 'IN PROGRESS': progress, 30 seconds; timeout: log ~ERROR: abort; progress : stop. Timeout,'; signoff: wa1tfor 'READY': ok, 20 seconds; log 'NOTE: Mainframe not responding, '; log ~You may need to manually logoff from TSO. ~: log 'Return to mainframe now and type LOGOFF at READY prompt.'; stop; ok: type 'ISPFUSER' enter; log 'NOTE: When you return to mainframe, you vill be at the Main Menu,'; log, ~ "--.; log' Do not forget to log off from TSO! '; log '; stop; The SAS Programs There are three versions of the SAS program that is submitted from the PC and downloads a SAS data set from the mainframe, Program 1 requires that the user manually signon and signoff the $AS micro-to-host link (via the SIGNON and S!GNOFF commands)_ The user modifies the %LET statement to contain the name of the mainframe SAS data set to download. Program 2 is a slight variation of Program 1 that lets users enter as many SAS data set names as they want on the O/OLET statement. The program will download an of them into separate SAS- data sets on the PC. the program executes. The program allocates the mainframe file that contains the SAS data set to download. This process is made easier since all these data sets are stored in one library (called SASUSER). SAS/SHARE" software is used to access this library since at any given time there may be several people who are writing to and reading from this library. I didn't want the users to attempt to download a mammoth data set that would take a long time to download or wouldo't fit on their PCs hard disk_ So, the first thing the program does is figure out the approximate size of the SAS data set and how long it will take to download. TIlls information is based on the results of a PROC CONTENTS performed on the mainframe. If the user tries to download a file that is larger than 1 megabyre (this is an arbitrary number), the program prints a warning message and stops. Otherwise, the mainframe SAS data set is downloaded to the PC_ More About Program 3 Program 3 works because of the ability of Version 6.03 of SAS software for PC's ability to use DM statements to remotely submit mainframe SAS statements from the PC. The program is submitted by typing SUB on the Command line instead of RSUB, as in the other two programs. Because of this, Program 3 can even be run from the DOS prompt without invoking SAS Display Manager. This leaves more memory free for the downloading process and the terminal emulation sofrware. Assuming the program is stored in a file called DOWN3.SAS, you could execute the program by typing SAS DOWN3.SAS from the DOS prompt. Program 3 automates the process even further. It automatically performs the signon and signofe to the SAS micro-to-host link. It then downloads one SAS data set from the mainframe to the PC, and then calls upon either PROC DlF or PROC DBF to create a.dlf or _DBF file for use with other PC software. A Closer Look at Program 1 Program 1 automatically invokes PROC DOWNLOAD to move a SAS data set from the mainframe to the PC. Users just fill in the name of the SAS data set they want to download on the '%LET SNAME =' line. Then, they type RSUB on the COMMAND line of the PGM EDlTOR window, and 1651

3 Program Listings Program 1 *** TYPE NAME OF DATASET TO OOWNLOAD ON NEXT LINE AFTER THE SIGN; %LET SNAME - SASUSER.8KNSEC **. THEN TYPE -> RSUB <- ON COMMAND LINE; OPTIONS DQUOTE MACROGEN; %GLOBAL FIRSTIKE; DATA _NULL_; :1:::S:E:TT::r:N:G::U:P::P:R:O:G:I!AM::::.:.:.::P:LE::AS::E::W:A:I:T:.:::~ : %MACRO DL; %IF &FIRSTIME NE N %THEN %00; LIBNAME SASUSER SERVER-SASSHARE; tlet FIRSTIKE - N; PROC CONTENTS DATA-&SNAKE NOPRINT OUT-TEMP; SET TEMP END=LAST; RETAIN TOTAL 0; TOTAL+ LENGTH; I F LAST THEN DO; KB = «TOTAL+4)*NOBS)+1000, MINS = KB/60000, ~=============================J'; YOU ARE TRYING TO DOWNLOAD A FILE ; THAT WILL REQUIRE ' KB 9. ' BYTES ; OF STORAGE ON YOUR PC.,, I~============================~'; PLEASE WAIT 'i THIS WILL TAKE' MINS 4.1 MINUTES.,, CALL SYMPUT ('KB',KB): END; %IF &KB > %THEN %00; PUT.=----= , ARE YOU KIDDING? THIS FILE IS TOO BIG TO DOWNLOAD! ' PUT, , tend, %ELSE %00; %LET PCNAME = %SUBSTR(&SNAKE,%INDEX(&SNAKE,.)+l); PROC DOWNLOAD DATA=&SNAME OUT=PERM.&PCNAME; DATA NULL, PUT" THERE IS NOW A FILE CALLED &PCNAME. SSD IN \MYSAS DIRECTORY." POT I PUT " YOU CAN REFER TO THE SAS DATA SET ON THE PC AS PERM. &PCNAME", I.. you SHOULD NOW SIGNOFF FROM MAINFRAME SAS BY TYPING SIGNOFF ON ANY COMMAND LINE. '; " PUT tmend DL; tdl; '; 1652

4 Program 2 *** TYPE NAMES OF SASUSER DATASETS TO DOWNLOAD ON NEXT LINE SEPARATED BY * SPACES AFTER THE = SIGN (DO NOT TYPE SASUSER.!) %LET FILES = MYFILEl MYFILE2 MVPlLE3 *** THEN TYPE -> RSUB <- ON COMMAND LINE; OPTIONS DQUOTE MACROGEN, %GLOBAL FIRSTIME, DATA NULL: SETTING UP PROGRAM.. PLEASE WAIT. PUT t %MACRO WORDS(STRING) : %LOCAL COUNT WORD, %LET COUNT=l: %LET WORD=%SCAN(&STRING,&COUNT,%STR(»: %00 %WHlLE(&WORD NE): lglobal W&COUNT: llet W&COUNT=&WORO: %LET COUNT = %EVAL(&COUNT+l): %LET WORD=%SCAN(&STRING,&COUNT): %EVAL(&COUNT-l) %MEND WORDS, %MACRO DL: %IF &FIRSTIME NE N %THEN %00: LIBNAME SASUSER SERVER=SASSHARE: %LET FIRSTIME = N; %ENO: %001=1 %TO %WORDS(&FlLES); llet PCNAME = lsubstr(&&w&i,%index(&&w&i,.)+l): PROC DOWNLOAD DATA=SASUSER.&&W&I OUT=PERM.&PCNAME: lendi %MEND OL; %OL: ij: 1653

5 Program 3 %LET TRANSFER ~ DBF TRANSFER CAN BE DBF OR DIF ; ******************* *******.*****; OM 1 OiJTPUT;CLEAR; SIGNONt ; OM 'RSUBMIT'; TYPE NAME OF DATASET TO DOWNLOAD ON NEXT LINE AFTER THE SIGN; *** THEN TYPE -> SUB <- ON COMMAND LINE; %LET SNAME ~ SASUSER.BKNSECl ; **********************************: OPTIONS DQVOTE MACROGEN; %GLOBAL FIRSTIME, DATA NULL, %MACRO DL; 1* Same as the DL macro in Program 1, but you can leave out the last four PUT lines, since you no longer have to type SIGNCFF on the command line. You also need to add a statement just before the %MEND DL; statement to properly display the PUT statements. *1 %MEND DL; %DL; ENDRSUBMIT; PUT" PLEASE WAIT WHILE THE.&TRANSFER FILE IS CREATED ", %MACRO TRANS, %LET PCNAME ~ %SUBSTR{&SYSLAST,6); %IF &TRANSFER ~ DIF %THEN %00: FILENAME OUT "C:\LOTUS\&PCNAME.. DIFtI; PROC DIF DATA~&SYSLAST DIF~OUT; %END; tif &TRANSfER DSF %THEN %00, FILENAME OUT "C:\DBASE\&PCNAME 0BF"' PROe DBF DATA~&SYSLAST DB3~OUT; tend: DATA NULL_; PUT " %MENO; %TRANS; DM 'SIGNOFF'; &PCNAME.. &TRANSFER FILE HAS BEEN CREATED": SAS and SAS/SHARE are registered trademarks of SAS Institute Inc., Cary, NC, USA. Contact: Bruce Nawrocki GE Capital Mortgage Insurance 6601 Six Forks Road Raleigh, NC (919)

CHAPTER 7 Examples of Combining Compute Services and Data Transfer Services

55 CHAPTER 7 Examples of Combining Compute Services and Data Transfer Services Introduction 55 Example 1. Compute Services and Data Transfer Services Combined: Local and Remote Processing 56 Purpose 56