T.R | Title | User | Personal Name | Date | Lines |
---|
5221.1 | Stab... | VMSNET::P_NUNEZ | | Thu Feb 13 1997 12:50 | 9 |
| Well, don't know if this applies, but until someone else replies...
$ exit 8596
%SYSTEM-F-NOLICENSE, operation requires software license
Do they have the appropriate UCX license loaded? (This couldn't be
a PATHWORKS license issue).
paul
|
5221.2 | license was a good idea - but... | MUNICH::BLASCH | | Wed Feb 19 1997 11:10 | 11 |
| re .1>
Thanks for the hint,
I was happy, because I logged in to the system and found that there
really was a license problem!
I enabled the appropriate license but the problem persisted. :-(
Now I'm again at a point where I got no ideas what to check further.
Birgit
|
5221.3 | | VMSNET::P_NUNEZ | | Thu Feb 20 1997 09:33 | 13 |
| Birgit,
What version of PATHWORKS is he using:
$ @sys$startup:pwrk$define_commands
$ pwver
Also, see if he has any concurrent use PATHWORKS licenses and report
the results:
$ show license pwlmvmscu05.00
Paul
|
5221.4 | UCX-License was the culprit | MUNICH::BLASCH | | Thu Feb 20 1997 11:21 | 15 |
| Hi Paul,
I was just logged in again to the customer system and found out
that your first guess was right:
The problem was the UCX-License!
When I was logged in the first time, I repaired the Licenses on
one node in a cluster, but the customer tested on ANOTHER node
on the cluster (I didn't fix the licenses on this node).
Therefore we didn't see any effect!
Many, many thanks (where shall I send the chocolate?)
Birgit
|
5221.5 | Sweet Rewards! | VMSNET::P_NUNEZ | | Fri Feb 21 1997 09:59 | 4 |
|
CHOCOLATE! Yesh...
Paul
|