Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Moving\s+DB\,\s+Etc\.\s+for\s+ADSM\/MVS\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Moving\s+DB\,\s+Etc\.\s+for\s+ADSM\/MVS\s*$/: 3 ]

Total 3 documents matching your query.

1. Moving DB, Etc. for ADSM/MVS (score: 1): Author: Frank Rehor <Frank.Rehor AT CLOROX DOT COM>; Date: Wed, 11 Sep 1996 17:52:15 -0700; 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 contr; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-09/msg00167.html (11,077 bytes)
2. Re: Moving DB, Etc. for ADSM/MVS (score: 1): Author: Bill Colwell <bcolwell AT CCLINK.DRAPER DOT COM>; Date: Thu, 12 Sep 1996 09:28:00 -0400; I suggest using the ADSM approach. Allocate, format, define (don't extend) the new db & log files, then do adsm delete commands on the old db & log volumes. The volhist and devcon files can be moved; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-09/msg00177.html (11,688 bytes)
3. Re: Moving DB, Etc. for ADSM/MVS (score: 1): Author: Bruce McClure <bamcclure AT AMOCO DOT COM>; Date: Thu, 12 Sep 1996 14:00:33 -0500; 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 seem; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-09/msg00199.html (11,571 bytes)

Current List: 1 - 3
Page: [1]