IBM Support

Ragged flash



FlashCopy services are a popular technology for taking a snapshot of an IBM i and replicating it to a copy node.
With IBM i 7.5, the FlashCopy user has new options to better control how the copy will be used.


If a FlashCopy is taken when database transactions are pending, the pending transactions are rolled back on the copy node when the node is IPLed. The rollback behavior is not ideal when the client wants to choose to apply or remove journal changes.

With IBM i 7.5, the Change ASP Attribute (CHGASPA) command is enhanced to include the No commit boundary (NOCMTBDY) parameter.

Specifies whether IPL or vary on of the specified ASP device (ASPDEV) or ASP number (ASP) on the system with the specified Serial number (LPARSER) and Partition identifier (LPARID) should leave partial transactions on all user journals with open commit cycles.
*NO (default)    
    Normal Commit Recovery processing will be performed during IPL or IASP vary on.
    IPL or IASP vary on will leave partial transactions for any objects with open commit cycles for all user journals. Pending changes will remain in the objects, and additional recovery is required to use objects marked with partial transactions. This is only honored for the subsequent vary on.
A reference document with detailed instructions on how to use this enhancement is available here:  Ragged Commit Boundary.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"IBM i 7.4","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
16 May 2022