make sure ur not logged into the system in the same shell which started the
tsm scheduler when the backup runs if it's started by the tsm scheduler of
course. Setup the "COMMAND"s schedule to execute on the tsm server side,
then goto the client system and restart the client scheduler (dsmc sched)
or managed services (dsmcad) and log completely out of the system and just
watch it run from the TSM server side with: "q sess".
--Justin Richard Bleistein
Unix/TSM Systems Administrator (Sungard eSourcing)
Desk: (856) 566 - 3600
Cell: (856) 912 - 0861
Email: [EMAIL PROTECTED]
"Conko, Steven"
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: "ADSM: cc:
Dist Stor Subject: Re: problem with a su script
Manager"
<[EMAIL PROTECTED]
.EDU>
04/02/2003 09:48
AM
Please respond to
"ADSM: Dist Stor
Manager"
we couldnt get it to work with the -c ... most all servers work fine
without
it.
-----Original Message-----
From: Joe Pendergast [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2003 9:48 AM
To: [EMAIL PROTECTED]
Subject: Re: problem with a su script
My system uses the -c option of the su commmand
su - oracle "-c /home/oracle/scripts/backup/db_backup.sh"
Amazing what a missing flag will cause.
"Conko, Steven" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/02/2003 05:25:07 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: problem with a su script
> On all of our database servers we run an archive nightly but instead of a
> regular "archive" we run a command instead:
>
> su - oracle /home/oracle/scripts/backup/db_backup.sh
>
> this script handles all the processing of the database and calls a dsmc
> archive command. on 97% of the servers it works fine. however, on just a
> few of them... that dont appear to be any different, the script
> immediately dies with a return code of 1 (no, its not permissions)....
> however tsm reports it as completed (another problem). it doesnt appear
> the script ever gets run because we use a debugging statement for the
> first line that never gets called. nothing in the environment seems to be
> a problem and on one system it just suddenly stopped working without any
> changes being made.
>
> any ideas whats going on here? we're running aix 4.3.3, tsm client 5.1.5
> and server aix 4.3.3 tsm 4.2.2... even on the servers it works on.
>
> Steven A. Conko
> Senior Unix Systems Administrator
> ADT Security Services, Inc.
>
