News
Abstract
Performance Data Investigator (PDI) uses PML packages for the definition of the charts and queries used to perform the chart display and interaction with the Collection Services data. With the New Navigator for i, the delivery of the packages has changed. The packages are now included in the JAR file for PDI. This document explains how the changes affect any custom or modified packages you use.
Content
You are in: IBM i Technology Updates > Performance Tools > Performance on the web > Packages & Perspectives > PML
The shipped packages have not changed. However, where the files are shipped and read in from is new. They are no longer provided in an IFS file (/QIBM/UserData/OS400/Navigator/config/PML). The serialized files are shipped with the PDI JAR file for security. The shipped files override any that are in the IFS location from the heritage navigator.
If you modified the shipped PML files, these are no longer read in by PDI. In order for PDI to read in a customized PML file, it needs to have a unique file and ID name from the files that we ship with PDI.
Any custom content in the subdirectory "CCP" is still read in for each user when they are logged in. The location is: /QIBM/UserData/OS400/Navigator/config/PML/CCP. Any additional PML files in the standard PML directory are only read in and available from PDI if the files have unique file names and unique internal IDs associated with them.
The shipped files are:
| Package | File Name | Collection Type | ID |
|---|---|---|---|
| Collection Services | cs_package.pml & cs_package.pml.ser | *CSFILE - standard | IBM_CS |
| Health Indicators | ghi_package.pml & ghi_package.pml.ser | *CSFILE - standard |
IBM_GHI
|
| Monitor | mn_package.pml & mn_package.pml.ser | *CSFILE - monitor collection | IBM_MN |
| Database | sql_package.pml & sql_package.pml.ser |
*CSFILE
Also, Database:
- plan cache snapshots
- event monitor
- SQL performance monitor
|
IBM_DB |
| Disk Watcher | dw_package.pml & dw_package.pml.ser | *DWFILE | IBM_DW |
| Job Watcher | jw_package.pml & jw_package.pml.ser | *JWFILE | IBM_JW |
| Performance Explorer | pex_package.pml & pex_package.pml.ser | *PEXFILE | IBM_PEX |
|
Batch Model
* not shipped with new Nav
|
bm_package.pml & bm_package.pml.ser | *BMFILE | IBM_BM |
Private packages are also created to keep the PML files from getting large. These PML files are read into the top package folder and shown as part of the top-level package.
| Package | File Name | Collection Type | ID |
|---|---|---|---|
| Collection Services |
cs_delta_61.pml & cs_delta_61.pml.ser
cs_delta_71.pml & cs_delta_71.pml.ser
|
*CSFILE - standard |
IBM_CS_DELTA_61
IBM_CS_DELTA_71
|
| Collection Services | cs_disk.package.pml & cs_disk.package.pml.ser | *CSFILE - standard |
IBM_CS_DISK
|
| Collection Services | cs_storage_allocation.package.pml & cs_storage_allocation.package.pml.ser | *CSFILE - standard | IBM_CS_STORAGE_ALLOCATION |
| Job Watcher |
jw_delta_61.pml & jw_delta_61.pml.ser
jw_delta_71.pml & jw_delta_71.pml.ser
|
*JWFILE |
IBM_JW_DELTA_61
IBM_JW_DELTA_71
|
| Job Watcher | jw_storage_allocation.package.pml & jw_storage_allocation.package.pml.ser |
*JWFILE
|
IBM_JW_STORAGE_ALLOCATION |
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CH1AAM","label":"IBM Navigator for i"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.3.0;7.4.0;and future releases"}]
Was this topic helpful?
Document Information
Modified date:
24 September 2021
UID
ibm16492607