Ragged Flash and Live Partition Mobility – Modify CHGASPA to use multiple serial numbers

• 1. Problem description

Currently at V7R5 the CHGASPA command with No commit boundary set to yes, we only have the option to enter a single serial number making restoring to a Recovery LPAR that has been migrated using LPM would not cut the ragged journal entry as the serial number is different.  We cannot recover a Ragged flash from a SafeGuarded Copy that was captured using the alternate serial number of our LPM servers as easily and as quickly as we do with the correct serial number.

• 2. Current workaround

Add another robot job or amend the current one to include two CHGASPA commands with the separate serial numbers and only allow the serial number where the recovery LPAR is residing to run, manually swap the CHGASPA when we have migrated using LPM.

• 3. Proposed resolution

Modify the CHGASPA command to allow multiple serial numbers so when we IPL the Ragged journal entry is created no matter what Server Serial number the LPAR resides.

• 4. Business impact

We would not be able to recover an LPAR using ragged flash as easily as we would if the ragged journal entry had been cut during the IPL, we have been working with LAB Services to produce a semi-automated recovery based on the ragged journal entries, and with our requirements to recovery an LPAR in case of a Cyber attack/bad actor ASAP this will slow things down

• 5. Which release do you see the problem on?

V7R5