Bookshelf Home | Contents | Index | PDF     

Implementing Siebel Business Applications on DB2 for z/OS > Installing the Siebel Database on the DB2 Host > Completing the Siebel Schema Installation Using Generated DDL >

Applying Installation DDL on the DB2 Host

When you install the Siebel Schema, if you select the Generate DDL Into Files option, the schema.sql and the ddlview.sql files are generated in the DDL output directory that you specified during the installation. Before continuing with the installation, you must transfer the DDL files to the DB2 host and then apply them. Both procedures are described in this topic (the instructions in this topic apply to both Windows and UNIX operating systems).

NOTE:  Ensure that the tool you use (SPUFI or DSNTEP2) to apply the DDL on the DB2 host uses a slash as the SQL delimiter. For further information, see Setting Up the SQL Delimiter on DB2.

Transferring the DDL Files to the DB2 Host

The following procedure describes how to transfer the DDL files to the host.

To transfer the DDL files to the DB2 host

  1. Navigate to the output directory (Windows: DBSRVR_ROOT\db2390\dboutput\install; UNIX: DBSRVR_ROOT/db2390/dboutput/install) and open the instftp.txt file.
  2. Edit the instftp.txt file using the following information:
    1. Change &IP into the IP address or domain name of your DB2 host, for example ZM01.
    2. Change &Username to your user name on the z/OS host, for example SADMIN.
    3. Change all occurrences of SIEBELQ1 to your own high-level qualifier (HLQ), for example, SADMIN. Save the file. The following is an example of the instftp.txt file.

    open &IP
    user &Username

    quote site cylinders primary=1 secondary=1
    quote site recfm=fb lrecl=80 blksize=0

    send &directoryPath1/jobinstl.txt 'SIEBELQ1.SIEBEL.INST.JOBINSTL'
    send &directoryPath1/ddlview.sql 'SIEBELQ1.SIEBEL.INST.DDLVIEW'

    quote site cylinders primary=10 secondary=25
    send &directoryPath1/schema.sql 'SIEBELQ1.SIEBEL.INST.SCHEMA'

    Quit

    NOTE:  The &directoryPath1 variable is substituted with the appropriate UNIX or Windows path.

  3. Save the changes you have made to instftp.txt.
  4. Double-click instftp.bat from Windows or issue the following command from UNIX:

    ftp -vn <instftp.txt> instftp.log

  5. Enter the password associated with the user name you entered in the instftp.txt file in Step 2.

    Press any key to continue.

  6. The files are sent to the DB2 host and the log file instftp.log is created in your DBSRVR_ROOT\db2390\dboutput\install directory (Windows) or your DBSRVR_ROOT/db2390/dboutput/install (UNIX) directory.

    The log contains information on the file transfer, for example:

    Connected to ZM01.siebel.com.

    220-FTPD1 IBM FTP CS V1R4 at LOOPBACK, 22:44:26 on 2011-02-27.
    220 Connection will close if idle for more than 5 minutes.
    331 Send password please.
    230 SADMIN is logged on. Working directory is SADMIN.
    200 SITE command was accepted
    200 SITE command was accepted
    200 Port request OK.
    125 Storing data set SADMIN.SIEBEL.INST.JOBINSTL
    250 Transfer completed successfully.
    ftp: 45038 bytes sent in 0.00Seconds 45038000.00Kbytes/sec.

    200 Port request OK.
    125 Storing data set SADMIN.SIEBEL.INST.DDLVIEW
    250 Transfer completed successfully.
    ftp: 1850 bytes sent in 0.00Seconds 1850000.00Kbytes/sec.

    200 SITE command was accepted
    200 Port request OK.
    125 Storing data set SADMIN.SIEBEL.INST.SCHEMA
    250 Transfer completed successfully.
    ftp: 8369624 bytes sent in 2.42Seconds 3452.82Kbytes/sec.

    221 Quit command received. Goodbye.

You can now apply the DDL on the DB2 host.

Applying the DDL Files on the DB2 Host

The following procedure describes how to apply the DDL files on the host.

To apply the DDL files on the DB2 host

  1. When the DDL file transfer is successfully completed, log on to the mainframe and navigate to the Data Set List Utility (DSLIST) panel.

    The DSLIST panel reflects the data sets associated with the user ID you entered previously when logging on.

  2. Edit the HLQ.SIEBEL.INST.JOBINSTL data set, for example, SIEBLQ1.SIEBEL.INST.JOBINSTL, by entering e to the left of the data set name and pressing Enter twice.

    The Edit Entry Panel appears.

  3. As instructed in the comments section, change all occurrences of SIEBELQ1 to your HLQ using the following command:

    c SIEBELQ1 HLQ ALL

    NOTE:  Make sure that your entry is in capital letters.

  4. Press Enter, and the changes are made.
  5. Enter submit on the Command line, and press Enter to submit the job.
  6. Details of the job are displayed. Press Enter again and a new data set named HLQ.SIEBEL.INST.EXEC is created.
  7. Press F3 to return to the DSLIST screen.
  8. On the DSLIST screen, edit the HLQ.SIEBEL.INST.EXEC data set by entering e to the left of the data set name and pressing Enter.
  9. Enter exec to the left of the SBLINST member and press Enter to start the installation.
  10. On the Siebel Install Main Menu screen, you can select one of the following options:
    • 1. Generate Siebel DDL - Generate JCL and DDL
    • 2. Generate View DDL - Generate VIEW DDL

      Enter 1 on the Command line to create the JCL and DDL used to generate the schema.

  11. Enter the DDL input data set name, for example, HLQ.SIEBEL.INST.SCHEMA, and then press Enter.
  12. Press Enter again and an SQL data set named HLQ.SIEBEL.INST.SCHEMA.SCH is created.
  13. Press F3 to exit after the job completes.
  14. On the DSLIST screen, enter e to the left of the HLQ.SIEBEL.INST.SCHEMA.SCH data set, and press Enter.

    NOTE:  If you use a tool other than the DSNTEP2 tool to create objects, specify the program and plan names of the tool you are using in the SIEBSQLA member, for example:

    DSN SYSTEM(Q109)
    RUN PROGRAM(MYTEP2) PLAN(MYTEP2) PARMS(' /SQLTERM(/) ')
    END

  15. In the HLQ.SIEBEL.INST.SCHEMA.SCH data set, edit the following JCL members in the order shown. Run the GRJCL member last because it grants permissions to the objects (database, table spaces and tables) created when you run the other three members.
    • DBJCL
    • TSJCL
    • TBJCL
    • GRJCL

      To edit and run each JCL member, do the following:

    1. Enter e to the left of the JCL member, and press Enter.
    2. Edit the job card parameters in each member, for example, specify the appropriate CLASS and MSGCLASS names:

    // D2PUNL0 JOB ACCNT#,CLASS=S,MSGCLASS=X,MSGLEVEL=(1,1),
    // TIME=1440,REGION=0M,NOTIFY=&SYSUID,LINES=9999
    //*TYPRUN=SCAN

    1. Enter an asterisk (*) to the left of the TYPRUN parameter to comment out this command.
    2. Enter submit on the Command line and press Enter to submit the job.

      After each job is completed, verify that the return code is 0 (zero) to make sure that no errors occurred and that the job ran successfully.

      The Siebel DDL is now generated.

  16. To generate the View DDL file, follow the instruction to edit the HLQ.SIEBEL.INST.EXEC data set described in Step 8.
  17. Select 2 on the Install Main Menu screen to generate the View DDL.
  18. Enter the DDL file name, for example, HLQ.SIEBEL.INST.DDLVIEW, to specify the DDL input data set, then press Enter.
  19. Press Enter to generate a DDLVIEW SQL data set named HLQ.SIEBEL.INST.DDLVIEW.VIE.
  20. Press F3 to exit after the job completes.
  21. On the DSLIST screen, enter e to the left of the HLQ.SIEBEL.INST.DDLVIEW.VIE data set, and press Enter.

    NOTE:  If you use a tool to create objects other than the DSNTEP2 tool, specify the program and plan names of the tool you are using in the SIEBSQLA member, for example:

    DSN SYSTEM(Q109)
    RUN PROGRAM(    MYTEP2) PLAN(MYTEP2) PARMS(' /SQLTERM(/) ')
    END

  22. In the HLQ.SIEBEL.INST.DDLVIEW.VIE data set, edit the VIEJCL member:
    1. Enter e to the left of the VIEJCL member, and press Enter.
    2. Edit job card parameters in each member, for example, specify the appropriate CLASS and MSGCLASS names:

    // D2PUNL0 JOB ACCNT#,CLASS=S,MSGCLASS=X,MSGLEVEL=(1,1),
    // TIME=1440,REGION=0M,NOTIFY=&SYSUID,LINES=9999
    //* TYPRUN=SCAN

    1. Enter an asterisk (*) to the left of the TYPRUN parameter to comment out this statement.
    2. Enter an asterisk (*) to the left of the GRANT statements; GRANT statements on views are not required with DB2 for z/OS. If you do not comment out these statements, error messages are returned when you run the VIEJCL member; you can ignore these messages.
    3. Enter submit on the Command line and press Enter to submit the job. Press Enter again.

      After each job is completed, verify that the return code is 0 (zero), to make sure that no errors occurred and that the job ran successfully.

  23. Return to the midtier to continue the Siebel Schema installation by verifying the schema that you have just created.

    The schema.sql file is overwritten during the schema validation process. Therefore, if you would like to save the schema.sql file with the complete Siebel Schema DDL that was generated for the Siebel Schema, rename schema.sql (located in the DBSRVR_ROOT\db2390\dboutput\install directory on Windows or DBSRVR_ROOT/db2390/dboutput/install directory on UNIX) after you apply schema.sql on the mainframe.

    
Implementing Siebel Business Applications on DB2 for z/OS Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.