Migration Information › Bind the Utility Plans and Packages

Bind the Utility Plans and Packages

In this step, do the following:

• Bind the CA Repository for z/OS utility plans and packages
• Grant access to the bound plans

Once the plans and packages are bound, CA Repository GRANTs access to PUBLIC for the CA Repository plan. Granting to PUBLIC saves time required to enroll new users and saves DB2 connection time when checking for plan access privileges.

To bind the utility plans and packages

1. At the Installation Customization Menu, select option 9 Plans. The DB2 Plans and Packages screen appears.

   -------------------------- CA Repository for z/OS ----------------------------
   ---------------------------- DB2 Plans and Packages --------------------------
   COMMAND ===>                                                                  
                                                                                 
    Prepare Packages ...                                                         
    Utility, All, or Foreign packages?  ===> U  (U, A, F)                        
                                                                                 
           Set SQLID to? ===> ARZUSER                                            
             BIND Plans? ===> Y (Y-yes,N-no)       Auth ID of Plan? ===>         
        Grant to PUBLIC? ===> N (Y-yes,N-no)                                     
     Foreign Cat SSIDs?  ===>        ===>        ===>                            
     Foreign Cat DB2VER? ===>        ===>        ===>                            
         Edit or Submit? ===> E (E-edit,S-submit)                                
            Save Output? ===> N (Y-yes,N-no)                                     
         Output Data Set ===>                                                    
                                                                                 
   Enter ENTER command to continue or END command to EXIT.                       
                                                                                
   

2. Enter values into the fields as follows:
   • Utility, All, or Foreign packages

     Specify U to bind only the Utility packages.

   • Set SQLID to

     The SQLID you want to use when creating the plans.

     If you enter a value in this field, a SET CURRENT SQLID statement is added to the beginning of the job.

   • BIND Plans

     Specify Y to bind the plans and packages.

   • AUTHID of Plan

     Specifies the AUTHID to use for the OWNER parameter of the bind.

   • Grant to PUBLIC

     Specify Y to grant access to the generated plans to the special DB2 ID, PUBLIC.

     PUBLIC access to a plan does not grant individual users access to the Repository data. We recommend that this switch be set to Y during the initial repository installation.

   • Foreign Cat SSIDs

     Leave blank.

   • This field should be blank during the initial installation.
   • Foreign Cat DB2VER

     Leave blank.

     This field should be blank during the initial installation.

   • Edit or Submit

     Specify E.

   • Save Output

     Specify Y to save the generated JCL in the data set specified in Output Data Set.

     Specify N to discard the JCL after running the job.

   • Output Data Set

     The fully qualified name (without quotation marks) of the partitioned data set you want to use to save the JCL that this step generates.

   Ensure that you change the names if you do not want to overwrite any previously saved JCL.

3. Press Enter.
4. Check the generated JCL before submission and correct any conflicts with your system environment.
5. Submit the job and check the output for errors. Things to look for include:
   • Occurrences of the word UNSUCCESSFUL in the job output.

     Unsuccessful BINDs that you can ignore are listed in the following table. If any unsuccessful BINDs occur that are not listed in the table, report them to CA Technical Support.

   • A non-zero return code for the job.

If the job ends with any return code other than 0, contact CA Technical Support.

1. Press PF3 twice to return to the Installation Customization Menu.

Note: The plan and collection names that this step generates are written to the DBXPARM member in the CAI.SHLQ.CUST.ISPPLIB data set for use after the installation.