Of Chuck
Tribolet
Sent: Tuesday, July 08, 2014 12:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Using DIRMAINT to copy an existing guest
Before cloning, make sure that /etc/fstab doesn't contain any entries that look
like:
/dev/disk/by-id/somebig string
or
/dev/dasdsomething
You will need
On 7/6/2014 at 07:19 PM, Cameron Seay cws...@gmail.com wrote:
Es claro. For my edification, how does the system handle the cloning of
the minidisks of the cloned-from guest? Are they physically the same
ones? Does it grad available DASD for the cloned user? Thanks!
DIRMAINT will use
Hi, Cam.
The complete format of the DIRM CLONED command is this:
DIRM FOIR new_user_id CLONED 150 existing_user_id 150 AUTOG dasd_group
Create a new minidisk by cloning another existing minidisk. The new disk
will have the same device type and size as the existing disk, and will
also contain
Given the proper environment, though, you can talk / coerce DirMaint into
using the DASD FlashCopy function to quickly copy one minidisk to the new
location (if I remember correctlyŠ Now that I think about it though, when
I built my Linux cloning engine, I used DirMaint to allocate the disks,
and
with the drive letter changing.
Chuck Tribolet
trib...@us.ibm.com (IBM business)
trib...@garlic.com (Personal)
http://www.almaden.ibm.com/cs/people/triblet
From: Mark Post mp...@suse.com
To: LINUX-390@vm.marist.edu,
Date: 07/07/2014 12:16 PM
Subject:Re: Using DIRMAINT to copy
Mark:
That is what I call very cool. Let me be clear, DIRM finds available DASD
from the pool (in our case MOD 9s) and gives them to the clone? For
example, the clones will have volumes E150, E152... E15n, which are all
named the same for each clone anyway, and find DASD for them. I want to
The 'pool' is what is defined in the DIRMAINT EXTENT CONTROL .. you must
define there the volumes DIRMAINT will use -- and then create at least one
group of these volumes that minidisks for guests will be assigned from.
Then you specify that group when you issue commands like AMDISK and
On Monday, 07/07/2014 at 10:36 EDT, Scott Rohling
scott.rohl...@gmail.com wrote:
Don't confuse the volume addresses for the DASD with the minidisk
addresses
for the guests.. A minidisk is not the same as an attached volume..
I'm
not sure which you're using, so want to be clear.. DIRMAINT
Sir Alan, I accept the correction - although I do wonder if the word
'pack' is even proper nowadays ;-) I think the list has discussed terms
like FP-1. etc. I agree regions should always start with cylinder 1. I'm
not sure I would tell DIRMAINT about any of my 0-END volumes in EXTENT
CONTROL,
On 7/7/2014 at 10:02 PM, Cameron Seay cws...@gmail.com wrote:
Mark:
That is what I call very cool. Let me be clear, DIRM finds available DASD
from the pool (in our case MOD 9s) and gives them to the clone? For
example, the clones will have volumes E150, E152... E15n, which are all
named
I have used DIRMAINT to edit an existing guest. I have an existing guest
profile that I would like to user to make more guests. What are the steps!
Thanks.
--
For LINUX-390 subscribe / signoff / archive access instructions,
Hi, Cam.
Do the following:
1) create a new USER DIRECT file, based on the existing guest you want
to copy, with the desired user name and password, etc.
2) use DIRMAINT to bring it on line:
DIRM ADD user_name
3) clone the existing user's mdisks to the new user_name
DIRM FOR user_name
Es claro. For my edification, how does the system handle the cloning of
the minidisks of the cloned-from guest? Are they physically the same
ones? Does it grad available DASD for the cloned user? Thanks!
On Sun, Jul 6, 2014 at 6:47 PM, Dave Jones d...@vsoft-software.com wrote:
Hi, Cam.
13 matches
Mail list logo
