Yes,
I only see the messages when the ODBC driver is
being used to run SQL queries.
"Large, M (Matthew)" wrote:
> I'm pretty sure these are only issued when the ODBC driver is used to
> run SQL queries on the TSM server.
> We get these every day from ODBC queries:
>
> Date/Time Message
> --------------------
> ----------------------------------------------------------
> 05/30/2006 17:23:56 ANR2017I Administrator ODBC issued command:
> FETCH NEXT 50
> (SESSION: 148454)
> 05/30/2006 17:23:57 ANR2017I Administrator ODBC issued command:
> FETCH NEXT 50
> (SESSION: 148456)
>
> I discovered a command some years ago 'q cursor', and then discovered,
> again, it's to do with ODBC queries.
>
> http://www.tsmwiki.com/tsmwiki <- useful
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Bell, Charles (Chip)
> Sent: 30 May 2006 15:22
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Discovered a new secret command -- anyone know
> what "fetch" does?
>
> He he. I really wish a TSM Developer would write a "TSM Unleashed" book,
> and within its pages somewhere finally documenting all of the
> undocumented commands, explaining each. But I guess that would put some
> out of work, which I certainly am not for. Oh well... <sigh>
>
> Fetch :)
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Robin Sharpe
> Sent: Friday, May 26, 2006 9:17 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Discovered a new secret command -- anyone know what
> "fetch" does?
>
> So, the other day, we replaced two LTO2 drives in our STK L700... new
> WWNs, so had to delete & redefine the drives & paths. I have four
> servers sharing the library, so that's four sets of path definitions...
> to make it easier I wrote up some macros to delete the paths for each
> drive & then define them. Well, due to an editing error, the "de" in
> the first "def path" command got deleted... so the command issued was "f
> path ...".
> TSM
> rejected this in an interesting way (recreated here):
>
> IBM Tivoli Storage Manager
> Command Line Administrative Interface - Version 5, Release 2, Level 0.0
> (c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights
> Reserved.
>
> Session established with server TSM_WAYNE_LM: HP-UX
> Server Version 5, Release 3, Level 2.0
> Server date/time: 05/26/06 22:13:17 Last access: 05/26/06
> 22:13:09
>
> ANS8000I Server command: 'f path'
> ANR2000E Unknown command - FETCH PATH.
> ANS8001I Return code 2.
>
> ANS8002I Highest return code was 2.
>
> TSM expanded the "f" to "FETCH"... I just thought it was amusing...
>
> Robin Sharpe
> Berlex Labs
>
> -----------------------------------------
> Confidentiality Notice:
> The information contained in this email message is privileged and
> confidential information and intended only for the use of the individual
> or entity named in the address. If you are not the intended recipient,
> you are hereby notified that any dissemination, distribution, or copying
> of this information is strictly prohibited. If you received this
> information in error, please notify the sender and delete this
> information from your computer and retain no copies of any of this
> information.
>
> _____________________________________________________________
>
> 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.
> _____________________________________________________________
|
