This chapter provides information for managing ObjectStore on OS/2 systems. For complete information, you should consult the first six chapters of this book along with this chapter.

The topics discussed are

• Specifying File Database Pathnames
• Setting Server Parameters
• Starting the Server
• Using OS/2 Environment Variables
• Specifying Utility Names
• Finding Files Containing ObjectStore Messages
• Creating a Rawfs
• Capturing Debug Information
• File Locking with NFS

os_database::open("d:\\carter\\myfiledb")

os_database::open("\\\\servername\\sharename\\myfiledb")

You can specify a relative pathname.

Server-remote databases

Server names

This specifies a database, employees, in the directory \usr\barbar on the host elvis.

Setting Server Parameters

OSTORE.INI

OSSETUP

Using -p

OS2.INI
OS2SYS.INI

Search order

1. File specified with the -p option to osserver
   
   
2. OSTORE.INI file created by OSSETUP
   
   
3. OS/2 user profiles (OS2.INI and OS2SYS.INI)
   
   

After you modify a Server parameter, you must shut down and restart the Server for the parameter to take effect.

Starting the Server

• Automatically when OS/2 is started. You specify this with OSSETUP, the ObjectStore setup utility. This is the usual method.
• From an icon.
• By running the OSSERVER utility.

Command-line options

After starting, the Server displays the message Server started to let you know that it is ready to accept requests from clients on the network.

Use -i and -I with caution

When you initialize the transaction log, anything in the log is lost. The Server resizes the log to the values specified by the Log Data Segment Initial Size and Log Record Segment Initial Size Server parameters. When the log is in the rawfs, this frees space for use by other files. When the log is in the native file system, this reallocates space dedicated to the transaction log. The size of the log does not change.

Initializing when you have a rawfs

The entire ObjectStore file system on this host is about to be initialized, 
thus destroying any data currently in it. Unless you have a backup of the 
ObjectStore file system, it will be impossible to recover the old contents 
once the initialization is started. Are you sure that you want to reinitialize 
the ObjectStore file system?

Initializing when you do not have a rawfs

You have asked for initialization which will create a new transaction log, 
deleting any old log that might exist, thus destroying any recovery data in 
the old log. This might leave some file databases in a broken state. Are 
you sure that you want to create a new log?

Starting Cache Manager

START /N OSCMGR4 0

Using OS/2 Environment Variables

UNIX.GID

UNIX.UID

Specifying Utility Names

HPFS names

This book refers to ObjectStore utilities by their full names.

Utility executables

%OS_ROOTDIR%\BIN\OSSERVER.EXE

If the file does not already exist, ObjectStore creates it. If the file does exist, ObjectStore appends to it.

ObjectStore uses the path assigned to one of the environment variables listed below to determine the directory in which to place these files. It searches in the following order:

Search order

1. %OS_TMPDIR%
   
   
2. %TEMP%
   
   
3. %TMP%
   
   

Deleting error files

Creating a Rawfs

Creating a rawfs

Using OSSETUP to Add File Partitions

The PartitionN Server parameter specifies the partitions in the rawfs. It creates the Server partition file if it does not exist, using the pathname given in the PartitionN statement. You add a partition to the rawfs by specifying a PartitionN statement when prompted to by the OSSETUP utility. Each PartitionN statement has the following form:

Syntax

PartitionN FILE pathname {expandable | nonexpandable}


N

Specifies a positive integer from 0 to N. PartitionN statements can appear in the Server parameter file in any order, but empty slots are not allowed. For example, if you have four partitions, they must be numbered 0 through 3. Required.


FILE

Specifies that the partition is a file partition. Required.


pathname

Specifies the absolute pathname of the partition. It must begin with a back slash. 


expandable | nonexpandable

Indicates whether or not the size of the partition can increase. Required.

Example

Partition0 FILE c:\mypart0 expandable
Partition1 FILE d:\mypart1 expandable
Partition2 FILE e:\bigpart99 expandable

• If one file is used, it expands dynamically as needed, as long as there is room in the partition containing the file.
• If multiple files are used for the rawfs, they can expand dynamically, if you specify expandable in the PartitionN statement.

Example

Partition0: FILE c:\usr1\one expandable
Partition1: FILE d:\usr2\two expandable
Partition2: FILE e:\usr3\three nonexpandable

1. On all machines, create the c:\temp directory if it is not already there.
   
   
2. Set the OS_TMPDIR environment variable to c:\temp by adding the following line to the config.sys file:
   
   

         SET OS_TMPDIR=c:\temp 
   

3. Reboot all machines.
   
   ObjectStore looks for OS_TMPDIR, then TEMP, and finally TMP. If none of these are defined, ObjectStore writes to the boot drive.

4. On the Server machine, open a window and stop the Server:
   
   

         ossvrsht -f hostname 
   

5. Set the OS_DEBUG_NETWORK environment variable to 1.
   
   
6. Start the Server with the following command:
   
   

         osserver -F -v -d 10 
   

   You do not need to redirect the output. ObjectStore places the output in the oss.out and osserver.txt files in the c:\temp directory, using the OS_TMPDIR environment variable.

   The osserver options have the following meanings:

   -F	Runs the Server in the foreground.
   -v	Runs the Server in verbose mode. This outputs a lot of information about what the Server is doing.
   -d	Indicates that the following number is a debug level.
   10	Specifies the debug level. The debug levels that you typically use are 1, 3, 5, or 10, depending on the level of detail required for the trace.

7. On each client,
   
   
   1. Open a window and shut down the Cache Manager with the oscmshtd utility.
   2. Set the OS_DEBUG_NETWORK environment variable to 1.
   3. Start the Cache Manager with the command

                  oscmgr4 0 50 0 1 1
      

      You do not need to redirect the output. ObjectStore uses OS_TMPDIR to send the output to the osc4.out file. The oscmgr4 options have the following meanings:

      0	Indicates that the Cache Manager was not automatically loaded with a previous connection to the first client.
      50	Specifies the Cache Manager debug level.
      0	Required queue length.
      1	Turns on debug messages for individual Cache Manager threads.
      1	Sends debug output to the osc4.out file.

      Before activating any client, open a window and set the environment OS_DEBUG_NETWORK variable to 1 in that window.

8. From that window, run the client to produce the error, redirecting the network debug information to a file in order to capture it.
   
   
9. Send the following output to Object Design:
   
   
   • For the Server, located in the c:\temp directory, the files oss.out, osc4.out, and osserver.txt
   • For each client, located in its c:\temp directory, the file osc4.out
   • For each client, the redirected network debug output

host:drive:\path 

For example, a client can access a database by means of NFS. The client NFS mounts the drive from the ObjectStore Server so that it appears as a local drive on the client. Now the client can reference the database as, for example,

g:\my\path\to\database

There is another scenario that is not safe. In this case, the database is not physically resident on the ObjectStore Server. By default, ObjectStore does not allow this. You can, however, set up a locator file to allow it. See Chapter 5, Using Locator Files to Set Up Server-Remote Databases. In this unsafe scenario, the database is physically resident on a third machine, the NFS server, which might be the client machine. The ObjectStore Server needs to lock the database by means of NFS. On OS/2, this is not possible. You cannot lock across NFS volumes, which makes it difficult to guarantee the integrity of the database.

Updated: 03/26/98 20:46:44