×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 22 Aug 2013 14:51, Scott Klement wrote:
You can report this to IBM as a bug if you like.... IBM should not
have broken compatibility w/ V7R1. <<SNIP>>
Reporting that size limitation for the specification\maximum, as a
defect, would be a waste of time on both ends. The limitation
introduced by a change to the default alignment for the API was a
well-documented incompatible change; refer to a Memo to Users since v5r4:
From the v5r4 MTU:
"...
_i Default will change for QUSCRTUS parameter i_
In the release after V5R4 of i5/OS, the default value for the Optimum
alignment parameter of the Create User Space (QUSCRTUS) API will change
from 0 to 1, so optimum alignment will become the default.
This change will reduce the maximum amount of space available for user
spaces created with the default value. ..."
From the v6r1 MTU:
"...
3.4.3 _Create User Space (QUSCRTUS) API_
In i5/OS V6R1, the default value for the Optimum Alignment parameter of
the Create User Space (QUSCRTUS) API has changed from 0 to 1, so optimum
alignment has become the default. This change reduces the maximum amount
of space available for user spaces created with the default value. You
can programmatically retrieve the maximum size of an optimally-aligned
space using option Hex 0003 of the Materialize Machine Data (MATMDATA)
MI instruction.
Recommendation: Because the performance benefits of using
optimally-aligned spaces might vary over time, IBM recommends creating a
user space with optimum alignment, even if an application does not
experience a performance benefit from using an optimally-aligned user
space on one particular release.
..."
midrange.com
