Browse Prior Art Database

Process to Use a Unix Message Facility File under OS/2

IP.com Disclosure Number: IPCOM000111648D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 54K

Publishing Venue

IBM

Related People

Redpath, RJ: AUTHOR

Abstract

This process details a new approach to supporting Messages under the Unix* and OS/2** systems simultaneously for National Language Support.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 57% of the total text.

Process to Use a Unix Message Facility File under OS/2

      This process details a new approach to supporting Messages
under the Unix* and OS/2** systems simultaneously for National
Language Support.

      OS/2 and Unix provide a Message Facility which is unique to
themselves.  Therefore, to support both systems inherently requires
more cost.  If one system could accept the other system's message
format without additional facilities written, the cost and
maintenance would be reduced.  An example Unix Message File is shown
below.

$quote "

$set FHX

FHX0100   "Close application?"

FHX0101  "This is the IBM ADCP demonstration\n\

application for Software Library Management"

$set FHB

FHB0100  "This is a new message"

FHB0200  "this is more information"

FHB0300   "finally more infor"

      The  message  file  is  called fhx.msg for reference.  The Unix
Message Facility uses the runcat command to create  an  include  file
for  applications  that  wish to use the catalog file fhx.cat created
from fhx.msg.  The name of the include file is usually the  name  and
extension  of  the  Message  File  with  a hyphen; in this case it is
fhx_msg.h created from fhx.msg.  In summary, using the  Unix  Message
Facility results in three files: the original Message File created by
the  programmer  fhx.msg,  the  include  file  created  by the runcat
command fhx_msg.h, and the catalog file created by the runcat command
fhx.cat.

      The sol...