Programms which run succesfully in Enterprise Guide run out of resources when ran via batch script

[AIS1]

Hi,

we have a recurring problem. Some moderatly complex code which runs succesfully when started via SAS Enterprise Guide fails to run when the same code is started as a batch script.

We have checked for the following things:

-There are no quotas

-We made sure that the config files for the batch user and the config files of the SAP Enterprise Guide user are functionally the same (batch user now has a config file in his home directory which gives him the same memsize, realmemsize etc. settings). We also verified that the config file added to the home directory gets processed using proc options. proc options also showed that there are no further config files which could override the settings

-We tried to reduce the log output as much as feasible by using

ODS _ALL_ CLOSE;

ODS exclude all;

Options NoNotes Nosymbolgen Nomprint;
before the critical code.

Unfortunately, we still run out of resources if the process is run via batch.

Any further ideas?

[andreas_lds]

Run proc options and compare results, there must be a difference in the configuration. I could also be helpful to post the exact error message you got.

[AIS1]

Failstate:

CONFIG=( /sas/sas_prog/9_4/SASFoundation/9.4/sasv9.cfg /sas/sas_prog/9_4/SASFoundation/9.4/nls/en/sasv9.cfg

/sas/sas_prog/9_4/SASFoundation/9.4/sasv9_local.cfg /home/aschmelz/sasv9.cfg )

Specifies the configuration file that is used when initializing or overriding the values of SAS system options.

ERROR: Insufficient space in file WORK.'SASTMP-000000006'n.UTILITY.

ERROR: File WORK.'SASTMP-000000006'n.UTILITY is damaged. I/O processing did not complete.

ERROR: There is not enough WORK disk space to store the results of an internal sorting phase.

ERROR: An error has occurred.

Succesfull run:

CONFIG=( /sas/sas_prog/9_4/SASFoundation/9.4/sasv9.cfg

/sas/sas_prog/9_4/SASFoundation/9.4/nls/en/sasv9.cfg

/sas/sas_prog/9_4/SASFoundation/9.4/sasv9_local.cfg

/sas/sas_prog/conf/Lev1/SASApp/sasv9.cfg

/sas/sas_prog/conf/Lev1/SASApp/sasv9_usermods.cfg

/sas/sas_prog/conf/Lev1/SASApp/WorkspaceServer/sasv9.cfg

/sas/sas_prog/conf/Lev1/SASApp/WorkspaceServer/sasv9_usermods.cfg )

 /home/aschmelz/sasv9.cfg  which is in the last one in the failed state is

/sas/sas_prog/conf/Lev1/SASApp/sasv9_usermods.cfg

/sas/sas_prog/conf/Lev1/SASApp/WorkspaceServer/sasv9.cfg

/sas/sas_prog/conf/Lev1/SASApp/WorkspaceServer/sasv9_usermods.cfg

(the three configs which are in the sucessfull but not in the non sucessfull state) taken together, in that order.

[Kurt_Bremser]

Use

/sas/sas_prog/conf/Lev1/SASApp/BatchServer/sasbatch.sh

to run your batch programs, and make sure that you run the batch under the same userid that runs the workspace server.

[AIS1]

Hi,

our /sas/sas_prog/conf/Lev1/SASApp/ folder does not have a batchserver subfolder.

Cheers,

Andrej