No problem.

The device licensing is for being able to connect to the server multiple
times from the same machine but only use 1 license. It won't prevent you
from connecting from the console.

Does it actually say it's licensed? Did you perhaps load UD locally
about a month ago? If smm is not running then no-one would be able to
connect. If it's a critical system I would expect you to be a lot more
frantic.

The service I've had problems with is "Windows Management
Instrumentation Service;" however, it let UniData start on the reboot.

A phantom simply lets the udt process run in the background. You will
still need smm running. It's pretty easy to use: from the command line
you simply enter "PHANTOM "command"" Note that the process will go
through the login voc item and the process will abort if it stops to ask
for input.

Hth
Colin Alfke
Calgary Canada

>-----Original Message-----
>From: Christensen, Steve
>
>Thanks, Colin and to everyone who offered suggestions.  Most 
>of these I have been through including the IBM docs I have 
>access to but Colin's suggestion about another service issue 
>may be a clue to the problem.
>
>I am giving myself a crash course in unidata since I am only 
>familiar with the more common relational database apps and I 
>have a critical system that runs on unidata but support 
>options for this are limited so I am not particularly familiar 
>with the platform at this point.
>
>If the licensing does not have the Device License option would that
>disallow running the udt command line on the local machine?   I have
>setup a script to run and extract the data to text files but 
>without the ability to start the udt session locally I am not 
>able to run the program.  I was also looking at perhaps 
>finding a way to run it as a phantom process but am not sure 
>on the syntax on that and whether or not I can bypass the udt 
>command in that fashion.
>
>Thanks for all the help.
>
>Steve
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to