Browse Prior Art Database

Selective Start And Stop of 3270 Sessions

IP.com Disclosure Number: IPCOM000100376D
Original Publication Date: 1990-Apr-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 1 page(s) / 45K

Publishing Venue

IBM

Related People

Meckstroth, JR: AUTHOR [+3]

Abstract

This technique enables the user of a 3270 emulator to choose the 3270 sessions desired to be started or stopped by link. This saves the user the cost of establishing unused links. Also, only the code required to support the links and protocols for the sessions requested is loaded. The emulator is ready at any given time to accept additional start or stop requests, loading or unloading code and establishing or taking down links as required.

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

Selective Start And Stop of 3270 Sessions

       This technique enables the user of a 3270 emulator to
choose the 3270 sessions desired to be started or stopped by link.
This saves the user the cost of establishing unused links. Also, only
the code required to support the links and protocols for the sessions
requested is loaded. The emulator is ready at any given time to
accept additional start or stop requests, loading or unloading code
and establishing or taking down links as required.

      A user interface menu contains two 'Start 3270 Emulation'
selections.  One selection starts 3270 sessions via connection to an
IBM 3174 or 3274 controller in Distributed Function Terminal (DFT)
mode.  The second selection establishes a Token-Ring connection on
which the 3270 sessions are started.  If no 3270 sessions are started
when the user selects one of these, the 3270 emulation code is
loaded.  The 3270 emulator establishes the required link, starts the
requested 3270 sessions, and creates a thread that waits for further
start or stop requests from the user.

      Should the user later select to start the 3270 sessions over
the other link, the 3270 emulator is notified by the clearing of a
semaphore on which the emulator thread is waiting.  This is also the
mechanism used to notify the emulator of user stop requests for
started 3270 sessions. Each link has an associated variable which
indicates to the emulator whether sessions on a particular link are
being st...