Results 1 to 2 of 2
  1. #1
    Join Date
    May 2005
    Location
    Bangalore, India
    Posts
    35

    Unanswered: WLM - Is it neccessary to associate Work Action Set to a Service Class

    DB2 9.7 Fp 7 on AIX

    Hi,

    I am in a process of setting up WLM for our environment. Regarding this I have a doubt. In almost all examples that I see for defining Work Action Set and Work Actions, a work action set is associated to a service superclass and work actions to service subclasses. I am wondering is it necessary to do it, if not what is the benefit to do it.

    At this stage all I want is to collect detailed activity information for the work classes I have defined. The work actions give us a capability to collect this information, so why associate them to service class and have service class to collect information.

    e.g. of DDL Stmts

    ---------------------------------------------
    --DDL Statements for Work Class Sets

    -----------------------------------------------

    CREATE WORK CLASS SET "CONTROL_COST"
    ( WORK CLASS "LOWCOST" WORK TYPE DML
    FOR TIMERONCOST FROM 0 TO 60000 ,
    WORK CLASS "MIDDLECOST" WORK TYPE DML
    FOR TIMERONCOST FROM 60000 TO 2000000 ,
    WORK CLASS "HIGHCOST" WORK TYPE DML
    FOR TIMERONCOST FROM 2000000 TO UNBOUNDED );


    ---------------------------------------------
    -- DDL Statements for Work Action Sets (without using Service class)

    -----------------------------------------------
    CREATE WORK ACTION SET "QUERY_COST"
    FOR DATABASE
    USING WORK CLASS SET "CONTROL_COST"
    (WORK ACTION "MAP_HIGHCOST" ON WORK CLASS "HIGHCOST"
    COLLECT ACTIVITY DATA ON COORDINATOR DATABASE PARTITION WITH DETAILS,
    WORK ACTION "MAP_MIDDLECOST" ON WORK CLASS "MIDDLECOST"
    COLLECT ACTIVITY DATA ON COORDINATOR DATABASE PARTITION WITH DETAILS",
    WORK ACTION "MAP_LOWCOST" ON WORK CLASS "LOWCOST"
    COLLECT ACTIVITY DATA ON COORDINATOR DATABASE PARTITION WITH DETAILS);


    ---------------------------------------------
    -- DDL Statements for Work Action Sets (using service class)

    -----------------------------------------------
    CREATE WORK ACTION SET "QUERY_COST"
    FOR SERVICE CLASS "SUPERCLASS"
    USING WORK CLASS SET "CONTROL_COST"
    (WORK ACTION "MAP_HIGHCOST" ON WORK CLASS "HIGHCOST"
    MAP ACTIVITY WITH NESTED TO "HIGHCOST_CLASS",
    WORK ACTION "MAP_MIDDLECOST" ON WORK CLASS "MIDDLECOST"
    MAP ACTIVITY WITH NESTED TO "MIDDLECOST_CLASS",
    WORK ACTION "MAP_LOWCOST" ON WORK CLASS "LOWCOST"
    MAP ACTIVITY WITH NESTED TO "LOWCOST_CLASS")

  2. #2
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Hi,

    If your goal is to collect activity data only, then it's not necessarily to use service classes.
    Service classes may be useful if you want to:
    - set different [agent | prefetch | bufferpool] priorities for different activities
    - use priority aging
    - use OS WLM
    - set CPU [shares | limits] (db2 10.x)
    Regards,
    Mark.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •