|
Thanks but I think Rob's link to the use of an API should work (thanks Rob). I just have to figure out how to use an API. The only code I know is a little CL. I just want to gain a better understanding of how our devices are described on the system. If I could query them I could see patterns. I have an immediate problem where some devices (such as the CLI thin client I just configured) are using device names that were already assigned to other devices. Assigned to another device but in a vary-on pending stage. It happens with devices that use something other than PC5250 emulation. I expected the new thin client to use a QPADEVxxxx type device name, but instead it took a device name assigned to a remote computer that was not using it. Bryan -----Original Message----- From: Jones, John (US) [mailto:John.Jones@xxxxxxxxxx] Sent: Wednesday, September 28, 2005 8:31 AM To: Midrange Systems Technical Discussion Subject: RE: DSPDEVD *All What about something like this? RTVCFGSRC CFGD(*ALL) CFGTYPE(*DEVD) SRCFILE(SOMELIB/QCLSRC) SRCMBR(DEVICES) It would take some parsing, but might work for you. What are you trying to accomplish?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.