The following explains functionality for collecting user-specific performance data and functionality for periodically executing user commands.
This functionality uses the jpcuser command to convert custom performance data output by users to a text file, into a format that can be stored in records provided by PFM - Agent for Platform (PD_UPD, PD_UPDB, PI_UPI, and PI_UPIB). To use this functionality for collecting user-specific performance data, a command must be created to output performance data to text files ahead of time.
The following figure shows how user-specific performance data is collected.
Figure 5-2 Mechanism for collecting user-specific performance data
The following describes the processing corresponding to the numbers in the figure.
To collect performance data periodically, use the functionality for periodically executing user commands to set a user command, and the jpcuser command, to execute automatically.
This functionality executes a user command from PFM - Agent for Platform at a fixed interval without using a task scheduler or other schedule functionality. The method for creating user data files from user commands is the same as described in (1) Functionality for collecting user-specific performance data.
Functionality for periodically executing user commands is executed using the same timing as record collection in PFM - Agent for Platform. After record collection processing is completed, a user data file is created by a user command, so that user data file collection processing and creation processing do not cause a race condition. Note that because functionality for periodically executing user commands is executed according to Collection Interval as set for the user record, it is executed for historical collection and alarm collection, but not for real-time collection. The following figure shows the flow of processing for functionality for periodically executing user commands.
Figure 5-3 Flow of processing for functionality for periodically executing user commands
Functionality for periodically executing user commands determines whether the previously started user command has terminated, and skips user command processing if it is executing.