topic Re: Cannot create library and read csv file from local computer in SAS Enterprise Guide

Re: Cannot create library and read csv file from local computer

Ram4sas — Wed, 15 Jul 2015 20:07:02 GMT

HI ALL,

we have SAS EBI system 9.4 on Unix servers. User having client applications having EG 6.1 on window 7.

Issue 1:

User A, having PC SAS and have create sas code, data sets and placed source files in shared drive.

User B, wants to create library for User A windows path to use sas code, data sets and source file, which is not working(User A and B are in same group, but User B EG not PC SAS).

Issue 2:

User X trying to read data(.csv) fill from windows machine, its giveing error (attached)

How to fix and enable users to create library for their windows path?

Error:

Libname bc ‘C:\xxxxx\data’;

ERROR: Physical file does not exist, /opt/sas/Config/Lev1/SASApp/J:\User\ Provid07132015.csv.

NOTE: The SAS System stopped processing this step because of errors. WARNING: The data set
WORK.TEST1 may be incomplete. When this step was stopped there were 0 observations and 11 variables.

NOTE: DATA statement used (Total process time):

real time 0.10 seconds

cpu time 0.02 seconds

66 data file1;

67 set test1;

68 pbase1_3= ' ';

69 pbase5_8= ' ';

70 pid1_4 = ' ';

71 pid5_7 = ' ';

72 provkey = ' ';

73 pbase1_3 =
substr(provbase,1,3);

74 pbase5_8 =substr(provbase,5,4);

75 pid1_4 =substr(provid,1,4);

76 pid5_7 =substr(provid,5,3);

77 provkey =pbase5_8||provtype||pid1_4||pbase1_3||pid5_7;

78 fname = scan(contname,1,'');

79 lname =scan(contname,2);

82 if email = ' ' then delete;

83 *if contname = ' ' then delete;

84 *drop contname;

87 run;

NOTE: There were 0
observations read from the data set WORK.TEST1.

NOTE: The data set WORK.FILE1 has 0 observations and 18 variables.

NOTE: DATA statement used (Total process time):

real time 0.08 seconds

cpu time 0.02 seconds

88 proc sort data = file1; by provkey;

89 run;

NOTE: Input data set is
empty.

NOTE: The data set
WORK.FILE1 has 0 observations and 18 variables.

NOTE: PROCEDURE SORT
used (Total process time):

real time 0.42 seconds

cpu time 0.00 seconds

3 The SAS System 10:47
Wednesday, July 15, 2015

90 proc print data =
file1(obs=10);

91 title "ARC
Provider file with provider key";

92 run;

NOTE: No observations
in data set WORK.FILE1.

NOTE: PROCEDURE PRINT
used (Total process time):

real time 0.00 seconds

cpu time 0.00 seconds

94 data bc.provider_file_&date.;

95 set file1;

96 by provkey;

97 *if provtype ='45';

98 run;

ERROR: Library BC does not exist.

NOTE: The SAS System
stopped processing this step because of errors.

NOTE: There were 0
observations read from the data set WORK.FILE1.

NOTE: DATA statement
used (Total process time):

real time 0.00 seconds

cpu time 0.01 seconds

Thanks,

Ram

Re: Cannot create library and read csv file from local computer

jakarman — Wed, 15 Jul 2015 21:35:28 GMT

1/ Your location for the csv should follow the Unix conventions where you have placed that file (drag drop for transfer windows to eguide files)

2/ your current dir is not your home dir. You will get a lot of errors on that. Either be secure in specifying always a full path or let that defult location be corrected to normal standards (not the SAS default).

Re: Cannot create library and read csv file from local computer

Kurt_Bremser — Wed, 15 Jul 2015 22:05:28 GMT

Since the workspace server that the Enterprise Guide connects to resides on a UNIX server, it has no access to the local PC. Transfer the files to the SAS server, and use UNIX naming conventions (https://en.wikipedia.org/wiki/Unix_filesystem).

Re: Cannot create library and read csv file from local computer

Tom — Thu, 16 Jul 2015 01:37:15 GMT

If your users are using a shared "J" drive on their PCs to store these text files then check with your SAS/UNIX administrators and see if they will mount the same drive on the Unix machine that is running SAS. So if "J:" on the PC is pointing to \\servname\sharename on the PC network ask them to mount this on the Unix filesystem and they will tell you the path.

Let's assume that they mounted it /usr/share/ then the file that you see as "J:\subdir\fname.txt" on WINDOWS will be visible at "/usr/share/subdir/fname.txt" on Unix. Watch out for the case of the names. On a unix system 'Provid.csv' and 'provid.csv' are two different files. But on a Windows machine they are the same file.

If however the "J" drive is just pointing the the individual users directories and permissions are such that user X cannot see files in the directory made for user Y then you might have other problems.

If you cannot get Unix admins to mount the files then you will need to get Enterprise Guide to upload the file to the Unix host before running the code module that reads it.

Re: Cannot create library and read csv file from local computer

jakarman — Thu, 16 Jul 2015 05:20:20 GMT

Tom, The "mounting" of a Windows environment into a Unix environment is technical possible with something like Samba (or part of those). The impact on the security approach is however getting you into nasty troubles. The reason is that basic concepts like LDAP and AD with Unix access controls do not match. That is why those tools are commonly banned for more secured environments.

Uploading files( binary) to Unix is rather easy and do not harm any of those environments.

Wanting to having a more direct interfaces and having access pc/files on Unix licensed you are free to use a "pc files-server" The IT guys that installed that all should be that business aware they have accepted that user request and did that installation. That is going along those guys understand the OS levels of both sides and the business. As there is already a problem seen on the OS level (home dir WS not set 50345 - Changing the current working directory for the SAS® Workspace Server) I am doubting on that.

Re: Cannot create library and read csv file from local computer

Ram4sas — Thu, 16 Jul 2015 17:54:12 GMT

Hi All,

Thank you very much and its very helpful to understand and resolve the issue which is round the systems lie UNIX and window and SAS lastly,.

Thanks,

Ram