Antwort: No Drives Available (Help)

["Felix Mülbaier"]

Hi
I got the same problem a few weeks ago. After updating a TSM 3.1 to 4.13. The
3494 mounted a tape once and then the drives are currently available in library
and ANR8447E.
I deleted the drives from TSM and OS (AIX 4.3.3 .M6 newest ATape and ATLDD ) .
Booting the machine. Drives are available one time then the same procedure.
Tivoli Hotline could not help. Tracing the server they did'nt find anything. At
least I am going back to version 4.1.2 and it worked fine. The same environment
at an other customer worked with TSM 4.1.3.
Hope it helps
frendly regards
Felix
TranCAT Gmbh & CO KG Germany

lbtest utility - reference?

[Walker, Lesley R]

Is there a reference somewhere for the lbtest utility?  I've looked in the
obvious places (Tivoli doco, Richard's quick facts) and can't find any
detailed info.

The ACSLS query commands seem fairly self-explanatory, but what I'm
wondering is whether the other commands are relevant, and if so how to use
them.

TSM 3.7.4 with STK Powderhorn library.

--
Lesley Walker
Unix Engineering, EDS New Zealand
[EMAIL PROTECTED]
"I feel that there is a world market for as many as five computers"
Thomas Watson, IBM corp. - 1943

SAN Question

[Gill, Geoffrey L.]

On an RS6000 is it better to connect a SAN fabric via 2 single fiber cards,
to a seperate fabrics/switches? Is it possible to have them both on the same
fabric somehow teamed together for better throughput or is that even
possible?

With 3590 fiber drives attached to a SAN what's the best anyones got from
throughput? Is it better to direct attach the drives to the RS6000 or
through the switch?

Are there any drawings out there that show possible routes with some
throughput figures? We're in a design phase and want to set up for the best
possible solution now. Even is it doesn't happen all at once at least we can
go forward.

Thanks for the help

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

Re: TSM/DFRMM

[Adolph Kahan]

I've worked with a couple of clients doing this successfully. What is
the issue?



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
GERARD PRATO
Sent: Monday, August 06, 2001 9:34 AM
To: [EMAIL PROTECTED]
Subject: TSM/DFRMM

I am running os390 and using DFRMM as my tape management system. Is
there anyone else doing the same thing?

Enterprise Software Programmer
Broward County Florida
Mr. Gerard Prato
[EMAIL PROTECTED]

Re: tsm 4.1.4 server dies

[Davidson, Becky]

You've run out of log spaceformat another log volume and start up the
database with the new volume.  The exact commands are in the archive.  Once
the database is back up back it up immediately.

-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 8:29 PM
To: [EMAIL PROTECTED]
Subject: tsm 4.1.4 server dies


At 1:30PM today our in-office TSM server (not particularly critical) died.
When I try to start it I get the output pasted below. The last known
function the server was doing when it crashed was deleting the filespace on
one particular node that had around 1.8 million objects. DB size is 2GB and
log size is 2GB. Before the process began my DB was about 71% utilized and
log space was hardly used at all. While it was doing the process it seemed
to jump around (log utilization) from 20-35% or so. DB utilization obviously
kept dropping.

I don t have any ideas offhand. I think theres a DB backup even that went
off during the filespace deletion. I m not sure offhand if that would have
an affect on any of this but I d like suggestions if anyone has any..

Thanks much!

Output:

Tivoli Storage Manager for AIX-RS/6000
Version 4, Release 1, Level 4.0

Licensed Materials - Property of IBM

5698-TSM (C) Copyright IBM Corporation 1990,2000. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt.
ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 2080 megabytes.
ANR0201I Database assigned capacity is 2108 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0353I Recovery log analysis pass in progress.
ANR0354I Recovery log redo pass in progress.
ANR0355I Recovery log undo pass in progress.
ANRD logseg.c(498): Log space has been overcommitted (no empty segment
found) - base LSN = 13617.0.0.
ANR7838S Server operation terminated.
ANR7837S Internal error LOGSEG871 detected.
ANR7834S Thread 8 (tid 809) terminating on signal 11 (Segmentation
violation).
ANR7834S GPR  0: 0xd0019a80,   1: 0x3126af40,   2: 0x30199d48,   3:
0x
ANR7834S GPR  4: 0x3126b508,   5: 0x0008,   6: 0x0002,   7:
0x
ANR7834S GPR  8: 0x10009833,   9: 0x10009833,  10: 0xf0218e04,  11:
0x3126d484
ANR7834S GPR 12: 0x1000f094,  13: 0x,  14: 0x,  15:
0x
ANR7834S GPR 16: 0x,  17: 0x,  18: 0x,  19:
0x3126b148
ANR7834S GPR 20: 0x,  21: 0xf01d7800,  22: 0x311763d8,  23:
0x3800
ANR7834S GPR 24: 0x3126aff8,  25: 0x1e9d,  26: 0x3126aff8,  27:
0x1000dc48
ANR7834S GPR 28: 0x0001,  29: 0x0053,  30: 0x,  31:
0x30035548
ANR7834S IAR: 0x1000f0a4   LR: 0x1000f094   CONTEXT: 0x3126abc0
  0x1000F0A4 pkAbort
  0x100B4DB0 LogAllocSegment
  0x100B16A8 ForceLogPages
  0x100B21F8 LogWriterThread
  0x1000D3E8 StartThread
  0xD00081FC _pthread_body
ANR7833S Server thread 1 terminated in response to program abort.
ANR7833S Server thread 2 terminated in response to program abort.
ANR7833S Server thread 3 terminated in response to program abort.
ANR7833S Server thread 4 terminated in response to program abort.
ANR7833S Server thread 5 terminated in response to program abort.
ANR7833S Server thread 6 terminated in response to program abort.
ANR7833S Server thread 7 terminated in response to program abort.
ANR7833S Server thread 8 terminated in response to program abort.
ANR7833S Server thread 9 terminated in response to program abort.
ANR7833S Server thread 10 terminated in response to program abort.
ANR7833S Server thread 11 terminated in response to program abort.
ANR7833S Server thread 12 terminated in response to program abort.
IOT/Abort trap(coredump)
root@sfaix:/usr/tivoli/tsm/server/bin>

Gerald Wichmann
Systems Engineer
StorageLink
408-844-8893 (v)
408-844-9801 (f)

No Drives Available (Help)

[Gill, Geoffrey L.]

For whatever reason I've had, what TSM says is drive problems.

08/06/01 09:33:31 ANR8447E No drives are currently available in library
3494LIB.

This has been going on since this morning. I don't get it because the drives
are available if I q drive. I also see mounts if I q mount. All 4 drives
seem to be working. So now what? I searched back in the log and this just
started happening at 9:30 this morning. I know IBM was in working on 2
drives that MVS has, I don't use or see them. They showed up at 9:20 so it's
obvious this was probably caused by them. They must have taken the library
offline to get at the 2 drives MVS uses. Why that afected me I don't know.

Here is some more of a sequential log listing. I haven't done anything at
all. I was out all last week so I couldn't and nobody else has access. I've
been running fine since my upgrade to 4.2 a few months ago so I have no clue
what's happened. I did a complete system shutdown and restart and this is
still going on.

08/06/01 17:29:37 ANR8341I End-of-volume reached for 3590 volume U00012.

08/06/01 17:29:38 ANR8447E No drives are currently available in library

   3494LIB.

08/06/01 17:29:38 ANR1404W Scratch volume mount request denied - mount

   failed.

08/06/01 17:29:38 ANR8447E No drives are currently available in library

   3494LIB.

08/06/01 17:29:38 ANR1401W Mount request denied for volume U00435 -
mount
   failed.

08/06/01 17:29:38 ANR8447E No drives are currently available in library

   3494LIB.

08/06/01 17:29:38 ANR1401W Mount request denied for volume U00435 -
mount
   failed.

08/06/01 17:29:38 ANR0986I Process 1755 for SPACE RECLAMATION running in
the
   BACKGROUND processed 88 items for a total of
676,862,037
   bytes with a completion state of FAILURE at 17:29:38.

08/06/01 17:29:38 ANR1081W Space reclamation terminated for volume
U01202 -
   storage media inaccessible.

08/06/01 17:29:38 ANR1042I Space reclamation for storage pool NT_TPOOL
will
   be retried in 60 seconds.

08/06/01 17:29:41 ANR8336I Verifying label of 3590 volume U00012 in
drive
   RMT4 (/dev/rmt4).

08/06/01 17:30:15 ANR8468I 3590 volume U00012 dismounted from drive RMT4

   (/dev/rmt4) in library 3494LIB.

08/06/01 17:30:38 ANR1043I Space reclamation retry delay ended; checking

   volume reclamation status for storage pool NT_TPOOL.

08/06/01 17:30:38 ANR0984I Process 1759 for SPACE RECLAMATION started in
the
   BACKGROUND at 17:30:38.

08/06/01 17:30:38 ANR1040I Space reclamation started for volume U00786,

   storage pool NT_TPOOL (process number 1759).

08/06/01 17:30:38 ANR1044I Removable volume U00786 is required for space

   reclamation.

08/06/01 17:30:38 ANR1044I Removable volume U01310 is required for space

   reclamation.

08/06/01 17:30:38 ANR8324I 3590 volume U00786 is expected to be mounted

   (R/O).

08/06/01 17:30:38 ANR8324I 3590 volume U01310 is expected to be mounted

   (R/O).

08/06/01 17:30:38 ANR8447E No drives are currently available in library

   3494LIB.

08/06/01 17:30:38 ANR1401W Mount request denied for volume U00786 -
mount
   failed.

08/06/01 17:31:10 ANR8337I 3590 volume U00012 mounted in drive RMT4

   (/dev/rmt4).

08/06/01 17:31:45 ANR0985I Process 1759 for SPACE RECLAMATION running in
the
   BACKGROUND completed with completion state FAILURE at

   17:31:45.

08/06/01 17:31:45 ANR1081W Space reclamation terminated for volume
U00786 -
   storage media inaccessible.

08/06/01 17:31:45 ANR1042I Space reclamation for storage pool NT_TPOOL
will
   be retried in 60 seconds.

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

tsm 4.1.4 server dies

[Gerald Wichmann]

At 1:30PM today our in-office TSM server (not particularly critical) died.
When I try to start it I get the output pasted below. The last known
function the server was doing when it crashed was deleting the filespace on
one particular node that had around 1.8 million objects. DB size is 2GB and
log size is 2GB. Before the process began my DB was about 71% utilized and
log space was hardly used at all. While it was doing the process it seemed
to jump around (log utilization) from 20-35% or so. DB utilization obviously
kept dropping.

I don t have any ideas offhand. I think theres a DB backup even that went
off during the filespace deletion. I m not sure offhand if that would have
an affect on any of this but I d like suggestions if anyone has any..

Thanks much!

Output:

Tivoli Storage Manager for AIX-RS/6000
Version 4, Release 1, Level 4.0

Licensed Materials - Property of IBM

5698-TSM (C) Copyright IBM Corporation 1990,2000. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt.
ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 2080 megabytes.
ANR0201I Database assigned capacity is 2108 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0353I Recovery log analysis pass in progress.
ANR0354I Recovery log redo pass in progress.
ANR0355I Recovery log undo pass in progress.
ANRD logseg.c(498): Log space has been overcommitted (no empty segment
found) - base LSN = 13617.0.0.
ANR7838S Server operation terminated.
ANR7837S Internal error LOGSEG871 detected.
ANR7834S Thread 8 (tid 809) terminating on signal 11 (Segmentation
violation).
ANR7834S GPR  0: 0xd0019a80,   1: 0x3126af40,   2: 0x30199d48,   3:
0x
ANR7834S GPR  4: 0x3126b508,   5: 0x0008,   6: 0x0002,   7:
0x
ANR7834S GPR  8: 0x10009833,   9: 0x10009833,  10: 0xf0218e04,  11:
0x3126d484
ANR7834S GPR 12: 0x1000f094,  13: 0x,  14: 0x,  15:
0x
ANR7834S GPR 16: 0x,  17: 0x,  18: 0x,  19:
0x3126b148
ANR7834S GPR 20: 0x,  21: 0xf01d7800,  22: 0x311763d8,  23:
0x3800
ANR7834S GPR 24: 0x3126aff8,  25: 0x1e9d,  26: 0x3126aff8,  27:
0x1000dc48
ANR7834S GPR 28: 0x0001,  29: 0x0053,  30: 0x,  31:
0x30035548
ANR7834S IAR: 0x1000f0a4   LR: 0x1000f094   CONTEXT: 0x3126abc0
  0x1000F0A4 pkAbort
  0x100B4DB0 LogAllocSegment
  0x100B16A8 ForceLogPages
  0x100B21F8 LogWriterThread
  0x1000D3E8 StartThread
  0xD00081FC _pthread_body
ANR7833S Server thread 1 terminated in response to program abort.
ANR7833S Server thread 2 terminated in response to program abort.
ANR7833S Server thread 3 terminated in response to program abort.
ANR7833S Server thread 4 terminated in response to program abort.
ANR7833S Server thread 5 terminated in response to program abort.
ANR7833S Server thread 6 terminated in response to program abort.
ANR7833S Server thread 7 terminated in response to program abort.
ANR7833S Server thread 8 terminated in response to program abort.
ANR7833S Server thread 9 terminated in response to program abort.
ANR7833S Server thread 10 terminated in response to program abort.
ANR7833S Server thread 11 terminated in response to program abort.
ANR7833S Server thread 12 terminated in response to program abort.
IOT/Abort trap(coredump)
root@sfaix:/usr/tivoli/tsm/server/bin>

Gerald Wichmann
Systems Engineer
StorageLink
408-844-8893 (v)
408-844-9801 (f)

Re: ODBC Problem

[Tab Trepagnier]

Andy,

Oops

I completely missed the "2000" part of the original message.  I guess I was
just so glad to have a reliable ODBC driver for use with Office 97 that I
didn't read the details.

My bad.

Tab








Andrew Raibeck <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/06/2001
04:33:13 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

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


To:   [EMAIL PROTECTED]
cc:
Subject:  Re: ODBC Problem


I guess I can't argue with success, but just the same, please note that
the Office 2000 products (Excel, MS Query, Access) are not supported in
the version 4.1 ODBC driver. However, they are supported in version 4.2
ODBC driver.

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.





Tab Trepagnier <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/06/2001 09:30
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: ODBC Problem



Mark,

Yes.  I had that problem too.  The latest ODBC client - 4.1.3. seems to
fix
that problem.

Good luck.

Tab Trepagnier
TSM Administrator
Laitram Corporation







"Remeta, Mark" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/06/2001
11:27:46 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

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


To:   [EMAIL PROTECTED]
cc:
Subject:  ODBC Problem


Hello all, I upgraded my client to 4.1.2.0 and my system to Windows 2000
and
since then haven't been able to run a query against the TSM server using
Excel 2000. When I try and create a new query I get the error message,
'Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'. Does anyone know what
this means and how to fix it???

Thanks in advance,

Mark Remeta
Seligman Data Corp.
100 Park Avenue
New York, NY 10017


Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities
other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: TSM 4.2 Win32 client requires 2 reboots?

[Ron James]

Wanda,

We've discovered that you can bring up task manager and end task on the
first re-boot (the windows installer) and you only need the second re-boot
if any dll's were upgraded(replaced) - if you don't make the second re-boot
the backup archive gui will report several errors - but will work just
fine - especially the command line. If you do end task on the first part -
the windows installer - you will receive the continuation message for the
rest of the setup the next time you actually re-boot the client.

Ron L. James
Storage Management Consultant
STORServer, Inc.
719-536-4801
[EMAIL PROTECTED]
www.storserver.com

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Prather, Wanda
Sent: Monday, August 06, 2001 1:46 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM 4.2 Win32 client requires 2 reboots?


 Thanks Ron, that explains a lot!

-Original Message-
From: Ron Pavan
To: [EMAIL PROTECTED]
Sent: 8/3/01 6:58 PM
Subject: Re: TSM 4.2 Win32 client requires 2 reboots?

This is normal on WinNT 4.0 since the TSM Client starting with 4.x
requires
the W2K installer.  The first reboot is really to install Windows2000
Installer.  The second one depends upon what is running on your client.
The
nice thing is that after you get to 4.x you should not have to reboot
for
the installer again.   As for the send reboot it really depends what is
running but make sure that you have stopped all TSM services on the
client
or it will require a reboot (or unsuccessful install).  I have installed
about 15 clients with 4.2 and none of them required a reboot (upgrading
from
4.1.2 on NT4 and W2K)

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 03, 2001 3:42 PM
To: [EMAIL PROTECTED]
Subject: TSM 4.2 Win32 client requires 2 reboots?


There were a few posts this week from people who are successfully using
the
4.2 client on NT.

I just tried installing it from the CD, and it forced me to reboot once
at
the beginning of the install, then finished the install and told me to
reboot a SECOND TIME!

Is this normal for 4.2 on WinNT?
Any idea what makes this necessary?
Any way around it!?!

Re: ODBC Problem

[Andrew Raibeck]

I guess I can't argue with success, but just the same, please note that
the Office 2000 products (Excel, MS Query, Access) are not supported in
the version 4.1 ODBC driver. However, they are supported in version 4.2
ODBC driver.

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.





Tab Trepagnier <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/06/2001 09:30
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: ODBC Problem



Mark,

Yes.  I had that problem too.  The latest ODBC client - 4.1.3. seems to
fix
that problem.

Good luck.

Tab Trepagnier
TSM Administrator
Laitram Corporation







"Remeta, Mark" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/06/2001
11:27:46 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

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


To:   [EMAIL PROTECTED]
cc:
Subject:  ODBC Problem


Hello all, I upgraded my client to 4.1.2.0 and my system to Windows 2000
and
since then haven't been able to run a query against the TSM server using
Excel 2000. When I try and create a new query I get the error message,
'Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'. Does anyone know what
this means and how to fix it???

Thanks in advance,

Mark Remeta
Seligman Data Corp.
100 Park Avenue
New York, NY 10017


Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities
other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: restore to different node

[Schopp, Kevin]

I change the servername in the opt file to the new nodename, or use the
-virtualnode parm

-Original Message-
From: Jason Jackson [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 2:43 PM
To: [EMAIL PROTECTED]
Subject: restore to different node


Can anyone tell me the options (client/server)  that need to be set to
allow me to restore files from a different node?

Thanks,
Jason

Re: restore to different node

[George Lesho]

If you are doing this from a command line, I can help... use the
virtualnodename option in the command line. You can also set a
virtualnodename in your dsm.opt file (on AIX client) and it will restore
from the named box to the node you are running the command from. Same thing
can be done from a GUI but I don't use them.

George Lesho
AFC Enterprises




Jason Jackson <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/06/2001 02:43:01
PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

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


To:   [EMAIL PROTECTED]
cc:
Fax to:
Subject:  restore to different node


Can anyone tell me the options (client/server)  that need to be set to
allow me to restore files from a different node?

Thanks,
Jason

restore to different node

[Jason Jackson]

Can anyone tell me the options (client/server)  that need to be set to
allow me to restore files from a different node?

Thanks,
Jason

Re: TSM 4.2 Win32 client requires 2 reboots?

[Prather, Wanda]

 Thanks Ron, that explains a lot!

-Original Message-
From: Ron Pavan
To: [EMAIL PROTECTED]
Sent: 8/3/01 6:58 PM
Subject: Re: TSM 4.2 Win32 client requires 2 reboots?

This is normal on WinNT 4.0 since the TSM Client starting with 4.x
requires
the W2K installer.  The first reboot is really to install Windows2000
Installer.  The second one depends upon what is running on your client.
The
nice thing is that after you get to 4.x you should not have to reboot
for
the installer again.   As for the send reboot it really depends what is
running but make sure that you have stopped all TSM services on the
client
or it will require a reboot (or unsuccessful install).  I have installed
about 15 clients with 4.2 and none of them required a reboot (upgrading
from
4.1.2 on NT4 and W2K)

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 03, 2001 3:42 PM
To: [EMAIL PROTECTED]
Subject: TSM 4.2 Win32 client requires 2 reboots?


There were a few posts this week from people who are successfully using
the
4.2 client on NT.

I just tried installing it from the CD, and it forced me to reboot once
at
the beginning of the install, then finished the install and told me to
reboot a SECOND TIME!

Is this normal for 4.2 on WinNT?
Any idea what makes this necessary?
Any way around it!?!

Bad disk replacement procedure

[David Longo]

I have TSM server 3.7.4.0 on AIX 4.3.3.  Have DB and Log mirrored
through TSM and not OS.  The other day we lost one of the internal
SSA disks that the DB is on.  (In all my years of AIX and several years
of TSM, I have never lost a disk - except on a small system that I had
to restore completely.)

I called IBM when the CE showed up with a replacement.  We had to
remove the disk and the filesystem that the DB mirror was on, install
new disk and then recreate the fs and remake the mirrors again!

In one way not a problem because TSM stayed up all this time and
nothing was lost.  But the time spent doing this I thought was long.
I know OS mirroring would have been much simpler to replace disk,
but everything I have read or heard says TSM mirroring is better for
other reasons.

Is there a simpler way to replace a defective disk with TSM mirroring?



David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]



"MMS " made the following
 annotations on 08/06/01 14:20:24
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: 3466 Migration: ya pays ya money and ya gets nothing.

[Joe Faracchio]

Wanda :  thanks!

NOW -   Can a 3466 owner answer this question and save me the cat-and-mouse
I'll get from Level 1:

What, if anything, and especially in the way of run-scripts, is preloaded
on currently shipped  C01 's ???

What I mean is, what will I (err, have I) overlaid in the way of
'features' by replacing the shipped database "shell" with my productin DB.

I did a dry run this weekend of restoring the DB from my production system
the the new C01 we have and it worked!  But when I tried to log into ADMIN
and the password was not ADMIN I suddenly realized that I just replaced
everything including, (if anything) that the shipped DB contains.

Shoulda done more lookin around before I ran the test mgration /cnversion.

SIGH!   ... please help!  ... otherwise I'll have to do a restore from
the rinky-dinky 3MM drive that comes with the C01 and redo a lot of
prepwork!!

thanks !
 ... joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley
Private mail on any topic should be directed to :
   [EMAIL PROTECTED]

Re: rename node

[Richard Sims]

>An HP Systems Admin. changed the hostname of an ADSM client.  We are at ADSM
>Server 3.1.2.90 and ADSM client 3.1.0.8.  Does ADSM use the first hostname
>in the /etc/hosts file?  There are a few aliases for this hostname in the
>hosts file.  What changes do I need to make to ADSM to have backups run
>under the new name?  Can I move previous backups that were ran as nodeA to
>nodenewname?

Debbie - This sounds like a case where you'd want to code NODename in
 your client options file, to keep ADSM from trying to deduce
a choice on its own.

  Richard Sims, BU

Re: Cannot restore 12Gb file

[MC Matt Cooper (2838)]

We were having a problem that looks very similar.  We ended up doing the
restore in pieces, a couple of files systems at a time.  IBM pointed me to
apar PQ46754.  I put the PTF in and have not experienced the problem since.
The apar is for TCPIP.  Hope it helps.
Matt

-Original Message-
From: Riddler, Garth (HAL) [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 12:46 PM
To: [EMAIL PROTECTED]
Subject: Cannot restore 12Gb file

Has anyone had problems with a large restore MVS to Sun?  Did you find a
solution?

Server:  OS 390 2.10 / TSM for MVS ver 4 rel 1 lev 3.0
Client:  SunOS 5.8 / TSM ver 4 rel 1 lev 2.0

We back up a large ".tar" file nightly (12 Gbyte) and keep 3 copies.
The backups appear successful, but when we try to restore we get:

Sun side:
07/30/01   15:01:58 ANS1810E TSM session has been reestablished.
07/30/01   15:08:40 sessRecvVerb(): Invalid verb received.
07/30/01   15:08:40 sessRecvVerb(): length=750a, verb=41,magic=90
07/30/01   15:08:40 TcpFlush: Error 9 sending data on Tcp/Ip socket
4294967295.
07/30/01   15:08:40 sessRecvVerb: Error -50 from call to 'readRtn'.
07/30/01   15:08:40 ANS1809E Session is lost; initializing session reopen
procedure.
07/30/01   15:08:55 ANS1810E TSM session has been reestablished.

MVS side:
14.56.56 STC06166  ANR0406I Session 1712 started for node PRDRMS01 (SUN
SOLARIS) (BPX-Tcp/Ip
14.56.56 STC06166  172.20.1.19(-28694)).

... and around 15:08:40 ...
data movement messages... nothing about the Sun session.

The restore gets between 1 Gbyte to 5 Gbyts to the client, then the
connection
ends and the restore retries a few minutes later.  We've tried different
versions
of the file and restoring to a different machine with the same results.

I've watched the connection on the MVS side and it disappears (no TimeWait,
no ClosWait, etc.).  There are no TCP/IP errors on the MVS side and I
haven't
found any TCP/IP errors on the Sun side (where to look?).

The last time this file was successfully restored was 5/27/01.  The only
major change
has been the switch from OS390 2.6 to OS390 2.10.  Nothing on IBM Link, etc.

Cannot restore 12Gb file

[Riddler, Garth (HAL)]

Has anyone had problems with a large restore MVS to Sun?  Did you find a
solution?

Server:  OS 390 2.10 / TSM for MVS ver 4 rel 1 lev 3.0
Client:  SunOS 5.8 / TSM ver 4 rel 1 lev 2.0

We back up a large ".tar" file nightly (12 Gbyte) and keep 3 copies.
The backups appear successful, but when we try to restore we get:

Sun side:
07/30/01   15:01:58 ANS1810E TSM session has been reestablished.
07/30/01   15:08:40 sessRecvVerb(): Invalid verb received.
07/30/01   15:08:40 sessRecvVerb(): length=750a, verb=41,magic=90
07/30/01   15:08:40 TcpFlush: Error 9 sending data on Tcp/Ip socket
4294967295.
07/30/01   15:08:40 sessRecvVerb: Error -50 from call to 'readRtn'.
07/30/01   15:08:40 ANS1809E Session is lost; initializing session reopen
procedure.
07/30/01   15:08:55 ANS1810E TSM session has been reestablished.

MVS side:
14.56.56 STC06166  ANR0406I Session 1712 started for node PRDRMS01 (SUN
SOLARIS) (BPX-Tcp/Ip
14.56.56 STC06166  172.20.1.19(-28694)).

... and around 15:08:40 ...
data movement messages... nothing about the Sun session.

The restore gets between 1 Gbyte to 5 Gbyts to the client, then the
connection
ends and the restore retries a few minutes later.  We've tried different
versions
of the file and restoring to a different machine with the same results.

I've watched the connection on the MVS side and it disappears (no TimeWait,
no ClosWait, etc.).  There are no TCP/IP errors on the MVS side and I
haven't
found any TCP/IP errors on the Sun side (where to look?).

The last time this file was successfully restored was 5/27/01.  The only
major change
has been the switch from OS390 2.6 to OS390 2.10.  Nothing on IBM Link, etc.




 Riddler, Garth (HAL).vcf

Re: rename node

[Mustafa Baytar]

Simply rename the node name.

You can use command  RENAME NODE  oldnode_name  newnode_name



Debbie Lane
  cc:
Sent by: "ADSM: Subject: rename node
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>


06.08.2001 19:27
Please respond
to "ADSM: Dist
Stor Manager"






An HP Systems Admin. changed the hostname of an ADSM client.  We are at
ADSM
Server 3.1.2.90 and ADSM client 3.1.0.8.  Does ADSM use the first hostname
in the /etc/hosts file?  There are a few aliases for this hostname in the
hosts file.  What changes do I need to make to ADSM to have backups run
under the new name?  Can I move previous backups that were ran as nodeA to
nodenewname?
Please reply to [EMAIL PROTECTED] as I receive the digest version.

Thanks and regards,

Debbie

rename node

[Debbie Lane]

An HP Systems Admin. changed the hostname of an ADSM client.  We are at ADSM
Server 3.1.2.90 and ADSM client 3.1.0.8.  Does ADSM use the first hostname
in the /etc/hosts file?  There are a few aliases for this hostname in the
hosts file.  What changes do I need to make to ADSM to have backups run
under the new name?  Can I move previous backups that were ran as nodeA to
nodenewname?
Please reply to [EMAIL PROTECTED] as I receive the digest version.

Thanks and regards,

Debbie

Re: ODBC Problem

[Tab Trepagnier]

Mark,

Yes.  I had that problem too.  The latest ODBC client - 4.1.3. seems to fix
that problem.

Good luck.

Tab Trepagnier
TSM Administrator
Laitram Corporation







"Remeta, Mark" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/06/2001
11:27:46 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

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


To:   [EMAIL PROTECTED]
cc:
Subject:  ODBC Problem


Hello all, I upgraded my client to 4.1.2.0 and my system to Windows 2000
and
since then haven't been able to run a query against the TSM server using
Excel 2000. When I try and create a new query I get the error message,
'Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'. Does anyone know what
this means and how to fix it???

Thanks in advance,

Mark Remeta
Seligman Data Corp.
100 Park Avenue
New York, NY 10017


Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: TSm and Frame Relay Network?

[Prather, Wanda]

Thanks Len!

(I think you are right about the EXPIRE INVENTORY - I had to write some
scripts to prevent other stuff like reclamation kicking off during an EXPIRE
INVENTORY.  But most of the problems seem to have gone away when  we went
back to NORMAL mode for the log.)



-Original Message-
From: Len Boyle [mailto:[EMAIL PROTECTED]]
Sent: Saturday, August 04, 2001 11:42 AM
To: [EMAIL PROTECTED]
Subject: Re: TSm and Frame Relay Network?


In article <[EMAIL PROTECTED]>,
"Prather, Wanda" <[EMAIL PROTECTED]> says:
>
>Any body out there doing some backups over Frame Relay that would be
willing
>to answer a few questions?
>We have a customer that is planning to do it with some NT clients and is a
>little nervous.
>
>Are you doing it?

Yes
>Approx. how many clients?

65

>About how much data per day?

30-50gig

>
>Any major problems other than the obvious issue that speed is slower than
>for local backups?

- Performance issues both in legnth in time to do the backup and conflicts
with other network use. Lately the network folks have changed something
which makes this worst. But we are going to start using the new block level
backup option to see if that helps.

Maybe Andy or Mike can tell us if TSM will look at single instance storage
across all clients on a TSM server and maybe QOS or pacing for help with
these problems.

One problem that was a surprize is the expire inventory process. This
was normally scheduled to run on sat mornings, but at this time we normally
have some long running client sessions. With the latest algorithims used by
the expire inventory process, the log file can be locked during the expire
inventory run and after, until all the long running clients come to a commit
point. With some of the clients with the right files this can be several
hours. Therefore this leads to more log filling. We used to have an adsm
vm server with over 1000 clients. The expire inventory on the server would
run for 6 days and we did not fill the log which was less then a third the
size. But then the expire inventory does seem to run faster now. Much
faster.

PS I am guessing at the exact details of the locking on the log, but it
seems
   to fit what I see, and the TSM folks have not published a how-does-it-
   work book for me to look it up. Other then what slips out here.

len

ODBC Problem

[Remeta, Mark]

Hello all, I upgraded my client to 4.1.2.0 and my system to Windows 2000 and
since then haven't been able to run a query against the TSM server using
Excel 2000. When I try and create a new query I get the error message,
'Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'. Does anyone know what
this means and how to fix it???

Thanks in advance,

Mark Remeta
Seligman Data Corp.
100 Park Avenue
New York, NY 10017


Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: TSM/DFRMM

[Brian L. Nick]

We are currently running OS/390 2.10 DFRMM and TSM 3.7.4. Let me know if
you have any specific questions and I'll try to help.

Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Companies.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281




   GERARD PRATO
 cc:
   Sent by: Subject: TSM/DFRMM
   "ADSM: Dist
   Stor Manager"
   <[EMAIL PROTECTED]
   RIST.EDU>


   08/06/01
   09:33 AM
   Please
   respond to
   "ADSM: Dist
   Stor Manager"






I am running os390 and using DFRMM as my tape management system. Is there
anyone else doing the same thing?

Enterprise Software Programmer
Broward County Florida
Mr. Gerard Prato
[EMAIL PROTECTED]

Antwort: Re: idletimeout

[Juergen Heinrich]

Hi,

Please use the setopt parameter.
Its valid for
BUFPOOLSIZE
COMMTIMEOUT
DATEFORMAT
EXPINTERVAL
EXPQUIET
IDLETIMEOUT
LOGWARNFULLPERCENT
MAXSESSIONS
NUMBERFORMAT
RESTOREINTERVAL
THROUGHPUTDATATHRESHOLD
THROUGHPUTTIMETHRESHOLD
TIMEFORMAT
The format is:
SETOPT option_name option_value

For more information see admin reference guide

Sincerly

Juergen Heinrich

Verdi Information Consult GmbH
Systemsmanagement
Niederlassung Berlin
Wittestraße 30K
D-13509 Berlin
http://www.verdi-ag.de

Re: AIX-Tape-Messages

[David McClelland]

Hi,

We assumed this was as a result of mis-matched drive microcode and Atape
drivers. Upgrading the drive microcode and atape lpp's  to the latest
levels fixed this instantly and gave us meaningful messages once again.

Rgds,

David McClelland
---
Tivoli Storage Management Team
IBM EMEA Technical Centre,
Mail Point SGJ3, IBM, North Harbour, Portsmouth PO6 3AU, England
Internet: [EMAIL PROTECTED]



David Longo <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 06-08-2001
14:58:04

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

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


To:   [EMAIL PROTECTED]
cc:
Subject:  Re: AIX-Tape-Messages



Yes, we have had that.  (We have 3575 library and use the Atape driver).
Updates  and some new fileset installs overwrite the message catalog
for Atape messages.  The solution is to reinstall the Atape driver.
Hopefully you still have the install file, if not download the current
version.  You don't have to delete and reinstall, just use installp with
the
-F option, this does a force overwrite of installed package.

It keeps the device definitions (actually I think it deletes and recreates
them
as they were).  For safety sakes I would make sure no tape activity is
going on in *SM and print out lscfg before doing install.  It only takes
about 1 -2 minutes.

IBM is aware of this problem, I don't know if there is a planned fix.



David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 08/06/01 09:45AM >>>
Hy all,

I have a problem with the messages in errpt on AIX 4.3.3
Since we installed Maintenance-Level 6 on AIX 4.3.3 messages from the
tape-drives in our tape-library (3490) look something strange. This does
not
only happens with new messages, also old (before the
maintenance-install)message are not more interpreted.
The messages look like this

DE9A52D1   0806150301 I S rmt2   AAA1
D1A1AE6F   0806144101 I H rmt5   AAA0

Does anybody know how to fix ?

Thanks

Christoph



"MMS " made the following
 annotations on 08/06/01 10:03:08
--

This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.  If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify
the sender.  You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.  Health First reserves the right to monitor all e-mail
communications through its networks.  Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of a particular
entity;  and (2) the sender is authorized by the entity to give such views
or opinions.

==

Re: Stop/Restart Scheduler on NT Client

[Lisa Cabanas]

In the NT world, you have to be a machine's administrator to stop/start a
service.  Running netsvc remotely requires you to be that admin, which in
some shops is a jealously defended right (rightly or wrongly I won't
debate-- it seems that the fact that you are the TSM admin and have the
BIG key to all the data is totally missed when discussing machine "admin"
rights...).

The easiest way around this is to run the script-- it will run in the
context of the security of the scheduler service which is usually an
admin, and you can always schedule an "immediate client action" to kick
off the schedules, so you don't have to wait for the query sched period.
You can also update passwords this way too-- all without you, personally
having the NT god mantle.  (AND, you don't have to rub the NT admins face
in the fact that you know how to get around the roadblock).

just my 2 cents, your mileage may vary
lisa




Michel Engels <[EMAIL PROTECTED]>
08/06/2001 04:33 AM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc: (bcc: Lisa Cabanas/SC/MODOT)
Subject:Re: Stop/Restart Scheduler on NT Client



What I use is a little refresh script on my workstation which executes a
netsvc
stop/start on the different clients. My script is written for one server
only
but can easily be extended for all your clients. A little "q node" which
lists
all you known clients to a file and than execute the refresh script for
all
these servers. The thing you need to all the clients is the rights to
execute a
stop/start of a service.

The solution Alex and Juergen gave is not bad but the problem is that it
only
will be executed the next time the client contacts the server which is the
"queryschedperiod" or less. For some clients this may be too late and when
there
are network problems contacting the server (for example when the client
has two
cards and the card which communicates with TSM has problems) sometimes the
"netsvc" method is more accurate.

Hope this helps,

Michel Engels
TSM Consultant
Devteam Belgium





"Chan, Kien" <[EMAIL PROTECTED]> on 08/02/2001 05:32:54 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Michel Engels/BE/Devoteam)

Subject:  Stop/Restart Scheduler on NT Client



Sir/Madam,

Can someone tell me how to stop/restart the backup scheduler on a massive
NT
clients from the server? I had more 200 clients and I updated my client
option on the server. In order for it to take effect, I have to stop and
restart the scheduler on clients. Server and clients are both running on
version 3.7.3. Is there a script I can create to do it this? Or perhaps on
the GUI windows?

Any help will be greatly appreciated. Thank you.


Kien Chan
[EMAIL PROTECTED] 
(316) 268-4318

Re: TSM/DFRMM

[Van Ruler, Ruud R SITI-ISES-31]

yes

working just fine  together with drm.


Ruud van Ruler, Shell Information Technology International B.V.   - ISES/31
Our Central Data Storage Management home page:
http://sww2.shell.com/cdsm/
> Room 1B/G01
> Dokter van Zeelandstraat 1, 2285 BD Leidschendam NL
Tel : +31 (0)70 - 3034644, Fax 4011, Mobile +31 (0)6-55127646
Email Internet: [EMAIL PROTECTED]
  [EMAIL PROTECTED]

R.vanRuler



-Original Message-
From: GERARD PRATO [mailto:[EMAIL PROTECTED]]
Sent: maandag 6 augustus 2001 15:34
To: [EMAIL PROTECTED]
Subject: TSM/DFRMM


I am running os390 and using DFRMM as my tape management system. Is there
anyone else doing the same thing?

Enterprise Software Programmer
Broward County Florida
Mr. Gerard Prato
[EMAIL PROTECTED]

Assertion Problem

[Amini, Mehdi]

Trying to install TSM 4.1.2.19 on an Windows 2000 and getting error when
trying to acCess the GUI

Here is the error:


Assertion failed
Program: N:\APPS\TIVOLI\ADSM\BACLIENT\DSM.EXE
File: DSMEM.CPP
Line: 1508

Exrpession:CB_HDRP((Char *) blkp - FB_Size(blkp))->prevfree==0

Mehdi Amini
LAN/WAN Engineer
ValueOptions
3110 Fairview Park Drive
Falls Church, VA 22042
Phone: 703-208-8754
Fax: 703-205-6879




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by email, delete and destroy this message and its
attachments.


**

Re: AIX-Tape-Messages

[David Longo]

Yes, we have had that.  (We have 3575 library and use the Atape driver).
Updates  and some new fileset installs overwrite the message catalog
for Atape messages.  The solution is to reinstall the Atape driver.
Hopefully you still have the install file, if not download the current
version.  You don't have to delete and reinstall, just use installp with the
-F option, this does a force overwrite of installed package.

It keeps the device definitions (actually I think it deletes and recreates them
as they were).  For safety sakes I would make sure no tape activity is
going on in *SM and print out lscfg before doing install.  It only takes
about 1 -2 minutes.

IBM is aware of this problem, I don't know if there is a planned fix.



David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 08/06/01 09:45AM >>>
Hy all,

I have a problem with the messages in errpt on AIX 4.3.3
Since we installed Maintenance-Level 6 on AIX 4.3.3 messages from the
tape-drives in our tape-library (3490) look something strange. This does not
only happens with new messages, also old (before the
maintenance-install)message are not more interpreted.
The messages look like this

DE9A52D1   0806150301 I S rmt2   AAA1
D1A1AE6F   0806144101 I H rmt5   AAA0

Does anybody know how to fix ?

Thanks

Christoph



"MMS " made the following
 annotations on 08/06/01 10:03:08
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

AIX-Tape-Messages

[Christoph Pilgram]

Hy all,

I have a problem with the messages in errpt on AIX 4.3.3
Since we installed Maintenance-Level 6 on AIX 4.3.3 messages from the
tape-drives in our tape-library (3490) look something strange. This does not
only happens with new messages, also old (before the
maintenance-install)message are not more interpreted.
The messages look like this

DE9A52D1   0806150301 I S rmt2   AAA1
D1A1AE6F   0806144101 I H rmt5   AAA0

Does anybody know how to fix ?

Thanks

Christoph

TSM/DFRMM

[GERARD PRATO]

I am running os390 and using DFRMM as my tape management system. Is there anyone else 
doing the same thing?

Enterprise Software Programmer
Broward County Florida
Mr. Gerard Prato
[EMAIL PROTECTED]

Re: idletimeout

[David Longo]

It's done with the SETOPT command.

David Longo

>>> [EMAIL PROTECTED] 08/06/01 07:31AM >>>
 Good morning SM'rs

 Can anybody remind me of the way to set the IDLETIMEOUT option on the
server while the  server is running?  I know there is a way in the options
file.

Maybe I'll remember after coffee

Thanks

Jack Palmadesso



"MMS " made the following
 annotations on 08/06/01 09:47:01
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: TDP SQL v2.2

[Del Hoobler]

>Getting the following message when I try to start TDP backup through the
>scheduler: ACO5424E Could not connect to SQL server; SQL server returned:
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
>AUTHORITY\SYSTEM'. Microsoft SQL-DMO (ODBC SQLState: 28000)
>(HRESULT:0x80044818)
> I'm running SQL 7.0 SP3 on Win 2000 SP2
>When I manually start backup by running sqlfull.cmd it completes OK.  Any
>suggestions would be greatly appreciated.

Bruce,

Try changing the "Login As" parameter for
the scheduler service to be the user account
that you sucessfully ran a backup with.

Thanks,

Del

Re: 3rd copy of dbvol on other Volumegroup

[Bandu Vibhute (GWB)]

Kumar,

You can create 2 additional copies of TSM DB with command "define dbcopy".
Creating database copy in AIX rootvg will degrade performance of database
and you will not able to take mksysb/sysback unless database is stopped. So
one copy is best solution. If you have problems with one VG you can remove
dbcopy, reduce vg and recreate dbcopy on separate VG.

Thank you,
Bandu Vibhute,
Bestfoods Baking Company,
55 Paradise Lane, Bay Shore, NY, 11706
Voice: 631-951-5212, Cell: 516-702-0323


-Original Message-
From: Pothula S Paparao [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 03, 2001 5:42 AM
To: [EMAIL PROTECTED]
Subject: 3rd copy of dbvol on other Volumegroup
Importance: High


Hi all,
Im having 2 dbvolume copies on same VG called tsmvg. Im intrsted in keeping
the third copy of the DBvol in rootvg instead in TSMvg . My view in this is
to recover latest dbvolume from rootvg incase of  TSMvg corruption.
Can i keep 3rd copy on rootvg. if so, please let me know the steps involed.

Help in this regard is highly appriciated.
THanks and regards
sreekumar.


"MMS Server " made the following
 annotations on 08/03/2001 05:47:51 AM

-
The origin of this electronic mail message was the Internet.
Bestfoods Baking cannot validate the authenticity
of the sender and therefore cannot be held accountable
for any content within.
===



"MMS Server " made the following
 annotations on 08/06/2001 09:15:05 AM
-
This message may contain confidential and trade secret information of Bestfoods 
Baking, and be subject to the Economic Espionage Act of 1996. For recipient's use 
only. If you have received this message in error, please delete immediately, and alert 
the sender.

===

TDP SQL v2.2

[Bruce Kamp]

Getting the following message when I try to start TDP backup through the
scheduler: ACO5424E Could not connect to SQL server; SQL server returned:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
AUTHORITY\SYSTEM'. Microsoft SQL-DMO (ODBC SQLState: 28000)
(HRESULT:0x80044818)
 I'm running SQL 7.0 SP3 on Win 2000 SP2
When I manually start backup by running sqlfull.cmd it completes OK.  Any
suggestions would be greatly appreciated.

---
Bruce Kamp
Network Analyst II
Memorial Healthcare System
P:(954) 987-2020 x4542
Fax: (954) 985-1404
[EMAIL PROTECTED]

idletimeout

[Palmadesso Jack]

 Good morning SM'rs

 Can anybody remind me of the way to set the IDLETIMEOUT option on the
server while the  server is running?  I know there is a way in the options
file.

Maybe I'll remember after coffee

Thanks

Jack Palmadesso

Re: Auditing a shared library

[Richard Sims]

>I'm on Solaris, so there's no mtlib utility.

Well, mtlib *is* available on Solaris.  It just may not be
appropriate to your library type.

Re: TSM post upgrade performance tunning

[Mauricio Angelino Massa]

Walter, thank you very much for answering.
Unfortunately I'm far from the site these days, but as soon as I can I'll
be checking this out.
Regards,
Mauricio





Walter Ridderhof
 cc:
Sent by: "ADSM: Dist   Subject: Re: TSM post upgrade 
performance tunning
Stor Manager"
<[EMAIL PROTECTED]
U>


06/08/01 06:56
Please respond to
"ADSM: Dist Stor
Manager"





Mauricio,

on an NT ADSM V3 -> V4 upgrade we also experienced some frightening
phenomena,
the database becoming twice the size it was, client backups taking longer,
severe impact on db cache hit (wel below 90%, was 98%) and db backup's
taking to
long (2 servers were upgraded the older and the one that had undergone
previous
upgrades got the db problems).
It was as if the db was dragging itself thru mud. What we ultimately did to
get
the db back up to spec's was to backup, dump, reformat, load and audit the
db. I
must say this was a succes the db returned to it's expected size, db cache
hit
went up and everything seems normal again.
Be aware we had problems with the audit, a recreate bit vector problem, an
upgrade to TSM V4.1.3.2 was necessary before the procedure could be
completed.
Below the dump/load procedure we followed for our environment, we let the
procedure run unattended in the weekend. Because the procedure was running
unattended and we didn't want any media problems to interfere, all db
operations
were done to disk.

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * backup the database >>d:\apps\tsm\server1\dsmdump.log
dsmadmc -id=id -pa=password backup db type=full devcl=file scra=yes
wait=yes
>>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * halt the server >>d:\apps\tsm\server1\dsmdump.log
net stop "TSM Server1" >>d:\apps\tsm\server1\dsmdump.log

echo * switch to TSM server dir (where dsmserv.dsk resides)
>>d:\apps\tsm\server1\dsmdump.log
d:
cd \apps\tsm\server1

echo * delete any previous dump volume >>d:\apps\tsm\server1\dsmdump.log
del g:\adsm\dblog\dumpdb.vol >>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * dump the db >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv dumpdb devcl=file vol=dumpdb.vol
>>d:\apps\tsm\server1\dsmdump.log

echo * delete existing db & log volumes >>d:\apps\tsm\server1\dsmdump.log
del f:\adsm\dblog\*.dsm >>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * reinitialize db & log volumes >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv loadformat 1 f:\adsm\dblog\log1.dsm 601 1
f:\adsm\dblog\db1.dsm 15001 >>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * load the dumped db >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv loaddb devcl=file vol=dumpdb.vol
>>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * audit the db as consistency check >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv auditdb fix=yes >>d:\apps\tsm\server1\dsmdump.log



regards Walter Ridderhof




-
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-

Re: TSM post upgrade performance tunning

[Walter Ridderhof]

Mauricio,

on an NT ADSM V3 -> V4 upgrade we also experienced some frightening phenomena,
the database becoming twice the size it was, client backups taking longer,
severe impact on db cache hit (wel below 90%, was 98%) and db backup's taking to
long (2 servers were upgraded the older and the one that had undergone previous
upgrades got the db problems).
It was as if the db was dragging itself thru mud. What we ultimately did to get
the db back up to spec's was to backup, dump, reformat, load and audit the db. I
must say this was a succes the db returned to it's expected size, db cache hit
went up and everything seems normal again.
Be aware we had problems with the audit, a recreate bit vector problem, an
upgrade to TSM V4.1.3.2 was necessary before the procedure could be completed.
Below the dump/load procedure we followed for our environment, we let the
procedure run unattended in the weekend. Because the procedure was running
unattended and we didn't want any media problems to interfere, all db operations
were done to disk.

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * backup the database >>d:\apps\tsm\server1\dsmdump.log
dsmadmc -id=id -pa=password backup db type=full devcl=file scra=yes wait=yes
>>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * halt the server >>d:\apps\tsm\server1\dsmdump.log
net stop "TSM Server1" >>d:\apps\tsm\server1\dsmdump.log

echo * switch to TSM server dir (where dsmserv.dsk resides)
>>d:\apps\tsm\server1\dsmdump.log
d:
cd \apps\tsm\server1

echo * delete any previous dump volume >>d:\apps\tsm\server1\dsmdump.log
del g:\adsm\dblog\dumpdb.vol >>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * dump the db >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv dumpdb devcl=file vol=dumpdb.vol
>>d:\apps\tsm\server1\dsmdump.log

echo * delete existing db & log volumes >>d:\apps\tsm\server1\dsmdump.log
del f:\adsm\dblog\*.dsm >>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * reinitialize db & log volumes >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv loadformat 1 f:\adsm\dblog\log1.dsm 601 1
f:\adsm\dblog\db1.dsm 15001 >>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * load the dumped db >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv loaddb devcl=file vol=dumpdb.vol
>>d:\apps\tsm\server1\dsmdump.log

time /t >>d:\apps\tsm\server1\dsmdump.log
date /t >>d:\apps\tsm\server1\dsmdump.log
echo * audit the db as consistency check >>d:\apps\tsm\server1\dsmdump.log
..\server\dsmserv auditdb fix=yes >>d:\apps\tsm\server1\dsmdump.log



regards Walter Ridderhof




-
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-

Re: Moving vol

[Michel Engels]

What about:
defining a new deviceclass,
using this deviceclass in a new storage pool,
defining this storage pool as next stgpool for the old stgpool,
updating all copygroups to the new stgpool
lowering the migration levels of the old stgpool to hi=0 and lo=0

With this method all is done automatically without specifying a move data for
every single volume in the old stgpool. Moving data for lets say 600 volumes
would be an enoying job.

Michel

Re: Auditing a shared library

[Frost, Dave]

Yes, _auditing_ the library is safe.  Audit will check the current tsm
logical libvols against the physical ones it finds, checking out any that
are no longer visible.  If you weren't running acsls it would also refresh
the cartridge<=>slot mapping.

What isn't safe is to run a checkin libv search=y unless you restrict the
volrange to those volumes that tsm should know about
(volrange=volxxx,volyyy).  When we were sharing our stk with an amass
application, we ensured that the two apps had distinct label ranges.

Also, tsm should reject any volume that wasn't labelled by "label libv" or
dsmlabel if one got accidentally included in the inventory.  I don't know
what netbackup would do in this case, though.

  Oook,

-=Dave=-
+44 (0)20 7803 8026

A beer in need is a beer indeed.



-Original Message-
From: Walker, Lesley R [mailto:[EMAIL PROTECTED]]
Sent: 06 August 2001 06:02
To: [EMAIL PROTECTED]
Subject: Auditing a shared library


Hi all,

Quick question - is it safe to run "audit library" if I'm sharing the
library with another app (Netbackup), and it's a StorageTek ACSLS-controlled
library WITHOUT user access control enabled?

I need to do this because I know a tape has been physically removed without
being checked out.  I have no physical access to the library so I can't just
put it back in (and besides, it may be damaged, as it was jammed in a
drive).

I REALLY don't want to find all the Netbackup volumes in my inventory.  It
would take forever to check them out.

I'm on Solaris, so there's no mtlib utility.  I can run lbtest but that only
lets me do queries.

Server is TSM 3.7.4 on Solaris 7
Library is STK PowderHorn (9310)

--
Lesley Walker
Unix Engineering, EDS New Zealand
[EMAIL PROTECTED]
"I feel that there is a world market for as many as five computers"
Thomas Watson, IBM corp. - 1943

_
This message has been checked for all known viruses by MessageLabs Virus
Control Centre.

www.guardianit.com

The information contained in this email is confidential and intended
only for the use of the individual or entity named above.  If the reader
of this message is not the intended recipient, you are hereby notified
that any dissemination, distribution, or copying of this communication
is strictly prohibited.  Guardian iT Group will accept no responsibility
or liability in respect to this email other than to the addressee.  If you
have received this communication in error, please notify us
immediately via email: [EMAIL PROTECTED]

_
This message has been checked for all known viruses by MessageLabs Virus Control 
Centre.

Re: Stop/Restart Scheduler on NT Client

[Michel Engels]

What I use is a little refresh script on my workstation which executes a netsvc
stop/start on the different clients. My script is written for one server only
but can easily be extended for all your clients. A little "q node" which lists
all you known clients to a file and than execute the refresh script for all
these servers. The thing you need to all the clients is the rights to execute a
stop/start of a service.

The solution Alex and Juergen gave is not bad but the problem is that it only
will be executed the next time the client contacts the server which is the
"queryschedperiod" or less. For some clients this may be too late and when there
are network problems contacting the server (for example when the client has two
cards and the card which communicates with TSM has problems) sometimes the
"netsvc" method is more accurate.

Hope this helps,

Michel Engels
TSM Consultant
Devteam Belgium





"Chan, Kien" <[EMAIL PROTECTED]> on 08/02/2001 05:32:54 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Michel Engels/BE/Devoteam)

Subject:  Stop/Restart Scheduler on NT Client



Sir/Madam,

Can someone tell me how to stop/restart the backup scheduler on a massive NT
clients from the server? I had more 200 clients and I updated my client
option on the server. In order for it to take effect, I have to stop and
restart the scheduler on clients. Server and clients are both running on
version 3.7.3. Is there a script I can create to do it this? Or perhaps on
the GUI windows?

Any help will be greatly appreciated. Thank you.


Kien Chan
[EMAIL PROTECTED] 
(316) 268-4318