dslictool usage
Moderators: chulett, rschirm, roy
dslictool usage
Hi ,
I understand that using dslictool , we can find the number of licenses being used by datastage. But I believe it is not working as supposed to.
When I logged into the corresponding project through dssh ( UV environment ) , I found that 1 license is being utilized otherwise I am getting the below message.
$ dslictool
Warning License is in effect.
Message[PIN0037]
8 CPU's licensed.
DSPX package licensed.
DSSRV package licensed.
No. Pid, Package Device name IP address Device sub-key
0 license seats are in use.
8 license seats are available.
How can we see the number of licenses being utilized.
Phani
I understand that using dslictool , we can find the number of licenses being used by datastage. But I believe it is not working as supposed to.
When I logged into the corresponding project through dssh ( UV environment ) , I found that 1 license is being utilized otherwise I am getting the below message.
$ dslictool
Warning License is in effect.
Message[PIN0037]
8 CPU's licensed.
DSPX package licensed.
DSSRV package licensed.
No. Pid, Package Device name IP address Device sub-key
0 license seats are in use.
8 license seats are available.
How can we see the number of licenses being utilized.
Phani
Re: dslictool usage
How did you find this out in dssh?phanee_k wrote:Hi ,
...When I logged into the corresponding project through dssh ( UV environment ) , I found that 1 license is being utilized otherwise I am getting the below message...Phani
The correct display of the number of licenses that DataStage thinks are in use are displayed via the dslictool; any other result you see (perhaps using PORT.STATUS) might show the number of DataStage processes in use but will not reflect the number of licenses.
Hi ,
Once you log onto UV account using ./bin/dssh you need to logto the project by issuing LOGTO <projectname>
Now login into the ETL box through Telnet and issue the command dslictool.
You will be able to see that a PID is listed and the license is being utilized.
But when you login through designer / director / manager , dslictool is not showing the licenses utilized.
thanks,
Phani
Once you log onto UV account using ./bin/dssh you need to logto the project by issuing LOGTO <projectname>
Now login into the ETL box through Telnet and issue the command dslictool.
You will be able to see that a PID is listed and the license is being utilized.
But when you login through designer / director / manager , dslictool is not showing the licenses utilized.
thanks,
Phani
This is all I ever get from it:
It always says 0 license seats are in use and 8 available, regardless of the number actually in use or the fact that we are licensed for 22. So, what am I missing? ![Confused :?](./images/smilies/icon_confused.gif)
Code: Select all
$ pwd
/opt/datastage/Ascential/DataStage/DSEngine
$ ./bin/dslictool
Standard License is in effect.
Message[PIN0037]
8 CPU's licensed.
DSSRV package licensed.
No. Pid, Package Device name IP address Device sub-key
0 license seats are in use.
8 license seats are available.
![Confused :?](./images/smilies/icon_confused.gif)
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Seriously, looks like a BUG..
In my case, I have DS license for 4 CPUs, 5 users.
But dslictool shows something totally wierd:
It's showing me the license for 80 CPUs ![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
In my case, I have DS license for 4 CPUs, 5 users.
But dslictool shows something totally wierd:
Code: Select all
nnj@lpar5m:/dstage/dsadm/Ascential/DataStage/DSEngine:$ ./bin/dslictool
Warning License is in effect.
Message[PIN0037]
80 CPU's licensed.
DSPX package licensed.
DSSRV package licensed.
No. Pid, Package Device name IP address Device sub-key
0 license seats are in use.
8 license seats are available.
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
Nitin Jain | India
If everything seems to be going well, you have obviously overlooked something.
If everything seems to be going well, you have obviously overlooked something.