Hello
Over the last couple of days, we've been getting the message "UniVerse user limit reached. Please try again later" when there are 13 or more users declared by LISTU.
We use the UniVerse engine a lot in our DataStage work. Could somebody tell us where this user limit comes from, and whether we can set it to a higher value?
Thanks in advance,
Mihai
_________________
desk: 01908448571
UniVerse user limit reached
Moderators: chulett, rschirm, roy
Hmm.. depends on the definition of 'license limit'.
We have a license of 1 developer and 64 run-time (Director) sessions. Anyway, it is possible to connect using the DS Client tools (e.g. Administrator/Director), so I can't nail it down to that.
What I omitted to mention is that the message appears when trying to telnet to the DataStage server.
Kind regards,
Mihai
_________________
desk: 01908448571
We have a license of 1 developer and 64 run-time (Director) sessions. Anyway, it is possible to connect using the DS Client tools (e.g. Administrator/Director), so I can't nail it down to that.
What I omitted to mention is that the message appears when trying to telnet to the DataStage server.
Kind regards,
Mihai
_________________
desk: 01908448571
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You didn't specify what version of DataStage you were using. The licensing model changed when the DataStage Engine began to diverge from UniVerse (which, in the longer term, may have impacts on how you are doing things - you may need a UniVerse licence from IBM as well as a DataStage licence from Ascential).
In the bin directory within the server engine directory you will find an executable called uvlictool that can report how many connections are licensed. If I recall correctly, at release 4.2 and earlier this was a hard-coded limit of 4; at release 5.0 it is tied explicitly to the number of developers you have licensed.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
In the bin directory within the server engine directory you will find an executable called uvlictool that can report how many connections are licensed. If I recall correctly, at release 4.2 and earlier this was a hard-coded limit of 4; at release 5.0 it is tied explicitly to the number of developers you have licensed.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
quote:Originally posted by Ray.Wurlod
[br]You didn't specify what version of DataStage you were using. The licensing model changed when the DataStage Engine began to diverge from UniVerse (which, in the longer term, may have impacts on how you are doing things - you may need a UniVerse licence from IBM as well as a DataStage licence from Ascential).
In the bin directory within the server engine directory you will find an executable called uvlictool that can report how many connections are licensed. If I recall correctly, at release 4.2 and earlier this was a hard-coded limit of 4; at release 5.0 it is tied explicitly to the number of developers you have licensed.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
[br]You didn't specify what version of DataStage you were using. The licensing model changed when the DataStage Engine began to diverge from UniVerse (which, in the longer term, may have impacts on how you are doing things - you may need a UniVerse licence from IBM as well as a DataStage licence from Ascential).
In the bin directory within the server engine directory you will find an executable called uvlictool that can report how many connections are licensed. If I recall correctly, at release 4.2 and earlier this was a hard-coded limit of 4; at release 5.0 it is tied explicitly to the number of developers you have licensed.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518