Enforcement Priority: Soft, Hard, or Just Window-Dressing? - comment by geethareddy

Fantastic! I am so glad that my puzzle has been resolved. Thank you very much Carrie.

Actually I read from the DB admin manual that,"When TASM workload definition (Category 3) is enabled, the PG portion of the ASE is ignored for purposes of priority assignment. Instead, workload classification determines the priority of the request. However, for the small amount of time that the first request of a session is being parsed prior to classification into a workload, the PG within the account string is used to establish priority."
From this above extract, I am not clear about what kind of work performed during that "small amount" of time.
For ex: I have a Batch User (BU1) under tactical enforcement priority who gets the resources from tactical resource partition. I defined the workload rule (WL1) on that user by defining the classification on ASE (on eg: $L$TACT&s7D&H). So in this case, eventually BU1 gets the tactical resouces, but I am not clear about that $L Performance Group defined in its account string and what exactly it plays a role for that "small amount" of time mentioned above in the extract.

There is a reason why i am asking this question so persistingly. We have current Account strings almost 800+ where almost 750+ are starts with $M on prod. There are some new users still not yet defined with any ASE. So my ONLY concern here is, how do i need to set them up. I understood that even if i create them with $R or $H it does not matter, becuase everything is controlled by TASM. And i am also considering that this is true for both APPLIANCE and ENTERPRISE platforms. Please clarify this for me.