To relieve your curiosity, Maint still had the 123, but DIRMAINT could no
t
get it RW to do updates.
I have gone the route suggested by Kris/Mike. Updated the EXTENT CONTROL
to put END back in on my REGIONS (540RES not part of that). Took the USER
BACKUP and changed all the MDISKs back to E
Using CMDISK would also be OK, of course. Just trying to figure out how you
lost that link...
On Sat, Apr 18, 2009 at 4:04 AM, Ivica Brodaric wrote:
> Valerie,
> How did you update the size of MAINT 123? Using GET/REPLACE or using
> DMDISK/AMDISK? If you used the latter, then maybe you forgot to
Valerie,
How did you update the size of MAINT 123? Using GET/REPLACE or using
DMDISK/AMDISK? If you used the latter, then maybe you forgot to use
KEEPLINKS operand of DMDISK. Without that, a LINK to MAINT 123 in DIRMAINT's
(and any other) directory entry would be deleted when you delete MAINT 123.
I like your explaination Mike. Very good.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]on
Behalf Of Mike Harding
Sent: Thursday, April 16, 2009 11:30 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Dirmaint Broken?
Part of the problem is that MAINT
You're welcome Valerie.
I am not sure what you mean by the comment that "the system itself
seems to use this". DIRMAINT uses it, for sure. And it also gives you
a way to adjust it as you see fit.
To me, "the system" is the operating system. DIRMAINT was tacked on
long after there was VM. I maint
Thanks to all for the information. Just to let you know, I am still
working on this and want to be sure that I know what and how I need to fi
x
before I try to start fixing.
I have learned a lot of useful information - commands, techniques -- from
you all and I really want to work through this
Hi Valerie,
I hope not to add to your confusion, and I have held off because I am
not on z/VM 5.4 but z/VM 5.3, plus there is always lots of expert
advice from this list.
A couple of things though.
If you have the MAINT extents, and others, listed in the EXTENT
CONTROL file, that is good, but yo
Good point, I forgot the STABLE links done by CP itself.
So proceed as I told, using DEFINE MDISK and DIRM USER BACKUP,
still fairly easy (in my eyes, will cost me 5 minutes).
DEFINE MDISK will create whatever you like in R/W mode, no need to
reipl, or create a USER INPUT
2009/4/16 Mike Harding :
Part of the problem is that MAINT 123 is no longer being seen as a
full-pack minidisk. Thus you truly have overlaps with other write links -
and the killer is the stable links to minidisks (probably your parm disks)
contained within the same extent.
You said: MAINT has MDISK 0123 3390 000 10
[mailto:ib...@listserv.uark.edu]on
Behalf Of Le Grande Valerie
Sent: Thursday, April 16, 2009 9:51 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Dirmaint Broken?
I guess the message is not telling the truth then! Since DIRMAINT is
broken, it is likely listed.
Some shortcut-key in GAMIL made the SEND go prematurely
2009/4/16 Kris Buelens :
> STABLE links is something that I only saw being used by DFSMS, it
> means no one else can get a R.W link, that's my MAINT's 123 got it MR
> link become R/O. Maybe newer support in DIRMAINT makes it use STABLE
> lin
STABLE links is something that I only saw being used by DFSMS, it
means no one else can get a R.W link, that's my MAINT's 123 got it MR
link become R/O. Maybe newer support in DIRMAINT makes it use STABLE
links?
Q LINKS does only reveal who has a minidisk starting at the same
cylinder, so your Q
I guess the message is not telling the truth then! Since DIRMAINT is
broken, it is likely listed.
@LISTSERV.UARK.EDU
Subject: Re: Dirmaint Broken?
I thought that sounded dangerous also, or at least weird.
Q LINKS 123 just gives me that MAINT has it R/O. Briefly checked manual. =
No parameter to add.
Logged off and on and still got:
09:20:08 HCPLNM103E DASD 0123 forced R/O; R/W by48, R/O by97
users
I thought that sounded dangerous also, or at least weird.
Q LINKS 123 just gives me that MAINT has it R/O. Briefly checked manual.
No parameter to add.
Logged off and on and still got:
09:20:08 HCPLNM103E DASD 0123 forced R/O; R/W by48, R/O by97
users; stable by 3
ting System [mailto:ib...@listserv.uark.edu]on
Behalf Of Le Grande Valerie
Sent: Thursday, April 16, 2009 8:53 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Dirmaint Broken?
With all the information I have been given, I am still unsure I know how =
to fix this.
Here is some more information:
Today when
With all the information I have been given, I am still unsure I know how
to fix this.
Here is some more information:
Today when I logged on to MAINT, I noticed I got error message HCPLNM103E
DASD 123 forced R/O; R/W by 48 R/o by 97 users Stable by 3
MAINT has MDISK 0123 3390 000 10016 540RES M
he new directory.
> Tom
>
> -Original Message-
> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]on
> Behalf Of Le Grande Valerie
> Sent: Wednesday, April 15, 2009 3:29 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Dirmaint Broken?
>
>
>
Sent: Wednesday, April 15, 2009 3:29 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Dirmaint Broken?
Hi all,
I thought I was getting the hang of using DIRMAINT, but now I think I =
shot myself in the foot. I am wondering now how to fix the wound.
Yesterday I made some changes that appeared
Hi all,
I thought I was getting the hang of using DIRMAINT, but now I think I
shot myself in the foot. I am wondering now how to fix the wound.
Yesterday I made some changes that appeared to be successful. After some
searches of the list archives, I thought I did something good but now I a
20 matches
Mail list logo
