|
midrange.com
I submitted that off to batch. So far it generated 162 spool files. Files,
not pages. And growing... Your number will vary based on the number of
subsystem descriptions, etc, which you have. This looks like the command.
Yes, I would definitely run these, and physically print the reports, prior
to replacing my OS from distribution media.
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
Pete Massiello
<pmassiello@os-solu To: midrange-l@midrange.com
tions.com> cc:
Sent by: Fax to:
midrange-l-admin@mi Subject: Re: Damaged objects
drange.com
09/07/2001 09:44 AM
Please respond to
midrange-l
--
[ Picked text/plain from multipart/alternative ]
Rob,
Is the command you are thinking about PRTSYSINF. Its a great
command for Documentation of your system.
Pete Massiello
rob@dekko.com wrote:
>Didn't the Road Map for migrating from CISC to RISC have a good data
>collection area? Like printing out all sorts of things like: System
>Values, PTF's, network attributes, etc. I think the backup/restore manual
>does a pretty good job of listing some of these out if you are doing
>something like a complete restore in a situation in which your first
>machine isn't quite dead yet. (We just used this to migrate from one
model
>and S/N of a 400 to another.) We didn't have any problems but I seem to
>remember getting a pile of paper about a knee deep when I did the roadmap.
>The backup and restore guide seemed to be much shorter.
>
>Rob Berendt
>
>==================
>A smart person learns from their mistakes,
>but a wise person learns from OTHER peoples mistakes.
>
>
>
> Chuck Morehead
> <cbmorehead@nokuse. To:
midrange-l@midrange.com
> com> cc:
> Sent by: Fax to:
> midrange-l-admin@mi Subject: Re: Damaged
objects
> drange.com
>
>
> 09/06/2001 11:22 AM
> Please respond to
> midrange-l
>
>
>
>
>
>
>Neil,
>
>Your email doesn't say whether or not you've spoken to IBM about this
>problem. I would suggest doing so first. If they have a fix it could
save
>you a lot of time and headaches.
>
>I had to do this about 3 years ago. We had major problems that prevented
a
>machine from IPL'ing. IBM finally said that they did not know what the
>cause was, but they guessed the OS had been corrupted. We could wait for
>their analysis of a system dump (taken via DST) to see if they could
figure
>out what was wrong, or reinstall the OS. They figured about 80% chance
>this
>would resolve the problem - and it did.
>
>I'll make a few points:
>1. Each case is different, so you want to take as many precautions as
>possible.
>2. Manual install - you do _NOT_ want to attempt an automatic here.
>3. I would recommend a full system save, i.e. make sure all of your data
>is
>backed up first.
>4. I would also recommend recording as much information about your system
>configuration as possible before this procedure.
>5. Good luck!
>
>As an aside, unless my mind has blocked the memory, I don't recall any big
>problems coming up when we did this. That is, our original problem was
>severe, the resolution was drastic, but given that it went very smoothly.
>
>Chuck
>
>----- Original Message -----
>From: "Carley, Neil" <carleyn1@Midas-Kapiti.com>
>To: <MIDRANGE-L@midrange.com>
>Sent: Thursday, September 06, 2001 10:48 AM
>Subject: Damaged objects
>
>
>>Hi group,
>>
>>Lately our system, a 720 at V4R3 has been reporting a very high amount of
>>damaged objects and it seems as though things are starting to get worse.
>>
>So
>
>>far this year I have had to run 4 reclaim storage and 1 reclaim DLO. I
>>
>now
>
>>have to do another rclstg this w/e as there is once again considerable
>>damage on the system. A rclstg on our system takes about 37 hours. One
>>
>thing
>
>>I am now thinking about doing is reinstalling the OS as I think perhaps
>>
>that
>
>>part of it may have become corrupt ?
>>I have completed DR restores, built systems from scratch successfully in
>>
>the
>
>>past but never just reinstalled the OS on a live system and am somewhat
>>hesitant about doing it on a mature system without finding out exactly
>>what's going to happen as a result. I'm sure someone has done this in the
>>past and would be very grateful if you would offer any advice on the
>>process, things to look out for, changes that may occur etc.
>>Any advice on any of the above will be very welcome.
>>
>>thanks again
>>Neil
>>_______________________________________________
>>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>>
>list
>
>>To post a message email: MIDRANGE-L@midrange.com
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>>or email: MIDRANGE-L-request@midrange.com
>>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@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>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@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>
>.
>
--
Pete Massiello
OS Solutions International
Phone: (203)-744-7854 Ext 11.
http://www.os-solutions.com
mailto:pmassiello@os-solutions.com
--
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
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-2025 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.
