× 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.


  1.  Home
  2. MIDRANGE-L
  3. September 2005

ASP Balance - *CAPACITY

Hi All,

Got a V5R1 system, latest cume.  Doing a STRASPBAL ASP(2)
TYPE(*CAPACITY) TIMLMT(*NOMAX)

In the DSPLOG I see this:

Message . . . . :   ASP balancing for ASP 2 ended.

Cause . . . . . :   The ASP balancing function of type *CAPACITY for ASP
2   
  ended.  The function had an ending code of  1.  

Ending code of 1 means it completed successfully, and the ASP is
"Completely Balanced." 

When I look at disk status I see this:

             Size    %     I/O   Request   Read  Write   Read  Write
%  
Unit  Type    (M)  Used    Rqs  Size (K)    Rqs   Rqs     (K)   (K)
Busy 
 61  6714  17548   4.7    8.8      5.5      .0    8.8     .0    5.5
0
 62  6714  17548   4.6    8.8      5.5      .0    8.8     .0    5.5
0
 63  6714  13161   6.2    9.7      5.6      .1    9.5   20.0    5.4
0
 64  6714  13161   6.3    9.3      5.3      .1    9.1    4.0    5.3
0
 65  6714  13161    .2     .1     20.0      .0     .1     .0   20.0
0
 66  6714  13161    .2     .0       .0      .0     .0     .0     .0
0

And view 2 shows these disks are actually ALL included in that ASP (for
JRNRCV objects, if you're wondering.)

           --Protection--             
Unit  ASP  Type  Status    Compression
 61    2  DPY   ACTIVE                  
 62    2  DPY   ACTIVE                  
 63    2  DPY   ACTIVE                  
 64    2  DPY   ACTIVE                  
 65    2  DPY   ACTIVE                  
 66    2  DPY   ACTIVE           

So what gives?  Unit 65 and 66 certainly don't look like they're doing
their share of the work here.  Ideas?        


Justin C. Haase - iSeries System Administrator
IBM Certified Systems Expert - eServer i5
Kingland Systems Corporation
email - justin.haase@xxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don
Sent: Monday, September 26, 2005 10:53 AM
To: Midrange Systems Technical Discussion
Subject: Re: COMMON Update... - the closing event



well, I've done it from SFO...:)



On Mon, 26 Sep 2005, rob@xxxxxxxxx wrote:

> I don't think there are many flights from west coast airports to east 
> coast destinations leaving after 1pm.  And considering that you have 
> to leave two hours early, plus cab/bus time.  They'd be hard pressed 
> to catch one session.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> Don <dr2@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 09/26/2005 10:06 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc
>
> Fax to
>
> Subject
> Re: COMMON Update... - the closing event
>
>
>
>
>
>
>
>
> actually 1.5....  People schedule a 1-3pm flight, catch the first 
> couple sessions in the day, zoom to room, checkout and catch a cab to
airport.
>
>
>
> On Mon, 26 Sep 2005, rob@xxxxxxxxx wrote:
>
>> Interesting.  What is more likely:
>>
>> 1 - West coast conference.  People blow off the whole Thursday in 
>> order
> to
>> catch a Thursday morning flight.
>> 2 - West coast conference.  People realize they can't catch a 
>> Thursday afternoon flight so they fly out on Friday morning instead.
>>
>> Rob Berendt
>> --
>> Group Dekko Services, LLC
>> Dept 01.073
>> PO Box 2000
>> Dock 108
>> 6928N 400E
>> Kendallville, IN 46755
>> http://www.dekko.com
>>
>>
>>
>>
>>
>> Don <dr2@xxxxxxxxxxxx>
>> Sent by: midrange-l-bounces@xxxxxxxxxxxx
>> 09/26/2005 09:09 AM
>> Please respond to
>> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>>
>>
>> To
>> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc
>>
>> Fax to
>>
>> Subject
>> Re: COMMON Update... - the closing event
>>
>>
>>
>>
>>
>>
>>
>>
>> this is one of the big reasons why, if COMMON wants to keep any kind 
>> of Thursday attendance, they kinda need to keep the conferences east 
>> of the MS, with the exception of say San Antonio...  You can get 
>> 5-7pm flights outta SAT and still hit east coast airports without 
>> having to catch a
> red
>> eye...
>>
>>
>>
>> On Mon, 26 Sep 2005, rob@xxxxxxxxx wrote:
>>
>>> If you're leaving a west coast COMMON for an east coast residence 
>>> you might as well stay for the Thursday night follies.  Many flights

>>> are
> not
>>> even available for after 11am or 12n from the west coast to the east

>>> coast.  Because by the time you get back east many airports are shut
>> down.
>>> East coast conferences do offer a lot of temptation for west 
>>> coasties
> to
>>> head back west though.
>>>
>>> Rob Berendt
>>> --
>>> Group Dekko Services, LLC
>>> Dept 01.073
>>> PO Box 2000
>>> Dock 108
>>> 6928N 400E
>>> Kendallville, IN 46755
>>> http://www.dekko.com
>>>
>>>
>>>
>>>
>>>
>>> "Greg Wenzloff" <GWenzloff@xxxxxxxxxxx> Sent by: 
>>> midrange-l-bounces@xxxxxxxxxxxx
>>> 09/26/2005 08:31 AM
>>> Please respond to
>>> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>>>
>>>
>>> To
>>> <midrange-l@xxxxxxxxxxxx>
>>> cc
>>>
>>> Fax to
>>>
>>> Subject
>>> Re: COMMON Update... - the closing event
>>>
>>>
>>>
>>>
>>>
>>>
>>> I'm sure I'll get slammed for this idea.
>>>
>>> Why not close the conference at noon on Thursday with a nice free 
>>> lunch and a guest speaker of the caliber of the ones that got 
>>> stepped on by Quadrant.
>>>
>>> No matter what you offer in an evening event, many people would have

>>> already left.
>>>
>>> Just an idea.
>>> Greg
>>>
>>>
>>> --
>>> 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.
>>>
>> --
>> 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.
>>
> --
> 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.
>
--
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.



CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
confidential, and may be legally privileged.  If you are not the intended 
recipient or believe you received this communication in error, please reply to 
the sender indicating that fact and delete the copy you received.  In addition, 
retention, dissemination, distribution, copying, or otherwise use of the 
information contained in this communication is strictly prohibited.  Thank you.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.