John, a first reaction to this would be that it is possible, but would require a lot of work. Due to the fact that some ADSM DB entries are platform specific, you cannot just move the database between your MVS and VM. The route to follow would be an export of the original server, and an import on the VM system. One advantage in this environment is that you can share DASD, which means that you might be able to use this DASD as export and import medium . For the tape volumes, I believe there will be an issue that you cannot read MVS/ADMS created tapes on a VM system. However, I never got real confirmation for this, so if someone tried it and it works, great. Also, watch out for server levels: this will only work when your ADSM running on MVS is at a lower or equal level that the one available on VM. I think one of my customers tried the reverse scenario by just "moving" the tapes (created a copy storage pool on the VM machine, and used that one to restore it on the MVS side). Didn't receive any feedback if this worked ... . I'll check. >I have an ADSM 3.1 server running on OS390 2.8. The OS390 2.8 machine, a >9672-R45, is running pretty much at capacity. Actually, we've shut down ADSM >and find that we are at about 90-95% CPU utilization. Not a lot of room for >ADSM. We have a shared DASD environment between our OS390 and VM machines. >The VM machine is a 9672-R35 with about 30% CPU capacity to spare. So, my >question is.... >Other than ADSM server licensing and software installation, how difficult >would it be to install ADSM 3.1 on the VM system and bring it up there using >the existing ADSM DBvolumes and Storage Pools? >I know there are some issues involving the life expectancy of both ADSM 3.1 >and *SM on any VM system. Consider this a brainstorming question. Any >suggestions and comments would be most welcome. Best regards, Wim. Wim Feyants IT Specialist - Tivoli Storage Manager support - IBM Belgium Tivoli ADSM certified consultant 32-2-2253825 [EMAIL PROTECTED]
