Server migration and disk connection problem

[Gieorgie]

Can you tell me that I understand well. Here he has a macro that refers to a server that was put on orcale, now we have a server from which we can connect locally. I cannot import any files because this server on oracle to which you can only connect remotely.

So now I have to write to my admin of the SAS that migrated this server to find out where this folder is located? How can I connect from my computer if the server is on UNIXIe.

/** file external connect
%include "&glb_path.\_global\*.sas";

/** links**/
%let path_lib = &glb_path.\02_libraries\ ;

WARNING: Physical file does not exist, /home/V1410190/&glb_path.\

ERROR: Cannot open %INCLUDE file &glb_path.\_global\*.sas.

[PaigeMiller]

WARNING: Physical file does not exist, /home/V1410190/&glb_path.\

The fact that this WARNING shows /home/V1410190 and then /&glb_path indicates it is looking on the remote machine (the server) for a folder named &glb_path, and it doesn't exist on the remote machine. Why? &glb_path is a folder on your local machine, not on the remote machine. The files you want in &glb_path must be uploaded to the remote machine (or perhaps on some remote machines you can make the local drive appear as a server drive, I don't know). You need to find out how to upload files from &glb_path to the remote server.

This is not something we can help with, because it is different in every company and every university. Your local staff or colleagues should be able to explain how to do this.

[Gieorgie]

Thanks !
I received information that this is the path and it is actually on the server

/sas/dev/data/users/V.../excel.xlsx

. However, when trying to connect

"% include" & glb_path. / Sas / dev / data / users / ";" I get such an error.

WARNING: Apparent symbolic reference GLB_PATH not resolved.
%include "&glb_path/sas/dev/data/users/V1410190";

WARNING: Physical file does not exist, /home/V1410190/&glb_path/sas/dev/data/users/V1410190.

ERROR: Cannot open %INCLUDE file &glb_path/sas/dev/data/users/V1410190

.

And i dont know why , Also, if I want to connect to this file, should I do it using import proc or select?

proc import out=polisy2
datafile="glb_path/sas/dev/data/users/V1410190/excel.xlsx"

[Sajid01]

The error message is clear. It is not able to resolve &glib_path.

You can try something like this

%let glb_path="The actual full path";

proc import out=polisy2
datafile="&glb_path./sas/dev/data/users/V1410190/excel.xlsx" ;

Include any other option you need in the proc import statement.

[ballardw]

---

@Gieorgie wrote:

Thanks !
I received information that this is the path and it is actually on the server

/sas/dev/data/users/V.../excel.xlsx

. However, when trying to connect

"% include" & glb_path. / Sas / dev / data / users / ";" I get such an error.

WARNING: Apparent symbolic reference GLB_PATH not resolved.
%include "&glb_path/sas/dev/data/users/V1410190";

WARNING: Physical file does not exist, /home/V1410190/&glb_path/sas/dev/data/users/V1410190.

ERROR: Cannot open %INCLUDE file &glb_path/sas/dev/data/users/V1410190

.

And i dont know why , Also, if I want to connect to this file, should I do it using import proc or select?

proc import out=polisy2
datafile="glb_path/sas/dev/data/users/V1410190/excel.xlsx"

---

If that is the code you actually submitted in this line:

"% include" & glb_path. / Sas / dev / data / users / ";" 

Is the leading quote part of your post as in this is the code is submitted within the quotes or did you actually submit that line?

The leading quote would case problems as you quote the Include, not the path.

I would expect errors. The Include must immediately follow the %, as in %include.

You have a gap between & and glb_path. So the macro variable is not referenced correctly. The spaces in the rest of the path around every folder name are also likely not actually in your system paths.

[Kurt_Bremser]

ALWAYS debug from the top down.

This is the most important message:

WARNING: Apparent symbolic reference GLB_PATH not resolved.

You need to make sure first that the macro variable GLB_PATH is defined correctly, and this most likely will fix the following issues.