I forgot the second question. Indeed DIRMAINT refuses to move a RESERVED minidisk. Such a minidisk is special, one cannot move the singe file on it using COPYFILE. A RESERVED minidisk has a somewhat special format: the records of the single file on the minidisk will never move around, this allows SW like SFS or DB2/VM to bypass the CMS filesystem and directly tell CP which block(s) to read/write using IUCV *BLOCKIO.
If you installed DFSMS, (free feature of z/VM) you can issue DFSMS MOVE to move such a reserved minidisk (with the help of DIRMAINT and DGTRSVnn servers), or manually with the DFSMS COPY command. Otherwise, the most easy method is indeed the use of DDR. DIRMAINT could use DDR too, or Flashcopy (DS8000) but there seems to be no code in DIRMAINT to handle it. DIRMAINT will use DFSMS COPY is DFSMS is available (as it is much faster than FORMAT + COPYFILE), but I think it still rejects RESERVED minidisks. (beside DFSMS and DDR a pure manual copy is possible too: reserve the new disk and then use PIPE FILEUPDATE to copy the records one by one from source to target file). 2008/11/19 Bruce Hayden <[EMAIL PROTECTED]>: > If you know the workunit number that failed, then this will retry it: > DIRM WORKUNIT nnnnnnnn RETRY > If you don't know the workunit number, DIRM DATAMOVE DISPLAY ERRLOG > will send you a file with the number in it. > > I don't understand your question about reserved.. Does the disk > appear in EXTENT CONTROL? Otherwise, DIRMAINT won't allocate anything > on it.. > > > On Wed, Nov 19, 2008 at 9:59 AM, Florian Bilek <[EMAIL PROTECTED]> wrote: >> Dear all, >> >> Some questions on Dirmaint: >> >> In case the DATAMOVE fails to links a minidisk that shall be moved because >> for example the owner has still linked to it, the transaction gets pending >> and at some time DATAMOVE machine is retrying the operation. Is there a >> command to resume the operation immediately? >> >> Another issue: I tried moving Logfiles from a CMS Fileserver to another >> minidisk because the DASD volume it was residing shall be cleaned. Dirmaint >> is rejecting this because the disk is RESERVED. What is the problem why >> Dirmaint cannot move such disks? I did it manually with DDR so why can't >> DATAMOVE this not for me? Is this room for future enhancements? >> >> -- >> Best regards >> >> Florian Bilek >> > > > > -- > Bruce Hayden > Linux on System z Advanced Technical Support > IBM, Endicott, NY > -- Kris Buelens, IBM Belgium, VM customer support
