topic Re: MeasureWare Application Definitions in Operating System - HP-UX

MeasureWare Application Definitions

Kelley Beckett — Thu, 03 Aug 2000 13:36:58 GMT

I am trying to define applications within the MeasureWare parm file. My problem is that I have several different applications using the same executable but with different options which I can see in the output of a ps command. When I put the option in the file statement the processes end up in the "other" category. Is there anyway to define each application?

Re: MeasureWare Application Definitions

John Palmer — Thu, 03 Aug 2000 14:04:14 GMT

The 'file' parameter in parm referes to the program name (max 15 chars). This is the program name only with no provision for arguments.

Can you distinguish the processes by 'user', 'group' or 'priority'.

If so then you can combine say 'user' and 'file' to define an application.

Hope this helps,

Regards,

John

Re: MeasureWare Application Definitions

Tim Malnati — Thu, 03 Aug 2000 14:12:14 GMT

Is it possible for your application to call a different executable that does the same thing? What I'm suggesting is that you create a script with a different name that calls the original executable and have Measureware watch for this new process name instead. The script could either pass the options, or they could be hard coded if they don't change.

Re: MeasureWare Application Definitions

Jim Welch — Thu, 03 Aug 2000 23:42:33 GMT

The only problem with that is that if you are looking for resource usage the resources will go to the app that gets the original process....you would have to copy the file N times and have the calling programs call the one you want....say if you have a program xxx that is used to access 4 different databases or instances and the difference is only in the calling parms...maybe the database instance is one of the parms. You could copy the program and give each copy a name like xxx_inst1, xxx_inst2, and so on, then put a script in place called xxx that looks at the parms and calls the correct copy with the same parms it was passed. Then your parm file would have an app defined for each instance with 'file = xxx_inst1' for app instance 1 and so on...But that may be more trouble than it's worth.
You can only assign processes to applications in the parm file based on filename, user, group, or priority.