Results 1 to 8 of 8
  1. #1
    Newcomer
    Join Date
    Apr 2008
    Posts
    9
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Paths table in TSM 6.1 database

    Hi,

    I see that there now isn't a paths table in the TSM DB in 6.1. Does anyone know where in the DB path information is? I'm looking to create a sql script to look up path online/offline status and can't find where I should be querying!

    Thanks

  2. #2
    Member
    Join Date
    Apr 2005
    Posts
    5
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Select * from paths still works on TSM 6.1.2.0?

  3. #3
    Newcomer
    Join Date
    Apr 2008
    Posts
    9
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Yep, it does indeed work within TSM command line, but trying it from DB2 command line returns table unknown:

    db2 => select * from tsmdb1.paths
    SQL0204N "TSMDB1.PATHS" is an undefined name. SQLSTATE=42704

    I can't see it listed as a table or a view anywhere.

    I need to access the DB2 data directly for reports / monitoring, but I can't find where the paths data is stored in the DB.

    Thanks

  4. #4
    Member
    Join Date
    Jul 2008
    Posts
    286
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Default

    i don't install tsm 6.1 but this command running without error ?
    select * from paths

  5. #5
    Newcomer
    Join Date
    Apr 2008
    Posts
    9
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Yep, select * from paths works from the 6.1 command line, and the database table/view does exist in TSM 5.5 and below, so that's all fine.

    I'm looking for how to access this data direct from the TSM 6.1 DB2 database - as far as I can see I don't have a DB2 table or view called paths, which is confusing the life out of me.

    I can query from the TSM command line, so it's obviously being stored somewhere... Even searching syscat.columns for any of the column names referenced in the select * from paths output returns nothing.

  6. #6
    Member
    Join Date
    Jul 2008
    Posts
    286
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Default

    i used this command :
    select library_name,destination_name,source_name,device,d irectory,online,destination_type,source_type from paths

  7. #7
    Newcomer
    Join Date
    Apr 2008
    Posts
    9
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    It's the "from paths" bit that I have trouble with - "paths" is not recognised as a table or view name when querying direct from DB2 command line.

    Works fine from TSM command line, which is the confusing part.


    Quote Originally Posted by Samuel View Post
    i used this command :
    select library_name,destination_name,source_name,device,d irectory,online,destination_type,source_type from paths

  8. #8
    Member
    Join Date
    Apr 2009
    Posts
    41
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Quote Originally Posted by mjp81 View Post
    It's the "from paths" bit that I have trouble with - "paths" is not recognised as a table or view name when querying direct from DB2 command line.

    Works fine from TSM command line, which is the confusing part.
    The SQL schema presented by the TSM SELECT command has always been a virtual schema, completely separate from the underlying database schema. This was true in 5.x and is stil true in 6.1. It's just easier to see what the underlying database schema is in 6.1 now that you can bypass TSM and go directly to DB2.

    The table names presented in the TSM command line typically correspond to the objects you can define in TSM... NODES, ADMINS, DEVCLASSES, PATHS, etc.. The underlying implementation may use similar table names, or completely different names. There are even a few 'tables' available via TSM's SELECT that have no presence in the underlying database at all.... OPTIONS being the typical example of this.

    All of which just goes to explain why there's a difference between what you see on the TSM command line and what is presented to you by DB2. The other thing to keep in mind is that the TSM SQL interface as seen from the TSM command line is a supported external interface. The database schema as seen from DB2 is not. The underlying database schema is the internal implementation used by TSM, and can change without notice. So if you have a dependency on the data you're trying to find, you should use the TSM SQL interface instead of DB2's.

    Now, with all these caveats in mind ... look at the NA_PATH table...
    Last edited by kehannigan; 11-10-2009 at 05:26 PM.
    --Ken Hannigan
    Tivoli Storage Manager Server Development

Similar Threads

  1. TEP - TSM Drive Paths
    By ChrisRees in forum TSM Reporting & Monitoring
    Replies: 12
    Last Post: 09-25-2009, 06:07 AM
  2. Paths on TSm changing by themselves?
    By spiffy in forum Tape / Media Library
    Replies: 4
    Last Post: 10-30-2008, 01:13 PM
  3. TS3500, TSM on AIX and Control paths
    By Stephan in forum TSM Server
    Replies: 8
    Last Post: 10-09-2008, 02:42 PM
  4. Need to Join Nodes table and Occupancy table
    By PierCed_3 in forum TSM Reporting & Monitoring
    Replies: 1
    Last Post: 05-01-2008, 07:00 PM
  5. drive WWN and TSM database table
    By denisl in forum Tape / Media Library
    Replies: 4
    Last Post: 05-24-2007, 10:52 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •