Thanks Jim, I'll look into the "RECOVER" option as soon as I get back to the home office. As for the quick fix here at the D/R site I was able to use the HMC to reset the OSA card to the factory default which was good enough to get my z/VM TCP/IP stack talking to the outside world.
Tom -----Original Message----- From: The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU Sent: 4/20/2007 6:58 AM Subject: Re: Install mistake I'm doing a similiar thing right now on a z/VM 5.2 install. I screwed up the RACFVM 200 and 300 mdisks and have found that there is a "RECOVER" option on the INSTALL EXEC. You could, mdisk by mdisk, load what you need. What you'd need to look for, however, is whether things like the PPF file is on the MAINT 51D disk. As a related FYI, however, I'm working with VM support right now to get past a "gotcha". I have all of 5.2 on a single 3590 cartridge. I need to recover the 281st and 282nd files from the SDO cartridge. INSTALL uses DDR. DDR's SKIP parameter accepts a maximum of 255. I need to skip 280 files for the RACFVM 200 disk. I should know in a little while if the new DDR will cure the problem. Jim Rich Smrcina wrote: > Perhaps part of the service procedure in the program directory will help: > http://www.vm.ibm.com/progdir/4osasf42.pdf > > Huegel, Thomas wrote: > >> This may be a lot easier than I thought. >> It appears all of the code is on 2VMVMV20 mdisks all I have to do is run >> a SES command to move them to production 200, 400 etc mdisks. >> >> I am at a D/R site with limited resources, can anyone suggest what the >> SES command might look like? >> >> Thanks >> >> -----Original Message----- >> From: The IBM z/VM Operating System >> To: IBMVM@LISTSERV.UARK.EDU >> Sent: 4/19/2007 3:29 PM >> Subject: Re: Install mistake >> >> Two alternatives: >> If you have the tape layout, the you can restore the minidisks one by >> one. I think each minidisk was separately DDRed. >> >> If not: then you need to restore a whole VM and you use the directory >> you just showed to extract the minidisks you want and DDR them from the >> new packs onto minidisks of your current VM. >> e.g. (after the restore to get MDISK 2C2 3390 3334 004 430W01 ) >> LINK 2VMVMV20 2C2 222 M (current VM) >> ATTACH restored_430W01 * 111 >> DDR >> SYS CONS#IN 111 DASD#OUT 222 DASD >> COPY 3334 3337 reorder 0 >> >> And, you need more than OSASF 200 and 400: the 2VMVMV20 user contains >> the real SW. >> As for the link error: in the past, OSA/SF installed a stupid PROFILE >> EXEC that tries to link to non-standard minidisk addresses. No need to >> a MAINT 19A for example. I don't know if this is better in z/VM V5. >> -- >> Kris Buelens, >> IBM Belgium, VM customer support >> >> > > -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
