Hello,   we have a rather unusual situation.   We have a process that regularly does updates and inserts on a given data_table (which is a 7bdat file). Our inserts fail because the batch user does not have permissions on the data_table.index .   Actual message: ERROR: User does not have appropriate authorization level for file SAS_OUT.PON_BCS.INDEX. NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements. (Bold by me)   In the past, similar errors could be fixed by giving write right on the specific table to the batch user (and it indeed makes sense that it would not work without those rights being given).   The batch user that does these updates does have R/W and even X permissions on the table SAS_OUT.PON_BCS . I cannot find a sas_out.PON_BCS.INDEX File.   The datafile does indeed have several indizes on it, and those will be neccessary for performance.     ... View more

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? ... View more

Hello,   we have a relatively weird problem. Using SAS Enterprise Guide 7.1 and SAS 9.4.   We have a datamart, which we used to rebuild daily using an automated process called "build_data_mart". This script worked fine for a long time, but suddenly stopped being succesfull about a week ago. Whenever this script is run automatically, it runs into the following error in the appropriate log files: File WORK.'SASTMP-000000028'n.UTILITY is damaged. I/O processing did not complete It also runs into this error at effectively the same step. When I activate the script via putty, I receive the following message: OUT OF RESOURCES  Select:   R. Retry   N. Tell procedure/DATA step no more resources.   C. Cancel Submitted Statements   T. Terminate SAS. ? Retry does nothing, if I cancel, the resulting log does not show an error but ends in the same spot of the SQL code.   Interestingly enough, if I execute the process via the Enterprise Guide, it runs without any problems whatsorever.   There are ample amounts of disc space available in the work directory, the same appears to be true for physical memory. We have also verified that there is not quota allocation. The step at which it fails is nothing particularly serious. The resulting table has, if it is run via Enterprise Guide, 28 columns (yes, we kind of need them) and some 489K observations, resulting in 282 pages compressed and 783 pages uncompressed. While not neglible, this is not a terribly large table, other tables the script creates before are larger.   Questions: Is there a way to find out with which options SAS Enterprise guide runs the script? How can I replicate these options for the batch script?   ... View more