RE: Why isn't a QPADEV* name used?

Pete,
We have some RF terminals (portable computers with barcode scanners actually) 
that get QPAD* names when they connect.  There's also a thin client that has a 
a QPAD* right now. I just can't see a pattern in all this.
Bryan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Pete Helgren
Sent: Thursday, December 07, 2006 11:05 AM
To: Midrange Systems Technical Discussion
Subject: Re: Why isn't a QPADEV* name used?


Hmmm.  Do other devices generate the QPADEV* names or are you only using 
"hard coded" names (except for these new thin clients)?

This is ringing a quiet bell in my head but I can't remember what it is 
about.  Is your QAUTOVRT value set to *NOMAX (or at least a large number)?

Pete


Burns, Bryan wrote:

Pete,
Work station type entries are *CONS, 5555, and *ALL and the only thing in 
work station name entries are some old device names.  
Bryan 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Pete Helgren
Sent: Thursday, December 07, 2006 9:20 AM
To: Midrange Systems Technical Discussion
Subject: Re: Why isn't a QPADEV* name used?


Seems to me that that is part of the subsystem configuration.  What atre 
the entries for "Work station name entries" "Work station type entries" 
in the subsystem running the interactive jobs (probably QINTER).

Pete Helgren

Burns, Bryan wrote:
  

I have some type 3477 device descriptions that are hard coded names for java 
based emulators.  When I connect a CLI thin client and leave the device name 
blank, the system uses one of the hard coded names for the java based 
emulators instead of using a QPADEV* name.  How can I get the thin clients 
to use a QPADEV* name?  

Bryan Burns
M.I.S. Department
ECHO, Incorporated