IBM Support

Long IPL or IASP vary on in Commit Recovery (C900 2AA1)

Flashes (Alerts)


Abstract

This document provides actions to take if defective PTFs SI79395 (7.3), SI79760 (7.4), SI79764 (7.5) have been applied to avoid a long IPL in commit recovery step (C9002AA1).

Content

PTFs SI79395 (7.3), SI79760 (7.4), SI79764 (7.5) have been marked defective as they can cause a large number of commit definitions to accumulate which may result in a long Commit Recovery step (C9002AA1) during IPL or IASP vary on. 

PSP link: https://www.ibm.com/support/pages/730-defective-ptfs

Corrective PTFs SI80825 (7.3), SI80881 (7.4), SI80882 (7.5) have been provided which prevent further accumulation of commit definitions but do not clean up commit definitions already orphaned since the last IPL. If a defective PTF has been applied to a system, the corrective PTF should be applied as soon as possible. The next IPL or IASP vary on may still take a long time in this step due to the number of commit definitions that have accrued.

Use the steps below to determine if this exposure exists and if further actions are needed to reduce the next IPL or IASP vary on duration. An IPL or IASP vary on should not be attempted until the impact of this issue is understood as the IPL step must run to completion once it has begun.  

Prior occurrences indicate that an IPL or IASP vary on cleans up commit definitions at a rate of 3000 to 7000/minute.  If the count found yields a large number that will result in an IPL duration that is unacceptable, contact your IBM i OS Support for further assistance.

1) Apply the corrective PTF

2) Issue the appropriate DMPSYSOBJ command for SYSBAS and any IASPs

                DMPSYSOBJ OBJ(QTRXLSIX) CONTEXT(QRECOVERY) TYPE(0E) SUBTYPE(A4)

                DMPSYSOBJ OBJ(QTRXLSIX) CONTEXT(QRCY00xxx) TYPE(0E) SUBTYPE(A4) (Replace xxx with IASP number)

3) Display the resulting QPSRVDMP file, go to the bottom and look at the number of the last entry on the left.  

The dump below shows that this system has 43,167 commit definitions.

image of sample spool file

An alternative method for estimating the number of commit definitions is to use the System Service Tools (SST) to get a count of all objects in the QRECOVERY library. This can be done when the system is active or during an IPL or IASP vary on. It is typical to see up to several thousand objects in this library, it is only a problem if there are hundreds of thousands or millions of objects in this library.

Issue STRSST.

Take option 1 to Start a service tool.

Take option 4 to Display/Alter/Dump.

Take option 1to Display/Alter storage.

Take option 1 for Machine Interface (MI) object.

Take option 4 for Permanent context (04).

Take option 1 to Find by object name.

Enter QRECOVERY for SYSBASE or QRCY00xxx (replace xxx with IASP number) and enter the correct ASP number

Take option 4 for Context summary.

Hit F5 to go to the bottom.

The example below shows there are 50,000 objects in the QRECOVERY. All but a few thousand of them will be orphaned commit definitions.

image-20221221092340-1

[{"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":"a8m0z0000000CRZAA2","label":"IBM i Db2-\u003ECommit \/ Rollback"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.3.0;7.4.0;7.5.0"}]

Document Information

Modified date:
26 January 2023

UID

ibm16614215