Networker

Re: [Networker] Why won't mminfo allow nsavetime on query?

2005-07-27 15:36:48
Subject: Re: [Networker] Why won't mminfo allow nsavetime on query?
From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 27 Jul 2005 15:27:44 -0400
I guess I worded the question wrong. What I observe is that if I run mminfo with -q savetime, and I use an nsavetime (numeric) value then it says no matches found, but if I include the client name like:

nsrinfo -s server -q 'savetime=nsavetimevalue, client=clientname'

then it returns what I expect, but why does it say no matches found when I say:

nsrinfo -s server -q 'savetime=nsavetimevalue'

George

Tim Mooney wrote:

In regard to: [Networker] Why won't mminfo allow nsavetime on query?,...:

I notice if I run mminfo -s server -q 'nsavetime=value', it won't work and just tells me the usage for the command. However, if I instead run:

mminfo -s server -q 'nsavetime=value, client=clientname'

then it works fine. Seems odd that you'd have to give it the client name. Why does it need that? Anyone else see this in laster releases? We're running 6.1.1 on Solaris 2.8.


Darren Dunham gave the definitive answer for this question several months
back (search the archives).  nsavetime can be used in reports (-r) only,
not in queries (-q).

However, `savetime' can be used in queries, and it will accept anything
that nsr_getdate can parse.  This includes a numeric savetime.

Tim

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=