Siebel Database Upgrade Guide for DB2 UDB for z/OS > Upgrading the Target Database > Performing the In-Place Target Database Upgrade >

Creating and Deploying Stored Procedures on the Target Database

Perform the following task to install stored procedures and functions on the target database and to verify that they deployed correctly.

To install and verify stored procedures

1. On the Target Database In-Place Upgrade Menu, select option 6: Create SPs & Functions (Bind), and press Enter.

   A message appears informing you that you should use the instructions in the @README member to install the stored procedures and functions.

2. Enter Y to continue, and press Enter.

   You are placed in edit mode for PDS dataset DSNHLQ.SIEBEL.SP.CNTL.

3. Select the DSNHLQ.SIEBEL.SP.CNTL(@README) PDS member.
4. Review the instructions in the @README file.
5. Select the IEBCOPY PDS member and submit the JCL in the dataset DSNHLQ.SIEBEL.SP.CNTL(IEBCOPY).

   This job moves the stored procedure load modules into the WLMSPAS (this is the WLM load library you specified in Preparing the Upgrade Environment and Building the Staging Database).

6. Verify that the job ran successfully, RC=0.

   The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

7. After submitting the job, enter cancel on the command line or press PF3 to save changes.
8. Select the PDS member for your upgrade path:
   • Use BINDHOR if you are upgrading a Siebel 7.0.4, 7.5.2, or 7.7 application.
   • Use BINDSIA if you are upgrading a SIA 6.2.1, SIA/FINS/SIS 7.0.4, SIA 7.5.2, or SIA 7.7 application.

     This places you in edit mode for PDS dataset member DSNHLQ.SIEBEL.SP.CNTL(BINDSIA) or DSNHLQ.SIEBEL.SP.CNTL(BINDHOR).

     This job binds the stored procedure packages.

     NOTE:  A DROP procedure job is included (DSNHLQ.SIEBEL.SP.CNTL (DRPSIA) or DSNHLQ.SIEBEL.SP.CNTL (DRPHOR)). If the procedure already exists, you must drop it before running the bind job.

9. Verify that the job ran successfully, RC=0 or RC=4.

   The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

10. After submitting the job, enter cancel on the command line or press PF3 to save changes.
11. Select the WLMREFSH PDS member and submit the JCL in the dataset DSNHLQ.SIEBEL.SP.CNTL(WLMREFSH).

    This job refreshes the DB2 WLM environment.

12. Verify that the job ran successfully, RC=0.

    The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

13. Press PF3 to return to the Target Database In-Place Upgrade Menu.
14. Select option 7: Verify SP and Function Deployment, and press Enter.

    This places you in edit mode for one of the following PDS datasets and members:

    • For Siebel Business Application upgrades: DSNHLQ.SIEBEL.SP.CNTL(SPVHOR)
    • For Siebel Industry Application upgrades: DSNHLQ.SIEBEL.SP.CNTL(SPVSIA)
15. Run the JCL in the appropriate dataset for your upgrade. The JCL in the SPVSIA and SPVHOR members executes each stored procedure against the target database after the new schema has been created and data has been loaded onto the target. This process verifies that the stored procedures have been installed and can be executed.
16. Verify that the job ran successfully, RC=0.

    The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

17. After submitting the job, enter cancel on the command line or press PF3 to save changes.