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?

Chances are fair to good that QINTER has a workstation type entry that
includes the type the scanners are created as.  This means that both QINTER
and SCANNER can potentially allocate the devices.  If I remember rightly,
when a device can be allocated by multiple subsystems, the last subsystem to
start gets the device.

So, you can take the scanner workstation type out of QINTER (remove the
duplicate subsystem possibility)  or end and start SCANNER after QINTER
comes up (have the last subsystem up grab the device.)

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.