In operation, the ReportCenter control region and the ReportCenter Java Task access all the necessary HFS files. In some special cases, you may need to access the ReportCenter HFS files manually. You can use any of the standard IBM OMVS functions, such as OBROWSE or OEDIT, to do so.
For performance and space reasons, the WebCenter Java Task Log option shows only the most recent log records. To examine the complete ReportCenter Java Task logs, look at all AdaptorNNN.log files in directory ?ics_prefix3/nm/reporter/usr/logs/...
Adaptor001.log is the current log, and the file with the highest number is the oldest.
If you are asked to forward your ReportCenter Java Task log files to Technical Support, transfer the entire contents of the ?ics_prefix3/nm/reporter/usr/logs/... directory as text, in zipped format.
Directory ?ics_prefix3/nm/reporter/usr/logs/... also contains status files written by the scheduled ReportCenter services. These files contain the last run status of the service. The filenames are SERVICENAME.log, for example, AGGREGATION.log.
The initialization parameters used by the ReportCenter Java Task are stored in the .../nm/reporter/usr/adaptor/Adaptor.ini file.
They are customized to reflect your input, the first time you update and action the REPORTCENTER Customizer parameter group on the ReportCenter control region.
If you want a greater level of customization, such as service timers or data retention rules, you can update this file manually.
Be careful, as errors can cause malfunctions in the ReportCenter Java Task. Make a backup copy of this file before you modify it.
You must then restart the ReportCenter Java Task to pick up your modified parameters.
Next time the REPORTCENTER parameter group is applied (for example, at ReportCenter control region startup), it will not override your manual updates. The parameter group only regenerates this file if the file is not customized.
To regenerate the file
Important! Never alter any files in any of the .../wr76/... directories. These files are maintained by SMP. Modifying these files can cause product malfunction. Changes made to these files will be lost after SMP/E maintenance.
| Copyright © 2012 CA. All rights reserved. |
|