Hi @jurlis   I think the difference in behaviour is due to the FMTERR System Option. With SAS Enterprise Guide (EG), the option is set to NOFMTERR while in batch you may have FMTERR. You can compare the two values by running: proc options option=fmterr; run; I'm guessing that with EG, if you change the value to FMTERR you'll have the same result as you have in batch. So if you set NOFMTERR in batch, you should not have the error and the result should be the same as the one you have with EG.   Hope that helps. Cheers, Damo   ... View more

Thanks for your reply. We aren't working in a GRID-setup. 1 Solaris server executes all SAS-tasks.   * In folder "/sas/prd/data/DIR_III_4" -> startfolder of this Workspace Server lrwxrwxrwx 1 sasdir34 sastusers 25 Nov 26 2012 SHARE_INVORDERING -> /sas/prd/data/invordering * In folder "/sas/prd/data" : lrwxrwxrwx 1 root root 23 Nov 20 2012 invordering -> /nfs_mounts/invordering * In file "/etc/vfstab" : prod2.drsns02.finbel.intra:/landing_invordering - /nfs_mounts/invordering nfs - yes nodevices,vers=3,xattr,zone=zdmsrvp01,sharez one=7 -> symlink (absolute path) is on a different disk (available via nfs) -> these disks are mounted since creating files/writing to the disks via SAS is possible via proc export data=JLSSET3 outfile="/sas/prd/data/DIR_III_4/SHARE_INVORDERING/OUTPUT/JLSSET3.xlsx" dbms=xlsx replace; run; -> writing through a DATA-step on this folder doesn't work ... View more