We are in the process of trying to build a second diskpool and tapepool to
have collocation set to *no for our smaller servers.  All of our disk
volumes were previously assigned to our original diskpool.

We defined a second tapepool with collocation set to no.
We then defined a second diskpool set with migration to the new tapepool.
We had no volumes in the diskpool - so we set 4 of the 23 volumes in our
original diskpool to read only - thinking that the disk volumes would go
empty today and therefore we could remove them from diskpool and add them to
our second diskpool.

Last night during our normal backup that should have gone to the diskpool
went to the tapepool instead.  There is lots of room on our diskpool - we
have cache set to *no.

Does anyone have any idea why this would have happened?  Did marking the 4
volumes as readonly cause this in some way?

Thanks
Nona Mire
Senior Systems Analyst
Our Lady of Lourdes Regional Medical Center
Miren AT lourdesrmc DOT com <mailto:Miren AT lourdesrmc DOT com>