Wouldn't this flow better if you started with program "S" which asked the user what they wanted to do, then call "M" to do that work and return to "S" which sends the user the status message? "M" would never need to access the display file, only "S" would need to do that. "M" could be reused from other places and as a batch job since it never needs to interact with the user
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Friday, April 04, 2008 1:46 PM
To: midrange-l@xxxxxxxxxxxx
Subject: 5250 data stream issue
Consider the following situation:
We have program "M" calling program "S," which puts up a display file
page requesting parameters for a multi-record operation.
Program "S" collects the parameters, puts up a "display-only" version of
the page, and returns to "M," leaving that page up on the terminal screen.
Program "M" then runs through every record of the file, performing the
operation requested through "S," which doesn't get called again. It
doesn't put up a display page of its own until the operation completes.
(For the QuestView users out there, I've just described QuestView Search
& Replace.)
Is there a way for "M" to update a message line on the page that "S"
left on the terminal screen, without "S" having to be called, and
without "M" having to rewrite the entire page?
--
James H. H. Lampert
Touchtone Corporation
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
