|
CA Express Beta for V5R1 allows for a "generic name" for example you can set users initials as the device name and specify that you want to add a prefix for printer or display, avoid duplicate names for this workstation and avoid duplicate nemes with other workstations. Devices will them be generated using these rules. You can them run multiple CA sessions using the same configuration file without any issues of duplicate devices. -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Jim Franz Sent: Monday, March 19, 2001 4:10 AM To: MIDRANGE-L@midrange.com Subject: Re: QPADEV proliferation In IBMs Client Access, for many releases now, you can assign a device name in the configuration screen. Most other tn5250 products now support this. If you want to run multiple sessions, you will have to config multiple sessions, each with it's own device name. If you change the system value qautovrt for virtual devices, to a lower number, that will also keep so many created, but if at any one time, all the virtuals are signed on, next device to try will not get on. Once a virtual is created, changing the sysval does not delete them. You can delete all of them, and as long as the sysval is not zero, the system will auto create them as people connect. The delete device allows generic, so dltdevd qpadev* is valid. btw- fix ip or dhcp does not matter in this. jim ----- Original Message ----- From: "Emanuele Salvador" <lele@profim.florida.it> To: <MIDRANGE-L@midrange.com> Sent: Monday, March 19, 2001 4:48 AM Subject: QPADEV proliferation > Hi, > is there a way to stop QPADEV proliferation, assigning a fixed > session name to a device connecting thru telnet to AS/400? > The ip addresses from where the requests come are fixed, not assigned by DHCP. > > Thanks, > Emanuele Salvador > -- > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.