|
I remember a change a version or two back where the behavior of that SYSVAL changed (maybe at V5R1?)... I think it changed to where it was more of a cumulative total limit, rather than a current total limit of devices that were created. This is a vague suggestion I realize... couldn't find any older "Memo to Users" documents in a quick search. Maybe it will trigger a more specific response... Mike.Crump@saint- gobain.com Sent by: To midrange-l-bounce Midrange Systems Technical s@xxxxxxxxxxxx Discussion <midrange-l@xxxxxxxxxxxx> cc 06/01/2005 03:16 PM Subject Re: (no subject) Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> James, One of the other factors to look for is the device types - there are certain attributes that the session may look for that you may not be needing - 24x80 vs. 27x132 being one of the obvious. I'm not sure if I can explain the exceeding QAUTVRT issue - my past problems have always dealt with issues revolving around device types. James H H Lampert <jamesl@xxxxxxxxx om> To midrange-l@xxxxxxxxxxxx 06/01/2005 02:07 cc PM Subject (no subject) Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> 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. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ForwardSourceID:NT00022B3E _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.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.