Query actlog
Hi, Is there a way to associate multiple criterias on a query actlog search= Pierre
Re: Query actlog
If by multiple criteria you mean specifying, for example, multiple MSGNO parameters, then the answer is no. As an alternative, you can use SELECT with the ACTLOG table to do that type of query. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.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 ADSM-L@VM.MARIST.EDU wrote on 10/11/2007 01:55:54 AM: Hi, Is there a way to associate multiple criterias on a query actlog search= Pierre
Re: Query actlog
Q ACTLOG can be searched using MSGno, Search string, nodename, client or server originated messages, by domain/sched/session... If you wish to search by multiple strings, I think it is better to dump it to a file and play around using your string handling capabilities... Cheers, Rama -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Thursday, October 11, 2007 7:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Query actlog If by multiple criteria you mean specifying, for example, multiple MSGNO parameters, then the answer is no. As an alternative, you can use SELECT with the ACTLOG table to do that type of query. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan ager.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 ADSM-L@VM.MARIST.EDU wrote on 10/11/2007 01:55:54 AM: Hi, Is there a way to associate multiple criterias on a query actlog search= Pierre This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: Query actlog
Thanks everybody -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Choudarapu, Ramakrishna (GTI) Envoyé : jeudi 11 octobre 2007 14:16 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Query actlog Q ACTLOG can be searched using MSGno, Search string, nodename, client or server originated messages, by domain/sched/session... If you wish to search by multiple strings, I think it is better to dump it to a file and play around using your string handling capabilities... Cheers, Rama -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Thursday, October 11, 2007 7:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Query actlog If by multiple criteria you mean specifying, for example, multiple MSGNO parameters, then the answer is no. As an alternative, you can use SELECT with the ACTLOG table to do that type of query. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoli StorageMan ager.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 ADSM-L@VM.MARIST.EDU wrote on 10/11/2007 01:55:54 AM: Hi, Is there a way to associate multiple criterias on a query actlog search= Pierre This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
select from actlog VS query actlog performance
Hello TSM'ers I'm doing some scripting that is using actlog queries fairly heavily, I have noticed that Select * from actlog where cast(date_time as date)=current_date and process=1234 Is a lot slower than Q actlog begint=-08:00 se=1234 (say, its 8am in the morning...) Although you need to be carefull you are actually getting what you want with the latter version. Is TSM doing anything internally to generate a SQL statement that works quicker than mine but gives the same/similar result? - I am assuming that internally TSM takes q actlog (and other q commands) and generates a SQL statement it then processes against the TSM DB, formatting the result to generate the query output as non-tables. Thanks, Matt. ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: select from actlog VS query actlog performance
Rather the other way round. The SQL is being converted to a native database call. I would presume most query commands would be quicker than their equivalent SQL queries. For tuning SQL queries you can look at the indexing of the columns in a table: select tabname, colname, colno, index_keyseq, index_order from columns where tabname='ACTLOG' TABNAME COLNAME COLNO INDEX_KEYSEQ INDEX_ORDER -- -- -- --- ACTLOG DATE_TIME 1 1 A ACTLOG MSGNO 2 ACTLOG SEVERITY 3 ACTLOG MESSAGE 4 ACTLOG ORIGINATOR5 ACTLOG NODENAME 6 ACTLOG OWNERNAME 7 ACTLOG SCHEDNAME 8 ACTLOG DOMAINNAME9 ACTLOG SESSID 10 ACTLOG SERVERNAME 11 Here you can see it is only indexed on DATE_TIME. Other tables have more indexed columns. Running functions on where clause columns may well cause the query to do a full table scan anyway (not using the index.) but that's just a guess. (I notice that you are using process=1234 in your where clause, so maybe you have a later release of TSM, I'm on 5.1 and don't have that column!) Remember as well that SQL queries use the free space in your database, so make sure you have plenty if you're doing big queries. Paul. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Warren, Matthew (Retail) Sent: Friday 19 November 2004 15:55 To: [EMAIL PROTECTED] Subject: select from actlog VS query actlog performance Hello TSM'ers I'm doing some scripting that is using actlog queries fairly heavily, I have noticed that Select * from actlog where cast(date_time as date)=current_date and process=1234 Is a lot slower than Q actlog begint=-08:00 se=1234 (say, its 8am in the morning...) Although you need to be carefull you are actually getting what you want with the latter version. Is TSM doing anything internally to generate a SQL statement that works quicker than mine but gives the same/similar result? - I am assuming that internally TSM takes q actlog (and other q commands) and generates a SQL statement it then processes against the TSM DB, formatting the result to generate the query output as non-tables. Thanks, Matt. ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432 Any e-mail message from the European Central Bank (ECB) is sent in good faith but shall neither be binding nor construed as constituting a commitment by the ECB except where provided for in a written agreement. This e-mail is intended only for the use of the recipient(s) named above. Any unauthorised disclosure, use or dissemination, either in whole or in part, is prohibited. If you have received this e-mail in error, please notify the sender immediately via e-mail and delete this e-mail from your system.
Re: select from actlog VS query actlog performance
BEGINT=-08:00 starts searching the activity log as of 8 hours from the present time (as opposed to the default, which is 1 hour from the present time). Leave out the '-' if you really mean 08:00 (8:00 AM). The raw TSM server database tables are not row-column format, but more like a B-tree, and were not originally designed to support SQL. The only methods for interrogating the database were those provided by the QUERY commands (QUERY ACTLOG, QUERY FILESPACE, etc.). The QUERY commands are optimized for accessing the raw tables of the TSM database, and thus perform quite well. Because customers wanted more query flexibility than what the TSM server already provided, and creating individual QUERY commands for each possible query was not practical (effectively an unbounded list), the SQL interface was created. The tables presented by the SQL interface are not those of the raw internal TSM tables; rather, they are virtualized versions of the internal tables that are created dynamically when you run the SELECT command (hence the need for available space in the database to run SELECT). While SELECT gives you more flexibility in the types of queries you can run, those queries tend to run more slowly. 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] 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 [EMAIL PROTECTED] wrote on 11/19/2004 07:55:02: Hello TSM'ers I'm doing some scripting that is using actlog queries fairly heavily, I have noticed that Select * from actlog where cast(date_time as date)=current_date and process=1234 Is a lot slower than Q actlog begint=-08:00 se=1234 (say, its 8am in the morning...) Although you need to be carefull you are actually getting what you want with the latter version. Is TSM doing anything internally to generate a SQL statement that works quicker than mine but gives the same/similar result? - I am assuming that internally TSM takes q actlog (and other q commands) and generates a SQL statement it then processes against the TSM DB, formatting the result to generate the query output as non-tables. Thanks, Matt. ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
