Thanks all. Yep, read the HELP , didn't see the devmaint part.
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Wakser, David
Sent: Wednesday, July 29, 2009 7:40 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DEFINE MDISK
Based on the Help:
The user
esday, July 29, 2009 4:51 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: DEFINE MDISK
Is anyone having problems with the DEFINE MDISK command? I get the
following:
define mdisk as 1c14 1 5 zz1c14
HCPDEF003E Invalid option - MDISK
I am a class A user. We're running VM 5.4 0902
Than
Steve, the help file for the CP DEFINE MDISK command notes:
The user must be the primary system operator or the user's OPTION
directory statement must include the DEVMAINT option.
You need to add the DEVMAINT option to your user id.
Gentry, Stephen wrote:
Is anyone having problems
Got DEVMAINT?
See HELP DEFINE MDISK
Marcy
"This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you must
not use, copy, disclose, or take any action based on this message or any
inform
Is anyone having problems with the DEFINE MDISK command? I get the
following:
define mdisk as 1c14 1 5 zz1c14
HCPDEF003E Invalid option - MDISK
I am a class A user. We're running VM 5.4 0902
Thanks,
Steve
> Hi Jim, thanks for your help. I tried your command and got:
> HCPLNM107e Linux1 0A10 not linked, not in CP directory
>
> At that point I had 0A10 attached to Linux1. I detached it and
attached i
> t
> to system and got the same message.
If it's attached to an ID, then you can't link it. LINK on
e
has it R/W).
Each time LINUX1 logs on the MDISK statement
will attempt to gain access to that minidisk in R/W mode.
In a previous post you mentioned use of
the CP command" DEFINE MDISK
IMHO opinion that (very powerful and important)
command is really just meant as an "oops/recovery&
Hi Jim, thanks for your help. I tried your command and got:
HCPLNM107e Linux1 0A10 not linked, not in CP directory
At that point I had 0A10 attached to Linux1. I detached it and attached i
t
to system and got the same message.
I thought about defining the mdisk to maint and then trying to link
006 10:08 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Define MDisk Question
>
>
> Your steps are spot-on except for one small part. You do not have to
> let
> the linux guest do a DEFINE MDISK nor have class A. Simply add the
> MDISK
> entry to the directory and then o
Why do you specify MR when you really mean M or W?
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Jim Vincent
Sent: Thursday, June 29, 2006 10:08 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Define MDisk Question
Your steps are spot-on
cal volume group on
> the fly. We have been able to do this by making sure all our dasd is
online
> at ipl, then we det the dev from system, att it to our userid, format it,
> att it back to system and then do a define mdisk from the linux vm
userid.
> We then add it to user direct for
Your steps are spot-on except for one small part. You do not have to let
the linux guest do a DEFINE MDISK nor have class A. Simply add the MDISK
entry to the directory and then on the linux guest, do a CP LINK * cuu cuu
MR to get access to it. Make sense?
In fact, there is a good paper on
serid, format it,
att it back to system and then do a define mdisk from the linux vm userid
.
We then add it to user direct for the next time the linux user logs off a
nd
back on.
The trouble with this is, the linux guest must have "A" priveledge and
devmaint, which is undesirable. D
13 matches
Mail list logo
