3583 lto library

2002-01-03 Thread Burak Demircan

Hi,
I have 2 "3583" library with "3580 LTO" drives on them. I am
confused about firmwares.  Do firmwares coming with "appcode.exe"
include FMR firmwares for the drives or do they include only library firmware?

I can easily update library firmare with serial cable as "download -C1 
-FVn_n_n.lif"
but I have trouble with drive FMR update for drives. I am using AIX 4.3.3 and 
all manuals
explain how to update drive FMRs with "ntutil". How about AIX?
Regards,
Burak


offsite backup

2002-01-03 Thread Burak Demircan

Hi,
Can you give me some hints about offsite backup automation? Can anybody
send me some schedule samples to automate offsite backups?
Best Regards,
Burak


Re: Memory Tuning For AIX

2002-01-03 Thread Joel Fuhrman

Chris -  tapas is part of which fileset and in which directory does it
reside?

On Thu, 3 Jan 2002, Chris Gibes wrote:

> There is a better tool. It was introduced in AIX 4.3.2 and it's called
> topas (it's very similiar to "monitor" or "top") Simply enter "topas" at
> the AIX command prompt. As to the problem, if the system is really paging,
> it's most likely your bufpool is set too high. I would try lowering your
> bufpool size. If that helps, then don't increase your bufpool until after
> you get more memory. Topas will allow you to see hot processes, disks,
> adapters and paging all at the same time, which will make it much easier to
> figure what process is monopolizing your resources.
>
> Good Luck
>
>
> At 07:02 AM 1/3/02 -0500, you wrote:
> >I think the wide range of answers as to what this output means is a good
> >indication that IBM would do well to develop a more concise tool for
> >reviewing resource utilization.  As for my opinion I would start with
> >'vmtune' and then look at 'iostat'.  Good Luck
> >
> >Thanks,
> >Jon Martin
> >
> >-Original Message-
> >From: Denis L'Huillier [mailto:[EMAIL PROTECTED]]
> >Sent: Wednesday, January 02, 2002 1:34 PM
> >To: [EMAIL PROTECTED]
> >Subject: Memory Tuning For AIX
> >
> >
> >Hello-
> >I am having a memory problem.
> >I am runnning AIX 4.3.2 on a H50.  TSM is the only application
> >running on the server.  When I run vmstat I get the following...
> >
> >kthr memory page  faultscpu
> >- ---   ---
> >  r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
> >  0  0 136233   202   0   3   2  99  210   0  52  240  66 17 30 16 37
> >  1  3 136234   342   0  38  11 3727 4204   0 1322 6136 4665 12 11  3 74
> >  2  3 136236   160   0  44  12 3728 5326   0 1324 5844 4644 10 11  2 76
> >  1  3 136237   295   0  17  19 4113 5725   0 1305 7174 5091 13 10  3 74
> >  0  3 136237   629   0  19   9 4240 7442   0 1316 7200 5082 14 13  5 68
> >
> >Does this look normal to anyone?  From my limited understanding of vmstat
> >it looks like:
> >CPU utilization is maxed out
> >I have blocked processes (the b column)
> >The scan rate (sr) column is very high.
> >The server has 1Gig of memory.  I'm really not sure how to tell how much is
> >allocated to
> >the OS and how much is allocated to TSM.  Does anyone have any ideas or
> >pointers is
> >tuning memory for AIX?  Do I need a memory upgrade?
> >I started checking this because my server response is horrible.
> >Thanks.
> >Denis
>
> Chris Gibes <[EMAIL PROTECTED]>
> Tivoli Certified Consultant
> IBM Certified System Administrator
> Berbee- Milwaukee Branch
> (262) 521-5616
>
>
> Berbee...putting the E in business
>



Re: FILESPACE_NAME vs. HL_NAME

2002-01-03 Thread Thomas A. La Porte

Are these by any chance NFS mounted directories? We do a lot of
archives with loopback-mounted filesystems, and over the course
of multiple iterations of the dsmc client we have found that
ADSM/TSM have treated these filesystems differently wrt to what
is FILESPACE_NAME and what is HL_NAME.

The proper way to find these files with a 'dsmc q arch' or
'dsmc retr' is to explicitly name the filespace in your filespec.

So, in your example, you have a single file which has been
archived under three different filespace names. Assuming you were
looking to retrieve the version of the file archived on
2001-12-22, you would issue the following command:

dsmc retr '{/WORK/DATA}/MARTINE/BS0266'

If you do not specify the filespace in your filespec, ADSM/TSM
will use the filespace that has the *longest* match, e.g., in
your case by default it will always find the version archived on
2001-11-20.

 -- Tom

Thomas A. La Porte
DreamWorks SKG
[EMAIL PROTECTED]

On 01/02/2002 Mike Crawford wrote:

>Good Afternoon,
>
>A client is having trouble locating archived files using dsmc q ar.  The
>problem
>seems to be that the filespace_name and hl_names differ between the files,
>even
>though they were archived from the same place.
>
>Server: AIX, ADSM v3.1
>Client: SunOS, ADSM v3.1
>
>An example:
>select filespace_name,hl_name,ll_name,archive_date from archives where
>node_name='HUBER'
>and ll_name='BS0266'
>
>
>FILESPACE_NAME: /WORK
>   HL_NAME: /DATA/MARTINE/
>   LL_NAME: BS0266
>  ARCHIVE_DATE: 2001-12-22 10:46:30.00
>
>FILESPACE_NAME: /WORK/DATA
>   HL_NAME: /MARTINE/
>   LL_NAME: BS0266
>  ARCHIVE_DATE: 2001-12-22 10:41:24.00
>
>FILESPACE_NAME: /WORK/DATA/MARTINE
>   HL_NAME: /
>   LL_NAME: BS0266
>  ARCHIVE_DATE: 2001-11-20 05:38:10.00
>
>
>Depending on how the client specifies the request, they will get a
>different
>version of the file.
>
>The question is, how does ADSM determine which part of the path is
>considered
>filespace_name, and which is hl_name?
>
>Thanks,
>Mike
>
>



Re: 3590 Tapes.

2002-01-03 Thread Zlatko Krastev/ACIT

(1) is an option but time consuming (3200 tapes!)
(2) might not be an option - it depends how paranoic you are. If someone
(usually a virus) fills sector 0 on a PC disk with garbage this does not
automatically mean the data is lost. But it might take too much efforts. If
the tapes are not degaused there is a chance that reading them might
uncover somehow at least some files (especially large ones occupy large
continuous blocks on the tape). And if you are very, very paranoic ...

Zlatko Krastev
IT Consultant





"Joshua S. Bassi" <[EMAIL PROTECTED]> on 03.01.2002 20:29:59
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: 3590 Tapes.

There are several ways to do this:

1) Use another backup utility to write over the tape.  You can use tar,
cpio, NT backup, or whatever to write over either the whole tape or
merely the TSM label.

2) Just do # 1 above to the TSM DB backups since the remaining tapes are
useless without the DB backup.

3) Relabel the tapes using TSM - this could be the easiest if you no
longer want any of the data in the tape library.


--
Joshua S. Bassi
Independent Consultant & IBM Server/Storage Sales Rep.
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Michael, Monte
Sent: Thursday, January 03, 2002 7:34 AM
To: [EMAIL PROTECTED]
Subject: 3590 Tapes.

I am currently in the process of replacing all of my 3590 tapes in my
ATL
with new 3590 EXTENDED length cartridges.  I have a buyer for the 3200
3590
tapes I am removing from TSM/ATL.  How do I go about making sure all
data
has been erased from the old 3590 cartridges?  It is my understanding
that
these tapes can not be degaussed.   Has anyone ran into this situation
before?

Thank You...



Re: FILESPACE_NAME vs. HL_NAME

2002-01-03 Thread Zlatko Krastev/ACIT

Be aware that the "filesystem" is not equal to "all directories and files
under the mount point tree"!
So continuing with your example and assuming we have filesystems /work,
/work/data and /work/data/martine:
a file /work/dummy_file will give us FILESPACE_NAME='/work', HL_NAME='/',
LL_NAME='dummy_file'
/work/tmp/~12345--> FILESPACE_NAME='/work', HL_NAME='/tmp',
LL_NAME='~12345'
/work/data/~12345   --> FILESPACE_NAME='/work/data', HL_NAME='/',
LL_NAME='~12345'
/work/data/garbage/empty--> FILESPACE_NAME='/work/data',
HL_NAME='/garbage', LL_NAME='empty'
.., etc.
Under *NORMAL* circumstances /work filesystem DOES NOT have files under
/work/data directory. Same for files under /work/data/martine in /work/data
filesystem.
But what if (just imagine, it is possible):
- There are *really* three distinct file versions residing in three
filesystems, i.e. three different files (!) with same path
- the query points that this is archives of the file, not backups. And last
two versions are made within five minutes (!)
So my guess is that the user(s) have been working with this file tree for a
long time, sometimes with one filesystem mounted, sometimes two or all
three. As a result he/she(they) got (up to) three copies of the file(s).
And whilst first archive can be assumed regular, most probably the last two
were made with the intention to archive both - look at 5 minutes interval.
This might happen if an application writes the file automatically
(re)creating the missing path. And the filename (LL_NAME) also may lead to
such conclusion.


Zlatko Krastev
IT Consultant






"Martin, Jon R." <[EMAIL PROTECTED]> on 03.01.2002 14:09:40
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: FILESPACE_NAME vs. HL_NAME

Along thos same lines maybe if there are three file systems with the
following naming conventions

/work
/work/data
/work/data/martine

Would TSM back up each of these filesystems separately thus giving you
three
different file names?

Thanks,
Jon Martin

-Original Message-
From: Vo An Nguyen/Quebec/IBM [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 02, 2002 5:01 PM
To: [EMAIL PROTECTED]
Subject: Re: FILESPACE_NAME vs. HL_NAME


Hello Mike,

In UNIX, a filespace for ADSM is a filesystem. So in this case,
it looks like the /work is the filespace unless you have mapped
a directory like /work/data as a nfs at the time of the backup or
perhaps you have used the client option virtualmountpoint.
Hope this helps.

Regards,

Vo An Nguyen
Email: [EMAIL PROTECTED]



Mike Crawford <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/02/2002
04:11:23 PM

Please respond to [EMAIL PROTECTED]

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:
Subject:  FILESPACE_NAME vs. HL_NAME


Good Afternoon,

A client is having trouble locating archived files using dsmc q ar.  The
problem
seems to be that the filespace_name and hl_names differ between the files,
even
though they were archived from the same place.

Server: AIX, ADSM v3.1
Client: SunOS, ADSM v3.1

An example:
select filespace_name,hl_name,ll_name,archive_date from archives where
node_name='HUBER'
and ll_name='BS0266'


FILESPACE_NAME: /WORK
   HL_NAME: /DATA/MARTINE/
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:46:30.00

FILESPACE_NAME: /WORK/DATA
   HL_NAME: /MARTINE/
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:41:24.00

FILESPACE_NAME: /WORK/DATA/MARTINE
   HL_NAME: /
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-11-20 05:38:10.00


Depending on how the client specifies the request, they will get a
different
version of the file.

The question is, how does ADSM determine which part of the path is
considered
filespace_name, and which is hl_name?

Thanks,
Mike



Re: moving data between pools

2002-01-03 Thread Zlatko Krastev/ACIT

Or just the opposite - a volume with data checked in as scratch, tried to
be used and (auto)changed by TSM to private to prevent scratch volumes
allocation become blocked.

Zlatko Krastev
IT Consultant





Doug Thorneycroft <[EMAIL PROTECTED]> on 03.01.2002 00:08:56
Please respond to "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: moving data between pools

If the volume is a database backup, Export, or scratch tape that was
checked in as
private, it will not show using a q vol. Check your volume history file to
see if it shows
up there.

-Original Message-
From:   Marc Levitan [SMTP:[EMAIL PROTECTED]]
Sent:   Wednesday, January 02, 2002 12:56 PM
To: [EMAIL PROTECTED]
Subject:moving data between pools

Hi All-

I have a Magstar tape library that I am phasing out.  I only have a couple
of tapes left with data.
I have an existing StorageTek 9740 tape library that i would like to use
exclusively.

When I do a Q libv I get:

Library Name   Volume Name   Status   OwnerLast UseHome
Element
   ---   --   --   -

MAGSTAR03F9A8Private   32
MAGSTAR063D56Private   33
TEKWOLF03Private   Data66
TEKWOLF04Private   Data73
TEKWOLF05Private   Data163
TEKWOLF06Private   Data290
etc...

But, when I look in the web gui I can only see the 063D56  volume and NOT
the 03F9A8 volume???  Why would this be?  It is a copy pool volume.
(I can see all of the TEKWOLF volumes.)

So, I am trying to move the data to a tape in my StorageTek library, but
apparently you cannot move data from a copy pool to any other pool!

Does anyone know if there is a way to move this data?
And how come the other tape volume (03F9A8) doesn't show in my web gui?

TSM 3.7.4
AIX 4.3.3
Thanks!
Marc Levitan
Storage Manager
PFPC Global Fund Services



Re: backup file list

2002-01-03 Thread Charles Anderson

I've got this SQL statement for backup, archive and restore stats.

"select activity,sum(bytes)/1048576*.001 from summary where activity in 
('BACKUP','ARCHIVE','RESTORE') and start_tim>TIMESTAMP(CURRENT_DATE -1 DAY, 
'08:00:00') group by activity order by 1"

I'm guessing that was at least partially a script that came with the server, as I 
don't usually write such in depth SQL.

As for your backup files lists I can only tell you what we're doing.  That's looking 
for files that had some sort of error state. Query the actlog ( I get the previous 24 
hours every morning at 08:00 and get the scripts to look through it for various things 
) and grep for the following codes. 
ANE4987E ( Files that were in use at backup time )
ANE4007E ( Files which TSM was denied accesss to )
ANE4005E ( Files that have probably been deleted )

Well, hope that helps, it should at least keep you busy for a while ;-)

-
Ed Anderson
[EMAIL PROTECTED]




>>> [EMAIL PROTECTED] 12/20/01 23:24 PM >>>
Does anyone have a query that will tell me the backup file lists 
and the average amount of data transmitted a day?

CD DATA CORP. IDC TEAM. KIM IN YOP
14th Floor,Sam Jung Bldg.
237-11,Nonhyun-Dong,Gangnam-Gu,
Seoul,Korea 135-831
TEL: 82-2-546-3108
MOBILE: 016 9770-2032
FAX: 82-2-514-9007



Re: 3590 Tapes.

2002-01-03 Thread Seay, Paul

I presume you have a server that has the TAPEUTIL utility (NTUTIL on NT).
If so, there is a capability to "erase" the tape using the same
functionality as the mainframe dataset erase (DSE) otherwise know as Erase
on Scratch with RACF.  This can also be issued in a batch mode.  The Magstar
Installation and User's Guide has the information on how to use the utility.

Hope this helps.

-Original Message-
From: Joshua S. Bassi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 03, 2002 1:30 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 Tapes.


There are several ways to do this:

1) Use another backup utility to write over the tape.  You can use tar,
cpio, NT backup, or whatever to write over either the whole tape or
merely the TSM label.

2) Just do # 1 above to the TSM DB backups since the remaining tapes are
useless without the DB backup.

3) Relabel the tapes using TSM - this could be the easiest if you no
longer want any of the data in the tape library.


--
Joshua S. Bassi
Independent Consultant & IBM Server/Storage Sales Rep.
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Michael, Monte
Sent: Thursday, January 03, 2002 7:34 AM
To: [EMAIL PROTECTED]
Subject: 3590 Tapes.

I am currently in the process of replacing all of my 3590 tapes in my
ATL
with new 3590 EXTENDED length cartridges.  I have a buyer for the 3200
3590
tapes I am removing from TSM/ATL.  How do I go about making sure all
data
has been erased from the old 3590 cartridges?  It is my understanding
that
these tapes can not be degaussed.   Has anyone ran into this situation
before?

Thank You...



Full DB disk causing ESA 10000 disk array to crash.

2002-01-03 Thread Stuart Pitt

Hi,

We currently have a problem, where our ESA 1 disk array will crash when
the disk that our database backs up to is full. Has anyone else suffered
from this problem.

Thanks

Stuart



The information contained in this email is intended only for the
use of the intended recipient at the email address to which it
has been addressed. If the reader of this message is not an
intended recipient, you are hereby notified that you have received
this document in error and that any review, dissemination or
copying of the message or associated attachments is strictly
prohibited.

If you have received this email in error, please contact the sender
by return email or call 01793 87 and ask for the sender and
then delete it immediately from your system.

Please note that neither Innogy nor the sender accepts any
responsibility for viruses and it is your responsibility to scan
attachments (if any).
*



Re: 3590 Tapes.

2002-01-03 Thread Cook, Dwight E (SAIC)

FYI #3 won't do anything to the data...
I talked with someone that had relabeled (by mistake) some tapes
(with valid data) on new 3590 E1A drives
they then put the labels back on with the 3590 B1A drives and experienced
only limited data loss. I believe just the first file on the tape(s).
but access to the data still required the TSM data base

Dwight

PS.  Kids, don't try this at home ;-)


-Original Message-
From: Joshua S. Bassi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 03, 2002 12:30 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 Tapes.


There are several ways to do this:

1) Use another backup utility to write over the tape.  You can use tar,
cpio, NT backup, or whatever to write over either the whole tape or
merely the TSM label.

2) Just do # 1 above to the TSM DB backups since the remaining tapes are
useless without the DB backup.

3) Relabel the tapes using TSM - this could be the easiest if you no
longer want any of the data in the tape library.


--
Joshua S. Bassi
Independent Consultant & IBM Server/Storage Sales Rep.
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Michael, Monte
Sent: Thursday, January 03, 2002 7:34 AM
To: [EMAIL PROTECTED]
Subject: 3590 Tapes.

I am currently in the process of replacing all of my 3590 tapes in my
ATL
with new 3590 EXTENDED length cartridges.  I have a buyer for the 3200
3590
tapes I am removing from TSM/ATL.  How do I go about making sure all
data
has been erased from the old 3590 cartridges?  It is my understanding
that
these tapes can not be degaussed.   Has anyone ran into this situation
before?

Thank You...



Re: 3590 Tapes.

2002-01-03 Thread Joshua S. Bassi

There are several ways to do this:

1) Use another backup utility to write over the tape.  You can use tar,
cpio, NT backup, or whatever to write over either the whole tape or
merely the TSM label.

2) Just do # 1 above to the TSM DB backups since the remaining tapes are
useless without the DB backup.

3) Relabel the tapes using TSM - this could be the easiest if you no
longer want any of the data in the tape library.


--
Joshua S. Bassi
Independent Consultant & IBM Server/Storage Sales Rep.
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Michael, Monte
Sent: Thursday, January 03, 2002 7:34 AM
To: [EMAIL PROTECTED]
Subject: 3590 Tapes.

I am currently in the process of replacing all of my 3590 tapes in my
ATL
with new 3590 EXTENDED length cartridges.  I have a buyer for the 3200
3590
tapes I am removing from TSM/ATL.  How do I go about making sure all
data
has been erased from the old 3590 cartridges?  It is my understanding
that
these tapes can not be degaussed.   Has anyone ran into this situation
before?

Thank You...



Re: Moving Log Volumes on 3.1

2002-01-03 Thread Jim Sporer

Stu,
Sure you can do that.  Format the new volume you want to use for the
database, then add the volume to the data base and extend it.  Delete the
current volumes one at a time by reducing the data base by the size of the
volume you are deleting and then just delete it.  TSM will move the data
off the volume before deleting it.  Use the same procedure for the log files.
Jim

At 12:01 PM 1/3/2002 -0500, you wrote:
>Jim
>
>Can I create one volume for each through this process?  I understand that I
>need to have equiv. or better size for the new volumes prior to mirroring,
>but there are currently 4 log volumes and 3 database volumes.  I want to
>amalgamate them and have one of each properly sized, then mirror, then
>delete the originals and then recreate and mirror just the one volume of
>each.
>
>Make sense? I think it does to me ;o)
>
>Stu
>
>-Original Message-
>From: Jim Sporer [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, January 03, 2002 11:41 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Moving Log Volumes on 3.1
>
>
>Stu,
>Creating mirrors is good way to move your log volumes and database.  Format
>your log volumes, the same size as your current logs, then add them as
>mirrors.  When the log volume mirror is in synch you can delete the current
>log volumes.
>Jim Sporer
>
>At 02:29 PM 12/26/2001 -0500, you wrote:
> >Hi
> >
> >I have recently taken over an ADSM implementation.  It is not configured
>the
> >way I believe it should be and I want to make some adjustments.  At some
> >point I hope to have the necessary funds to upgrade the version too as I
> >believe we are out of date here.
> >
> >Anyhow, I have ADSM 3.1 at level 2.9 and a configuration such that I have
> >logs and database on same hard drive.  I have another hard drive I wish to
> >put in the machine and ultimately want to end up with some semblance of
> >correct configuration.  I wish to have a duplicate copy of DB and logs on
> >both hard drives.  At present there is no ADSM mirroring set up and such,
>if
> >I can move the logs I think I'm golden.
> >
> >My question therefore, is how I go about moving the log volumes safely
> >without jeopardising the installation.  Once they are moved I will
>implement
> >a mirror of the respective DB/LOGS on the opposing disks.
> >
> >Any and all help is appreciated.
> >
> >Thanks
> >
> >Stu



Re: Linux support.

2002-01-03 Thread Ed Anderson

We're using RH7.2 and TSM 4.1.2 client here.

Some things to note :
   (1) If you're using a journaled filesystem, like ext3, you need to put
a the following in your dsm.sys for each mount point defined in /etc/fstab
for your local harddisks and/or NFS mounts.
VirtualMountPoint "/"
VirtualMountPoint "/var"
etc...
   (2)  I make it a habit to exclude the .ISD, .ISM, and .frm files for
mysql, but I do nightly dumps of the databases and then make monthly tars
of the nightly dumps.

Well, it should work, so enjoy and good luck!

-
Ed Anderson
Unix Systems Administrator
University Of Mississippi Medical Center
[EMAIL PROTECTED]

On 2002.01.02 01:25 Pothula S Paparao wrote:
> anyone using TSM client 4.1.x on Linux Red Hat 7.2 to backup filesystems
> and Databases on TSM 4.1.2 running on AIX.
> Does TSM support Red Hat Linux 7.2.
>
> Thanks and regards
> sree.
>



How to pass answer to dsmc question?

2002-01-03 Thread Yury Us

Hi all!
I have open registration on the server and at first login dsmc starts asking
the questions about password, login and contact information.

Does anybody knows how to pass answers on PC to that questions from script?

Thank you in advance,
Yuriy Us.



Re: Moving Log Volumes on 3.1

2002-01-03 Thread Ward, Stuart

Jim

Can I create one volume for each through this process?  I understand that I
need to have equiv. or better size for the new volumes prior to mirroring,
but there are currently 4 log volumes and 3 database volumes.  I want to
amalgamate them and have one of each properly sized, then mirror, then
delete the originals and then recreate and mirror just the one volume of
each.

Make sense? I think it does to me ;o)

Stu

-Original Message-
From: Jim Sporer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 03, 2002 11:41 AM
To: [EMAIL PROTECTED]
Subject: Re: Moving Log Volumes on 3.1


Stu,
Creating mirrors is good way to move your log volumes and database.  Format
your log volumes, the same size as your current logs, then add them as
mirrors.  When the log volume mirror is in synch you can delete the current
log volumes.
Jim Sporer

At 02:29 PM 12/26/2001 -0500, you wrote:
>Hi
>
>I have recently taken over an ADSM implementation.  It is not configured
the
>way I believe it should be and I want to make some adjustments.  At some
>point I hope to have the necessary funds to upgrade the version too as I
>believe we are out of date here.
>
>Anyhow, I have ADSM 3.1 at level 2.9 and a configuration such that I have
>logs and database on same hard drive.  I have another hard drive I wish to
>put in the machine and ultimately want to end up with some semblance of
>correct configuration.  I wish to have a duplicate copy of DB and logs on
>both hard drives.  At present there is no ADSM mirroring set up and such,
if
>I can move the logs I think I'm golden.
>
>My question therefore, is how I go about moving the log volumes safely
>without jeopardising the installation.  Once they are moved I will
implement
>a mirror of the respective DB/LOGS on the opposing disks.
>
>Any and all help is appreciated.
>
>Thanks
>
>Stu



Re: Cluster setup

2002-01-03 Thread Gill, Geoffrey L.

>Any groups you create on 1 server must also be defined
>on the other server(s) in the cluster otherwise, the
>cluster will not start between the servers this is if
>you're using HACMP as your cluster application.  After
>defining each volume group on each server in the
>cluster you have to "sync" the cluster so that each
>server in the cluster has the correct info.  Hope this
>helps and that I understood correctly that you're
>using HACMP as your clustering application.
>Thanks,
>Angela

Sorry, Should have included a bit more info here. This is a Windows2000
Advanced server cluster.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   [EMAIL PROTECTED] 
Phone:  (858) 826-4062
Pager:   (888) 997-9614



Re: Moving Log Volumes on 3.1

2002-01-03 Thread Jim Sporer

Stu,
Creating mirrors is good way to move your log volumes and database.  Format
your log volumes, the same size as your current logs, then add them as
mirrors.  When the log volume mirror is in synch you can delete the current
log volumes.
Jim Sporer

At 02:29 PM 12/26/2001 -0500, you wrote:
>Hi
>
>I have recently taken over an ADSM implementation.  It is not configured the
>way I believe it should be and I want to make some adjustments.  At some
>point I hope to have the necessary funds to upgrade the version too as I
>believe we are out of date here.
>
>Anyhow, I have ADSM 3.1 at level 2.9 and a configuration such that I have
>logs and database on same hard drive.  I have another hard drive I wish to
>put in the machine and ultimately want to end up with some semblance of
>correct configuration.  I wish to have a duplicate copy of DB and logs on
>both hard drives.  At present there is no ADSM mirroring set up and such, if
>I can move the logs I think I'm golden.
>
>My question therefore, is how I go about moving the log volumes safely
>without jeopardising the installation.  Once they are moved I will implement
>a mirror of the respective DB/LOGS on the opposing disks.
>
>Any and all help is appreciated.
>
>Thanks
>
>Stu



Re: Cluster setup

2002-01-03 Thread Angela Hughes

Gill,
Any groups you create on 1 server must also be defined
on the other server(s) in the cluster otherwise, the
cluster will not start between the servers this is if
you're using HACMP as your cluster application.  After
defining each volume group on each server in the
cluster you have to "sync" the cluster so that each
server in the cluster has the correct info.  Hope this
helps and that I understood correctly that you're
using HACMP as your clustering application.
Thanks,
Angela
--- "Gill, Geoffrey L." <[EMAIL PROTECTED]>
wrote:
> I'm working on setting this up on a new cluster. The
> redbook that Tivoli
> directed me to is a bit out of date. I can tell
> because when I tried to
> install the first service it gave errors of missing
> options. Maybe someone
> can help me a bit on this.
>
> The cluter name is CP-ITS-SQLCL01
> the node names associated with this are
> SQLCLPD1
> SQLCLPD2
>
> SQLCLPD1 has these groups associated with it:
> SQL01
>
> SQLCLPD2 has these groups associated with it.
> SQL03
> SQLDEV
> DCMSQLPD
>
> Here is what I put together to get the SQL01 group
> going on SQLCLPD1. The
> service installed and started ok.
> dsmcutil inst /name:"TSM Schedule Service for SQL01"
> /clientdir:"C:\program
> files\tivoli\tsm\baclient" /optfile:E:\TSM\sql01.opt
> /clusternode:yes
> /clustername:cp-its-sqlcl01 /node:cp-its-sqlcl01
> /password:test
> /validate:yes /autostart:yes /startnow:yes
>
> Can someone help me with what I have to do to get
> the rest of the groups
> installed with their own service? I have 3 nodes
> registered in TSM,
> SQLCLPD1, SQLCLPD2(both for the local disk backups),
> and CP-ITS-SQLCL01 for
> the rest. Is this the easiest/preferred way to setup
> TSM?
>
> Options file for SQL01 group. Is there anything I
> can delete from this? Is
> there anything I need to add?
>
> LANG AMENG
>
> COMMmethod TCPIP
>
> TCPServeraddress adsm
>
> TCPPort 1500
>
> compression on
>
> COMPRESSALWAYS NO
>
> Clusternode Y
>
> REPLACE PROMPT
>
> SUBDIR Y
>
> TCPBUFFSIZE 32
>
> TCPWINDOWSIZE 63
>
> passwordaccess generate
>
> resourceutilization 2
>
> changingretries 2
>
> maxcmdretries 2
>
> queryschedperiod 24
>
> Retryperiod 15
>
> Schedmode prompted
>
> SCHEDLOGNAME E:\TSM\dsmclsched.log
>
> ERRORLOGNAME E:\TSM\dsmclerror.log
>
> SCHEDLOGRETENTION 7,D
>
> ERRORLOGRETENTION 7,D
>
> tapeprompt no
>
> Quiet
>
> DOMAIN E: F: G:
>
> Exclude.dir *:\TEMP\...\*
>
> EXCLUDE "*:\RECYCLED\...\*"
>
> EXCLUDE "*:\RECYCLER\...\*"
>
> Exclude *:\...\*.mdf
>
> Exclude *:\...\*.ldf
>
> Exclude *:\...\*.dbf
>
> Exclude *:\...\*.nsf
>
> Exclude *:\...\*.dat
>
> Exclude *:\...\*.tmp
>
> As always thanks for the helpand Happy New Year
> to all.
>
> Geoff Gill
> TSM Administrator
> NT Systems Support Engineer
> SAIC
> E-Mail: [EMAIL PROTECTED]
> Phone:  (858) 826-4062
> Pager:   (888) 997-9614


__
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com



Re: Memory Tuning For AIX

2002-01-03 Thread Chris Gibes

There is a better tool. It was introduced in AIX 4.3.2 and it's called
topas (it's very similiar to "monitor" or "top") Simply enter "topas" at
the AIX command prompt. As to the problem, if the system is really paging,
it's most likely your bufpool is set too high. I would try lowering your
bufpool size. If that helps, then don't increase your bufpool until after
you get more memory. Topas will allow you to see hot processes, disks,
adapters and paging all at the same time, which will make it much easier to
figure what process is monopolizing your resources.

Good Luck


At 07:02 AM 1/3/02 -0500, you wrote:
>I think the wide range of answers as to what this output means is a good
>indication that IBM would do well to develop a more concise tool for
>reviewing resource utilization.  As for my opinion I would start with
>'vmtune' and then look at 'iostat'.  Good Luck
>
>Thanks,
>Jon Martin
>
>-Original Message-
>From: Denis L'Huillier [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, January 02, 2002 1:34 PM
>To: [EMAIL PROTECTED]
>Subject: Memory Tuning For AIX
>
>
>Hello-
>I am having a memory problem.
>I am runnning AIX 4.3.2 on a H50.  TSM is the only application
>running on the server.  When I run vmstat I get the following...
>
>kthr memory page  faultscpu
>- ---   ---
>  r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
>  0  0 136233   202   0   3   2  99  210   0  52  240  66 17 30 16 37
>  1  3 136234   342   0  38  11 3727 4204   0 1322 6136 4665 12 11  3 74
>  2  3 136236   160   0  44  12 3728 5326   0 1324 5844 4644 10 11  2 76
>  1  3 136237   295   0  17  19 4113 5725   0 1305 7174 5091 13 10  3 74
>  0  3 136237   629   0  19   9 4240 7442   0 1316 7200 5082 14 13  5 68
>
>Does this look normal to anyone?  From my limited understanding of vmstat
>it looks like:
>CPU utilization is maxed out
>I have blocked processes (the b column)
>The scan rate (sr) column is very high.
>The server has 1Gig of memory.  I'm really not sure how to tell how much is
>allocated to
>the OS and how much is allocated to TSM.  Does anyone have any ideas or
>pointers is
>tuning memory for AIX?  Do I need a memory upgrade?
>I started checking this because my server response is horrible.
>Thanks.
>Denis

Chris Gibes <[EMAIL PROTECTED]>
Tivoli Certified Consultant
IBM Certified System Administrator
Berbee- Milwaukee Branch
(262) 521-5616


Berbee...putting the E in business



3590 Tapes.

2002-01-03 Thread Michael, Monte

I am currently in the process of replacing all of my 3590 tapes in my ATL
with new 3590 EXTENDED length cartridges.  I have a buyer for the 3200 3590
tapes I am removing from TSM/ATL.  How do I go about making sure all data
has been erased from the old 3590 cartridges?  It is my understanding that
these tapes can not be degaussed.   Has anyone ran into this situation
before?

Thank You...



Re: ANR1217E (insufficient mount points) ... TSM 4.2.1.9 ???

2002-01-03 Thread Lisa Cabanas

I went ahead yesterday and applied the patch to my production  servers.  I didn't see any evidence of mount point wait
failures from last night, nor any drives becoming unavailable due to mount point
errors.

So, hopefully, 4.2.1.9 DID fix the problem!

thanks

lisa



Lisa Cabanas
Tivoli Storage Manager Administrator
Missouri Department of Transportation
105 West Capitol
Jefferson City, MO 65102-0270
[EMAIL PROTECTED]
voice 573.526.4532
fax 573.522.9691


|+-->
||  Sheelagh Treweek|
||  <[EMAIL PROTECTED]|
||  ord.ac.uk>  |
||  |
||  01/03/2002 05:56 AM |
||  Please respond to Sheelagh Treweek  |
||  |
|+-->
  >|
  ||
  |  To: [EMAIL PROTECTED]  |
  |  cc: Lisa Cabanas/SC/MODOT@MODOT, [EMAIL PROTECTED]  |
  |  Subject: Re: ANR1217E (insufficient mount points) ... TSM 4.2.1.9 |
  |   ???  |
  >|





Following my tests before Christmas with TSM 4.2.1.9 server on AIX I posted a
note regarding mount point mis-behaviour.  I have now done some more testing
and I think the problem I saw related to the subtle behaviour when you have
no tape drives defined to a server : processes do not wait.  If you have at
least one drive defined, regardless of whether it is already busy, a second
process will wait for its turn on the drive.  I think this behaviour is as
it was at earlier versions (and I have come across this before but had not
remembered it).  So, sorry if I worried anyone before Christmas ...

[We still are not running this code in production but might very soon.]

Regards, Sheelagh
--
Sheelagh Treweek
Oxford University Computing Services
Email: [EMAIL PROTECTED]
Phone: +44 (0)1865 273205 Fax:-273275



Re: Memory Tuning For AIX

2002-01-03 Thread Mr. Lindsay Morris

We solved this exact problem by reducing BUFPOOLSIZE in dsmserv.opt.  It was
set very high, causing TSM to (apparently) pin that much memory for its own
use - then the OS didn't have enough.  Symptoms: high paging, rotten TSM
performance, admin sessions took minutes to connect.

Recommend using SELFTUNEBUFPSIZE. (If you already are, then this advice
won't help of course.)
Good luck.


Mr. Lindsay Morris
CEO
Applied System Design
www.servergraph.com 
859-253-8000 ofc
425-988-8478 fax
> > Hello-
> > I am having a memory problem.
> > I am runnning AIX 4.3.2 on a H50.  TSM is the only application
> > running on the server.  When I run vmstat I get the following...
> >
> > kthr memory page  faultscpu
> > - ---   ---
> >  r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
> >  0  0 136233   202   0   3   2  99  210   0  52  240  66 17 30 16 37
> >  1  3 136234   342   0  38  11 3727 4204   0 1322 6136 4665 12 11  3 74
> >  2  3 136236   160   0  44  12 3728 5326   0 1324 5844 4644 10 11  2 76
> >  1  3 136237   295   0  17  19 4113 5725   0 1305 7174 5091 13 10  3 74
> >  0  3 136237   629   0  19   9 4240 7442   0 1316 7200 5082 14 13  5 68
> >
> > Does this look normal to anyone?  From my limited understanding
> of vmstat
> > it looks like:
> > CPU utilization is maxed out
> > I have blocked processes (the b column)
> > The scan rate (sr) column is very high.
> > The server has 1Gig of memory.  I'm really not sure how to tell how much
> is
> > allocated to
> > the OS and how much is allocated to TSM.  Does anyone have any ideas or
> > pointers is
> > tuning memory for AIX?  Do I need a memory upgrade?
> > I started checking this because my server response is horrible.
> > Thanks.
> > Denis
> >
>



Re: Memory Tuning For AIX

2002-01-03 Thread Sotonyi Attila

HI,

Can you give me the output of these commands:

/usr/samples/kernel/vmtune
iostat 1
vmstat 1
svmon -G
netstat -m
netstat -in
netstat -v
ps aux |more
ps avx | more
ps -ef | sort +3 -r | more
ps -ef | egrep -v "STIME|$LOGNAME" | sort +3 -r | head -n 10
nfsstat -s
nfsstat -c
no -a

After this maybe I can tell you what's the problem.

Regards,
 Sótonyi Attila  mailto:[EMAIL PROTECTED]
 System Engineer
 MÁV Informatika Kft.
 Tel.:06(1)457-9372



> I think the wide range of answers as to what this output means is a good
> indication that IBM would do well to develop a more concise tool for
> reviewing resource utilization.  As for my opinion I would start with
> 'vmtune' and then look at 'iostat'.  Good Luck

> Thanks,
> Jon Martin

> -Original Message-
> From: Denis L'Huillier [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 02, 2002 1:34 PM
> To: [EMAIL PROTECTED]
> Subject: Memory Tuning For AIX


> Hello-
> I am having a memory problem.
> I am runnning AIX 4.3.2 on a H50.  TSM is the only application
> running on the server.  When I run vmstat I get the following...

> kthr memory page  faultscpu
> - ---   ---
>  r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
>  0  0 136233   202   0   3   2  99  210   0  52  240  66 17 30 16 37
>  1  3 136234   342   0  38  11 3727 4204   0 1322 6136 4665 12 11  3 74
>  2  3 136236   160   0  44  12 3728 5326   0 1324 5844 4644 10 11  2 76
>  1  3 136237   295   0  17  19 4113 5725   0 1305 7174 5091 13 10  3 74
>  0  3 136237   629   0  19   9 4240 7442   0 1316 7200 5082 14 13  5 68

> Does this look normal to anyone?  From my limited understanding of vmstat
> it looks like:
> CPU utilization is maxed out
> I have blocked processes (the b column)
> The scan rate (sr) column is very high.
> The server has 1Gig of memory.  I'm really not sure how to tell how much is
> allocated to
> the OS and how much is allocated to TSM.  Does anyone have any ideas or
> pointers is
> tuning memory for AIX?  Do I need a memory upgrade?
> I started checking this because my server response is horrible.
> Thanks.
> Denis



Re: FILESPACE_NAME vs. HL_NAME

2002-01-03 Thread Martin, Jon R.

Along thos same lines maybe if there are three file systems with the
following naming conventions

/work
/work/data
/work/data/martine

Would TSM back up each of these filesystems separately thus giving you three
different file names?

Thanks,
Jon Martin

-Original Message-
From: Vo An Nguyen/Quebec/IBM [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 02, 2002 5:01 PM
To: [EMAIL PROTECTED]
Subject: Re: FILESPACE_NAME vs. HL_NAME


Hello Mike,

In UNIX, a filespace for ADSM is a filesystem. So in this case,
it looks like the /work is the filespace unless you have mapped
a directory like /work/data as a nfs at the time of the backup or
perhaps you have used the client option virtualmountpoint.
Hope this helps.

Regards,

Vo An Nguyen
Email: [EMAIL PROTECTED]



Mike Crawford <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/02/2002
04:11:23 PM

Please respond to [EMAIL PROTECTED]

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:
Subject:  FILESPACE_NAME vs. HL_NAME


Good Afternoon,

A client is having trouble locating archived files using dsmc q ar.  The
problem
seems to be that the filespace_name and hl_names differ between the files,
even
though they were archived from the same place.

Server: AIX, ADSM v3.1
Client: SunOS, ADSM v3.1

An example:
select filespace_name,hl_name,ll_name,archive_date from archives where
node_name='HUBER'
and ll_name='BS0266'


FILESPACE_NAME: /WORK
   HL_NAME: /DATA/MARTINE/
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:46:30.00

FILESPACE_NAME: /WORK/DATA
   HL_NAME: /MARTINE/
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:41:24.00

FILESPACE_NAME: /WORK/DATA/MARTINE
   HL_NAME: /
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-11-20 05:38:10.00


Depending on how the client specifies the request, they will get a
different
version of the file.

The question is, how does ADSM determine which part of the path is
considered
filespace_name, and which is hl_name?

Thanks,
Mike



Re: Memory Tuning For AIX

2002-01-03 Thread Martin, Jon R.

I think the wide range of answers as to what this output means is a good
indication that IBM would do well to develop a more concise tool for
reviewing resource utilization.  As for my opinion I would start with
'vmtune' and then look at 'iostat'.  Good Luck

Thanks,
Jon Martin

-Original Message-
From: Denis L'Huillier [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 02, 2002 1:34 PM
To: [EMAIL PROTECTED]
Subject: Memory Tuning For AIX


Hello-
I am having a memory problem.
I am runnning AIX 4.3.2 on a H50.  TSM is the only application
running on the server.  When I run vmstat I get the following...

kthr memory page  faultscpu
- ---   ---
 r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
 0  0 136233   202   0   3   2  99  210   0  52  240  66 17 30 16 37
 1  3 136234   342   0  38  11 3727 4204   0 1322 6136 4665 12 11  3 74
 2  3 136236   160   0  44  12 3728 5326   0 1324 5844 4644 10 11  2 76
 1  3 136237   295   0  17  19 4113 5725   0 1305 7174 5091 13 10  3 74
 0  3 136237   629   0  19   9 4240 7442   0 1316 7200 5082 14 13  5 68

Does this look normal to anyone?  From my limited understanding of vmstat
it looks like:
CPU utilization is maxed out
I have blocked processes (the b column)
The scan rate (sr) column is very high.
The server has 1Gig of memory.  I'm really not sure how to tell how much is
allocated to
the OS and how much is allocated to TSM.  Does anyone have any ideas or
pointers is
tuning memory for AIX?  Do I need a memory upgrade?
I started checking this because my server response is horrible.
Thanks.
Denis



Re: ANR1217E (insufficient mount points) ... TSM 4.2.1.9 ???

2002-01-03 Thread Sheelagh Treweek

Following my tests before Christmas with TSM 4.2.1.9 server on AIX I posted a
note regarding mount point mis-behaviour.  I have now done some more testing
and I think the problem I saw related to the subtle behaviour when you have
no tape drives defined to a server : processes do not wait.  If you have at
least one drive defined, regardless of whether it is already busy, a second
process will wait for its turn on the drive.  I think this behaviour is as
it was at earlier versions (and I have come across this before but had not
remembered it).  So, sorry if I worried anyone before Christmas ...

[We still are not running this code in production but might very soon.]

Regards, Sheelagh
--
Sheelagh Treweek
Oxford University Computing Services
Email: [EMAIL PROTECTED]
Phone: +44 (0)1865 273205 Fax:-273275



multiple schedule session with one node

2002-01-03 Thread Sotonyi Attila

Hi All!

System environment:

One TSM server and six TSM client. Oracle financials application and Oracle 8.1.6 
database.
The system environment consists of 4 nodes and one extention node type S7A. The S7A is 
the
TSM server, the nodes are the TSM clients. AIX file level daily incremental backups 
are done
automatically every night. Other oracle backups are performed daily.

Problem description:

When aixfiledaily_gir05 file level incremental backup is started then other backups 
are in
pending and after the backup window expire to missed status while the incremental 
backup is
in progress and takes 6 or more hour. During this time other scheduled backups are 
missed. I
set the resourceutiliziation parameter to 4 in the client option file, but it's not 
working.
I pasted the system outputs below. The problem is occurs with gir05 tsm node.


Software versions:

AIX 4.3.3 ML08
TSM server 4.1.4.0
TSM client 4.1.2.20

Scheduler output:

01/03/2002 04:00:00   01/03/2002 04:00:03   CAT__LG_D_ON   GIR17  Completed
01/03/2002 04:00:00   01/03/2002 04:00:04   MAV05_LG_D_RM  GIR05  Completed
01/03/2002 04:00:00   01/03/2002 04:01:43   MAV1_LG_D_ON   GIR17  Completed
01/03/2002 04:00:00   01/03/2002 04:01:35   MAV__LG_D_ON   GIR17  Completed
01/03/2002 04:20:00   01/03/2002 04:20:02   MAV2_LG_D_ON   GIR17  Completed
01/03/2002 04:30:00   01/03/2002 04:30:03   ORD__LG_D_ON   GIR17  Completed
01/03/2002 04:40:00   01/03/2002 04:40:03   PROD_LG_D_ON   GIR05  Completed
01/03/2002 05:00:00   01/03/2002 05:00:28   AIXFILEDAILY-  GIR05  Started
 _GIR05
01/03/2002 05:00:00   01/03/2002 05:00:02   CAT__LG_D_ON   GIR17  Completed
01/03/2002 05:00:00   01/03/2002 05:00:03   MAV05_LG_D_RM  GIR05  Completed
01/03/2002 05:00:00   01/03/2002 05:01:05   MAV__LG_D_ON   GIR17  Completed
01/03/2002 05:20:00   01/03/2002 05:20:06   MAV2_LG_D_ON   GIR17  Completed
01/03/2002 05:20:00 SUP__LG_D_ON   GIR05  Missed
01/03/2002 05:40:00 PROD_LG_D_ON   GIR05  Missed
01/03/2002 06:00:00   01/03/2002 06:00:35   CAT__DB_D_ON   GIR17  Completed
01/03/2002 06:00:00   01/03/2002 06:02:43   CAT__LG_D_ON   GIR17  Completed
01/03/2002 06:00:00 MAV05_LG_D_RM  GIR05  Missed
01/03/2002 06:00:00   01/03/2002 06:03:00   MAV1_LG_D_ON   GIR17  Completed
01/03/2002 06:00:00   01/03/2002 06:02:52   MAV__LG_D_ON   GIR17  Completed
01/03/2002 06:20:00   01/03/2002 06:22:58   MAV2_LG_D_ON   GIR17  Completed
01/03/2002 06:30:00   01/03/2002 06:31:49   ORD__LG_D_ON   GIR17  Completed
01/03/2002 06:40:00 PROD_LG_D_ON   GIR05  Missed
01/03/2002 07:00:00   01/03/2002 07:00:32   CAT__LG_D_ON   GIR17  Completed
01/03/2002 07:00:00 MAV05_LG_D_RM  GIR05  Missed
01/03/2002 07:00:00   01/03/2002 07:01:32   MAV__LG_D_ON   GIR17  Completed
01/03/2002 07:20:00   01/03/2002 07:21:45   MAV2_LG_D_ON   GIR17  Completed
01/03/2002 07:20:00 SUP__LG_D_ON   GIR05  Missed
01/03/2002 07:40:00 PROD_LG_D_ON   GIR05  Missed
01/03/2002 08:00:00   01/03/2002 08:00:36   CAT__LG_D_ON   GIR17  Completed
01/03/2002 08:00:00 MAV05_LG_D_RM  GIR05  Missed
01/03/2002 08:00:00   01/03/2002 08:02:26   MAV1_LG_D_ON   GIR17  Completed
01/03/2002 08:00:00   01/03/2002 08:02:14   MAV__LG_D_ON   GIR17  Completed
01/03/2002 08:20:00   01/03/2002 08:20:02   MAV2_LG_D_ON   GIR17  Completed
01/03/2002 08:30:00   01/03/2002 08:31:54   ORD__LG_D_ON   GIR17  Completed
01/03/2002 08:40:00 PROD_LG_D_ON   GIR05  Missed
01/03/2002 09:00:00   01/03/2002 09:00:40   CAT__LG_D_ON   GIR17  Completed
01/03/2002 09:00:00 MAV05_LG_D_RM  GIR05  Missed
01/03/2002 09:00:00   01/03/2002 09:01:42   MAV__LG_D_ON   GIR17  Completed
01/03/2002 09:20:00   01/03/2002 09:20:07   MAV2_LG_D_ON   GIR17  Completed
01/03/2002 09:20:00 SUP__LG_D_ON   GIR05  Pending
01/03/2002 09:40:00 PROD_LG_D_ON   GIR05  Pending

Client option file (dsm.sys):

Servername GIR17
 COMMmethod TCPip
 TCPPort1504
 TCPServeraddress   sw17
Tcpclientport   1505
Tcpbuffsize 256
Tcpwindowsize   256
Tcpnodelay  yes
Nodenamegir05
Changingretries 4
Compression no
Dirmc   AIX_GEN
Inclexcl/usr/tivoli/tsm/client/ba/bin/inclexcl.tsm
Maxcmdretries   2
Schedlogname/usr/tivoli/tsm/client/ba/bin/aixsched.log
Schedlogretention   30 D
Schedmode   PROMPTED
Pas