<![CDATA[WMI query returns codes]]>Hi Victor,

Some WMI queries return code numbers. For example, WMI.Query(root\CIMV2, Win32_Processor, Architecture) returns 0 for x86, 9 for x64. How to write a script which can transform the result ? Some example will be really helpful, as there are lot of queries which return code numbers. I am configuring the queries in DCI configuration.

Thanks in advance,

Ravi

]]>https://forum.netxms.org/topic/6254/wmi-query-returns-codesRSS for NodeFri, 13 Nov 2026 13:20:19 GMTMon, 04 Nov 2019 13:15:56 GMT60<![CDATA[Reply to WMI query returns codes on Tue, 12 Nov 2019 12:46:20 GMT]]>Thank you so much for all the info. I look forward for the 3.1 version.

Thanks and best regards,

Ravi.

]]>https://forum.netxms.org/post/26924https://forum.netxms.org/post/26924Tue, 12 Nov 2019 12:46:20 GMT<![CDATA[Reply to WMI query returns codes on Mon, 11 Nov 2019 10:30:19 GMT]]>Support for WMI queries returning lists or tables will be made available in 3.1 version.

]]>https://forum.netxms.org/post/26912https://forum.netxms.org/post/26912Mon, 11 Nov 2019 10:30:19 GMT<![CDATA[Reply to WMI query returns codes on Wed, 06 Nov 2019 15:15:57 GMT]]>Currently WMI subagent does not support data presentation as table or list, it just takes first from received values. We are planning to implement this at some point of time.

Capabilities are stored as a bitfield in that long integer, here you can find which bit represents what capability: https://www.netxms.org/documentation/datadictionary-3.0/#t-nodes

]]>https://forum.netxms.org/post/26894https://forum.netxms.org/post/26894Wed, 06 Nov 2019 15:15:57 GMT<![CDATA[Reply to WMI query returns codes on Tue, 05 Nov 2019 09:38:42 GMT]]>Thank you so much Filipp  and Victor. I added the script in the transformation and it is working fine. Great.

Another query I had, some of the WMI queries return a list, for example, WMI.Query(root\CIMV2, select * from Win32_LogicalDisk, caption), will return the list containing all the drives i.e. C:, D:, E: etc. How can I address this ? Also, , is it possible anyway, to a different row in raw_dci_values for each of these,  like - Caption: C:, Free Space: 87982829 bytes.

Secondly, in the Object details screen, we get the capabilities list, which displays what kind of device it is, e.g. Printer, Bridge, Router etc. I think this comes from the nodes table from the column capabilities. If it is so, how does the "capabilities" column represent the description, since it contains a long integer. Can you explain this to me ? I needed this info to display in a different screen.

Thanks a lot.

Best regards,

Ravi

]]>https://forum.netxms.org/post/26879https://forum.netxms.org/post/26879Tue, 05 Nov 2019 09:38:42 GMT<![CDATA[Reply to WMI query returns codes on Tue, 05 Nov 2019 09:03:14 GMT]]>Small addition: if you have lot of values to convert or they change frequently you may want to create mapping table on the server (via Configuration -> Mapping Tables) and use NXSL function map (https://www.netxms.org/documentation/nxsl-3.0/#func-map) to map code to text.

Best regards,
Victor

]]>https://forum.netxms.org/post/26875https://forum.netxms.org/post/26875Tue, 05 Nov 2019 09:03:14 GMT<![CDATA[Reply to WMI query returns codes on Mon, 04 Nov 2019 17:05:59 GMT]]>So, transformation scripts, as well as other scripts in NetXMS are written in NXSL - custom scripting language. It's syntax is resembling C language syntax. Language documentation can be seen here: https://www.netxms.org/documentation/nxsl-3.0/

Here's a sample script:

if ($1 == 9) {
  return "x64";
}
else if ($1 == 0)
{
  return "x86";
}
else
{
  return "unknown: ".$1;
}

$1 is the raw value (after step 1 of transformation), so in this case it's either 0 or 9. Other variables are also available in the script, e.g. $node in the node object to which the DCI belongs to. $node->name would be the name of the node.

You can use trace function to print debug information to server's log file, first parameter of trace is debug level on which the information is printed

trace(0, $node->name)

P.S. For me only the following syntax of the parameter worked on Win7:
WMI.Query(root\CIMV2,SELECT * FROM Win32_Processor, Architecture)

]]>https://forum.netxms.org/post/26872https://forum.netxms.org/post/26872Mon, 04 Nov 2019 17:05:59 GMT