IBM Support

Steps Required to Migrate Data from a System with an iASP to Another System with an iASP

Troubleshooting


Problem

When migrating data from one system to another and there are independent ASP (auxiliary storage) devices, special steps are required during restore operations. Generally, migration steps are provided in manuals titled Backup & Recovery for V5R4 operating system, or System management - Recovering your system for V6R1, 7.1 and later. Steps to create independent ASP (called iASP) devices are provided in other manuals. This document provides basic (but not all) steps for migration and configuring iASP devices.

Resolving The Problem

When migrating data from one system to another and there are independent ASP (auxiliary storage) devices, special steps are required during restore operations. Generally, migration steps are provided in manuals titled Backup & Recovery for V5R4 operating system, or System management - Recovering your system for V6R1mX, 7.1 or later. Steps to create independent ASP (called iASP) devices are provided in other manuals. This document provides basic (but not all) steps for migration and configuring iASP devices.

In this document, we are assuming the following:
o The source system is at a lower release, such as V5R4 operating system (OS), while the target system is at a higher release, such as 7.1 operating system.
o There are four iASP devices on the source system - ASPAAA, ASPBBB, ASPCCC, and ASPDDDD.
o Four iASP devices with the same names will be created on the target system.
o The iASP numbers are 33 through 36.
Note: Libraries and IFS data can be stored in iASP devices. Document library data (DLOs) are not supported in iASP devices.
  • - A. On V5R4 Operating System Source System

    1. Install ANZOBJCVN PTFs - SI28415 and its requisites including SI35565, SI25502 and SI26706 or their supersedes.
    2. Make sure all ASP devices are available and verify all programs will convert to run at V7R1.

    a. Issue the following command:

    WRKCFGSTS CFGTYPE(*DEV) CFGD(*ASP)

    b. Ensure that all iASP devices have a status of available. Select Option 1 to vary on if necessary to change status to available.

    c. Issue the following command:

    ANZOBJCVN ASPDEV(*ALLAVL)

    d. Verify that programs in the system ASP and iASP devices will convert after migration to the V7R1 operating system.
    3. Follow Chapter 15 of the V7R1 Recovery Guide to do the following:

    a. Issue the RTVSYSINF command.

    Note: This step is no longer necessary if you have V5R4 PTF 5722SS1 SI34094 or its supersede applied. RTVSYSINF data is automatically saved in library QUSRSYS during SAVE Option 21 backup.

    b. Create a GO SAVE Option 21 tape.
    4. Find file sequence numbers of various data saved by each command that is issued for GO SAVE Option 21 backup tape(s):

    a. Run DSPTAP OUTPUT(*PRINT) command.

    b. Issue command WRKJOB, select Option 4 for spooled file, and select Option 5 to display contents of that spooled file.

    In our example, the following information was found:

    Seq   File        
    No.   Label        Backup command and data saved
    ---   --------     -----------------------------
    35    QFILEUPR     SAVSECDTA - Security data  
    36    QFILEIOC     SAVCFG    - Configuration data  
    37    QFILE        SAVLIB    - Libraries in system ASP 1
    450   QDOC         SAVDLO    - Document library objects in system ASP 1
    451   SAVyyyymmdd  SAV       - IFS data in system ASP 1 where yyyy, mm and dd are year, month
                                   day when SAV command is issued for system ASP

    452   QFILE        SAVLIB    - Libraries in ASP 33 iASP device ASPAAA
    569   SAVyyyymmdd  SAV       - IFS data in ASP 33 iASP ASPAAA

    570   QFILE        SAVLIB    - Libraries in ASP 34 iASP device ASPBBB
    666   SAVyyyymmdd  SAV       - IFS data in ASP 34 iASP device ASPBBB

    667   QFILE        SAVLIB    - Libraries in ASP 35 iASP device ASPCCC
    752   SAVyyyymmdd  SAV       - IFS data in ASP 35 iASP device ASPCCC

    753   QFILE        SAVLIB    - Libraries in ASP 36 iASP device ASPDDD
    838   SAVyyyymmdd  SAV       - IFS data in ASP 36 iASP device ASPDDD
 
  • - B. On New System Built with 7.1 or later Operating System

    1. Make sure that only V7R1 or later License Internal Code and operating system *BASE options are installed.
    2.
    Sign on as QSECOFR and get to a restricted state by issuing command ENDSBS *ALL *IMMED.

    Notes:
    1) You should refer to Chapter 14, section Previous release to current release support of the Recovery Guide for your version of the IBM i OS level, in addition to the steps provided here.

    2) We have specified file sequence numbers in case restores are interrupted and have to be started over. If the commands are issued without any interruption, the SEQNBR parameter is not required. The sequence numbers can/will be different if changes are made (such as libraries are deleted or new libraries added) and another GO SAVE Option 21 backup is taken. Use command DSPTAP DATA(*LABELS) OUTPUT(*PRINT) to get correct file sequence numbers from the media. Important Note: As a precaution, you should have this information available before starting the restore on the target system.
    3. Restore security data including user profiles:

    RSTUSRPRF DEV(TAPXX) ALWOBJDIF(*ALL) ENDOPT(*LEAVE) SEQNBR(35)

    Replace TAPxx with the tape device that will be used for the restore. Use the tape created in Step 3b on the V5R4 operating system source system.
    4. Restore configuration data:

    RSTCFG OBJ(*ALL) DEV(TAPXX) ENDOPT(*LEAVE) SRM(*NONE) ALWOBJDIF(*ALL) SEQNBR(36)
    5. Restore IBM and user libraries in system ASP 1:

    RSTLIB SAVLIB(*NONSYS) DEV(TAPXX) OPTION(*NEW) MBROPT(*ALL) +
    ALWOBJDIF(*ALL) ENDOPT(*LEAVE) SEQNBR(37)
    6. Restore document library objects / DLOs:

    RSTDLO DLO(*ALL) DEV(TAP01) ENDOPT(*LEAVE) ALWOBJDIF(*ALL) SEQNBR(450)
    7. Restore IFS link objects in system ASP 1:

    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) +
    OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT)) +
    OPTION(*NEW) SEQNBR(451)

    In the above steps, data has been restored in system ASP 1.
    8. Now you will create/configure 4 iASP devices and get them ready for restores.

    a. Create iASP device ASPAAA for ASP number 33:

    b. Issue command CFGDEVASP to configure first iASP device:

    ASP device . . . . . . . . . . . >  ASPAAA (Name of first iASP device for ASP # 33)  
    Action . . . . . . . . . . . . . > *CREATE      
    ASP type . . . . . . . . . . . .   *PRIMARY    
    Protection . . . . . . . . . . .   *NO          
    Encryption . . . . . . . . . . .   *NO          
    Disk units . . . . . . . . . . .   *SELECT      
                   + for more values                
                                                   
                               Additional Parameters
                                                   
    Confirm  . . . . . . . . . . . .   *YES        

    c. Press the Enter key.

    System will list non-configured (available) disk units.

    d. Select the disk units you want to add to the first iASP device.

    e. Press the Enter key.

    The system will initialize each disk unit and add them to that particular iASP device.

    Note: The iASP storage size/capacity can be different from what you have on your source V5R4 system. It needs to be larger than the amount of data you have on your source system for each of the corresponding iASP devices.
    9. Repeat Step 8 for each iASP device. In the example, this step would be performed for iASP 34 device ASPBBB, iASP 35 device ASPCCC, and iASP 36 device ASPDDD.

    Note: By default restore will be performed into an ASP with the same number. If IASP will have a different number IASP name should be specified into the restore command.
    10. Vary on iASP devices as follows:

    WRKCFGSTS CFGTYPE(*DEV) CFGD(*ASP)

    Select Option 1 to vary on each iASP device.

    Notes:
    If the backup was done when file systems were unmounted (which is recommended) continue with step 11
    If the backup was done when file systems were mounted check note below.
    11. If the backup was done when file systems were unmounted (which is recommended), issue an unmount command of type *UDFS for each iASP. For example, using the following unmount commands on each QDEFAULT user-defined file systems in the iASP devices.

    UNMOUNT TYPE(*UDFS) MNTOVRDIR('/ASPAAA')
    UNMOUNT TYPE(*UDFS) MNTOVRDIR('/ASPBBB')
    UNMOUNT TYPE(*UDFS) MNTOVRDIR('/ASPCCC')
    UNMOUNT TYPE(*UDFS) MNTOVRDIR('/ASPDDD')
    12. Now that our iASP devices are ready, we will restore data into them.

    Restore libraries in iASP 33 - ASPAAA:

    RSTLIB SAVLIB(*ALLUSR) DEV(TAPXX) OPTION(*NEW) MBROPT(*ALL) +
    ALWOBJDIF(*ALL) ENDOPT(*LEAVE) SEQNBR(452)
    13. Restore IFS link data in iASP 33 - ASPAAA.

    Note: If there is no IFS data in this iASP device, this RST step can be skipped. You can issue command WRKLNK '/dev', and select Option 5 to look for path /dev/ASPAAA/QDEFAULT.UDFS:

    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) +
    OBJ(('dev/*')) ENDOPT(*LEAVE) SEQNBR(569)
    14. Restore libraries in iASP 34 - ASPBBB:

    RSTLIB SAVLIB(*ALLUSR) DEV(TAPXX) OPTION(*NEW) MBROPT(*ALL) +
    ALWOBJDIF(*ALL) ENDOPT(*LEAVE) SEQNBR(570)
    15. Restore IFS link data in iASP 34 - ASPBBB;

    Note: If there is no IFS data in this iASP device, this RST step can be skipped. You can issue command WRKLNK dev, and select Option 5 to look for path /dev/ASPBBB/QDEFAULT.UDFS:

    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) +
    OBJ(('dev/*')) ENDOPT(*LEAVE) SEQNBR(666)
    16. Restore libraries in iASP 35 - ASPCCC:

    RSTLIB SAVLIB(*ALLUSR) DEV(TAPXX) OPTION(*NEW) MBROPT(*ALL) +
    ALWOBJDIF(*ALL) ENDOPT(*LEAVE) SEQNBR(667)
    17. Restore IFS link data in iASP 35 - ASPCCC;

    Note: If there is no IFS data in this iASP device, this RST step can be skipped. You can issue command WRKLNK '/dev', and select Option 5 to look for path /dev/ASPCCC/QDEFAULT.UDFS:

    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) +
    OBJ(('dev/*')) ENDOPT(*LEAVE) SEQNBR(752)
    18. Restore libraries in iASP 36 - ASPDDD:

    RSTLIB SAVLIB(*ALLUSR) DEV(TAPXX) OPTION(*NEW) MBROPT(*ALL) +
    ALWOBJDIF(*ALL) ENDOPT(*LEAVE) SEQNBR(753)
    19. Restore IFS link data in iASP 36 - ASPDDD;

    Note: If there is no IFS data in this iASP device, this RST step can be skipped. You can issue command WRKLNK '/dev', and select Option 5 to look for path /dev/ASPDDD/QDEFAULT.UDFS:

    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) +
    OBJ(('dev/*')) ENDOPT(*LEAVE) SEQNBR(838)
    20. Restore authorities to link private authorities:

    RSTAUT
    21. Now that all data has been restored, you should mount type *UDFS for each iASP -- Mount QDEFAULT user-defined file systems that were unmounted earlier:

    MOUNT TYPE(*UDFS) MFS('/dev/ASPAAA/QDEFAULT.UDFS') MNTOVRDIR('/ASPAAA)
    MOUNT TYPE(*UDFS) MFS('/dev/ASPBBB/QDEFAULT.UDFS') MNTOVRDIR('/ASPBBB)
    MOUNT TYPE(*UDFS) MFS('/dev/ASPCCC/QDEFAULT.UDFS') MNTOVRDIR('/ASPCCC)
    MOUNT TYPE(*UDFS) MFS('/dev/ASPDDD/QDEFAULT.UDFS') MNTOVRDIR('/ASPDDD)
    22. Now that all user data and iASP data are available, it is recommended that STROBJCVN be run now to convert user objects including programs. You can either run this command for system ASP first and then for each of the four iASP device separately, or run STROBJCVN ASPDEV(*ALLAVL).
    23. If PTF SI34094 (for product 5722SS1) or its supersede was installed on your source V5R4 system, then run UPDSYSINF LIB(QUSRSYS). If that PTF was not installed and you ran RTVSYSINF on your source system before running GO SAVE option 21 backup, then issue command UPDSYSINF for the library into which you manually saved RTVSYSINF.
    24. Upgrade/install all operating system and LPP options that are compatible with the V7R1 operating system.

    Issue the GO LICPGM command, select Option 1, and select the following:

       Install option . . . . . .   1        
       Installation device  . . .   TAPxx            
       Replace if current . . . .   N        
       Nonaccepted agreement  . .   2        
       Automatic IPL  . . . . . .   N    
    25. Install any additional license programs that you need on your new V7R1 or later operating system that were not installed on your V5R4 system.
    26. Install V7R1 or later cumulative, HIPER, DB2, and all other PTF groups required for your system.
    27. Check that all your data in libraries and the IFS for system ASP and all four iASP devices was migrated. Test applications as necessary.
 
  • - Note for Section B. If the backup was done when file systems were mounted



    If the backup was done when file systems were mounted, check if the file system is mounted using command dspudfs or statfs. If file system is not mounted, the directory is restored to the SYSBAS instead of IASP; for example, using the following commands on each QDEFAULT user-defined file systems in the iASP devices:

    DSPUDFS UDFS('/dev/ASPAAA/QDEFAULT.UDFS')
    DSPUDFS UDFS('/dev/ASPBBB/QDEFAULT.UDFS')
    DSPUDFS UDFS('/dev/ASPCCC/QDEFAULT.UDFS')
    DSPUDFS UDFS('/dev/ASPDDD/QDEFAULT.UDFS')

    or

    STATFS OBJ('/ASPAAA')
    STATFS OBJ('/ASPBBB')
    STATFS OBJ('/ASPCCC')
    STATFS OBJ('/ASPDDD')

    If file system is mounted, directories contained by file system over mounted directory can be restored using the following commands:

    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) OBJ(('/ASPAAA/*')) ENDOPT(*LEAVE) SEQNBR(569)
    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) OBJ(('/ASPBBB/*')) ENDOPT(*LEAVE) SEQNBR(666)
    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) OBJ(('/ASPCCC/*')) ENDOPT(*LEAVE) SEQNBR(752)
    RST DEV('/QSYS.LIB/TAPxx.DEVD') ALWOBJDIF(*ALL) OBJ(('/ASPDDD/*')) ENDOPT(*LEAVE) SEQNBR(838)

    To complete migration, you should continue with Step 20.

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z000000cwp6AAA","label":"Save Restore"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

646296407

Document Information

Modified date:
08 November 2024

UID

nas8N1010783

Page Feedback