A user was trying to monitor a WLM AE (workload manager application environment).
There were multiple application environments with the same name running on the LPAR. The user was able to determine which of the application environments he wanted to monitor. In the MAT panels (option 2 Active Jobs), he typed an 'M' next to the task he wanted to monitor, verifying it by address space number. However, this is not the task that was monitored. MAT monitored one of the other same named application environments. We don't understand why MAT didn't monitor the task that was selected.
This does not seem to be working as desired. Is there something we should do differently in order to get MAT to monitor the desired task?
The ASID isn't used by Mainframe Application Tuner (MAT) to target an application from the Active display and you can't request the ASID in a monitor definition.
We only target the application by Jobname, Stepname, Procstepname and finally programname. We have a couple of enhancement requests to change this.
However, there is a TUNCALL parm, ASID, that you can submit via a batch measurement request, providing it the ASID and it will focus only on that ASID regardless of what the jobname or other parms are.
Here is a sample TUNCALL JCL to measure an STC with ASID of 131
//TUNCALL EXEC PGM=TUNCALL
//STEPLIB DD DISP=SHR,DSN=hlq.MATRB0.LOADLIB
// DD DISP=SHR,DSN=hlq.CEESPLD
//TUNPRINT DD SYSOUT=*
//TUNIN DD *
MATB0LS MONITOR INVOKE JOBNAME(SPIBTEST) ASID(131)
As long as WLM STC 219 or 218 are up and running, you should be able to submit this request and get a measurement for the STC you want.
The measurement request will be built in the GIF...