KXH105@PSUVM.BITNET ("Ken Hornstein 862-7007", 814) (09/17/90)
Ok, here's a good one for you: For those of you who saw my post earlier about having messages break into xedit, I think I got an answer. I check to see if full-screen is active when it comes time to to display messages (much thanks to the well-commented code of MSGTRAP); if it is active, then I save the message in memory. Now I have an I/O interrupt also, and when it is called for a console attention (ie - I get an interrupt on device X'09') THEN is display the message. It works, but I lose any changes that were made on the screen. Now is there a way I can "save" the screen changes, or perhaps display the messages after the screen update stuff has been done? Is there any hope? Or am I just wasting my time beating a dead horse? *sigh* What I wouldn't do just to *LOOK* at a few IBM manuals. --- Keep laughing at death, and eventually at least you may die laughing. Ken Hornstein kxh105@psuvm.psu.edu Phone: 814/862-7007
eric@sunic.sunet.se (Eric Thomas SUNET) (09/19/90)
Just set a flag when you get the attention but don't write the stuff right away; the next time you get a device end with the flag set, write your stuff and reset the flag. Eric
OPRJ38@TREARN.BITNET (or) (09/20/90)
for to save the screen, the following operations may be used..
- write (X'01') command (WCC X'00')
- if an error exist in CSW, the screen is not FSSM mode
- if screen is FSSM mode, 'CP MSG * message....'#ATTN'
else 'WRTERM message....'
- endKXH105@PSUVM.BITNET ("Ken Hornstein 862-7007", 814) (09/21/90)
In article <9009191529.AA29218@ucbvax.Berkeley.EDU>, you say: > >Just set a flag when you get the attention but don't write the stuff right >away; the next time you get a device end with the flag set, write your stuff >and reset the flag. Hmmm... ok, how do you check for a device end? Please remember that this is all done with interrupts ... some people haven't figured this out yet :-) --- You have your problems, and I have yours. Ken Hornstein kxh105@psuvm.psu.edu Phone: 814/862-7007
eric@sunic.sunet.se (Eric Thomas SUNET) (09/22/90)
In article <9009210036.AA13133@ucbvax.Berkeley.EDU> IBM 370 Assembly Programming Discussion List <ASM370@OHSTVMA.BITNET> writes: >Hmmm... ok, how do you check for a device end? Please remember that this is >all done with interrupts ... some people haven't figured this out yet :-) A device end is an interrupt, like an attention; it's just a different bit to test in the 5th byte of the CSW (ie CSW+4). Attention is X'80', device end is X'04'. Note that it may not come alone, actually if you're doing a read it will definitely not come alone, so use a TM rather than a CLI. Eric
eric@sunic.UUCP (Eric Thomas SUNET) (09/22/90)
In article <9009210036.AA13133@ucbvax.Berkeley.EDU> IBM 370 Assembly Programming Discussion List <ASM370@OHSTVMA.BITNET> writes: >Hmmm... ok, how do you check for a device end? Please remember that this is >all done with interrupts ... some people haven't figured this out yet :-) A device end is an interrupt, like an attention; it's just a different bit to test in the 5th byte of the CSW (ie CSW+4). Attention is X'80', device end is X'04'. Note that it may not come alone, actually if you're doing a read it will definitely not come alone, so use a TM rather than a CLI. Eric