MSIR.0303 SORT/HASH key out of order: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
(Automatically generated page update)
 
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
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.  
This message is preceded by <code>MSIR.0304</code>, and it 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''.  
If you are using <var>[[Fast/Reload statements#The LAI statement|LAI]]</var>, the ordering can be done by the <var>HASH</var> or <var>SORT</var> option of the <var>[[Fast/Unload Extraction Language (FUEL)#UNLOAD ALL INFORMATION or UAI|UAI]]</var> statement in [[Fast/Unload]].  


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. This can be achieved using the M204HASH utility, as described in the ''"Model 204 File Manager's Guide"''.  
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 <code>TAPEI</code> data set in order by the [[Sorted files#Sort key characteristics|SORT key]], or by the '''hash code''' of the hash key. You can do this hash key sorting using the [[Hash key files#M204HASH utility|M204HASH utility]].


If you can suffer the slower speed of loading without full track I/O, use the OPTION ANYORDER statement, as described in the ''Fast/Reload Reference Manual''.
If you can tolerate the slower speed of loading without full track I/O, use the <var>[[Fast/Reload_statements#ANYorder|OPTIONS ANYORDER]]</var> statement.


[[Category:Sirius Mods Messages]]
{{Template:MSIR.0303 footer}}
[[Category:MSIR.0200 - MSIR.0399]]

Latest revision as of 23:08, 3 March 2017

This message is preceded by MSIR.0304, and it 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.

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 data set 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 OPTIONS ANYORDER statement.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=0Sets batch (single user) return code
CLASS=IInformation class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter

Back to list of messages

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=MSIR.0303_SORT/HASH_key_out_of_order&oldid=101403"