05-31-2012 12:45 PM
We are having a problem (not limited to one user ) with creating permanent datasets using EG.
We could still create permanent datasets using PC SAS and doing a RSubmit or using Putty to submit code in a non interactive mode.
The issue pops up when we start to use EG.
Here is a simple code that replicates the error:
libname test '/sas/products/dev ';
ERROR: Rename of temporary member for TEST.ABCD.DATA failed.
Basically the file gets created but has .lck extension next to it and the rename from ABCD.sas7bdat.lck to ABCD.sas7bdat fails..
We have checked the permissions on unix and at the file system and they seem to be fine as the user is able to create the datasets using Remote submission of code and Non interactive mode.
The space on the file system is also ample .
Can someone point if there is anything else that we need forgot to check.
The whole thing started after a planned reboot of the SAS server.
Here are some of the threads that we have gone through, but didn't relate to our problem.
05-31-2012 01:12 PM
Sounds like a problem we had on an old Novell network. They had granted us Write and Create permission, but we did not have permission to Delete files.
When SAS creates a dataset it first creates it with a different name and then renames it.
When SAS recreates a dataset it waits till it has created the file with the different name first before it deletes the original and then renames the file it just created.
05-31-2012 01:33 PM
Thanks Tom,for the reply.
We are able to create datasets using PC SAS but not with EG.
Is there something different that's going on the server when we use EG rather than PC/SAS?
05-31-2012 01:51 PM
It normally runs with a different account, so that account might have different permissions than the individual users.
I have no idea about that type of administrative detail, but SAS support can definitely help.
05-31-2012 03:11 PM
Can some SAS Administrative gurus comment on which accounts (if present by default on the SAS server) are used by EG to write/delete/rename the datasets and how to view the permissions associated with those accounts , so that I could forward that information to our support guys here.