Macro to include all .sas file from a folder

[Reeza]

And the Z drive is where? That path looks like a Windows path not Unix path.

[RAVI2000]

The folder is a shared folder which we have to map manually. Once I map it then only I am able to access it.

[Reeza]

From your unix system? Show me a unix command that shows this path is correct via echo.

[Tom]

---

@RAVI2000 wrote:
The folder is a shared folder which we have to map manually. Once I map it then only I am able to access it.

---

On unix you don't "map" disks, you "mount" them.  And individual users do not have permission to mount disk, just the system administrators.

On Unix the whole file systems looks like on giant tree starting with the root node ( / ).  Individual shared disks or folders are mounted to subdirectories in that tree.  

So if on Windows you use something like:

net use Z: \\hostname\sharename

to "map" the shared folder to the Z virtual drive letter.

On Unix someone would mount that share at some directory path. perhaps something like:

/usr/local/hostname/sharename

[Kurt_Bremser]

Z\:

is incorrect syntax. The colon has to immediately follow the drive letter:

Z:\

[RAVI2000]

Thank you for the input Kurt! But if you observe my log, I have given it correctly. But SAS is reading it like this Z\:

How can I correct it?

[Kurt_Bremser]

From a later post of yours I see you are using SAS on UNIX, so

dir /s /b

can't work at all.

dir has to be a shell script or an alias mimicking the DOS command, but it does not "understand" the same options or the same syntax. And there will not be a Z: drive on UNIX ever, as these systems do not have the concept of drives, they have a single filesystem starting at root (/) where all resources need to be mounted.

So I guess the re-ordering of the characters is a consequence of the mistaken use of a Windows path.

[Ksharp]

Post your log.
And in log should display all these .sas filename .

P.S Assuming your PIPE could be execute under SAS.