On Thursday, 04/17/2008 at 07:36 EDT, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > ok, your objection is principally correct, but first the message you > mentioned appears always also when you restore a cylinder range from a > 530RES DDR DUMP to a correctly defined minidisk with RESTORE xxx TO yyy > REORDER 0. So this message ist not necessarily a problem. In fact it > appears very often and if you restore multiple DASDs or mdisks I'm sure > everyone will enter the PROMPT OFF and put the necessary commands in a > DDR PARM file.
If you get HCP725D (or HCP699I with PROMPTS OFF) when a RESTORE or COPY fits on the target volume with no truncation, with or without REORDER, that would be a bug (IMO, of course). Given a source disk of 5 cyls: COPY ALL REORDER x fails with a syntax error COPY 0 TO 4 REORDER 1 (to a 5 cyl target) fails COPY 0 TO 3 REORDER 1 (to a 5 cyl target) works COPY 0 TO 4 (or ALL) to a smaller volume gives HCP725D COPY 0 to a smaller valume gives HCP725D COPY (anything) to a smaller volume gives HCP725D I don't like HCP725D being displayed when DDR can perform the requested operation with no truncation. (Of course, if all the things I don't like in the world were fixed, what would I do? :-) ) But I wouldn't call it in unless I was on a supported level of VM. I don't think an extended support contract on z/VM 4.4 covers this. Sorry. I've opened an internal problem report on this. If Development agrees that there is a problem that needs to be fixed, it will find its way into a future release. > But the main reason why I think that DDR should abend or > at least give a return code other than zero is, that when you RESTORE > ALL to a minidisk which is too small, the only result can be garbage. I don't agree. DDR should not make value judgements on your RESTORE or COPY commands. It should simply tell you if it cannot do as you asked. If you choose to ignore the warning, well, that's not an issue with DDR. Alan Altmark z/VM Development IBM Endicott
