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

----- Original Message -----
From: "Jim Langston" <>
To: <>
Sent: Thursday, January 17, 2002 1:57 PM
Subject: Separate subsystem - Devices not being allocated to it.

> 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
> *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
> 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?
> Any help is appreciated.
> Regards,
> Jim Langston
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> To post a message email:
> To subscribe, unsubscribe, or change list options,
> visit:
> or email:
> Before posting, please take a moment to review the archives
> at

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 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.