User Accounts transfer...

[Noor Ahmed_1]

Hi managers,

I have to move all user accounts from ALPHA 2100 system running OpenVMSV6.2 to Hp integrety server RX2600 running OpenVMS V8.2, which file I have to move and How??...

Rgds
noor

[Ian Miller.]

SYSUAF.DAT, RIGHTSLIST.DAT usually found in SYS$SYSTEM (but can be else where so check for logical names) contain the data. You can copy the files but will have to reconfigure products such as TCPIP which create usernames, you can copy individual records from SYSUAF (a small piece of DCL can do this) or you can retype.

[Kris Clippeleyr]

Hi,

Basically 2 files:

SYS$COMMON:[SYSEXE]SYSUAF.DAT
SYS$COMMON:[SYSEXE]RIGHTSLIST.DAT

Unless you have relocated them using logicals.

Make sure you use BACKUP to copy them.
Also a word of warning, I seem to remember that the layout of the SYSUAF.DAT file changed with V7.x (cannot check though since I don't have a 6.2 system at hand).

Regards,
Kris (aka Qkcl)

[Antoniov.]

Hi,
SYSUAF of V6.2 can be read on V7.3.
However, some user are differents (e.g. UCX vs TCPIP) and it isn't a good idea simply copy files.
It better make a merge.

Antonio Vigliotti

[Jeroen Hartgers_3]

aftre moving sysuaf file be sure the version is ;1 other wise it wil not work.

If the are anay system specific item in your sysuaf it is possible the authorization wil not work.

Im thinking about de things as lgicmd and the default (the home dir of a user)

you can also create a script to extract the information you need and use a script to create al the account on the new system.

[Robert Gezelter]

Noor,

Remember, after moving the file, you may need to make changes to quotas to reflect the requirements of your applications environments on the different architecture.

This can be done by changes to the SYSUAF, or temporarily by changes to the system minimums.

- Bob Gezelter, http://www.rlgsc.com

[Volker Halle]

Noor,

appendix B of the OpenVMS Cluster manual describes, how to merge SYSUAF and RIGHTSLIST

http://h71000.www7.hp.com/doc/731FINAL/4477/4477pro_contents_003.html#toc_appendix_b

Just taking both files from your 'old' system may corrupt/remove system-specific accounts (TCPIP, DECnet etc.). So you would best just move your user-accounts into the environment on the new system. Also consider increasing the user's quotas. Look at the DEFAULT account on your Itanium system and increase your user's quota appropriately.

Volker.

[Daniel Fernandez Illan]

Hi
Also you must re-create proxy database. To make this, the best option is recreate proxies, because doesn't compatible with older version.
Saludos.
Daniel.

[Bojan Nemec]

noor,

You can copy the old uaf file and clean it. To do this define a logical name SYSUAF to the old uaf and run SYS$SYSTEM:AUTHORIZE. When you are shure that this is the old uaf copy, remove all the system-specific accounts and unwanted accounts. When you have a clean version merge the files as Volker instructed.

Bojan

[Volker Halle]

Bojan,

careful ! Removing accounts will also remove identifiers from RIGHTSLIST. So you better also define a logical to point to the copy of the old RIGHTSLIST.DAT as well. Note: you must use DEF/EXEC for the RIGHTSLIST logical.

Volker.

[David Jones_21]

I was only coming from a 7.1 system, but I copied the the old SYSUAF and RIGHTSLIST files to the new system and then DCL to read and insert the few additional records from the new system's original SYSUAF. I then manually fixed up the RIGHTLIST. Finally, I wrote a procedure that scanned an authorize listing of the SYSUAF and generated commands to update the account quotas to the new recommended minimums.

[Ian Miller.]

David, parhaps you could contribute your DCL procedure at http://dcl.openvms.org ?

[David Jones_21]

>David, parhaps you could contribute your
>DCL procedure at http://dcl.openvms.org ?

OK. I submitted a pared down version of it, the original also did things like clean out stray privileges users were historically given and generate a list of diskquota commands (user volumes went from 50GB & 100GB disks to 600MB & 1TB disks).

[Bart Zorn_1]

Jeroen Hartgers wrote:

"aftre moving sysuaf file be sure the version is ;1 other wise it wil not work."


There is no need for this. Our production cluster's SYSUAF file is at version ;13.

The only case that I know of that you must have version ;1 is for directory files.

Regards,

Bart Zorn

[David Jones_21]

>"aftre moving sysuaf file be sure the version is ;1 other wise it wil not work."
>
>
>There is no need for this. Our production cluster's SYSUAF file is at version ;13.
>
>The only case that I know of that you must have version ;1 is for directory files.

If the SYSUAF logical definition includes a version (e.g. ";1"), services that open SYSUAF will only look for that version.