I seem to remember that DB2 would not alter add volume if the volume was
already in the allocation. I think the crucial error is not having the DB2
stogroup defined as colume (*) - which will never match an existing volume.
That will force it to the SMS allocation.
Mike
On 9/20/06, Robert Lawrence <[EMAIL PROTECTED]> wrote:
Jacky,
I believe for DB2 stogroups to use SMS the DB2 stogroup should be
defined
as VOLUMES('*') for it to work the way you wish with the proper ACS
routines. We are not SMS managed so I am not sure how to accomplish this.
I
would try an ALTER STOGROUP STGP1 REMOVE VOLUMES (PDB001) followed by an
ALTER STOGROUP STGP1 ADD VOLUMES('*'). Look it up in DB2 SQL REFERENCE.
----------------------------------------------------------------------
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
