Frank, just based upon the number of changes required..it is less
risky to alter the ACS logic and use DFDSS to relocate the current
files while ADSM is down. Creating a entirely new environment seems
error prone to me. For what its worth. :)


______________________________ Reply Separator _________________________________
Subject: Moving DB, Etc. for ADSM/MVS
Author:  ADSM-L (ADSM-L AT VM.MARIST DOT EDU) at unix,mime
Date:    9/11/96 7:52 PM


When we initially installed ADSM/MVS we placed all of the ADSM server dasd
files (DB, Storage Pools, Volume History, Device Config, etc) under DFSMS
control.  We now want to remove them from SMS control so that if we have to
go offsite to recover only a client paltform, e.g., and not the whole shop,
we can do so with a single pack MVS operating system and not need DFSMS,
et al.  The question is how to make this shift.  Would it be easier/better
to leave the current file names, update the ACS routines to make them non-
managed, and use something like DFDSS to move the files to non-SMS volumes
with ADSM shut down?  Or, allocate new files with non-managed names, vary
the old files offline and let ADSM move the data to the new files? Or...

Has anybody done anything like this or have any suggestions on either what
to do or, more importantly, what not to do?

Thanks,

Frank Rehor
The Clorox Services Company
(510) 847-4814
frank.rehor AT clorox DOT com