IBM Support

FSFC Features and Upgrades - 5.2

General Page

This page describes the features added and defects addressed with each build.
Contact support to access the upgrade files. A valid maintenance agreement is required.
  • Features added in 5.2

    PowerHA Tools for IBM i 5.2 is now available for all customers current on maintenance. It has all the features and fixes from prior releases, and adds the following:

    • 58120: Support for FlashSystem volume-group Flashcopy

    • 53031: BRMS Exit Program Changes for 7.5

    • 59763: CSM profile *CSMAUT

    • 48045: APIs updated to support FlashSystem volume-group FlashCopy

    • 37482: Only show IBM i LPARs when prompting the HMC

    • 51511: Better coverage for using the message queue specified in CSEDTA

    • 59358: Flash system safeguarded sessions no longer require CSM

    • 58835: QSTRUPPGM is not changed on flashcopy LPAR (CFGSTRPRSC must be added to client QSTRUP)

    • 58751: Don't delay for iCC transfer if iCC isn't installed

    • 234684: Removed BRMS locking parameters (will use *FCNUSG and *SRCONLY)

    The following features were added (or fixed) in the February 5th, 2023 build (20240205):

    • 698538: Flashcopy doesn't remove userspace, preventing CFGSTRPRSC from running clean on source

    • 685204: STR/CHKFSFLASH run on source should not try to release PowerHA licenses

    • 678246: Add data exposure time parm to RTVCSMSSNS command

    • 6788196: VGFC and SGC creating snapshots in wrong pool

    • 678069: WRKCSE *SELECT for Volume fails when policy name contains a space

    • 680745: Remove VGFC flash from PPRC target parameters

    • 680745: Change Target Volume Pool to Target Snapshots Pool

    • 684731: Print Java stack traces in select catch blocks

    • 678195: CG FC mappings increment mix was only checked if the CG was running

    • 666765: SVC Storage protection was counting backwards

    • 666518: More log messages related to VGFC and PBR.

    • 625627: Add more log files to DMPINF

    • 461964: PowerVS API URL errors in SYD

    • 503146: Improve Java JSON parsing messages

    • 46853: Backup IDs on WRKSGCCPY need to be sorted

    • 448932: Some 4.6 CSEDTA's weren't readable by 5.2

    • 451494: Cal't call registered exit progrmas with program data

    • 368771: CHKFSFLASH with bad RCCG results in MCH6902

    • 234836: STRFSFLASH on source received CPF9E11

    • 369619: STRSGCPY invalid check for inactive PPRC

    • 368442: FSFC SVC WRKCSE opt 12 opt 17 doesn't show correct ID or allow changing copy rates

    • 234795: WRKCSE opt 12 DS8K FC F8 wasn't working

    • 234590: STRSGCPY should issue escape message if it fails

    • 193104: VGFC SGC recovery pool ID defaults to 16448 (and it shouldn't)

    • 185585: Remote VGFC wasn't monitoring PCYGM

    • 184477: WRKCSE opt 1 needs to check input parameter for storage type

    • 66009: Validation of VGFC CSE when CSE has no hosts defined should fail

    • 61091: SGC groups issues IAS2026 when it shouldn't

  • Upgrading to 5.2 from a prior release

    Upgrading to 5.2 is only recommended from version 4.6 or 5.1 - upgrading from any other release will require manually re-creating all WRKCSE, WRKCSEDTA and WRKCSECRDL entries. Use the following command to display the version and build date:

    
    DSPDTAARA DTAARA(QZRDHASM/BUILD)

    All the controllers and source LPARs in a cluster must be at the same version (i.e. 5.2). We strongly recommend that they also all be at the same build date. The version and build date is stored in data area QZRDHASM/BUILD.

    The 5.2 controllers will support non-cluster source LPARs running at 4.6, 5.1 or 5.2, which facilitates upgrading source LPARs in stages.

    Use WRKCSE opt 2 to update any FSFC environments using FlashCopy from FlashSystem MMIR targets. Add the source device IP and consistency group. This will enable the toolkit to pause replication before a FlashCopy to prevent torn pages.


    To upgrade the controllers:

    1. Ensure the controllers are at 4.6 or 5.1 before proceeding.
    2. Ensure no STRFSFLASH or STRFLASH or SWCSE commands are in process.
    3. End the toolkit subsystem:
      
      ENDSBS QZRDFSR *IMMED
    4. Generate a text file with all of the WRKCSE / WRKCSEDTA information:
      
      QZRDHASM/DMPINF ENV(*ALL) EXTDLOGS(*NO)
    5. Save the DDD information:
      
      MKDIR '/tmp/ddd46backups'
      QZRDHASM/SAVDDD PATH('/tmp/ddd46backups')
    6. On each controller, issue the restore command:
      
      RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/QZRDHASM52) MBROPT(*ALL) ALWOBJDIF(*COMPATIBLE) OMITOBJ((QZRDHASM/*ALL *DTAQ))
    7. Update to the most recent Secure Java JAR file.
      Download it from here: https://sourceforge.net/projects/jsch/files/jsch.jar/0.1.55/jsch-0.1.55.jar/download
      Place it on all controllers in /QIBM/Qzrdhasm/ssh/
      Then update the links if a new jar file is downloaded:
      RMVLNK OBJLNK('/QIBM/Qzrdhasm/ssh/jsch.jar') 
      ADDLNK NEWLNK('/QIBM/Qzrdhasm/ssh/jsch.jar') OBJ('/QIBM/Qzrdhasm/ssh/jsch-0.1.55.jar') 
    8. On each controlling partition issue the setup command:
      
      SETUPFSFC NODEROLE(*CTL) MIGRATE(*YES)

    To upgrade a source LPAR:
    1. End the toolkit subsystem:
      
      ENDSBS QZRDFSR *IMMED
    2. On each source partition, issue the restore command:
      
      RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/QZRDHASM52) MBROPT(*ALL) ALWOBJDIF(*COMPATIBLE) OMITOBJ((QZRDHASM/*ALL *DTAQ))
    3. On each source partition issue the setup command:
      
      SETUPFSFC NODEROLE(*SRC)
    4. On each source partition add CFGSTRPRSC to the beginning of the startup program:
      
      DCL VAR(&IPLTYPE) TYPE(*CHAR) LEN(5) VALUE('?????')
      /* PowerHA Tools for IBM i */
      QZRDHASM/CFGSTRPRSC RTNVAR(&IPLTYPE)
      MONMSG     MSGID(CPF0000)
      IF         COND((%SST(&IPLTYPE 1 3) *EQ '*FC') *OR +
                      (%SST(&IPLTYPE 1 5) *EQ '*DTCH') *OR +
                      (%SST(&IPLTYPE 1 5) *EQ '?????')) +
                 THEN(RETURN)
      STRTCP
      MONMSG     MSGID(CPF0000)
      
    5. On each source partition add a *FC entry to WRKSTRPRSC (only the 'System Information' panel)
    6. After these steps have been performed, it is recommended that CHKFSFLASH be performed before the next planned flashcopy to test the configuration.
  • Updating 5.2 to a newer build date

    1. Ensure no STRFSFLASH or STRFLASH or SWCSE commands are in process on the LPAR being upgraded.
    2. End the toolkit subsystem:
      
      ENDSBS QZRDFSR *IMMED
    3. Issue the restore command:
      
      RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/QZRDHASM52) MBROPT(*ALL) ALWOBJDIF(*COMPATIBLE) OMITOBJ((QZRDHASM/*ALL *DTAQ))
    4. Issue the appropriate setup command:
      
      SETUPFSFC NODEROLE(*CTL)
      SETUPFSFC NODEROLE(*SRC)  

    After these steps have been performed, it is recommended that CHKFSFLASH be performed before the next planned flashcopy to test the configuration.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z000000cxy9AAA","label":"High Availability-\u003EFull System Flash Copy"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Document Information

Modified date:
07 February 2024

UID

ibm16986607