CA RC/Migrator
CA Endevor SCM Interface
DB2 Administration
CA RC Compare for DB2 for z/OS
CA RC Extract for DB2 for z/OS
CA RC/Query
CA RC Secure for DB2 for z/OS
CA RC Update for DB2 for z/OS
CA Database Analyzer for DB2 for z/OS
CA Fast Unload for DB2 for z/OS
CA Fast Check for DB2 for z/OS
CA Fast Index for DB2 for z/OS
CA Fast Load for DB2 for z/OS
CA Rapid Reorg for DB2 for z/OS

In Thread Terminator DSNZPARM Display, MAXRBLK value is displayed as 12500 but in DSNZPARM source was specified as 400000.

DESCRIPTION VALUE KEYWORD

------------------------------------------------ ---------- -------

Max 32K RID blocks allowed. 12500 MAXRBLK

DESCRIPTION VALUE KEYWORD

------------------------------------------------ ---------- -------

Max 32K RID blocks allowed. 12500 MAXRBLK

Release:

Component: PTT

Component: PTT

The MAXRBLK DSNZPARM actually specifies the amount of storage in Kilobytes that is needed for the RID pool. When DB2 DSN6SPRM macro is assembled, the value of the MAXRBLK DSNZPARM itself is not stored. Instead, the value of the MAXRBLK DSNZPARM is divided by 32, giving the max number of 32K RID blocks. The proof is in the output for the DSNTIZA step in the DSNTIJUZ job, where you'll find this:

0000E8 000030D4 ... 115+SPRMRMAX DC AL4(400000/(8*4)) ... # OF RIDPOOL RIDBLKS @K0330

So Thread Termination/Dynamic DSNZPARM (PTT) is actually displaying the correct "Max 32K RID blocks allowed" value of 12500, which is derived from the MAXRBLK value of 400000. Note that 400000/(8*4) = 12500.

0000E8 000030D4 ... 115+SPRMRMAX DC AL4(400000/(8*4)) ... # OF RIDPOOL RIDBLKS @K0330

So Thread Termination/Dynamic DSNZPARM (PTT) is actually displaying the correct "Max 32K RID blocks allowed" value of 12500, which is derived from the MAXRBLK value of 400000. Note that 400000/(8*4) = 12500.