Not really a problem, copying 530RES to another volume name, and IPLing that
volume. But you have to do a lot of things first.
1. Go to your SYSTEM CONFIG file (MAINT's CF1) and save your current SYSTEM
CONFIG under another name. This SYSTEM CONFIG is used for your original
system.
2. Edit SYSTEM CONFIG and change 530RES to 531RES (for example). That is for
the new system.
3. Edit your USER DIRECT and change all 530RES to 531RES. This includes the
first statement which says where the location of this directory is located (now
on 531RES). Save under a new name. DO NOT DIRECTXA it. The directory
statement looks like:
DIRECTORY 123 3390 520RES
3. COPY your 530RES to 531RES (for example).
4. Now, on your current system, DIRECTXA your new directory (which will be
witten to 531RES. You need to detach Maints virtual address of 123 and attach
your 531RES volume to Maint as 123, then do the DIRECTXA.
5. Before you forget, go back to MAINTs CF1 disk and put back your original
SYSTEM CONFIG, so you can still IPL your production system.
6. Detach Maint's 123 just so you don't accidently use a wrong volume later on.
Now you can IPL the new volume.
Of course, in your USER DIRECT and SYSTEM CONFIG, you also need to make volume
changes for your paging pack names, spool pack names, and any other volumes
that you may wish to copy (like where you put your SFS packs).
For me, I have the following volumes for VM (I'm z/VM 5.2)
520RES
520W01 System software and VMSYS:
520W02 System software
520W03 System software
520PG1 paging
520PG2 paging
520PG3 paging
520SP1 Spool
520SP2 Spool
My VMSERVU SFS user, has it's software and catalogs on 520W02, but the storage
pools are on dedicated user packs. I thought I could get away from duplicating
the VMSERVU packs, but I can't.
I do the above process to create my Linux LPAR system. The packs are all
521xxx on that side. Well, with more paging packs and one less spool pack. I
then have to delete 390 only products not licensed for the IFL (but they run
there just fine). Like VTAM, and TubesGCS and some other venders products that
have a VM component. They run fine on an IFL, they just don't have anything to
connect to (like VSE <G>).
Tom Duerbusch
THD Consulting
Law of Cat Acceleration
A cat will accelerate at a constant rate, until he gets good and
ready to stop.
>>> "Peter E. Abresch Jr. - at Pepco" <[EMAIL PROTECTED]> 5/14/2008 1:05 PM
>>> >>>
z/VM 5.1 to 5.3 upgrade handholding
We are starting our upgrade from z/VM 5.1 to z/VM 5.3. We use z/VM
strictly for Linux. We are all old MVSers that originally installed z/VM
5.1. Now we are rethinking our z/VM installation and maintenance
methodology. We have talked to various VMers but have become overwhelmed
with the many methods of accomplishing this. Here is what we wish to do.
We wish to install z/VM 5.3 as a second level guest in our current z/VM
5.1 system. We wish to develop an environment where we can test the hell
out of it and once we are happy with it, we wish to implement it into
production by simply changing the IPL address for our z/VM LPAR. This
methodology will hold true for z/VM maintenance as well. Another words, we
will always have a production and a test z/VM. This is not uncommon as we
all know.
We have chosen to install second level using FTP from the install DVD on a
Linux server. We are calling our second level VM VMTESTSV and created the
following entry (please provide comments if this entry is not all that it
can be).
USER VMTESTSV VMTES530 256M 256M BG
ACCOUNT SYSTEMS
IPL CMS
MACH XA
OPTION LNKNOPAS
CONSOLE 0009 3215
NICDEF 0600 TYPE QDIO LAN SYSTEM VSWTCH00
SPOOL 000C 2540 READER *
SPOOL 000D 2540 PUNCH A
SPOOL 000E 1403 A
LINK MAINT 0190 0190 RR
LINK MAINT 019E 019E RR
MDISK 0191 3390 371 25 VMUSR0 MR
MDISK 2222 3390 241 5 VMUSR0 MR
MDISK 22CC 3390 246 5 VMUSR0 MR
MDISK 2CF1 3390 251 120 VMUSR0 MR
We will install z/VM to the following DASD volsers:
Pack Type Prod Test
RES 530RES (can we change this volser?)
SPOOL VMSPLP VMSPLT
PAGE VMPAGP VMPAGT
USER1 VMWK01 VMWK01 (shared)
USER2 VMWK02 VMWK02 (shared)
USER3 VMWK03 VMWK03 (shared)
I know, we have to migrate our customization and users over after we
install. Let?s say we do all that and completed our testing and are ready
for production implementation.
We wish to copy the RES volume to another volser and IPL the LPAR from
that address. Is this possible and what will be involved? Are we on the
right track?
Go slow, remember we are old MVSers and very young VMers. Thanks as
always.
Peter
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies. PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication. PHI will not accept any liability in respect of such
communications.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
