JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
ToolTalk User's Guide
search filter icon
search icon

Document Information

Preface

1.  Introducing the ToolTalk Service

2.  An Overview of the ToolTalk Service

3.  Message Patterns

4.  Setting Up and Maintaining the ToolTalk Processes

5.  Maintaining Application Information

Installing Application Types

Examining ToolTalk Type Information

Removing ToolTalk Type Information

Updating the ToolTalk Service

To send the ttsession process a SIGUSR2:

Process Type Errors

Using ttsnoop to Debug Messages and Patterns

Composing and Sending Messages

Composing and Registering Patterns

Displaying Message Components

Sending Pre-Created Messages

Receiving Messages

Stop Receiving Messages

6.  Maintaining Files and Objects Referenced in ToolTalk Messages

7.  Participating in ToolTalk Sessions

8.  Sending Messages

9.  Dynamic Message Patterns

10.  Static Message Patterns

11.  Receiving Messages

12.  Objects

13.  Managing Information Storage

14.  Handling Errors

A.  Migrating from the Classing Engine to the ToolTalk Types Database

B.  A Simple Demonstration of How the ToolTalk Service Works

C.  The ToolTalk Standard Message Sets

D.  Frequently Asked Questions

Glossary

Index

Process Type Errors

One or both of the following conditions exists if applications report the error:

Application is not an installed ptype.
  1. The ToolTalk service has not been instructed by the application to reread the recently updated type information in the ToolTalk Types Database. See for instructions on how to force the ToolTalk service to reread type information from the ToolTalk Types Database.

  2. The application's ptypes and otypes have not been compiled and merged into the ToolTalk Types Database. See for instructions on how to compile and merge type information.