We created the golden image server on EDEV FBA disk as well so our clone is
from EDEV FBA to EDEV FBA. I presume if we are using the CMS FORMAT/RESERVE
sequence we should do so for the source golden image build as well as the
clone system before copying. When we tried using dd to clone, I
On 3/2/2011 at 03:47 PM, Richard Troth vmcow...@gmail.com wrote:
There is a lot of confusion about 'dasdfmt' versus 'mkfs'. If you
already know the difference, please excuse this note.
Rick,
Do me a favor and stick this out on the wiki (after editing it a bit for
style). I think this
1. rebuilt the golden image, preparing the disk with CMS FORMAT RESERVE on
EDEV FBA mini-disks
2. prepared the clone system disk with CMS FORMAT RESERVE on EDEV FBA
mini-disks
3. Altered the clonerw.sh script so that it recognized the disk as FBA
instead of CKD to get the device names and
On 3/3/2011 at 11:29 AM, Craig Collins grizl...@gmail.com wrote:
So, we have a method to make the clone, but the clonerw.sh script doesn't
seem to work with this disk without further modifications that we can't
figure out at this point.
Are you using the sync option on the dd command, or
the script does have the sync command executing after the copy with dd
completes
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
FYI - the problem we were having with the boot.findself script had to do
with upper/lower case matching issues when the script interrogated the
sles11 parameter files searching for the source and destination server names
and ip addresses. So, the script worked fine once we matched the cases to
We're walking through the IBM doc Sharing and Maintaining SLES11 Linux
under z/VM using DCSSs and an NSS but using EDEV FBA devices instead of
native CKD devices. We've move to the point where we are making our first
cloned copy and are running into issues.
The original script identifies the CKD
Craig,
We've altered the script to identify the FBA devices,
format them with 'mkfs' and then use the 'dd' to perform
the block copy. When we try to boot the cloned copy
Just some thoughts - after you dd them, but before you try to IPL, are you
able to mount the new targets as file systems?
Hi, Craig, --
For FBA, you are correct to dispense with 'dasdfmt'. (Will detail
that in a following note.)
You still need to stamp a bootstrap onto the FBA disk, and the
bootstrap is different for FBA than for CKD.
... We've altered the script to
identify the FBA devices, format them
There is a lot of confusion about 'dasdfmt' versus 'mkfs'. If you
already know the difference, please excuse this note. The water is
muddier for mainframers because in z/OS land the concept of
filesystem and volume is blurred. z/OS uses the low level
structure (tracks, blocks, records, even
10 matches
Mail list logo
