Re: Separate subsystem - Devices not being allocated to it.

["Dan Turkeltaub" <dturk@xxxxxxx>]

jim,

we also have scanners as 5250 devices and have an interactive subsystem for
them. here's what to do...

- add a workstation entry to subsystem qinter for workstation name SCAN*, with
an allocation at *ENTER
- add a workstation entry to subsystem scanner for workstation name SCAN* with
an allocation at *SIGNON
- remove any workstation entries you made refering to device type.

this did the trick for us.

which scanner are you using? we have intermec 2425's, but we're looking for an
alternative that has a bigger screen.

regards,
dan turkeltaub
technology manager
keeney manufacturing
dturk@upt.com





Jim Langston <jlangston@celsinc.com> on 01/17/2002 02:44:57 PM

Please respond to midrange-l@midrange.com

To:   "'midrange-l@midrange.com'" <midrange-l@midrange.com>
cc:    (bcc: Dan Turkeltaub/UPT)

Subject:  Re: Separate subsystem - Devices not being allocated to it.




Well, I can change settings for the SCANNER subsystem no problem, since it's
a new one I just made the other day and I know that I won't be breaking
anything by not adding work station entries I need to.

But I am very hesitant about changing QINTER Works station entries or type
entries.  Although the majority of sessions are Client Access, there may be
some telnet sessions now and then (normally me, when I'm on a PC without
Client Access and need to get to an AS/400 command line quickly) and such.
Right now QINTER has no entries for either Work Station Names or Types.

The only sessions I want started in the scanner subsystem are sessions named
SCAN<something>.

I will try adding specific entries in addition to my default of SCAN* and
see if that helps.  That is, I will add SCAN133, SCAN134, SCAN135, etc...

The main reason I created a new subsystem for the Scanners is because they
have a dinky display, and the normal sign on screen looks bad on them.  So I
created a custom sign on screen for the SCANNER subsystem that looks rather
good on their screens.  By the time they get to a command line to type
TFRJOB or I have a CL do it, they're already in and it's a moot point.

Regards,

Jim Langston