The level selector allows you to associate constraints with specific SMS classes. Any clusters that are defined with specified classes acquire the constraints associated with the matching classes.
The SMSCLASS level is actually composed of three individual sub-levels. The three SMS level selectors are (from low to high precedence):
You specify the SMS level selectors as:
DCLASS=DOGS (constraints for any cluster defined in the DOGS dataclass) MCLASS=BARK (constraints for any cluster defined in the BARK management class) DCLASS=BITE (constraints for any cluster defined in the BITE data class)
Note that a cluster can belong to none, one, two, or all three SMS classes. All matching SMS class constraints are merged for each cluster.
You can specify constraints for as many SMS classes as you may have defined in your shop. You can even define SMS class constraints for SMS classes that you have not yet defined on your system, but plan to.
If you code SMS constraints, and SMS is not active on your system when you activate CA Hyper-Buf, you get a warning message to alert you to this fact. The warning does not affect CA Hyper-BufCA Hyper-Buf safely ignored - although you may want to start the SMS subsystem, if that is your intention.
The SMS class names that you specify can be generic or full class name specifiers. Generic names are discussed more fully on page 2-15 for Clusters.
|
Copyright © 2011 CA.
All rights reserved.
|
|