When DDR sees a discrepancy in the sizes of the disks, it usually requests permission to proceed unless you have specified PROMPTS OFF, in which case, it behaves as though the permission were already given.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: Monday, April 14, 2008 10:50 AM > To: [email protected] > Subject: curious behaviour of DDR RESTORE ALL > > @moderator: Sorry, I have sent the message first with the > wrong sender email. Please delete the mail with the wrong address. > > Hi listers, > > I have found ou a curious behaviour with DDR Restore. If had > the following situation. I have backed up a VSE volume with > DUMP ALL. At the test recovery site I have restored it with > RESTORE ALL. I thought all mdisks started at physical > cylinder 1 so I defined the mdisk accordingly in the USER > DIRECT, but this volume was historically a fullpack minidisk > at the original site. I would have expected that the restore > will abend with the last cylinder not being written, but DDR > told me that cylinder 0 to 3337 was restored and dump ended > with RC=0. The only thing which you could see was the message > that source device is larger than input device, but this > message appears also if you restore a 50 cyl cms mdisk from a > 530RES DDR dump with RESTORE xxx TO yyy to a correctly > defined 50 cyl. mdisk. So this cannot be seen as an error > message. I have tested it for demonstration with a dump of a > 5 cyl mdisk and restored it with RESTORE ALL to a 4 cyl > mdisk. My problem is that the customer has no support > contract with IBM. I would say this is a defect and want to > open a PMR on it, but my customer is surely not willing to > pay for that if IBM says that's no defect for whatever > reason. I would be interested in Alan's opinion what I should > do. I have attached the log of my above mentioned test which > you can easily repeat. > > -- > kind regards > Franz Josef Pohlen >
