A Closer Look at How to Set up a Parsing-Only Workload - comment by carrie

Geeta,
 
Try redefining the POW workload classification without the Profile=* part.  Unless you are 100% sure that all your users have profiles, it could be problematic in this case.
 
Just to re-iterate one of the points mentioned above related to Profiles:
 
"It is recommended that the Profile classification criterion not be used in defining a parsing-only workload, unless all users accessing the platform have an actual Profile assigned. When there is wild card classification on Profile (Profile = *), any session that logs on without providing a Profile will be disqualified from the workload."
 
Any session where a user does not have a profile assigned will not classify to the POW workload the way it is defined.
 
Also,  I'd suggest you reconsider how you setup the criteria to exclude queries from executing in this Workload.  What you had was the followoing:
 
                Classfcn Criteria: USER: = *ACCTSTR: = *APPLIC: = *PROFIL: = *ALL_AMP:
                excludeMIN_EPT: 0:01:00.000
 
The exclude above looks odd to me.  I don't believe you can exclude on a minimum.  What you want is to add query characteristic criteria like EPT > or = some very large number of seconds AND that does not use all AMPs (as shown in the posting above), or some query characteristic criteria that it will be impossible for any query to classify to, like a dummy table or view name that no query will access.
 
Thanks, -Carrie