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 (August 1999, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Sun, 1 Aug 1999 11:53:36 -0400
Reply-To:     RHOADSM1 <RHOADSM1@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         RHOADSM1 <RHOADSM1@WESTAT.COM>
Subject:      Re: Access to Novell
Comments: To: HEATONE <HEATONE@westat.com>
Content-Type: text/plain; charset=US-ASCII

Ed,

I don't think it's as much a question of access rights, but of whether or not you are attached to the Novell server in question. Under Novell 3.x, if you are not logged on or attached to the server, you can't get to a file stored in it, regardless of the access rights you may have.

You can still, however, get around the need to map a drive letter. If this is not a server to which you are normally attached, you can create a BAT file to do the connection and then call this from your SAS program. For instance, put the two lines below in c:\junk\attach.bat:

attach reg/guest exit

and then run code something like that below: options xsync noxwait; x 'c:\junk\attach.bat';

filename test "\\reg\sys\weswin2\sas612\autoexec.sas";

data _null_; infile test; input; put _infile_; run;

Mike Rhoads Westat RhoadsM1@Westat.com

<<Ed Heaton asked>> Greetings; Here at Westat, we have some SAS macros that are stored on a Novell network in folders where I have no access. (I rather like having no write access, read access would simplify matters.) We normally access these macros by assigning a drive letter to the folder (logging in as "guest" with no password) and then using that path in a FILENAME statement. However, I do not like to use mapped network drive letters in my code. I get much more portability if I use network path designations such as FILENAME coll_adj "\\Red\Sys\TechPup\StatMacs\Coll_Adj.mac" ; %INCLUDE coll_adj ; But this does not work. It seems that my job does not have the permissions necessary to include the macro. I tried FILENAME coll_adj "\\Red\Sys\TechPup\StatMacs\Coll_Adj.mac" NAME= "guest" ; %INCLUDE coll_adj ; but it also did not work; NAME= is not a valid option. I have not found the documentation for the FILENAME statement that allows me to include this macro. So I mapped a network drive and ran the job using FILENAME coll_adj "o:\StatMacs\Coll_Adj.mac" ; %INCLUDE coll_adj ; However, I really do not like to use mapped network drives. Do you know how I can access the COLL_ADJ.MAC macro on a Novell network?

Ed

Edward Heaton, Sr. Systems Analyst, Westat (An Employee-Owned Research Corporation), 1550 Research Boulevard, Room 2018, Rockville, MD 20850-3159 voice: (301) 610-4818 fax: (301) 294-3992 mailto:heatone@westat.com http://www.westat.com


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