Ed, how would you change this post install? Does this need to be done during an upgrade/install process, or can it be changed after the fact?
* action taken
Development has just shipped a new function PTF which I believe resolves this issue.
APAR PH12893 / PTF UI63542
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1 *
* and above *
****************************************************************
* PROBLEM DESCRIPTION: 1. The applgrp data tablespaces are *
* created with SEGSIZE 64. SEGSIZE is *
* deprecated. *
* 2. The applgrp data tablespaces are *
* created with MAXPARTITIONS 1. *
****************************************************************
1 ARGSEG was specifying SEGSIZE 64
2 ARGSEG was always using 1 for the MAXPARTITIONS value
COMMENTS:
1. ARGSEG will no longer specify SEGSIZE 64
2. ARGSEG is enhanced to determine a MAXPARTITIONS value when a
new ars.cfg setting is specified:
ARSMVS_DB_DSSIZE
Specifies the value to use for the DSSIZE value for the
application group data table tablespaces. This must be a
power-of-two in the range of 1 - 256.
When not specified, the application group data table tablespaces
\ will be created with a MAXPARTITIONS 1, and the PRIQTY and
SEQTY will be chosen based on the max rows for the application
group. The INDEX will be created with a PRIQTY and SECQTY also
based on the max rows.
When ARSMVS_DB_DSSIZE specifies a valid value, that value will
be used in the DSSIZE N G clause when creating the application
group data table tablespace. Additionally, the PRIQTY and
SECQTY will default to -1, and the MAXPARTITIONS will be set
based on the application group max rows value. Any index
created will specify a PIECESIZE based on the max rows, and
default to a PRIQTY and SECQTY of -1
Regardless of ARSMVS_DB_DSSIZE being specified or not, the
ARSMVS_MAXROWS_PRIQTY, ARSMVS_MAXROWS_SECQTY,
ARSMVS_NOMAXROWS_PRIQTY, ARSMVS_NOMAXROWS_SECQTY,
ARSMVS_MAXROWS_INDEX_PRIQTY, ARSMVS_MAXROWS_INDEX_SECQTY,
ARSMVS_NOMAXROWS_INDEX_PRIQTY, and ARSMVS_NOMAXROWS_INDEX_SECQTY
can be used to override the PRIQTY and SECQTY values chosen by
CMOD.
For example, with ARSMVS_DB_DSSIZE=4 and an applgrp with a max
rows of 50,000,000, the tablespace might get created with:
CREATE TABLESPACE DAA23 IN ARSDBA10 USING STOGROUP SYSDEFLT
PRIQTY -1 SECQTY -1 MAXPARTITIONS 2 DSSIZE 4 G BUFFERPOOL BP0
and the index with:
CREATE INDEX ARSUSE10.DAA23_0 ON ARSUSE10.DAA23
( REPORT_NUMBER ) USING STOGROUP SYSDEFLT PRIQTY -1 SECQTY -1
BUFFERPOOL BP0 PIECESIZE 512 M How this works is it figures out the number of bytes for a row for the applgrp, then the number of those size rows in a 4K or 32K page. From the number of rows per page and applgrp max rows it calculates how many pages it needs. The number of pages times page size is the amount of space it needs. It divides that by the dssize to get the max partitions.
This is heavier into Db2 than I usually get. Hopefully your DBA's can sort this all out for you.
Ed
Show Posts
