From: Atar Baer on
Two SAS programs that have been running without errors for months have
been choking recently with "generic critical error" messages. I
discovered that when I run these programs interactively in SAS
everything works fine, but when I run these same programs in batch
mode (e.g., when the Task Scheduler initiates SAS to run the code),
there is a failure with a generic critical error. Furthermore, if I
start a SAS session and keep it active as a window (but without
running anything in it), and then run my code in batch mode,
everything works fine, but if there is no active SAS session in the
background, the program fails to run in batch.

Has anyone run into this issue, or have suggestions for fixing it so
that I don't have to keep a SAS session running in the background?
From: Arthur Tabachneck on
Atar,

I have a couple of questions.

1. What version of SAS are you using and on what operating system.
2. When you submit the batch job is it submitted to your machine or to a
server? If its a server which version of SAS is it running and on what
operating system?

I ask because the same problem has been mentioned before when the code
called for something that was licensed on the local machine, but not the
server.

Art
---------
On Thu, 10 Dec 2009 12:59:08 -0800, Atar Baer <atarbaer(a)GMAIL.COM> wrote:

>Two SAS programs that have been running without errors for months have
>been choking recently with "generic critical error" messages. I
>discovered that when I run these programs interactively in SAS
>everything works fine, but when I run these same programs in batch
>mode (e.g., when the Task Scheduler initiates SAS to run the code),
>there is a failure with a generic critical error. Furthermore, if I
>start a SAS session and keep it active as a window (but without
>running anything in it), and then run my code in batch mode,
>everything works fine, but if there is no active SAS session in the
>background, the program fails to run in batch.
>
>Has anyone run into this issue, or have suggestions for fixing it so
>that I don't have to keep a SAS session running in the background?