The V5R2 Memo to Users has a section on QAUTOVRT and indicates that non-0 values will now be enforced for Telnet and Virtual Terminal Manager APIs. This is probably the change you are thinking of. Bruce Vining rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 06/01/2005 02:20 cc PM Subject Re: (no subject) Please respond to Midrange Systems Technical Discussion James, Awhile back I was less than impressed with the QAUTO... series of system values. To me it looked like the system ignored these and did a command 'under-the-covers' to create devices and thus it didn't count as an auto-anything. However when I stated so I took quite a trouncing on this list. Perhaps this explains it. Maybe on the earlier versions of OS it was poorly implemented. And then on the newer versions it actually worked as intended. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "James H H Lampert" <jamesl@xxxxxxxxxxx> Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx 06/01/2005 02:07 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Subject (no subject) On one of our customers' systems (a V5R2 box), we've found that the Telnet server is running into some sort of brick wall when creating new named devices, throwing CPF87D7s ("Cannot automatically select virtual device/The VTM/FM cannot automatically select . . .")in the QSYSOPR *MSGQ. They have QAUTOCFG and QAUTORMT turned on, and QAUTOVRT set at 99. The obvious hypothesis is that QAUTOVRT is being exceeded, which is supported by the fact that they've got a whole bunch of named and QPADEVxxxx devices sitting around, many of them varied off. The weirdest part is that if I try and exceed the QAUTOVRT on our V4R5 box (albeit through the secured Telnet server, since we have the unsecured one disabled on that box), it just keeps going, defining one whole series well beyond the limit, and continuing to define virtual devices even if I set QAUTOVRT down to 10, well below the number we have defined. So I tried our V4R4 box (which does have the unsecured Telnet server enabled), and it still gleefully creates named devices. Can anybody explain what the #%!! is going on here? Where else I should be looking? -- Puzzled on my first day back on duty JHHL -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact