STREAMS-UX Programmer's Guide (February 2007)
5
About This Document
This document describes how to use STREAMS, a generalized, flexible communication framework and set of
tools that facilitate the development of communication services for UNIX.
The document printing date and part number indicate the document’s current edition. The printing date will
change when a new edition is printed. Minor changes may be made at reprint without changing the printing
date. The document part number will change when extensive changes are made.
Document updates may be issued between editions to correct errors or document product changes. To ensure
that you receive the updated or new editions, you should subscribe to the appropriate product support service.
See your HP sales representative for details.
The manual is organized as follows:
Chapter 1, “Overview.”
This chapter shows an overview of the STREAMS components, system calls, messages and
queues and STREAMS multiplexor.
Chapter 2, “STREAMS Mechanism and System Calls.”
This chapter describes system calls most commonly seen in user applications that interact
with STREAMS devices.
Chapter 3, “Messages.”
This chapter discusses STREAMS messages, their structure, linkage, queuing and
interfacing into other STREAMS components.
Chapter 4, “Modules and Drivers.”
Describes various data structures essential to modules and drivers and provides design
guidelines for developing them.
Chapter 5, “Multiplexing.”
Shows how the STREAMS IOCTL commands enable the user process to perform a variety of
control functions on a stream.
Appendix A, “STREAMS IOCTL Commands.”
Shows how the STREAMS IOCTL commands enable the user process to perform a variety of
control functions on a stream.
Appendix B, “STREAMS Utilities Supported by HP-UX.”
Deals with the STREAMS utilities supported by HP-UX which are used to perform specific
operations/functions in module and driver development.
Appendix C, “Message Types.”
Describes the fixed set of message types recognized by STREAMS/UX.
Appendix D, “STREAMS Administrative Driver.”
Describes the STREAMS Administrative Driver. The STREAMS Administrative Driver,
also known as SAD, is an interface to the autopush facility. SAD enables administrative
tasks to be performed on STREAMS modules and drivers.
Appendix E, “Differences Between STREAMS/UX and System V Release 4 STREAMS.”