I struggled with this too. The full-pack disks for Linux write out a 
semi-standard VTOC that z/OS understands so it can see the various partitions 
as data sets that it can backup individually. If the minidisk starts anywhere 
other than cyl 0, Linux will put a VTOC there but it isn't in the right spot 
for z/OS to find it (not at cyl 0), so no data set names show up.

Did you see this section in the DFSMS manual? That's where I eventually found 
some of this explanation when I was trying this out.
http://tinyurl.com/6cj6rm

We ended up just taking full volume dumps if needed and not trying to use the 
data set name. Although to make this easier we only give each Linux whole 
disks. This might have to change as disk sizes get larger.
__________________________________
Tom Stewart
Infrastructure Analyst
John Deere - z/OS Support Services
__________________________________




-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of LJ Mace
Sent: Tuesday, June 24, 2008 7:54 AM
To: [email protected]
Subject: Re: DFDSS Backups

I'll try to answer some of the question.
> How does that name get generated on the Z/OS side?
When the pack is backed-up the jcl has a specific pack ddname associated with 
it ie(DSN=PROD.BACKUP.FULLVOL.VMUS01(+1) and in your case 
LINUX.VLX1047.PART0001.NATIVE and this is more than likely a full volume 
backup. Also they are pointed to a specific vol ser in your case I'll guess the 
pack name is VLX1047  This is usually a gdg so after a certain number of 
backups older ones roll off Then next two questions I'll take a stab at:
I going to assume the mini disks are only a portion of your 3390 so I'm going 
to guess that the mini disks are backed-up but on a different vol ser  or it is 
a logical backup . This means that only a portion/certain dataset is 
pulled(backed-up) but I don't know how this could be unless your z/os guys are 
backing up certain cyl/trk numbers.
We do full pack backups here.
I hope this helps
Mace


--- On Tue, 6/24/08, Walters, Gene P <[EMAIL PROTECTED]> wrote:

> From: Walters, Gene P <[EMAIL PROTECTED]>
> Subject: DFDSS Backups
> To: [email protected]
> Date: Tuesday, June 24, 2008, 8:01 AM
> 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.  When I do an fdasd with the P option on the
> problem volumes, it looks like this:
>
> Cylinders ............. 10016
> Tracks per cylinder ... 15
> Blocks per track ...... 12
> Bytes per block ....... 4096
> Volume label .......... VOL1
> Volume serial ......... LX1047
> Max partitions ........ 3
>
> ------------------ tracks -------------------------------
>       Device       start     end   length    id   system
>    /de/dasdc1          2  150239   150238     1   Linux
> Native
>
> The S option shows me
> Device .......... /dev/dasdc
> Volume label .... VOL1
> Volume serial ... LX1047
>
> /dev/dasdc1  - LINUX.VLX1047.PART0001.NATIVE
>
> How does that name get generated on the Z/OS side?
> Why does it get generated on the Z/OS side for dedicated dasd, but not
> for mini-disks?
> How can I get it on the Z/OS side for the mini-disks?
>
> Thanks
>
> ----------------------------------------------------------------------
> 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

----------------------------------------------------------------------
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

----------------------------------------------------------------------
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

Reply via email to