× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It was a runaway job.

We didn't actually crash...but it was close.

Now I'm looking for ammo for the battle over better monitoring.

Charles


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Carmen Nuland
Sent: Wednesday, December 05, 2007 11:04 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Recovery Time estimate for abnormal system end
due to DASD usage

I think the last time this happened for us, it took 3-4 hours
to come back
up (normal IPL - 1 hour) - I think it takes longer because it
has to do some
extra recovery.

The tough part is to figure out why you filled up the DASD
and fix it. Are
you that tight in disk space or did you have a runaway job
(which is what
happened to us the last time)?
Carmen

-----Original Message-----
From: Wilt, Charles [mailto:WiltC@xxxxxxxxxx]
Sent: Wednesday, December 05, 2007 8:46 AM
To: Midrange Systems Technical Discussion
Subject: Recovery Time estimate for abnormal system end due
to DASD usage

All,

Just wondering if anyone has any experience or knowledge to
share I can use
to estimate how long it
might take to re-IPL after an abnormal system end cause by
the DASD filling
up.

Box is an 810 running v5r2, with 500GB (14x70GB mirrored)
DASD and about
1,500 active jobs unusually
running 50-60% CPU.

Thanks!

Charles Wilt

Software Engineer

CINTAS Corporation - IT 92B

513.701.1307

wiltc@xxxxxxxxxx <mailto:wiltc@xxxxxxxxxx>



This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and
you are not a
named addressee you are hereby notified that you are not
authorized to read,
print, retain, copy or disseminate this communication without
the consent of
the sender and that doing so is prohibited and may be
unlawful. Please
reply to the message immediately by informing the sender that
the message
was misdirected. After replying, please delete and otherwise
erase it and
any attachments from your computer system. Your assistance
in correcting
this error is appreciated.

--
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 e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.