• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TSM commands help


why the backup is failed with maximum number of mountpoint when running the backup in inc -absolute? backup is completed when on scheduled run but failed with maxnump when running inc -absolute?

can you clear for me the ff?

  1. is there a limit in max nump? can i edit it to any number?
update node <nodename> maxnummp=<value>

2. if i edit this, is there any other backup that will affected by this?

Could you please explain what exactly you mean with "rerun" a backup ? How do you initiate this ?

You have to understand that "q event" command will only return information about scheduled backups (means there must be a schedule defined in TSM server, and this schedule has to be associated with some client node existing on he TSM server. To find these, try following commands : "q sched * * f=d" and "q assoc * *").
Thus, if you did not make use of a schedule to initiate your backup "rerun", the command will not provide any information.
Note as well, that you might use "q event * * f=d" to get details on the start and end time for a given backup schedule.

For your information, there's a table in TSM database, named "summary", which, you guessed it, is summarizing most of the operations executed on the TSM server. This includes of course backup as well as archive operations.
It is possible to execute SQL queries against this table, to extract the information you're needing.
Following example would provide you with backup/archive activity for each node during the last 24 hours :

SELECT entity as "NODE", number as "SESSION", activity, -
TO_CHAR(CHAR(start_time),'YYYY-MM-DD HH24:MI:SS') as START_TIME, -
TRANSLATE('a bc:de:fg', DIGITS(end_time-start_time), '_______abcdefgh_____',' ') as "ELAPTIME (D HHMMSS)", -
CAST(bytes/1024/1024 AS DECIMAL(8,2)) as "MB", -
CAST(bytes/TIMESTAMPDIFF(2,CHAR(end_time-start_time))/1024/1024 AS DECIMAL(8,2)) AS "MB/s" -
FROM summary WHERE ( activity='ARCHIVE' OR activity='BACKUP' ) AND -
start_time>=current_timestamp - 24 hours

You just have to copy-paste the whole text (exactly as is) into TSM server command line interface to get the data !


After running the above said select command i got the error:
tsm: PORUA019S1>SELECT entity as "NODE", number as "SESSION", activity, -
cont> TO_CHAR(CHAR(start_time),'YYYY-MM-DD HH24:MI:SS') as START_TIME, -
cont> TRANSLATE('a bc:de:fg', DIGITS(end_time-start_time), '_______abcdefgh_____',' ') as "ELAPTIME (D HHMMSS)", -
cont> CAST(bytes/1024/1024 AS DECIMAL(8,2)) as "MB", -
cont> CAST(bytes/TIMESTAMPDIFF(2,CHAR(end_time-start_time))/1024/1024 AS DECIMAL(8,2)) AS "MB/s" -
cont> FROM summary WHERE ( activity='ARCHIVE' OR activity='BACKUP' ) AND -
cont> start_time>=current_timestamp - 24 hours
ANR2944E The reference 'TO_CHAR' is an unknown SQL scalar function name.

er as "SESSION" , activity, TO_CHAR(CHAR(start_time), 'YYYY-MM-

ANS8001I Return code 3.

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 59 60.8%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.4%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Latest member