ADSM-L

Re: TDP for Domino Schedule via Script

2002-03-29 11:52:56
Subject: Re: TDP for Domino Schedule via Script
From: Del Hoobler <hoobler AT US.IBM DOT COM>
Date: Fri, 29 Mar 2002 11:45:33 -0500
> Error-Message:

> Tivoli Storage Manager

> Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level

> 2.0

> (C) Copyright IBM Corporation 1999, 2001. All rights reserved.

> License file exists and contains valid license data.

> CEE3501S The module libApiDS.a was not found.

> From entry point

> DDsmApi::ddsmQueryApiVersion(DBaseApiStatus*,dsmApiVersion*) at compile

> unit offset +00000120

> at address 0F541ED0.

> exec error

Helmut,

When using the TSM scheduler to run the TDP for domino script file
for backup there is no environment setup automatically.
The TSM scheduler runs from the /etc/rc and this does not source or
read any of the /etc/profiles or other environment.
The LIBPATH would need to be setup to have the /usr/lib to find the
libApiDS file and also the /usr/lpp/lotus/notes/latest/os390 directory
for the lotus wrapper startup script.
On the USS system, the TSM scheduler would start as UID 0 (there can
be multile UID 0) and there is no way to know which UID account is running
the scheduler, so would need to surrogate the accounts for the domino
user that would run the script (or the su would not work). This can cause
a security concern for some customers.  In version 4.1.2 of the TSM server
they added schedcmduser option to the schedule to alleviate this issue.

On the TSM Server do a DEFINE SCHEDULE and setup the option
for the schedcmduser=userid.  The userid would be set to the Domino
user that they want to run the script for the TDP Domino backup.

Several things might cause problems when using the -schedcmduser=:
1) Ensure that the tsm client is version 4.1.2 as this is the first
   version that had the schedcmduser capability for the scheduler.
2) In the script file that is running the TDP Domino backup, remove
   the section for the "su".  Since the script is going to be run as
   the user specified by the schedcmduser there is no need for the "su".
3) Make sure that the proper authority is in place within os390.
   the dsmc and dsmswitch applications would both need to have the
   authority to switch for this user.  This is setup on os390 with
   the daemon authorization (the os390 manual has more details on this).

If you are still having problems, please IBM support.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

Leave everything a little better than you found it.
Smile a lot: it costs nothing and is beyond price.
<Prev in Thread] Current Thread [Next in Thread>