On Thu, 2 Nov 2006 11:34:59 -0800, Schwarz, Barry A <[EMAIL PROTECTED]> wrote:
>A PDS without members can still be opened so that appears to be a >secondary problem. Is there only one copy of each dataset on the target >system? Are they on the IPL volume? Are they catalogued correctly? >Did the DUMP and RESTORE jobs use the ADMINISTRATOR operand to bypass >security checking? Do the source and target volumes have the same >geometry (we got burned dumping a 9345 and restoring to a 3390)? Is the >target volume at least as large as the source? Did you IPL with the >correct LOADxx member? Are the PARMLIB statements in it correct? Good questions which I should have put in the original: - Each PDS that is empty cannot be opened at all. Even trying to create a new member via ISPF gives: I/O error, insufficient virtual storage, or other BLDL error. - Nope, the target system has the sam name datasets except that its only really a system used to build the real target system. There is no cataloging of datasets being done as these are full disk restores - ADMIN was used - Disks are all exactly the same - IPL was done correctly (the source system is sitting next to me so I can check it as I do everything) and the PARMLIB is all correct We're now trying a couple of other things but thanks for all the help. Seb ---------------------------------------------------------------------- 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
