Implementing Siebel Business Applications on DB2 for z/OS > Migrating a Siebel Database to Unicode Format > Process of Preparing the z/OS Host Environment >

Defining Environment Variables for the Unicode Migration

After creating the z/OS data sets required to run the Unicode migration, you have to set up the z/OS system environment variables appropriately for the migration process. The following procedure describes how to perform this task.

This task is a step in Process of Preparing the z/OS Host Environment.

To set up the migration environment on the z/OS host

1. Display the Siebel Unicode Migration Option Menu panel (panel ID is UNIMIG8P) by navigating to the TSO command line processor panel, then entering the following command:

   UNIMIG82

2. To define the environment variables that will be used for the Unicode migration process, select option 1: Environment Setup and press Enter.
3. The Unicode Migration Environment Setup Menu appears. The panel ID is SBLSSETP.
4. Select option 1: Set System Environment Variables, and press Enter. The System Variable Definitions panel is displayed (panel id SBLSETVP).
5. Enter values in the following fields, or amend any of the values that are displayed, as appropriate for your environment.
   • Source DDL From: Create Target On:

     Enter information in the following fields to identify your source and target databases:

     • Host/LPAR Name. Enter the source and target MVS subsystem LPAR identifiers. For a subsystem to subsystem migration, the MVS source and target LPAR names can be the same or different, depending on where the DB2 subsystems reside. For a same subsystem migration, the MVS source and target LPAR names must be the same.
     • DB2 Subsystem. Enter the DB2 subsystem identifier (SSID) for the source and target databases. For a subsystem to subsystem migration, the source and target SSIDs must be different. For a same subsystem migration, the source and target SSIDs must be the same.
     • Table Owner. Enter the character IDs that identify the source and target Siebel Schema table owners. The source and target table owner names must be different.
   • Source DB2 Libraries: Target DB2 Libraries

     The default DB2 library names are displayed for your source and target databases. Amend these values as necessary.

6. Press PF3 and the values you entered are saved in the EXEC library.
7. On the Unicode Migration Environment Setup Menu select option 2: Unpack JOB1, and press Enter.
8. Submit the JCL in the data set DSNHLQ.SIEBEL.UNI.JOB1.
9. Verify that the job ran successfully (RC is 0) and that the following data set libraries were created:
   • DSNHLQ.UNI.INSTALL.JCL
   • DSNHLQ.UNI.JCLLIB
   • DSNHLQ.UNI.LOAD
   • DSNHLQ.UNI.PROC
10. On the Unicode Migration Environment Setup Menu select option 3: Set Jobcard Variables, and press Enter. The Jobname Prefix/Parm Definitions Jobcard Parameters panel appears; the panel ID is SBLJPXP.
11. Specify values for the following fields:
    • Accntg. Verify that you are using the correct Accounting class.
    • Notify. You can change the NOTIFY value from &SYSUID to your TSO ID or leave it as &SYSUID.

      NOTE:  You can remove the notify parameter from the job card if you choose.

    • Scheduling. Enter either 1: Siebel Scheduled mode or 2: Vendor Scheduled mode. For information about choosing a scheduler, see Siebel Database Upgrade Guide for DB2 for z/OS.
12. Enter a three-character job name prefix for the following Unicode migration job types:
    • Cross Loader
    • Rebuild Indexes
    • RunStats

      It is recommended that the three-character prefix is unique as this makes it easier to find your jobs in the queue but this is not a requirement. The remaining five characters of the job name are defined by Oracle and are unique across all Unicode migration jobs.

13. Press Enter after entering the job name prefix and parameter definitions. The JCL template files are updated. Messages indicate when each step is completed.
14. On the Unicode Migration Environment Setup Menu, select option 4: Verify target environment, and press Enter.

    A process is run to determine whether or not any objects exist in the target environment. If objects are found, you must delete them before proceeding.

    NOTE:  Running option 4: Verify target environment, might not locate all objects in a target environment. It is recommended that you perform additional checks to verify that your target environment is empty.

15. On the Unicode Migration Environment Setup Menu, select option 5: Build Log Table, and press Enter.

    This option creates and loads the temporary logging table for the Unicode migration jobs.

16. Submit the JCL in the data set DSNHLQ.SIEBEL.UNI.INSTALL.JCL(CREATLOG) to create the logging table.

    The DSNHLQ.SIEBEL.SBLLOG.LOADFILE file is also created; this file loads the initial set of jobs that were transferred to the z/OS host.

17. Verify that the job ran successfully (RC is 0). You can review the output in SDSF or another job output facility.

    The Environment Setup is now completed.

18. Press PF3 to return to the Siebel Unicode Migration Option Menu panel.

    You can now proceed to build the target schema. For information on this task, see Building the Target Schema.