If we want to alter a series of tablespaces in a database, for example to move them to another bufferpool, change the Close Rule, compress them, or set them to LOGGED/NOT LOGGED, in Db2 Administration Tool we have to set up and execute the ALTER TABLESPACE statement for each tablespace to be altered, going through panels ADB21 (to choose the database), ADB21D (choosing command S) ADB21S (choosing command AL), ADB21SA (choosing what to alter), arriving at ADB2PSTM to execute the alter for each tablespace. That is a repetitive set of actions for each tablespace.
Even if we use WSL, we have to add one ALTER TABLESPACE statement to a WSL, edit the WSL to include the other tablespaces we want to alter and run the WSL in batch.
For using WSL. we calculate that to be hitting around 10 screens from panel ADB21 inclusive, followed by issuing the SUBMIT on the generated WSL job.
Our workaround is to set up and issue the ALTER TABLESPACE statements through SPUFI, where we can type in one alter statement, repeat it as many times as necessary, alter the tablespace names accordingly, add a semi-colon after each statement and run them.
|Who would benefit from this IDEA?||Anyone having responsibility for issuing the ALTER TABLESPACE statement|
How should it work?
When we have gone through panels ADB21 (to choose the database), ADB21D (choosing command S) ADB21S (choosing command AL), ADB21SA (choosing what to alter) and have arrived at ADB2PSTM to execute the ALTER TABLESPACE statement, we edit the statement in ADB2PRED , repeat it as many times as necessary, alter the tablespace names accordingly, add a semi-colon after each statement and F3 back to panel ADB2PSTM .
At this point Db2 Administration Tool should recognise that there are now multiple statements to execute and offer option A -
(Add an A for all stmts. A is supported for options 1, 3, and 4.
For example 1A - Execute all statements):
We calculate that to be hitting around 7 screens from panel ADB21 inclusive, followed by issuing the proposed new option 1A.
An alternative enhancement would be for the user to type AL next to the first tablespace to be altered followed by the '=' sign on subsequent tablespaces to be altered. This will indicate to Db2 Administration Tool that the same alter action is to be carried out against all of the tablespaces identified. The user will then be directed to panel ADB21SA (to choose what to alter), make the choice and Db2 Administration Tool will build the alter statement for all of the tablespaces identified, using the user's alter option.
We calculate that to be hitting around 5 screens from panel ADB21 inclusive, followed by issuing what would have to be new option 1A.
|IBM's success depends on gathering feedback from customers like yourself. Aha Ideas Portal is the third party tool through which IBM Offering Managers gather feedback from customers such as yourself.|
|IBM is a global organization with business processes, management structures, technical systems and service provider networks that cross borders. As such, the information collected through Aha Ideas Portal (Customer Name, Customer Email Address) will be stored by them in the United States, and handled only as per IBM's instructions and policies. Your data (Name and Email Address) will NOT be shared with other IBM customers.|
|In order to safeguard your information in Aha, do not leave your workstation unattended while using this application, log off after using it, and print only if necessary. If you need to make a hardcopy, remember to pick up the print-out immediately, keep it under lock, and destroy it immediately when no longer needed.|
|NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions|