×
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.
I am not sure this is the problem, but it might be. There are some new PTFs
on 6.1 that put in a few (I think it was 2) waits when you do a GO SAVE 21,
because when the system goes into Restricted state, there are a few TCP/IP
jobs still running. QIBMHELP and something else, but I noticed the problem
when I was doing a SAVSYS on a 6.1 machine and I got a lock. A lock? How
the heck can you have a lock in a restricted state was my first thought,
well there was a PTF that fixed this and I think it put like 2 ten minute
waits in for these two jobs to end.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutionw on LinkedIn:
http://www.linkedin.com/groups?gid=2206093
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, December 09, 2009 8:10 AM
To: Midrange Systems Technical Discussion
Subject: SAVSYS running over an hour
I've got a little wimp lpar that's guested on another lpar. It's in a
restricted state. Just finished RCLSTG and I am running the SAVSYS. Nice
LTO3 tape drive. SAVSYS on this normally runs in 28 minutes (I can pull
stats for over a year's worth of data on length of run). Now it's been
running over an hour.
Hmm, maybe I should have looked into why our percent used changed so
much...
Rob Berendt
midrange.com
