|
No, The system values QMODEL, QSRLNBR and QPRCFEAT and consistent across all partitions. Assuming that you are using licensing that uses these metrics (as IBM's licensing does), then it should run in any partition given enough memory, disk, yada, yada, yada. There is a unique partition ID that can be retrieved by an API that a different licensing technique could use. I know of a few vendors who do that. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Steve Martinson <Steve.Martinson@ NetIQ.com> To Sent by: "'midrange-l@xxxxxxxxxxxx'" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc Subject 05/16/2003 03:30 LPAR Specifications PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxx nge.com> Is it possible for there to be situations where the processor or interactive feature code is different in one or more partitions of a single physical machine? Or are they all the same across all partitions (along with the serial number, of course)? I've seen situations where users were unable to get an application to work in one partition using the same license code that was generated for another partition, so they had to have a new code generated. It wasn't clear to me exactly what was different about the partitions. Was it because it wasn't a shared processor LPAR implementation? Steve Martinson _______________________________________________ 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.
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.