SAS IT Resource Management uses the ADMIN library of each IT data mart to generate both job code and status information for data duplication controls that are used by staging transformations. If you have only one ADMIN library, contention issues could arise if multiple staging jobs are executing concurrently or if multiple jobs are being generated in the same IT data mart. Therefore, when you attempt to generate code for a SAS IT Resource Management job in SAS Data Integration Studio, you might receive the following error message:

Cannot generate code to prefix.ADMIN location because previously submitted job is still running on this location. You can submit/generate code for this job once the prior job execution is complete.

where prefix is the root directory path or the high-level qualifier for the data mart you are working with.

It is also possible to receive this message if you do not have write access to the ADMIN library, if you have run out of space in the ADMIN library or directory, if the ADMIN library is damaged, or if there is a hanging UNIX System Services process.

To avoid this conflict and error, do not attempt to generate code when staging jobs are executing. Also verify that you have write access to the ADMIN library, verify that you have enough disk space allocated to the ADMIN SAS library, and check to see if there is a hanging UNIX System Services process.

You might also see this error message when SAS Data Integration Studio is unable to access the ADMIN library. Possible causes include not having the appropriate permissions on the physical library, the ADMIN library having no more available space, or a damaged catalog within the ADMIN library.

The following process tests for some of these conditions in SAS Data Integration Studio:

1. Select Tools ► Source Editor from the Menu bar to open a Source Editor window.
2. Select Tools ► Options from the Menu bar and ensure that the Show Output Tab in the Source Editor check box is checked.
3. In the Custom tab, navigate to the Admin library in the Libraries folder of the data mart in which you are experiencing the problem.
4. Right-click that Admin library and select Display Libname.
5. Highlight the complete statement, right-click, and select Copy to copy that statement to your PC clipboard.
6. Right-click in the open Source Editor window and select Paste.
7. Run the following code (with your own LIBNAME statement):

      *your admin libname statement goes here; 
   
      * this tests that the user can write to the ADMIN library;  
      data admin.test;  
          x=1; 
      run; 
       
      * this verifies that the library exists and is not damaged; 
      proc contents data=admin._all_;  run;  
   
   

   Check the log and output tabs for error messages that might indicate why you cannot write to the ADMIN library.

Operating System and Release Information

A fix for this issue for SAS IT Resource Management 3.1.1 is available at: