Here's a solution I came up with:   https://communities.sas.com/t5/Base-SAS-Programming/Clean-bak-files-from-PROC-EXPORT/m-p/395642#M95460   Is this what you wanted? ... View more

Your whole approach is likely to be problematic. Doing remote SUBMITs to multiple SAS sessions inside a macro means that you are spreading your macro logic across all those sessions and hoping it all synchronises OK, even though all of those "child" sessions are not aware they are embedded in a macro that is defined only in the primary SAS session.   A better approach would be to use the DATA step CALL EXECUTE to generate your required statements in open SAS code, rather than contained inside a SAS macro.  ... View more

Inside the macro, after the signon but before referenced to macrovar JOBNUM, you have to tell your sas/connect client to upload the macrovar to the host:   %syslput jobnum=&jobnum;   JOBNUM is a local macrovar in your client machine, but will be a global macrovar on the host. ... View more