|
midrange.com
All the suggestions below may be good. However I have a question. I've
done a few CISC-to-RISC migrations, but it's been awhile. What would be
the drawbacks to saving a library off, restoring it to the new machine and
then running the command to convert that library? Don't we have strange
shops out there that actually have their development machines older than
their production machines? And aren't some of these CISC? And don't they
distribute these libraries to RISC production machines? So in effect, they
do this all the time, right?
Rob Berendt
==================
Remember the Cole!
Edward Koziol
<koziol@chaney.net> To:
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
Sent by: cc:
owner-midrange-l@mi Subject: RE: Cisc to Risc
Disk Requirement
drange.com
04/03/01 12:39 PM
Please respond to
MIDRANGE-L
It's been a while, but you may want to try doing the following:
1) Permanently apply all temporary PTF's
2) Perform all disk housekeeping tasks (ie. reorgs, delete old spool
files, remove unnecessary objects, etc.)
3) Save and delete any libraries that aren't needed.
4) When this fails, adding disk may be your only other alternative.
Ed
-----Original Message-----
From: Scott Klement [mailto:klemscot@klements.com]
Sent: Tuesday, April 03, 2001 11:56 AM
To: MIDRANGE-L@midrange.com
Subject: Re: Cisc to Risc Disk Requirement
On Tue, 3 Apr 2001, Bill Albert wrote:
> I am helping a client with Cisc to Risc upgrade and the planning tool
> states that there is not enough disk capacity. This is a 3GB machine
> with 2.5GB used by Customer. EUA planner says IMPI requirement is
> 2.4GB. Is there a way do do this in pieces or some other way around
> putting disks into an old machine?
>
> Any experience with this? (Al?)
Before I comment, I want to make sure we're talking about the
same thing. :) When I did my upgrade, I looked at my disk usage
information in the EUA's option called "QB020" and it looked
something like this:
Estimated Storage
Target release . . . . . . . : V4R5M0
Date collected . . . . . . . : 02/23/01
Current supported system capacity (M) . . . . . . : 5158.99
Storage used (M) . . . . . . . . . . . . . . . . : 4559.72
Required IMPI system capacity (M) . . . . . . . . : 4813.21
Required PowerPC AS capacity (M) . . . . . . . . . : 6709.89
Storage IMPI PowerPC AS
Sufficient Capacity Storage Storage
ASP Storage (M) Required Required
1 No 5158.99 4813.21 6709.89
Storage Requirements
Detai
ASP number . . . . . . . . . . . . . . . . . . . : 1
Sufficient Storage . . . . . . . . . . . . . . . : No
As you can see, it says that I don't have sufficient storage. The IMPI
(CISC) storage required is below the amount of storage that I have, and
the PowerPC (RISC) storage required is above the amount.
To me, it appeared that the reason it said I wouldn't have enough storage
seemed to be that it assumed that I was using the same disks on the RISC
machine as I had on a CISC machine. (Does anyone actually do that?!)
In reality, my RISC machine had 5 times as much disk space as my CISC
machine -- the 6gb wasn't even close to filling the disk.
So I went ahead and did the upgrade -- I didn't have any problems. It
only needed a tiny amount of additional space on the CISC machine (for
the QUPGRADE library) I had absolutely no problems with disk space.
> Any help appreciated.
>
> Bill
>
Hope that helps...
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
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.
