TDMF has worked fairly well for us for migrating between control units without taking an outage. Just did so within the last month matter of fact. I thought it was fun (and useful) that D IPLINFO shows both the original address you IPL'ed from as well as the current. I don't remember noticing that last time we did a TDMF migration (~4.5 years ago), but I may simply not have looked.
IEE254I 06.33.28 IPLINFO DISPLAY 326 SYSTEM IPLED AT 11.20.21 ON 05/19/2013 RELEASE z/OS 01.12.00 LICENSE = z/OS USED LOAD0J IN SYS1.IPLPARM ON 04678 ARCHLVL = 2 MTLSHARE = N IEASYM LIST = (MJ,L) IEASYS LIST = (MJ) (OP) IODF DEVICE: ORIGINAL(0624A) CURRENT(04678) IPL DEVICE: ORIGINAL(06252) CURRENT(04304) VOLUME(RES600) Non-disruptive application releases take a little more work. I believe it's not necessarily impossible though, depending on how the application is architected and how much effort you want to put into it. Scott Chapman On Wed, 17 Jul 2013 20:59:57 +0200, R.S. <[email protected]> wrote: >Q3. How do you move your datasets from old DASD to a new one? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
