Desktop productivity for business analysts and programmers

Can same libref in two different environments work?

Reply
N/A
Posts: 0

Can same libref in two different environments work?

We are using lev 1 for development and lev 2 for QA.(Both the levels are on the same server/ machine). I am having a sas libraray in both the environments pointing to different locations with same libref.
For eg: In Lev1: libname x 'D:\abc";
In Lev2: libname x 'D:\QA\abc";

This is creating a problem. When both the levs are up and running then both the librefs are pointing to the path 'D:\QA\abc".

This problem is valid if we have same libref pointing to different paths in the SAME environment. But here we have two diff environments. So is there a way we can avoid this?

(Currently we have changed the name of libref in lev2 - QA to avoid problems.)
Esteemed Advisor
Posts: 5,198

Re: Can same libref in two different environments work?

I don't understand how you have configured your two environments?
Where have you defined the search paths? How are your libnames assigned?
There should not be problem if done this right. In fact, having different search paths is one benefit of using different metadata levels.

/Linus
Data never sleeps
N/A
Posts: 0

Re: Can same libref in two different environments work?

I have given the libname statements in the autoexec files.

For eg:
libname x 'D:\abc'; in autoexec file present in lev1 environment's application workspace server

libname x 'D:\qa\abc'; in autoexec file present in lev2 environment's application workspace server

Is it incorrect?
Esteemed Advisor
Posts: 5,198

Re: Can same libref in two different environments work?

Looks ok.
Be sure that the "Library is pre-assigned" check-box is marked for this library in both environments. And of corse that they are named X.
If this is still not working, attach a LOG.

/Linus
Data never sleeps
Ask a Question
Discussion stats
  • 3 replies
  • 89 views
  • 0 likes
  • 2 in conversation