I don't have 1.10 running yet, but someone reported to me that my RXSTOR64 exec told them to "call home". I have a check in there for in a subroutine that converts memory amounts to their largest possible unit.
FORMAT_MEMSIZE: /****************************************************************/ /* The following code is used to display the storage size in */ /* the largest possible unit. For example, 1023G and 1025G are */ /* displayed as 1023G and 1025G, but 1024G is displayed as 1T. */ /* The size passed to the routine must be in MB. */ /****************************************************************/ Anyway, my check for displaying MEMLIMIT as "NOLIMIT" looks for RAXLVMEMLIM = 17592186040320 - 16 exabytes. However, the value reported for health checker in z/OS 1.10 (at least for this person) is 17592186048514. Did z/Architecture just grow? :-) The fix is easy enough... to check for >= 17592186040320, but I am curious how this happened. Other than HC, all the other ASIDs with nolimit have 17592186040320 in the RAX. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[email protected] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
