Report Definitions define how and when a report will be generated for a Node. The Report Definition can be run manually or it can be scheduled to run at defined intervals.
The output created by running a Report Definition will be stored in a user designated output queue on the Hub. The output can also be stored in a user designated output queue on the Node and/or emailed to the Contacts for the Node.
IBM plans to withdraw the heritage Navigator for i. IBM and HelpSystems continue to work on the strategy for the BRMS product and its interfaces. As an alternative to accessing BRMS in the heritage Navigator for i, customers can use the BRMS SQL services.
Starting with PTFs SI80271 (7.3), SI80272 (7.4) and SI80273 (7.5) the Report Policy concept is no longer used.
Report Policy
Each Report Definition has an associated Report Policy. The Report Policy defines properties that can be shared between multiple Report Definitions. Each Report Definition can reference the Report Policy for any of its properties.
Report
When a Report Definition is run for a Node, a Report is generated. Each Report will identify when the Report Definition was run, what Report Output was produced and where the Report Output was stored.
NOTE:
The report definition and report policy Command to run field can only be used to specify a command with parameters that generate spooled files. Parameters specified for the command that cause results other than spooled file generation will be ignored. For example, if the Start Maintenance for BRM (
STRMNTBRM) command is specified for the Command to run field, the following parameters will be ignored when the report is run:CHGJRNEXPMEDEXPSETMEDMOVMEDREFREERGZBRMDBRMVMEDIRMVLOGERMVMGRINFRUNCLNUP
Report Output
Report Output is produced when a Report is run for a Report Definition. The Report Output can be found through the Report that identifies when the Report Definition was run. Report Output may include multiple files.