On Mon, 22 Nov 2010 14:57:15 -0600, Arthur Gutowski <[email protected]> wrote:
>On Wed, 17 Nov 2010 17:40:10, Mark Zelden <[email protected]> asked: > >>... What's wrong with this: >> >>FDR: >> >[...useful JCL removed for brevity...] >> >>DFSMSdss: >> >[...useful JCL removed for brevity...] >> >>BTW, for the other thread I saw start... this is a DFDSS logical dump. :-) > >If you're weird, like us, is that doesn't capture the IPLText and PAGEDUMP >dataset on &SYSR2 for SADump. We keep it on the logical SYSRES bundle to >ensure SADump stays in sync with z/OS. We rebuild it on our staging volumes >as directed by ++HOLD ACTION, once and only once. Then it just rolls. > >This makes physical copy a requirement. Since we're never IPLed from our >staging SYSRES, logical copy is not a requirement. Now, if we used DSS >instead of FDR, we could copy track zero first, then logical copy all other >datasets on the voume with RENAMU/REPLACEU, but we use FDR, and I have >seen no provision therein for copying one and only one track. At least not >with PGM=FDR and COPY TYPE=FDR. > We use 2 3390-9 for the IBM sysres and the zFS files (formerly HFS) are on their own volume. Full volume copy is done for volume #1, but the zFS dsns are logically copied to facilitate rename to match the sysres as part of the dsn. I used to use indirect cataloging with HFS and no sysres qualifier in the DSN until a 2nd volume was needed. My SADUMP is on the maintenance version of my zFS vol (sysres #2). I only rebuild it when needed. So the address is always the same and that makes it easy for operations to drag & drop an activate profile for SADUMP that is in it's own SADUMP customized group in the HMC. So a new profile gets created once per new OS and then the icons for each LPAR (current activation profile) get updated as the new OS rolls out. (BTW, the options use the HMC for console and no responses are required per SADUMP best practices). Since the SADUMP volume changes with each new sysres set, I assume your operators (or someone) must have procedures to manually IPL SADUMP if needed, which takes extra time. Our normal IPL process requires the operator to enter the load address (and load parm, but that normally doesn't change), but that isn't when time is a critical factor. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- 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
