z/OS MVS Planning: APPC/MVS Management
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Examples ssing ASCHPMxx Parmlib members

z/OS MVS Planning: APPC/MVS Management
SA23-1388-00

Because of the cumulative way the ASCHPMxx parmlib members interact, you might consider creating a separate member for:
  • Initial setup
  • Each anticipated modification
  • Deletion of each class
For example, you could create the following parmlib member for initial setup:
Figure 1. ASCHPM1S
  CLASSADD
    CLASSNAME(FAST)
    MAX(10)
    MIN(2)
    RESPGOAL(.01)
    MSGLIMIT(200)

  CLASSADD
    CLASSNAME(SLOW)
    MAX(5)
    MIN(0)
    RESPGOAL(60)
    MSGLIMIT(300)

  CLASSADD
    CLASSNAME(MULTI)
    MAX(1)
    MIN(1)
    RESPGOAL(.1)
    MSGLIMIT(500)

  OPTIONS
    DEFAULT(SLOW)
    SUBSYS(JES2)

  TPDEFAULT
     REGION(2M)
     TIME(1,30)
     MSGLEVEL(1,0)
     OUTCLASS(J)
Along with the initial setup, you might consider creating parmlib members for anticipated modifications such as:
  • Changing the default class for varying system workloads
  • Modifying the MAX and MIN parameters of a class for tuning purposes.

For example, you could create the following parmlib member for changing the default class from FAST to SLOW for second shift:

Figure 2. ASCHPM2M
  OPTIONS
    DEFAULT(SLOW)

You could also create the following parmlib member for increasing the MAX and MIN values for class FAST, and use it to tune scheduler performance:

Figure 3. ASCHPM1M
  CLASSADD
    CLASSNAME(FAST)
    MAX(15)
    MIN(10)
    RESPGOAL(.01)
    MSGLIMIT(200)

You might also want to create parmlib members for deleting each class. The following parmlib members delete each of the classes shown in the CLASSADD statements listed above.

Figure 4. ASCHPM1D
  CLASSDEL
    CLASSNAME(FAST)
Figure 5. ASCHPM2D
  CLASSDEL
    CLASSNAME(SLOW)
    WORKQ(PURGE)
Figure 6. ASCHPM3D
  CLASSDEL
    CLASSNAME(MULTI)
    WORKQ(DRAIN)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014