### MSGBIND - Input File (C, OS/2)

The input file contains the following three types of lines:

- > Executable file
- < Message file
- Message numbers.

Executable file
The file in which messages are to be bound, is preceded by a greater-than symbol (>). The name of the file can be any valid OS/2 file name.

Two or more different executable files can be modified by the specifications found in one input file. MSGBIND continues to use this file until it encounters another greater-than symbol.

Message file
The message file to be read from is preceded by a less-than sign (<). You create this file by using the MKMSGF program. The name can be any valid OS/2 file name. All message numbers that follow it are located in the specified message file and are copied to the current output executable file. MSGBIND reads the message-number list until it encounters one of the following: the end of the input file, a new output specification, or a new input message file.

Message Numbers
The messages in the message file are listed below the message-file name. Only those message numbers that you specify will be added. You can also specify an asterisk (*) to indicate that all messages within the message file will be added. Message numbers must consist of a three-letter component identifier followed by a four-digit message number.

See Input Message File for a more detailed description of message numbers.

MSGBIND - Message Segment Binder
MSGBIND - Syntax
MKMSGF - Make Message File Utility
MKCATDEF - Preprocess Message Source File Utility