For the SAS/Base language I know the issues well  with all quutin issues SAS(R) 9.4 Macro Language: Reference See the different meanings of special chars. Al lot of work when they are involved and needing bypasses. The difference between single and double quotes for strings can be very important. There is somewhere interference of symbols You did not show the command (put statement) in full glory or other debugging action. The usage of this as SCL function or as modified (submit block) SAS-base processing I am also not seeing...  The SAS-base is probably easier to debug focus on the quoting remarks. ... View more

sudharsanam, That explains a lot.   The servername you are referring is not one like the hostname of the machine it is a logical SAS name the user has to give when doing the connection. It has the same naming conventions as the libname statement. With async processing you can have a lot them all running at the same moment. Could become as stressing situation for one taking care of the server. In that case it would make much sense to have you sas-admin a global defined table in the sasautos / autoexec. As long you are working with the last connected session you have sas macro-variable containing that session name. It is easy to find with %put _all_ ;  (do not remember the exact name could be comething like remoteid) It is the same approach as some connect statements not needing the servername as long it is the last session. As you are telling proc download is slow, you have more troubles to solve as that one should be fast. It can only be slow by bad network or not optimized SAS settings (small buffers being resized). The remote libname is easy to show the remote structure, to combine some data. The datatransfer rate is the same or lower as proc download.    ... View more

and the listtask information? (also documented with SAS/connect) as is waitfor. ... View more

SAS(R) Component Language 9.3: Reference (submit terminate) is documented to be used with caution. SAS(R) Component Language 9.3: Reference (error handeling) is quite an other concept. SAS(R) Component Language 9.3: Reference (stop) is the normal way to halt your AF program The init main term sections have special meanings with AF (SCL).   When you  give the terminate action running SAS statements (outside AF) there can be a problem AF wants to continue wiht the next (term) section. By that you will see a hanging or even looping system. I have seen this kind of errors with AF Macro-language and SAS/connect. As timing and event-triggering are that important it is very difficult to pinpoint and explain the issue/error. More easy is to bypass it with a more reliable logical construct. ... View more

You seem to have mixed macro and data step logic there. In a data step you can call the PATHNAME() function directly. data _null_;   path = pathname('sashelp');   put path=; run; In macro code you can call the PATHNAME() function using %SYSFUNC(). %put path=%sysfunc(pathname(sashelp)); ... View more