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 (June 2000, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 26 Jun 2000 13:58:06 +0100
Reply-To:     Peter Crawford <peter.crawford@DB.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Peter Crawford <peter.crawford@DB.COM>
Subject:      Re: Where is SASAUTOS?
Comments: To: sashole@mediaone.net, shiling@MATH.WAYNE.EDU
Content-type: text/plain; charset=us-ascii

I seem a bit late, entering this thread, but I've become "open" and "multiplatform" and "enterprise integration technologied" at SeUGI last week ! To find out where the "sasautos" exist, issue the pathname function in a data step or open macro statement, like appears in this snip from my mainframe SAS display manager log window, following statement %put %sysfunc( pathname(sasautos));

NOTE: The initialization phase used 0.04 CPU seconds and 2863K. 1 %put %sysfunc( pathname(sasautos)); MVS.SAS.AUTOLIB

so it appears that the pds holding the sasauto macros is MVS.SAS.AUTOLIB

And on win v6.12, the same code applies, but with far more output ! 1 %put %sysfunc( pathname(sasautos)); c:\Program Files\SAS\af\sasmacro c:\Program Files\SAS\assist\sasmacro c:\Program Files\SAS\base\sasmacro c:\Program Files\SAS\calc\sasmacro c:\Program Files\SAS\sascbt\sasmacro c:\Program Files\SAS\connect\sasmacro C:\Program Files\SAS\core\sasmacro

In v8 on os390 NOTE: The initialization phase used 0.10 CPU seconds and 5951K. 1 %put %sysfunc( pathname(sasautos)); MVS.SAS.V80.AUTOLIB

So it seems fair to expect this to apply across all recent versions and platforms !

Datum: 23/06/2000 21:00 An: SAS-L@listserv.uga.edu

Antwort an: sashole@mediaone.net

Betreff: Re: Where is SASAUTOS? Nachrichtentext:

Shiling,

Submit some SAS job and look at at it in SDSF. Type 'l' or '?' next to your job name, press <enter> and select JESJCL entry. Do a find on AUTOLIB, because SAS autocall library (PDS) is usually called something like SYS*.SAS.V8*.AUTOLIB. It is also usual to find SASHELP and SASMSG libraries right beneath it. If you want to add your own autocall library to this one, simply use

//SASAUTOS DD DSN=SHILING.AUTOLIB,DISP=SHR

after the JCL line containing EXEC.

Oh yeah, and welcome to the rough world of real computers.

Kind regards, ==================== Paul M. Dorfman Jacksonville, FL ==================== >From: shiling@MATH.WAYNE.EDU >Reply-To: shiling@MATH.WAYNE.EDU >To: SAS-L@LISTSERV.UGA.EDU >Subject: Where is SASAUTOS? >Date: Fri, 23 Jun 2000 18:53:48 GMT > >I have no idea about where SASAUTOS is when one gives me JCL+SAS codes? > >I added getoption('sasautos') in the PGM, the return value is SASAUTOS >which did no give me any clues. > >So where is the SASAUTOS usually set up on a mainframe,or any >conventions? > >TIA. > > >Sent via Deja.com http://www.deja.com/ >Before you buy.

________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com


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