|
Basically, it allows you to view another users screen. It brings up a list of users who are signed on and you select the job you want. It then displays their screen exactly as they see it. It uses a message queue break handling program and data queues to do this. When the user signs on, his job creates a message queue in QRPLOBJ. The message queue name incorporates the job number so it is always unique and can be easily determined. The message queue is set in break mode with the break handling program set to the screen scraper program. When you request to view the screen, a message is sent to that message queue. The break handling/screen scraper program is fired off which gets the current screen and sends it back to your job in a data queue, where it is displayed. The user is not aware this is happening. To get a list of users who are signed on. I simply get a list of message queues in QRPLOBJ. In the version that I use, I have added additional functions to the break handling program so that I can, for example, dump the contents of the QTEMP library, or sign off the job. Once the break handling program takes control, the sky's the limit. Albert -----Original Message----- From: Chuck Lewis [SMTP:clewis@iquest.net] Sent: Wednesday, January 03, 2001 9:45 AM To: MIDRANGE-L@midrange.com Subject: Re: March 1996 The Display User Screen Utility (B960306.txt) Albert, What exactly does this program do ? Thanks, Chuck "York, Albert" wrote: > Chris, > > I wrote that article (and the program). I have been using it without any > problems since then, although I haven't tried it under V4R4. > > What problems are you having? > > Albert York > > -----Original Message----- > From: Quazy [SMTP:quazy@SoftHome.net] > Sent: Wednesday, January 03, 2001 8:38 AM > To: MIDRANGE-L@midrange.com > Subject: March 1996 The Display User Screen Utility > (B960306.txt) > > http://www.midrangecomputing.com/ftp/prog/96/b960306.txt > > Does anyone have a copy of this working on V4R4? I tried to get it > working, > but there must have been a quite a few changes with how message > queues were > used when this was written. > > Thanks > > Chris > > > +--- > | 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 +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.