AW: [ADSM-L] Find what tape a particular backup resides on

If the object_ID is nnn then issue the command: SHOW BFO 0 nnn Which will show you the volume name -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Joni Moyer Gesendet: Mittwoch, 22. März 2006 16:05 An: ADSM-L@VM.MARIST.EDU Betreff: [

AW: [ADSM-L] Lock and unlock TSM client manually

Why not disable sessions ? -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von nghiatd Gesendet: Donnerstag, 16. März 2006 10:32 An: ADSM-L@VM.MARIST.EDU Betreff: [ADSM-L] Lock and unlock TSM client manually Hi all, I want to lock all TSM clie

AW: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Move Node Data from one Policy to another Policy

-L] AW: [ADSM-L] AW: [ADSM-L] Move Node Data from one Policy to another Policy Some more Information to my situation: The client-files are now in a disk-storage pool and not in a sequential-storage-pool Christiane Schaub Joachim Paul ABRAXAS INFORMATIK AG schrieb: >Oh i'm sorry, &

AW: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Move Node Data from one Policy to another Policy

] Move Node Data from one Policy to another Policy Some more Information to my situation: The client-files are now in a disk-storage pool and not in a sequential-storage-pool Christiane Schaub Joachim Paul ABRAXAS INFORMATIK AG schrieb: >Oh i'm sorry, >Puh, you have to go over sequen

AW: [ADSM-L] AW: [ADSM-L] Move Node Data from one Policy to another Policy

tiane Schaub Joachim Paul ABRAXAS INFORMATIK AG schrieb: >In your case, define the sgn_pc as next storage pool by upading the diskpool1 >with: >Upd stg diskpool1 next=sgn_pc > >Then set the migration threshold low: >Upd stg diskpool1 hi=0 lo=0 > > >Regards >joachim

AW: [ADSM-L] Move Node Data from one Policy to another Policy

In your case, define the sgn_pc as next storage pool by upading the diskpool1 with: Upd stg diskpool1 next=sgn_pc Then set the migration threshold low: Upd stg diskpool1 hi=0 lo=0 Regards joachim -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im A

Novell scheduler RC12, datasession still running

Dear list The session sending the data still exists after the aknowledge has done by another session, the scheduler ends with RC 12. No other related messages found in client and server logs. thanks in advance Joachim Environment: TSM Server 5.3.2.1 on Z/OS 1.6 Put 0510+ TSM Client 5.1.6.0 TSANDS

AW: [ADSM-L] Automating server scripts

Simple:Build an admin scheduler with command run script ;-) -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Timothy Hughes Gesendet: Mittwoch, 8. Februar 2006 14:48 An: ADSM-L@VM.MARIST.EDU Betreff: [ADSM-L] Automating server scripts Hel

AW: [ADSM-L] AW: [ADSM-L] Query occupancy for nodes in a policy d omain

ADSM-L] AW: [ADSM-L] Query occupancy for nodes in a policy d omain Joachim, I have tried this, using my domain names for 'mydomain' but I get no match found. Adam -Original Message- From: Schaub Joachim Paul ABRAXAS INFORMATIK AG [mailto:[EMAIL PROTECTED] Sent: 31 January 2

AW: [ADSM-L] Query occupancy for nodes in a policy domain

select node_name, sum (cast(physical_mb as decimal(12,4))) as OCC_MB from occupancy where node_name in (select node_name from nodes where domain_name='mydomain') group by node_name order by occ_mb Regards Joachim -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL P