Question
Cognizant
IN
Last activity: 26 Feb 2024 7:54 EST
Unable to handle Keystrokes using # and % in Mainframe.
Hi,
In few machines, special character like #, % and @ is not accepting in mainframe while we pass this character through send key method in pega. Unable to find solution. Please help me.
***Edited by Moderator Marije to add Support Case INC-B5615; update capability tags***
Accepted Solution
Pegasystems Inc.
GB
@JagadeeshB2503 I see that you logged INC-B5615 (Unable to pass special character in Mainframe Emulator) on 9th February
Our support team have been investigating since then
The latest details are:
------------------------------------ GCS:
"We have been waiting from feb 15th for a response, we need verbose runtime log to further troubleshoot on the issue.
We need to review the previous entries in the log as well to understand the exact rootcause.
Also please let us know your convenient time to have a quick webex on this issue, to further discuss on this issue."
Your confirmation for closure :
"I requested the user to change the pwd with out “@” , It worked and concluded @ is not working .
As is it working now I was not able to collect the error log from the user .
I do have a different issue facing with respect to SSO configuration . For now, we can close this SR ."
---------------------------------------
Pegasystems Inc.
US
@JagadeeshB2503I think the best way to resolve this for you is to open a support request. Getting hands on with your specific emulator is necessary to know which keys it is unable to accept and how to get them there.
Accepted Solution
Pegasystems Inc.
GB
@JagadeeshB2503 I see that you logged INC-B5615 (Unable to pass special character in Mainframe Emulator) on 9th February
Our support team have been investigating since then
The latest details are:
------------------------------------ GCS:
"We have been waiting from feb 15th for a response, we need verbose runtime log to further troubleshoot on the issue.
We need to review the previous entries in the log as well to understand the exact rootcause.
Also please let us know your convenient time to have a quick webex on this issue, to further discuss on this issue."
Your confirmation for closure :
"I requested the user to change the pwd with out “@” , It worked and concluded @ is not working .
As is it working now I was not able to collect the error log from the user .
I do have a different issue facing with respect to SSO configuration . For now, we can close this SR ."
---------------------------------------