>>> On Tue, Jun 24, 2008 at 8:01 AM, in message <[EMAIL PROTECTED]>, "Walters, Gene P" <[EMAIL PROTECTED]> wrote: > We use DFDSS to do preliminary full volume backups of Linux volumes. In > doing so, we have had a few problems backing up some of our mod-9's that > we setup as minidisks, as opposed to dedicated. For some reason, some > of our volumes will show a z/os dataset name such as > LINUX.VLX114B.PART0001.NATIVE, some do not show a z/os dataset name at > all. It is the one that do not show a z/os dataset name, that we have > problems backing up. -snip- > How does that name get generated on the Z/OS side?
It is created by running the Linux dasdfmt and fdasd commands. > Why does it get generated on the Z/OS side for dedicated dasd, but not > for mini-disks? Because for mini-disks, the z/VM systems programmer does not allocate cylinder 0 to the Linux guest. So, when Linux writes the VTOC on what it thinks is cylinder 0, it is really writing it somewhere else. > How can I get it on the Z/OS side for the mini-disks? It should have been created by z/VM when it was CP formatted by the z/VM systems programmer. If it was not, they need to look at how they're initializing the volumes. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
