Re: 3489 mouse issue

Al Barsa wrote:
> A mouse was supported on the 3487, 3488 and 3489, and it was more or
> less useless.  I primarily used my 3489 as a vehicle to order free mice
> when one of the PC's mouse broke;  IBM would deliver it free!


and Pat Barber wrote:
> What version of OS/400 and how does the 3489 "appear" to the 400 ???
>
> The mouse is not really known to the system and is a terminal function...
>
> I can't find my 3488 manual right this moment but I can't see a mouse
causing a "terminal crash"....
>
> What is the error message number ???

Actually, I find the mouse somewhat useful on a terminal, moreso with the
3489 than the 3487 (especially with the neat mouse-aware split screen and
color-coded display sessions). 'Twould be nice if it also had some of the
mouse-related features I put into our emulator, but it's nice enough as it
is.

At any rate, the failure sent a CPI9357, "Error with magnetic stripe
reader or selector light pen on device DSP01," to the QSYSOPR message
queue. Problem analysis produced "The work station controller received
status that was not valid from the work station. One of the following was
not valid: *Magnetic stripe reader status   *Selector light pen status."
After telling problem analysis that the terminal wasn't connected through
a link protocol converter, it reported 55% Display, 20% Magnetic stripe
reader, 20% Selector light pen, 5% Work Station IOP or IOA system Licensed
Internal Code.

As I said, "Saturn" is a D02, running V2R3, with a non-enhanced twinax
controller. Nothing in the InfoWindow or InfoWindow II series has a
magnetic stripe reader option, nor a Selector Light Pen option, so far as
I know; as I recall, there is, however, some sort of mouse-based light pen
emulation available in the InfoWindow II series.

Our 510 is also on a non-enhanced controller, but it simply ignores mouse
clicks, making the mouse safe for use controlling the split-screen.

--
JHHL