I believe Accuterm is one of the 3rd party products you mentioned. At least is does have a U2 device licensing option in its configuration. However we cannot get device licensing to work using Accuterm, with SSH protocol and RHEL 4.0, Universe 10.2.4 enterprise version?
Is Accuterm still supported? Is SSH supported? Does the host os make a difference? What version of the uvlicn.dll is required? Anything else to look out for. Cheers, Phil. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Jenkins Sent: Thursday, 28 June 2007 10:30 a.m. To: u2-users@listserver.u2ug.org Subject: [U2] Device Licensing As others have posted: Device Licensing works for both U2 databases as long as you have a license which is one of: * Workgroup * Enterprise * Server with device licensing (a recent offering) In order that this will work you need a TELNET client that supports Device Licensing, and as there have been some changes in DL internals over time they should also concurrent in release - ideally (of course) the latest releases or fairly close. IBM supply SBClient, wIntegrate and Dynamic as Telnet clients that work with DL - on wIntegrate and DC you need to remember to check the "Use Device Licensing on Unix" check box if that is you server platform. DL will also work with UniObjects and ODBC (for example) thought you should read up on the use of subkeys for UO. Some 3rd parties have arrangements with IBM to use the DL software libraries with their software, and they offer DL compatibility with their TELNET clients. It is worth noting the point above though, DL internals have changed over time. You might find that older versions of the TELNET clients may not work correctly froma DL viewpoint with more recent copies of the databases. That being the case then an upgrade from your friendly local TELNET client provider to a current build with updated software should resolve it. Issues which got in the way in the past related mostly to combinations of "stty" settings in Unix, all (even vaguely) recent versions got the code modified so that's not an issue. There was also an issue more recent) where ODBC sessions (for example) used a different DL user pool to TELNET sessions. So ODBC would allow up to 10 sessions as one license, and TELNET would do the same - but each connection would use a separate slot. In those circumstances (for example) one UO and one TELNET would take 2 licenses (fixed). Always a useful test - try using Dynamic Connect from the current client software............that should work fine and act as a check on any 3rd party software. Hoping this answers any queries - please post if any follow-ups. Regards JayJay ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
