Re: Events table
On Nov 13, 2006, at 8:04 AM, Smith, I (Ian) wrote: So if a scheduled event exists within the eventretention period but was before the time the node was associated- will this return a missed status? It appears to be the case. You can also encounter "misses" with small schedule Duration values (APAR IC49730). And you thought computers were deterministic... Richard Sims
Re: Events table
So if a scheduled event exists within the eventretention period but was before the time the node was associated- will this return a missed status? _ Ian Smith SAN/TSM Specialist -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 13 November 2006 12:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Events table On Nov 13, 2006, at 7:27 AM, Smith, I (Ian) wrote: > > Richard > > Does this make sense: > > That when a server is associated to a schedule, the events table > populates an entry for the server back to every scheduled time until > the start_time parameter. Hence all the uncertains. I expect that it > then attempts to poulate the returns be cross referencing the summary > table. > If there is no return code in the summary then it assumes missed. > Ian - The Uncertain's result from selecting beyond the age bounds of your EVentretention value. When performing an expansive Select on the Events "table", you need to specify a date/time, because this pseudo- table is unbounded. Richard Sims _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: Events table
On Nov 13, 2006, at 7:27 AM, Smith, I (Ian) wrote: Richard Does this make sense: That when a server is associated to a schedule, the events table populates an entry for the server back to every scheduled time until the start_time parameter. Hence all the uncertains. I expect that it then attempts to poulate the returns be cross referencing the summary table. If there is no return code in the summary then it assumes missed. Ian - The Uncertain's result from selecting beyond the age bounds of your EVentretention value. When performing an expansive Select on the Events "table", you need to specify a date/time, because this pseudo- table is unbounded. Richard Sims
Re: Events table
Richard Does this make sense: That when a server is associated to a schedule, the events table populates an entry for the server back to every scheduled time until the start_time parameter. Hence all the uncertains. I expect that it then attempts to poulate the returns be cross referencing the summary table. If there is no return code in the summary then it assumes missed. _ Ian Smith SAN/TSM Specialist Hitachi Data Systems Certified Professional IBM Tivoli Storage Manager Certified Consultant IT Infrastructure Rabobank International Thames Court, One Queenhithe London EC4V 3RL t: +44 (0)20 7809 3046 f: +44 (0)20 7809 3599 m: +44 (0)7843 689914 Mailto: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 13 November 2006 12:25 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Events table Ian - The peculiarities of the Events table can be found in many past discussions preserved in the List archives. It is not an actual table, but instead presents information derived from other sources in the TSM database (see APAR IC28825). As noted in ADSM QuickFacts, you need to specify values for the SCHEDULED_START and/or ACTUAL_START columns. See other APARs for more perspective. As you've noticed, you get different information reported from the table vs. the Query EVent command. Richard Sims _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: Events table
Ian - The peculiarities of the Events table can be found in many past discussions preserved in the List archives. It is not an actual table, but instead presents information derived from other sources in the TSM database (see APAR IC28825). As noted in ADSM QuickFacts, you need to specify values for the SCHEDULED_START and/or ACTUAL_START columns. See other APARs for more perspective. As you've noticed, you get different information reported from the table vs. the Query EVent command. Richard Sims
Events table
> When I do a select on the events table to get status of scheduled > events into the past, the table suggests nodes missed their schedule > even before they were associated with it! > > I need help here, as my statistics for missed backups look terrible!!! > > Does it assume a node was associated for ever, even though it was > associated recently: > > EG: > THE RETURN FROM THE SELECT: (Note the date) > > MONTHLYMTH_SUN_0300 LONS131001_MONTHLY > Missed 2006-10-01 > > 03:00:00.00 > > ONLY ASSOCIATED ON the 4th!! > > 10/04/2006 16:36:02 ANR2017I Administrator SMITHI issued command: > DEFINE > ASSOCIATION monthly MTH_SUN_0300 > > lons131001_monthly,lons131019_monthly,lons131024_monthly > (SESSION: 158168) > > > NB: > > When I do a q eve, it returns the following: > > tsm: LONTSM1>q eve * * begind=-60 endd=today nodes=LONS131001_MONTHLY > > Scheduled Start Actual Start Schedule Name > Node Name Status > - > - - > 11/05/2006 03:00:00 11/05/2006 03:15:38 MTH_SUN_0300 > LONS131001_M- Completed > > ONTHLY > > _ > Ian Smith > SAN/TSM Specialist > > > _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: select events table
Ahh, I see. I knew that TSM tables were built 'on the fly'; but had't realised that the events table is essentially unbounded, hence the need for the 'special' behaviour. Thanks, Matt. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Henrik Wahlstedt > Sent: 07 November 2006 11:01 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] select events table > > Nope, see the explanation in 'Why does it Work that Way (Andy > Raibeck).pdf' from TSM Symposoium in Oxford 2005. > > "Events table is calculated at runtime..." etc > > Cheers > Henrik > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of > Matthew Warren > Sent: den 7 november 2006 11:37 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: select events table > > Odd, how can it be that select * from events returns > different to select > * from events where scheduled_start>'1900-01-01' How is the table > 'special'? > > > > Matt. > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf > > Of Rainer Tammer > > Sent: 07 November 2006 09:15 > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] select events table > > > > Hello, > > > > goc wrote: > > > hi, > > > when i make select * from events i get data only for > current date , > > > i know with q event you can get back as defined in server options > > > but i would like to make some count(*) and stuff on > events data, so > > > my question is can i get further in past with direct > > select statement > > > to events table ? > > > > > This is a special table. > > You need a SELECT similar to the following statement: > > > > select count(*) as \"Administrative Schedules Successful\" > from events > > > where LENGTH(domain_name) IS NULL and scheduled_start > > '1900-01-01' > > and scheduled_start between (current_timestamp - 24 hours) and > > current_timestamp and status='Completed' and result=0 > > > > The important part is the scheduled_start > '1900-01-01' . > > Without the boundary you will get no useful events. > > > > > thanks big time > > > > > > goran > > > > > > > > Bye > > Rainer Tammer > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --- > > > 3.3TB in 12hours > > > > > > > > > > > > > > > > > This email is confidential and may be privileged. If you are not the > intended recipient please notify the sender immediately and delete the > email from your computer. > > You should not copy the email, use it for any purpose or disclose its > contents to any other person. > Please note that any views or opinions presented in this email may be > personal to the author and do not necessarily represent the views or > opinions of Digica. > It is the responsibility of the recipient to check this email for the > presence of viruses. Digica accepts no liability for any damage caused > by any virus transmitted by this email. > > UK: Phoenix House, Colliers Way, Nottingham, NG8 6AT UK > Reception Tel: + > 44 (0) 115 977 1177 Support Centre: 0845 607 7070 > Fax: + 44 (0) 115 977 7000 > http://www.digica.com > > SOUTH AFRICA: Building 3, Parc du Cap, Mispel Road, Bellville, 7535, > South Africa > Tel: + 27 (0) 21 957 4900 > Fax: + 27 (0) 21 948 3135 > http://www.digica.com > > > --- > The information contained in this message may be CONFIDENTIAL and is > intended for the addressee only. Any unauthorised use, > dissemination of the > information or copying of this message is prohibited. If you > are not the > addressee, please notify the sender immediately by return > e-mail and delete > this message. > Thank you. > > > >
Re: select events table
Nope, see the explanation in 'Why does it Work that Way (Andy Raibeck).pdf' from TSM Symposoium in Oxford 2005. "Events table is calculated at runtime..." etc Cheers Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Warren Sent: den 7 november 2006 11:37 To: ADSM-L@VM.MARIST.EDU Subject: Re: select events table Odd, how can it be that select * from events returns different to select * from events where scheduled_start>'1900-01-01' How is the table 'special'? Matt. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Rainer Tammer > Sent: 07 November 2006 09:15 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] select events table > > Hello, > > goc wrote: > > hi, > > when i make select * from events i get data only for current date , > > i know with q event you can get back as defined in server options > > but i would like to make some count(*) and stuff on events data, so > > my question is can i get further in past with direct > select statement > > to events table ? > > > This is a special table. > You need a SELECT similar to the following statement: > > select count(*) as \"Administrative Schedules Successful\" from events > where LENGTH(domain_name) IS NULL and scheduled_start > '1900-01-01' > and scheduled_start between (current_timestamp - 24 hours) and > current_timestamp and status='Completed' and result=0 > > The important part is the scheduled_start > '1900-01-01' . > Without the boundary you will get no useful events. > > > thanks big time > > > > goran > > > > > Bye > Rainer Tammer > > > > > > > > > > > > > > > > > > > > --- > > 3.3TB in 12hours > > > > > > > > This email is confidential and may be privileged. If you are not the intended recipient please notify the sender immediately and delete the email from your computer. You should not copy the email, use it for any purpose or disclose its contents to any other person. Please note that any views or opinions presented in this email may be personal to the author and do not necessarily represent the views or opinions of Digica. It is the responsibility of the recipient to check this email for the presence of viruses. Digica accepts no liability for any damage caused by any virus transmitted by this email. UK: Phoenix House, Colliers Way, Nottingham, NG8 6AT UK Reception Tel: + 44 (0) 115 977 1177 Support Centre: 0845 607 7070 Fax: + 44 (0) 115 977 7000 http://www.digica.com SOUTH AFRICA: Building 3, Parc du Cap, Mispel Road, Bellville, 7535, South Africa Tel: + 27 (0) 21 957 4900 Fax: + 27 (0) 21 948 3135 http://www.digica.com --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: select events table
Odd, how can it be that select * from events returns different to select * from events where scheduled_start>'1900-01-01' How is the table 'special'? Matt. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Rainer Tammer > Sent: 07 November 2006 09:15 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] select events table > > Hello, > > goc wrote: > > hi, > > when i make select * from events i get data only for current date , > > i know with q event you can get back as defined in server options > > but i would like to make some count(*) and stuff on events data, > > so my question is can i get further in past with direct > select statement > > to events table ? > > > This is a special table. > You need a SELECT similar to the following statement: > > select count(*) as \"Administrative Schedules Successful\" from events > where LENGTH(domain_name) IS NULL and scheduled_start > > '1900-01-01' and > scheduled_start between (current_timestamp - 24 hours) and > current_timestamp and status='Completed' and result=0 > > The important part is the scheduled_start > '1900-01-01' . > Without the boundary you will get no useful events. > > > thanks big time > > > > goran > > > > > Bye > Rainer Tammer > > > > > > > > > > > > > > > > > > > > --- > > 3.3TB in 12hours > > > > > > > > This email is confidential and may be privileged. If you are not the intended recipient please notify the sender immediately and delete the email from your computer. You should not copy the email, use it for any purpose or disclose its contents to any other person. Please note that any views or opinions presented in this email may be personal to the author and do not necessarily represent the views or opinions of Digica. It is the responsibility of the recipient to check this email for the presence of viruses. Digica accepts no liability for any damage caused by any virus transmitted by this email. UK: Phoenix House, Colliers Way, Nottingham, NG8 6AT UK Reception Tel: + 44 (0) 115 977 1177 Support Centre: 0845 607 7070 Fax: + 44 (0) 115 977 7000 http://www.digica.com SOUTH AFRICA: Building 3, Parc du Cap, Mispel Road, Bellville, 7535, South Africa Tel: + 27 (0) 21 957 4900 Fax: + 27 (0) 21 948 3135 http://www.digica.com
Re: select events table
Hello, goc wrote: > hi, > when i make select * from events i get data only for current date , > i know with q event you can get back as defined in server options > but i would like to make some count(*) and stuff on events data, > so my question is can i get further in past with direct select statement > to events table ? > This is a special table. You need a SELECT similar to the following statement: select count(*) as \"Administrative Schedules Successful\" from events where LENGTH(domain_name) IS NULL and scheduled_start > '1900-01-01' and scheduled_start between (current_timestamp - 24 hours) and current_timestamp and status='Completed' and result=0 The important part is the scheduled_start > '1900-01-01' . Without the boundary you will get no useful events. > thanks big time > > goran > > Bye Rainer Tammer > > > > > > > > > > --- > 3.3TB in 12hours > >
select events table
hi, when i make select * from events i get data only for current date , i know with q event you can get back as defined in server options but i would like to make some count(*) and stuff on events data, so my question is can i get further in past with direct select statement to events table ? thanks big time goran --- 3.3TB in 12hours
Re: select on events table question
Yes, what you describe is documented in IC34609, which is related to IC28825. The workaround is to include a hard-coded date as the first filtering criteria in your WHERE clause. Picking a hard-coded date will force the EVENTS table to include all events from that date, after which additional filtering criteria can be applied. For example: select node_name, status, scheduled_start \ from events \ where scheduled_start>='2005-01-01' and \ scheduled_start>=current_timestamp - 7 days and \ (status='Failed' or status='Missed') The first WHERE criterion forces the EVENTS table to include all events following 1 Jan, 2005 to be included for consideration, thus satisfying the use of a hard-coded date as described in IC28825. The other WHERE criteria provide the actual filtering we want, which is to look at events from up to a week ago that are either failed or missed. Using your specific example: select count(*) \ from events \ where scheduled_start between \ timestamp(current date - 30 day,'18:00:00') and \ timestamp(current date,'18:00:00') Change it to something like this: select count(*) \ from events \ where scheduled_start>'2005-01-01' and \ scheduled_start between \ timestamp(current date - 30 day,'18:00:00') and \ timestamp(current date,'18:00:00') The hard-coded date you use doesn't matter as long as it is as old (or older) than the oldest records you want to view. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" wrote on 2005-10-14 14:59:52: > I know that per APAR IC28825 if you try running select * from events > you will only get the events for today. > > > > That APAR lists a work around where running select count(*) from > events where scheduled_start between '2005-10-01 18:00:00' and > '2005-10-15 06:00:00' will actually give you the events for a date > range. With this I have to update the range each time I run it. > > > > I tried to use the timestamp with between as follows select count(*) > from events where scheduled_start between timestamp(current date - 30 > > day,'18:00:00') and timestamp(current date,'18:00:00'). But when I > use timestamp it reverts back to the problem where it only shows you > todays event data. > > > > Just wondering if Andy or any other SQL guru's out there might now > if I am using timestamp incorrectly with between. > > Kyle > > > > - > Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
select on events table question
I know that per APAR IC28825 if you try running select * from events you will only get the events for today. That APAR lists a work around where running select count(*) from events where scheduled_start between '2005-10-01 18:00:00' and '2005-10-15 06:00:00' will actually give you the events for a date range. With this I have to update the range each time I run it. I tried to use the timestamp with between as follows select count(*) from events where scheduled_start between timestamp(current date - 30 day,'18:00:00') and timestamp(current date,'18:00:00'). But when I use timestamp it reverts back to the problem where it only shows you todays event data. Just wondering if Andy or any other SQL guru's out there might now if I am using timestamp incorrectly with between. Kyle - Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
TSM 5.1.8 and 'events' table
Hello. Somehow 'events' table got broken some time ago. All schedules with 'missed' status have 'actual_start' set to 1900-01-01 :( Is this a common problem and about to be fixed? -- Przemysław Maciuszko Agora SA
TSM Optional Reporter and the EVENTS table
Hi all Have any of you had a chance to work with the new free TSM Optional Reporter ? (get ver. 7 here: ftp://index.storsys.ibm.com/tivoli-storage-management/techprev/tsmopreport/latest/ ) It just keeps getting better and better - now they are using XML as stanza/config files, which means we can edit the XML files and share our reports. Just wanted to know if anybody had some they'd like to share, and if anyone had figured out just how to use the special variables that are passed to the select statement (i.e. '%s'). Also, it seems that the EVENTS table does not contain the same information as the Q EVENT command queries, but only a very limited subset - are any of you familiar with this? This is not only the case with the TSM Optional Reporter, but also the commandline - and different versions of TSM. If you do a select * from event It returns much less entries than i.e. q event * * begindate=-3 enddate=today How come? Thanks! Best Regards Michael Gimm
Re: Events table information.
> I am not sure you will be able to do what you want even when you get > the selection criteria sorted out. The events table on our 5.1.7.2 server > does not have a column for completion time. If the same is true on your > server you will probably have to use 'query event' output to compute > durations. I believe that information can be found in the summary table (but then theres no problem with the criterias). SELECT ENTITY AS NODE_NAME,(END_TIME-START_TIME) AS DURATION FROM SUMMARY WHERE UPPER(ACTIVITY)='BACKUP' AND CURRENT_TIMESTAMP-START_TIME<'2 00:00:00' regards, Anders Pontusson
Re: Events table information.
> Hi TSM expert > I am trying to write a script to check a duration time of each schedule > in a day. I need to use an events table to select the data. But in this table it > show only the information of a current date. I dont know why. But when I use > q event begind=-2, it can display the information of 2 previous days. Dose the > information is corrected in this table? I am not sure you will be able to do what you want even when you get the selection criteria sorted out. The events table on our 5.1.7.2 server does not have a column for completion time. If the same is true on your server you will probably have to use 'query event' output to compute durations.
Re: Events table information.
The problem is when selecting from events table it's by default generated with the information of todays date only. Using (CURRENT_TIMESTAMP-SCHEDULED_START<'2 00:00:00') will get information less than two days old within todays info. See the problem? However if you specify a specific date (i.e. '2003-10-25') the events table will be generated from this. There's no limitation in SQL saying you can't use both a specific date and CURRENT_TIMESTAMP at the samt time. I spent hours figuring this out and note that the following workaround will only work for less than 200 years... SELECT * FROM EVENTS WHERE SCHEDULED_START BETWEEN '1970-01-01' AND '2199-12-31' AND CURRENT_TIMESTAMP-SCHEDULED_START<'2 00:00:00' regards, Anders Pontusson
Events table information.
Hi TSM expert I am trying to write a script to check a duration time of each schedule in a day. I need to use an events table to select the data. But in this table it show only the information of a current date. I dont know why. But when I use q event begind=-2, it can display the information of 2 previous days. Dose the information is corrected in this table? Thanks you, Wira Chinwong.
Re: Events table
You might want to read this article on this subject: http://msgs.adsm.org/cgi-bin/get/adsm0111/816.html > -Original Message- > From: David E Ehresman [mailto:[EMAIL PROTECTED] > Sent: vrijdag 28 maart 2003 14:03 > To: [EMAIL PROTECTED] > Subject: Events table > > > If I do a "SELECT * FROM EVENTS" I only get events for the > current day. > Are the events from previous days (like those available from > q event * * > begind=-1) available in another table? > > David >
Events table
If I do a "SELECT * FROM EVENTS" I only get events for the current day. Are the events from previous days (like those available from q event * * begind=-1) available in another table? David
Réf. : Re: Réf. : Re: Select statement (using events table)
I get nothing, as in ANR2034E SELECT: No match found using this criteria. ANS8001I Return code 11. I don't get it... I should have all the shceduled backups for yesterday. I've tried and tried to come up with a SQL query that would enable me to format the ouput of a q ev * * the way I want it (without long node names wrapping) but nothing seems to work... Guillaume Gilbert CGI Canada Zlatko Krastev/ACIT <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-07 10:58:30 Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Pour :[EMAIL PROTECTED] cc : Objet : Re: Réf. : Re: Select statement (using events table) Why it does not work? What error is returned and if it complains for syntax at which word? To be sure it works I've tested it on TSM 3.7.0 for Win (being at customer site) but when I return to office I will test it on 4.1.4.1 for AIX (out test one) and on 4.2.1.15. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Réf. : Re: Select statement (using events table) I can't seem to get a handle on this events table. The SQL you supplied isn't working on my server (4.1.3.0 on AIX). When I do a select with no dates in the where clause, all I get is the admin scheds for the current day. Other than that, I can't get a thing. Is there something I'm missing?? Thanks Guillaume Gilbert CGI Canada Zlatko Krastev/ACIT <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-07 08:54:26 Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Pour :[EMAIL PROTECTED] cc : Objet : Re: Select statement (using events table) select schedule_name, status, result, reason - from events - where date(scheduled_start) <= current_date - cast(1 as interval day) Zlatko Krastev IT Consultant Please respond to <[EMAIL PROTECTED]> To: "'Zlatko Krastev/ACIT'" <[EMAIL PROTECTED]> cc: Subject:RE: Select statement (using events table) Hi Zlatko, So that's the trick... I've trying to get the startdate set, using some example statements, but I cannot get it done it seems. Here's what I tried: select schedule_name,status,result,reason from events where (scheduled_start - 1 day) Well, that doesn't work :-( (obviously because the syntax isn't right :-) ). Do you happen to know how that works? Kind regards, Rick -Oorspronkelijk bericht- Van: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Verzonden: 6 juni 2002 14:56 Aan: [EMAIL PROTECTED] Onderwerp: Re: Select statement (using events table) Rick, the trick is that Tivoli decided for some reasons select from events to be limited as is in Q EVENT. You need to specify WHERE clause. Zlatko Krastev IT Consultant Please respond to [EMAIL PROTECTED] Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Select statement Hi *SMers, I've trying to figure something out using select-statements. I want to know what events did or didn't complete succesfully for, say, the last 24 hours. I'm getting the results, but I only get the results since last midnight. How do I get the results from the last 24 hours. This is what I have so far: select schedule_name,scheduled_start,actual_start,result from events Anyone here who can help? Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED]
Re: Réf. : Re: Select statement (using events table)
Why it does not work? What error is returned and if it complains for syntax at which word? To be sure it works I've tested it on TSM 3.7.0 for Win (being at customer site) but when I return to office I will test it on 4.1.4.1 for AIX (out test one) and on 4.2.1.15. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Réf. : Re: Select statement (using events table) I can't seem to get a handle on this events table. The SQL you supplied isn't working on my server (4.1.3.0 on AIX). When I do a select with no dates in the where clause, all I get is the admin scheds for the current day. Other than that, I can't get a thing. Is there something I'm missing?? Thanks Guillaume Gilbert CGI Canada Zlatko Krastev/ACIT <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-07 08:54:26 Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Pour :[EMAIL PROTECTED] cc : Objet : Re: Select statement (using events table) select schedule_name, status, result, reason - from events - where date(scheduled_start) <= current_date - cast(1 as interval day) Zlatko Krastev IT Consultant Please respond to <[EMAIL PROTECTED]> To: "'Zlatko Krastev/ACIT'" <[EMAIL PROTECTED]> cc: Subject:RE: Select statement (using events table) Hi Zlatko, So that's the trick... I've trying to get the startdate set, using some example statements, but I cannot get it done it seems. Here's what I tried: select schedule_name,status,result,reason from events where (scheduled_start - 1 day) Well, that doesn't work :-( (obviously because the syntax isn't right :-) ). Do you happen to know how that works? Kind regards, Rick -Oorspronkelijk bericht----- Van: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Verzonden: 6 juni 2002 14:56 Aan: [EMAIL PROTECTED] Onderwerp: Re: Select statement (using events table) Rick, the trick is that Tivoli decided for some reasons select from events to be limited as is in Q EVENT. You need to specify WHERE clause. Zlatko Krastev IT Consultant Please respond to [EMAIL PROTECTED] Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Select statement Hi *SMers, I've trying to figure something out using select-statements. I want to know what events did or didn't complete succesfully for, say, the last 24 hours. I'm getting the results, but I only get the results since last midnight. How do I get the results from the last 24 hours. This is what I have so far: select schedule_name,scheduled_start,actual_start,result from events Anyone here who can help? Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED]
Réf. : Re: Select statement (using events table)
I can't seem to get a handle on this events table. The SQL you supplied isn't working on my server (4.1.3.0 on AIX). When I do a select with no dates in the where clause, all I get is the admin scheds for the current day. Other than that, I can't get a thing. Is there something I'm missing?? Thanks Guillaume Gilbert CGI Canada Zlatko Krastev/ACIT <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-07 08:54:26 Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Pour :[EMAIL PROTECTED] cc : Objet : Re: Select statement (using events table) select schedule_name, status, result, reason - from events - where date(scheduled_start) <= current_date - cast(1 as interval day) Zlatko Krastev IT Consultant Please respond to <[EMAIL PROTECTED]> To: "'Zlatko Krastev/ACIT'" <[EMAIL PROTECTED]> cc: Subject:RE: Select statement (using events table) Hi Zlatko, So that's the trick... I've trying to get the startdate set, using some example statements, but I cannot get it done it seems. Here's what I tried: select schedule_name,status,result,reason from events where (scheduled_start - 1 day) Well, that doesn't work :-( (obviously because the syntax isn't right :-) ). Do you happen to know how that works? Kind regards, Rick -Oorspronkelijk bericht- Van: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Verzonden: 6 juni 2002 14:56 Aan: [EMAIL PROTECTED] Onderwerp: Re: Select statement (using events table) Rick, the trick is that Tivoli decided for some reasons select from events to be limited as is in Q EVENT. You need to specify WHERE clause. Zlatko Krastev IT Consultant Please respond to [EMAIL PROTECTED] Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Select statement Hi *SMers, I've trying to figure something out using select-statements. I want to know what events did or didn't complete succesfully for, say, the last 24 hours. I'm getting the results, but I only get the results since last midnight. How do I get the results from the last 24 hours. This is what I have so far: select schedule_name,scheduled_start,actual_start,result from events Anyone here who can help? Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED]
Re: Select statement (using events table)
select schedule_name, status, result, reason - from events - where date(scheduled_start) <= current_date - cast(1 as interval day) Zlatko Krastev IT Consultant Please respond to <[EMAIL PROTECTED]> To: "'Zlatko Krastev/ACIT'" <[EMAIL PROTECTED]> cc: Subject: RE: Select statement (using events table) Hi Zlatko, So that's the trick... I've trying to get the startdate set, using some example statements, but I cannot get it done it seems. Here's what I tried: select schedule_name,status,result,reason from events where (scheduled_start - 1 day) Well, that doesn't work :-( (obviously because the syntax isn't right :-) ). Do you happen to know how that works? Kind regards, Rick -Oorspronkelijk bericht- Van: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Verzonden: 6 juni 2002 14:56 Aan: [EMAIL PROTECTED] Onderwerp: Re: Select statement (using events table) Rick, the trick is that Tivoli decided for some reasons select from events to be limited as is in Q EVENT. You need to specify WHERE clause. Zlatko Krastev IT Consultant Please respond to [EMAIL PROTECTED] Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Select statement Hi *SMers, I've trying to figure something out using select-statements. I want to know what events did or didn't complete succesfully for, say, the last 24 hours. I'm getting the results, but I only get the results since last midnight. How do I get the results from the last 24 hours. This is what I have so far: select schedule_name,scheduled_start,actual_start,result from events Anyone here who can help? Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED]
Re: EVENTS Table
set eventretention . Use q stat to see current value. _ William Mansfield Senior Consultant Solution Technology, Inc Gerald Wichmann <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/26/2002 11:26 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:EVENTS Table How often does the events table get cleaned out? i.e. how far back should a "select * from events" go or what tunable parameter dictates how far that goes? Is it the same as how far back the activity log is retained? Thanks, Gerald Wichmann Sr. Systems Development Engineer Zantaz, Inc. 925.598.3099 w 408.836.9062 c
EVENTS Table
How often does the events table get cleaned out? i.e. how far back should a "select * from events" go or what tunable parameter dictates how far that goes? Is it the same as how far back the activity log is retained? Thanks, Gerald Wichmann Sr. Systems Development Engineer Zantaz, Inc. 925.598.3099 w 408.836.9062 c
Date math and the Events table
First off, I should say that I have read (and think I understand) Andy Raibeck's explanation from 11/23/2001 of the restrictions on queries against the Events table. However, in trying to craft a query that returns records from a relative timeframe, I am running into some problems getting the result that I would like to get. What I am trying to do is run a query that yields the same results as "q ev * * begind=-1 endd=today begint=08:00 endt=07:59" with an eye toward doing some calculations on the number of events with different status conditions This is what I came up with: select - schedule_name, - time(scheduled_start) as "Scheduled", - time(actual_start) as "Actual", - status as "Status", - node_name as "Client" - from events - where node_name is not null - and date(scheduled_start+16 hour-1 minute)=date(current_timestamp) This returns events only from the current day However, if I hard-code the dates as follows: select - schedule_name, - date(scheduled_start),- time(scheduled_start) as "Scheduled", - time(actual_start) as "Actual", - status as "Status", - node_name as "Client" - from events - where node_name is not null - and scheduled_start between - '2002-01-16 08:01:00' and - '2002-01-17 08:00:59' I get a lengthy listing of all events, as I do from the query event command. I suspect that there is some voodoo happening with the relative date calculation not occurring before the events are restricted to the current date, but I have not been able to come up with a query that works as I would like it to. Any suggestions or pointers on performing date math in SQL queries would be greatly appreciated Thanks, Ted
AW: Events table vs Query events
I asked this question in the past on the list, the answer was basically that the select for events doesn't function like a select, but just like a query. If you add dates in where clauses it works like a query event with dates. Not very chic. Mit freundlichen Grüßen - With best regards Serdeczne pozdrowienia - Slan agus beannacht Paul Baines TSM/ADSM Consultant -Ursprüngliche Nachricht- Von: Alexander Verkooijen [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 13. November 2001 11:29 An: [EMAIL PROTECTED] Betreff: Events table vs Query events Hello, Is there anybody out there who can tell me why a 'select * from events' only gives me today's events and a 'q ev * * begind=-1' also gives me yesterday's events? Where does 'q ev' gets it's information? I can't find this particular problem in the list archive, but I feel I am overlooking something obvious. Regards, Alexander -- --- Alexander Verkooijen([EMAIL PROTECTED]) Senior Systems Programmer SARA High Performance Computing
Re: AW: Events table vs Query events
"Baines, Paul" wrote: > > I asked this question in the past on the list, the answer was basically that > the select for events doesn't function like a select, but just like a query. > If you add dates in where clauses it works like a query event with dates. > Not very chic. Thanks. Using a date in the where clause does work. This is a rather strange implementation of the select command... Thanks again, Alexander -- --- Alexander Verkooijen([EMAIL PROTECTED]) Senior Systems Programmer SARA High Performance Computing
Events table vs Query events
Hello, Is there anybody out there who can tell me why a 'select * from events' only gives me today's events and a 'q ev * * begind=-1' also gives me yesterday's events? Where does 'q ev' gets it's information? I can't find this particular problem in the list archive, but I feel I am overlooking something obvious. Regards, Alexander -- --- Alexander Verkooijen([EMAIL PROTECTED]) Senior Systems Programmer SARA High Performance Computing
select and events table
Hello, is there still a problem in selecting client schedules from the events table from today? I ran select * from EVENTS and it came back with administrative entries only. This is a AIX 4.3.2/TSM 4.1.2.0,and Event Record Retention Period is 10 Days. Regards, -- Horst SCHERZER e-Mail: [EMAIL PROTECTED] Zentraler Informatikdienst Uni Wien Phone: (+43 1) 4277 x14053 Universitaetsstr.7 Fax:(+43 1) 4277 x9140 A-1010 Vienna, Austria URL: http://mailbox.univie.ac.at/~sc begin:vcard n:Scherzer;Horst tel;fax:4277-9140 tel;work:4277-14053 x-mozilla-html:FALSE url:http://mailbox.univie.ac.at/~sc org:Zentraler Informatikdienst Uni-Wien adr:;;Universitaetsstr.7;A-1010 Wien;Oesterreich;; version:2.1 email;internet:[EMAIL PROTECTED] title:Systems Programmer fn:Horst Scherzer end:vcard
Re: SELECT from the EVENTS table doesn't look right.
Paul, You are correct. the design of the SELECT * FROM EVENTS was intended to present only events for today (just like QUERY EVENTS). However, I agree that the design ought to be changed to reflect the SQL standard: that is, SELECT * FROM presents *all* records in that table, not just certain ones. In the case of QUERY EVENTS, you can query events as far back as you want, but the status may be "uncertain" if the events go back further than your event record retention setting. So in my opinion, SELECT * FROM EVENTS should show you all events that are available within the event record retention timeframe. This is a change I am lobbying for with the server developers. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Hello, Can anyone explain the following results to me? tsm: TEST>select count(*) from events Unnamed[1] --- 117 tsm: TEST>select count(*) from events where '08/01/2000' < scheduled_st art Unnamed[1] --- 8507 It seems as if by narrowing down my selection I get more results. This seems to be behaving like a Q EVENTS rather than SQL. Confused of Frankfurt. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
SELECT from the EVENTS table doesn't look right.
Hello, Can anyone explain the following results to me? tsm: TEST>select count(*) from events Unnamed[1] --- 117 tsm: TEST>select count(*) from events where '08/01/2000' < scheduled_st art Unnamed[1] --- 8507 It seems as if by narrowing down my selection I get more results. This seems to be behaving like a Q EVENTS rather than SQL. Confused of Frankfurt. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
Re: Events Table
There is now. Hurray. I can't remember off hand which version of the server delivered it (other than it was very recent) but my 3.7.3.6 servers do have the EVENTS table. Trevor -Original Message- From: Lambelet,Rene,VEVEY,FC-SIL/INF. [mailto:[EMAIL PROTECTED]] Sent: Thursday, 14 September 2000 2:53 AM To: [EMAIL PROTECTED] Subject: Re: Events Table Helas, helas there is no such table to use ! Regards, René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41(021) 924 3543 7 +41 (021) 924 4589 * B 133 Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. > -Original Message- > From: Klein, Robert (CIT) [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, September 13, 2000 5:30 PM > To: [EMAIL PROTECTED] > Subject: Events Table > > I am in the process of converting my tasks which use the query command to > use the select command instead. For the most part this has been > relatively > straighforward but I have not been able to find a table which contains > information corresponding to what is provided by the query events command. > Our server is ADSM 3.1 for MVS. Any pointers as to where such a table > might > be hiding would be greatly appreciated. -- This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. If you have received it by mistake please let us know by reply and then delete it from your system; you should not copy the message or disclose its contents to anyone.
Re: Events Table
The EVENTS table is available in the V3.7 and 4.1 servers. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Helas, helas there is no such table to use ! Regards, Ren é Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41(021) 924 3543 7 +41 (021) 924 4589 * B 133 Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. > -Original Message- > From: Klein, Robert (CIT) [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, September 13, 2000 5:30 PM > To: [EMAIL PROTECTED] > Subject: Events Table > > I am in the process of converting my tasks which use the query command to > use the select command instead. For the most part this has been > relatively > straighforward but I have not been able to find a table which contains > information corresponding to what is provided by the query events command. > Our server is ADSM 3.1 for MVS. Any pointers as to where such a table > might > be hiding would be greatly appreciated.
Re: Events Table
Helas, helas there is no such table to use ! Regards, René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41(021) 924 3543 7 +41 (021) 924 4589 * B 133 Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. > -Original Message- > From: Klein, Robert (CIT) [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, September 13, 2000 5:30 PM > To: [EMAIL PROTECTED] > Subject: Events Table > > I am in the process of converting my tasks which use the query command to > use the select command instead. For the most part this has been > relatively > straighforward but I have not been able to find a table which contains > information corresponding to what is provided by the query events command. > Our server is ADSM 3.1 for MVS. Any pointers as to where such a table > might > be hiding would be greatly appreciated.
Events Table
I am in the process of converting my tasks which use the query command to use the select command instead. For the most part this has been relatively straighforward but I have not been able to find a table which contains information corresponding to what is provided by the query events command. Our server is ADSM 3.1 for MVS. Any pointers as to where such a table might be hiding would be greatly appreciated.
