Bookshelf Home | Contents | Index | PDF     

Siebel Database Upgrade Guide for DB2 for z/OS > Creating the Siebel Staging Database > Preparing the z/OS Upgrade Environment and Creating the Staging Database >

Preparing the Upgrade Environment and Building the Staging Database

After the files transferred from the midtier have been defined and allocated, you must set up the z/OS system environment variables, receive the files (uncompress the files), create JCL libraries, create the staging database, and assign jobname prefixes. The following procedure describes how to perform these tasks.

To set up the z/OS upgrade environment and build the staging database

  1. Enter the following command and press Enter:

    TSO SBLUPG81

    The Siebel In-Place Upgrade Main Menu appears. The panel ID is SBLUPG8P. You can find the panel ID in the bottom right corner of the screen.

    TIP:   To access Help on any screen, press PF1. To exit Help and return to the prior screen, press PF3.

  2. On the Siebel Upgrade Main Menu, select option 0: Environment Setup, and press Enter.

    The Staging Database Environment Setup Menu appears. The panel ID is SBLSSETP. The options on this panel allow you to prepare files and set environment variables to create the staging database.

  3. On the Staging Database Environment Setup Menu, select option 0: Set System Environment Variables.

    The Staging System Variable Definitions panel appears. The panel ID is SBLSETVP.

  4. Enter the following information and then press Enter:
    • WLM Name. Enter the DB2 WLM name, for example, DB28WLM.
    • WLM Load Library. Enter the DB2 WLM load library name.
    • Extract DB2 Libraries: Enter the DB2 load / runlib library names for the target subsystem. (These are the libraries where the DSN, DSNTEP2, and DSNTIAUL programs are located.)
    • Staging DB2 Libraries. Enter the DB2 load / runlib library names for the staging subsystem.

      NOTE:  The libraries you enter must exist (that is, they must be cataloged).

  5. Press Enter.

    Messages appear indicating that the DSNHLQ and DB2 load library information was written to individual PDS members in the DSNHLQ.SIEBEL.JCLLIB library.

  6. Press PF3 to return to the Staging Database Environment Setup menu.
  7. Select option 1: Receive XMIT Datasets, and press Enter.
  8. Submit the JCL in data set DSNHLQ.SIEBEL.install.jcl(SPXMITR).
  9. After submitting the job, enter cancel on the command line or press PF3 to save changes.

    This job receives XMIT format files. Three PDS data sets are allocated and populated with members. The three PDS data set names are:

    • DSNHLQ.SIEBEL.LOAD
    • DSNHLQ.SIEBEL.SP.SPDDL
    • DSNHLQ.SIEBEL.DBRMLIB
  10. Verify that the job ran successfully.
    1. Review the output in SDSF or another job output facility. Verify that the RC is 0 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.
    2. Review the output to verify that all three data sets (and members) were received properly. You will get a message for each member successfully received for each of the three data sets.

      From this point on, all jobs contain one of the following JCL INCLUDE members to check job step return codes. If condition codes are not met, then the job ends abnormally, with a return code of User 99. Acceptable return codes for each step of each job is controlled by the following three JCL test condition checks:

    • JCLTEST requires that the return code is less than or equal to 4
    • JCLTEST0 requires that the return code is 0
    • JCLTEST8 requires that the return code is less than or equal to 8

      NOTE:  You must fix any failed jobs before proceeding with the upgrade. For information on restarting failed jobs, see Restarting Upgrade Jobs That Fail.

  11. Press PF3 to return to the Staging Database Environment Setup menu.
  12. Select option 2: Create JCL Libraries, and press Enter. This option builds and allocates the install JCL libraries.

    You are placed in edit mode for data set DSNHLQ.SIEBEL.VSTG00nn (nn varies according to your upgrade path).

    NOTE:  If you want to change the job card, do so at this time.

  13. Run the job using the JCL in data set DSNHLQ.SIEBEL.VSTG00nn. The install JCL libraries are built and allocated and path-specific panels are added to the DSNHLQ.SIEBEL.EXEC library.
  14. Verify that the job ran successfully.
    1. Review the output in SDSF or another job output facility. Verify that the return code is 0 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, then you can verify the condition codes by searching for the condition code IEF206I.
    2. Verify that this job allocated and populated data set DSNHLQ.SIEBEL.INSTALL.JCL. This job also adds path-specific panels to the DSNHLQ.SIEBEL.EXEC library.
  15. After submitting the job, enter cancel on the command line or press PF3 to save changes.
  16. On the Staging Database Environment Setup menu, select option 3: Create Siebel Logging Table (1). This option allows you to create and load the logging table for the staging jobs and to create the staging TMP_ADDR table.

    You are placed in edit mode for data set DSNHLQ.SIEBEL.INSTALL.JCL(LOADLOG1).

    NOTE:  If you want to change the job card, do so at this time.

  17. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(LOADLOG1).

    This job runs the DDL to create the TMP_SBLLOG_STG table in the staging environment and loads an initial set of log entries for logging batch job execution.

  18. Verify that the job ran successfully:
    1. Review the output in SDSF or another job output facility. Verify that the return code is 0 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, then you can verify the condition codes by searching for the condition code IEF206I.
    2. Verify that this job created the TMP_SBLLOG_STG table on the staging database and loaded an initial set of log entries for logging batch job execution.
  19. After submitting the job, enter cancel on the command line or press PF3 to save changes.
  20. On the Staging Database Environment Setup menu, select option 4: Create Staging Database (DDL), and press Enter to execute the DDL necessary to create the staging database.

    You are in edit mode for data set DSNHLQ.SIEBEL.INSTALL.JCL(STGDDL).

    NOTE:  If you want to change the job card, do so at this time.

  21. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(STGDDL).
  22. Verify that the job ran successfully. Review the output in SDSF or another job output facility. Verify that the return code is 0 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

    This job executes the staging database DDL to create an exact schema version of the target database (database to be upgraded) in a staging environment using the Host/LPAR, DB2 subsystem and tableowner values you specified when you ran the Database Configuration Wizard.

    Only the schema exists; it does not have to be populated with data. All objects must contain the DDL syntax DEFINE NO. Index definitions include the DEFER YES syntax.

  23. Press PF3 to return to the Environment Setup menu.
  24. Select option 5: Assign Jobname Prefix/Parms, and press Enter to assign unique jobname prefixes to JCL upgrade jobs by job type.

    The Staging Jobname Prefix/Parm Definitions Jobcard parameters panel is displayed. The panel ID is SBLJPXP.

  25. You must enter a three-character job name prefix for all upgrade job types for items 1 through 20.

    It is recommended that the three-character prefix is unique to make it easier to find your jobs in the queue, but it is only required for the nonunique index and obsolete index job prefixes (which cannot be the same). The remaining five characters of the job name (which do not appear and cannot be modified) are defined by Oracle and are unique for all upgrade jobs.

  26. You can change the NOTIFY value from &SYSUID to your TSO ID or leave it as &SYSUID.

    NOTE:  If you want to remove the notify parameter from the job card, replace the symbolic parameter &sysuid with spaces.

  27. Review the job card parameters and make any necessary changes. Verify that you are using the correct accounting, job class, and message class.
  28. Press Enter after entering the job name prefix and parameter definitions. The JCL template files are updated. Messages indicate when each step is completed.
    
Siebel Database Upgrade Guide for DB2 for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.