LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (March 1998, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 13 Mar 1998 19:26:12 -0500
Reply-To:     Interhub Mailer Daemon <support@LANSOFT.QUINTILES.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Interhub Mailer Daemon <support@LANSOFT.QUINTILES.COM>
Organization: Quintiles, Inc.
Subject:      Message Delivery Refused - Unknown Account
Content-type: text/plain; charset="US-ASCII"

Please present this message to your Administrator.

Dear Administrator:

The email message below has NOT been delivered to the internet because InterHub was unable to determine the status of your account. This may be due to your site being so new that the InterHub database has not updated with your information yet, or possibly because you have not asked Lansoft to provide this site with Internet access.

The site in question appears after the @ sign below.

Examined address: SAS-L@QRTPSMTP (SAS(r) Discussion) {SAS-L@AKH-WIEN.AC.AT}

If this symptom continues for longer than 60 minutes or if you otherwise feel that this is in error, please contact us by replying to this message or calling us at 614-786-1713 to verify and validate your account information.

Note: If this message was intended to any Lansoft staff, it was sent regardless of the above condition but only to Lansoft recipients.

Your original message is included below: ---------------------------------------

240Send-to: mail@mailrout {richard_paterson@yahoo.com} To: SAS-L@QRTPSMTP (Recipients of SAS-L digests) {SAS-L@AKH-WIEN.AC.AT} 200MCB-options: YNYNANA Date-posted: 13-Mar-98 18:12:08 220Hop-count: 8 200O-C2-Routed-By: IH; received from QRTP; at 13-Mar-98 19:04:51 200O-C2-Routed-By: QRTP; received from QEDI; at 13-Mar-98 18:15:31 200O-C2-Routed-By: QEDI; received from QEDI2; at 13-Mar-98 23:12:08 202C2-ID: 84E8443681DC0000 200O-C2-Routed-By: QEDI2; received from -Local-; at 13-Mar-98 23:11:58 O-C2-Forwarded-by: RPATERSO@QEDI2 200O-C2-Routed-By: QEDI2; received from QEDI; at 13-Mar-98 23:11:56 200O-C2-Routed-By: QEDI; received from -Local-; at 13-Mar-98 23:11:00 O-C2-Forwarded-by: RPATERSO@QEDI 200O-C2-Routed-By: QEDI; received from QRTP; at 13-Mar-98 23:10:51 200O-C2-Routed-By: QRTP; received from -Local-; at 13-Mar-98 18:12:08 Sender: SAS-L@QRTPSMTP (SAS(r) Discussion) {SAS-L@AKH-WIEN.AC.AT} O-SMTP-Date-posted: 13-Mar-98 18:11:48 -0500 From: LISTSERV@QRTPSMTP (Automatic digest processor) {LISTSERV@AKH-WIEN.AC.AT} Reply-to: SAS-L @ QRTPSMTP ("SAS(r) Discussion") {SAS-L@AKH-WIEN.AC.AT} Subject: SAS-L Digest - 12 Mar 1998 to 13 Mar 1998 Date: 13-Mar-98 18:00:21 -0500 Message-id: AAE8443601DC0000 O-SMTP-Envelope-From: <owner-SAS-L@VM.AKH-WIEN.AC.AT> 200MHS-id: 84E8443681DC0000 200Via-host: QRTP.QRTP 200O-C2-Serial-Host: QRTP 200O-C2-Serial-No: IAANAAAANM, IAANAAAMIA, IAANAADPJE, IAANAADPJF, IAANAADPJD, IAANAAEAHA, IAANAAEAGO, IAANAAEAGM, IAANAAEAGP, IAANAAEAGN, IAANAPECGC, IAANAPEFMI, IAANAPEJBA, IAANAPEHGN, IAANAPEJKA

There are 45 messages totalling 3035 lines in this issue.

Topics of the day:

1. Merge format catalogs? (6.12 NT) (2) 2. SAS Output -> MS Word97 3. I like your site (3) 4. Matching data on tax forms to individuals' financial records 5. Re[2]: MVS & Missing Files 6. Suppressing printing of carriage control (2) 7. Help: remote central macro library? (2) 8. Codes on email addresses (4) 9. Anybody doing Version Control? (2) 10. (MVS) Re(4): Re: MVS & Missing Files 11. SAS opportunity in Raleigh 12. Merging datasets with common vars 13. Please explain: List input (implied by INFORMAT) is incompatibale with the specified binary informat. 14. Duh. 15. SAS and Latex 16. TSO and GDG's (under IBM MVS system) 17. From Unix to PC 18. Subsetting very large sasdataset, 19. Splitting a variable into two variables based on a character somewhere in the field (2) 20. Delaware SAS Opportunity 21. email codes 22. FW: Codes on email addresses 23. Subsetting very large sasdataset (Related) (2) 24. MVS & Missing Files 25. Capturing return codes from a device 26. X command & EXIT (4) 27. Data _null_ help 28. Thanks![RE: Read SAS datasets across different platforms] 29. SAS/SQL Programming Position at Hoffmann La-Roche 30. Proc Tabulate Question 31. Proc Tabulate Question-2

----------------------------------------------------------------------

Date: Thu, 12 Mar 1998 18:09:01 -0500 From: RHOADSM1 <RHOADSM1@WESTAT.COM> Subject: Re: Merge format catalogs? (6.12 NT)

[please excuse if this is a duplicate posting]

<<Tom Frenkel asks>> I'm running SAS 6.12 on a Windows NT machine. I have a number of format catalogs, each named FORMATS.SC2, in various subdirectories. Is there a way, without actually rerunning the PROC FORMAT steps, to merge or consolidate these catalogs into one "big" format catalog? I know that I can always use the multiple format catalogs in a SAS job by specifying "OPTIONS FMTSEARCH", but I am going to be sending a SAS dataset to someone else, who might not know how to use this option. Thanks! <<end question>>

Tom,

Try the following:

1. For each format catalog, run PROC FORMAT with the CNTLOUT option to create a SAS data set containing all the necessary information about the formats.

2. Run a data step to combine all of the SAS data sets created in (1). This will be simple if you are sure that the same format is not in more than one library. If this assumption is not true, you will need some additional code to deduplicate and/or resolve inconsistencies.

3. Run PROC FORMAT with the CNTLIN option, which will use the SAS data set created in (2) as input to create your "big" combined format catalog.

Good luck!

Mike Rhoads Westat RhoadsM1@Westat.com

------------------------------

Date: Thu, 12 Mar 1998 15:22:53 -0800 From: "Michael F. Murphy" <murphym2@NATIONWIDE.COM> Subject: Re: SAS Output -> MS Word97

I have found it best to load the following fonts into Word 97: SAS Monospace SAS Monospace bold

Then your PROC TABLUATE sheets should come out very nicely. -- Michael F. Murphy Nationwide Insurance

------------------------------

Date: Thu, 12 Mar 1998 07:40:35 -0000 From: coolio@UNKNOWN.COM Subject: Re: I like your site

Hello,

I have a document that can place you in the top 10 listings of the search engines. This document will show you the tricks of the trade . How would like to have more traffic to your web site? Well here is the answer to that question.

Simply fill out the form below and mail it in to me along with .00 US CASH and I will e-mail the files to you.

As once as I receive your payment I will e-mail you the files and then you are free to do what you want with the files. There are over 30 pages of text that will show you what tricks that the others on the Internet are using to get sales. I hope to hear from you soon.

Have a nice day

-----------------------------------------------------------------

Please fill out this form completely and mail it to the following address. Please write in L A R G E B L O C K L E T T E R S. I can't fill your order if I can't read it.

Scamper Technologies 400 Alexandre St #1. Sherbrooke Quebec Canada J1H 4T3

Name ____________________________________________

Address ____________________________________________________

____________________________________________________

____________________________________________________

Phone Number _____________________________

Work Number _____________________________

E-mail Address __________________ @ ________________________

Web Page URL http://___________________________________________

-----------------------------------------------------------------

------------------------------

Date: Thu, 12 Mar 1998 18:28:33 -0500 From: HERMANS1 <HERMANS1@WESTAT.COM> Subject: Matching data on tax forms to individuals' financial records

I am studying disclosure-proofing of financial information collected from individuals and know something about using SAS and other programs to link records for persons on data (as opposed to key) fields. Could anyone suggest types of financial data found on tax forms (wage, royalties, dividends, capital gains, or other income; deduction types; etc.) that in combination might help identify individuals? Also, what methods might one use to help distinguish one individual from another?

I would especially like to hear from anyone involved in credit or mortgage scoring, financial rating, or other industries that make use of financial information. I will not reveal my sources. Neither do I need to know much in way of specifics other than the types of financial information that provide the greatest discriminatory power.

Thanks for any insights that you might share. Sig

------------------------------

Date: Thu, 12 Mar 1998 14:41:13 -0600 From: Jack Hamilton <jack_hamilton@HCCOMPARE.COM> Subject: Re[2]: MVS & Missing Files

Michael Stuart <mstuart@PRUDENTIAL.COM> wrote:

>Thanks (Tim Berryhill and Ray Pass and Bernard Tremblay) for getting me >started. I uncovered information on FILEEXIST to check if a file is out >there, and started putting together a solution. Unfortunately ... every >time I FILEEXIST a file that doesn't exist -- I get a system error -- kind >of irksome if you consider the purpose of the function. The specific error >I get is: "FATAL: Undetermined execution error detected in the execution >of the data step program. Aborted during the EXECUTION phase."

This may depend on the version and service level of SAS you're running. I got all sorts of odd messages (similar to the one you're seeing) under VMS when I used the new data step SCL functions until we upgraded to 6.12. That is, the functions were there in the older version (6.11, I think), but didn't always work.

------------------------------

Date: Thu, 12 Mar 1998 18:09:10 GMT From: Harvey CoChien <Harvey.CoChien@ALZA.COM> Subject: Suppressing printing of carriage control

How do I suppress printing the carriage control on PC of a text file created by SAS proc printto? Thanks for any clues.

------------------------------

Date: Thu, 12 Mar 1998 13:15:33 -0600 From: boston01@HOTMAIL.COM Subject: Re: Help: remote central macro library?

Here is one possible solution.

create a macro using PROC DOWNLOAD to copy the macro to the local working library at request time. Let us name the macro getmacro. It goes like this:

%GetMacro(MacroNm); %LET DIRWORK =%SYSFUNC(PATHNAME(WORK)); RSUBMIT; PROC DOWNLOAD INFILE = '\some where\TheMacro.sas' OUTFILE="&DIRWORK.TheMacro.sas" RUN; ENDRSUBMIT; %MEND GetMacro;

point the auto macro call library to the work dir before user call the macros on your remote side. After the session, download macros will be gone away...

hope that helps

> ZHAO,JUN BDM BIPUS wrote: > > > > Hi, everyone: > > > > Thank everyone for response my early question about creating 'remote > > central macro library'. Options of using 'SASAUTO=' or MAUTOSOURCE, > > suggested by several people, do not work across the platform. The > > problem we are facing is server is using Unix and client is using Win95, > > and they are connected by SAS/Connect. We are not able put Unix path in > > SASAUTO path. If we put macros in server's SAS catalog, remote library > > engine does not support accessing remote catalog. Any other thought? > > Will filename using FTP help? >

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading

------------------------------

Date: Thu, 12 Mar 1998 18:21:41 -0700 From: Steve Bousquin <sbous@LAMAR.COLOSTATE.EDU> Subject: Codes on email addresses

I give up on finding a suitable place to post this question, so I'll just ask some statisticians, who of course know everything. The question is where I can find a directory that explains the codes used in email addresses, especially the 2-letter code at the end of addresses that are overseas, which appear to be codes for countries.

Steve Bousquin

------------------------------

Date: Thu, 12 Mar 1998 19:17:35 -0600 From: Jack Hamilton <jack_hamilton@HCCOMPARE.COM> Subject: Re: Codes on email addresses

Steve Bousquin <sbous@LAMAR.COLOSTATE.EDU> wrote:

>I give up on finding a suitable place to post this question, so I'll >just ask some statisticians, who of course know everything.

Perhaps, but I'd guess that most people on SAS-L aren't statisticians.

>The >question is where I can find a directory that explains the codes used in >email addresses, especially the 2-letter code at the end of addresses >that are overseas, which appear to be codes for countries.

They are. Use a web browser to look for "ISO Country Codes" in yahoo, and you will find several different sources.

"Overseas" is probably not the right term to use, since it depends on where the reader is, or where you are (which we don't know). It's not accurate, since there are email addresses without the country suffix which are not in the US, and email addresses with the country suffix which are in the US. And, of course, Canada and Mexico aren't overseas, and Hawaii is.

There are actually two naming systems, one which uses country codes and one which doesn't.

------------------------------

Date: Fri, 13 Mar 1998 22:33:26 +1300 From: Robin and Charmaine Templer <templer@IBM.NET> Subject: Re: Merge format catalogs? (6.12 NT)

This is a multi-part message in MIME format. --------------48F3316329153AB46E371078 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit

Try the following, if you have SA/AF licensed: proc build BATCH c=libname.bigcat ; merge c=libname.firstcat replace ; merge c=libname.firstcat replace ; etc ... run ;

The replace on the merge statement can be a tad dangerous - be careful !!

RHOADSM1 wrote:

> [please excuse if this is a duplicate posting] > > <<Tom Frenkel asks>> > I'm running SAS 6.12 on a Windows NT machine. I have a number of format > catalogs, each named FORMATS.SC2, in various subdirectories. Is there a > way, without actually rerunning the PROC FORMAT steps, to merge or > consolidate these catalogs into one "big" format catalog? I know that I > can always use the multiple format catalogs in a SAS job by specifying > "OPTIONS FMTSEARCH", but I am going to be sending a SAS dataset to someone > else, who might not know how to use this option. Thanks! > <<end question>> > > Tom, > > Try the following: > > 1. For each format catalog, run PROC FORMAT with the CNTLOUT option to > create a SAS data set containing all the necessary information about the > formats. > > 2. Run a data step to combine all of the SAS data sets created in (1). > This will be simple if you are sure that the same format is not in more than one > library. If this assumption is not true, you will need some additional code to > deduplicate and/or resolve inconsistencies. > > 3. Run PROC FORMAT with the CNTLIN option, which will use the SAS data set > created in (2) as input to create your "big" combined format catalog. > > Good luck! > > Mike Rhoads > Westat > RhoadsM1@Westat.com

-- ====================================================================== Robin & Charmaine Templer Email: templer@ibm.net TRAC Consulting Ltd Fax: 64-4-476-4299 Wellington, New Zealand.

--------------48F3316329153AB46E371078 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Robin Templer Content-Disposition: attachment; filename="vcard.vcf"

begin: vcard fn: Robin Templer n: Templer;Robin org: TRAC Consulting Ltd adr: 49 Campbell Street;;;Karori;Wellington;;New Zealand email;internet: templer@ibm.net tel;work: 64-25-875-484 tel;fax: 64-4-476-4299 tel;home: 64-4-476-4299 x-mozilla-cpt: ;0 x-mozilla-html: TRUE version: 2.1 end: vcard

--------------48F3316329153AB46E371078--

------------------------------

Date: Fri, 13 Mar 1998 12:24:52 -0000 From: Phil Mason <woodst@SURFAID.ORG> Subject: Re: Anybody doing Version Control?

I recently looked at the SCM (available for download from the SAS web site) which is quite good for version control when deveoping in SAS/AF. However if just using plain old base code, it "can" be used, but is not intended for that.

I have worked on a very complex & involved change control system in the past which handled multiple versions, platforms, all types of code, etc. That was a nice system but took a lot of development and maintenance.

I recently wrote a nice little system which implemented change control with a dataset and 3 macros. It does about 90% of what my old complex system did. I basically just keep a dataset with lock information. I then have a macro for checking out and another for checking in. There is also an archive macro. The macros handle base SAS, catalog members, version numbering, etc.

If anyone is interested I could send them the code.

Phil Mason

> -----Original Message----- > From: SAS(r) Discussion [mailto:SAS-L@UGA.CC.UGA.EDU]On Behalf Of Deanna > Castorena > Sent: 02 March 1998 19:39 > To: SAS-L@UGA.CC.UGA.EDU > Subject: Anybody doing Version Control? > > > Our group is in the process of defining departmental procedures and > we're interested in developing some sort of revision control process for > batch programs and web-related programs for all of our SAS programs. > With ISO and CMM becoming a bigger part of everyone's internal > procedures, I'm sure there are a few of you who have already experienced > the pain. Is there anybody out there who would be willing to share > their experience with me on version control of programs? I would be > interested in tools, processes, procedures, or insight you would like to > pass on. > > Thanks, > Deanna Castorena >

------------------------------

Date: Fri, 13 Mar 1998 08:14:21 -0500 From: "Michael A. Raithel" <MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM> Subject: (MVS) Re(4): Re: MVS & Missing Files

In an interesting exchange between Michael Stuart and Tim Berryhill III, Michael posted (in part):

>Re: your comment about not loading the same cycle/files >more than once ... I'll have to think your comments. PROC >IDCAMS though? Where is that documented? >

Michael, the only place that I have ever seen PROC IDCAMS documented is in:

SAS Communications, Vol XXII, No. 2, Second Quarter 1996 Technical Tips (column) page 56.

This was the source that, for me, opened the door to being able to execute actual IBM utilities from within the SAS System for Information Delivery. And, it is a door worth opening!

Michael, I see that Tim gave you some good advice on PROC IDCAMS. The rest of this posting amplifies that advice. Below, you will find an example of PROC IDCAMS, with explanation, that I posted in April of last year. Perhaps a full-fledged example will assist you in getting off the ground...

BEGIN EXAMPLE: -------------

//******************************************************** //* EXECUTE 'PROC IDCAMS' (IDCAMS) UNDER SAS. * //******************************************************** //STEP01 EXEC SAS,OPTIONS='SYSIN=SASINPUT' //SYSPRINT DD DSN=&&TEMPDSN, // DISP=(,CATLG,DELETE), // SPACE=(CYL,(1,1)),UNIT=SYSDA, // DCB=(RECFM=FBA,LRECL=133,BLKSIZE=27930) //SASINPUT DD *

/*********************************************/ /* ALLOCATE TEMP SYSIN DATA SET. */ /*********************************************/ FILENAME SYSIN '&SYSIN' SPACE=(CYL,(1,1)) UNIT=SYSDA RECFM=FB LRECL=80 BLKSIZE=27920;

/*********************************************/ /* PUT IDCAMS STATEMENT IN THE SYSIN DATA SET*/ /*********************************************/ DATA _NULL_; FILE SYSIN;

PUT " LISTCAT LVL(annabels.gdg.base)";

RUN;

/*********************************************/ /* EXECUTE IDCAMS AS A SAS PROC. OUTPUT GOES*/ /* TO THE SYSPRINT DATA SET. */ /*********************************************/ PROC IDCAMS; RUN;

/*********************************************/ /* PARSE THE SYSPRINT DATA SET TO GET THE */ /* SPECIFIC GDG DATA SET NAMES. */ /*********************************************/

DATA DSNAME(KEEP=DSNAME); INFILE SYSPRINT;

LENGTH DSNAME $44.;

INPUT @1 BIGLINE $133.;

IF BIGLINE =: '0NONVSAM' THEN DO; DSNAME = SCAN(BIGLINE,3,' '); OUTPUT; END; ELSE DELETE;

RUN;

/*********************************************/ /* PROCESS THE CAPTURED GDGNAMES... */ /*********************************************/

... more SAS code to process the individual GDG's ...

RUN;

Let's first consider the JCL in the example above. Since both IDCAMS and the SAS System use the SYSIN DD name, it is necessary to reassign the SAS System's SYSIN DD name. This is done through OPTIONS='SYSIN=SASINPUT' on the EXEC statement. You will see that, further down, all of the SAS code follows the SASINPUT DD statement.

Also in the JCL, a temporary SYSPRINT data set is created to capture the output of the IDCAMS command. After that output is captured in this temporary data set, we will process it with SAS character handling functions.

In the SAS code, we begin by creating a SYSIN file for IDCAMS. This SYSIN file must contain valid IDCAMS commands for 'PROC IDCAMS' to execute. We populate the SYSIN file in the DATA _NULL_ step with an IDCAMS LISTCAT command. Everything within the double quotes (including the leading blank) will be inserted into the SYSIN file. It is in the PUT statement that you will put the base nodes of your GDG. In the example, the base nodes are: ANNABELS.GDG.BASE.

Now, IDCAMS is executed from within SAS via 'PROC IDCAMS'. IDCAMS processes the IDCAMS statements within the SYSIN file and writes output messages to the SYSPRINT file. We have directed IDCAMS to list every cataloged level of the GDG named ANABELS.GDG.BASE.

The final SAS DATA step parses the SYSPRINT data set, capturing the DSNAMES of the GDG's. Those DSNAMES are written to variable DSNAME and populate a data set called DSNAME. At this point, you have all of the full GDG names for the ANABELS.GDG.BASE generation data set. You can go on to do... what you have to do with them.

END EXAMPLE; -----------

Michael, I hope that the example, above, gives you a good home base for making your own forays into the world of executing PROC IDCAMS from with the SAS System. Good luck!

I hope that this suggestion proves helpful now, and in the future!

Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Michael A. Raithel "The man who wrote the book on performance" E-mail: maraithel@mcimail.com Author: Tuning SAS Applications in the MVS Environment +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Can you see the real me? Can ya? CAN YA? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

------------------------------

Date: Fri, 13 Mar 1998 09:06:57 -0500 From: ksklenic@AEROTEK.COM Subject: SAS opportunity in Raleigh

Here in the Raleigh, NC area we have an opportunity for a SAS programmer. MAXIM Group is an IT consulting firm providing professionals to all companies. We are looking for a SAS programmer to work on a statistical gathering and projecting application on a very long-term project. 3 years of SAS experience, SQL, and UNIX. Great project with a dynamic companu and team. Please contact Kim Sklenicka at 1-800-369-8994 or contact me by email at ksklenic@maximgroup.com. Thank you for your interest, Kim Sklenicka

------------------------------

Date: Fri, 13 Mar 1998 07:59:53 -0600 From: Hays McLean <Hmclean@PEACH.FRUIT.COM> Subject: Re: Merging datasets with common vars

Nat,

Thanks for your tip. I've never known of this feature before, but I have numerous uses for it.

If it's undocumented, I wonder if it's ever going away?

--Hays McLean

Martha Wooding wrote: > Hays > > I know you have gotten a number of replies on your posting. Your > particular example may not work with the following but I have found > that SAS has an undocumented (I can't find it) feature such that one > could write > > DROP A: BC: ; > > and any variables whose names started with "A" or "BC" will be dropped. > I stumbled on this recently when I had a situation in which I wanted to > do so and recalled the method of selecting or excluding files when > running PROC SOURCE (this is an MVS procedure) and the method worked! I > asked tech support and as I recall they said something like "Yes, it > does work in your case but it may not work for all procs, etc). Of > course, this syntax is also similar to using "IF A=: ..." when > subsetting. > > Nat Wooding > Virginia Power

------------------------------

Date: Fri, 13 Mar 1998 09:26:14 +0100 From: Gerard.HANNEY@EUROSTAT.CEC.BE Subject: Please explain: List input (implied by INFORMAT) is incompatibale with the specified binary informat.

<WINa2f-980313082648-08A4*/G=Gerard/S=HANNEY/O=EUROSTAT/PRMD=CEC/ADMD=RTT/C=BE/ @MHS> X-LSVTag: MIME-Version: 1.0 X-LSVTag: Content-Type: text/plain; charset=us-ascii To: $PEER$ <SAS-L@VTVM1.CC.VT.EDU>

The following log is from a SAS program which is automatically generated to read in an external file which is in EBCDIC format. The variables are read in as Character then converted using an input() function to the required value. It works ok for the character variables but I get a WARNING for the packed numeric variables - the program continues to read the data apparently ok though.

Can anyone explain the Warning message?

Thank you,

Gerard.

< --------- SAS Log ----------------------------------------------------> data l; infile '/home/com_dpscurrent/workdata/B0045130.DECL.9634.NL.SPG_OR.F66' RECFM=F LRECL=66 END=END;

attrib PER label =" PER" format = $4. informat= $4.; PER='9652';

input @1 X1 $4. @; attrib PER_OR format = $4. informat= $EBCDIC4. label ="PER_OR" ; PER_OR=input(X1,$EBCDIC4.); if _ERROR_=1 then do; _ERROR_=0; ERRTOT+1; ERRX1+1; ERRNM1='PER_OR'; HEX1=put(X1,$HEX8.); put PER_OR= OBS= HEX1=; end; ... ... Code removed for remaining character variables ...

input @25 X9 $7. @; attrib VAL_CUM 9 format = 17.3 informat= S370FPD7.0 ---------- 535

label ="VAL_CUM" ; VAL_CUM=input(X9,S370FPD7.0); if _ERROR_=1 then do; _ERROR_=0; ERRTOT+1; ERRX9+1; ERRNM9='VAL_CUM'; HEX9=put(X9,$HEX14.); put VAL_CUM= OBS= HEX9=; end;

input @32 X10 $7. @; attrib QNT_CUM format = 14.1 informat= S370FPD7.0 ---------- 535

label ="QNT_CUM" ; QNT_CUM=input(X10,S370FPD7.0); if _ERROR_=1 then do; _ERROR_=0; ERRTOT+1; ERRX10+1; ERRNM10='QNT_CUM'; HEX10=put(X10,$HEX14.); put QNT_CUM= OBS= HEX10=; end;

input @39 X11 $7. @; attrib SUP_CUM format = 14.0 informat= S370FPD7.0 ---------- 535

label ="SUP_CUM" ; SUP_CUM=input(X11,S370FPD7.0); if _ERROR_=1 then do; _ERROR_=0; ERRTOT+1; ERRX11+1; ERRNM11='SUP_CUM'; HEX11=put(X11,$HEX14.); put SUP_CUM= OBS= HEX11=; end;

if END then do; array ERRNM {*} $ ERRNM1-ERRNM11; array ERRX {*} ERRX1-ERRX11; put _PAGE_@; if ERRTOT gt 0 then put @30 'Total Read errors =' ERRTOT //; DO I=1 to 11; if ERRX{I} gt 0 then put @10 ERRNM{I} ' READ ERRORS ' ERRX{I} /; end; end; OBS+1; DROP X1-X11 ERRNM1-ERRNM11 ERRX1-ERRX11 ERRTOT I HEX1-HEX11; RETAIN OBS; RUN;

WARNING 535-185: List input (implied by INFORMAT) is incompatible with the specified binary informat. Formatted input will be used.

< --------------------------------------------------------------------------- >

I use SAS 6.12 under Solaris. ************************************************************ * G. Hanney,JMO B3/69, L-2920, Luxembourg. :Ph. 4301-34929 * * ======================================================== * * X400: G=Gerard; S=HANNEY; O=EUROSTAT; P=CEC; A=RTT; C=BE * * Internet: Gerard.Hanney@eurostat.cec.be * ************************************************************

NOTE: 10260 records were read from the infile '/home/com_dpscurrent/workdata/B0045130.DECL.9634.NL.SPG_OR.F66'. NOTE: The data set WORK.L has 10260 observations and 13 variables.

------------------------------

Date: Wed, 4 Mar 1998 11:51:22 -0500 From: "Paul M. Dorfman" <pdorfma@UCS.ATT.COM> Subject: Re: Duh.

Karsten M. Self, in particular, wrote:

> It took me about 18 - 24 months to start feeling proficient in SAS. I've > now been using it daily for about five years, and manage to fool some of > the people on this list all the time, and all of them on occasion. Mom > has no idea what I'm talking about, so the old adage holds true.

It may take even less than that to start feeling proficient (it depends, among other factors, on the demands one imposes on himself), but actually becoming proficient requires tackling a variety of tasks. That's where years of experience may begin to matter...

...

> I would add a sweet little number, "The Little SAS Book", by Susan > Slaughter and Lora Delwiche, published by SAS. While not the most > complete SAS reference, it is a gentle and bite-sized introduction that > contains an amazing amount of substance in a very readable, well organized > format. This is the one book I would recommend to anyone from researcher > to statistician to business analyst to "real programmer", who needs to > become acquainted with SAS.

I'd concur, it is a wonderful book, indeed. For a complete novice, though, I would also recommend the book by Thomas Miron "SAS Software Solutions" available from SI. It embraces the classical pedagogical approach: formulate a problem, present a SAS program solving it, and explain the program line after line digressing only when necessary. Several people I know have admitted that after having done all the book suggested they felt they grasped the essence of SAS enough to be able to successfully expand their SAS knowledge.

...

> Learning other languages and software tools is also helpful. SAS is > powerful in many ways, but it is rooted in tradition and sometimes just > bass ackwards. Seeing other ways of doing things again provides > perspective. What languages? I speak a little SQL, several Unix > scripting tongues, and a smattering of C, BASIC, and Pascal. > > I also feel it's important to have an idea about general programming > principles.

Agreed. With respect to these notions, "SAS Professional Programming Secrets" by Rick Aster and Rhena Seidman may provide gobs of help. First, it explains how SAS works in detail; second, it's the only SAS book I know treating SAS as a general programming language, and the text is structured with this in mind.

...

My $.02, anyway...

Very truly,

+++++++++++++++++++++++++++++++++ Paul M. Dorfman AT&T UCS Decision Support Systems Jacksonville, Fl +++++++++++++++++++++++++++++++++

------------------------------

Date: Thu, 12 Mar 1998 17:34:51 -0800 From: William Kreuter <billyk@U.WASHINGTON.EDU> Subject: Re: SAS and Latex

On Thu, 12 Mar 1998, Chris Latham wrote:

> The macro you are looking for was posted by Paul Thompson. I have > included it in the SNUG Toolbox (SAS NSW User Group). The web site > is currently at > http://www.ozemail.com.au/~chrisnat/snugttt-toolbox.html

I looked at this set of macros. If I'm not mistaken, I think that it translates tabular output to LaTeX.

What would be really handy would be a macro suite which took any possible .lst file and set it up either in Postscript or LaTeX (or, for that matter, any page-description or markup language), with table line-drawing handled correctly and proportional fonts supported with proper lineup of all columns. The existing HTML converter does some of this, but it's rather inadequate. Some weeks ago I posted a method to obtain Postscript output using the beta-test proc jprint, but in practice the appearance of what this produces leaves a bit to be desired.

Direct output to Postscript is supposed to be supported in version 7, but its release date keeps getting pushed back all the time. I don't think that SI is any longer planning to support LaTeX or .dvi output in version 7's Output Display System.

So anybody feel like writing a full suite of .lst-to-LaTeX macros? Or know of an existing one?

Billy

------------------------------

Date: Thu, 12 Mar 1998 23:19:12 GMT From: Melvin Klassen <Klassen@UVIC.CA> Subject: Re: TSO and GDG's (under IBM MVS system)

On Fri, 6 Mar 1998 02:59:56, lpogoda@aol.com (LPogoda) wrote:

> I have an SCL application on TSO. Everything's fine, but some of the nervous > nellies in the office would -like- daily transactions processed by the system > to be written out to a flat file, preferably a GDG. Each day's transactions > would be written to the +1 bias number. Therein lies the problem. > > At this installation, coding a GDG in JCL looks something like this: > //DD DAILY DSN=XXXXXXXX.XXXXXXXX.DAILY.TRANS(+1), > // DISP=(NEW,CATLG,DELETE), > // DCB=(DUMMY,LRECL=80,SPACE(TRK(10,10)),RECFM=FB,BLKSIZE=0) > // UNIT=SYSDA > > In the DCB clause, BLKSIZE=0 tells the OS to assign an "optimum" blocksize, > and DUMMY references the GDG base. The file created will have as the last > qualifier G0001V00, G0002V00, etc. > > Well, that's OK for a batch job, but this particular app doesn't run in batch. > I can code all the parameters I need in a FILENAME statement FILENAME > function *except* the DMMY. No matter where I put it, SAS says this isn't a > valid option for a filename. Without it, the OS tells me it can't find the > base index, and the file isn't created. Anyone have any suggestions?

Just once, run a simple batch job to create the "base index" dataset:

//STEP1 EXEC PGM=IEFBR14 //ANYNAME DD DSN=xxxxxxxx,DISP=(NEW,CATLG),UNIT=SYSDA, // SPACE=(TRK,0),DCB=(RECFM=FB)

This creates a DSCB (Data Set Control Block) entry on the disk's VTOC (Volume Table of Contents). Note that the dataset is allocated "zero" tracks; it's only a "model" DSCB, so this amount of disk-space is 100% adequate.

------------------------------

Date: Thu, 12 Mar 1998 21:04:42 GMT From: First Last <First.Last@ADD.SSW.ABBOTT.COM> Subject: From Unix to PC

This should be an easy question for you.

I have SAS map datasets for Unix (SAS 6.09) and I would like to use them on PC (SAS 6.12). How can I do it?

Thank you. David ddavtian@math.umbc.edu

------------------------------

Date: Fri, 13 Mar 1998 08:45:08 +0000 From: "Karsten M. Self" <kmself@IX.NETCOM.COM> Subject: Re: Codes on email addresses

RTFWP (Read These Fine Web Pages):

http://www.rtw.com.au/internet/suffixes.html http://www.yahoo.com/Computers_and_Internet/Internet/Domain_Registration/Top_Lev el_Internet_Domains/ http://www.isi.edu/in-notes/usdnr/

...which I found at: http://www.yahoo.com/Reference/Standards/ISO_Country_Codes/

Steve Bousquin wrote: > > I give up on finding a suitable place to post this question, so I'll > just ask some statisticians, who of course know everything. The > question is where I can find a directory that explains the codes used in > email addresses, especially the 2-letter code at the end of addresses > that are overseas, which appear to be codes for countries. > > Steve Bousquin

-- Karsten M. Self (kmself@ix.netcom.com)

Use address above, or edit spam trap from reply address,when responding.

What part of "gestalt" don't you understand?

------------------------------

Date: Fri, 13 Mar 1998 08:35:39 +0000 From: "Karsten M. Self" <kmself@IX.NETCOM.COM> Subject: Re: Subsetting very large sasdataset,

Morgens:

Index the dataset. Your system load to create a single, simple index on a dataset of the number of observations you mention is minimal, equal or less than the load of a single query against the unsorted dataset, and should be more than paid back by improved response of subsetting queries against it.

Rule of thumb is that an index will add about 10% to the storage requirements of the data. Utilizing an index for small (< 10 - 20% of the data) lookups or extracts will result in drastically improved performance, as SAS is able to perform a binary rather than sequential search for key values. With larger subsets, this benefit is offset by inefficiencies of having to traverse both an index and the primary data table multiple times.

No other method, short of logically subsetting your dataset into smaller files, will offer near the same optimization of an index, as they will rely on sequentially traversing the data or some subset of it.

Even multiple or complex indicies may be indicated if multiple criteria are used in accessing the data. Keep in mind that SAS typically will utilize only one of multiple indexes in satisfying a specific query.

You will also have to rebuild the index after DATA step (or PROC APPEND) manipulations on the table, or add new records via SQL INSERT INTO statements, which will (I think) update the index as a part of normal operations.

The alternative is to split your large table into smaller subsets, by some logical ordering. These subsets may have to be indexed in turn, as it appears that your primary key is not related to your data accretion process (data are being added out-of-sequence to your existing table, from your comments.). You may need to do this soon anyway, for logistical reasons, given the size of the dataset.

You can monitor methods used to access the table by setting the SAS sytem option MSGLEVEL=INFO and the (undocumented) _METHOD SQL option:

proc sql _method; /* query */ ;

...INFO will return information on index usage in DATA step and PROC processing. _METHOD returns a coded schema describing how SQL fulfills your query request. _METHOD is documented in a SUGI paper by Paul Kent, of SI, available at http://www.sas.com/techsup/download/technote/ts553.txt. This paper also discusses methods of SAS SQL query optimization. Another related paper by Paul is also available from the same technotes page.

MSL wrote: > > I am currently working on SAS-program which is subsetting a very large > sasdataset, at the moment the dataset contains more than 22 mill. records. > The problem is that the dataset is not indexed or sortet, the keyvalue is > scattered all over the dataset and the numbers of observations increases > rapidly day by day. > To ad an index is not relevant while the total load of the main computer > during the night is already heavy. SO if anybody out there has been in a > likewise situation and has any good suggestion about adding SPEED to ONLINE > requests for small subsets (approximately 100 obs), I'll be glad to hear > from you. > Please replay to this address > > msl@dmt.sonofon.dk > > Mogens Larsen. > Systemdeveloper > Sonofon > Denmark.

-- Karsten M. Self (kmself@ix.netcom.com)

Use address above, or edit spam trap from reply address,when responding.

What part of "gestalt" don't you understand?

------------------------------

Date: Fri, 13 Mar 1998 08:18:13 +0000 From: "Karsten M. Self" <kmself@IX.NETCOM.COM> Subject: Re: Anybody doing Version Control?

Deanna:

I have been using and/or introduced the use of RCS and/or CVS at several assignments, and have found good success. This is far and away superior to managing multiple copies of programs scattered among users' directories, mixed with data, or an freestanding machines across the network. You also gain a development history (often worth more than inline comments) and the ability to extract any given revision of code.

Both these tools are freely available (CVS is a front-end to RCS), and either should suite the needs of a typical SAS shop. They are native to Unix, but have been ported to most major operating systems (including Window 3.x/95/NT, DOS, VMS, and others). A key advantage of RCS archives is that the same file format is used on all platforms, making multi-platform support much easier. Both are command-line based, though graphical front ends can and have been built.

RCS is simpler, consisting primarially of commands to create archives, check in, check out, and compare differences between files. CVS introduces concepts to support team-oriented configuration management, and was originally developed to support work on the Sun Unix source code at distributed sites.

An interesting also-ran is TCCS, freely available but heavily beta application. It includes some neat tools, including tkdiff, a visual front-end to the Unix diff utility with support for RCS archives. There are also a number of commercially available packages, based variously on open and proprietary data formats. I would tend to avoid closed systems. SCCS is another commonly available source control system, which may be more readily available (it is part of the POSIX standard and is bundled with several Unix distributions) but is more cumbersome and less capable than RCS.

For implementation, I'd recommend a person (preferably non-developer -- perhaps QA?) be the point designee for authorizing and/or identifying releases. I would *not* restrict the ability of developers to check out and check in revisions -- that's the whole point of SW configuration management (SCM). You'll shoot yourself in the foot and kill the whole concept if you put any barriers between your coders and actually working on the code.

What you want to do is put someone between implementation and release who can keep his or her hands off of things (programmers had this trait bred out of them a looong time ago). If your coders keep hacking at stuff, the SCM system will allow you to back out to the last known good revision. Most advanced systems allow concepts of branching and/or "obsoleting" a series of revisions, which you would probably want restricted to an administrator.

Good sources of additional information:

Don Bolinger & Tan Bronson, "Applying RCS and SCCS", O'Reilly & Associates, (c) 1995, ISBN: 1-56592-117-8 http://www.ora.com

Timi Mikkelsen & Suzanne Pherigo, "Practical Software Configuration Management", Prentice Hall/Hewlett Packard, (c) 1997. ISBN: 0-13-240854-6 http://www.prenhall.com Includes CD-ROM software for Unix, DOS, and Win 3.x/95/NT.

...avoid the books writen by the big-systems ISO standards organizations. You'll end up with a wonderful set of checklists....and have your source code all over the map.

Good luck.

Deanna Castorena wrote: > > Our group is in the process of defining departmental procedures and > we're interested in developing some sort of revision control process for > batch programs and web-related programs for all of our SAS programs. > With ISO and CMM becoming a bigger part of everyone's internal > procedures, I'm sure there are a few of you who have already experienced > the pain. Is there anybody out there who would be willing to share > their experience with me on version control of programs? I would be > interested in tools, processes, procedures, or insight you would like to > pass on. > > Thanks, > Deanna Castorena

-- Karsten M. Self (kmself@ix.netcom.com)

Use address above, or edit spam trap from reply address,when responding.

What part of "gestalt" don't you understand?

------------------------------

Date: Thu, 12 Mar 1998 23:01:20 -0700 From: Jim Linck <jim.linck@ASU.EDU> Subject: Splitting a variable into two variables based on a character somewhere in the field

Seems like the pointer, input and substring commands may be able to be used together to handle this task; however, I'm not sure how to do it.

I have a Name which I read in originally as part of an overall .csv file. The name is in the format last, first. What I want to do is create two variables from the Name variable, last and first where last contains all info before the command and first contains all info after the comma. Anybody know how to do that?

Thanks.

------------------------------

Date: Thu, 12 Mar 1998 20:03:05 -0800 From: Sloan <faith@FRSA.COM> Subject: Re: Codes on email addresses

At 06:21 PM 3/12/98 -0700, Steve Bousquin wrote: >I give up on finding a suitable place to post this question, so I'll >just ask some statisticians, who of course know everything. The >question is where I can find a directory that explains the codes used in >email addresses, especially the 2-letter code at the end of addresses >that are overseas, which appear to be codes for countries. > >Steve Bousquin >

I ain't no statistician but check out http://www.domainit.com/country-domains.htm for a list of country domains. Don't have a web address for the other domains but here they are from memory:

.edu educational institutions .com commercial entities .net commercial entities supposedly specifically network types only .org typically non-profit organizations .mil military entities

There may be others but my long-term memory ain't what it used to be since i strayed from my statistical background. ;-)

best...

-- FRS ASSOCIATES,LLC - Your Corporate Intranet Experts! Linking Strategy with Technology to Give You The Edge on Your Competition... SAS Software and Internet Training Netscape DevEdge Gold Member | Allaire Alliance Partner Oracle Developers Programme Member | SAS Quality Partner Microsoft Developers Network Member faith@frsa.com http://www.frsa.com/ 415 626-9796 http://www.frsa.com/bbpage.shtml (Bodybuilding for the Masses!!)

------------------------------

Date: Fri, 13 Mar 1998 09:22:36 -0500 From: "Zuckier, Gerald" <Zuckier@CHIME.ORG> Subject: Re: I like your site

Hey, the price is right.

> ---------- > From: coolio@UNKNOWN.COM[SMTP:coolio@UNKNOWN.COM] > Sent: Thursday, March 12, 1998 2:40 AM > To: SAS-L@UGA.CC.UGA.EDU > Subject: Re: I like your site > > Hello, > > I have a document that can place you in the top 10 > listings of the search engines. This document will show you the tricks > of > the trade . How would like to have more traffic to your web site? Well > here > is the answer to that question. > > Simply fill out the form below and mail it in to me along with > .00 US CASH and I will e-mail the files to you. > > As once as I receive your payment I will e-mail you the files and then > you > are free to do what you want with the files. There are over 30 pages > of > text that will show you what tricks that the others on the Internet > are > using to get sales. I hope to hear from you soon. > > Have a nice day > > ----------------------------------------------------------------- > > Please fill out this form completely and mail it to the following > address. > Please write in L A R G E B L O C K L E T T E R S. I can't fill > your > order if I can't read it. > > Scamper Technologies > 400 Alexandre St #1. > Sherbrooke Quebec Canada > J1H 4T3 > > Name ____________________________________________ > > Address ____________________________________________________ > > ____________________________________________________ > > ____________________________________________________ > > Phone Number _____________________________ > > Work Number _____________________________ > > E-mail Address __________________ @ ________________________ > > Web Page URL http://___________________________________________ > > ----------------------------------------------------------------- >

------------------------------

Date: Fri, 13 Mar 1998 09:42:53 -0500 From: Leigh Cassara <lcassara@MAXIMGROUP.COM> Subject: Delaware SAS Opportunity

The Maxim Group is in search of an entry level SAS programmer for an opportunity in Wilmington, Delaware. This is for a Fortune 500 client who would optimally need the programmer to start next week. This would be a great opportunity for an entry level SAS programmer to "get their foot in door". The qualifications for this position are 1-2 years of SAS programming experience.(Pulling reports, working with spread sheets - Unix is a plus and you will receive the opportunity to learn Oracle) If you know of anyone that would be suitable for this kind of opportunity please do not hesitate to have them give me a call.

Leigh Cassara 888-448-8812 ext.9135 610-238-9135 Maxim Group. www.maximgroup.com

------------------------------

Date: Fri, 13 Mar 1998 09:30:58 -0500 From: "Hampton, Jonathan" <JHampton@ALLDATA.NET> Subject: Re: I like your site

You can't argue with that price.

---------- From: coolio@UNKNOWN.COM[SMTP:coolio@UNKNOWN.COM] Sent: Thursday, March 12, 1998 2:41 AM To: SAS-L@UGA.CC.UGA.EDU Subject: Re: I like your site

Hello,

I have a document that can place you in the top 10 listings of the search engines. This document will show you the tricks of the trade . How would like to have more traffic to your web site? Well here is the answer to that question.

Simply fill out the form below and mail it in to me along with .00 US CASH and I will e-mail the files to you.

As once as I receive your payment I will e-mail you the files and then you are free to do what you want with the files. There are over 30 pages of text that will show you what tricks that the others on the Internet are using to get sales. I hope to hear from you soon.

Have a nice day

-----------------------------------------------------------------

Please fill out this form completely and mail it to the following address. Please write in L A R G E B L O C K L E T T E R S. I can't fill your order if I can't read it.

Scamper Technologies 400 Alexandre St #1. Sherbrooke Quebec Canada J1H 4T3

Name ____________________________________________

Address ____________________________________________________

____________________________________________________

____________________________________________________

Phone Number _____________________________

Work Number _____________________________

E-mail Address __________________ @ ________________________

Web Page URL http://___________________________________________

-----------------------------------------------------------------

------------------------------

Date: Fri, 13 Mar 1998 09:50:33 -0500 From: RHODESD1 <RHODESD1@WESTAT.COM> Subject: email codes

Steve asked about the two digit country codes. Far from official, check out this site

http://www.soasoas.com/stats/0497.html

It is the "unofficial" parrothead page that lists the access of Jimmy Buffett fans by their two digit country codes. (That's Son Of a Son Of a Sailor).

Dianne Rhodes in Rockville, MD where it is cold enough for boat drinks!

------------------------------

Date: Fri, 13 Mar 1998 10:01:13 -0500 From: Schechter Robert RS <robert.schecter@PHWILM.ZENECA.COM> Subject: FW: Codes on email addresses

>---------- >From: Schechter Robert RS >Sent: Friday, March 13, 1998 8:54 AM >To: 'Steve Bousquin' >Subject: RE: Codes on email addresses > > Steve asked about the two digit country codes. > >Found at Big Dummy's Guide to the Internet - Internet Country Codes: >(use that phrase on any search engine for more information). > >ISO 3166 Codes & Top level domains > > >Code Country Conn Notes main nameserver > >AD Andorra >AE United Arab Emirates * ns.uu.net >AF Afghanistan >AG Antigua and Barbuda * upr1.upr.clu.edu >AI Anguilla >AL Albania P gwd2i.cnuce.cnr.it >AM Armenia Ex-USSR >AN Netherland Antilles >AO Angola >AQ Antarctica FI * luxor.cc.waikato.ac.nz >AR Argentina FI B * ns.uu.net >AS American Samoa >AT Austria FI B * >pythia.edvz.univie.ac.at >AU Australia FI * munnari.oz.au >AW Aruba >AZ Azerbaidjan Ex-USSR >BA Bosnia-Herzegovina Ex-Yugoslavia >BB Barbados * upr1.upr.clu.edu >BD Bangladesh >BE Belgium FI B * ub4b.buug.be >BF Burkina Faso * orstom.orstom.fr >BG Bulgaria FI B * pythia.ics.forth.gr >BH Bahrain B * Gulfnet >BI Burundi >BJ Benin >BM Bermuda * ns.uu.net >BN Brunei Darussalam >BO Bolivia * ns.uu.net >BR Brazil FI B * fpsp.fapesp.br >BS Bahamas * upr1.upr.clu.edu >BT Buthan >BV Bouvet Island >BW Botswana * hippo.ru.ac.za >BY Belarus * Ex-USSR >BZ Belize P upr1.upr.clu.edu >CA Canada FI B * relay.cdnnet.ca >CC Cocos (Keeling) Isl. >CF Central African Rep. >CG Congo >CH Switzerland FI B * scsnms.switch.ch >CI Ivory Coast >CK Cook Islands >CL Chile FI B * dcc.uchile.cl >CM Cameroon FI * in .fr domain inria.inria.fr >CN China PFI * iraun1.ira.uka.de >CO Colombia B * cunixd.cc.columbia.edu >CR Costa Rica FI B * ns.cr >CS Czechoslovakia FI B * still works... ns.cesnet.cz >CU Cuba * igc.org >CV Cape Verde >CX Christmas Island >CY Cyprus B * pythia.ics.forth.gr >CZ Czech Republic FI * ns.cesnet.cz >DE Germany FI B * >deins.informatik.uni-dortmund.de >DJ Djibouti >DK Denmark FI B * ns.dknet.dk >DM Dominica P upr1.upr.clu.edu >DO Dominican Republic P upr1.upr.clu.edu >DZ Algeria * >EC Ecuador FI B * ecua.net.ec >EE Estonia FI * Ex-USSR uvax2.kbfi.ee >EG Egypt PFI B * frcu.eun.eg >EH Western Sahara >ES Spain FI B * sun.rediris.es >ET Ethiopia >FI Finland FI B * funet.fi >FJ Fiji * truth.waikato.ac.nz >FK Falkland Isl.(Malvinas) >FM Micronesia >FO Faroe Islands P danpost.uni-c.dk >FR France FI B * inria.inria.fr >FX France (European Ter.) ??? >GA Gabon >GB Great Britain (UK) FI * X.400 & IP ns1.cs.ucl.ac.uk >GD Grenada P upr1.upr.clu.edu >GE Georgia * Ex-USSR ns.eu.net >GH Ghana >GI Gibraltar >GL Greenland >GP Guadeloupe (Fr.) >GQ Equatorial Guinea >GF Guyana (Fr.) >GM Gambia >GN Guinea >GR Greece FI B * pythia.ics.forth.gr >GT Guatemala * ns.uu.net >GU Guam (US) >GW Guinea Bissau >GY Guyana >HK Hong Kong FI B * hp9000.csc.cuhk.hk >HM Heard & McDonald Isl. >HN Honduras * ns.uu.net >HR Croatia FI * Ex-Yugo dns.srce.hr >HT Haiti >HU Hungary FI B * sztaki.hu >ID Indonesia * ns.uu.net >IE Ireland FI B * nova.ucd.ie >IL Israel FI B * relay.huji.ac.il >IN India FI B * sangam.ncst.ernet.in >IO British Indian O. Terr. >IQ Iraq >IR Iran B * >IS Iceland FI B * isgate.is >IT Italy FI B * dns.nis.garr.it >JM Jamaica * upr1.upr.clu.edu >JO Jordan >JP Japan FI B * jp-gate.wide.ad.jp >KE Kenya * rain.psg.com >KG Kirgistan Ex-USSR >KH Cambodia >KI Kiribati >KM Comoros >KN St.Kitts Nevis Anguilla P upr1.upr.clu.edu >KP Korea (North) P >KR Korea (South) FI B * ns.kaist.ac.kr >KW Kuwait FI * No BITNET dns.kuniv.edu.kw >KY Cayman Islands >KZ Kazachstan * Ex-USSR in .su domain >LA Laos >LB Lebanon P >LC Saint Lucia P upr1.upr.clu.edu >LI Liechtenstein PFI * scsnms.switch.ch >LK Sri Lanka * ns.eu.net >LR Liberia >LS Lesotho * hippo.ru.ac.za >LT Lithuania PFI * Ex-USSR aun.uninett.no >LU Luxembourg FI B * menvax.restena.lu >LV Latvia FI * Ex-USSR lapsene.mii.lu.lv >LY Libya >MA Morocco P >MC Monaco >MD Moldavia Ex-USSR >MG Madagascar >MH Marshall Islands >ML Mali >MM Myanmar >MN Mongolia >MO Macau * hkuxb.hku.hk >MP Northern Mariana Isl. >MQ Martinique (Fr.) >MR Mauritania >MS Montserrat >MT Malta P ns.iunet.it >MU Mauritius >MV Maldives >MW Malawi >MX Mexico FI B * mtecv1.mty.itesm.mx >MY Malaysia FI B * mimos.my >MZ Mozambique * hippo.ru.ac.za >NA Namibia * rain.psg.com >NC New Caledonia (Fr.) >NE Niger * in .fr domain inria.inria.fr >NF Norfolk Island >NG Nigeria >NI Nicaragua * ns.uu.net >NL Netherlands FI B * sering.cwi.nl >NO Norway FI B * nac.no >NP Nepal >NR Nauru >NT Neutral Zone >NU Niue >NZ New Zealand FI * truth.waikato.ac.nz >OM Oman >PA Panama B * >PE Peru B * rain.psg.com >PF Polynesia (Fr.) >PG Papua New Guinea * munnari.oz.au >PH Philippines * ns.uu.net >PK Pakistan * ns.uu.net >PL Poland FI B * danpost.uni-c.dk >PM St. Pierre & Miquelon >PN Pitcairn >PT Portugal FI B * ns.dns.pt >PR Puerto Rico (US) FI B * sun386-gauss.pr >PW Palau >PY Paraguay * ns.uu.net >QA Qatar >RE Reunion (Fr.) FI * In .fr domain inria.inria.fr >RO Romania FI B * roearn.ici.ac.ro >RU Russian Federation P Ex-USSR >RW Rwanda >SA Saudi Arabia B * GulfNet >SB Solomon Islands >SC Seychelles >SD Sudan >SE Sweden FI B * sunic.sunet.se >SG Singapore FI B * solomon.technet.sg >SH St. Helena >SI Slovenia FI * Ex-Yugos via .yu klepec.yunac.yu >SJ Svalbard & Jan Mayen Is >SK Slovak Republic FI * ns.eunet.sk >SL Sierra Leone >SM San Marino >SN Senegal * rain.psg.com >SO Somalia >SR Suriname P upr1.upr.clu.edu >ST St. Tome and Principe >SU Soviet Union FI B * Still used. ns.eu.net >SV El Salvador >SY Syria >SZ Swaziland >TC Turks & Caicos Islands >TD Chad >TF French Southern Terr. >TG Togo >TH Thailand FI * chulkn.chula.ac.th >TJ Tadjikistan Ex-USSR >TK Tokelau >TM Turkmenistan * Ex-USSR in .su domain >TN Tunisia FI B * alyssa.rsinet.tn >TO Tonga >TP East Timor >TR Turkey FI B * knidos.cc.metu.edu.tr >TT Trinidad & Tobago P upr1.upr.clu.edu >TV Tuvalu >TW Taiwan FI B * moevax.edu.tw >TZ Tanzania >UA Ukraine FI * Ex-USSR via .su ns.eu.net >UG Uganda >UK United Kingdom FI B * ISO 3166 is GB ns1.cs.ucl.ac.uk >UM US Minor outlying Isl. >US United States FI * see note (4) venera.isi.edu >UY Uruguay B * ns.uu.net >UZ Uzbekistan Ex-USSR >VA Vatican City State >VC St.Vincent & Grenadines P upr1.upr.clu.edu >VE Venezuela FI * nisc.jvnc.net >VG Virgin Islands (British) >VI Virgin Islands (US) * >VN Vietnam * >VU Vanuatu >WF Wallis & Futuna Islands >WS Samoa >YE Yemen >YU Yugoslavia FI B * Bitnet is cut klepec.yunac.yu >ZA South Africa FI * rain.psg.com >ZM Zambia >ZR Zaire >ZW Zimbabwe * rain.psg.com > > > >See section Main nameservers for the next top level domains >(rs.internic.net): > > > > >ARPA Old style Arpanet * alias still works ns.nic.ddn.mil >COM Commercial FI * ns.internic.net >EDU Educational FI B * ns.internic.net >GOV Government FI * ns.internic.net >INT International field FI * used by Nato ns1.cs.ucl.ac.uk >MIL US Military FI * ns.nic.ddn.mil >NATO Nato field * soon to be deleted >NET Network FI * ns.internic.net >ORG Non-Profit OrganizationFI * ns.internic.net > >---------- >From: Steve Bousquin[SMTP:sbous@LAMAR.COLOSTATE.EDU] >Sent: Thursday, March 12, 1998 8:21 PM >To: SAS-L@VTVM1.zen.com >Subject: Codes on email addresses > >I give up on finding a suitable place to post this question, so I'll >just ask some statisticians, who of course know everything. The >question is where I can find a directory that explains the codes used in >email addresses, especially the 2-letter code at the end of addresses >that are overseas, which appear to be codes for countries. > >Steve Bousquin > >

------------------------------

Date: Fri, 13 Mar 1998 10:03:14 -0500 From: "Mark D. H. Miller" <mdmiller@SYR.EDU> Subject: Re: Splitting a variable into two variables based on a character somewhere in the field

Jim Linck wrote: > > Seems like the pointer, input and substring commands may be able to be used > together to handle this task; however, I'm not sure how to do it. > > I have a Name which I read in originally as part of an overall .csv file. > The name is in the format last, first. What I want to do is create two > variables from the Name variable, last and first where last contains all > info before the command and first contains all info after the comma. > Anybody know how to do that? > > Thanks.

Use the SCAN function. which separates a character expression into words and returns the Nth word SCAN( argument, n <,delimiters> ) where argument is a valid SAS character expression, n is a valid SAS numeric expression, and delimiter is the character(s) you wish to use to delimit words.

If delimiter is omitted, the following are treated as delimiters (on ASCII systems) blank . < + | & ! $ * ) ; ^ / , % > \

Since you are parsing a name which could have embedded periods, to explicitly follow the rule you describe would require

username= 'lastname, firstname' ; *sample data;

lname = scan(username,1,','); fname = scan(username,2,',');

-- *-------------------------------------------------------------* Mark D. H. Miller <mdmiller@syr.edu> Faculty Computing and Media Services Tel: 315.443-2143 272 Newhouse Communications Center II Fax: 315.443-5658 Syracuse University Syracuse, NY 13244-2110 *-------------------------------------------------------------*

------------------------------

Date: Fri, 13 Mar 1998 07:26:46 -0800 From: Jason Jones <jasonj@RCF.USC.EDU> Subject: Re: Subsetting very large sasdataset (Related)

On a note related to large datasets, indexing, and SAS having to traverse the index and data files... I read an article that suggested storing index and data files on separate physical drives for speed purposes. Has anyone ever tried to do this and were the results promising with SAS? As far as I can tell, SAS always creates the index in the same directory as the data file, which would make it impossible to store the index and data files on separate disks.

Jason

Jason Jones J2DbStat Data Management & Analysis 213.508.5347

------------------------------

Date: Fri, 13 Mar 1998 09:20:26 -0800 From: Robert Mengis <rmengis@BCO.COM> Subject: Re: MVS & Missing Files

Mike,

What OS are you running? OS390, MVS/ESA or what? FILEEXIST does not work on our OS390 machine either. I had to go to "DSNEXST". I called SAS about it and they said for V6.09 FILEEXIST does indeed not work, and that "DSNEXST" is not supported...well BFD...DSNEXST works, do a archive search on DSNEXST.... cheers

---------- > From: Michael Stuart <mstuart@PRUDENTIAL.COM> > To: SAS-L@UGA.CC.UGA.EDU > Subject: Re: MVS & Missing Files > Date: Thursday, March 12, 1998 2:00 PM > > Thanks (Tim Berryhill and Ray Pass and Bernard Tremblay) for getting me > started. I uncovered information on FILEEXIST to check if a file is out > there, and started putting together a solution. Unfortunately ... every > time I FILEEXIST a file that doesn't exist -- I get a system error -- kind > of irksome if you consider the purpose of the function. The specific error > I get is: "FATAL: Undetermined execution error detected in the execution > of the data step program. Aborted during the EXECUTION phase." > > I've tried various approaches to basically the same concept and it happens > everytime time, when a non-existent file is FILEEXIST'd. It only happens > in batch mode however, I've run some tests in interactive (using the same > file names, etc.), and I get no errors. The code below runs cleanly if > there are no missing files. > > I've opened a ticket at SAS, but they didn't sound too enthusiastic about > finding a quick reason/solution for the problem. In the meantime, has > anyone else encountered this? > > Any rate ... the solution that I was trying for was to use FILEEXIST to > verify a file was out there, and if it was, load the full name of the > dataset to a SAS file. After checking for all the files I want, use PROC > SQL to create a comma/quote delimited macro variable of all the file names > that do exist, and passing that to a FILENAME statement. Unfortunately, > it's not getting past the first step ... > > > //OTCIP04 JOB (B,X,41RHMS),'IIG,STU',MSGCLASS=V,NOTIFY=&SYSUID,PRTY=09 > > //M1 OUTPUT DEST=PSHR1.&SYSUID > > //*------------------------------------------------------------------ > > //SCRATCH EXEC PGM=IEXUNCAT > > //SYSIN DD SUBSYS=(CCSS, > > // ' BX41RH.X041979.OTCIP04.SASLIB ') > > //*------------------------------------------------------------------ > > //SAS EXEC SAS > > //SASLIST DD SYSOUT=*,OUTPUT=*.M1 > > //SASLOG DD SYSOUT=*,OUTPUT=*.M1 > > //MPRINT DD SYSOUT=* > > //NLIB DD DSN=BX41RH.X041979.OTCIP04.SASLIB, > > // UNIT=DASD,LABEL=RETPD=60,DISP=(,CATLG), > > // DCB=(RECFM=FS,LRECL=28160,BLKSIZE=28160,DSORG=PS), > > // SPACE=(28160,(5000,2500),RLSE) > > //SYSIN DD * > > > > OPTIONS ERRORS=1 MERROR SYMBOLGEN SERROR MLOGIC MPRINT RESERVEDB1 ; > > > > %MACRO LOADOTC(CYCLE) ; > > > > DATA FLIST ; > > > > %MACRO CHEKSTRM(STREAM) ; > > > > IF FILEEXIST("BX41RH.OTCIP04.&STREAM..&CYCLE") THEN DO ; > > FILE = "BX41RH.OTCIP04.&STREAM..&CYCLE" ; > OUTPUT ; > END ; > > > %MEND ; > > > > %CHEKSTRM(CAMO) ; > > %CHEKSTRM(MMO) ; > > %CHEKSTRM(NEMO) ; > > %CHEKSTRM(PPFS) ; > > %CHEKSTRM(SCMO) ; > > %CHEKSTRM(WMO) ; > > > > PROC SQL ; > > > > SELECT QUOTE(FILE) INTO :FLIST SEPARATED BY ',' FROM FLIST ; > > > > %PUT _USER_ ; > > > > FILENAME OTCIP (&FLIST) ; > > > > DATA OTCIP ; > > LENGTH DSCB $200 STREAM $4 CYCLE $6 ; > > INFILE OTCIP DSCB=DSCB UNBUFFERED ; > > INPUT @145 DOPOL $CHAR1. > > @146 ROPOL $CHAR1. > > @147 PCKPOL PD4. > > @151 SFRMYR PD3. > > @154 SFRMMO PD2. > > @156 SFRMDY PD2. > > @158 STOYR PD3. > > @161 STOMO PD2. > > @163 STODY PD2. > > @171 POLYR PD3. > > @174 POLMO PD2. > > @176 POLDY PD2. > > @3685 TABFUND PD6.2 > > @3691 DIFFUND PD6.2 > > @3697 ACMPREMD PD6.2 > > @3703 ACMPREMR PD6.2 > > @3709 PREMACCT PD6.2 > > @3786 RORLYR PD3.4 > > @3789 RORCDUR PD3.4 ; > > > > POLICY = DOPOL || ROPOL || INPUT(PUT(PCKPOL,Z7.),$CHAR7.) ; > > STFROMDT = MDY(SFRMMO,SFRMDY,SFRMYR) ; > > STTODT = MDY(STOMO,STODY,STOYR) ; > > POLDT = MDY(POLMO,POLDY,POLYR) ; > > > > TEMP = TRANSLATE(SUBSTR(DSCB,INDEX(DSCB,'OTCIP04')+8,11),' ',',') ; > > PTPOS = INDEX(TEMP,'.') ; > > > > STREAM = SUBSTR(TEMP,1,PTPOS-1) ; > > CYCLE = SUBSTR(TEMP,PTPOS+1,6) ; > > > > DROP DOPOL ROPOL PCKPOL SFRMMO SFRMDY SFRMYR STOMO STODY STOYR > > POLMO POLDY POLYR TEMP PTPOS ; > > > > FORMAT STFROMDT STTODT POLDT MMDDYY10. ; > > > > PROC APPEND DATA=WORK.OTCIP BASE=NLIB.OTCIP FORCE ; > > > > PROC DATASETS LIBRARY=WORK ; > > DELETE OTCIP ; > > > > FILENAME OTCIP CLEAR ; > > > > %MEND ; > > > > %LOADOTC(D9809C) ; > > %LOADOTC(D9809D) ; > > %LOADOTC(D9809E) ; > > %LOADOTC(D9807B) ; > > > > > > TWB2%Rates%FAR@bangate.pge.com on 03/12/98 01:08:29 PM > Thursday March 12, 1998 10:08 AM > > Please respond to TWB2%Rates%FAR@bangate.pge.com > To: mstuart@prudential.com > SAS-L@UGA.CC.UGA.EDU > cc: (bcc: Michael Stuart/M&P/Prudential) > Subject: re:MVS & Missing Files > > > > > > Michael, We face a similar problem here. Our solution uses PROC IDCAMS, > but > just for flash--it should have been a two step job instead. Anyway, the > outline > is to run a first (non-SAS) step which lists catalog entries matching your > pattern to a flat file, then run a SAS step which parses the file to locate > available entries. If you also maintain a history of previously processed > entries you can exclude anything in history from current processing. Our > solution accepts a list of new files to ignore and a list of old files to > reprocess. Once you have the list of files to process you can either read > them > in using the FILEVAR option of the INFILE statement or use CALL EXECUTE to > write > FILENAME statements. > Tim Berryhill - Contract Programmer and General Wizard > TWB2@PGE.COM or http://www.aartwolf.com/twb.html > Frequently at Pacific Gas & Electric Co., San Francisco > The correlation coefficient between their views and > my postings is slightly less than 0 > ----------------------[Reply - Original Message]---------------------- > Sent by:"Michael Stuart" <mstuart@PRUDENTIAL.COM> > Greetings. I'm developing a production process on MVS (SAS v6.09 TS450) > to > read data from daily regional files, and load to a SAS dataset for analysis > and reporting. One of the problems that I'm running into is that > occasionally a file from one of the six regions may not be created.<SNIP> > I'm also interested in hearing comments on how I can prevent a particular > cycle from being loaded twice.<SNIP>

------------------------------

Date: Fri, 13 Mar 1998 12:16:14 -0500 From: Victor Kamensky <kamensky@AECOM.YU.EDU> Subject: Re: Suppressing printing of carriage control

The simpliest way to get rid of carriage control is not to use proc printto. Instead save output window using file command, and the file will not have carriage control. But if you want to delete carriage control from the first columns of a file, you can do the following: data _null_; infile "printto.out" missover ; input c $ char1.; file "new.out"; put _infile_ @; if c=byte(12) then put @1 ' '; else put; run; Sincerely Victor Kamensky Programmer Albert Einstein College of Medicine

At 06:09 PM 3/12/98 GMT, you wrote: >How do I suppress printing the carriage control on PC of a text file >created by SAS proc printto? Thanks for any clues. > >

------------------------------

Date: Fri, 13 Mar 1998 17:52:07 +0000 From: "Karsten M. Self" <kmself@IX.NETCOM.COM> Subject: Re: Subsetting very large sasdataset (Related)

Under some operating systems (in particular Unix), it is possible to spcify concatenated libnames which include several directories, which may be on multiple filesystems and/or physical disks. SAS defaults to writing to, and searching from, the first path found in the libname, though data may be placed on subsequent paths to be accessed through the libnmae.

Similar results can be obtained through effective use of striping technologies, in which the the contents of a single filesystem are spread across several physical disks, the advantage here being that access optimization and load balancing are dealt with by the disk I/O interface rather than by direct intervention at the application level.

The ultimate in index/data response would be to include a ramdisk in the search path and place the index on the ramdisk partition -- essentially loading it in memory. This technique, along with the use of SAS formats for value lookup, is used extensively in very large database and data warehouse applications, where sever memory may be measured in gigabytes.

To utilize the concatenated libname approach and locate the index on a non-primary partition, it would be necessary to manually move the index to an alternate location with operating system interfaces (eg: Unix "cp foo.ssnx001 /otherpath" would work, PROC COPY would not, as SAS treats a dataset and its index as one logical unit).

Incidentally, the suggestion made by several other respondants to the initial post, of building and sorting a key values lookup table, is essentially what indexing does. This goes against a common rule of thumb I have of not rolling your own when an off-the-shelf method is available.

Utilizing SAS indexes availails you to a debugged, integrated, and optimized method. Building your own key-value lookup system introduces additional layers of complexity and maintenance, and introduces more opportunities for things to go wrong. I am not saying the technique is never justified or that the results could not improve on what SAS has built in. I am saying that your odds of improving on the available methods, and not breaking your application under the weight of complexity, are slim.

A SAS index is a key value lookup which allows direct access to its host data. The keys may be hashed or optimized by other methods, reducing storage (and index access I/O time). Binary traversing of the index is built in. Index utilization by data access methods (data step/proc BY statement, SQL) is built in. Maintenance of the index is integrated into available dataset access and update mechanisms (data step, data set options, SQL). These are powerful advantages and should not be disregarded lightly.

Jason Jones wrote: > > On a note related to large datasets, indexing, and SAS having to traverse > the index and data files... > I read an article that suggested storing index and data files on separate > physical drives for speed purposes. Has anyone ever tried to do this and > were the results promising with SAS? As far as I can tell, SAS always > creates the index in the same directory as the data file, which would make > it impossible to store the index and data files on separate disks. > > Jason > > Jason Jones > J2DbStat > Data Management & Analysis > 213.508.5347

-- Karsten M. Self (kmself@ix.netcom.com)

Use address above, or edit spam trap from reply address,when responding.

What part of "gestalt" don't you understand?

------------------------------

Date: Fri, 13 Mar 1998 12:00:51 GMT From: LBuchanan7 <lbuchanan7@AOL.COM> Subject: Capturing return codes from a device

I need to write program that sends set up codes and data to a card embosser either directly through the printer port or through a print driver (not sure which yet). I plan to use a data _null_ step with put statements and the PRINTER option on the filename statement to point to the device. We will be using SAS 6.12 and Win95.

My problem is that I need to control the flow of the data based on return codes from the embosser. The machine can only accept one record at a time so I need to know when the machine is ready for the next card by querying it and capturing the return codes. Any suggestions on how I can do this with SAS?

Thanks, Laurie Buchanan LBuchanan7@aol.com

------------------------------

Date: Thu, 12 Mar 1998 00:28:59 GMT From: Reiling Lee <Reiling.Lee@ALZA.COM> Subject: X command & EXIT

When I submit an X command on PC, a MS-DOS window session is open and stays open until I issue an EXIT command. Is there any way to bypass the EXIT command and come back to SAS session? I have tried "x dir; x exit;" and it doesn't work. Thanks in advance for any information.

------------------------------

Date: Fri, 13 Mar 1998 12:36:12 -0800 From: "TERJESON, Mark" <TERJEMW@DSHS.WA.GOV> Subject: Re: X command & EXIT

Try the noxwait option.

options noxwait; x dir;

HTH,

Mark Terjeson Office of Forecasting and Policy Analysis DSHS Headquarters State of Washington terjemw@dshs.wa.gov

> ---------- > From: Reiling Lee[SMTP:Reiling.Lee@ALZA.COM] > Reply To: Reiling Lee > Sent: Wednesday, March 11, 1998 4:28 PM > To: SAS-L@UGA.CC.UGA.EDU > Subject: X command & EXIT > > When I submit an X command on PC, a MS-DOS window session is open and > stays > open until I issue an EXIT command. Is there any way to bypass the EXIT > command and come back to SAS session? I have tried "x dir; x exit;" and it > doesn't work. Thanks in advance for any information. >

------------------------------

Date: Fri, 13 Mar 1998 12:44:06 PST From: Jay patel <ggccnnjj@HOTMAIL.COM> Subject: Data _null_ help

Dear SAS users :

Can you please look at following code & shed some lights ?!

Thanks in advance for your time & interest .

>>>>>>>> Program >>>>>>>>

data a; input a $ x1 ; cards; b400 10 b401 20 ; run;

data b; input b $ y1 ; cards; c100 30 c101 40 ; run;

data c; input c $ z1 ; cards; ct100 30 ; run;

data abc; merge a b c; run; proc print; title1 'data=abc'; run;

proc sort data=abc; by a b c ; run; data _null_; set abc; by a; file print notitles header=hd;

%let g1=group1; %let g2=group2; %let g3=group3;

IF _N_ = 1 THEN do;

PUT @15 "&g1" ; end;

IF FIRST.a THEN DO;

PUT @15 a @30 x1 // ;

END;

IF _N_ = 1 THEN DO;

PUT @15 "&g2" ; END;

PUT @15 b @30 y1 // ;

IF _N_ = 1 THEN DO;

PUT @15 "&g3" ; END;

PUT @15 c @30 z1 // ;

RETURN;

HD : /* ******** Header information ********** */

PUT /

@8 'RESPONSE' /

@3 '_____________________________________________________________________'

; RETURN; RUN;

OUTPUT OF THE PROGRAM >>>>>>>>>>>>>>>>>>>

data=abc 5:20 Friday, March 13, 1998 1

OBS A X1 B Y1 C Z1

1 b400 10 c100 30 ct100 30 2 b401 20 c101 40 .

RESPONSE _____________________________________________________________________ group1 b400 10

group2 c100 30

group3 ct100 30

b401 20

c101 40

.

The output should be >>>>>>>>>>>>>>> AS

RESPONSE _____________________________________________________________________ group1 b400 10 b401 20

group2 c100 30 c101 40

group3 ct100 30

______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

------------------------------

Date: Fri, 13 Mar 1998 15:48:42 -0500 From: Ray Pass <raypass@WORLDNET.ATT.NET> Subject: Re: X command & EXIT

At 12:28 AM 3/12/98 +0000, Reiling Lee <Reiling.Lee@ALZA.COM> wrote: >When I submit an X command on PC, a MS-DOS window session is open and stays >open until I issue an EXIT command. Is there any way to bypass the EXIT >command and come back to SAS session? I have tried "x dir; x exit;" and it >doesn't work. Thanks in advance for any information.

Reiling,

That's exactly what the XWAIT/NOXWAIT system option is for. There is also an XSYNC/NOXSYNC option that you should check out. Read up on these options in either the SAS Windows Companion or in the online help system as there are a few subtleties involved, such as whether you are issuing arguments along with the X command. Good luck.

HTH,

Ray

/---------------------------------------------------------\ | Ray Pass voice: (203) 356-9540 | | ASG, Inc. fax: (203) 967-8644 | | 1100 Summer Street | | Stamford, CT 06905 e-mail: raypass@worldnet.att.net | \---------------------------------------------------------/

------------------------------

Date: Fri, 13 Mar 1998 15:51:46 -0500 From: Schechter Robert RS <robert.schecter@PHWILM.ZENECA.COM> Subject: Re: X command & EXIT

Reiling,

In the SAS Companion for MS Windows Environment Second Edition there's an explanation about the XWAIT system option being used to control whether you have to type EXIT to return to your SAS session after an X statement or command. Try entering OPTIONS NOXWAIT; before issuing your X command and see if this is what you want. I tried it on SAS6.12 and it seems to work great.

HTH,

* _________Bob Schechter, Systems Engineer, Pharmaceutical Information Services, Zeneca Pharmaceuticals ( (302) 886-5561 + mailto:Robert.Schecter@usphwilm.zeneca.com

>---------- >From: Reiling Lee[SMTP:Reiling.Lee@ALZA.COM] > >When I submit an X command on PC, a MS-DOS window session is open and stays >open until I issue an EXIT command. Is there any way to bypass the EXIT >command and come back to SAS session? I have tried "x dir; x exit;" and it >doesn't work. Thanks in advance for any information. >

------------------------------

Date: Fri, 13 Mar 1998 15:23:44 CST From: Tsaimei Lin <tlin@MAIL.DOH.STATE.AR.US> Subject: Thanks![RE: Read SAS datasets across different platforms]

Dear SAS-L,

Many thanks to all

CCCS@VTVM1.CC.VT.EDU (Todd Pukanecz) Tom_Teng@em.fcnbd.com (Tom Teng) bernard@capitale.qc.ca (Bernard Tremblay) Klassen@UVic.CA (Melvin Klassen) ajlcary@CaryConsulting.com (Andrew J. L. Cary) sdubnoff@CIRCLESYS.COM (Steven Dubnoff) llddelwiche@ucdavis.edu(Lora Delwiche) amichielson@regence.com (Allen Michielsen)

who responded to my post on "Read SAS datasets across different platforms". The comments and suggestions were very helpful.

Thanks again!!!

Tsai Mei Lin -------- Arkansas Department of Health Center For Health Statistics 4815 W. Markham, Slot 19 Little Rock, AR 72205-3867 Voice : (501)661-2514 or (501)661-2368 Fax : (501)661-2544 E-mail : tlin@mail.doh.state.ar.us ADH HOME Page: http://health.state.ar.us

------------------------------

Date: Fri, 13 Mar 1998 16:10:00 -0500 From: Benjamin Blake <BENJAMIN_W.BLAKE@ROCHE.COM> Subject: SAS/SQL Programming Position at Hoffmann La-Roche

Hoffmann La-Roche, a leading northern New Jersey pharmaceutical corporation located 12 miles west of New York City, currently has a full-time, permanent position opening for a Clinical Programmer in the phase IIIb/IV Statistics and Data Management department, which supports all U.S. post-marketing pharmaceutical clinical trials.

The responsibilities for this position include:

Supporting the set-up and design of Oracle Clinical data bases; Writing SQL scripts to derive and validate Oracle Clinical data; Setting-up and verifying batch jobs to input patient, clinical and laboratory data; Mapping Oracle data variables to standardized SAS data sets.

Qualified individuals must have a minimum of a Bachelor of Science degree in the natural or computer sciences and 3+ years SAS/SQL programming experience in clinical data management.

Direct experience with Oracle Clinical is desirable, but not mandatory.

Salary and compensation plans at Hoffmann La-Roche are highly competitive. We are an equal opportunity employer, fully committed to diversity in the workplace. We appreciate your interest in Hoffmann La-Roche, but can only respond to qualified candidates.

Please fax your resume to: Benjamin Blake 973/235-5987

or mail to: Benjamin Blake, Hoffmann La-Roche, Inc., Bldg. 1 / 5, 340 Kingsland Street, Nutley, NJ 07110

------------------------------

Date: Thu, 12 Mar 1998 00:36:42 GMT From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@VTVM1.CC.VT.EDU> Subject: Re: Help: remote central macro library?

In <D1DB928E2481D111890C00805FE68B8D1BC20F@RIDMSG01>, "ZHAO,JUN BDM BIPUS" <JZHAO@BI-PHARM.COM> writes: >Hi, everyone: > >Thank everyone for response my early question about creating 'remote >central macro library'. Options of using 'SASAUTO=' or MAUTOSOURCE, >suggested by several people, do not work across the platform. The >problem we are facing is server is using Unix and client is using Win95, >and they are connected by SAS/Connect. We are not able put Unix path in >SASAUTO path. If we put macros in server's SAS catalog, remote library >engine does not support accessing remote catalog. Any other thought? >Will filename using FTP help? > >TIA > >Jun Zhao >Boehringer Ingelheim Pharmaceuticals, Inc >jzhao@bi-pharm.com

Jun,

How about an NFS mount of the UNIX box onto your PC? Then you should be able to employ SASAUTO=.

Dale

Dale McLerran dmclerra@fhcrc.org Fred Hutchinson Cancer Research Center ph: (206) 667-2926 1124 Columbia Street fax: (206) 667-5977 Seattle, WA 98104

------------------------------

Date: Fri, 13 Mar 1998 13:48:59 -0800 From: "Yen, Wei" <Wei.Yen@OFM.WA.GOV> Subject: Proc Tabulate Question

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

------ =_NextPart_000_01BD4E86.C6BAB170 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit

>Hi Everyone: > >I am wondering if Proc Tabulate is capable of producing a table as >shown below. If not, are there any other ways to obtain such a table >in SAS? What I am looking for is to have the column variable to show a >weighted total (with percent) and unweighted total with frequency >distributions. > >Any response would be appreciated. > > >

>Wei Yen >Washington State Office of Financial Management >P.O. Box 43113 >Olympia, WA 98504-3113 >(360)902-0591 >(360)664-8941 (fax) >wei.yen@ofm.wa.gov

------ =_NextPart_000_01BD4E86.C6BAB170--

------------------------------

Date: Fri, 13 Mar 1998 14:02:44 -0800 From: "Yen, Wei" <Wei.Yen@OFM.WA.GOV> Subject: Proc Tabulate Question-2

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

------ =_NextPart_000_01BD4E88.B27542F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit

In my last email, I did a copy and paste of the Excel table. The table was lost in the transmittal. Here I included it as an attachment and hopefully it won't get lost again. TIA for your help.

Wei Yen

>---------- >From: Yen, Wei >Sent: Friday, March 13, 1998 1:48 PM >To: 'SAS-L' >Subject: Proc Tabulate Question > >Hi Everyone: > >I am wondering if Proc Tabulate is capable of producing a table as >shown below. If not, are there any other ways to obtain such a table >in SAS? What I am looking for is to have the column variable to show a >weighted total (with percent) and unweighted total with frequency >distributions. > >Any response would be appreciated. > > > > > >Wei Yen >Washington State Office of Financial Management >P.O. Box 43113 >Olympia, WA 98504-3113 >(360)902-0591 >(360)664-8941 (fax) >wei.yen@ofm.wa.gov > >

------ =_NextPart_000_01BD4E88.B27542F0 Content-Type: application/octet-stream; name="Book2.xls" Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAAQAAAAAAAAAA EAAAAgAAAAEAAAD+////AAAAAAAAAAD///////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////9 /////v////7////+////BQAAAAYAAAAHAAAACAAAAP7///8KAAAACwAAAAwAAAANAAAADgAAAA8A AAAQAAAABAAAABIAAAATAAAA/v////////8WAAAAFwAAABgAAAAZAAAAGgAAABsAAAAcAAAAEQAA AP////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////1IA bwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAWAAUA//////////8CAAAAEAgCAAAAAADAAAAAAAAARgAAAAAAAAAAAAAAACBsFb3KTr0B AwAAAIAAAAAAAAAAQgBvAG8AawAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAoAAgD///////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAJAAAANRkAAAAAAAABAEMAbwBtAHAATwBiAGoAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgACAQEAAAADAAAA/////wAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABqAAAAAAAAAAUAUwB1AG0AbQBhAHIAeQBJ AG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAIA//////// ////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFQAAALAUAAAAAAAAAQAA AP7///////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////8BAP7/ AwoAAP////8QCAIAAAAAAMAAAAAAAABGHgAAAE1pY3Jvc29mdCBFeGNlbCA1LjAgV29ya3NoZWV0 AAYAAABCaWZmNQAOAAAARXhjZWwuU2hlZXQuNQD0ObJxAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAP7/AAADXwAA4IWf8vlPaBCrkQgAKyez2QEAAADghZ/y+U9oEKuRCAArJ7PZMAAA AIQUAAAIAAAAEQAAAEgAAAACAAAAIBQAAAMAAAAoFAAABAAAADAUAAAFAAAAUBQAAAYAAABYFAAA EgAAAGAUAAATAAAAeBQAAEcAAADQEwAA/////wMAAAAIADYanRFe1wEACQAAA8gJAAAKAAUCAAAA AAUAAAAJAgAAAAAFAAAAAQL///8ABAAAAAQBDQAEAAAAAgECAAUAAAAMAtUAPQEDAAAAHgAFAgAA 9wAAAwABAAAAAIAAAAAAgAAAgIAAAAAAgACAAIAAAICAAMDAwADA3MAApsrwAIAAAAQAgAAEgIAA BAAAgASAAIAEAICABICAgASAgP8EgCBgBP//wASg4OAEYACABP+AgAQAgMAEwMD/BADP/wRp//8E 4P/gBN2cswSzj+4EKm/5BD+4zQRIhDYElYxBBI5eQgSgYnoEYk+sBB0vvgQoZnYEAEUABAgIAAAF EABsCckHCwIMAAAAAAAAAAAATxEAAA0AAgABAAwAAgBkAA8AAgABABEAAgAAABAACAD8qfHSTWJQ P18AAgABACoAAgAAACsAAgAAAIIAAgABAIAACAAAAAAAAAAAACUCBAAAADgBjAAEAAEAAQCBAAIA wQQUAAAAFQAAAIMAAgAAAIQAAgAAAE0AmAAAAEhQIExhc2VySmV0IElJSQAAAAAAAAAAAAAAAAAA AAAACgOBOEQAUgADBwAAAQABAAAAAAAAAAEAAQD8/wAAAQAAAAAAAACAywMAAAAAAAAAAAAAAAAA AAAAAAAAAAABAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPALwCAAAA/3//f/8A AgACAAEAAKEAIgABAGQAAQABAAEAAgD8/wAAAAAAAAAA4D8AAAAAAADgPwEAVQACAAgAAAIKAAAA AAAAAAABAAA+AgoAtgAAAAAAAAAAAB0ADwADAAAAAAAAAQAAAAAAAAAKAAAACQgIAAAFEABsCckH CwIMAAAAAAAAAAAA2BIAAA0AAgABAAwAAgBkAA8AAgABABEAAgAAABAACAD8qfHSTWJQP18AAgAB ACoAAgAAACsAAgAAAIIAAgABAIAACAAAAAAAAAAAACUCBAAAADgBjAAEAAEAAQCBAAIAwQQUAAAA FQAAAIMAAgAAAIQAAgAAAE0AmAAAAEhQIExhc2VySmV0IElJSQAAAAAAAAAAAAAAAAAAAAAACgOB OEQAUgADBwAAAQABAAAAAAAAAAEAAQD8/wAAAQAAAAAAAACAywMAAAAAAAAAAAAAAAAAAAAAAAAA AAABAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPALwCAAAA/3//f/8AAgACAAEA AKEAIgABAGQAAQABAAEAAgD8/wAAAAAAAAAA4D8AAAAAAADgPwEAVQACAAgAAAIKAAAAAAAAAAAB AAA+AgoAtgAAAAAAAAAAAB0ADwADAAAAAAAAAQAAAAAAAAAKAAAACQgIAAAFEABsCckHCwIMAAAA AAAAAAAAYRQAAA0AAgABAAwAAgBkAA8AAgABABEAAgAAABAACAD8qfHSTWJQP18AAgABACoAAgAA ACsAAgAAAIIAAgABAIAACAAAAAAAAAAAACUCBAAAADgBjAAEAAEAAQCBAAIAwQQUAAAAFQAAAIMA AgAAAIQAAgAAAE0AmAAAAEhQIExhc2VySmV0IElJSQAAAAAAAAAAAAAAAAAAAAAACgOBOEQAUgAD BwAAAQABAAAAAAAAAAEAAQD8/wAAAQAAAAAAAACAywMAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAEA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPALwCAAAA/3//f/8AAgACAAEAAKEAIgAB AGQAAQABAAEAAgD8/wAAAAAAAAAA4D8AAAAAAADgPwEAVQACAAgAAAIKAAAAAAAAAAABAAA+AgoA tgAAAAAAAAAAAB0ADwADAAAAAAAAAQAAAAAAAAAKAAAACQgIAAAFEABsCckHCwIMAAAAAAAAAAAA 6hUAAA0AAgABAAwAAgBkAA8AAgABABEAAgAAABAACAD8qfHSTWJQP18AAgABACoAAgAAACsAAgAA AIIAAgABAIAACAAAAAAAAAAAACUCBAAAADgBjAAEAAEAAQCBAAIAwQQUAAAAFQAAAIMAAgAAAIQA AgAAAE0AmAAAAEhQIExhc2VySmV0IElJSQAAAAAAAAAAAAAAAAAAAAAACgOBOEQAUgADBwAAAQAB AAAAAAAAAAEAAQD8/wAAAQAAAAAAAACAywMAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAEAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPALwCAAAA/3//f/8AAgACAAEAAKEAIgABAGQAAQAB AAEAAgD8/wAAAAAAAAAA4D8AAAAAAADgPwEAVQACAAgAAAIKAAAAAAAAAAABAAA+AgoAtgAAAAAA AAAAAB0ADwADAAAAAAAAAQAAAAAAAAAKAAAACQgIAAAFEABsCckHCwIMAAAAAAAAAAAAcxcAAA0A AgABAAwAAgBkAA8AAgABABEAAgAAABAACAD8qfHSTWJQP18AAgABACoAAgAAACsAAgAAAIIAAgAB AIAACAAAAAAAAAAAACUCBAAAADgBjAAEAAEAAQCBAAIAwQQUAAAAFQAAAIMAAgAAAIQAAgAAAE0A mAAAAEhQIExhc2VySmV0IElJSQAAAAAAAAAAAAAAAAAAAAAACgOBOEQAUgADBwAAAQABAAAAAAAA AAEAAQD8/wAAAQAAAAAAAACAywMAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAEAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAPALwCAAAA/3//f/8AAgACAAEAAKEAIgABAGQAAQABAAEAAgD8 /wAAAAAAAAAA4D8AAAAAAADgPwEAVQACAAgAAAIKAAAAAAAAAAABAAA+AgoAtgAAAAAAAAAAAB0A DwADAAAAAAAAAQAAAAAAAAAKAAAACQgIAAAFEABsCckHCwIMAAAAAAAAAAAA/BgAAA0AAgABAAwA AgBkAA8AAgABABEAAgAAABAACAD8qfHSTWJQP18AAgABACoAAgAAACsAAgAAAIIAAgABAIAACAAA AAAAAAAAACUCBAAAADgBjAAEAAEAAQCBAAIAwQQUAAAAFQAAAIMAAgAAAIQAAgAAAE0AmAAAAEhQ IExhc2VySmV0IElJSQAAAAAAAAAAAAAAAAAAAAAACgOBOEQAUgADBwAAAQABAAAAAAAAAAEAAQD8 /wAAAQAAAAAAAACAywMAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAEAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAPALwCAAAA/3//f/8AAgACAAEAAKEAIgABAGQAAQABAAEAAgD8/wAAAAAA AAAA4D8AAAAAAADgPwEAVQACAAgAAAIKAAAAAAAAAAABAAA+AgoAtgAAAAAAAAAAAB0ADwADAAAA AAAAAQAAAAAAAAAKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJCAgAAAUFAGwJ yQfhAAAAwQACAAAAvwAAAKQABgABABAPAADAAAAA4gAAAFwAIAABICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIEIAAgDkBJwAAgAOABkAAgAAABIAAgAAABMAAgAAAD0AEgB4ADwAzCRoEzgA AAAAAAEAVwJAAAIAAACNAAIAAAAiAAIAAAAOAAIAAQDaAAIAAAAxAB4A8AAAAP9/kAEAAAAAAKUP VGltZXMgTmV3IFJvbWFuMQAeAPAAAQD/f7wCAAAAAAClD1RpbWVzIE5ldyBSb21hbjEAHgDwAAIA /3+QAQAAAAAApQ9UaW1lcyBOZXcgUm9tYW4xAB4A8AADAP9/vAIAAAAAAKUPVGltZXMgTmV3IFJv bWFuMQAeAPAAAAD/f5ABAAAAAAClD1RpbWVzIE5ldyBSb21hbh4EGgAFABciJCIjLCMjMF8pO1wo IiQiIywjIzBcKR4EHwAGABwiJCIjLCMjMF8pO1tSZWRdXCgiJCIjLCMjMFwpHgQgAAcAHSIkIiMs IyMwLjAwXyk7XCgiJCIjLCMjMC4wMFwpHgQlAAgAIiIkIiMsIyMwLjAwXyk7W1JlZF1cKCIkIiMs IyMwLjAwXCkeBDUAKgAyXygiJCIqICMsIyMwXyk7XygiJCIqIFwoIywjIzBcKTtfKCIkIiogIi0i Xyk7XyhAXykeBCwAKQApXygqICMsIyMwXyk7XygqIFwoIywjIzBcKTtfKCogIi0iXyk7XyhAXyke BD0ALAA6XygiJCIqICMsIyMwLjAwXyk7XygiJCIqIFwoIywjIzAuMDBcKTtfKCIkIiogIi0iPz9f KTtfKEBfKR4ENAArADFfKCogIywjIzAuMDBfKTtfKCogXCgjLCMjMC4wMFwpO18oKiAiLSI/P18p O18oQF8p4AAQAAAAAAD1/yAAwCAAAAAAAADgABAAAQAAAPX/IPTAIAAAAAAAAOAAEAABAAAA9f8g 9MAgAAAAAAAA4AAQAAIAAAD1/yD0wCAAAAAAAADgABAAAgAAAPX/IPTAIAAAAAAAAOAAEAAAAAAA 9f8g9MAgAAAAAAAA4AAQAAAAAAD1/yD0wCAAAAAAAADgABAAAAAAAPX/IPTAIAAAAAAAAOAAEAAA AAAA9f8g9MAgAAAAAAAA4AAQAAAAAAD1/yD0wCAAAAAAAADgABAAAAAAAPX/IPTAIAAAAAAAAOAA EAAAAAAA9f8g9MAgAAAAAAAA4AAQAAAAAAD1/yD0wCAAAAAAAADgABAAAAAAAPX/IPTAIAAAAAAA AOAAEAAAAAAA9f8g9MAgAAAAAAAA4AAQAAAAAAABACAAwCAAAAAAAADgABAABQArAPX/IPjAIAAA AAAAAOAAEAAFACkA9f8g+MAgAAAAAAAA4AAQAAUALAD1/yD4wCAAAAAAAADgABAABQAqAPX/IPjA IAAAAAAAAOAAEAAFAAkA9f8g+MAgAAAAAAAA4AAQAAAAAAABACIwwCAAABKAQADgABAAAAAAAAEA IjDAIAAAEABAAOAAEAAAAAAAAQAiMMAggIAQAEAA4AAQAAAAAAABACYwwCAAABKAQADgABAAAAAA AAEAJjDAIAAAAoAAAOAAEAAAAAAAAQAmMMAgAACCgAAg4AAQAAAAAAABACIwwCAAAAqAQADgABAA AAAAAAEAIjDAIICACABAAOAAEAAAAAAAAQAiMMAggICQAEAg4AAQAAAAAAABACIwwCAAAIqAQCDg ABAAAAAAAAEAIjDAIICAiABAIOAAEAAAAAAAAQAiMMAgQIASgEAA4AAQAAAAAAABACIwwCBAgAqA QADgABAAAAAAAAEAIjDAIECAkoBAIOAAEAAAAAAAAQAiMMAgQICKgEAg4AAQAAAAAAABACIwwCBA gBAAQADgABAAAAAAAAEAIjDAIECACABAAOAAEAAAAAAAAQAiMMAgQICQAEAg4AAQAAAAAAABACIw wCBAgIgAQCCTAgQAEIAD/5MCBAARgAb/kwIEABKABP+TAgQAE4AH/5MCBAAAgAD/kwIEABSABf+F AA0AuwYAAAAABlNoZWV0MYUADQBkCwAAAAAGU2hlZXQyhQANAO0MAAAAAAZTaGVldDOFAA0Adg4A AAAABlNoZWV0NIUADQD/DwAAAAAGU2hlZXQ1hQANAIgRAAAAAAZTaGVldDaFAA0AERMAAAAABlNo ZWV0N4UADQCaFAAAAAAGU2hlZXQ4hQANACMWAAAAAAZTaGVldDmFAA4ArBcAAAAAB1NoZWV0MTAK AAAACQgIAAAFEABsCckHCwIQAAAAAAADAAwATQgAAP8KAAANAAIAAQAMAAIAZAAPAAIAAQARAAIA AAAQAAgA/Knx0k1iUD9fAAIAAQAqAAIAAAArAAIAAACCAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAA4 AYwABAABAAEAgQACAMEEFAAAABUAAACDAAIAAACEAAIAAABNANYAAABIUCBMYXNlckpldCA0U2kg KENvcHkgMikAAAAAAAAAAAAEAQSUAEAAA3cABAEAAQAAAAAAAAABAAkB/P8BAAEAWAIEAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAgAAAAAAAAAAAAAAAQBAAE1TVUROA0hQIExhc2VySmV0IDRTaQAAAAAAAAAAAAAAAAAA AAAA5QEAAA0BAAA7AQAAAAAEAGQACgAAAKEAIgABAGQAAQABAAEAAgD8/1gCAAAAAAAA4D8AAAAA AADgPwEAVQACAAgAfQAMAAEAAQBMCg8AAAACAAACCgADAAwAAAAHAAAACAIQAAMAAAAHAEQBAAAS ogABACAIAhAABAAAAAcARAEAAAAAAAEAIAgCEAAFAAAABwBEAQAAAAAAAZclCAIQAAYAAAAHAEQB AADXBQABCCEIAhAABwAAAAcAOAEAAKoAAAECAAgCEAAIAAAABwA4AQAAqgAAAQIACAIQAAkAAAAH ADgBAAAAAAABAAAIAhAACgAAAAcAOAEAAKoAAAFKgggCEAALAAAABwBEAQAA0gAAAViiBAIPAAQA AAAVAAcAVmFybmFtZQQCFgAEAAEAGAAOAFZhcmlhYmxlIExhYmVsvgAQAAQAAgAZABkAGQAZABoA BgABAgYABQAAABUABAIWAAUAAQAYAA4AV2VpZ2h0ZWQgVG90YWwBAgYABQACABkABAImAAUAAwAY AB4AVW53ZWlnaHRlZCBTYW1wbGUgRGlzdHJpYnV0aW9uvgAMAAUABAAZABkAGgAGAAECBgAGAAAA FgAEAgkABgABABUAAQBOBAIJAAYAAgAbAAEAJQQCDQAGAAMAFQAFAFRvdGFsBAIPAAYABAAbAAcA R3JvdXAgMQQCDwAGAAUAGwAHAEdyb3VwIDIEAg8ABgAGAB4ABwBHcm91cCAzBAINAAcAAAAiAAUA Q2F0IDG+ABIABwABACAAIQAgACEAIQAjAAYABAINAAgAAAAmAAUAQ2F0IDK+ABIACAABACQAJQAk ACUAJQAnAAYABAINAAkAAAAmAAUAQ2F0IDO+ABIACQABACQAJQAkACUAJQAnAAYABAINAAoAAAAm AAUAQ2F0IDS+ABIACgABACQAJQAkACUAJQAnAAYABAINAAsAAAAdAAUAVG90YWy+ABIACwABABcA HAAXABwAHAAfAAYA1wAWAI4CAACgAAAAQQBoAG4AJwAnACcAJwA+AgoAtgYDAAAAAAAAAB0ADwAD BwAAAAAAAQAHAAcAAACrACIAIAD9/////////////////////////////////////////woAAAAJ CAgAAAUQAGwJyQcLAgwAAAAAAAAAAAC0DAAADQACAAEADAACAGQADwACAAEAEQACAAAAEAAIAPyp 8dJNYlA/XwACAAEAKgACAAAAKwACAAAAggACAAEAgAAIAAAAAAAAAAAAJQIEAAAAOAGMAAQAAQAB AIEAAgDBBBQAAAAVAAAAgwACAAAAhAACAAAATQCYAAAASFAgTGFzZXJKZXQgSUlJAAAAAAAAAAAA AAAAAAAAAAAKA4E4RABSAAMHAAABAAEAAAAAAAAAAQABAPz/AAABAAAAAAAAAIDLAwAAAAAAAAAA AAAAAAAAAAAAAAAAAAEAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8AvAIAAAD/ f/9//wACAAIAAQAAoQAiAAEAZAABAAEAAQACAPz/AAAAAAAAAADgPwAAAAAAAOA/AQBVAAIACAAA AgoAAAAAAAAAAAEAAD4CCgC2AAAAAAAAAAAAHQAPAAMAAAAAAAABAAAAAAAAAAoAAAAJCAgAAAUQ AGwJyQcLAgwAAAAAAAAAAAA9DgAADQACAAEADAACAGQADwACAAEAEQACAAAAEAAIAPyp8dJNYlA/ XwACAAEAKgACAAAAKwACAAAAggACAAEAgAAIAAAAAAAAAAAAJQIEAAAAOAGMAAQAAQABAIEAAgDB BBQAAAAVAAAAgwACAAAAhAACAAAATQCYAAAASFAgTGFzZXJKZXQgSUlJAAAAAAAAAAAAAAAAAAAA AAAKA4E4RABSAAMHAAABAAEAAAAAAAAAAQABAPz/AAABAAAAAAAAAIDLAwAAAAAAAAAAAAAAAAAA AAAAAAAAAAEAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8AvAIAAAD/f/9//wAC AAIAAQAAoQAiAAEAZAABAAEAAQACAPz/AAAAAAAAAADgPwAAAAAAAOA/AQBVAAIACAAAAgoAAAAA AAAAAAEAAD4CCgC2AAAAAAAAAAAAHQAPAAMAAAAAAAABAAAAAAAAAAoAAAAJCAgAAAUQAGwJyQcL AgwAAAAAAAAAAADGDwAADQACAAEADAACAGQADwACAAEAEQACAAAAEAAIAPyp8dJNYlA/XwACAAEA KgACAAAAKwACAAAAggACAAEAgAAIAAAAAAAAAAAAJQIEAAAAOAGMAAQAAQABAIEAAgDBBBQAAAAV AAAAgwACAAAAhAACAAAATQCYAAAASFAgTGFzZXJKZXQgSUlJAAAAAAAAAAAAAAAAAAAAAAAKA4E4 RABSAAMHAAABAAEAAAAAAAAAAQABAPz/AAABAAAAAAAAAIDLAwAAAAAAAAAAAAAAAAAAAAAAAAAA AAEAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8AvAIAAAD/f/9//wACAAIAAQAA oQAiAAEAZAABAAEAAQACAPz/AAAAAAAAAADgPwAAAAAAAOA/AQBVAAIACAAAAgoAAAAAAAAAAAEA AD4CCgC2AAAAAAAAAAAAHQAPAAMAAAAAAAABAAAAAAAAAAoAAAAJFQAAAPsC7P8AAAAAAACQAQAA AAAAAAASVGltZXMgTmV3IFJvbWFuAEyEBAAAAC0BCQAFAAAAAQL///8ABAAAAAQBDQAEAAAAAgEB ABIAAAAyCocALwAHAAAAVmFybmFtZQANAAkABwAJAAkADgAJAAQAAAAtAQQABQAAAAkC////AAQA AAACAQIACQAAAB0GIQDwABkAAgCEAOMACQAAAB0GIQDwABkAAQCEAOUACQAAAB0GIQDwABkAAgCE ADsBCQAAAB0GIQDwABkAAQCEAD0BCQAAAB0GIQDwABkAAgCEAJMBCQAAAB0GIQDwABkAAQCEAJUB CQAAAB0GIQDwABkAAgCEAOsBCQAAAB0GIQDwABkAAQCEAO0BCQAAAB0GIQDwABkAAgCEAEMCCQAA AB0GIQDwABkAAQCEAEUCBQAAAAkCAAAAAAQAAAACAQEAHAAAADIKhwBSAQ4AAABWYXJpYWJsZSBM YWJlbA0ACQAHAAYACQAKAAYACQAFAAsACQAKAAkABgAFAAAACQL///8ABAAAAAIBAgAJAAAAHQYh APAAGQACAJ8A4wAJAAAAHQYhAPAAGQABAJ8A5QAFAAAACQIAAAAABAAAAAIBAQAcAAAAMgqiAKAA DgAAAFdlaWdodGVkIFRvdGFsEgAJAAYACQAJAAUACQAKAAUADAAKAAUACQAGAAUAAAAJAv///wAE AAAAAgECAAkAAAAdBiEA8AAZAAIAnwCTAQkAAAAdBiEA8AAZAAEAnwCVAQkAAAAdBiEA8AAZAAIA nwDrAQkAAAAdBiEA8AAZAAEAnwDtAQkAAAAdBiEA8AAZAAIAnwBDAgkAAAAdBiEA8AAZAAEAnwBF AgUAAAAJAgAAAAAEAAAAAgEBADQAAAAyCqIAbAEeAAAAVW53ZWlnaHRlZCBTYW1wbGUgRGlzdHJp YnV0aW9uDQAJAA8ACQAGAAkACQAFAAkACgAFAAsACQAOAAoABgAJAAUADgAGAAgABQAHAAYACgAJ AAUABgAKAAkACQAAADIKvQCqAAEAAABOAA4ACQAAADIKvQAIAQEAAAAlABEABAAAAC0BAQAEAAAA LQEIAAQAAAAnAf//AwAAAB4ABAAAAC0BCQAFAAAAAQL///8ABQAAAAkCAAAAAAcAAAAWBNUAPQEA AAAABAAAAC0BAQAEAAAABAENAAQAAAACAQIABAAAAPABAgAJAAAA+gIAAAAAAAAAAAAAIgAEAAAA LQECAAUAAAAUAgAAAAAFAAAAEwIAAD0BBAAAAC0BAwAJAAAAHQYhAPAAAQA9AQAAAAAEAAAALQEC AAUAAAAUAgAAAAAFAAAAEwLVAAAABAAAAC0BAwAJAAAAHQYhAPAA1QABAAAAAAAEAAAALQEBAAQA AAAnAf//AwAAAAAAM9CJVwa4AQDrAjPAXsnKAgCQyBAAAI1G8FD/dgiaOwCflIpG9irkA0bwi1by UlCKHgAAAAAAAAAeAAAAAAAAAB4AAAAVAAAASW5mb3JtYXRpb24gU2VydmljZXMAAAAAHgAAAAAA AAAeAAAAAAAAAB4AAAAQAAAATWljcm9zb2Z0IEV4Y2VsAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGgAAAAQAAAAtAQIABQAAABQCAAB9 AAUAAAATAhsAfQAEAAAALQEDAAkAAAAdBiEA8AAbAAEAAAB9AAQAAAAtAQIABQAAABQCAADkAAUA AAATAhsA5AAEAAAALQEDAAkAAAAdBiEA8AAbAAEAAADkAAQAAAAtAQIABQAAABQCAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAAA18AAOCFn/L5T2gQq5EIACsn s9kBAAAA4IWf8vlPaBCrkQgAKyez2TAAAACEFAAACAAAABEAAABIAAAAAgAAACAUAAADAAAAKBQA AAQAAAAwFAAABQAAAFAUAAAGAAAAWBQAABIAAABgFAAAEwAAAHgUAABHAAAA0BMAAP////8DAAAA CAA2Gp0RXtcBAAkAAAPICQAACgAFAgAAAAAFAAAACQIAAAAABQAAAAEC////AAQAAAAEAQ0ABAAA AAIBAgAFAAAADALVAD0BAwAAAB4ABQIAAPcAAAMAAQAAAACAAAAAAIAAAICAAAAAAIAAgACAAACA gADAwMAAwNzAAKbK8ACAAAAEAIAABICAAAQAAIAEgACABACAgASAgIAEgID/BIAgYAT//8AEoODg BGAAgAT/gIAEAIDABMDA/wQAz/8Eaf//BOD/4ATdnLMEs4/uBCpv+QQ/uM0ESIQ2BJWMQQSOXkIE oGJ6BGJPrAQdL74EKGZ2BABFAARFPgEEaigTBIU5agRKMoUEBAQEBAgICAQMDAwEERERBBYWFgQc HBwEIiIiBCkpKQQwMDAEX19fBFVVVQRNTU0EQkJCBDk5OQQABwAEDQAABLeZgQSEmbQEvb2QBH9/ YARgYH8EAA4ABBsAAAQoAAAECAkrBAAdAAQ5AAAEAACbBAAlAARJAAAEERE7BAAvAARdAAAEFxdF BAA6AARJEREEHBxTBAAW/wQrAP8EISFsBFkUFAQAUQAERxpqBBkyZwQAYQAEADH/BGEA/wRTIHsE FkNnBC4u4gQmWRYEUUYEBGguSQQHUo8Eahi4BJAjFQQAU/8EowD/BGpKEgR1M2wESkGaBDdlCwSk LBUEgx+xBE4s/wQgUbYECGSSBG9WCwRZQ60ENnISBLAzFwQAoQAEd18fBIlHcQSwQxwEty19BACG lQR6biMEJp8ABHOpAQQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABADKAASsWwEEIB3C BJRScAQkqkwECpSJBDZuewREdZAE/wCoBABx/wTfAP8EVpFKBDRI+ATMMoIE5EFwBGjKAQQ2vEIE AJr/BJYitwSFfTMEJbeMBDZa7QRc/wAE/0gABCKbogRCz00EwlhSBCDTlQSlJOAEc1a1BKmpAATQ bzwEZ59YBInPCwT/rAAEpy7+BOJZfwRM3GcE/xj/BDp9/wSx0BgEx/8ABP/iAATfmj0EVoGfBMZD ugSvcYsEOKLJBNFTzgT/mmUERsrbBP9N/wTI6WoETN7gBP+Y/wTfwIIE6eylBPX2zQT/0P8Esaxa BGORrgQiTGUEjU4/BFBwcATQ//8E/+f/BGlpaQR3d3cEhoaGBJaWlgSdnZ0EpKSkBLKysgTLy8sE 19fXBN3d3QTj4+ME6urqBPHx8QT4+PgEssFmBIC/eATG8PAEsqT/BP+z/wTRjqMEw9w3BKCeVAR2 rnAEeJ7BBINkvwSkg9ME0T8yBP99AAREeCMEJF9gBA4OLAS+AAAE/x8ABDE5AATZhT4EAneFBLDY gQRWIR0EAAAwBIjIswSgeQAEwMDABOpwgQRR8WkE//+ABJF0zQT/fP8Eov//BP/78ACgoKQAgICA AP8AAAAA/wAA//8AAAAA/wD/AP8AAP//AP///wAEAAAANAIAAAMAAAA1AAQAAAAnAf//BQAAAAsC AAAAAAMAAAAeAAUAAAABAv///wAFAAAACQIAAAAABAAAACcB//8DAAAAHgAFAAAAAQL///8ABQAA AAkCAAAAAAcAAAAWBNUAPQEBAAEABwAAAPwCAAAAAAAAAAAEAAAALQEBAAUAAAABAgAAAAAEAAAA BAENAAQAAAACAQIACQAAAPoCAAAAAAAAAAAAACIABAAAAC0BAgAFAAAAFAIAACUABQAAABMC1QAl AAkAAAD6AgAAAAAAAAAAAAAiAAQAAAAtAQMACQAAAB0GIQDwANUAAQAAACUABAAAAC0BAgAFAAAA FAI0AAAABQAAABMCNAAmAAQAAAAtAQMACQAAAB0GIQDwAAEAJgA0AAAABAAAAC0BAgAFAAAAFAJO AAAABQAAABMCTgAmAAQAAAAtAQMACQAAAB0GIQDwAAEAJgBOAAAABAAAAC0BAgAFAAAAFAJoAAAA BQAAABMCaAAmAAQAAAAtAQMACQAAAB0GIQDwAAEAJgBoAAAABAAAAC0BAgAFAAAAFAKDAAAABQAA ABMCgwAmAAQAAAAtAQMACQAAAB0GIQDwAAEAJgCDAAAABAAAAC0BAgAFAAAAFAKeAAAABQAAABMC ngAmAAQAAAAtAQMACQAAAB0GIQDwAAEAJgCeAAAABAAAAC0BAgAFAAAAFAK5AAAABQAAABMCuQAm AAQAAAAtAQMACQAAAB0GIQDwAAEAJgC5AAAABAAAAC0BAgAFAAAAFALUAAAABQAAABMC1AAmAAQA AAAtAQMACQAAAB0GIQDwAAEAJgDUAAAABAAAAC0BAgAFAAAAFAIaAAAABQAAABMCGgA9AQQAAAAt AQMACQAAAB0GIQDwAAEAPQEaAAAABAAAAC0BAgAFAAAAFAIAAH0ABQAAABMCGwB9AAQAAAAtAQMA CQAAAB0GIQDwABsAAQAAAH0ABAAAAC0BAgAFAAAAFAIAAOQABQAAABMCGwDkAAQAAAAtAQMACQAA AB0GIQDwABsAAQAAAOQABAAAAC0BAgAFAAAAFAIAADwBBQAAABMCGwA8AQQAAAAtAQMACQAAAB0G IQDwABsAAQAAADwBBwAAAPwCAAD///8AAAAEAAAALQEEAAQAAAAnAf//AwAAAB4ABAAAAC0BAQAF AAAAAQIAAAAABQAAAAkCAAAAAAcAAAAWBNUAPQEbACYABwAAAPwCAADAwMAAAAAEAAAALQEFAAUA AAAJAsDAwAAFAAAAAQLAwMAABAAAAAQBDQAEAAAAAgECAAQAAADwAQIACQAAAPoCAAAAAAAAwMDA ACIABAAAAC0BAgAFAAAAFAI0ACYABQAAABMCNAA9AQQAAAAtAQMACQAAAB0GIQDwAAEAFwE0ACYA BAAAAC0BAgAFAAAAFAJOACYABQAAABMCTgA9AQQAAAAtAQMACQAAAB0GIQDwAAEAFwFOACYABAAA AC0BAgAFAAAAFAJoACYABQAAABMCaAA9AQQAAAAtAQMACQAAAB0GIQDwAAEAFwFoACYABAAAAC0B AgAFAAAAFAKDACYABQAAABMCgwA9AQQAAAAtAQMACQAAAB0GIQDwAAEAFwGDACYABAAAAC0BAgAF AAAAFAKeACYABQAAABMCngA9AQQAAAAtAQMACQAAAB0GIQDwAAEAFwGeACYABAAAAC0BAgAFAAAA FAK5ACYABQAAABMCuQA9AQQAAAAtAQMACQAAAB0GIQDwAAEAFwG5ACYABAAAAC0BAgAFAAAAFALU ACYABQAAABMC1AA9AQQAAAAtAQMACQAAAB0GIQDwAAEAFwHUACYABAAAAC0BAgAFAAAAFAIbAH0A BQAAABMC1QB9AAQAAAAtAQMACQAAAB0GIQDwALoAAQAbAH0ABAAAAC0BAgAFAAAAFAIbAOQABQAA ABMC1QDkAAQAAAAtAQMACQAAAB0GIQDwALoAAQAbAOQABAAAAC0BAgAFAAAAFAIbADwBBQAAABMC 1QA8AQQAAAAtAQMACQAAAB0GIQDwALoAAQAbADwBBAAAAC0BAQAFAAAACQIAAAAABQAAAAEC//// AAQAAADwAQIACQAAAPoCAAAAAAAAAAAAACIABAAAAC0BAgAFAAAAFALuACYABQAAABMC7gB8AAQA AAAtAQMACQAAAB0GIQDwAAEAVgDuACYABAAAAC0BAgAFAAAAFAK6AOQABQAAABMC0wDkAAQAAAAt AQMACQAAAB0GIQDwABkAAQC6AOQABAAAAC0BAgAFAAAAFALuAH4ABQAAABMC7gA7AQQAAAAtAQMA CQAAAB0GIQDwAAEAvQDuAH4ACQAAAB0GIQDwAG0AAgCCACQACQAAAB0GIQDwAGsAAgCEAHwACQAA AB0GIQDwAFAAAgCfADsBBAAAAC0BAgAFAAAAFALVAOQABQAAABMC7wDkAAQAAAAtAQMACQAAAB0G IQDwABoAAQDVAOQACQAAAB0GIQDwAAIAbwGCACYACQAAAB0GIQDwAAIAbwGdACYACQAAAB0GIQDw AAIAFwG4AH4ACQAAAB0GIQDwAAIAbwHTACYABAAAAC0BAgAFAAAAFALuAD0BBQAAABMC7gCVAQQA AAAtAQMACQAAAB0GIQDwAAEAWADuAD0BBAAAAC0BBAAEAAAAJwH//wMAAAAeAAQAAAAtAQEABQAA AAEC////AAUAAAAJAgAAAAAHAAAAFgTVAD0BAQABABUAAAD7Auz/AAAAAAAAvAIAAAAAAAAAElRp bWVzIE5ldyBSb21hbgD8/wQAAAAtAQYABQAAAAECwMDAAAQAAAAEAQ0ABAAAAAIBAQANAAAAMgoD ACkAAQAGAAMAAwAlABoAIAAEAAcAAAD8AgAAgICAAAAABAAAAC0BBwAFAAAACQKAgIAABQAAAAEC ////AAQAAAACAQIABAAAAPABAgAJAAAA+gIAAAAAAACAgIAAIgAEAAAALQECAAUAAAAUAhkAAgAF AAAAEwIZACUABAAAAC0BAwAJAAAAHQYhAPAAAQAjABkAAgAEAAAALQECAAUAAAAUAgIAJAAFAAAA EwIZACQABAAAAC0BAwAJAAAAHQYhAPAAFwABAAIAJAAEAAAALQECAAUAAAAUAhgAAwAFAAAAEwIY ACUABAAAAC0BAwAJAAAAHQYhAPAAAQAiABgAAwAEAAAALQECAAUAAAAUAgMAIwAFAAAAEwIaACMA BAAAAC0BAwAJAAAAHQYhAPAAFwABAAMAIwAEAAAALQEBAAQAAAAtAQYABQAAAAkCAAAAAAUAAAAB AsDAwAAEAAAAAgEBAA0AAAAyCh0ADgABAAIAAgAcACUANAAxAAoADQAAADIKNwAOAAEAAgACADYA JQBOADIACgANAAAAMgpRAA4AAQACAAIAUAAlAGgAMwAKAA0AAAAyCmsADgABAAIAAgBqACUAgwA0 AAoADQAAADIKhgAOAAEAAgACAIUAJQCeADUACgANAAAAMgqhAA4AAQACAAIAoAAlALkANgAKAA0A AAAyCrwADgABAAIAAgC7ACUA1AA3AAoADQAAADIKAwBLAAEAAgAnAAIAfQAaAEEADgANAAAAMgoD AKsAAQACAH8AAgDkABoAQgANAA0AAAAyCgMACgEBAAIA5gACADwBGgBDAA4AEAAAAPsCFAAJAAAA AAC8AgAAAAABAgIiU3lzdGVtAG4EAAAALQEIAAQAAAAnAf//AwAAAB4ABAAAAC0BBgAFAAAAAQLA wMAABQAAAAkCAAAAAAcAAAAWBNUAPQEbACYA

------ =_NextPart_000_01BD4E88.B27542F0--

------------------------------

End of SAS-L Digest - 12 Mar 1998 to 13 Mar 1998 ************************************************

Original Recipient: RPATERSO.DVSEMAIL @ QEDI

Original Recipient: RPATERSO.DVSEMAIL @ QEDI2


Back to: Top of message | Previous page | Main SAS-L page