IBM Support

FSFC Features and Upgrades - 4.2

General Page

  • Features added in 4.2

    The following features were added (or fixed) in the June 8th, 2017 build:

    • Product access code 86 (Storwize FSFC) allows WRKCSE F6
    • Exit program is not called during CHKFSFLASH except for the *PRECHKSRC

    The following features were added (or fixed) in the June 18th, 2017 build:

    • GMCV with IPL memory flush timing issues addressed
    • SAVSYSBCH sample program source included in QZRDHASM/QCLSRC
    • SETUPFSFC uses *PRD with correct prompt control
    • SETUPFSFC will grant more authorities to QPGMR
    • Updated some messages, cleaned up logs
    • Support up to 512 LUNs in Storwize units (caused MCH3601's on the controller)
    • STRFLASH Flashcopy B works correctly
    • Flash for Storwize Full Copy and Resynch missing parameters

    The following features were added (or fixed) in the June 21st, 2017 build:

    • CHGBRMSOBJ accepts the correct access codes

    The following features were added (or fixed) in the June 28th, 2017 build:

    • Source LPAR lock released after flashcopy if not BRMS and not IPL
    • Locking tweaks
    • Quiesce time limit units are now consistent
    • Fixed repeated 'Busy' error
    • Suppress noise log messages

    The following features were added (or fixed) in the June 29th, 2017 build:

    • Enable socket keep alive packets

    The following features were added (or fixed) in the July 5th, 2017 build:

    • Set job name for remote STRFSFLASH to CSE Data name
    • Fixed issue with FLASHCOPY and SVC/V7K when a DATA CRG is provided. 
    • Fixed issue of missing UserQ with the name of the DATA CRG

    The following features were added (or fixed) in the July 7th, 2017 build:

    • Fixed issue of target LPAR lock not being released if time out occurred

    The following features were added (or fixed) in the next build:

    • CHKFSFLASH properly releases the BRMS port
    • GMCV + *FRCWRT will wait up to two hours for replication to catch up
    • Better communication between the source and controller when the flash takes too long
  • Upgrading to 4.2 from a prior release

    To upgrade from any prior version to 4.2 the environments and CSE Data must be recorded, removed, and then recreated after the upgrade.

    NOTE: 7.70 and older releases can co-exist with 4.2+ so there is no need to remove 7.70 data when installing 4.2.

    All the controllers and source LPARs in the cluster must be at the same version (i.e. 4.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.

    1. Ensure no STRFSFLASH or STRFLASH or SWCSE commands are in process.
    2. Issue WRKCSEDTA or DSPCSEDTA and record all the environments (opt 5)
    3. Issue WRKCSEDTA SELECT(*ALL) then delete them (opt 4)
      - Prior releases may not have WRKCSEDTA, therefore use WRKCLU opt 9 to remove the CRG's associated with CSE Data
    4. Issue WRKCSE and:
      - record all the environments (opt 5)
      - record all the host connections (opt 16)
      -
      delete them (opt 4). Delete all files when prompted.

    5. Issue WRKCSECRDL, record all the credentials (opt 5) then delete them (opt 4)

    6. End the toolkit subsystem:
      ENDSBS QZRDFSR *IMMED

    7. Place the savefile on each controller and production LPAR and restore into QZRDHASM
      RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/PHATOOLS42) MBROPT(*ALL) ALWOBJDIF(*ALL) OMITOBJ((QZRDHASM/*ALL *DTAQ))                              

    8. On each controlling partition:
      - issue the command SETUPFSFC NODEROLE(*CTL)
      - Recreate the credentials: WRKCSECRDL opt 1
      - Recreate the environments: WRKCSE opt 1 and host connections, opt 16
      - Recreate the CSE data: WRKCSEDTA opt 1

    9. On each source partition, end the toolkit subsystem:
      ENDSBS QZRDFSR *IMMED

    10. On each source partition, issue the SETUPFSFC NODEROLE(*SRC) command

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

  • Updating 4.2 to a newer build date">Updating 4.2 to a newer build date

    All the controllers and source LPARs in the cluster must be at the same version (i.e. 4.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.

    1. Ensure no STRFSFLASH or STRFLASH or SWCSE commands are in process.
    2. On each LPAR, end the toolkit subsystem:
      ENDSBS QZRDFSR *IMMED

    3. Place the savefile on each controller and production LPAR and restore into QZRDHASM
      RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/PHATOOLS42) MBROPT(*ALL) ALWOBJDIF(*ALL) OMITOBJ((QZRDHASM/*ALL *DTAQ))                              

    4. On each controlling partition issue the command SETUPFSFC NODEROLE(*CTL)

    5. On each source partition, issue the command SETUPFSFC NODEROLE(*SRC)

    After these steps have been performed, it is recommended that CHKFSFLASH be performed prior to 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"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]

Document Information

Modified date:
18 December 2019

UID

ibm11138324