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

["John Earl" <johnearl@xxxxxxxxxxxxxxxxxx>]

> We have some scanners that do 5250.  I named each of the scanner 5250
> sessions SCAN<something> like SCAN133, SCAN134, etc..
>
> 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.  I
> have to vary off the device, reinitiate conversation and it comes up into
> the SCANNER subsystem like I want.
>
> What did I miss?  Why aren't these communiations being initiated in the
> SCANNER subsystem but QINTER?  What do I need to do to fix this?

The rules for device acquisition are clearly spelled out in the Work
Management guide (Circa V3r1) - and I've doubt they have changed much.  I
can regurgitate some relative parts...

If two subsystems are eligible to acquire a Varied On device, whent he
subsystems are started, the subsystem that comes up _last_ will steal the
device from any subsystem that had previously aquired the device.

If a device is Varied Off when the two subsystems are initially started,
which subsystem will eventually aquire the device cannot be predicted.
:(  (That's prit neer a quote from the manual).

HTH,

jte

--
John Earl
www.powertechgroup.com  johnearl@powertechgroup.com
The Powertech Group Inc. Seattle, Washington
Where the Security Experts Live!

Phone: +1-253-872-7788 (optional)
Fax:   +1-253-872-7904 (optional)
--