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

["Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>]

Then what would prevent it from picking a PC5250 session name?  Almost all our 
PCOMM sessions are hard coded.

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


I've always thought that when connecting it just picks the next device
randomly out of the pool of VARY ON PENDING devices which match the
device type, no matter if they start with QPAD or not. 


--
Justin C. Haase - Solution Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
Sent: Thursday, December 07, 2006 7:46 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Why isn't a QPADEV* name used?

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?