Howdy,

    There is an APAR opened to address this...  The APAR is IC60909.  The
current target to have this fixed is in the 6.1.2.0 fix pack - with the
usual caveats that this is only the current projected target and this may
be subject to change...

    The intended fix will correct the select processing for the
SYSCAT.COLUMNS and SYSCAT.TABLES tables to only display the tables that
should be selectable through the TSM administrative interface.  Please note
that these results will be either different then or a subset of what would
be displayed if you went directly to DB2 to view the SYSCAT.COLUMNS and
SYSCAT.TABLES.  The reason for this is that the TSM administrative
interface is attempting to preserve (to the degree possible) the tables and
columns that were available for SELECT processing in the prior
version/releases of the product.

    If an administrator were to choose to connect directly to the DB2
database using a supported connection technology (ODBC, JDBC, etc) then
they would be able to see the entire server schema and all the production
tables, views, and such.  The warning in this regard is that this should be
done with care - any connection to the database should be done for READONLY
(SELECT) purposes.  Changes to the schema (DDL), insertion, deletion, or
modification of data in the server database through means other then the
TSM server application may result in the loss of data, a server crash, or a
failure to restart the server.

Thanks,
Colin

-----------------------------------------------------
Colin Dawson
Master Inventor, TSM Server Development Lead
colind AT us.ibm DOT com



  From:       Remco Post <r.post AT PLCS DOT NL>

  To:         ADSM-L AT VM.MARIST DOT EDU

  Date:       05/07/2009 10:10 AM

  Subject:    Re: [ADSM-L] V6 selectable tables question






Richard,

this might be an oversight in development. Just because some of these
tables are pseudo-tables and some are read DB2 tables and some are
real DB2 views and well... a mistake might have been made.... Colin or
another IBM person will probable agree with me that this will need to
be fixed and ask you to open a call with IBM support.

On May 7, 2009, at 18:32 , Cowen, Richard wrote:

> Some tables that are selectable seem to not have syscat.columns
> entries.
>
> processes
> status
> paths
> mgmtclasses
> cloptsets
> clientopts
> scripts
> stgspacetrigger
> collocgroup
> datamovers
> disks
> drmsrpf
> group_member
> spcmgfiles
>
> So I can do a
> SELECT * FROM MGMTCLASSES
> successfully, but not a
> SELECT COLNAME FROM SYSCAT.COLUMNS WHERE TABNAME='MGMTCLASSES'
>
> I know there are some "view" tables (nodes, filespaces), and some
> related tables MANAGEMENT_CLASSES, but how do you get the column names
> for the tables listed above?  (besides doing a full select on the
> table.)
>
> ANS8000I Server command: 'select * from mgmtclasses'
>     DOMAIN_NAME: STANDARD
>        SET_NAME: ACTIVE
>      CLASS_NAME: STANDARD
>       DEFAULTMC: No
>     DESCRIPTION: Installed default management class.
> SPACEMGTECHNIQUE: NONE
>   AUTOMIGNONUSE: 0
> MIGREQUIRESBKUP: YES
>  MIGDESTINATION: SPACEMGPOOL
>        CHG_TIME: 2009-05-01 15:53:33.000000
>       CHG_ADMIN: SERVER_CONSOLE
>         PROFILE:
>
> ANS8000I Server command: 'select colname from syscat.columns where
> tabname='MGMTCLASSES'
> ANR2034E SELECT: No match found using this criteria.
> ANS8001I Return code 11.
>
> ANS8000I Server command: 'select colname from syscat.columns where
> tabname='MANAGEMENT_CLASSES''
> COLNAME: DOMAINNAME
> COLNAME: SETNAME
> COLNAME: MCNAME
> COLNAME: MCID
> COLNAME: MC_DESCR
> COLNAME: UPDATE_DATE
> COLNAME: UPDATOR
> COLNAME: SPACEMGMT_TECHNIQUE
> COLNAME: AUTOMIGINUSE
> COLNAME: MIGREQBKUP
> COLNAME: MIGDEST
> COLNAME: CHG_PENDING
>
> Thanks.
>
>
>
> The information contained in this transmission may contain
> privileged and confidential information.
> It is intended only for the use of the person(s) named above. If you
> are not the intended
> recipient, you are hereby notified that any review, dissemination,
> distribution or
> duplication of this communication is strictly prohibited. If you are
> not the intended recipient,
> please contact the sender by reply email and destroy all copies of
> the original message.
> To reply to our email administrator directly, please send an email
> to postmaster AT sbsplanet DOT com.

--
Met vriendelijke groeten,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622