MIGRATE ALIAS

Use the MIGRATE ALIAS command to migrate alias profiles from NS to ARPA in the AliasDB file on the client. You can choose the automatic option to migrate all profiles or the manual option which prompts you for the server node name of each profile. To use the automatic option, this command must be used before installing HP-UX 10.0 on the client and/or the server.

If you execute MIGRATE ALIAS VERBOSE, all diagnostic information written to the log file will also appear on the screen. See the description of the log file below.

MIGRATE ALIAS can be abbreviated to MA. MIGRATE ALIAS VERBOSE can be abbreviated to MAV.

You must be logged on as MANAGER.SYS or have SM capability to execute this command.

NETUtil Syntax

   netutil=> MIGRATE ALIAS [VERBOSE]

Automatic Migration (y/n)? {y[es]} {n[o]}

   Alias Name : testdb

   Current Server Node Name : ServerNodeName

   New     Server Node Name (NewServerNodeName) : ServerNodeName 



   Migrate profile (y/n)?  y

Parameters

ServerNodeName: is the name of the server you want to access. You should enter the ARPA host name here. If a value for (ServerNodeName(ARPA value)) is displayed, you may press Return to select that value.

Description

MIGRATE ALIAS only targets alias profiles where client and/or server is a HP9000 S700 or S800 and the datacomm type is NS. In addition, MIGRATE ALIAS will alert you if any alias profiles specify a machine type of HP 9000 S300 or S400. The use of a HP 9000 S300 and S400 as a server is not supported in the ALLBASE/SQL G.0 release.
MIGRATE ALIAS prompts you to select a migration option, either automatic or manual:
- automatic - All targeted alias profiles will be changed automatically. The datacomm type will be changed from NS to ARPA and the NS node name entry for Server Node Name will be changed to an ARPA host name. To use MIGRATE ALIAS with the automatic option, do the following:
  Do the migration before installing HP-UX 10.0 on the client and/or server, otherwise only manual migration can be used.
  Install patch release phne_2288 and phne_3502 on HP-UX.
  Make sure remote loopback is enabled on all servers.
- manual - For each targeted alias profile, the alias name and current server node name will be displayed. A prompt will appear for the new server node name, with the ARPA host name in parentheses (if it can be determined by NETUtil). You may enter an ARPA host name at the prompt, or if the ARPA host name appears, you may press the Return key instead. The datacomm type will automatically change from NS to ARPA.
When all migration completes, totals for successful and unsuccessful migration attempts are displayed. Finally, you will be prompted to save the migration changes.
When the migration commands are used, two files are created or appended to on the client: a migration log file, named HPDAMIG.PUB.SYS, and a server list file, named DAUSFMIG.PUB.SYS. The migration log file contains the following information for each profile:
- a timestamp
- the command name MIGRATE ALIAS
- the alias name
- current server node name (NS value)
- new server node name (ARPA value)
The server list file contains a list of affected servers. For each server, use MIGRATE USER or CHANGE USER to migrate the client from an NS value to an ARPA value.

Examples

In this example, MIGRATE ALIAS is executed and the automatic option is chosen. A migration error occurs during migration.

   netutil=>  MIGRATE ALIAS

   Automatic Migration (y/n)?  y



   Migration in progress ...



   Cannot migrate alias (testdb2) for server (node1)  (DBERR 28029)



   Migration complete.

   3 alias(es)     migrated successfully.

   1 alias(es) NOT migrated - see screen above or HPDAMIG.PUB.SYS

   for error information.



   Save migration changes (y/n)?  y



   Migration changes saved.



   netutil=>

In this example, MIGRATE ALIAS VERBOSE is executed and the automatic option is chosen. A migration error occurs during migration.

   netutil=>  MIGRATE ALIAS VERBOSE

   Automatic Migration (y/n)?  y



   Migration in progress ...



     Alias: testdb  Migrated Server : snode.sdomain.sorg -> snode

   Cannot migrate alias (testdb2) for server (node1.dom.org) (DBERR 28029)

     Alias: testdb3  Migrated Server : hana.dom.org -> hana1.site1.co1.domain1

     Alias: testdb4  Migrated Server : merc.dom.org -> merc2



   Migration complete.

   3 alias(es)     migrated successfully.

   1 alias(es) NOT migrated - see screen above or HPDAMIG.PUB.SYS

   for error information.

   Save migration changes (y/n)?  y



   Migration changes saved.



   netutil=>

In this example, the manual option is chosen. Two profiles were found; the ARPA host name value for the new server node name could only be determined for the first profile.

   netutil=>  MIGRATE ALIAS

   Automatic Migration (y/n)?  n



   Alias Name : testdb

   Current Server Node Name : snode.sdomain.sorg

   New     Server Node Name (snode) :  Return



   Migrate profile (y/n)?  y



   Profile migrated.



   Alias Name : testdb2

   Current Server Node Name : node1.dom.org

   New     Server Node Name (snode1) :  newnode



   Migrate profile (y/n)?  y



   Profile migrated.



   Migration complete.

   2 alias(es)     migrated successfully.

   0 alias(es) NOT migrated - see screen above or HPDAMIG.PUB.SYS

   for error information.



   Save migration changes (y/n)?  y 



   Migration changes saved.



   netutil=>

In this example, the manual option is chosen. The user exits before all migration is completed.

   netutil=>  MIGRATE ALIAS

   Automatic Migration (y/n)?  n



   Alias Name : testdb

   Current Server Node Name : snode.sdomain.sorg

   New     Server Node Name (snode) : Return



   Migrate profile (y/n)?  y



   Profile migrated.



   Alias Name : testdb2

   Current Server Node Name : node1.dom.org

   New     Server Node Name () :  //



   Migration complete.

   1 alias(es)     migrated successfully.

   0 alias(es) NOT migrated - see screen above or HPDAMIG.PUB.SYS

   for error information.

   Save migration changes (y/n)?  y



   Migration changes saved.



   netutil=>

MIGRATE ALIAS

Technical documentation

» Table of Contents

» Glossary

» Index

NETUtil Syntax

Parameters

Description

Examples