Browse Prior Art Database

Simulating Inter-process Messages in an IBM Automated Logistics and Production Solution System

IP.com Disclosure Number: IPCOM000108293D
Original Publication Date: 1992-May-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 63K

Publishing Venue

IBM

Related People

Hearin, L: AUTHOR [+4]

Abstract

Disclosed is an OS/2* application called the Message Simulator, which simulates messages for an Automated Logistics and Production Solution (ALPS) system.

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

Simulating Inter-process Messages in an IBM Automated Logistics and Production Solution System

       Disclosed is an OS/2* application called the Message
Simulator, which simulates messages for an Automated Logistics and
Production Solution (ALPS) system.

      In an ALPS system, processes communicate with each other via
inter-process messages. The Message Simulator process allows the user
to create inter-process messages through a set of prompts defined in
a configuration file and to send these messages to another process in
the system. Under normal operating conditions this process would not
be used.  However, when installing and testing a system, this process
becomes a useful system utility.

      The Message Simulator reads an ASCII file created by the user
which describes the messages that are being used in the ALPS system.
The following is an example:
      ==========top of file============================
      1075 = "Enter parm 1 ,%d,2,n,17"
      1075 = "Enter parm 2 ,%d,2,y"
      1075 = "Enter parm 3 ,%d,2,n,1"
      310  = "  parm 1 ,%u,2,y"
      310  = "  parm 2 ,%s,10,y,RT34567"
      ==========bottom of file=========================

      In this example 1075 and 310 are message datacode/function
codes.  A datacode is simply used as a message identifier. In this
example, message 1075 is made up of three integers, parm 1, parm 2
and parm 3.  Each line describes how the parameter is to be
interpre...