While activating a Universe/HP-UX site we realized that the license verification process may work differently depending on the OS user permissions. To explain this I thought I’d provide some insight into how our activation process works.
As mentioned recently I upgraded my Universe and Unidata Personal Editions to the latest releases. Actually I just did trial runs earlier in the week but today I did the real thing. After upgrading UniAdmin, Uni SDK, Universe and Unidata, I checked telnet connectivity, then decided to check my mv.NET connectivity. I thought I’d share the painless experience.
For someone getting started with mv.NET it’s easy to open an mvAccount, open an mvFile, maybe use an mvSelect on it, then read an mvItem. Some developers want to make more use of the environment, allowing users to select from a list of Login Profiles to access a specific account, then allowing selection of specific files, etc. It’s very easy to do this and I’ve provided the code here.