We're trying to get the shared licensing working on all our machines. We've run into a very strange issue. Most of our users run the Adds Viewpoint Enhanced emulation with a terminal type of wy50-vp.  Everything works fine if they run the uv command. If they run uvdls it sends this string: 

 ESC BS "A" BS "R" BS "D" BS "T" BS EOT BS "/" BS "x" BS

That's basically sending CHAR(27): "ARDT": CHAR(4):"/x" with a backspace after each character.

This is borking up the Viewpoint Enhanced terminal so you have to reset it from the menu to get it working again. It doesn't seem to do it if I use the Linux console with the linux term type but I'm the only one that runs with those settings.

I must be missing something. I couldn't find any information on how it's supposed to work so I'm asking here.

I think I figured out the issue. With the Wyze 50. That EOT character that's part of the license negotiation string also locks the keyboard. I worked around it by sending the STX character which unlocks it.

That's not a valid fix because I would have to change every logon on the system to send the STX character. I don't think the license negotiation should be locking the keyboard.

Does anyone have a better fix or work around?

I put a line in the UV account's UV.LOGIN proc that outputs the  STX character whenever anyone logs in. That got around the locking keyboard issue. Now the problem is that I'm not getting any license sharing. I login four times and it shows four licenses used. I've tried it with and without the LF option but that doesn't seem to make any difference.

I can see from the linux process listing that all my sessions are running uvdls. 

I'm still trying to find an answer. In my search I found this thread on the asent forum: https://forum.asent.com/universe-device-licensing_topic2547.html

The funny thing is, I started it and it's from 2015. That's when I got the shared licenses working. I don't know when it stopped working and I don't remember the solution. Pete says everything after the AccuTerm options is handled by Rocket and that I'd need to contact them. 

Anyone at Rocket want to chime in?