MSIR.0303 SORT/HASH key out of order: Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| Line 7: | Line 7: | ||
If you can tolerate the slower speed of loading without full track I/O, use the OPTION ANYORDER statement, as described in the <var class="book">[http://m204wiki.rocketsoftware.com/images/9/95/FrelrNew.pdf Fast/Reload Reference Manual]</var>. | If you can tolerate the slower speed of loading without full track I/O, use the OPTION ANYORDER statement, as described in the <var class="book">[http://m204wiki.rocketsoftware.com/images/9/95/FrelrNew.pdf Fast/Reload Reference Manual]</var>. | ||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]] | ||
Revision as of 15:52, 13 August 2015
This message is preceded by MSIR.0304, and indicates that the switch was required because you were loading data to a hash or sort key file and a record was encountered out of hash or sort key order.
If you are using LAI, the ordering can be done by the HASH or SORT option of the UAI statement in Fast/Unload; see the Fast/Unload Reference Manual.
Otherwise, you should ensure that your input records are in the correct order, to obtain the full track I/O benefits of Fast/Reload. You must sort the TAPEI dataset in order by the SORT key, or by the hash code of the hash key. You can do this hash key sorting using the M204HASH utility.
If you can tolerate the slower speed of loading without full track I/O, use the OPTION ANYORDER statement, as described in the Fast/Reload Reference Manual.