|
|
|
This HFS directory contains both system files and user files, such as your generated report output and your report schedules.
Note: Any HFS directories and files created prior to r11.5 are obsolete. If you do not want to save any of your report output or schedules, use the new ReportCenter HFS directory.
The HFS files supplied with ReportCenter r11.7 were installed in the wr65 directory.
These old files do not work with ReportCenter Release 12.1. A new SMP/E target library directory is created during the installation of ReportCenter Release 12.1, and named …/nm/reporter/wr76/….
In general, use new, separate user HFS directories in ReportCenter Release 12.1. If you implement any of the exceptions described later, ensure that only the specified files and subdirectories are reused. Incompatibilities between these files in this release and files in previous releases can cause unforeseen errors.
For the purpose of migration, prefix_Release 12.1 refers to the ?iia_prefix you used for Release 12.1 and prefix_r117 refers to the ?iia_prefix you used for r11.7.
The Java Task parameters for ReportCenter r11.5 were generated into the …/nm/reporter/usr/adaptor/… user directory.
These parameters are not compatible with ReportCenter r11.6 and above. If you reuse the directory, delete all files from it first. They are regenerated when you apply the REPORTCENTER parameter group in the ReportCenter control region.
If you have a customized version of the Adaptor.ini file, note your changes, and print or save a copy of this old file. After the new Adaptor.ini file is generated, make your changes again to this new file.
Prompts for ReportCenter r11.5 were generated into the …/nm/reporter/usr/prompts/… directory.
Although you may use the old database for ReportCenter r11.6 and above, some prompt file names have changed between versions. If you reuse this directory, delete all files from it first. They are regenerated when the Prompt Generator service runs.
Schedules that you added for ReportCenter r11.5 and r11.6 were saved into the …/nm/reporter/usr/schedules/… directory.
The schedule control file (report.sched) format has not changed.
To retain your existing report schedules, do one of the following:
mv -R prefix_r117/nm/reporter/usr/schedules/* prefix_Release 12.1/nm/reporter/usr/schedules/
Note: For a description of the mv command, see IBM's UNIX System Services Command Reference.
ReportCenter Java Task log files for ReportCenter r11.5 through r11.7 were written to the …/nm/reporter/usr/logs/… directory.
Although the log file format is unchanged, there should be no requirement to retain log files from a previous release. If you reuse this directory, delete all files from it first. This action ensures that it contains only logs from the current version and avoids potential confusion while browsing logs.
Report output for ReportCenter r11.5 through r11.7 was placed into the …/nm/reporter/usr/output /… directory.
Most report output is kept for short periods, and it is not common to keep it from one version to another. If you want to retain report output, we recommend that you keep the same output directory for reports. Specify it in the REPORTCENTER parameter group in the ReportCenter control region.
The Report Expiry service of ReportCenter r11.6 and above deletes expired report output from all versions.
Important! Do not use report definition files with a different version of ReportCenter. The XML DTD is different, and the files do not work.
| Copyright © 2012 CA. All rights reserved. |
|