RE: event-driven data to 4+ screens

["Kahn, David [JNJFR]" <DKahn1@xxxxxxxxxxxxx>]

Doug,

Depending how it's written there may be a single display file that's always
locked for each user in the application, but it's not necessarily the case. 

Dave Kahn
Johnson & Johnson International (Ethicon) France
Phone : +33 1 55 00 3180
Email :  dkahn1@jnjfr.jnj.com (work)
           dkahn@cix.co.uk      (home)



-----Message d'origine-----
De: dhandy@isgroup.net [mailto:dhandy@isgroup.net]
Date: 19 July 1999 19:30
À: MIDRANGE-L@midrange.com
Objet: Re: event-driven data to 4+ screens


Dave/Booth,

>Another idea might be to have the application's front end put a shared lock
>on a specific object, or there may already be a handy object that's always
>locked by all users within the application. Then simply retrieve the object
>lock details and send a break message to each locking workstation.

Since it is obviously an interactive application, why not just use the
DSPF associated with the program?  It automatically gets shared
no-update locks while the display file is open.  The QWCLOBJL api
documented in the Work Management APIs manual can be used to return
the list of current locks to a user space.

Doug

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---