Closed ShuguangSun closed 1 year ago
Hey, thanks for enhancing this! Appreciate the contribution. This seems like a good addition and I've been trying it out and it works well. Do you mind adding a comment/signature based upon the CONTRIBUTING.md in the root of the repo. I'll be happy to merge this in then.
Also, just another way you have to implement autoexec functionality from the client side is to use that keyword in your config. That works for both saspy in any python as well as for this script. In the simplest way you could do this (course you could write a few lines of code and open, read into a variable, close then pass in the variable). Just FYI:
auto = {'java' : '/usr/bin/java',
'authkey' : 'saspy1',
'iomhost' : 'tom64-7',
'iomport' : 8591,
'autoexec' : open('autoexec.sas').read()
}
Now add the signed-off.
Thanks for the tips.
Awesome, thanks again!
This PR makes run_sas.py accpect more than one SAS file, e.g.,
./run_sas.py -s example_1.sas example_2.sas
./run_sas.py -s autoexec.sas example_2.sas
saspy or run_sas doesn't honor
autoexec.sas
automatically which is different with SAS V9 in batch mode. Our projects useautoexec.sas
and a project level setting SAS file to manange project settings. We have to using%include
in each file if we callrun_sas
. It makes the code complicated and%include
can't includes the remote file which might not be the updated one.In case we are using IOM with Workspace server (for example, SAS EG), after the PR,
run_sas
can source local copy files which is different to%inclue
which source the one the server.It makes the
run_sas
a kind workable solution using in the task in vscode.