IBM WorkSpace On-Demand 2.0 on Warp Server for e-business

©. Copyright IBM Corp. 1999

IBM Universal Database OS/2 Client Application Enabler V5.0

These instructions identify how to establish the DB2 CAE program to run on WorkSpace On-Demand clients.

SETUP STEPS

Use these steps to setup DB2 CAE:

  1. Install the DB2 Client Application Enabler
  2. Create a Client with DB2 Enabled
  3. Update the Default FIT File on the Server
  4. Modify Access Feature
  5. Create a DB2 Folder on the Client Desktop

  1. Install the DB2 Client Application Enabler  [DB2 Steps]

    Install DB2 CAE on an OS/2 client. After the installation of DB2 CAE completes on the client, XCOPY the DB2 CAE files into the RPL tree on the WorkSpace On-Demand Server as shown below.

    Use the following commands to install the DB2 CAE files on the server.C: represents the drive where the DB2 CAE files reside.

    NET USE X: \\WSODSRVR\D$ XCOPY C:\SQLLIB\*.* X:\IBMLAN\RPL\SQLLIB /S /E /V COPY C:\SQLLIB\DB2CLI.INI X:\IBLMAN\RPLUSER\BB20.US\SQLLIB COPY C:\SQLLIB\DB2\DB2IDIR X:\IBMLAN\RPLUSER\BB20.US\SQLLIB\DB2\DB2IDIR

  2. Create a Client with DB2 Enabled  [DB2 Steps]

    To enable DB2 on a client:

    1. Create a WorkSpace On-Demand 2.0 client
      Use the GUI to create a WorkSpace On-Demand 2.0 client. You can also create clients with "NETRPLMACH" at a command line.
    2. Update the client's CONFIG.SYS

    When you create a client, the process creates client specific FIT files and client specific directories on the server in the \IBMLAN\RPLUSER\machine subdirectory. Machine represents the name of the client.

    DB2 CAE requires FFST support. Verify that the following entries are present in the client \IBMLAN\RPL\MACHINES\machine_name\CONFIG.SYS file. Where machine_name represents the name of the client.

    DEVICE=Z:\OS2\LOG.SYS RUN=Z:\OS2\SYSTEM\LOGDAEM.EXE RUN=Z:\OS2\EPW.EXE THREADS=1024 LIBPATH=Z:\SQLLIB\DLL;Z:\SQLLIB\ALT; SET PATH=Z:\SQLLIB\BIN;Z:\SQLLIB\ALT; SET DPATH=Z:\SQLLIB\BIN:Z:\SQLLIB; SET HELP=Z:\SQLLIB\HELP; SET BOOKSHELF=Z:\SQLLIB\BOOK; SET CLASSPATH=Z:\SQLLIB\JAVA\DB2JAVA.ZIP;Z:\SQLLIB\JAVA\RUNTIME.ZIP SET DB2CHKPTR=ON SET DB2INSTANCE=DB2 SET DB2PATH=Z:\SQLLIB

    Note: Pre-existing values (such as LIBPATH, PATH, DPATH, and HELP) may be present. If these values exist, append the additional path to the END of the pre-existing statement. For other entries (such as THREADS=), modify the setting according to these conditions. If the value is less than the value suggested here, increase it. However, do not decrease if it is higher.

  3. Update the Default FIT File on the Server  [DB2 Steps]

    Add the following entries to the default FIT file, IBMLAN\RPL\FITS\DFBB20US.FIT. These entries map DB2 CAE log&trace, INI, and data output files to specific directories on the WorkSpace On-Demand Server.

    ; ********************************************************** ; * DB2 CAE - read/write files ; ********************************************************** ; Following required to access the DB2 CAE binaries Z:\SQLLIB SQLLIB ; Following required to update DB2 CAE client specific files Z:\SQLLIB\*.log \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\SQLLIB Z:\SQLLIB\*.ini \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\SQLLIB Z:\SQLLIB\*.!!! \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\SQLLIB Z:\SQLLIB\BIN\*.log \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\SQLLIB\BIN Z:\SQLLIB\BIN\*.ini \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\SQLLIB\BIN Z:\SQLLIB\BIN\*.!!! \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\SQLLIB\BIN Z:\SQLLIB\DB2 \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\SQLLIB\DB2 Z:\OS2\INSTALL\ZIP.ERR \\<RPLBOOTSERVER>\WRKFILES\DEFAULT\CMLIB

    Note: The IBM WorkSpace On-Demand workstation name replaces DEFAULT automatically.

    RPLBOOTSERVER represents your server name.

  4. Modify Access Feature Access Control Profile Settings  [DB2 Steps]

    After you create a WorkSpace On-Demand 2.0 client, update the EPW.INI and the VPD.INI files to reflect the correct paths, as defined in the DB2 application. Use an INI file maintenance tool to make these changes or a REXX program (or a similar program) that calls system APIs.

    Update the following INI file settings.

    INI file Updates
    EPW.INI Application: CFG Key: ADP From data: C:\OS2\SYSTEM\EPW To data: Z:\OS2\SYSTEM\EPW Application: CFG Key: MLN From data: C:\OS2\SYSTEM\EPW\OS2MLOG.DAT To data: Z:\OS2\SYSTEM\EPW\OS2MLOG.DAT Application: CFG Key: SDP From data: C:\OS2\SYSTEM\EPW To data: Z:\OS2\SYSTEM\EPW
    VPD.INI Application: HVPD Key: TID From data: legacy_workstation_name To data: wsod_workstation_name

    NOTES:
    Update INI files cautiously. If the modification of INI files is done incorrectly, the execution of the application might run incorrectly.

    The VPD.INI file must be edited for every workstation that will run eNetwork Communications Server for OS Access Feature or DB2.

  5. Create DB2 Folder on the Client Desktop  [DB2 Steps]

    To create the DB2 folder on the client desktop:

    1. Verify that Remote Boot services are started on the bootserver.

      To start the services, at a command prompt, type:
      net start RPL

    2. Start and Log on the client you created in Step 2.
    3. RPL the workstation and logon.
    4. Click the OS/2 command icon.
    5. Change to the \SQLLIB\MISC directory.
    6. Create the DB2 folder:
      CD \SQLLIB\MISC
      DB2ICO