Hardware upgrade with a disk image change - subsequent steps - assure_mimix - 10.0

To perform this portion of the upgrade process, do the following after you have upgraded and restored all user data, including all MIMIX libraries:

1. Ensure the following system values are set the same way on the new system as they were on the old system: QAUDCTL, QAUDLVL, QALWOBJRST, QALWUSRDMN, QLIBLCKLVL, QRETSVRSEC, QSECURITY, and QSYSLIBL. For more information about system value settings, see the Assure MIMIX Administrator Reference book.

2. Type the following on a command line and press Enter:

   LAKEVIEW/UPDINSPRD

3. Enter the new product license key on the system. Do the following:

   1. From the MIMIX main menu select option 31 (Product Management Menu). The License Manager Main Menu appears.

   2. Select option 1 (Update license key). The Update License Key (UPDLICKEY) command appears. Follow the instructions displayed for obtaining license keys. For more information, see “Obtaining license keys using UPDLICKEY command” in the License Manager for IBM i Products book.

4. If the installed version of License Manager is at service pack 8.1.08.00 or higher, skip this step. For earlier versions of License Manager (8.1.01.00 through 8.1.07.00), you must reinstall License Manager using the installation wizard or the instructions in the “Installing products” topic in the License Manager for IBM i Products book.

5. Do the following from a command line on each system in the replication environment to register MIMX exit points in the system registry:

   1. Add the MIMIX installation library to your library list.

   2. Type CALL MXXPREG and press Enter.

6. Update any transfer definitions that require changes. For more information, see Considerations for performing a hardware system upgrade with a disk image change.

7. Ensure all automation, including MIMIX exit programs, for MIMIX is available and configured on the new system.

8. Make any necessary modifications to the QSTARTUP program. This may need to be modified to start the MIMIX subsystem after an IPL. For more information, see Considerations for performing a hardware system upgrade with a disk image change.

9. Start the MIMIX subsystem with the following command:

   STRSBS SBSD(MIMIXQGPL/MIMIXSBS)

10. On each system, do the following to clean up journals associated with system manager RJ links:

    1. Use the following command to display a list of the appropriate journal definitions:

       WRKJRNDFN JRNDFN(*ALL *LOCAL) RJLNK(*TGT) PROCESS(*INTERNAL)

    2. For each journal definition listed, do the following:

       • Type option 17 (Work with jrn attributes) and press Enter.

       • Press F15 (Work with receiver directory).

       • Type option 4 (Delete) for all receivers in the list. If message CPA7025 is issued, reply with an “I”.

11. Confirm that communications work between the new system and other systems in the MIMIX environment. For more information, see Verifying a communications link for system definitions.

12. Start the system manager with the following command:

    STRMMXMGR SYSDFN(*ALL) MGR(*SYS)

13. Optional step: Perform a data group switch by following the steps in your runbook, then skip to Step 15 for the target system. See Considerations for performing a hardware system upgrade with a disk image change to determine if a switch is required.

    Important!

    The role of the upgraded system within your production replication environment determines what step to perform next.

    • If the upgraded system is both the source and target of data groups within your environment, you must perform both Step 14 and Step 15.

    • If the upgraded system is only a source system, perform Step 14.

    • If the upgraded system is only a target system, perform Step 15.

14. If the source system was upgraded, use this step to ensure that journaling on the new system is correct and start replication processes:

    1. On the source system, type the following on a command line, and press Enter:

       WRKJRNDFN JRNDFN(*ALL *LOCAL) PROCESS(*REP)

    2. Press F10 to verify the Receiver Prefix, Library, and all other parameters (option 5) are correct. Make any necessary changes from the MIMIX management system before continuing.

    3. From the Work with Journal Definitions display, do the following to build the journaling environment and record the journal receiver names:

       • Type option 14 next to a journal definition with a value of *SRC or *NONE in the RJ Link column and press F4 (Prompt).

       • Type *JRNDFN for the Source for values parameter and press Enter.

       • Record the newly attached journal receiver name by placing the cursor on the posted message and pressing F1 or Help. You will need this information to start data groups.

    4. Repeat Step 14c for each journal definition with an RJ Link value of *SRC or *NONE.

    5. For each data group that has the upgraded system as its source system, run the following commands to ensure that files and objects are journaled to the correct journal:

       • To verify file entries are journaled, run:

         VFYJRNFE DGDFN(data-group-name) FILE1(*ALL) JRNSYS(*SRC)

       • To verify IFS entries are journaled, run:

         VFYJRNIFSE DGDFN(data-group-name) JRNSYS(*SRC)

       • To verify object entries are journaled, run:

         VFYJRNOBJE DGDFN(data-group-name) JRNSYS(*SRC)

    6. Start the Assure Unified Interface server using the command:

       VSI001LIB/STRVSISVR

    7. For each data group that has the upgraded system as its source system, start the data group with a clear pending start from the receivers recorded in Step 14c of this procedure:

       STRDG DGDFN(data-group-name) DBJRNRCV(user-journal-receiver) DBSEQNBR2(*FIRST) 
       OBJJRNRCV(security-journal-receiver) OBJSEQNBR2(*FIRST) CLRPND(*YES) 
       DTACRG(*YES)

    8. User and application activity can be resumed on the system.

15. If the target system was upgraded, use this step to ensure that journaling on the new system is correct and start replication processes:

    1. On the target system, type the following on a command line and press Enter:

       WRKJRNDFN JRNDFN(*ALL *LOCAL) PROCESS(*REP)

    2. Press F10 to verify the Receiver Prefix, Library, and all other parameters (option 5) are correct. Make any necessary changes from the MIMIX management system before continuing.

    3. From the Work with Journal Definitions display, do the following to build the journaling environment:

       • Type option 14 next to a journal definition with a value of *SRC or *NONE in the RJ Link column and press F4 (Prompt).

       • Type *JRNDFN for the Source for values parameter and press Enter.

    4. Repeat Step 15c for each journal definition with an RJ Link value of *SRC or *NONE.

    5. On a command line, type the following and press Enter:

       WRKJRNDFN JRNDFN(*ALL *LOCAL) RJLNK(*TGT)

    6. For the journal definitions listed on the Work with Journal Definitions display, do the following:

       • Type option 17 (Work with jrn attributes) and press Enter.

       • Press F15 (Work with receiver directory).

       • Type option 4 (Delete) for all receivers in the list. If message CPA7025 is issued, reply with an “I”.

    7. Repeat Step 15f for each journal definition associated with the target system.

    8. For each data group that has the upgraded system as its target system, run the following commands to ensure that files and objects are journaled to the correct journal:

       • To verify file entries are journaled, run:

         VFYJRNFE DGDFN(data-group-name) FILE1(*ALL) JRNSYS(*TGT)

       • To verify IFS entries are journaled, run:

         VFYJRNIFSE DGDFN(data-group-name) JRNSYS(*TGT)

       • To verify object entries are journaled, run:

         VFYJRNOBJE DGDFN(data-group-name) JRNSYS(*TGT)

    9. Start the Assure Unified Interface server using the command:

       VSI001LIB/STRVSISVR

    10. Use the following command and the printed information collected in Step 6 of Hardware upgrade with a disk image change - preliminary steps to start all of the data groups.

        Note: For each data group, use the Last read receiver and sequence number from its printed Object Status view (Step 6c) as the values for OBJJRNRCV andOBJSEQNBR2, and the values from the printed Database Status view (Step 6d) as the values for DBJRNRCV and DBSEQNBR2 in the following command:

        STRDG DGDFN(data-group-name) DBJRNRCV(last-read-database-journal-receiver) 
        DBSEQNBR2(last-read-database-sequence-number) 
        OBJJRNRCV(last-read-object-journal-receiver) OBJSEQNBR2(last-read-object-sequence-number) 
        CLRPND(*YES) DTACRG(*YES)

16. From both systems, delete any old receivers with different library or prefix names.

17. Run your MIMIX audits to verify the systems are synchronized. See Running an audit immediately for more information about running audits.