The value of the KEYID specifier on the OPEN statement is either less than 1 or greater than the number of start-end pairs in the KEYS specifier. Therefore, no pair (and hence no key) can be associated with the value of the KEYID specifier.
This conflict can arise even if no KEYS specifier is coded: a default of one key is assumed, so if keyid has a value greater than 1, an error is detected.
If neither the ERR nor the IOSTAT specifier is present on the I/O statement, the condition is signaled. If the condition is unhandled, the application is terminated.
Qualifying Data: The basic set of four qualifying data for I/O conditions as shown in Table 1. Within this basic set, statement has a value of READ, and parm_count has a value of 4.
| Name | Action Taken after Resumption |
|---|---|
| RN | The remainder of the input item list is ignored, and execution continues. |
If the KEYS specifier on the OPEN statement accurately indicates the keys that you want to use, then change the value of the KEYID specifier so that it is a positive integer that is no larger than the number of start-end pairs in the KEYS specifier. Its value should be the ordinal number of the start-end pair for the key that you want to use.
If you intended to have additional keys available for use, then specify their starting and ending record positions as start-end pairs in the KEYS specifier on the OPEN statement. In addition, provide the file definitions (DD statements or TSO ALLOCATE commands) to refer VSAM paths for the additional keys.
FOR1104