Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!sunic.UUCP!eric
From: eric@sunic.UUCP (Eric Thomas SUNET)
Newsgroups: comp.lang.asm370
Subject: Re: More dorky questions from me
Message-ID: <9009211758.AA03296@ucbvax.Berkeley.EDU>
Date: 21 Sep 90 17:20:51 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List
              <ASM370@OHSTVMA.BITNET>
Distribution: inet
Organization: The Internet
Lines: 11

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