Preparing for data migration from i5/OS V5R3 or OS/400 V5R2 or V5R1

Use these instructions if you cannot or do not want to load i5/OS® V5R4 on your source server. These instructions will prepare to migrate your data from a server running i5/OS V5R3 or OS/400® V5R2 or V5R1 to a target server running i5/OS V5R4.

If you cannot install i5/OS V5R4 on your source iSeries™ server, you can still migrate your data by saving your source server, performing a full server recovery, and installing i5/OS V5R4 onto the target server. Before you begin this procedure, be sure you have completed these prerequisite tasks:

To prepare to migrate your data from a server running OS/400 V5R1 or V5R2 or i5/OS V5R3, perform these tasks:

Prepare target server

  1. Verify that the target server is set up and is running with only the Licensed Internal Code and i5/OS installed (feature code 0205).
  2. If you are configuring a server with logical partitions, create logical partitions on the target server and then install the Licensed Internal Code and i5/OS on each logical partition.

    Allow at least two additional hours to do this for each logical partition. For more information about logical partitions, see Configure logical partitions.

  3. Ensure that your console is set up and ready. For information on performing this task, see Managing consoles, interfaces, and terminals.
    Note: If you are using a twinaxial console on the source server and using Operations Console on the target server, ensure that you have a twinaxial controller for any twinaxial devices you plan to run from the target server.
  4. Perform disk unit management (for example, manage disk protection and disk configuration). To do this, you can use the Work with Disk Units option from the Dedicated Service Tools display. For information, see the chapter that contains procedures for configuring disks and disk protection in the Backup and Recovery Guide Link to PDF.
  5. Make sure that you have a copy of the distribution media for the target server.

Prepare the source server

  1. Clean up the source server as follows:
    1. Use the Work with Line Descriptions (WRKLIND) command to view and delete unused lines and line descriptions.
    2. Use the Work with Device Descriptions (WRKDEVD) command to delete unused device descriptions.
      Note: You can use the Work with Line Descriptions and Work with Device Descriptions commands to view and verify that all of the descriptions listed are in use. If you are sure that one is not in use, delete it. If you are not sure, you should leave it.
    3. Clean up disk storage space. For more information, see Cleaning up disk storage space.
  2. Ensure that you have the required fixes (also called program temporary fixes or PTFs). For more information about software fixes, see Use software fixes.
  3. Gather performance data. This gives you a basis for comparing performance before and after the data migration.
  4. On an i5/OS command line, enter RTVSYSINF (Retrieve System Information).

    When you run this command, specify the library to use. Typically, you can specify the QUPGRADE library. If this library does not exist, create it with the Create Library (CRTLIB) command.

  5. Print your server configuration information as follows:
    1. On an i5/OS command line, enter PRTSYSINF, and then print the resulting spooled file.

      This prints reports of the hardware resources, software resources, system values, installed fixes, and other configuration information.

    2. Print a new server configuration list and keep this list for future reference. For detailed instructions, see Printing the server configuration list.
    3. On an i5/OS command line, enter WRKDEVD and enter option 6 (Print) to print the device descriptions.
    4. On an i5/OS command line, enter WRKCTLD and enter option 6 (Print) to print the controller descriptions.
    5. If you have a partitioned server, print the server configuration for logical partitions using the Start System Service Tools (STRSST) command. For more information about printing the server configuration for logical partitions, see Print server configuration for logical partitions.
    6. If necessary, save spooled files. For instructions, see Save spooled files in the "Back up your server" topic collection.
    7. Record your current job scheduler entries so that you can manually re-create them on the target server. To do this, use the print option on the WRKJOBSCDE (Work with Job Scheduler Entries) command.
  6. Save the entire server using option 21 of the GO SAVE command. For more information, see the GO SAVE topic. Specify the following options:
    1. Vary off the network server...*ALL
    2. Unmount file systems..........Y
      Note: Ensure that you have two copies of the backup media.

Send feedback | Rate this page