M204.0767: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add <var>'s) |
||
Line 1: | Line 1: | ||
{{Template:M204.0767 skeleton}} | {{Template:M204.0767 skeleton}} | ||
<P>A sort or hash key was specified for a file during initialization or as an argument of a host language interface IFINIT call. However, the file was created with a FILEORG parameter inconsistent with the key specified. | <P> | ||
A sort or hash key was specified for a file during initialization or as an argument of a host language interface <var>[[IFINIT (HLI function)|IFINIT]]</var> call. However, the file was created with a <var>FILEORG</var> parameter inconsistent with the key specified. | |||
Initialization fails. </P> | Initialization fails. </P> | ||
<p><b>Response:</b> If the file is not a sorted or hash file, eliminate the sort or hash key from the INITIALIZE command or IFINIT call and retry. If the file should be a sorted or hash file, contact the file manager to create the file with | <p> | ||
the proper FILEORG parameter. </p> | <b>Response:</b> If the file is not a sorted or hash file, eliminate the sort or hash key from the <var>INITIALIZE</var> command or <var>IFINIT</var> call and retry. If the file should be a sorted or hash file, contact the file manager to create the file with the proper <var>FILEORG</var> parameter value. </p> | ||
<p><b>File manager response:</b> Consider creating the file again, setting FILEORG to allow for sort or hash keys. </p> | <p> | ||
<b>File manager response:</b> Consider creating the file again, setting <var>FILEORG</var> to allow for sort or hash keys. | |||
</p> | |||
{{Template:M204.0767 footer}} | {{Template:M204.0767 footer}} | ||
<!-- skeleton as it was in pdf/UNNECESSARY SORT/HASH KEY REJECTED /--> | <!-- skeleton as it was in pdf/UNNECESSARY SORT/HASH KEY REJECTED /--> |
Latest revision as of 00:08, 2 March 2018
M204.0767 Unnecessary sort/hash key rejected
A sort or hash key was specified for a file during initialization or as an argument of a host language interface IFINIT call. However, the file was created with a FILEORG parameter inconsistent with the key specified. Initialization fails.
Response: If the file is not a sorted or hash file, eliminate the sort or hash key from the INITIALIZE command or IFINIT call and retry. If the file should be a sorted or hash file, contact the file manager to create the file with the proper FILEORG parameter value.
File manager response: Consider creating the file again, setting FILEORG to allow for sort or hash keys.
Message attributes:
RETCODEO=0 | Sets online return code |
---|---|
RETCODEB=4 | Sets batch (single user) return code |
CLASS=E | Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter |
AUDITER | Writes the message with line type ER to the audit trail |
COUNT | Increments the error count (ERCNT) parameter |