Prev: Proc summary error:
Next: Retain and max() ??
From: Deepak Mathur on 2 Jun 2010 06:46
Hi Folks,

I would like to know if there is any way in EG 4.1 / SAS 9.1.3 to
disable a SAS user from defining their own libnames. We wish to
provide standard libnames, and not allow a SAS user to define their
own libraries.

Any help/workarounds for these would be useful.

Regards
Deepak
From: Steve James on 2 Jun 2010 14:20
On Jun 2, 6:46 am, Deepak Mathur <deepaksin...(a)gmail.com> wrote:
> Hi Folks,
>
> I would like to know if there is any way in EG 4.1 / SAS 9.1.3 to
> disable a SAS user from defining their own libnames. We wish to
> provide standard libnames, and not allow a SAS user to define their
> own libraries.
>
> Any help/workarounds for these would be useful.
>
> Regards
> Deepak

I'm not an EG-person, but in SAS I don't know anyway that you could do
that nor can I imagine that it's possible. There's no system option
NEWLIBNAME=ON/OFF switch. You can prevent people from creating
additional libraries by using operating system controls to prevent
them from creating a different folder. But in terms of how they refer
to a folder in their SAS code there isn't any way that I know of.

OK, I guess technically it's possible in a way but not easy. You
could theoretically insert code to run prior to each submissions of a
person's job and look at all the libnames that are defined and if
they're not in your pre-approved list you could then clear them, But
that's a lot of work just to keep people following coding standards.
There are far less drastic measures to do that.

Steve

From: Reeza on 2 Jun 2010 15:42
On Jun 2, 11:20 am, Steve James <s...(a)cdc.gov> wrote:
> On Jun 2, 6:46 am, Deepak Mathur <deepaksin...(a)gmail.com> wrote:
>
> > Hi Folks,
>
> > I would like to know if there is any way in EG 4.1 / SAS 9.1.3 to
> > disable a SAS user from defining their own libnames. We wish to
> > provide standard libnames, and not allow a SAS user to define their
> > own libraries.
>
> > Any help/workarounds for these would be useful.
>
> > Regards
> > Deepak
>
> I'm not an EG-person, but in SAS I don't know anyway that you could do
> that nor can I imagine that it's possible.  There's no system option
> NEWLIBNAME=ON/OFF switch.  You can prevent people from creating
> additional libraries by using operating system controls to prevent
> them from creating a different folder.  But in terms of how they refer
> to a folder in their SAS code there isn't any way that I know of.
>
> OK, I guess technically it's possible in a way but not easy.  You
> could theoretically insert code to run prior to each submissions of a
> person's job and look at all the libnames that are defined and if
> they're not in your pre-approved list you could then clear them, But
> that's a lot of work just to keep people following coding standards.
> There are far less drastic measures to do that.
>
> Steve

Why would you want that?

Doesn't that stifle the innovation of your staff, no room for
creativity or improvements?

As a programmer/SAS user that would frustrate me, because there would
probably be restrictions on where datasets could then be
saved...processes are good, enforcing them with absolutes are not.
From: Arthur Tabachneck on 2 Jun 2010 18:37
Deepak,

I don't use EG, thus can't give you a definitive answer. However, the
following implies that you can do what you want:

support.sas.com/techsup/technote/ts788.pdf

HTH,
Art
-------------
On Jun 2, 6:46 am, Deepak Mathur <deepaksin...(a)gmail.com> wrote:
> Hi Folks,
>
> I would like to know if there is any way in EG 4.1 / SAS 9.1.3 to
> disable a SAS user from defining their own libnames. We wish to
> provide standard libnames, and not allow a SAS user to define their
> own libraries.
>
> Any help/workarounds for these would be useful.
>
> Regards
> Deepak

From: xlr82sas on 20 Jun 2010 21:04
Hi Deepak,

I have talked to EG and DI-Studio administrators and they have
experienced issues when non-programmers lock up libraries or datasets.
They leave the SAS session open or don't understand the implications
of the generic libname engine.

For non-programmers a nasty solution might be to define and old
style macro, or a command macro, something like % libname * % or
%macro libname/cmd; * %mend. (untested code). Not sure of the syntax
or if SAS will let you do this. This macro would have to be avaialble
at the start of the EG session. The user command libname would be
executed instead of the generic libname command.

Your question just confirms my belief that EG is for non-
programmers. I would not do this to SAS programmers.

Regards
Roger

On Jun 2, 3:37 pm, Arthur Tabachneck <art...(a)netscape.net> wrote:
> Deepak,
>
> I don't use EG, thus can't give you a definitive answer.  However, the
> following implies that you can do what you want:
>
> support.sas.com/techsup/technote/ts788.pdf
>
> HTH,
> Art
> -------------
> On Jun 2, 6:46 am, Deepak Mathur <deepaksin...(a)gmail.com> wrote:
>
>
>
> > Hi Folks,
>
> > I would like to know if there is any way in EG 4.1 / SAS 9.1.3 to
> > disable a SAS user from defining their own libnames. We wish to
> > provide standard libnames, and not allow a SAS user to define their
> > own libraries.
>
> > Any help/workarounds for these would be useful.
>
> > Regards
> > Deepak- Hide quoted text -
>
> - Show quoted text -

 | 
Pages: 1
Prev: Proc summary error:
Next: Retain and max() ??