Problem Determination Guide: Introduction

# Problem Determination Guide

# Introduction

The information in this book is designed to help you determine the nature of any problems you encounter and to provide assistance to resolve them. It is recommended that you become familiar with the resources available to you. A familiarity with the methods of implementation for the various tools and diagnostic schemes enhances your effectiveness.

## Creating a Log File

Sample utilities are provided for displaying warning, assertion, and PRINT messages (refer to the sample utilities listed in the OpenDoc Programming Reference ). All of these messages can be routed to an OpenDoc log file by using the following coding:

    SetOutputMode(kWriteToFile);         // Turns on logging to file
    SetOutputMode(kWriteToDebugWindow);  // Turns off logging to file

opendoc.log file in the current directory.

## Real Time Logging

On WIndows NT/95, messages are sent to the MSGDISP utility. You can start MSGDISP before running OpenDoc.

On AIX, messages are routed to the system console.

On OS/2, messages are sent to the PMPRINTF utility. You can start PMPRINTF.EXE before running OpenDoc.

## Suppressing Pop-Up Message Boxes

The Opendoc warning and assertion message boxes can be suppressed by setting the following system environment variable:

         SET OpenDocDisplayBoxes=no

The default setting is:

         SET OpenDocDisplayBoxes=yes

## Defining Your Own Messages

You can define your own warning and assert messages using the provided utility macros (refer to the utility macros listed in the OpenDoc Programming Guide ). You can either supply your own message catalog with index values or use an index of -1 to display a message without using a catalog.

[ Top | Previous | Next | Contents | Index | Documentation Homepage ]