Date: Mon, 13 Apr 2009 14:48:17 -0700
Reply-To: jfh@stanfordalumni.org
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Subject: Re: Store programs: who uses them?
In-Reply-To: <OFF5234719.8E003413-ON85257594.004CB489-85257597.00760225@dom.com>
Content-Type: text/plain; charset="ISO-8859-1"
We use them to make sure that only users in a security list are allowed
to read confidential data fields from a data set. It adds some
complexity and increases the execution of the program, but it's the only
way we could find to create a flexible security mechanism.
On Mon, 13 Apr 2009 17:28:54 -0400, "Nat Wooding"
<Nathaniel.Wooding@DOM.COM> said:
> The thread was getting rather far afield so it seemed a good time to
> change
> the title.
>
> Can anyone share experiences with the usefullness of stored programs?
>
>
> I do see the paper
>
> http://www.nesug.org/proceedings/nesug07/ap/ap22.pdf by Cynthia
> Zender
>
> and I'm pretty sure that I have heard Ed Heatone speak on the topic
> (sorry
> Ed, I must not have had enough coffee that day).
>
>
>
> Nat Wooding
> Environmental Specialist III
> Dominion, Environmental Biology
> 4111 Castlewood Rd
> Richmond, VA 23234
> Phone:804-271-5313, Fax: 804-271-2977
>
>
>
> "./ ADD NAME=Data
> _null_;"
> <iebupdte@GMAIL.C
> To
> OM> SAS-L@LISTSERV.UGA.EDU
> Sent by: "SAS(r)
> cc
> Discussion"
> <SAS-L@LISTSERV.U
> Subject
> GA.EDU> Re: run and quit after libname
>
>
> 04/10/2009 08:38
> AM
>
>
> Please respond to
> "./ ADD NAME=Data
> _null_;"
> <iebupdte@GMAIL.C
> OM>
>
>
>
>
>
>
> My programs are obsolete as soon as they're written, so I don't use
> stored programs either.
>
> I've written a couple to see if I could used them similar to macros,
> that can be achieved for the simple cases I have explored.
>
> I would be interested to hear from those who do use them often.
>
> On 4/10/09, Nat Wooding <Nathaniel.Wooding@dom.com> wrote:
> > ./ Add
> >
> > Interesting. While I have at least heard of stored programs, I have never
> > found the need to learn to use them.
> >
> > Nat
> >
> > Nat Wooding
> > Environmental Specialist III
> > Dominion, Environmental Biology
> > 4111 Castlewood Rd
> > Richmond, VA 23234
> > Phone:804-271-5313, Fax: 804-271-2977
> >
> >
> >
> > "./ ADD NAME=Data
> > _null_;"
> > <iebupdte@GMAIL.C To
> > OM> SAS-L@LISTSERV.UGA.EDU
> > Sent by: "SAS(r) cc
> > Discussion"
> > <SAS-L@LISTSERV.U Subject
> > GA.EDU> Re: run and quit after libname
> >
> >
> > 04/10/2009 07:49
> > AM
> >
> >
> > Please respond to
> > "./ ADD NAME=Data
> > _null_;"
> > <iebupdte@GMAIL.C
> > OM>
> >
> >
> >
> >
> >
> >
> > Old syntax.
> >
> > 41 data _null_;
> > 42 do _n_ = 1 to 10;
> > 43 Put 'NOTE: ' _n_=;
> > 44 end;
> > 45 run pgm=work.nat;
> > NOTE: The STORED PROGRAM creation syntax on the RUN or DATALINES
> > statement will not be supported
> > after this release. Please specify the STORED PROGRAM definition
> > on the DATA statement as
> > per the new syntax described in the current documentation.
> >
> >
> > On 4/10/09, Nat Wooding <Nathaniel.Wooding@dom.com> wrote:
> > > I happen to have a V5 basics manual at hand. The Quit statement did not
> > > exist then but there was a Quit option for the Run statement that
> appears
> > > to have been equivalent to a Cancel. I just checked and the Run Quit
> is
> > no
> > > longer allowed but, oddly enough, I see that Run PGM= is accepted. I
> > > have not tested this further yet but it looks like a variation of the
> > > %include statement.
> > >
> > > As I can best recall, the Quit statement appeared in V6 with the advent
> > of
> > > more real-time sessions and the development of Procs that would
> continue
> > to
> > > run until stopped by the quit.
> > >
> > > Nat Wooding
> > > Environmental Specialist III
> > > Dominion, Environmental Biology
> > > 4111 Castlewood Rd
> > > Richmond, VA 23234
> > > Phone:804-271-5313, Fax: 804-271-2977
> > >
> > >
> > >
> > > Savian
> > > <savian.net@GMAIL
> > > .COM>
> To
> > > Sent by: "SAS(r) SAS-L@LISTSERV.UGA.EDU
> > > Discussion"
> cc
> > > <SAS-L@LISTSERV.U
> > > GA.EDU>
> Subject
> > > Re: run and quit after libname
> > >
> > > 04/09/2009 10:35
> > > PM
> > >
> > >
> > > Please respond to
> > > Savian
> > > <savian.net@GMAIL
> > > .COM>
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Apr 9, 7:03 pm, snoopy...@GMAIL.COM (Joe Matise) wrote:
> > > > I wonder if that is a SAS <v6 thing ... I've seen it also, but always
> > > with
> > > > people from the dinosaur era. :) Even with people reasonably
> > > knowledgeable
> > > > about SAS...
> > > >
> > > > -Joe
> > > >
> > > > On Thu, Apr 9, 2009 at 7:48 PM, Kenneth M. Lin
> > > > <kenneth_m_...@sbcglobal.net>wrote:
> > > >
> > > >
> > > >
> > > > > "Savian" <savian....@gmail.com> wrote in message
> > > >
> > >news:bec57f24-47f7-4a49-820b-1138a9a6ed76@k2g2000yql.googlegroups.com...
> > > > > On Apr 9, 4:23 pm, rogerjenkin...@YAHOO.COM (Roger Jenkins) wrote:
> > > > > >> I saw some code recently that used the run; and quit; statements
> > > after
> > > > > >> the
> > > > > >> libname statement. I've never used this myself. Is there any
> > reason
> > > that
> > > > > >> doing so would enhance the efficiency of my program?
> > > >
> > > > > >No. Someone doesn't know how to use SAS.
> > > >
> > > > > >Alan
> > > > > >Savian
> > > >
> > > > > You have no ideas how many times I have seen something like that.
> > The
> > > > > funniest is when someone indented the lines so a PROC SORT
> statement
> > > > > appears
> > > > > to reside within a DATA STEP. It works but you wonder if the
> person
> > > who
> > > > > wrote it understand what he/she was doing.- Hide quoted text -
> > > >
> > > > - Show quoted text -
> > >
> > > Joe,
> > >
> > > I have been using SAS since v 5 and never recall using a run quit on a
> > > libname.
> > >
> > > Alan
> > > Savian
> > >
> > >
> > > CONFIDENTIALITY NOTICE: This electronic message contains
> > > information which may be legally confidential and or privileged and
> > > does not in any case represent a firm ENERGY COMMODITY bid or offer
> > > relating thereto which binds the sender without an additional
> > > express written confirmation to that effect. The information is
> > > intended solely for the individual or entity named above and access
> > > by anyone else is unauthorized. If you are not the intended
> > > recipient, any disclosure, copying, distribution, or use of the
> > > contents of this information is prohibited and may be unlawful. If
> > > you have received this electronic transmission in error, please
> > > reply immediately to the sender that you have received the message
> > > in error, and delete it. Thank you.
> > >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic message contains
> > information which may be legally confidential and or privileged and
> > does not in any case represent a firm ENERGY COMMODITY bid or offer
> > relating thereto which binds the sender without an additional
> > express written confirmation to that effect. The information is
> > intended solely for the individual or entity named above and access
> > by anyone else is unauthorized. If you are not the intended
> > recipient, any disclosure, copying, distribution, or use of the
> > contents of this information is prohibited and may be unlawful. If
> > you have received this electronic transmission in error, please
> > reply immediately to the sender that you have received the message
> > in error, and delete it. Thank you.
> >
>
>
> CONFIDENTIALITY NOTICE: This electronic message contains
> information which may be legally confidential and or privileged and
> does not in any case represent a firm ENERGY COMMODITY bid or offer
> relating thereto which binds the sender without an additional
> express written confirmation to that effect. The information is
> intended solely for the individual or entity named above and access
> by anyone else is unauthorized. If you are not the intended
> recipient, any disclosure, copying, distribution, or use of the
> contents of this information is prohibited and may be unlawful. If
> you have received this electronic transmission in error, please
> reply immediately to the sender that you have received the message
> in error, and delete it. Thank you.
--
Jack Hamilton
Sacramento, California
jfh@alumni.stanford.org <== Use this, not jfh @ stanfordalumni.org
| 
