LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (May 2008, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 6 May 2008 12:45:20 -0700
Reply-To:     Lex Jansen <lexjansen@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Lex Jansen <lexjansen@GMAIL.COM>
Organization: http://groups.google.com
Subject:      Re: Licensed vs. Installed?
Comments: To: sas-l@uga.edu
Content-Type: text/plain; charset=ISO-8859-1

Worse, if you look at how the output from the DIR pipes is read (hard- coded columns ...), it most likely needs tweaking if your regional system settings are different from the standard US settings: mm/dd/ yyyy hh:mm tt

filename file1 pipe 'dir "c:\program files\sas\SAS System\9.0"';

data temp1; infile file1 truncover; input var1 $ 1-100; tester=substr(var1,26,3); product=substr(var1,40,30); run; quit;

Lex

On May 6, 1:43 pm, Nathaniel.Wood...@DOM.COM (Nat Wooding) wrote: > Andrew > > The consensus at the time was that Proc Setinit only spoke of licensing. > The function Sysprod() also does not help here. > > If you are on a Windows machine, there is a downloadable SAS job for > checking on installed products. The support note at > > http://support.sas.com/kb/7/640.html > > tells of this and gives a link for downloading the job. I see that there > are different ones for V8 and V9 ( Filedetv8.sas and Filedetv9.SA ) . They > operate by searching the SAS directory and check for specific dlls. eg > > if (dllprod='sasimode.dll') then prodinst='Access to PC File Formats'; > if (dllprod='sasioodb.dll') then prodinst='Access to ODBC'; > if (dllprod='sasiosyb.dll') then prodinst='Access to Sybase'; > if (dllprod='sasioora.dll') then prodinst='Access to Oracle'; > if (dllprod='sasiotra.dll') then prodinst='Access to Teradata'; > if (dllprod='sasiodbu.dll') then prodinst='Access to DB2'; > if (dllprod='sasioole.dll') then prodinst='Access to OLE/DB'; > > I don't see why someone could not write a similar job for other OS. > > Hope all is well out there. > > Nat > > Ps: Don't let Toby look at either of these programs or he'll bust a gut > swearing at the programming style. There's a whole lot of > > Data a; ... > > Data B; > set a; > Data C; > set b; > > and I don't see later refs. to the earlier sets. > > Nat Wooding > Environmental Specialist III > Dominion, Environmental Biology > 4111 Castlewood Rd > Richmond, VA 23234 > Phone:804-271-5313, Fax: 804-271-2977 > > "Sierra > Information > Services (Andrew To > H Karp)" SA...@LISTSERV.UGA.EDU > <sfbay0...@AOL.CO cc > M> > Sent by: "SAS(r) Subject > Discussion" Licensed vs. Installed? > <SA...@LISTSERV.U > GA.EDU> > > 05/06/2008 12:37 > PM > > Please respond to > "Sierra > Information > Services (Andrew > H Karp)" > <sfbay0...@AOL.CO > M> > > Hi... > > I seem to recall a discussion some months ago about what's licensed > vs. what's installed. Can someone please remind me how we can > determine what SAS software modules are installed on your machine vs. > what's been licensed? My recollection is that PROC SETINIT will tell > you what is licensed, not what's actually installed. > > Thanks! > > Andrew Karp > Sierra Information Serviceswww.SierraInformation.com > > ----------------------------------------- > CONFIDENTIALITY NOTICE: This electronic message contains > information which may be legally confidential and/or privileged and > does not in any case represent a firm ENERGY COMMODITY bid or offer > relating thereto which binds the sender without an additional > express written confirmation to that effect. The information is > intended solely for the individual or entity named above and access > by anyone else is unauthorized. If you are not the intended > recipient, any disclosure, copying, distribution, or use of the > contents of this information is prohibited and may be unlawful. If > you have received this electronic transmission in error, please > reply immediately to the sender that you have received the message > in error, and delete it. Thank you.


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