Automated Space Management

dinesh_deadman · New User Joined: 10 Aug 2007 Posts: 32 Location: Chicago

Hello,

Automated Space Management or Sliding Space Allocation is a new feature in DB2 for z/OS V8. This feature lets you get away without giving SECQTY while you CREATE TABLESPACE or CREATE INDEX. It looked cool to me. However, I would like to know the experiences of others who already used it.

Is it beneficial or not?
Are there any unforeseen problems?
Or is it just another feature with no great benefits?

Any of your experiences with this, would be really helpful.

Dinesh Karthik

senthilssg · New User Joined: 09 Dec 2005 Posts: 64 Location: USA

Hi,

It is really useful feature. It will avoid the -904 resource unavailable due to max extent reached problems and also unnecessary Reorgs for changing Secondary Qty with ALTER TABLESPACE / INDEX statement.

Thanks
Senthil

dinesh_deadman · New User Joined: 10 Aug 2007 Posts: 32 Location: Chicago

Senthil,

You know what, you are the first person to repond to this post. Infact, I posted the same question in multiple forums, but yet to see any response - besides yours. Thank you very much.

Anyway, I request you to be more specific. Do you mean that we would NEVER have -904 for 'max extent reached' problems?

2. 'Unnecessary Reorgs for changing Secondary Qty with ALTER TABLESPACE/INDEX statement' - Once you turn this feature on, you would never have to ALTER TABLESPACE/INDEX for SECQTY?

or am I being too greedy...

Also, could you tell me how this feature handles when you create datasets with 16G size and 10,000 cyls per partition, what would be the SECQTY then?

Any other benefits/problems you have experienced...

I would be really thankful to you if you can answer these questions as like I said, I got to convince my team to have this feature in our shop.

Dinesh Karthik

dinesh_deadman · New User Joined: 10 Aug 2007 Posts: 32 Location: Chicago

Senthil - one more question. Once you have this feature on, you do not have to specify SECQTY while creating TS/IX. However, what if you still mention a non-zero number there? would DB2 take the number you gave or it ignores the number you gave and let this feature 'Automated Space Management' handle this?

I understand that, it takes the number you mentioned. Unless it is 'NOTHING' there, it does not let ASM handle it. Is that correct?

Please clarify.

Dinesh Karthik