BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
JuanDaniel
Quartz | Level 8
Hi!

I have a doubt. Can i create a user in SCM and this user can be used by 3 persons at time?

I think is better a user for each person, but what happen with the WORK library in the case that 1 user is used by 3 persons?

Has SAS something similar to a central reposity where the users can block objetcs like projects to work in it and then publish the changes that the user have made? with this method of work the others users can not make changes over the project until that the project have been published.
1 ACCEPTED SOLUTION

Accepted Solutions
Damo
SAS Employee

Hi @JuanDaniel

 

You can certainly shared an account but as you mentioned, each user having its own account is the way to go.

When it comes to the WORK library, it will be assigned to the session and not shared by your three users (if they use the same account).

 

For your last question, there isn't a way to achieve what you want but versioning might be what you're looking for. Might.

If you have questions about versioning, many if not all will be answered with Paper 179 - 2014 Check It Out! Versioning in SAS® Enterprise Guide®.

 

Hope that helps.

 

Cheers,
Damo

View solution in original post

3 REPLIES 3
Damo
SAS Employee

Hi @JuanDaniel

 

You can certainly shared an account but as you mentioned, each user having its own account is the way to go.

When it comes to the WORK library, it will be assigned to the session and not shared by your three users (if they use the same account).

 

For your last question, there isn't a way to achieve what you want but versioning might be what you're looking for. Might.

If you have questions about versioning, many if not all will be answered with Paper 179 - 2014 Check It Out! Versioning in SAS® Enterprise Guide®.

 

Hope that helps.

 

Cheers,
Damo

JuanDaniel
Quartz | Level 8

Thx for your help @Damo 

Kurt_Bremser
Super User

Version control with a central repository and check-out/check-in functionality works on text files, which EG projects are not.

EG projects are compressed archives of several types of objects, and that prevents a versioning system from detecting the changes and keeping the diff's, so for future refence a specific version can be recreated.

So the way to go (IMO) is to finalize each development into Base SAS code, and check that in to the repository.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 800 views
  • 2 likes
  • 3 in conversation