ObjectStore C++ Release Notes

Chapter 3

Platform-Specific Considerations

This chapter describes platform-related considerations you should anticipate when using ObjectStore Release 5.1.

Note that some of the books contain platform-specific information about platforms for which ObjectStore Release 5.1 is not yet available. Such information refers to behavior using the previous version of ObjectStore. These Release Notes and the other documents in the documentation set will be updated as ObjectStore Release 5.1 becomes available on additional platforms.

The topics are organized in the following manner:

Windows

The following paragraphs describe platform-specific considerations for ObjectStore Release 5.1 on Windows NT.

Installing DEBUG.ZIP or DDEBUG.ZIP

To install DEBUG.ZIP or DDEBUG.ZIP follow the steps described here.

Install ObjectStore Release 5 with the SETUP program. See ObjectStore Installation for Windows NT documentation for instructions.
Shut down the ObjectStore Server and Cache Manager by using the ObjectStore SETUP program. Answer Yes to the question about shutting down servers, then exit from SETUP.
Go to the %OS_ROOTDIR% directory.
Rename bin and binsngl directories (from the command prompt window or Windows Explorer) to retail.bin and retail.binsngl.
Unzip the file (DEBUG.ZIP or DDEBUG.ZIP) from the command prompt by typing the following command.The -d option creates and restores the directories included in the zip file.
```
      pkunzip -d debug.zip 
```
Run the ObjectStore SETUP program to start the Server. In the first setup dialog select the Setup Server option. In the menu Choosing to start ObjectStore services automatically, select Yes. Then a Confirm Message dialog asks if you want to start the services right now. Select Yes.

Now you can debug your application. For more information about required compilation options, see the Windows DEBUG and DDEBUG Builds of ObjectStore in the Windows section of Chapter 4, Compiling, Linking, and Debugging Programs in ObjectStore Building C++ Interface Applications.

Solaris 2

The following paragraphs describe platform-specific considerations for ObjectStore Release 5.1 on Solaris 2.

HP

HP aC++ source file naming clarification

A clarification has been added to the Chapter 4, Compiling, Linking, and Debugging Programs of ObjectStore Building C++ Interface Applications. See HP aC++ Source Files for details.

16K Page Size and Heterogeneous Database Access

In releases prior to ObjectStore Release 5.1, there is a bug in our support of heterogeneous access to databases created on machines with a 16K page size, such as SGI platforms: databases created on 16K page big-endian platforms cannot be accessed from small-endian platforms. Although this has been fixed in Release 5.1, older databases created on 16K page size platforms must be upgraded to be accessible to small-endian platforms.

In Release 5.1 we provide a tool that can be used to check whether a database has such limitations. The tool can also be used to upgrade a database if such limitations exist. It can be used from a command line option to osverifydb, or with the API os_dbutil::osverifydb().

Note

There is no need to use this tool if the database has been created on a platform that has a 4K or 8K page size.

New Option to osverfiydb

To check or upgrade a database for hetergeneous accessibility with the osverifydb command line utility, you can specify a newly added command line option, -info_sector_tag_verify_opt option. This verifies info segment sector tags in accordance with the option value you specify.

Valid options are:

0

Skips verifying info segment sector tags (default).

1

Verifies info segment sector tags and reports whether the database can be used heterogeneously.

2

Upgrades the database for heterogeneous accessibility.

5

Causes osverifydb to report information for this option only. Other verifications usually performed by osverifydb are not made.

6

Performs an upgrade only. Other verifications usually performed by osverifydb are not made.

New Argument to osdbutil::osverifydb()

You can also use the upgrade tool by means of the os_verifydb_options argument to the API os_dbutil::osverifydb() with os_verifydb_options::info_sector_tag_verify_opt set to the desired value:

class os_verifydb_options 
{ public: 
      ... 
      enum info_sector_tag_verify_opt_enum { 
            verify_skip = 0,                                          /* do not verify info sector tag */ 
            verify_report_only = 1,                                          /* report only */ 
            verify_upgrade = 2,                                          /* upgrade info sector tag */ 
            verify_skip_others = 4,                                          /* skip other verifications */ 
      } info_sector_tag_verify_opt ; 
      ... 
}

Valid os_verifydb_options::info_sector_tag_verify_opt values are:

      verify_skip 
      verify_report_only 
      verify_upgrade 
      verify_report_only | verify_skip_others 
      verify_upgrade | verify_skip_others

[previous] [next]

Copyright © 1998 Object Design, Inc. All rights reserved.

Updated: 04/02/98 12:47:39