This is within EG 4.2. I am trying to move a large SAS dataset on a SAS EG server into a pipe delimited text file and move this text file to a Windows network drive. Need to know how this can be accomplished. Have already tried several methods, but no luck so far.
I suggest you explore FTP (File Transfer Protocol) as a way of moving your files from Unix to Windows. FTP is built into both operating systems and you can get SAS to do the FTP for you using a FILENAME statement with the FTP option.
The first thing you will need to check out is can you logon to your Windows network from your Unix server. Since you haven't worked with Unix before I suggest you get help from other Unix users at your site to confirm you can do this. From a Unix command line you can test a Windows connection by typing ftp then type open . It will then prompt you for a userid and password.
I cannot "open" the Windows server from the Unix command line. Being told "A remote host refused an attempted connect operation." I have access to a folder on this Windows server. Wondering why I cannot open. Any idea?
Try to ping the Windows server from the Unix command line: ping . If this doesn't work then your Unix server cannot identify your Windows server. This is a job for your IT network administrators to solve, not you. From the message you quote I suspect ping will work.
If you can successfully ping then the Windows server is blocking your FTP logon request and you need to get a Windows administrator to enable FTP remote logins to that server. Many organisations tightly control this so I am not surprised it is blocked by default.
The samba approach works fine, but does require that the UNIX admin set it up. It also is much easier if the UNIX box and the windows network are on the same subnet. A samba limitation is that the end-of-line character on UNIX is different from the end-of-line characters on the PC, so some Windows programs (like NotePad) get confused.
One technique that I have used is to create the file in UNIX and store it and then run an ftp session from the Windows workstation to bring the file over to Windows. Windows IT admins often "turn off" incoming FTP, so you can only "get" things and not "put" things. For repeated production activities, I will use the cron on UNIX to run the SAS job to create the file and scheduled tasks on windows for a .BAT file to execute the ftp session.