RE: STRDSKRGZ command

["Graap, Kenneth" <keg@xxxxxxxxxxxxx>]

Due to a requirement where the application developers need a certain amount of 
access to production applications (it's a long story.....) we run in a single 
system / single LPAR environment, however we have allocated disk storage 
through the use of ASP's. We actually have 3 of them:

        ASP1 = System code/data along with Production application code/data

        ASP2 = Production Application and System Audit journal receivers 
(Isolate disk arms for journaling)

        ASP3 = Developers playground 

ASP3 was specifically set up to restrict how much space the developers can use 
... You know those developers, they will use up everything if you give them 
half a chance.


Kenneth

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Albert York
Sent: Friday, October 06, 2006 2:25 PM
To: Midrange Systems Technical Discussion
Subject: RE: STRDSKRGZ command


Thanks Ken.

I have always used one ASP because it is simpler. What is the benefit of
running more than one?

Thanks,

Albert

  ----- Original Message -----
  From: "Graap, Kenneth"
  To: "Midrange Systems Technical Discussion"
  Subject: RE: STRDSKRGZ command
  Date: Fri, 6 Oct 2006 14:21:30 -0700


  Albert -

  We don't do that, but we do regularly balance our Auxiliary Storage
  Pools based on usage traces...

  Every Friday I run these processes during the busiest time of the
  day:

  TRCASPBAL ASP(1) SET(*ON) TIMLMT(600)
  TRCASPBAL ASP(3) SET(*ON) TIMLMT(600)

  Then on Saturday we start balancing based on the trace ran on Friday:

  STRASPBAL ASP(1) TYPE(*USAGE) TIMLMT(1440)
  STRASPBAL ASP(3) TYPE(*USAGE) TIMLMT(1440)

  Help Text for TRCASPBAL:

  Trace ASP Balance - Help

  The Trace ASP Balance (TRCASPBAL) command controls the function that
  gathers the auxiliary storage pool (ASP) usage statistics. The
  trace function monitors the frequency that data is accessed on the
  disk units within the specified ASP. The 'high' use data and the
  'low' use data on the units is identified. The tracing of the usage
  of data on the units can be started on a specific ASP or for
  multiple ASPs. The trace may be started for a specific length of
  time. The trace can be stopped by specifying *OFF for the Trace
  option setting (SET) parameter. The trace can be ended at any time
  and restarted at a later time. The statistics that are collected
  are cumulative. For example, if the trace is started and ended and
  then restarted without clearing the statistics, the second group of
  statistics are added to the first collection.

  After statistics have been collected the ASP may be balanced using
  the Start ASP Balance (STRASPBAL) command, specifying TYPE(*USAGE)
  or TYPE(*HSM). After the balance has run to completion, the
  statistics will be cleared automatically by the balance function.

  The balancing of the ASP should be done shortly after the statistics
  have been collected. The usefulness of the balance is diminished as
  the trace statistics age. If the statistics are not current, the
  statistics may be cleared by specifying *CLEAR for the SET
  parameter.

  A message will be sent to the system history (QHST) log when the
  trace function is turned on, when it is stopped, or the trace data
  is cleared.

  For more information about ASP balancing, see the Hierarchical
  Storage Management Use, SC41-5351.

  -----Original Message-----
  From: midrange-l-bounces@xxxxxxxxxxxx
  [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Albert York
  Sent: Friday, October 06, 2006 1:59 PM
  To: midrange-l@xxxxxxxxxxxx
  Subject: STRDSKRGZ command


  Is anyone using the STRDSKRGZ utility? Is it something that should be
  run
  on a reular basis?
  --
  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.