What this 256-byte ""warning"" is telling you is that you are susceptible
to a
0C4 abend if you use a sort-key variable that is less than 256 bytes
long nd is allocated less than 256 bytes from the end of a physical 4K
page oundary.
The reason for this potential S0C4 is that if your program does not
""own""
he next physical 4K page, when 256 bytes are moved the move would start
on page that you own, but the end of the move would be on a page that
you do ot own. Somewhere during the execution of the move you will cross
the hysical 4K page boundary of storage to a page you don't own and will
get he S0C4 abend when this occurs.
When coding an OBTAIN USING SORT-KEY, remember that you can only have a
ingle variable in the SORT-KEY clause. If your INDEX or SORTED set has a
ey built of multiple values, you must supply a GROUP level SORT-KEY
ariable and each element within the group must match the picture and
order f the individual sort keys. This is noted in the second NOTE
following the OTE already cited by Chris.
Chuck