Thank you very much for information. I have upgraded our test server from TSM 6.1.1 to TSM 6.1.2 successfully. I have created scripts by scripts.smp as well. I do not think that everything is fine in 6.1.2. I couldn't explain next error message: =================================================================== tsm: BKME>run Q_COLUMNS activity_summary
activity_summary column --------------------------------------------------------------------------------------------------------------------------------- ACTIVITY ACTIVITY_NUM BYTES_AFFECTED COMM_ADDR COMM_METH COMM_WAIT_TIME DRIVE_NAME END_TIME IDLE_SECONDS LIBRARY_NAME MEDIAW_SECONDS MOUNT_INT_USE MOUNT_NAME OBJECTS_AFFECTED OBJECTS_EXAMINED OBJECTS_FAILED OWNER RETURN_CODE SCHEDULE START_TIME THREADS_USED UNIQUE ANR1462I RUN: Command script Q_COLUMNS completed successfully. tsm: BKME>select SCHEDULE,START_TIME,RETURN_CODE from activity_summary ANR0162W Supplemental database diagnostic information: -1:42S22:-206 ([IBM][CLI Driver][DB2/AIX64] SQL0206N "SCHEDULE" is not valid in the context where it is used. SQLSTATE=42703). ANR2940E The command 'select SCHEDULE , START_TIME , RETURN_CODE from SUMMARY ' contains an unknown SQL column name. ANS8001I Return code 3. tsm: BKME> It gives the same error, if table SUMMARY is used. By the way it is impossible to list columns for SUMMARY. Regards, Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: [email protected] Please consider the environment before printing this Email -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Joerg Pohlmann Sent: Wednesday, August 12, 2009 11:53 PM To: [email protected] Subject: Re: [ADSM-L] V6.1.2.0 server has arrived Note to development - thanks for putting the updated 6.1.2.0 ITM Reporting function in the maintenance directory of the ftp site. This way many more people can start experimenting with the Tivoli Common Reporting function. I have just upgraded my Windows TSM server to 6.1.2.0 - very successful, clean upgrade. A bunch of the schema changes took place which I interpret to be an equivalent of UPGRADEDB. I also re-installed scripts.smp. I have some questions about the tables in TSM 6.1.2.0 . The Q_TABLES script now produced nice, concise output. If I compare the Q_TABLES script output from v5 to v6, the following tables do not show up in the v6 output: AUDITOCC CLIENTOPTS CLOPTSETS COLLOCGROUP DATAMOVERS DOMAINS DRMEDIA DRMMACHINE DRMMACHINECHARS DRMMACHINENODE DRMMACHINERECINST DRMMACHINERECMEDIA DRMRECOVERYMEDIA DRMSRPF DRMSTANZA DRMTRPF LICENSE_DETAILS LOG MGMTCLASSES PATHS PROCESSES PROFILES RECLAIM_ANALYSIS RESTORES SCRIPT_NAMES SHREDSTATUS STATUS STGSPACETRIGGER SUBSCRIPTIONS VFSMAPPINGS SUMMARY seems to have become ACTIVITY_SUMMARY SERVER_GROUP has become SERVERGROUP Even though these tables in the list don't show up in the output of run Q_TABLES, they seem to exist. For example, select * from drmedia works fine. Since I operate TSM environments, I am particularly interested in the DRMEDIA table to get a quick summary status of DR tapes, so a long time ago I created a script called drmstate which contains select state, count(*) as TAPES from drmedia group by state select state, volume_name, voltype from drmedia order by state, volume_name Both select statements fail on v6: tsm: VISTA1>ru drmstate5 ANR2944E The reference 'SELECT' is an unknown SQL scalar function name. | V.............................................................. select state , count ( * ) as TAPES from drmedia group by state ANR2944E The reference 'ORDER' is an unknown SQL scalar function name. | ..................................................V............ select state , volume_name , voltype from drmedia order by stat ANR1463E RUN: Command script DRMSTATE5 completed in error. ANS8001I Return code 3. I ended up having to use where clauses: tsm: VISTA1>q scr drmstate f=r select count(*) as vaultretrieve from drmedia where state='VAULTRETRIEVE' select count(*) as mountable from drmedia where state='MOUNTABLE' select count(*) as vault from drmedia where state='VAULT' select count(*) as courier from drmedia where state='COURIER' select count(*) as courierretrieve from drmedia where state='COURIERRETRIEVE select state,volume_name,voltype from drmedia where state='VAULTRETRIEVE' select state,volume_name,voltype from drmedia where state='MOUNTABLE' select state,volume_name,voltype from drmedia where state='VAULT' select state,volume_name,voltype from drmedia where state='COURIER' select state,volume_name,voltype from drmedia where state='COURIERRETRIEVE' If anyone has any ideas on how to make this new level of functionality a bit more elegant, I would appreciate hearing about it. Thanks. Joerg Pohlmann 250-245-9863 "ADSM: Dist Stor Manager" <[email protected]> wrote on 2009-08-12 09:09:08: > Hi All, > > The README's for server fix-pack 6.1.2.0 are delayed by a few days... > We expect they will be available on Friday 8/14. > > Thanks, > Colin > > ----------------------------------------------------- > Colin Dawson > TSM Server Development > [email protected] > > > > From: Zoltan Forray/AC/VCU <[email protected]> > > To: [email protected] > > Date: 08/12/2009 06:48 AM > > Subject: Re: [ADSM-L] V6.1.2.0 server has arrived > > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > > > > > > Yeah, some readme's would be nice. I guess they will get around to posting > the page, soon. > > I just installed it and the README.html file that appears points to pages > that don't exist. > > > > From: > Timothy Hughes <[email protected]> > To: > [email protected] > Date: > 08/12/2009 07:53 AM > Subject: > Re: [ADSM-L] V6.1.2.0 server has arrived > Sent by: > "ADSM: Dist Stor Manager" <[email protected]> > > > > Are Backup Sets enabled? I can't find any readme information > > regards > > Zoltan Forray/AC/VCU wrote: > > >In case folks haven't noticed................... > > > >Look under the "Maintenance" folder on the FTP site > >service.boulder.ibm.com, i.e. > >/storage/tivoli-storage-management/maintenance/server/v6r1/Linux/6.1.2.0 > > > >Here's hoping we can finally start to use V6.1 as a production server. > > > > Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
