What makes the decision to launch those SAS processes?
A long time ago (forget galaxy ...) I wrote a routine that would launch SAS programs based on a trigger = "that a file exists".
My routine was a SAS task that watched and tested for the trigger file with fileexist( 'trigger file name') which is FALSE (0) until that file exists. Once TRUE, it used the X-statement to launch the SAS programs because they were to run independantly. Another trigger was needed to stop the "watching" task. That watcher process could have been set up as a windows service.
I think a proper scheduler should be able to do that in a much more supportable way ;-)