Push DCI values due to register maintenance operations

[gannet]

Hello! I am on my way to account periodic maintenance operations - a toner change, waste a toner box, consumables (DrumUnit for example) replacement and I found that snmp in netxms could be helpful for this question too, because each modern MFP shows a lifetime counter and each component part has it's own lifetime resource too.
Fixing a counter in individual metrics script is an absurd, so I reach to acqusition of maintenance lifetime stamps through Push Agent. I get the lifetime counter through nxsnmpget and for /f "tokens=3", then...
Then I check nxpush and found that in 3.1.3 Windows version of NetXMS it does not work at all! It just shows help information and checks existence of one "-" after it. No output, no errors\events on a server!
A command like 'nxpush -u pa -p secret localhost 4352:WasteTonerClean=21333' has no result. As well as 'nxpush -USA pa -p notsecret localhostel 43fifty2->WasteTonerClean~=21333' in each combination of wrong parameters.
I've read Administrator's quide but user's on our server does not have a "Push Data" rights option. And no other barrier for the command execution! Why doesn't work? ЧЯДНТ? Please help me to realize this simple idea:)

[Filipp Sudanov]

Try to use -P instead of -p.
(one day nxpush will give correct error message in that case :))

[gannet]

Thank you very much! I was inattentive :-[ Don't know why but now this serene perception of all my attempts reminds me light clouds floating across the sky ???

@filipp-sudanov said in Push DCI values due to register maintenance operations:

Try to use -P instead of -p.

For me at first it had sounded like a joke (P - parking)