Re: Is it possible to have 2 display devices in one program?

["Steve Landess" <sjl_123@xxxxxxxxxxx>]

Booth -

I remember working with a couple of MAPICS MRT programs on the S/34.  Talk
about *UGLY* and hard-to-maintain code!

To work like on of the old-style MRT programs, your TALK program would have
to use the ACQ (Acquire) operation to allocate the devices, and then the
application could be running as you envision.  I don't believe you can use
ACQ to acquire a device unless it is *not* currently in use, and then *your*
application has exclusive control of the device.

IIRC, I don't think this is possible unless you assume that the user(s) on
the other terminal(s) sign off first.  And then how would you know which
terminal(s) to ACQuire?  This is not very workable in the real world.

Steve


----- Original Message -----
From: "Booth Martin" <Booth@xxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Monday, October 20, 2003 12:23 PM
Subject: Re: Is it possible to have 2 display devices in one program?


Actually, no.  That wouldn't be what I want to do.  I want a user able to
type "TALK UserName" and have the same subfile open on both people's screen.
 The called person would be interrupted, and would either continue the chat
or F3 the window closed.   The requirement is that both screens have the
same subfile, exactly.


---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------

-------Original Message-------

From: Midrange Systems Technical Discussion
Date: Monday, October 20, 2003 12:10:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: Is it possible to have 2 display devices in one program?

At 11:32 AM 10/20/03, you wrote:
>"Care to share?" Sure, why not, but no laughing, ok? I would like to
>develop a TALK utility. Reaching another user for a casual question is not
>graceful. Obviously the phone or Instant Messenger will always be a better
>method, but sometimes you just need to ask a quick question and SNDBRKMSG
is
>not very graceful.

Ahh, what you need then is a break message handling program, not the funky
program that reads/writes screens to more than one machine. If specified,
this program runs whenever a message comes in. You can decide how to
format it, what to do with it and so on. What is real nice is that you can
prompt a response from the user, and TALK it back to the sender.

CHGMSGQ MSGQ(FOO)
          PGM(MYLIB/MYPGM)

Take a look at the help on the PGM prompt and it will tell you what parms
get passed in.

It's been a long while, but my old one prefaced each message with a
constant, like 'TALK', and then handled those, but just did a DSPMSG on any
others.
_______________________________________________
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.