FSR Features and Upgrades - 4.3

The following features are added (or fixed) in the initial build:

• All fixes to 4.2
• Removed the limit of how many CSE Data's it can manage (it used to be approximately 11)

The following features were added (or fixed) in the January 16th, 2018 build:

• Data queue will be recreated if damage is detected
• Ping reported failure despite being successful
• Log includes toolkit version
• Nuisance message CPIBC05 removed from logs
• Miscellaneous log, joblog, help text and message fixes (typo's, missing, etc)
• IASP CSEDTA flash options added back in
• IAS0857 not issued during *IPL
• Savefile name changed (from QZRDHASM_43 to QZRDHASM43)
• FIXSTRPRSC/RTVLPARINF/RUNLPARCMD LPAR# increased to 1000
• Detach/Re-attach consistently displayed on WRKCSE opt 12
• Keylock parameters consistently work
• FSR LUN warning caused other checks to be skipped
• MSG_ERROR put garbage in the job log

The following features were added (or fixed) in the April 9th, 2018 build:

• GMIR attempted to replicate wrong direction after switch
• Resume replication shows entire LPAR name and PS vs PT
• Improvements to DMPVFYINF and DMPINF
• Improved encryption error logging
• Improvements in pulling joblogs
• CRTCSEDTA handles spaces in secondary controller field
• WRKCSE, WRKCSEDTA and WRKCSEDRL check for cluster partitioned state
• Removed IASP-related parameters from WRKCSEDTA
• WRKCSE GMCV cycle period shows entire field
• MMIR Target LPAR in error creates joblog message

The following features were added (or fixed) in the April 26th, 2018 build:

• Remove non-standard Java parameters
• DS8K MMIR unable to start replication after a switch
• Additional logging

The following features were added (or fixed) in the August 20th, 2018 build:

• GMCV Flashcopy freeze monitoring time extended
• WRKSTRPRSC allows BRMS objects containing 'V'
• RunSshTunnel has more logging
• WRKCSEDTA looks for existing CRGs instead of IFS objects
• RunSshTunnel extended timeout interval for slow HMC/SVC/Network responses
• MCH3601 from QZRDIAEXT2 in getJobLogs resolved
• MSG_BUSY improvements (process interlocks)
• GMCV SWCSE method changed (does not use GMIR mode as an intermediate)

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

• DMPVFYDTA includes WRKSTRPRSC files, but not empty files
• ShowOOS used the wrong direction pointer
• FSR target IPL always changes IPL type to *NORMAL

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

• SAVDDD / RSTDDD added
• All line descriptions varied off during IPL
• Increase number of concurrent ssh tunnels
• Tolerate slower networks and HMCs
• DMPVFYDTA includes WRKSTPRSC files
• showOOS uses the proper direction
• Prevent a switch if prod does not shut down

The following features were added (or fixed) in the March 27th, 2020 build:

• Allow CHKCSE to skip LUN check
• Allow customers to turn off DS8K ping
• CHKCSE / CHKPPRC –turn off invocation cancel handler before sending final status message
• Log volumes for FSR LUN validation
• Change RTVINF to retrieve GMIR/MMIR direction
• Fix autostart cluster for WRKCSEDTA
• CRTCSECTA –license check for 88 is missing
• Enable TCP KEEPALIVE for EXT2 socket
• RUNSVCCMD doesn't insert extra lines in known_hosts
• Update RLSASPIO to handle MMIR2, MMIR3, and GMIR2
• DMPINF EXTDLOGS(YES) fails on invalid token message
• Use PowerHA sessions flag not honored for flash only sessions
• FSRPort needs to be closed if it’s ever opened
• When retrieving hardware resources, use *REPLACE instead of *ADD
• WRKCSE needs to allow code 82 for WRKCSE
• WRKSTRPRSC *BRM -field is NULL padded instead of space padded
• RTVINF shouldn’t tryto set a DDD lock before ensuring that clustering is active
• Miscellaneous enhancements to DMPVFYDTA
• Add timestamps to log records for RunSshTunnel

To upgrade from any prior version to 4.3 the environments and CSE Data must be recorded, removed, and then recreated after the upgrade. All the controllers and IASP source LPARs in the cluster must be at the same version (i.e. 4.3). 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 controllers will support non-clustered source LPARs running at 4.3 or 4.2, which facilitates upgrading source LPARs in stages.

1. Obtain the savefile from a Lab Services consultant.
2. Ensure the cluster information is in a consistent state:
   - WRKCLU
   - Option 6

3. Ensure no STRFSFLASH or STRFLASH or SWCSE commands are in process.
4. ENDSBS QZRDFSR *IMMED
   - OK if no subsystem running

5. Issue WRKCSEDTA or DSPCSEDTA and record all the environments (opt 5)
6. 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
   - At 4.3, there are no CRG's created with CSE Data for FSR, so ensure that no associated data CRG's exist after deleting the CSE Data

7. On each controller, if the jar file /QIBM/Qzrdhasm/ssh/jsch-0.1.52.jar does not exist, download it from the following webpage and place it in /QIBM/Qzrdhasm/ssh:
   http://sourceforge.net/projects/jsch/files/jsch.jar/0.1.52/jsch-0.1.52.jar/download

8. On each controller, issue the restore command:
   - RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/QZRDHASM43) MBROPT(*ALL) ALWOBJDIF(*ALL) OMITOBJ((QZRDHASM/*ALL *DTAQ))

9. On each controlling LPAR, issue the setup command:
   - SETUPFSR NODEROLE(*CTL)

10. If you updated from 4.1 or older and were using DS8K, enter the credentials for the DS8K:
    - WRKCSECRDL

1. Ensure no STRFSFLASH or STRFLASH or SWCSE commands are in process.
2. ENDSBS QZRDFSR *IMMED
   - OK if no subsystem running

3. Restore the toolkit library:
   - RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/QZRDHASM43) MBROPT(*ALL) ALWOBJDIF(*ALL) OMITOBJ((QZRDHASM/*ALL *DTAQ))

4. Issue the setup command:
   - SETUPFSR NODEROLE(*CTL)

After these steps have been performed, it is recommended that CHKCSE be performed for each environment.

The version and build date is stored in data area QZRDHASM/BUILD. The controllers will support non-clustered source LPARs running at 4.3 or 4.2, which facilitates upgrading source LPARs in stages.

1. Obtain the savefile from a Lab Services consultant.
2. Ensure the cluster information is in a consistent state:
   - WRKCLU
   - Option 6

3. Ensure no STRFSFLASH or STRFLASH or SWCSE commands are in process.
4. ENDSBS QZRDFSR *IMMED
   - OK if no subsystem running

5. On each controller, issue the restore command:
   - RSTLIB SAVLIB(QZRDHASM) DEV(*SAVF) SAVF(QGPL/QZRDHASM43) MBROPT(*ALL) ALWOBJDIF(*ALL) OMITOBJ((QZRDHASM/*ALL *DTAQ))

6. Issue the appropriate setup command:
   - If updating a controlling LPAR: SETUPFSR NODEROLE(*CTL)
   - If updating a source LPAR: SETUPFSR NODEROLE(*PRD)

After these steps have been performed, it is recommended that CHKCSE be performed for each environment.