Using SAS/ACCESS with Controlled Access Multiple Oracle Instances on DEC V AXlVMS Systems. Abstract

Transcription

1 Using SAS/ACCESS wih Conrolled Access Muliple Oracle Insances on DEC V AXlVMS Sysems A. Richardson Merck Sharp & Dohme. Absrac A mehod is described ha enables SASIACCESS insalled on DEC VAX!VMS sysems o be used in conjuncion wih muliple Oracle insances under condiions where securiy consideraions preven he general user having direc knowledge of Oracle accoun names and passwords. Conrol of daa exracion from a clinical rials sysem is used o illusrae he echniques involved. Inroducion SASjACCESS [1] enables daa held in non-sas daabases o be exraced direcly ino SAS daases for furher analysis or examinaion. When used wih Oracle daabases he basic SASIACCESS insallaion and configuraion assumes he program is o operae in conjuncion wih a single Oracle insance where he user will know he names and passwords of he Oracle accouns from which hey will exrac daa. In many cases hese assumpions will no be me due o insallaion and securiy consideraions ha give rise o (a) muliple Oracle insances possibly a differen revision levels ha are running Oracle applicaions where (b) he Oracle accoun names and passwords are hidden from he user. For example i is no uncommon o find developmen and producion daabases coexising on a single sysem and many Oracle applicaions use special 'Daa Enry' or 'Query Only' accouns o preven user accouns requiring high levels of accoun privileges by defaul In hese cases he sandard procedures for insalling and using SAS/ACCESS wih Oracle daabases will no enable users o exrac daa from Oracle daabases easily and may compromise securiy if spf!cial Oracle accoun names and passwords have o be made widely available. This paper describes a mehod o overcome hese problems when SAS and Oracle are operaing on DEC V AX compuers under he VMS operaing sysem. Alhough he deails of he mehod are only applicable o his operaing sysem he general principles may also be applicable o oher operaing sysems where hese producs coexis. Background and Mehods 1 Using SAS/ACCESS wih Muliple Oracle Insances As wih oher programs inerfacing wih Oracle SASIACCESS requires he program code used o communicae wih he daabase managemen sysem o be linked wih Oracle library rouines o produce he final usable execuable image. This linking is par of he SAS/ACCESS insallaion and resuls in he producion of he SASIACCESS execuable image INTER.EXE. This program is used by SAS in response o PROC ORACEXT saemens in SAS programs o exrac daa from. Oracle daabases. An INTER.EXE produced by his procedure will only operae wih Oracle insances a he 59

2 same revision level as he original Oracle sysem used for he linking and could no be used wih oher Oracle insances. In hose Siuaions where muliple Oracle insances exis a differen revision levels new versions of INTER.EXE will be required for each insance. In conras PROC ORACEXT can be used as par of any SAS program and on sysens running muliple Oracle insances maybe required o exrac daa from daabases associaed wih any or all of hem. In order for SAS o resolve and acion PROC OAACEXT saemens wihou error an appropriae version ofinter.exe mus be used o obain he daa. By defaul SAS expecs o find INTER.EXE in one of he direcories referenced by he SAS logical name SASLIBRARY which is normally assigned a sysem sarup ino he sysem logical name able. The Oracle revision level problem and any oher problems arising from operaing muliple Oracle insances wih SAS under VMS can be overcome by (a) using special SAS/ ACCESS direcories conaining copies of INTER.EXE linked o specific Oracle insances.and (b) using SASLIBRARY o ac as a swich o direc PROC OAACEXT calls o an appropriae INTER.EXE a runime. To implemen he mehod he following basic seps are required a Creae one direcory per Oracle insance o hold he SAS/ACCESS program INTER.EXE b For each Oracle insance creae a version of INTER.EXE linked o his Oracle insance in he direcory creaed above c Remove SASLIBRARY from he sysem logical name able o he job or process logical name able. d Provide a mechanism o reference he appropriae INTER.EXE direcory in he SASLIBRARY assignmen saemen prior o running SAS. 2psing PROC ORACEXT wih Conrolled Access Daabases Acces Oracle daabases is conrolled hrough he use of unique usemames and passwords before SQL or oher saemens can be processed and as wih oher general inerfacing producs SAS/ACCESS mus provide his informaion o Oracle rufore PROC ORACEXT can begin o build SAS daases from Oracle daa. Thisinformaion is provided o PROCORACEXT eiher in he form of procedure ()pions (NAME=and PWD=) or wihin. a password file (PWD1'ILE.DAT) referenced by he logical name PWDFILE [1]. In boh hese cases he user Will have direc knowledge of he usemame and password for he Oracle daabase accoun... Securiy and daa inegriy consideraions ofen give rise o Oracle applicaions wih special accouns accessed indirecly by he general er ha are designed o enhance or re.sric he Ora<J.efuncionaliy available o he user. A 'Daa Enry' accoun requiring iuser and updae privileges migh he an e?llllllple of an accoun requiring eohanced access and a 'Query Only' accoun anexaniple of. an accoun requiring limied access. Knowledge of husern;.iilesand password.ofhisype of accoun are usually resriced o he applicalom'adiudisraors and are no made generally available. SAS/ACCESS can pose a securily riskfor hese. applicaions. Using a variey of VMS DCL(Digial Commad La!lguage) echniques SAS/ACCE\SS can be made available o general users o conrolled access Oracle applicaions wihou hem requiring direc knowledge of he special accoun usemames and 60

3 passwords whils a high level of securiy for his infonnaion is mainained. By. placing he Oracle usemame and password in 'execue only' command files ha build he PROC ORACEXT job using emporary working files SAS/ACCESS jobs can be run wihou he user having direc knowledge of his accoun infonnaion. The mehod requires he following basic componens for successful operaion a An execue only DCL command procedure holding he applicaions' Oracle username and passwordha builds and submis a PROC ORACEXT job o a suiable bach queue in response o he users reques. b Operaing sysem mechanisms o conrol unauhorized use of he PROC ORACEXT DCL procedures c Mechanisms o remove or replace emporary working files and SAS log files ha may conain password infonnaion. I is also helpful o provide mehods o d Incorporae user defned SQL saemens and SAS daase infonnaion ino he PROC ORACEXT job e Provide he_user wih a lis of he SAS daase variable names upon successful compleion of he job. Implemenaion and Resllls ; " f' ; 1. j. 1. MSDRL's Neuroscience Research Cenre operaes Oracle daabases in conjuncion wih he SAS Sysem for basic research clinical rials and general adminisraion. CUrrenly hree producion Oracle sysems and one developmen sysem are in operaion supporing corporae clinical rials UK clinical rials basic research sysems and UK medical sysems developmen. All hese daabases hold daa ha has o. be ransfe.rred o SAS for analysis and all use Oracle securiy mehods ha resric he knowledge of special. accoun names and passwords _o applicaions supporsiuf only. In addiion o his organizaional separaion of Oracle. sysems resricions are aiso placed on he Oracle revision level for corporae sysems o ensure compaabiliy wih sysems world-wide resulinin differen versions.of Ora<le operaing simulaneously. The mehods described above have been implemened.on.adc VAX-620 operaing ndervms Version S.0-2. The Oracle insances were a revision levels S (one insance) and S.!.22 (hree insances) operaing in conjuncion wih SAS a revision levels.is... 1 Using SAS/ACCESS i'h Mluiple Oracle insimces i. ' The direcory srucure shown in Figure 1 holds he copies of INJER.EXE associaed wih e-ach of he NRC Oracle insances. These direcories are locaed ina SAS/ACCESS direcory ha lias been added o he sandard SAS direcory srucure and uses a nlllning cpnvenion based on he Oracle sysem idenifcaion leer (Oracle SID) o associae each SAS/ACCESS area wih he appropriae Oracle insance. Figure 2 shows he DCL command procedure used o assign he SAS logical e SASLffiRARY (which has bcenreinoved' from he sysem logical name able) priororunrung SA..This DCL places SASUBRARY in he process logical name able however oher logical name ables couldbe used.ifrequired. - \ " \ - \.. i 61

4 INTER.EXE INTER.EXE INTER.EXE INTER.EXE Figure 1 SAS/ACCESS direcory srucure used o hold he copies of INTER.EXE associaed wih he four Oracle insances operaed a he NRC. The use of he Oracle SID as he basis for he direcory naming convenion assiss in opimizing he DCL required for he associaed SASLffiRARY assignmen (Figure 2). r F' i To use he. copy of INTER.EXE associaed wih a paricular Oracle insance he user defines he Oracle symbols and logical names assigns SASLmRAR Y as above and aeivaes SAS. All subsequen SAS program references o PROC ORACEXT will hen use he version of INTER.EXE referenced by SASLIBRAR Y o build he SAS daase. In order o swich SAS/ACCESS o use an alernaive INTER.EXE his manoeuvre needs only o be repeaed before running SAS again. 2 Using PROC ORACEXT wih Conrolled Access Daabases The echniques described above o enable SAS/ACCESS o be used wih conrolled access Oracle daabases luis been implemened for use wih clinical rials daabases using wo DCL command files o ereae and run SAS/ACCESS jobs. The firs of hese command files creaes he SAS PROC ORACEXT program and passes his program o he second file which conrols execuion of he SAS job in bach mode. Full deails of hese files and he emporary file creaed during execuion; are presened in he Appendix. The fi r s 0 f he sed C L com ma nd f He s (N R C f i I e SASACCESS_<app_name>.COM where <app_name> is he name of he Oracle applicaion) builds he specific.sas/access job by performing he following asks a Creaing a SAS. program fi.l in a semi-hiddedirecory using a basic PROC. ORACEXT emplae o which is added a name for he SAS daase and he name of he file conaining he SQL o be used o.exrac he daa boh provided by he user b Submiing he second DCL command file o a ba.cb queue for processing passing o his command file heorade insance sysem idenificaion hesasprogram filename and he SAS daase filename. Access o SASACCESS_ <app...name>.comfiles is sricly conrolled. The VMS securiy scheme denies general access o all users excep he files' owner and SYSTEM (PROTECTION=(SRWEDORWEDGW». User access is hen conrolled hrough he use of an Access Conrol Enry (ACE) placed on he file. Each applicaion has a unique idenifier associaed wih i (of he form USER_ <app_name» and used as par of an ACE j 62

5 ! !!----- Obain he Oracle SID.! osid=fm1nm("oraclesid")!! If he Oracle SID is no assigned... 1 if (osid.eqs. "") 1! hen assign he SAS version of SASLIBRARY.! hen assign/nolog sysdisko sasroo[procs] sasroo[image ] sasexension[load] saslibrary 1! else include he Oracle Insance INTER.EXE direcory. 1 else assign/nolog sysdisko- sasroo [procs] sasroo [image] sasexension[load]- sasroo [sasaccess.oracle_' osid '] saslibrary endif!! Figure 2 SASLIBRARY assignmen. The DCL which needs o be run prior o running SAS assigns he logical name SASLIBRAR Y o include when appropriae he direcory for he Oracle insance in use prior o running SAS. This DCL operaes in conjuncion wih he SASIACCESS direcory srucure shown in Figure 1; oher direcory srucures would require appropriae modificaions o be made o his code if he SASIACCESS direcory srucure followed oher naming convenions. wih he characerisics IDENTIFIER=USER_ <app_name> ACCESS=EXECUTE placed on SASACCESS_<app_name>.COM. Auhorized applicaion users hen are graned he applicaion idenifier as par of heir AUTHORlZE profile and can hereafer gain access o he procedure. The second DCL command file (SASACCESS-SUBMIT.COM) conrols he execuion of he SAS job by a Esablishing he required Oracle and SAS environmen b Running he SASIACCESS job c Removing all job specific files conaining Oracle username and password infonnaion including he SAS log file 63

6 d Creaing he final user job files. Running hese procedures creaes one or wo user files following execuion. When he job has compleed successfully he SAS daase conaining he daa exraced from Oracle will be in a sandard *.SSD file ogeher wih a *.US file deailing he names of he SAS variables in he SAS daase. No SAS log file will be presen as hese files are removed by he bach job since hey conain he Oracle username and password informaion. If he job did no successfully complee a *.US file wih an error message reporing he fac will be presen If he job fails because Oracle reurns no recons a null SAS daase will also be presen; if oher Oracle errors or DCL or VMS errors occur only he *.US file will be presen. This use of he *.US file ensures he user is consisenly presened wih a leas one file of he oucome of he SAS/ ACCESS job and serves as a subsiue SAS log file. Deails of he user inerface and examples of he *.LIS files from ypical SAS/ACCESS jobs are presened in Figures 3 and 4 Daa exraced from Oracle using hese mehods can hen be used in oher SAS programs by referencing he SAS daase using he SET saemen in he DATA sep. In order o operae he sysem wih several applicaions each applicaion mus have is own copy of SASACCESS_ <app_name>.com suiably configured for use wih he applicaion. Figure 5 shows schemaically he muli-applicaion sysem used a he NRC which is accessed via a SAS/ACCESS opion menu for ease of use. SAS/ACCESS Inerface BDB Sysem Ener a name for he SAS daase SUBI89 Ener he name of he SQL file SUBI89.sQL SAS daasefile will be [RICHARDSON.SAS]SUBI89.SSD SAS daase conens files will be [RICHARDSON.SAS]SUBI89.US Job SASACCCESS_SUBMIT (queue SYSBATCH enry 228) sared on SYSBATCH Press <rn> o coninue Job SASACCESS_SUBMIT (queue SYSBATCH enry 228) compleed... Figure 3 User Inerface. The enninal screen oupu from a ypical NRC applicaion is shown. 64

7 1 Successful Compleion SAS 1322THURSDAYAUGUST CONTENTS PROCEDURE CONTENTS OF SAS MEMBER SASLlB.SUBI89 NUMBER OF OBSERVATIONS 143 NUMBER OF VARIABLES 18 MEMTYPE DATA # VARIABLE --ALPHABETIC LIST OF VARIABLES AND ATIRIBUTES--- TYPE LENGTH POSITION FORMAT INFORMAT LABEL 3 BOOK 14 COMMENTS 5 EXDATE 2 LNUMBER 16 OPDATE 17 OPERAT1 4 PAGE 18 PNUM 1 RECORD. 6 RES1 7 RES2 8RES3 9 RES4 10 RES5 11 RES6 12 RES7 13 RES8 15 SCIENTO CHAR 50 CHAR 16 CHAR 20 CHAR 10 CHAR 1 CHAR 10 CHAR 1 CHAR 10 CHAR 1 CHAR o OPERATION SCIENTIST 2 Unsuccessful Copleion SAS/Oracle Inerface 31-AUG Error in SAS Procedure Error creaing SAS Dae SU8189.SSD. a Daase may no exis (if no -.SSD file). b Daase may be empy. FiguI'e4 example.sof *.LIS files. Example 1 shows he *.LIS file produced following a successful SASIACCESS Inerface job; Example 2 he file produced following an unsuccessful SASIACCESS Inerface job. 65

8 Applicaion 1 A App.l App.2 App.N Applicaion 2 Applicaion N Bach Processing *.LIS/SSD Figure 5 Schemaic represenaion of he SAS/ACCESS sysem used o suppor he exracion of clinical and oher applicaion daa from he NRC's Oracle daabases for analysis by SAS. The solid lines represen penn anen files; he doed lines emporary files. The user eners he sysem via a menu driven inerface (A) from which each of he applicaion copies of SASACCESS_ <app_name>.com can be accessed (B). The menu sysem raps any file access violaions and reurns users o he menu sysem if aemps o use unauhorized applicaions are made. SASACCESS_ <app_name>.com creaes he emporarysas program files (C) based on user and applicaion requiremens and passes deails o SASACCESS_SUBMIT.COM (D) for processing. SASACCESS-SUBMIT.COM produces be final oupu in he fonn of he *.LIS and *.SSD files in he user [.SAS] subdirecory (E). Addiion of a new applicaion o he sysem requires only ha a new applicaion specific copy of SASACCESS_ <app_name>.com is made and he new applicaion added o he menu sysem. 66

9 Discussion The SAS/ACCESS Inerface produc for Oracle offers a valuable mehod of exracing daa easily from Ora'cle daabases ino SAS for furher processing. SAS/ACCESS provides a link beween Wo fundamenally differen producs and is use can be problemaic when used wih cerain Oracle configuraions. These problems arise for wo reasons. Firsly as par of SAS SAS/ACCESS exiss in a form available for all SAS programs o use whereas he Oracle daabase wih which i has o inerac may be one of several daabases coexising on he same sysem. Secondly access o SAS/ACCESS will generally no be under any conrol (ie. anyone can use i) whils access o Of;lCle daabases always requires auhorizaion. These differences can lead o problems when using SAS/ACCESS in Oracle environmens consising of muliple insances running applicaiolis where sric securiy has o be mainained on cerain accouns. This paper describes a mehod o overcome some of hese problems enabling he full value and versailiy of SAS/ACCESS o be used in hese circumsances whils mainaining any securiy arrangemens buil ino he Oracle applicaions. The firs problem ha of operaing SAS/ACCESS in conjuncion wih muliple Oracle insances has been solved by providing each Oracle insance wih is own copy of he SAS/ACCESS program. By hen employing mechanisms o dynamically assign (or. reassign) he SAS logical name SASLIBRARY when SAS is invoked o include he pah o he appropriae direcory SAS/ACCESS can operae wih any number of Oracle insances. { n r r ;- ' ; ' 1 f The need o provide individual copies of INTER.ExE for each Oracle insance is no sricly required 3.'1 only hose insances running differen versions of he Oracle code require a new image. Experience suggess however ha providing individual copies of INTER.EXE for each Oracle insance is desirable. Paricularly Oracle upgrade problems are resriced o specific insances only and modificaion and esing paricularly of developmen daabases bas no knock-on effec ono oher more criical sysems. The major overhead in adoping his approach is he need o provide mechanisms o assign SASLIBRARY prior o running SAS. This however can be minimized by he inclusion of he necessary DCL in suiable command files acivaed a login or when he Oracle applicaions are run.. The second poenial problep wih SAS/ACCESSas wih all Oracle inerfacing producs is he need o provide ljsemamesand passw!>rds o' he daabase managemen sysem before daa be exraced rom. he daabase.when users have co!ilple access o passwords no problem exiss bu many Sensiive or. coll'!plex Qracle applicaiosuse ecniques ba provide lilcess special applicaion accouns hidden from he user. A he NRC all. clinical daabases adop hese mehods and knowl ge of he applicaion accoun usemames and passwords is resri.ced o developmen and operaions saff only. Providing SAS/ACCESS funcionaliy in his siuaion has been solved using DCL echniques ha build special SAS/ACCESS jobs auomaically and use bach processing o run he SAS job. This approach enabies all funcionaliy o be reained; whils providing he necessary securiy for he Oracle applicaions. WhilS iniproving securiy considerably.he mehod is no foolproof. Users have o have. he applicaion usemames aqd passwords in read access files for a leas he duraion of he bach processing and could herefore obain hem for use direcly in PROC ORACEXT. However by using semi-hidden direcories fur processing (a he NRC all users have a scrach direcory ildependen of heir uller direcories) and by appropriae pos-job 'clearing rip' his informaion is avahable only ransienly and only very experienced VMS wiers are likely o. find i. In l \. \. - ' 67

10 conras. seeking his informaion a oher imes will no mee wih success as he useinames and passwords are held in execue-only files. This echnique offers some advanage over oher suggesed SAS/ACCESS mehods o hold Oracle accoun names and passwords [1] (eg he use of he 10gicaI name PWDFII...E and a password file). as in hese cases he user mus have pennanen read access o he password file. The echniques described here also simplifies SAS/ACCESS suppor for.he Oracle applicaion suppor saff. and offers some advanages for cusomizing SAS/ACCESS jobs. The requiremen for each Oracle applicaion o have is own single copy of SASACCESS_ <app_name>.com enables he DCL o be locaed and suppored as one of he applicaion programs. and is herefore easily mainained. In paricular. password managemen is simplified. wih renewal of passwords being possible wihou user knowledge and wih minimal applicaion downime. In addiion o ease of mainenance. he need for one SASACCBSS_<app_name>.COM per Oracle applicaion also enables he PROC ORACEXT program o be ailored o sui he paricular applicaion. The examples presened here assume he users will be developing SQL saemens heinselves. and herefore makes use of he SAS %INCLUDE saemen in order o incorporae hese saemens a runime. However. here is no requiremen for his o be he case. and SAS programs exracing pre-defined Oracle daa. or running full SAS analysis jobs could jus as easily be he funcion of he PROC ORACEXT program.. The echniques described here overcome some of he limiaions of using SAS/ACCESS in muliple insance Oracle environmens where access o applicaions is sricly conrolled. Whils he mehods presened here apply only o SAS/ACCESS for Oracle on VMS sysems. he general principles may also be applied o oher SAS/Oracle inerfacing ools [2]. or he oher producs in he SAS/ACCESS range. References [1] Angnymous. SAS Technicai Repor P-18!. SAS/ACCESS Inerface o Oracle. SAS InsiUe Inc.. Cary. Norh Carolina. USA. (1988).. [2] Anonymous OSTAT A Link Beween ORACLE and The SAS Sysem. Sofware Inerfaces Iilc. Houson; Texas. USA.... Aclmowledgemen ".;." Theauor woui4likeomr.d.joon for valuable. dlscussioll8 d J.B for assisance wih he preparaion of he manuscrip. Address for Correspondence Quiniles(UI<;) Limied. 56 MinserSee;. Reading.. Brksbire. RGl 2lB. Unied Ki[Igdom... 68

11 Appendix The following secions presen he deails of he DCL command files and he emporary SAS program file used o run SAS/ACCESS jobs a he NRC. The following DCL is specific o he NRC (1) say wrie sysoupu (2) area assigns all symbols and logical names for he program or uiliy passed as pi o he procedure (3) uiliies logical name for he DCL uiliies direcory (4) sysscrach logical name for he user scrach direcory. The files creaed by hese DCL files are auomaically placed in a user SAS subdirecory [.SASJ Wrien by A.Richardson 1O-JUL I-----Oracle applicaion accoun informaion osid Oracle insance SID onain Applicaion accoun name opwd Applicaion accoun password 1 1 opid="u" onam="qry_account" opwd="qry_password" Obain SAS daase name (sasdaase) and SQL filename (sqlfilename) from user. 1 1 say "SAS/ACCESS Inerface <Applicaion Name>" say"" say nn read!promp="ener a name for he SAS daase " syscommand sasdaase read!promp="ener he name of he SQL file." syscommand sqlfilename Exrac user ID from usemame. 1 uid=fuser() comma=flocae(" "uid) pid=fexrac( comma+ 1flengh(uid)-comma-2uid)!!----- Inform user of files o be creaed. 1 say 1111 say li. say "SAS daase file will be ["+pid+".sas]"+sasdaase+".ssd" say "SAS daase conens file will be ["+pid+".sas]+sasdaase+".lis" say"" say lin!!----- Creae a unique filename (fnam) for he emporary file.! fnam="sasaccess"+fcvime(fimeo"absolute" "DA Y")+ - fcvime(fime() "ABSOLUTE""HOUR")+ - 69

12 fcvime(fime()... ABSOLUTE... MINUTE.. )+ - fcvime(fime()... ABSOLUTE... SECOND.. ) Creae he SAS emporary program file in he users scrach direcory. 1 1 open/wrie sasfile sysscrach'fnam'.sas wrie sasfile "OPTIONS OBS=O;" wrie sasfile "LIBNAME SASLIB SYSUSER(+pid+".SAS];" wrie sasfile "PROC ORACEXT OUT=SASLIB. "+sasdaase "+NAME='"+onam+''' PWD=.. +opwd+.. ;" wriesasfile "%INCLUDE "'+sqlfilename+"';" wrie sasfile "PROC CONTENTS DATA=SASLffi."+sasdaase+";" wrie sasfile "RUN;" close sasfile 1--- Submi he SAS/ACCESS bach job wih he required pai'ameers.! submi/nolo&...file/noify /parameers=('fnani' sasdaase'.' osid') - ui1iiessasaccess_submi 1!----- Le he user read he screen.! 1 say fill say Ui say" " inquire/nop.uncuaion ans "Press <rn> o coninue "!--- EndofDCL. 1 2 SASACCESS_SUBMlT.COM ' l. '. ' e i ' Wrien by A.Richardson ll-jul !!---- Parameers!--- pi ;= SAS program filename p2 = Name for SAS daase and relaed files p3 = Oracle insance SID Assign he Oracle symbols and logical names for his job. 1. areaoracle_'p3' Assign SASLIBRARY for his job.! area sasaccess! Run he SAS/ACqsS job using he emporary SAS file. 1 sas sysscrach pl.sas Delee he SAS/ACCESS emporary file. 1. ; j. \. " 70

13 delee sysscrach'pl '.S38;*! Delee he SAS logfile. 1 delee 'p l'.log;* Creae or rename a * LIS file for he user If SAS job OK Rename *.US file o mach SAS daase name. 1---If SAS job no OK Creae *.LIS file wih error message. 1 if (fsearch(""pl'.lis").eqs."") hen oped/wrie lisfile 'p2'.lis wrie lisfile "" wrie lisfile "SASIOracle Inerface "+fimeo+".". wrie lisfile "" wrie lisfile "Error in SAS Procedure Error creaing SAS Daase." wrie lisfile " a Daase may no exis (if no *.SSD file)." wrie lisfile n b Daase may be empy." wrie lisfile "" close lisfile else rename 'pl'.lis 'p2'.lis endif End ofdcl. 1 3 SASACCESS SAS (Temporary File) J! j;!'.. " ' { -) E j) G &;\.J f (. r ;'.. { ;' f!; j j; I \ lc '-' OPTIONS OBS=O; LIBNAME SASLIB 'SYSUSER;[RICHARDSON.SAS]; PROCORACEXT OUT=SASLIB.DATAI NAME='QRY_ACCOUNT' PWD='QRY_PASSWORD'; %INCLUDE 'SQL_DATAl.SQL'; PROC CONTENTS DATA=SASLffi.DATAli RUN; This file was creaed\lsing he following responses for informaion requesed by SASACcEsS_ <app_name>.com Ener a name for he SAS daase DATAl Ener he name of he SQL file. SQL_DATA1.SQL 71