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

Installing Application Types

Installing application types is an occasional task; you only need to install type information when new types are created, or when an application error condition exists. Ptype and otype files are run through the ToolTalk type compiler at installation time. tt_type_comp merges the information into the ToolTalk Types Database. The application then tells the ToolTalk service to read the type information in the database.

To install an application's ptype and otype files, follow these steps:

  1. Run tt_type_comp on your type file.
    % tt_type_comp your-file

    tt_type_comp runs your-file through cpp, compiles the type definitions, and merges the information into a ToolTalk Types table. describes location of the XDR-base format tables; describes the location of the Classing Engine-base format table.


    Note - The Classing Engine interface exists for compatibility reasons only. The default is XDR.


    Table 5-1 XDR-base Format ToolTalk Types Tables

    Database
    Uses XDR Table
    user
    ~/.tt/types.xdr
    system
    /etc/tt/types.xdr
    desktop
    /usr/dt/appconfig/tttypes/types.xdr
    network
    $OPENWINHOME/etc/tt/types.xdr

    Table 5-2 Classing Engine-base Format ToolTalk Types Tables

    Database
    Uses Classing Engine Table
    user
    ~/.cetables/cetables
    system
    /etc/cetables/cetables
    network
    $OPENWINHOME/lib/cetables/cetables

    There are four XDR databases. The $TTPATH environment variable determines which three will be used. See tt_type_comp(1) for details about the format and priority of $TTPATH entries.

    By default, tt_type_comp uses the user database. To specify another database, use the -d option. For example:

    % tt_type_comp -d user|system|[network|desktop]your_file

    Note - When you run tt_type_comp on your ptype or otype files, it first runs cpp on the file and then checks the syntax before it places the data into the ToolTalk Types Database format. If syntax errors are found, a message is displayed that indicates the line number of the cpp file. To find the line, enter: cpp -P source-file temp-file and view the temp-file to find the error on the line reported by tt_type_comp.


  2. ttsession will reread the ToolTalk Types Database automatically.

    To force ttsession to reread the ToolTalk Types Database, see the .