Informix Error -1134
-1134 There is no termcap entry for this function key.
The key that is specified in one clause of this OPTIONS statement is not defined in the termcap file (or the terminfo file if you are using it instead). Review the HELP KEY, INSERT KEY, NEXT KEY, PREVIOUS KEY, and DELETE KEY clauses. Compare the function keys that they specify to the current termcap definition.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-1134 fires when a key named in an OPTIONS statement clause (HELP KEY, INSERT KEY, NEXT KEY, PREVIOUS KEY, or DELETE KEY) has no corresponding definition in the active termcap (or
terminfo) file — per the official guidance, the key was specified but the terminal definition
doesn't back it.
- A key named in one of these
OPTIONSclauses that the active termcap/terminfo entry doesn't define, per the official guidance — the direct, only cause. - A terminal type switched (via
TERM/TERMCAP/INFORMIXTERM) without checking that the new entry still defines every key the program'sOPTIONSstatement relies on.
Solutions / Resolution
- Review the
HELP KEY,INSERT KEY,NEXT KEY,PREVIOUS KEY, andDELETE KEYclauses, per the official guidance, and compare the specified function keys against the current termcap definitions. - Choose a key that the active termcap/terminfo entry does define, or update the terminal definition to add the missing key.
Examples
Checking the active termcap definition
$ echo "$TERMCAP"
$ infocmp | grep -i "kf1\|khlp"
Diagnostic Checks
- Compare each key named in the program's
OPTIONSclauses against the active termcap/ terminfo entry, to find which one is undefined.
Related Errors / Related Topics
- -1005 — "Your specified termcap file cannot be read." A related termcap error, about file accessibility rather than a missing key definition.
- -1008 — "Termcap entry too long." A related termcap-content error, about excessive length.
- -1009 — "Bad termcap entry." A related termcap-content error, about malformed punctuation.
- -1010 — "Too many tc= indirections." A related termcap-content error, about chained references.
A key named in the program's OPTIONS clause has no definition in the active termcap/terminfo
entry — compare the two and adjust whichever is wrong.