Troubleshooting Collection Services Historical data (Graph History) display issues.

When Collection Services Historical data fails to display the following steps can be performed to troubleshoot the problem and gather data if these steps fail to resolve the problem. 

 1.  Verify Collection Services configuration

a.      Collection Services does not create historical data by default. The following changes need to be made to enable historical data creation.

b.      This will only create data for the current collections on the system usually up to 10 days and then will create data daily after.

Use the CFGPFRCOL command (F4 to prompt) to set the following parameters (you can also set the retention intervals for this data if you would like to keep more/less days of data note that increasing the number of days collected will increase the storage used on the system):

Create historical data . . . . . CRTPFRHST *YES

Create historical detail data . CRTHSTDTL *YES

The following command can be used to directly set those params:

CFGPFRCOL CRTPFRHST(*YES) CRTHSTDTL(*YES)

After making these changes Collection Services will have to be cycled (usually occurs at midnight with default settings) or manually via:

ENDPFRCOL FRCCOLEND(*YES)

STRPFRCOL CYCCOL(*YES)

2. Verify that PM400 is fully disabled.

PM400 support was withdrawn in 2020 if it s not completely disabled it can cause issues with Historical data display and data retention. The following link contains additional info regarding this product and the steps needed to fully disable.

https://www.ibm.com/support/pages/disabling-pm-agent

3. Verify that the latest HTTP group is applied.

Performance Data Investigator/Historical data viewer PTFs are included in the HTTP group. It is also recommended that the latest Java group PTF and Performance Tools Group PTF are applied. Links to the group PTFs for your specific release can be found here:

https://www.ibm.com/support/pages/ibm-i-group-ptfs-level

4.  Historical data libraries MUST be in SYSBASE/System ASP.

Run the following commands (from a user with *ALLOBJ authority or *SECOFR class)

       DSPLIB LIB(QPFRHIST) ASPDEV(*ALLAVL)

       DSPLIB LIB(QPFRTEMP) ASPDEV(*ALLAVL)

If these libraries exist in any library other than SYSBASE they must either be moved to SYSBASE or deleted. The create historical data process will properly create these libraries the next time they run 

5. Authority considerations.

Consider using/testing with a user that has *ALLOBJ authority if you currently are using a user profile with fewer authorities on the system. If you re able to see the data after signing on to Navigator for I when using QSECOFR (or equivalent user profile) then the user profile that was originally used has inadequate authority to access the data.

6. Review the QYPSPFRHST joblog for any errors.

The following are some common errors and their resolutions. 

  MCH5802 data files locked often by another prestart job. Review the joblog for that prestart job (usually in the message details) and end the job if no longer used.

  MCH3402 or CPD0A40 RC99 also can indicate that files are locked. The QSQSRVR job listed in the QYPSPFRCOL joblog may contain these messages.

7. Force the generation of Historical data files.

The following command can be used to trigger Collection Services to process the current collection objects and to create the Historical data.

CALL QSYS/QYPSPFRHST PARM('*CONFIG' '*ALL' '*FORCE')

NOTE: This command may run for an extended period of time, depending on the number of collections that need to be processed.
If historical data still fails to display review the joblog for the job that executed the above command for any errors. If there are error please open a case with IBMi support and upload the FULL joblog for review.

8. Gather data

If Historical data fails to display (after signing on/off to Navigator for i) please gather the following data and open a case with IBMi support.

a. Change the logging level to ensure that joblogs are generated.

CHGJOBD JOBD(QSYS/QYPSJOBD) LOG(4 0 *SECLVL)

b. Start a collector trace via the following command please ensure that appropriate PTF is applied for your release or the trace will fail to start:

SJ01447 - v7r3m0f
SJ01446 - v7r4m0f
SJ01438 - v7r5m0f

Then start the trace with:

CALL QSYS/QYPSCONFIG PARM('QYPS_TRACE' '1')

ENDPFRCOL FRCCOLEND(*YES)

STRPFRCOL CYCCOL(*YES)

c. Recreate the failure to display sign off/on to Navigator for i and attempt to view the historical data please gather a screenshot of the failed display and make note of the system time. Please include this info in the case with IBMi support.

d. End the above trace:

CALL QSYS/QYPSCONFIG PARM('QYPS_TRACE' '-1')

The trace will be stored in file QUSRSYS/QPFRHSTTRC please save this file and attach to the case.

e. Joblogs

Please gather the current joblogs for the following jobs:

QYPSPFRCOL

QYPSPFRHST

Interactive job where the command from Step 5 was executed.

f.  Gather the expiration info of collection services objects.   Please gather a screen shot of all entries.  Run the following SQL statement from  STRSQL.  

SELECT CCLIB, CCCNNAME, CCCLNFMT, CCSTRDT, CCEXP2, CCSTATUS, CCPROP  FROM QUSRSYS/QAPMCCCNTB WHERE CCLIB = '<Your Collection Services Library name in caps>' and CCCLNFMT = '*CSMGTCOL' ORDER BY CCLIB, CCCNNAME

g. HTTP Admin Collector

Please use the instructions in the following document to gather HTTP Admin collector data.

https://www.ibm.com/support/pages/node/645361

h. Change the logging level back to the default value.

CHGJOBD JOBD(QSYS/QYPSJOBD) LOG(4 0 *NOLIST)

ENDPFRCOL FRCCOLEND(*YES)

STRPFRCOL CYCCOL(*YES)

i. upload all of the generated data:

- QYPSPFRCOL joblog

- QYPSPFRHST joblog

- Interactive joblog for the job that ran step 5

- QUSRSYS/QPFRHSTTRC savf (generated in 6d)

- HTTP Admin collector file

- screen print of the Historical data screen and time stamp