Date:         Thu, 20 Nov 1997 12:14:22 PST
Reply-To:     TWB2%Rates%FAR@bangate.pge.com
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Tim Berryhill 3rd time <TWB2%Rates%FAR@BANGATE.PGE.COM>
Subject:      Re: ... no subject ...
Comments: To: Wendih.Yao.at.Parexel-Chicago@PAREXEL.COM

On MVS I would let system security handle this.  On another box (Alpha), I think
you could approach it by checking the user ID and running PROC FSBROWSE instead
of PROC FSEDIT for unauthorized users.  You could also check the user ID before
executing a libname statement, only requesting write access for authorized
users.   My point is that, rather than using SCL associated with each variable
to prevent edits, I would check authorization before calling the PROC.
 
Did I answer the wrong question?  Were you asking how to capture the user ID on
an Alpha?
 
----------------------[Reply - Original Message]----------------------
 
Sent by:"Wendih Yao" <Wendih.Yao.at.Parexel-Chicago@PAREXEL.COM>
      Hi,
 
     I am developing a FSEDIT screen for entering some information on
     Alpha machine.  In EDIT mode, everyone in the group can add and
     modify the record.  The potential risk is that someone will
     modify the record by mistake.   Is there a way that I can write a
     SCL code to prevent this?  I.e., if the user id is not matching
     with a FLAG, the record can not be modified.  Your help is
     appreciated.
 
     Wendih
     PAREXEL International, Crop.
 
=====================================================================