Browse Prior Art Database

Automatic Clearing or Program Start Up by an X25 Call

IP.com Disclosure Number: IPCOM000108999D
Original Publication Date: 1992-Jul-01
Included in the Prior Art Database: 2005-Mar-23
Document File: 3 page(s) / 109K

Publishing Venue

IBM

Related People

Price, S: AUTHOR [+3]

Abstract

Disclosed are two methods of accommodating incoming X25 calls for which an application program is neither currently active nor resident. Both methods propose changes to the incoming call routing table entries and relate to OS/2* Extended Edition. The first is to allow a relevant valid application program to start up and respond to the call. The second method is so that unwanted calls can be rejected immediately without waiting for the time-out period to expire. Automatic Program Start Up by X25 Calls

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

Automatic Clearing or Program Start Up by an X25 Call

       Disclosed are two methods of accommodating incoming X25
calls for which an application program is neither currently active
nor resident.  Both methods propose changes to the incoming call
routing table entries and relate to OS/2* Extended Edition.  The
first is to allow a relevant valid application program to start up
and respond to the call.  The second method is so that unwanted calls
can be rejected immediately without waiting for the time-out period
to expire.
Automatic Program Start Up by X25 Calls

      When an incoming X25 call arrives at an OS/2 Extended Edition
(EE) workstation, there has to be a program active to accept or to
reject the call before the X25 network clears (rejects) the call
itself after a time delay.

      This method solves the problem of what to do when there is no
such program active, by enabling the Communications Manager component
of OS/2 EE to start a program automatically when an X25 call is
received at the workstation.  Different programs can be started to
process different calls under the control of a user-configurable
table.  Each program started can receive a parameter (argument),
under the control of the same table.  The program started does not
have to be an X25 program or even a communications program; nor does
the program necessarily have to process the particular call that
caused it to be started.

      To implement this method, new fields are added to the incoming
call routing table entries.  (The incoming call routing table is part
of the OS/2 EE X25 feature.)  The contents of the fields are
configured by the user when creating or changing the routing table.
The fields are:
*    pgmname
     This is the path name of an EXE file containing the program to
be started.  When a call is received that matches the routing table
entry, and there is no application program already listening on this
entry, and the pgmname field is not null, the Comms Mgr uses the OS/2
verb DosStartSession to start the program identified by this field.
*    pgminputs
     This parameter is passed to the started program, as an argument
string.

      Other fields are used to allow the user to specify the
following data for the DosStartSession verb (see the OS/2 Programming
Reference documentation for details).  Each would have an appropriate
default.  The fields are:
*    Foreground or background session (fgbg)
*    Program title (pgmtitle)
*    Session type (sessiontype)
*    Icon file (iconfile)
*    Initial state for wi...