To get to the new volumes are you using DEL/DEFs or letting SMS manage the space for DB2 using STOGROUPS.
What I know about DB2 and Extending can fit on a pin, however, here goes. Depending on the VERSION of DB2 if you do an ADDVOL but did not have enough canidate volumes in the list, they may or maynot be used. The UCB and UCBEXT control blocks tells the system how many volumes can be added. In the UCB it is 10 (I think), and the UCBEXT are 5 each. If you define the DB2 DB/TS/TB with VOL(* * * * * * * * * * * *) you would get the UCB + UCBEXT. If you define VOL(* * * *) then you only get the UCB and not the UCBEXT. In which case, when you try to extend it will not be able to. Only the REORG or possibly the stopping and starting of the DB will work. I am sure if I am in error in this, there will be correction information passed ;-). But this is my understanding of ADDVOL and DB2 extensions. I know at some point, IBM correct the ADDVOL in DB2 to get another UCBEXT without have to cycle or reorg the data base. The DB2 List might have better information on this issue. Lizette Koehler > >I am facing problem in production DB2. > >5 Volumes were configured for Database in storage group while creation of >tablespace A. > >Later in 1 month these 5 volumes were full and added another 2 volumes, >however Tablespace A could not extend to these newly created volumes. > >After performing REORG for Tablespace A , Tablespace VSAM dataset got >extended to these newly created volumes. > >Is it necessary to do REORG of Tablespace everytime you add volumes in >storage group. > >*Note : Tablespace were created using Storage group and not using volumes >parameter.* >** >What could be the reason for the same ? Please reply urgently > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
