From:	SMTP%"RELAY-INFO-VAX@CRVAX.SRI.COM" 23-DEC-1993 08:43:31.20
To:	EVERHART
CC:	
Subj:	VMS 6.0 & Username Swap Program

X-Newsgroups: comp.os.vms
Subject: VMS 6.0 & Username Swap Program
Message-Id: <1993Dec15.134224.186@decus.org.nz>
From: wilsone@decus.org.nz
Date: 15 Dec 93 13:42:24 +1200
Organization: DECUS New Zealand
Lines: 19
To: Info-VAX@CRVAX.SRI.COM
X-Gateway-Source-Info: USENET

VMS 6.0 broke our username swap program, or to be exact, left the process
unable to run some standard VMS utilities such as TYPE and TPU after swapping.

The reason turned out to be changes in the way the access to the terminal
device is handled, and the fix required is to change ownership of that device
to the UIC of the new username.  VMS 6.0 provides a new system service -
SYS$SET_SECURITY - which makes this very simple.

The SYS$SET_SECURITY service also makes it possible to change ownership of
2 other objects that have access problems after swapping usernames and uics -
the job logical name table and the termination mailbox of the process if
swap is used in a spawned process.  My previous version of SWAP added an ACL
to these 2 objects so that the process could continue to use them after the
process UIC had changed.  These ACLs are no longer needed with VMS 6.0.
Instead the ownership of them can be changed to the new UIC with the
SYS$SET_SECURITY system service.

I hope this is of use to anyone with a SWAP utility who is upgrading to
VMS 6.0.