topic Re: LSF warnings issue in SAS Data Management

LSF warnings issue

chirumalla — Tue, 21 Oct 2014 06:42:26 GMT

Hi,

My SAS scripts generating some warning messages. when I run this scripts in LSF warnings consider as a errors and jobs become red and exit the flow. is any option or method to suppress/ignore warnings in LSF scheduler.

Re: LSF warnings issue

Kurt_Bremser — Tue, 21 Oct 2014 06:57:13 GMT

I STRONGLY advise to make any SAS batch program completely free of warnings before running it with a scheduler. That way, when an exit code <> 0 is encountered, you can be sure that something unexpected happened. Ignoring WARNINGs will lead to undetected errors, sooner or later, and is BAD practice.

Re: LSF warnings issue

chirumalla — Tue, 21 Oct 2014 07:06:02 GMT

Yes I agree, but am automating client existing scripts I don't have authorization to modify/edit. pls advise me if any way to overcome this issue.

Re: LSF warnings issue

LinusH — Tue, 21 Oct 2014 07:20:22 GMT

Sounds like you have a system maintenance process issue, rather than a technical one.

Just contact the responsible for the SAS jobs and have them correct the warnings.

I shouldn't say this, but SAS configuration is prepared for this, check out the comment in ..\BatchServer\sasbatch.bat/sh.

Re: LSF warnings issue

jakarman — Tue, 21 Oct 2014 07:30:09 GMT

You cannot overcome this without a good description coming in from your client how to handle all conditions. When there is something getting into contradictions with some code that must also get decided&described.

A pitty as you cannot answer always "yes" to them on forehand.

Some info:

SAS(R) 9.4 Language Reference: Concepts, Fourth Edition Handling error codes.

SAS(R) 9.4 Companion for UNIX Environments, Fourth Edition syscc see notes on recognizing errors they can be changed (not stable).

SAS(R) 9.4 Companion for Windows, Third Edition syscc has no documented vaules SAS(R) 9.3 Macro Language: Reference And at this one the value of 4 (normal to mainframe) is mentioned.

Batch processing (like LSF) was common to mainframes having a well defined CC. At Windows it got the focus on pc-desktop usage not batch.

Re: LSF warnings issue

Kurt_Bremser — Tue, 21 Oct 2014 07:42:13 GMT

Use a LART on the "clients".

(LART = Luser Attitude Readjustment Tool, in the US aka baseball bat)

Simply reject any SAS program that does not terminate with exit code 0 at successful execution. Or obtain the authorization to modify the codes and do the work yourself. (That is what I do when being handed user's SAS codes to run in batch. I optimize/correct the code until it exits with 0, and run a proc compare on the results of the altered and original code before handing the job off to the datacenter people).

BTW, not only do we flag an exit code <> 0 as error, I have actually an expanded version of error checking in our sasbatch (that predates the sasbatch in SAS' own Batchserver by about 10 years) where I artificially generate non-zero exit codes if I encounter certain phrases/words in the log file.