pung@ornl-ncc ("M. S. Pung") (11/03/87)
> Original question: > > I am currently working on a project which will centralize the > management of VAX/VMS authorizations, priviledges, etc. on all > of our VAXes. > > ... A critical issue involved in this is > whether of not the username field will be expanded in VMS V5.0 > to something like 32 characters. There are currently 32 bytes > set aside in the authorize record, with only 12 being used... > |------------------------------------------------------------------| > | Mike Pung | (615) 574-8082 | > | Oak Ridge National Lab | Pung%ornl-ncc@ornl-msr.arpa | > | Martin Marietta Energy Systems | 192.12.68.201 | > |------------------------------------------------------------------| In reference to the above article, Larry Campbell responded: >> Is this a trick question? Why don't you just assume that it will be >> expanded? If it is, you get big points for foresight; if not, no harm >> has been done, and maybe you're ready for VMS 6.0. >> >> Larry Campbell The Boston Software Works, Inc. >> Internet: campbell@maynard.bsw.com 120 Fulton Street, Boston MA 02109 >> uucp: {husc6,mirror,think}!maynard!campbell +1 617 367 6846 In response to Larry's remark, let me clarify the original question. Since the project completion date is slated to be within a year, the project could use a 32 character username if support was provided for it in VMS V5.0. If an extended username will not be provided within the short term (i.e. 6 months -> year), then the project will have to be implemented using a standard of a 12 character username. I wish we had the luxury of waiting for the extended username support to be provided in a later release, but unfortunately we do not. Any help/info is greatly appreciated. |------------------------------------------------------------------| | Mike Pung | (615) 574-8082 | | Oak Ridge National Lab | Pung%ornl-ncc@ornl-msr.arpa | | Martin Marietta Energy Systems | 192.12.68.201 | |------------------------------------------------------------------| ------