Hi, Howard.
Try the following:
1) create another VM user id with the proper privileges. Call it, say, MAINTX.
2) create the new MAINT mindisks on the new volume,using your favorite
directory manager
tools.
3) logo off of MAINT
4) from MAINTX, link to both the old MAINT's minidisks, and the new
Thanks all...great suggestions.
Dave Jones [EMAIL PROTECTED] 6/27/2008 9:52 AM
Hi, Howard.
Try the following:
1) create another VM user id with the proper privileges. Call it, say, MAINTX.
2) create the new MAINT mindisks on the new volume,using your favorite
directory manager
tools.
3) logo
One addition question:
Doesn't all of this (19E 19D) have some effect on the saved segments for CMS?
Dave Jones [EMAIL PROTECTED] 6/27/2008 9:52 AM
Hi, Howard.
Try the following:
1) create another VM user id with the proper privileges. Call it, say, MAINTX.
2) create the new MAINT mindisks
Hi, Howard.
No, there is no effect on the CMS saved segments...they are only effected if you change
the their contents, not just their location.
Howard Rifkind wrote:
One addition question:
Doesn't all of this (19E 19D) have some effect on the saved segments for CMS?
Dave Jones [EMAIL
Why an extra user? Just use MAINT, and change the addresses. I'd use
the password fields to tell which is which, for example
MDISK A190 3390 nnn mmm oldvol RR OLD190 TOREMOVE mmdd
MDISK 0190 3390 kkk mmm newvo RR ALL
And, if you have an ESM, the passwords on the MDISK records don't
count
[mailto:[EMAIL PROTECTED] On
Behalf Of Howard Rifkind
Sent: Friday, June 27, 2008 10:25 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Moving User Maint's minidisks.
One addition question:
Doesn't all of this (19E 19D) have some effect on the saved segments
for CMS?
Dave Jones [EMAIL PROTECTED] 6
Do the renames (MAINT--MAINTOLD and MAINTX--MAINT) in the source directory and update the object
directory. That will put both into effect at the same time. With no problems with new users log on.
If they logon before the DIRECTXA command they get the old disks and if the logon after the command
: Friday, June 27, 2008 11:09 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Moving User Maint's minidisks.
Why an extra user? Just use MAINT, and change the addresses. I'd use
the password fields to tell which is which, for example
MDISK A190 3390 nnn mmm oldvol RR OLD190 TOREMOVE mmdd
MDISK 0190
@LISTSERV.UARK.EDU
Subject: Re: Moving User Maint's minidisks.
Why an extra user? Just use MAINT, and change the addresses. I'd use
the password fields to tell which is which, for example
MDISK A190 3390 nnn mmm oldvol RR OLD190 TOREMOVE mmdd
MDISK 0190 3390 kkk mmm newvo RR ALL
And, if you have
If you are moving MAINT 190 you must use DDR to copy all of it. If you move MAINT 19E and you use
DDR then you don't have to save CMS after it is moved. With any other disk you can save the FORMAT
step and the ACCESS.
Your plan would work if you are careful. If you just comment out the
Thanks Stephen, that's what I thought and you confirmed the issue with those
people already linked to disks in question.
Stephen Frazier [EMAIL PROTECTED] 6/27/2008 11:58 AM
If you are moving MAINT 190 you must use DDR to copy all of it. If you move
MAINT 19E and you use
DDR then you don't
On: Fri, Jun 27, 2008 at 11:43:21AM -0400,Howard Rifkind Wrote:
} Now is it save to swap the 1193 to 193 although several user have access to
the 193. In the directory I'm going to comment out the original 193 and give
the 1193 mini the 193 address. (your comments please)
Don't just delete
Actually, if your ESM is VM:Secure you don't have to worry about any of
this. He'll happily let you move R/O minidisks AND automatically
reclaim the old extent after ALL links to it have been severed. As long
as you aren't changing the size of the disk, I believe he'll copy it
track by track
If you use Dirmaint: use the CLEAN option for a DMDDISK or CMDISK
(delete/change minidisk): the DATAMOVE tries to get an exclusive
link. Only when that succeeds, the minidisk is cleared after which it
becomes free for re-use.
Without CLEAN, the problem is not only that current users of old
14 matches
Mail list logo
