Using a calculated timestamp value in a query against the events table does not work as you would expect. It boils down to an issue with when TSM constructs the events table to run the query against. The default for "q event" and "SELECT xxx,yyy,zzz from EVENTS..." is for the current day *only*.
When you run your query with a calculated value to compare the scheduled_start against, TSM builds the events table first (using the default current day) BEFORE doing the comparison of "scheduled_start>current_timestamp - 1 day"
If, on the other hand, you use a static value for the comparison, TSM will return the results that you expect. I've tried multiple tacks on getting around this, including nesting the date comparison in one or more sets of parentheses, but I was not able to come up with a way to have a server-side TSM script that would allow us to just type "ru q_cl_status". There may be a way to do this, but I was not able to puzzle it out...
I had opened a PMR with IBM about this, and essentially got a "working as designed" response from development.
Ted
At 10:04 AM 10/3/2003 -0400, you wrote:
Hello everyone!
I have tried this select statement many times with no success. I thought that this statement had previously worked, but now I'm having problems again... I am looking for all nodes that begin with HM and PA for the past day. Does anyone have any suggestions? This is on a mainframe TSM server 5.1.6.2 and I am trying to query NT clients. I have also tried to create this through the TSM Opertional Reporting tool without any luck, so I am assuming that something is wrong with my syntax. Thanks in advance!!!
select node_name, scheduled_start, schedule_name, status - from events - where (node_name like 'HM%' or node_name like 'PA%') - and scheduled_start>current_timestamp - 1 day - order by node_name
Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338
