|
Good point.
I wonder what happens if I try this going from V5R1 to V5R2 and it is not
supported.
Does it just not work, or hose my system (in which case I have to do a
system restore)
Just guessing, the processing for the upgrade is done in the V5R1 OS, thus
the need for the PTF's. If that guess is accurate it should work
I won't know until I try it
John
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Tuesday, March 16, 2010 1:36 PM
To: Midrange Systems Technical Discussion
Subject: Re: Error CPA3DE1 during OS upgrade
Were not image catalogs enabled at V5R1 for upgrading to V5R3 only? I
have this from the V5R3 Memo to Users
2.3 Upgrading to V5R3 using image catalog support
When you use image catalog support to upgrade to V5R3 from V5R1 or V5R2,
you must apply the following PTFs before you prepare your image catalog
for the upgrade:
* For V5R1, use SI10553
* For V5R2, use SI10563
The Virtual media PTFs required for the corresponding releases are
listed below:
* V5R1M0: SI17565
* V5R2M0: SI17564
* V5R3M0: SI17566
So I don't think there is any way to use image catalogs at V5R1 for
installing or applying anything. That is a murky part of my memory from
over 6 years ago.
The Memo to Users is at
http://www-912.ibm.com/s_dir/sline003.nsf/PSP%20Number%20View/SF98086
HTH
Vern
Pete Massiello wrote:
Way back then, you used different parameters for creating the virtualuse
device.
CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(QVRTOPT)
ONLINE(*YES) TEXT(virtual optical device)
Your image catalogue MUST be a certain name at V5R1. I always used
QUPGRADE1
Then you had to use a special command to initiate the upgrade, and NOT
PWRDWNSYShttp://www.linkedin.com/groups?gid=2206093
STRVRTINS IMGCLG(QUPGRADE1)
I hope this helps. If you don't have that command, then you need
the required PTFs to get it and image cat support.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn:
weekend.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Allen
Sent: Tuesday, March 16, 2010 9:20 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Error CPA3DE1 during OS upgrade
Rob,
Thanks for the help, I plan on trying the image catalog method this
LICPGM,
However, I tried step one:
CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(*VRT) ONLINE(*YES)
and get an error
"Value *VRT for parameter RSRCNAME not a valid name"
Is this not available for me to use on V5R1
or should I use one of the choices *NONE or OPT01?
John
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, March 15, 2010 9:51 PM
To: Midrange Systems Technical Discussion
Subject: RE: Error CPA3DE1 during OS upgrade
I_BASE is always first. Which is what should have been first during your
last OS upgrade attempt. Use the image catalog and restart the GO
5, 1. How to use an image catalog is outlined in the software--
installation manual.
Basic steps are something like
CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(*VRT)
VRYCFG CFGOBJ(OPTVRT01) CFGTYPE(*DEV) STATUS(*ON)
MD DIR('/imageCatalog')
CRTIMGCLG IMGCLG(VSOMETHING) DIR('/imageCatalog/vsomething')
Stick I_BASE cd in drive
ADDIMGCLGE IMGCLG(VSOMETHING) FROMDEV(OPT01) TOFILE(*GEN)
repeat for each physical cd in the order referred to in the manual. Do
NOT do the cume.
LODIMGCLG VSOMETHING OPTVRT01
GO LICPGM
5, 1
VFYIMGCLG IMGCLG(VSOMETHING) SORT(*YES)
Start your upgrade and go home and monitor it remotely from your HMC. No
need to be there and physically feed it discs. No worry that you'll be 3
discs into the upgrade and find out it's damaged.
Cume:
LODIMGCLG VSOMETHING OPTION(*UNLOAD)
CRTIMGCLG IMGCLG(CUME) DIR('imageCatalog/cume')
ADDIMGCLGE IMGCLGE(CUME) ...
Repeat as necessary.
LODIMGCLG CUME OPTVRT01
VFYIMGCLG IMGCLG(CUME) TYPE(*PTF) SORT(*YES)
GO PTF, 8
LODIMGCLG CUME OPTION(*UNLOAD)
Rob Berendt
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.