Steven,
If you want to add target criteria to a workload so that all stored procedure CALL statements will run there you would select Target Critieria, then Stored Procedure in the drop down box. Then in the Database box put "*" and then in the Stored Procedure box put "*". That will catch all SP CALL statements from all databases. I was a little confused what you meant by "object=*" but maybe you were referring to the stored procedure object type.
However, there is a problem with this approach: If you have user classification of "user=*' as well, as you would likely have if this was your parsing workload, then TASM will AND the user and the SP classification together. So then both the user and the SP classification would have to be satisfied, with the end result that only SP call statements will classify there. There is no OR capability supported between unlike criteria types.
Might be cleaner to just set up a separate workload for CALL statements. You can still run it at a high priority if you wish. Doing so would also make it easy for you to break out SP calls independently for monitoring things like resource usage, etc.
Thanks, -Carrie
Steven,
If you want to add target criteria to a workload so that all stored procedure CALL statements will run there you would select Target Critieria, then Stored Procedure in the drop down box. Then in the Database box put "*" and then in the Stored Procedure box put "*". That will catch all SP CALL statements from all databases. I was a little confused what you meant by "object=*" but maybe you were referring to the stored procedure object type.
However, there is a problem with this approach: If you have user classification of "user=*' as well, as you would likely have if this was your parsing workload, then TASM will AND the user and the SP classification together. So then both the user and the SP classification would have to be satisfied, with the end result that only SP call statements will classify there. There is no OR capability supported between unlike criteria types.
Might be cleaner to just set up a separate workload for CALL statements. You can still run it at a high priority if you wish. Doing so would also make it easy for you to break out SP calls independently for monitoring things like resource usage, etc.
Thanks, -Carrie