|
HP OpenVMS Systemsask the wizard |
|
The Question is: Currently running v6.1 on a alpha 2100. We are replacing this with a alpha 4000 running v7.1-h2. How can I utilize or retain the sysuaf.dat file from the 2100 so that I don't need to redo all the user info on the 4000? The Answer is : SYSUAF, RIGHTSLIST, NETPROXY, and related files are compatible. (There are approximately twenty files that comprise the system personna of an OpenVMS system. See below.) The easiest course of action here would likely be to upgrade the existing AlphaServer 2100 to V7.1-1H2, and then transfer the disks (or the contents of the disks) over to the new AlphaServer 4000. Transfering just the core files is certainly possible, but it requires somewhat more "bookkeeping": UICs must be kept lined up, directories must be kept consistent, identifiers must use identical values, etc... The following topics are related: (60), (203), (767), (915), (961), (1201), (1861), (6106), (6735), (6982), and (6982). ... $! Site-specific VMScluster core file definitions are required whenever $! there is more than one system disk present in the VMScluster, and whenever $! the standard file naming and/or file location conventions are not used. $! $! The user should include definitions for the devices, directories, and file $! names for the various core VMScluster and DECnet files, typically including $! all of the logical names and file names shown below. (The file locations $! shown below use search list logical names such as SYS$SYSTEM: for clarity $! -- be aware that the files actually reside in the system disk system-common $! root, and not in the system-specific root. eg: the common files reside in $! SYS$SYSROOT:[SYSEXE], in the case of any files accessable via SYS$SYSTEM:.) $! $! The translations of the following list of logical names -- the translations $! shown here are the default names, device, and directory locations -- should $! be altered to match the local site-specific location and filename for the $! core files: $! $! DEFINE/SYSTEM/EXECUTIVE SYSUAF SYS$SYSTEM:SYSUAF.DAT $! DEFINE/SYSTEM/EXECUTIVE SYSUAFALT SYS$SYSTEM:SYSUAFALT.DAT $! DEFINE/SYSTEM/EXECUTIVE SYSALF SYS$SYSTEM:SYSALF.DAT $! DEFINE/SYSTEM/EXECUTIVE RIGHTSLIST SYS$SYSTEM:RIGHTSLIST.DAT $! DEFINE/SYSTEM/EXECUTIVE NETPROXY SYS$SYSTEM:NETPROXY.DAT $! DEFINE/SYSTEM/EXECUTIVE NET$PROXY SYS$SYSTEM:NET$PROXY.DAT $! DEFINE/SYSTEM/EXECUTIVE NETOBJECT SYS$SYSTEM:NETOBJECT.DAT $! DEFINE/SYSTEM/EXECUTIVE NETNODE_REMOTE SYS$SYSTEM:NETNODE_REMOTE.DAT $! DEFINE/SYSTEM/EXECUTIVE LMF$LICENSE SYS$SYSTEM:LMF$LICENSE.LDB $! DEFINE/SYSTEM/EXECUTIVE VMSMAIL_PROFILE SYS$SYSTEM:VMSMAIL_PROFILE.DATA $! DEFINE/SYSTEM/EXECUTIVE VMS$OBJECTS SYS$SYSTEM:VMS$OBJECTS.DAT $! DEFINE/SYSTEM/EXECUTIVE VMS$AUDIT_SERVER SYS$MANAGER:VMS$AUDIT_SERVER.DAT $! DEFINE/SYSTEM/EXECUTIVE VMS$PASSWORD_HISTORY SYS$SYSTEM:VMS$PASSWORD_HISTORY.DATA $! DEFINE/SYSTEM/EXECUTIVE VMS$PASSWORD_DICTIONARY SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA $! DEFINE/SYSTEM/EXECUTIVE NETNODE_UPDATE SYS$MANAGER:NETNODE_UPDATE.COM $! DEFINE/SYSTEM/EXECUTIVE VMS$PASSWORD_POLICY SYS$LIBRARY:VMS$PASSWORD_POLICY.EXE $! DEFINE/SYSTEM/EXECUTIVE LAN$NODE_DATABASE SYS$SYSTEM:LAN$NODE_DATABASE.DAT $! $! The following QMAN$MASTER queue manager logical name definition requires $! the use of the queue manager startup command: $! $! $ START/QUEUE/MANAGER/ON=(NodeX,NodeY,NodeZ) QMAN$MASTER $! $! The above queue manager startup command should be entered in the site-specific $! system startup command procedure SYSTARTUP_VMS.COM whenever the following $! logical name is used: $! $! DEFINE/SYSTEM/EXECUTIVE QMAN$MASTER SYS$SYSTEM: $! $! The above logical name references the device and directory that contains the $! set of files that comprise the queue manager database. ...
|