Hi:
If you search in the EG topic for "Error using PIPE to create directory", you will find this explanation from somebody in SAS R&D who works with EG:
"PIPE, SYSTASK and XCMD are among the features disabled by default when running a SAS server configured with SAS Integration Technologies. These features can present a risk to use on a central server that is accessed by lots of users with Enterprise Guide.
By default, the Object Spawner starts the SAS session with the -NOXCMD option which does not allow SYSTASK commands to be run.
I'd suggest opening a track with tech support and explaining your situation; they can advise you as to the best workaround for what you're trying to do."
You are in a slightly different situation, but it seems that issuing X commands or PIPEs is not going to get you the ability to read your local data.
Imagine this scenario -- you have Excel data on your personal machine stored in the directory: C:\mydata\wombat.xls
BUT, the stored process server and the workspace server are probably out on the network someplace and they may not even be on Windows machines. So the "C:\mydata drive address" method won't work. You will probably have to use some kind of machine name addressing, such as:
\\machine\sharename\dirname\filename.ext in your filename or libname statement: \\PC4343\public\mydata\wombat.xls
If you use SAS Data Integration Studio, you can define these source tables in the metadata so they are available for subsequent use. DIStudio will build the appropriate filename/libname statements for you. If you do not have DIStudio, then your best bet is still to contact SAS Tech Support for help in figuring out the correct way to reference these files from within EG in a server environment.
cynthia