dslictool usage?

chulett · Post by **chulett** » Wed Oct 26, 2005 10:16 am

Curious on how exactly I'm supposed to use the dslictool utility. Just had a situation where all 16 of our licenses were in use, so needed to find out who was on and who I could kick off.

Querying DS_LICENSE gave me most of what I was looking for, but it wasn't obvious how many of the 16 DataStage thought was actually in use. Running 'dslictool' from the command line gave me this output:

$ ./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.

What 'license seats' is it referring to here? All 16 were in use, not zero and none were available, hence the question.

ArndW · Post by **ArndW** » Wed Oct 26, 2005 10:26 am

I did the same here and it said 1 in use, 8 available and there are more than that working on this environment! I wonder if this is an older program using the old licensing scheme?

ray.wurlod · Post by **ray.wurlod** » Wed Oct 26, 2005 4:39 pm

Try it with the report_lic option explicitly specified.

chulett · Post by **chulett** » Wed Oct 26, 2005 5:06 pm

Should have mentioned that I saw that in another post and tried it earlier - it didn't change what was output. At least not for me. :cry:

chulett · Post by **chulett** » Thu Oct 27, 2005 1:17 pm

Since this doesn't seem to be the answer, what is the alternative? A query of DS_LICENSE returns as many rows as there are connections not licenses in use. Is there some quick way to get how many licenses it thinks are currently in use?

ray.wurlod · Post by **ray.wurlod** » Thu Oct 27, 2005 4:48 pm

That is, of course, what dslictool should give.

You could also try analyze.shm -x (also known as smat -x), in which there's a "login count".

Within the dssh environment (in the UV account) you can issue CONFIG BRIEF to determine how many licences you have. In this environment you also have the ANALYZE.SHM command (but the option -x must still be in lower case).

Finally, you can make use of the fact that every DataStage process on the server machine has a "printer shared memory segment" allocated. These have keys of the form "0xdaebnnnn" where "dae" is the key prefix set by the INSTANCETAG parameter in the uvconfig file, and nnnn is the "port number" for that process. You can view these shared memory segments using the ipcs command in UNIX, or the shrdump command in Windows.