topic WRQ reflection problem in Operating System - HP-UX

WRQ reflection problem

Isa_pr — Fri, 07 Apr 2006 05:08:05 GMT

Hello.

I use WRQ Reflection version 11.0 to conect with a Mainframe system, and I have a strange problem with the keyboard.
I need to use the character '#', and when I type it I can watch it in my screen, but later, I push ENTER and the character '#' is changed to character ':'. I don't know why.

I've tried to map it several times, and change a lot of characteristic of my keyboard, but I can't solve it.

Can somebody help me with this problem, please??

Isabel

Re: WRQ reflection problem

Paul Thomson_2 — Fri, 07 Apr 2006 09:04:56 GMT

Isabel

We use the same version of reflection for general X windows and connection to unix / linux machines.

Im UK based and my keyboard map is
UK Enhanced 102 Key
The terminal is US WYSE Keyboard.

Whilst this is probably not what you use I can access and type the # symbol.

Previously we had an issue with customers using symbols in Danish language and when they refreshed the screen the symbol would disappear and be replaced with something else. We had to update our locale setup for HPUX. Does the mainframe system support this symbol ?

Re: WRQ reflection problem

Isa_pr — Fri, 07 Apr 2006 12:54:21 GMT

Hello Paul,

I'm sure that Mainframe system supports this symbol, because I usually work with different machines and the problem I explained before only happens in one of them.
The configuration of each connection with WRQ Reflection is the same, but I don't know why in this one it can't run. But and the same time, I'm the only one that have this problem, because several of my partners usually access to the same machine and don't have this problem :(

Thanks

Re: WRQ reflection problem

John Dvorchak — Fri, 07 Apr 2006 14:15:53 GMT

Isabel to determine if it is WRQ problem or your profile on the mainframe. Go to a PC that works and have that person logoff then you logon as you and see if the # works or not. Then have that same person logon from your PC and see if # works or not.

From what you are describing I think you need to know if it's the PC or the Mainframe that has the problem.