In reply to Chris Hemedinger.

Thanks Chris!

That's exactly what I was thinking. Too many hops and programs running elsewhere. Is it all possible to capture that the RSubmit sessions have been spun up and signed off? Just wondering since info is written to the log regarding the sign on and off from the remote sessions. If it was somehow possible to capture those events and display it in the Task Status window that would at least provide some feedback regarding these programs? Does that make sense? I'm using some code and macros from Doug Haigh's paper "Divide and Conquer - Writing Parallel SAS Code To Speed Up Your SAS Program" (SAS1935-2015). As part of the code and macros in the paper you create a bunch of variables related to each session being spun up so was curious if there is some way to possibly leverage those variables or the info being written back to the log in the Task Status. Even this would be really helpful when it comes to knowing what's going on with my programs that are running.

Here are some of the example notes in the log:
NOTE: Remote signon to MYSESS4 commencing (SAS Release 9.04.01M1P120413).
NOTE: Remote signon to MYSESS4 complete.
NOTE: Background remote submit to MYSESS4 in progress.
NOTE: Remote submit to MYSESS4 commencing.
NOTE: Remote submit to MYSESS4 complete.
NOTE: Remote signoff from MYSESS4 commencing.
NOTE: Remote signoff from MYSESS4 complete.

Thanks,
-Andrew