Skip to content

Setting Up Unplanned Approvals

The Unplanned Approvals definition determines who must approve packages, the order of approvals, and how approvers are notified that their approval is required.

See Package Approvals for a discussion of the difference between Unplanned and Planned Approval lists.

To create or update an Unplanned Approvals list, follow these steps:

  1. On the Update Application Administration Options panel, type 6 on the Option line and press Enter. The application - Unplanned Approvals Part 1 of 2 panel is displayed.

    CMNCAPLD        ACTP - Planned Approvals Part 1 of 2       Row 1 to 3 of 3 
Command ===> ____________________________________________ Scroll ===> CSR 

                                            Security    Order   Int.
    Approver description                    entity      no.     apr.
___ Development Team Lead                   DEVLEAD     10 
___ Quality Assurance                       QA          20 
___ Program Manager                         PGMMGR      30      YES
*************************** Bottom of data *******************************

    The following table describes the fields on the Application Planned Approvals Part 1 of 2 panel.

    Field Description
    Line Command Type a line command:
    S - Select to see the next panel for this approval.
    I - Insert a blank approval row.
    R - Repeat an existing approval.
    D - Delete an existing approval.
    Approver description Type a description of the approval.
    To avoid excessive maintenance, do not use an approver’s name.
    Security entity Type the security entity name that is used to grant authority to TSO userids to enter this approval.
    You must define this security entity in your security system. Grant the appropriate authority to TSO userids in your security system to grant approver authority to individuals. See Pre-Implementation Decisions for details.
    Order no. Type an order number if an approval hierarchy is required. Order number 00 may be approved at any time.
    A group of approvals with the same non-zero order number may be approved in any order.
    Start with order numbers 10 and increment by 10 so that other approvers can be added later.
    Link Package approvals automatically reset their order numbers to 00.

    ...

  2. On the application - Unplanned Approvals Part 1 of 2 panel, type S on the line command for an approval and press Enter. The application - Unplanned Approvals Part 2 of 2 panel is displayed.

    The following table describes the fields on the Planned Approvals Part 2 of 2 panel.

    CMNCAPL1       DEMX - Planned Approvals Part 2 of 2        Row 1 to 2 of 2 
Command ===> ____________________________________________ Scroll ===> CSR

Approver:   Development Team Lead
Entity:     DEVLEAD
Order no:   10

    Vehicle     User(s) to Notify                           Order
___ MVSSEND     USER010                                     10 
___ MVSSEND     USER020                                     20
*************************** Bottom of data *******************************
    Field Description
    Vehicle Type the vehicle used to notify approvers about packages pending approval. You may use any vehicle activated in Global Administration Parameters. You can also use MVSSEND.
    BATCH - File tailor skeleton CMN$$NTF and submit the generated JCL with Job Card Information defined in Application Administration Parameters.
    EMAIL - Send notification through SERNET to the internal email server for delivery to the specified recipient.
    MVSSEND - Issue an MVS SEND message to TSO user IDs.
    The IP address of the EMAIL (or SERNET) server is defined in global administration on the Global Parameters - Part 5 of 7 (CMNGGP05) panel. See Setting up Global Parameters.
    User(s) to Notify Type the appropriate user identifications for the notification vehicle. Separate multiple user identifications with commas:
    E-mail Address or Mailing List - Use with the EMAIL vehicle. Also use with the BATCH vehicle if REXX program CMNSMTP has been activated in skeleton CMN$$NTF.
    TSO Userid - Use for vehicle MVSSEND.

    The information on the Unplanned Approvals Part 2 of 2 panel is used to:

    • Notify an approver that there is a package awaiting for their approval.

    • Allow queries for packages awaiting approval based on TSO userids entered in User(s) to Notify.

    These rules apply when you are setting up approval notifications:

    • Approver notification is not required for an approval.

    • You can create multiple notifications for an approval.

    • You can create multiple notifications using the same vehicle.