APAR status
Closed as documentation error.
Error description
Out of memory errors can occur as a result of a report running but cannot identify which report. So we need a way to identify the report that is running, who ran it, how long it is running so analysis can be provided.
Local fix
Problem summary
Adding a place on the Performance WIKI on how to enable report run history tracking.
Problem conclusion
Enable report tracking system wide In the 3.5.1 release, a new flag was added to reports to enable them to be tracked over time. This tracking includes who ran the report, when it was run, and the total duration the report took to complete. By default this is disabled, however it may be a good idea to enable full tracking across all reports in the system to help trace performance issues, and usage over time. To enable this, run the following statement: update rep_template_hdr set rep_track_history = 1; On Oracle commit.
Temporary fix
Comments
APAR Information
APAR number
IV95201
Reported component name
TRI APP PLTFM R
Reported component ID
5725F26RE
Reported release
342
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-17
Closed date
2017-04-20
Last modified date
2017-04-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"342","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 March 2022