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

[Jim Langston <jlangston@xxxxxxxxxxx>]

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

From: "Dare" <oludare@ix.netcom.com>
Can you define these 2 options below for the 2 subsystems (QINTER and
SCANNER) without having any problem.  This may resolve it. You may also
write a CLP that does TFRJOB to SCANNER.

4. Work station name entries
5. Work station type entries