Secure and insecure Production Reporting jobs are handled differently. For secure jobs, security tags are applied to report sections. The following topics explain what secure jobs are and how their security is accomplished and protected.
If the Production Reporting programmer applies security tags to report sections, thereby restricting access to the sections to specified users, the report is secure. Production Reporting produces only HTML output (with images) for a secure report. For details on programming a secure Production Reporting report, see your Production Reporting documentation.
When a secure Production Reporting job is run, the security tags are written to the Production Reporting. When the document is executed, each resulting HTML file is given a security tag assuring that only users authorized to see all data in the file can see the file.
It is important to set the bursting (or demand paging) options appropriately for a secure report, so the resulting files correspond to the way that the Production Reporting program divided data among users. If you do not burst the Production Reporting document correctly, security is preserved, but some users may not have access to data that they should be able to see.
The Production Reporting document written by running a Production Reporting program can be imported into the repository. Executing a secure document yields the same output with the same access privileges as executing the secure job.