The solution is here:
Edit:
I didn't remember it was a longer thread. Sorry...
The solution is to edit your "E:\SAS\Config\Lev1\SASApp\BatchServer\sasbatch.bat" and remove the REM-statements in the end of the script...
/Christian
If you right click on the job in Flow Manager, you should see an option to view runtime attributes, which should include the log file for that particular job. Typically it should be under <config>\Lev1\SASApp\BatchServer\Logs (depending on how your environment is configured).
Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF
View now: on-demand content for SAS users
The solution is here:
Edit:
I didn't remember it was a longer thread. Sorry...
The solution is to edit your "E:\SAS\Config\Lev1\SASApp\BatchServer\sasbatch.bat" and remove the REM-statements in the end of the script...
/Christian
Hi,
Are you sure the first job is finishing with the right exit code? Does it turn blue in Flow Manager?
As Christian suggests, you might need to uncomment the last 5 lines of sasbatch.sh to allow SAS jobs that complete with warnings to return an exit code of zero. Some more info on this can be found at https://support.sas.com/rnd/scalability/grid/platformfaq.html
Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF
View now: on-demand content for SAS users
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.