Re: Problem with AS/400 Devices

Dale,

Be SURE to get a printout of every device on the line that the problem device is
on and then verify the address at every one of these devices. Be SURE to check
the number of sessions configured against your printout i.e. Device "A" shows at
address 0 on you printout but you go to device "A" and it is configured with a
Display at 0 and a Printer at 1 and it does not HAVE a printer. NORMALLY a
printer would be created in a situation like this UNLESS the line is FULL, then
it just causes address problems. I would also suspect a failing device but it
might NOT be the one that shows Failed... In this case you basically have to
check them one at a time. Something else I've seen it the "pig tail" that
attaches your device to the cabling has failed. This isn't real common but it
DOES happen (had a printer with this problem the other day...). Are these IBM
terminals ? Unfortunately I'm stuck with Decision Data and we have been having
WAY to many of these devices going "haywire" and causing similar problems to 
what
you are describing. On them you have a "Printer Sessions - Yes or No" and it
appears that EVEN THOUGH it is SET at NO it really is YES. Replacing the device
(once I found it) fixed the problem. Bringing it back to the Corporate location
and plugging it in here caused duplicated the problem. So it WASN'T the wiring 
at
the branch,  it wasn't the control unit, it WAS the device...

Fun, fun, fun...

Good luck and let me know how it turns out !!

Chuck

Dale Pascual B Jose wrote:

> Has anyone experienced this?
>
> 1.)  There is a 3486 Dumb Terminal that fails, cursor is on the upper left
> of the screen and the status of these devices on the AS/400 is "failed" .
> Do we have to change the emulation type that these terminals are emulating.
>
> 2.)   There is this Dumb Terminal that return to sign on screen even though
> they are using these devices. And there are dumb terminals that return to
> sign on screen even though this terminals are idle, terminal screen are on
> users menu.
>
>      Note: This is a terminal that had dual session and only one session
>      return to sign on screen.
>
> 3.   Once users are using this device, there are times that the character
> they are encoding/typing is not displayed. But when they check it, number 0
> sometimes replaces the character.
>
> +---
> | 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
+---