Thanks! I know it's not perfect to check key words like ERROR or WARNING in SAS log. However, it provides a solution for us to notify operators that something should be paid attention to. I know for each .sas program running, operator should at least take a look at the details of SAS log file.  ... View more

Thanks for the comments! Excellent explanation!  Would SASpy also provide another flag like? check_warning_log Thus, if either of check_warning_log or check_error_log is true,  user can consider that the SAS program is not run smoothly.  From my perspective, we use Automation tool to schedule the .sas programs which are written by others. It's not easy to change the existing .sas program files to add additional checks on each data step. ... View more

Thanks! I agree with you. For automatica SAS job scheduling, if there are ERRORs or WARNINGs in the sas log file, it should report the job is failed to notify user something wrong there. ... View more

Thanks!  I agree with you. If one WARNING message indicates a logic error problem, we can think it's an error. But if that WARNING is an error, why not report it as ERROR directly. There should be some cases of WARNING which are not errors. How do we distinguish them during automatic scheduling jobs? ... View more

Thanks! Use SYSERR macro is helpful if SAS or user defined procedures or steps write return code to syserr. From my understanding, it not as useful as checking ERROR in SAS log file. ... View more

Thanks! This enhancement is convenient for us to catch ERROR through SASpy.  Only check_error_log  method is called to verified. User doesn't need to check log file himself. As the document points out, there is no perfect solution to know whether it's a real problem there. From automatic SAS job scheduling perspective,  if we find there is ERROR in log file, no matter it's checked through check_error_log or ourselves, we can just report that scheduling job failed and let user to verify in further steps.  ... View more

Thanks for your comments! I think it's better to search "ERROR" in latest SAS log file. However I don't know whether the WARNING message is really error. ... View more

Thanks! It is non-grid SAS server running on Windows platform. ... View more

I think the problem is related to SSH connection. If using admin/password authentication, the scripts can be executed successfully.  But non-admin can't even though it can run the scripts in local command prompt. ... View more

Thanks! I think it's a good idea of using CoPilot to generate Powershell based on VBscript. I will try it in future. I agree with you that Scheduler has nothing to do with VBscript. But when using OpenSSH to connect the two things, something may be different, especially one side is on Windows system.  ... View more

Thanks! We previously use Windows Task Scheduler to schedule many VBscript files.  There are some limitations on using Windows Task Scheduler. So we decide to switch to Airflow. However, SAS programmers don't want to change the existing VBscrit files.   ... View more

Thanks for your reply! The VBscript is on the remote machine. In fact, per my understanding, when login on through OpenSSH, it uses a network login on session, it is different from the local login on session. But I don't know the real difference between them, especially for calling applications like SAS EG. ... View more

Thanks! In theory, it should be ok to use exteral scheduling. However, in the VBscript, if it calls  application like Excel which may run in Desktop sesstion, the OpenSSH protocol may not be suitable. ... View more

Thanks for your reply! Yes, I know the difference between 32 bits and 64 bits. I use this one because we run 32 SAS EG on 64 machine. c:\Windows\SysWOW64\cscript.exe c:\projects\AutomationNewProgram.vbs  The problem is that this command can run successuflly on command prompt locally.   I see other comments in this communities and some people suggested to run the following two commands: 1. C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /tlb:SASEGScripting.tlb /codebase "C:\SASHome\x86\SASEnterpriseGuide\5.1\SASEGScripting.dll" 2. C:\SASHome\x86\Integration Technologies\RegTypeLib.exe  C:\SASHome\x86\SASEnterpriseGuide\5.1\SASEGScripting.tlb   I just wonder that whether these two commands are useful and safe to fix the problem. Our system is running in production. I can't try any command before I conclude that it's safe. ... View more