On Friday, 03/23/2018 at 12:25 GMT, Mariusz Walczak
wrote:
> @Alan your explanation is interesting, but we reference those DASD
labels on
> zOS for backup purposes. If I understood correctly you recommend to
forget
> about the labels on VM and use real device numbers, which is a no-go.
I didn'
: zLinux with HyperPAV
When you use dasdfmt in linux add the -l volser option to reapply the VM volume
label.
When a full pack minidisk formatted with dasdfmt will look just like an z/OS
volume with a vtoc with 1 - 3 datasets and can be backed up by DFDSS on a z/os
system.
-Original Message
390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mariusz
Walczak
Sent: Thursday, March 22, 2018 11:20 AM
To: LINUX-390@VM.MARIST.EDU
Subject: zLinux with HyperPAV
The below email is classified: Internal
Hello,
I'm trying to setup HyperPAV on our SLES 11.4. From documentation I read I
Jersey City, N.J. 07302
Work 201-395-1509
Cell917-903-0102
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mariusz
Walczak
Sent: Thursday, March 22, 2018 11:20 AM
To: LINUX-390@VM.MARIST.EDU
Subject: zLinux with HyperPAV
The below email is
On Thursday, 03/22/2018 at 03:20 GMT, Mariusz Walczak
wrote:
> The below email is classified: Internal
>
> Hello,
>
> I'm trying to setup HyperPAV on our SLES 11.4. From documentation I read
I must
> define a full-pack minidisk in form:
> MDISK basevdev devtype DEVNO rdev mode OR MDISK basev
The below email is classified: Internal
Hello,
I'm trying to setup HyperPAV on our SLES 11.4. From documentation I read I must
define a full-pack minidisk in form:
MDISK basevdev devtype DEVNO rdev mode OR MDISK basevdev devtype 0 END
volser mode
I used DEVNO and I believe I was able to se
