zD&T comes with an ADCD system, which used to lag behind 12-18 months (when I worked on an RDT system) about 2 years ago.
ADCD does not have *any* z/OS support as we know it (when you only have an RDT system, you cannot order ptfs). The process of 'migrating' to a new ADCD version is cumbersome to say the least because you have to migrate all applications to the new system, including any customization you may have done. The setup does encourage a terrible mixing of applications and systems, at least if you're not a sysprog. It did not come with SMS set up. I made the effort of fixing the ADCD system to make it maintainable. Which means that I completely restructured the system setup (starting with SMPE and the sysres layout and including a better USS setup). I also fixed the RACF database and set up a simple SMS/HSM environment (only L1 migration). Once you've done the initial effort of cleaning it up, you can order ptf refreshs on your 'real' :-) z/OS and distribute them like you would to another lpar. After that, an RDT system was just another lpar to roll things out to. An ADRDSSU volume dump can get ftp'd to the ADCD system where it can get restored to the emulated 'DASD' (Linux files). I got lucky in that the upgrade to new z1090 code got done by someone who knew what he was doing in Linux. For day-to-day operations you need so few Linux commands that even I could handle that. I was even able to define an EAV volume for testing purposes. It is discouraged to use them heavily because there is no such thing as HiperPAV (every 'volume' is emulated as a 'simple' Linux File), but testing was good. Check the archives, I talked about the ADCD shortcomings in the past. (I even have a large list of what should get done or get done better flying around somewhere). Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
