WorkSpace On-Demand Client Install Notes

It is possible to install KTRACE on a WorkSpace On-Demand (WSOD) client.  The following changes are recommended to enable this installation.

CONFIG.SYS Changes

The CONFIG.SYS changes necessary to add KTRACE on WSOD are similar to a local install, with one caveat.  In the default WSOD environment, a device driver named PROTDISK.SYS is loaded in the client's CONFIG.SYS.  This device driver is responsible for disabling access to local disk drives for all files except SWAPPER.DAT.  This driver utilizes the same SES tracepoints which KTRACE requires.  Since only one driver can be using the SES tracepoints for any particular IPL, this driver MUST BE REMOVED from CONFIG.SYS if KTRACE is to be used.  Please see the prerequisites section for more details on this requirement.
BASEDEV=KTRACE.SYS
This line is the sole, required change to the system's configuration to enable KTRACE.  This device driver MUST be loaded as a BASEDEV, which means it is loaded at a very early point in the system's IPL.  This also means that the driver must reside in either the root directory of the boot drive (e.g., C:\) or in the \OS2\BOOT directory on the boot drive.  OS/2 cannot find BASEDEV drivers if they do not reside in one of these two directories.

On the client, this BASEDEV statement is is added after NET RIPLMACH processing completes.  In addition, the driver must be FITted to the C:\OS2\BOOT directory (see below).

Location of KTRACE Files on the Server

Here is an example of the directory structure for a KTRACE install on a WSOD Server.
e:\ibmlan\rpl\ktrace\ktrace.exe
e:\ibmlan\rpl\ktrace\ktrace.sys
e:\ibmlan\rpl\ktrace\ktrace.cfg
e:\ibmlan\rpl\ktrace\license.kto
All of the required files are installed in a KTRACE directory.  Golden Code recommends placing this directory under \IBMLAN\RPL as it should be read-only and is not dependent upon OS version.

In addition, Golden Code recommends creating a KTRACE subdirectory on the WSOD server, in order to create a writable area on the client, in which traces can be generated.  The location for this subdirectory varies, depending upon the version number and national language for your WSOD installation.  For example, the subdirectory should be created under IBMLAN\RPLUSER\BB10.US for the U.S. release of WSOD v1.0.  When the NET RIPLMACH command is issued, the WSOD requester that is generated will have a directory structure identical to that created under this template directory, copied into the writable area under RPLUSER.  Combined with the FIT file entries below, the creation of this subdirectory on the server ensures that a writable KTRACE directory will be available to the WSOD client.

File Index Table (FIT) Changes

To make these files visible to the correct locations on the WSOD client, the default File Index Table (FIT) must be modified.  For example, this is \IBMLAN\RPL\FITS\DFBB10US.FIT for the U.S. release of WSOD v1.0.  At a minimum, the KTRACE.SYS driver must appear in this FIT because this driver must be found during the machine's IPL.

Entries in this file must be kept to a minimum, as the size is limited.  However, if there is no problem with including additional entries in this file, the rest of the entries may be placed here as well.  Example entries:

; KTRACE
C:\KTRACE                   KTRACE
C:\OS2\BOOT\KTRACE.SYS      KTRACE\KTRACE.SYS
C:\KTRACE\*.KTR             \\<server_name>\WRKFILES\DEFAULT\KTRACE
This allows the KTRACE directory to be accessed (read-only) as C:\KTRACE, while the device driver is loaded as C:\OS2\BOOT\KTRACE.SYS.  In addition, it permits access to the writable KTRACE user directory on the server.

Apparent Location of KTRACE Files on the Client

The above FIT configuration, combined with the above server directory structure, will result in the KTRACE files being available to the client machine as follows:
c:\ktrace
c:\ktrace\ktrace.exe
c:\ktrace\ktrace.cfg
c:\ktrace\license.kto
c:\os2\boot\ktrace.sys

© 2001 Golden Code Development Corporation.  ALL RIGHTS RESERVED