Here is a sample log ￿le for a serv er. The MIGRATE USER BACKWARD command returns the NETUsers ￿le to its state before the 3:41 PM migration.

TUE, APR 20, 1993,

3:40 PM: MIGRATE USER

 

Migrated Client : Umach.Udom.Uorg -> Umach.Usite.Uco.Udom

 

 

Login Name : user1.somegrp.someacct

 

 

Login Name : user2.somegrp.someacct

Migration complete.

 

2

user(s)

migrated successfully.

0

user(s) NOT migrated successfully - see above for error information.

TUE, APR 20, 1993,

3:41 PM: MIGRATE USER

 

Migrated Client : mach2.dom.org -> mach2.site.co.domain

 

 

Login Name : user3.somegrp.someacct

Migration complete.

 

1

user(s)

migrated successfully.

0

user(s) NOT migrated successfully - see above for error information.

TUE, APR 20, 1993,

3:45 PM: MIGRATE USER BACKWARD

Server List File

Each alias pro￿le that w as changed to show a di￿erent datacomm type requires that all corresponding user pro￿les on the serv er be changed also. If y ou use MIGRATE ALIAS to change an alias pro￿le, a serv er list ￿le, DASVRLST.PUB.SYS, is created and lists all a￿ected corresponding serv ers for the clien t. At the top of the ￿le, the NS v alue and ARPA value (if it can be determined by ALLBASE/NET) for the clien t node name are displa yed.

Here is a sample serv er list ￿le.

Client Node Name (NS value) : cnode.cdom.corg

Client Node Name (ARPA value) : chost.site.co.domain

Server Node Name List (NS value, ARPA value) : (snode.sdomain.sorg, snode)

(hana.dom.org, hana) (merc.dom.org, merc2) (mach1.dom1.org1, mach1)

Setting Up ALLBASE/NET 2-3