Willie, As you've said that you have FDR, take a look at Section 80.12 titled "Data Movement Between Different Device Devices".
Stephen Mednick Computer Supervisory Services Sydney, Australia > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter > Sent: Friday, 24 March 2006 12:35 PM > To: [email protected] > Subject: Re: 3380-3390 Conversion - DISAPPOINTMENT > > Thanks Mike for the info. We have FDR. I presume it should > work just the same. > > Thanks for answering my SOS. > > Mike Bell <[EMAIL PROTECTED]> wrote: > VSAM is VSAM - so DB2 and IMS that is on VSAM can be moved > with DF/DSS or any other tool. someone already said that. > IMS that is on OSAM is not device dependent but the blksize > was probably chosen for 3380 optimum - The DBA's will have to > fix it later. If you mark the old volumes as disabled for new > allocations, HSM migrate and recall will move to the new > packs. I have done it both ways. I would recomend taking your > biggest files and moveing them with DF/DSS. SMS will scatter > the new allocations accross all the packs so it doesn't > really matter how you do it. > DB2 image copies, archive logs, IMS image copies and logs are > all QSAM and idenpendent of device. blksizes may not be > optimum but I doubt it is worth changing. > > The single biggest issue I remember was blksize on loadlibs. > After much discussion, we moved them manually with copymod to > set new blksizes. > > Mike > > ---------------------------------------------------------------------- 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
