[comp.os.vms] VMS V5.0

pung@ornl-ncc ("M. S. Pung") (10/28/87)

Hello,
	I am currently working on a project which will centralize the
	management of VAX/VMS authorizations, priviledges, etc. on all
	of our VAXes.

	We are currently looking to settle a dispute on the format/length
	of the VAX/VMS username.  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...

	Does anyone have any insight as to whether or not the username
	field will be expanded in VMS V5.0?

	Any info/rumors would be 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	   |
	|------------------------------------------------------------------|

------

JMS%uamis@RVAX.CCIT.ARIZONA.EDU.UUCP (11/02/87)

PUNG@ORNL-NCC asks if usernames will ever be expanded to
32 bytes.

The answer to this question is, EVEN IF WE KNEW, you would
be incredibly foolhardy not to build into your "uaf" AT LEAST
as many bytes of space as Digital has allocated, *if not more!*

We have a similar product/project, and we looked at the DECnet
specs, which allocate 39 bytes for both username and account fields,
for a total of at least 78 bytes.  

jms

+-------------------------------+
| Joel M Snyder                 |            BITNET: jms@arizmis.BITNET
| Univ of Arizona Dep't of MIS  |          Internet: jms@mrsvax.mis.arizona.edu
| Tucson, Arizona 85721         |   Pseudo-PhoneNET: (602) 621-2748
+-------------------------------+              ICBM: 32 13 N / 110 58 W
(I have gotten into trouble too many times to put any faith in disclaimers)
"There's nothing here that an overdose of Seconal won't cure." 

I7100501@DBSTU1.BITNET.UUCP (11/20/87)

"M. S. Pung" <PUNG@ORNL-NCC> writes:
>    We are currently looking to settle a dispute on the format/length
>    of the VAX/VMS username.  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...

This information is from a german field test site for VMS V5.0:

VMS V5.0 will NOT support usernames longer than 12 characters.

-----------------------------------------------------------------------------
Eckart Meyer                            BITNET: I7100501@DBSTU1
Inst. f. Nachrichtentechnik             PHONE:  0531 / 391-2454
Technical University of Braunschweig    ADDR:   Schleinitzstr. 23
Germany                                            3300 Braunschweig
-----------------------------------------------------------------------------

"RCSDPR::RHEAUME@gmr.COM" (06/29/88)

We have just installed VMS V5.0 on a new VAX 6210.

Following are a few brief comments about the installation:
**********************************************************

- The 6210 will only run VMS V5.0. 
	(I believe this is the 1st official release of V5.0)

- Hardware installation took about 2 hours
	( a very nice compact machine )

- Software installation took about 2 hours
	( This was a new install, not an upgrade )
	( This was very easy to do, nothing like V3.x -> V4.0 )

- License Management Facility (LMF) is now available and DEC has
	shipped Product Authorization Keys (PAK's) for 
	VMS, DECNET, and VAXCLUSTER. At this time, these are the
	only products which will require PAK's. All other products
	will install without the PAK.

- We have installed (without any problems)
	- FORTRAN		- PASCAL
	- PL/I			- MMS
	- VAXC			- CMS
	- LSE
	(we are waiting for the official release of 
	 DNS, DQS, DFS, and RSM for V5.0)

- We have tested MASS11 and TEX and they both work

- The SYSUAF file is unchanged from V4.x but the NETUAF file
	has changed format and its name to NETPROXY.DAT.

- We added the machine to a 750/780 VMS V4.7 cluster
	and have had no problems.

- We have mounted user disks from both the V4.7 and V5.0
	system but were not able to mount the V4.7 system
	disk from the V5.0 system.

- VMS V5.0 manual set 	- fills 5 boxes
			- (32) 3" ring binders
			- about 10 ft of shelf space

- We haven't made the system available to users yet.
	So, I can't give you any user comments.