Simple answer is - No
Partitioned opbjects cannot get a second dataset as they are, by definition, single dataset partitions. Your best hope is to convert to PBR RPN and then you can very simply change the DSIZE of any part or part index with an ALTER. On-line, instantly with no rebind or reorg required!
Cheers!
------------------------------
Roy Boxwell
Senior Software Architect
Software Engineering GmbH
Duesseldorf
+4921196149675
------------------------------
Original Message:
Sent: Mon September 02, 2024 01:44 AM
From: Srini Atmakur
Subject: Maximum Partition Size of a Partitioned (non-UTS) tablespace defined with DSSIZE 2G LARGE keyword
Hi,
We have a partitioned (non-UTS) tablespace defined with DSSIZE 2GB & LARGE keyword with 64 partitions in our Db2 for z/OS subsystem. The partitions of this tablespace are about 90% full and are growing every day. Will Db2 allocate & use a second dataset for each partition once the first dataset of the partition becomes full? We are planning to convert this tablespace to UTS, but, it has to wait a few months per prioritization.
I appreciate your responses in this regard.
Best,
Srini Atmakur
atmakur@us.ibm.com
------------------------------
Srini Atmakur
------------------------------