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

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Check the archives!  What you do is create an entry for SCAN* in QINTER with
the allocation set to *ENTER.  The new subsystem should have an entry of
SCAN* with the allocation set to *SIGNON.  Now QINTER will NOT allocate the
workstation at the SIGNON screen but the new subsystem will.  Any thing else
will be unpredictable.

Chris Bipes
CrossCheck, Inc.

-----Original Message-----
From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
Sent: Thursday, January 17, 2002 11:17 AM
To: midrange-l@midrange.com
Subject: RE: Separate subsystem - Devices not being allocated to it.


Jim writes:

>We have some scanners that do 5250.
>
>I then created a new subsystem called
>SCANNER, set up autostart job 999 for
>*ANY to do QCMD, and added the Work
>Station Entry SCAN*
>
>When a scanner first initiates and the
>device description is created, it's
>running under QINTER.  Not much of
>a problem, I vary off the device
>(make it unavailable) and re-initiate
>conversation with the scanner and
>the session comes up in the SCANNER
>subsystem like I want.
>
>But... the next day, turn on a scanner,
>initiate conversation and it comes
>up into the QINTER subsystem again,
>even with the device name SCAN133.
>
>What did I miss?  Why aren't these
>communiations being initiated in the
>SCANNER subsystem but QINTER?