01-03-2013 11:37 AM
Can anybody help this?
The scenario is this:
XCMD is disabled, no way to use shell command,
We need check the status (running, complete, failed...) of a scheduled job inside another SAS program.
Thanks in advance,
01-06-2013 10:22 PM
How is the SAS program scheduled? What operating system is it being run on? Often the job scheduler will show you this type of information. For example the LSF scheduler that comes bundled with SAS BI Server shows you the job status.
01-07-2013 09:22 AM
The program is scheduled inside LSF scheduler. The OS is SUN Solaris.
We need check the status of a scheduled job inside another SAS program.
01-07-2013 01:59 AM
HI if you are using the LSF you can check the log up to what extend the code was writen for example as you are scheduling another job in the sas job when the inside job reach that code it will write the onfo in the log just check it.
01-07-2013 10:19 AM
You could get the program that is running on a schedule to write some sort of log entries to a SAS dataset and then read from that to determine whether the process worked or not?
We have a macro that is stored on the server to create a record in a log table when a process starts and then update the record with an end date and success/fail message when it finishes.
Alternatively, even with xcmd turned off you should be able to use some combination of DOPEN/FOPEN/FINFO to look at the last modified dates on the lsf log files or to read in the log files to search for completion messages.
01-07-2013 04:07 PM
XCMD might be disabled when running your job out of DIS (session created using object spawner). But when running the job in batch (like done via LSF) then the setting is very likely XCMD - else you can set it yourself by passing -XCMD as start option.
I personally believe that for DIS development XCMD should be set. There was some time ago some rational posted which can be used to discuss this within an organisation - but I just can't find this thread anymore.
01-07-2013 02:42 PM
If you have used DIS to create the job you can get it to create a status file/dataset (easy point and click), your other job can then check for that file and it's contents