Previous Topic

Next Topic

Book Contents

Book Index

Preventing reports from being published before approval

Reports that have not yet been approved can be prevented from being viewed and printed by users other than those defined in the Approval name.

To prevent reports from being viewed before approval

  1. Define the Approval name as follows:

    The Approval tree is comprised of a hierarchy of Approval names. Each Approval name can view and approve reports of Approval names situated below. For more information, see the section on Defining the Approval tree in the Control-D and Control-V User Guide.

  2. Assign a report for approval by adding a DO APPROV statement in the decollation definition with the following specifications:

    Users can also approve one report, and grant approval to all other reports related to the same $SYSDATA. For this option, specify the value of Multi as S. If the Hidden value is Y, all reports related to the same $SYSDATA, are also hidden.

    If the report for approval, is created as a result of a STORE = Y print mission, specify the value of STORE as Y.

    DO

    WHEN LINE 00020 - 00060 COL 00020 - 00024 PRINT   REF NXT   CT     AND/OR

         STRING = TOTAL

    DO APPROV  = FINANCE HIDDEN Y MULTI STORE N SLA 5

    DO

    For more information on DO APPROV, see the section on Decollation Mission Parameters in the Control-D and Control-V User Guide.

    Note: It is also possible to add approval attributes, using the User Permanent file. For more information, see the section on Permanent User Report List File in the INCONTROL for z/OS Administrator Guide.

    During the decollation process, an Approval Object is created for each report with a valid approval definition. The Approval name is checked against the Approval tree and if there is a match, the Approval Object is created. The SLA (Service Level Agreement) for the report is then added to the Approval Object. Once the report is either approved or rejected the Approval Object is deleted. Approval Objects can be viewed in the DO.5 screen. For more information, see the Control-D and Control-V User Guide.

    Each user must filter for the reports that are assigned to them for approval using the Control-D/WebAccess Server. For more information, see the section on filtering for reports that need approval, in the Control-D/WebAccess User Guide.

  3. Run the CTDAPRV utility, as needed, in order to:

For more information, see the INCONTROL for z/OS Utilities Guide.

Note:

Parent Topic

Approving reports