Migration Information › Bind All Plans and Packages

Bind All Plans and Packages

This step binds all the CA Repository utility packages. Binding the packages at this stage is essential for later steps of the installation process.

To bind the utility 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?  ===> A (U, A, F)                        
                                                                                 
           Set SQLID to? ===> USER01                                            
             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

     A

   • 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 will be added to the beginning of the job.

   • BIND Plans

     Y

   • AUTHID of Plan

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

   • Grant to PUBLIC

     Y-to grant the special DB2 ID PUBLIC access to the generated plans. PUBLIC access to a plan does not grant individual users access to the Repository data.

   • Foreign Cat SSIDs

     Leave blank.

   • Foreign Cat DB2 Ver

     Leave blank.

   • Edit or Submit

     E

   • Save Output

     Y-to save the generated JCL in the data set specified in Output Data Set.
     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. Be sure to change the names if you do not want to overwrite any previously saved JCL.

3. Press Enter to generate the JCL.
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

     Contact CA Technical Support if the job ends with any return code other than 0.

   Note: You can ignore any +562 SQL codes on the GRANT step. This message indicates that the authority you are attempting to assign has already been given.