|
A change is being contemplated to an esoteric option offered in the LOCKTSL (lock teraspace storage location) instruction. Changes to MI functionality are quite rare and never taken lightly but it seems unlikely that this particular option has much, if any, use. Is anyone using LOCKTSL? If so, is the "Lock the resolved single- level store location mapped to the teraspace storage location" option specified (i.e. a '1' value is given for the fifth bit at byte offset 0xE within the lock request template)? If so, please describe the reason for using this option, at a high level. Thank you. Paul Godtland, IBM
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.