- 最新
- 投票最多
- 评论最多
Hi there, the exception you’re seeing:
java.lang.RuntimeException: Unexpected attention key: "CLOSE" --> indicates that the GAPWalk runtime is receiving an unexpected AID key (e.g., a function key or attention key like F3, PF12, etc.), specifically "CLOSE", which it does not recognize.
Root Cause This typically happens when: An emulator interaction or terminal session simulation sends a key or input not supported by the underlying AIDConverter logic. Your transaction flow exits prematurely, and the GAPWalk runtime expects a different key (like ENTER or CLEAR) but gets CLOSE — which isn't mapped properly in convertToCharacter(...).
A thread pool task returns unexpectedly during a dialog or screen map transition.
**Fixes to Try: **1. Check Your Dialog Flow Make sure the terminal interaction or transaction handler (CICS emulation) does not return or simulate a "CLOSE" key unexpectedly. Review the screen/dialog mappings in your GAPWalk runtime setup (.bms/.jics files) to ensure "CLOSE" is not misconfigured.
-
Update AID Mappings (if customizable) If your setup allows it (check GAPWalk’s runtime configs), update the AIDConverter mapping logic or override it to ignore "CLOSE" or treat it as a no-op/exit. // Pseudo-override to skip "CLOSE" if ("CLOSE".equals(inputKey)) { return AID.EXIT; // or handle gracefully }
-
Upgrade BluAge Runtime or Patch This might be a known issue. If you're using Netfective BluAge GAPWalk (JICS), check for: Latest patches or hotfixes for your version (esp. for Java 17+ runtime compatibility). Release notes from BluAge about unsupported AIDs.
-
Debugging Tip: Wrap the LocalTaskRunner.invoke(...) or doCICSDialog() logic with additional logs to see which key is being sent from the frontend and when the error is triggered.
