Re: WLM Service Definition for DDF Thread

2006-04-24 Thread Ted MacNEIL
1  SI   DBP1
2PN   FIPLAN DB2TTRAN
2PN   MANTIS DB2PTRAN
2PN   *

DBP1 is our production subsystem.  I assume that DBTTRAN has a lower 
priority than DB2PTRAN.  (Because FIPLAN is mostly batch against 
production and MANTIS is mostly online.) 

Can't make that assumption here.
You need to know how the two service classes are defined.
Different set of panels to look that up.


I assume the asterisk is to 
prevent our DDF threads from falling into the default discretionary class. 


Since there is no service class defined on the same line as '*', it will fall 
into what ever is defined as your default class for DDF work.
If that's discretionary, it will be discretionary.

-
-teD

O-KAY! BLUE! JAYS!
Let's PLAY! BALL!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: WLM Service Definition for DDF Thread

2006-04-24 Thread Steve Samson

Steve

It appears that the first level definition does not specify a default 
service class for SI DBP1. Therefore the asterisk does exactly what it 
should, putting the fallthrough threads in DISC.


The problem can be remedied by specifying as follows:

1 SI DBP1DB2TTRAN
2  PNMANTIS  DB2PTRAN

All the non-MANTIS transactions will go to DB2TTRAN. A level 2 
definition is an exception to the general rule that the first hit fixes 
the classification. If a different default from DB2TTRAN is necessary, 
put it on the level 1 line and add a level 2 for PN FIPLAN. If the 
MANTIS transactions are more important or much more numerous than the 
others, put the MANTIS rule as the first level 2, to save some minuscule 
increment of processing time.


The asterisk catcher is unnecessary here. It was a leftover from the 
days of implicit classification of STCs.


Cheers,

Steve Samson

Steve Grimes wrote:
Hello, DB2 V7.1, z/OS 1.4, WLM Goal Mode here, with DB2 PM, cross posting 
to DB2-L and IBM-Main, here!


There is a lot written about this topic in the archives, and I'm also 
looking at other resources (Hugh Smith presentation, DB2 Admin guide, 
etc.) but I'd like to make a recommendation to our Systems folks this 
afternoon and would appreciate any perspective anyone can offer:


Here is an excerpt  from our WLM DB2 Transaction Classification screen:

1  SI   DBP1
2PN   FIPLAN DB2TTRAN
2PN   MANTIS DB2PTRAN
2PN   *

DBP1 is our production subsystem.  I assume that DBTTRAN has a lower 
priority than DB2PTRAN.  (Because FIPLAN is mostly batch against 
production and MANTIS is mostly online.)  I assume the asterisk is to 
prevent our DDF threads from falling into the default discretionary class. 
 (Is this true?)


My issue is that I would like to throttle our users MSACCESS threads to 
this DBP1 subsystem.  Could this be as simple as adding:


2CI   MSACCESS   DB2TTRAN 

To the above list?   (DB2 PM says MSACCESS is the 'Correlation Name'.  It 
also says MSACCESS.EXE is the 'Client Application Name'.)  I get plenty of 
'Thread Id' stuff from PM, but am having trouble mapping it to the 'WLM 
Classification Attribute' abbreviations in the DB2 Admin guide.


Is there a better approach? 


Thanks in advance!

Stg


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html