running scheduler automatically on SUSE Sles9

dalemcinnis

ADSM.ORG Member
Joined
Jul 20, 2005
Messages
11
Reaction score
0
Points
0
Website
Visit site
I am attempting to have the dsm scheduler start automatically at boot time on my sles 9 box.

I modified the /etc/inittab as per the TSM documentation, adding the following line



tsmsched::eek:nce:/usr/bin/dsmc sched > /dev/null 2>&1



however after reboot there are no dsm processes running on the system :confused:



if I issue dsmc schedule as root it works.



How can I get this to run automatically?



I am running SUSE Sles 9 FixPak1 and TSM Client 5.3.2



Thanks

Dale McInnis
 
Hi,



it seems OK,

my /etc/inittab looks like this

tsm::respawn:/opt/tivoli/tsm/client/ba/bin/dsmc sched >/dev/null 2>&1

(we kill the sheduler daily to be respawned in case of problems ..../usr/bin/dsmc is a link, so it should work as well)



is there any message in the dsmsched.log, dsmerror.log? can you run dsmc sched from the commandline on the foreground? Have you got Passwordaccess generate? Do you see anything regarding dsmc during the startup? In the /var/log/messages?



Hope it helps



Harry
 
Harry

i changed my inittab and there is still no dsmc process running after a reboot.

nothing logged in /var/log/messages, or in /opt/tivoli/tsm/client/ba/bin



If works only if I start it by hand, which makes automating the process real hard. :cry:



dsm.opt does have passwordaccess set to generate.
 
How about changing:



tsmsched::eek:nce:/usr/bin/dsmc sched > /dev/null 2>&1



to



tsmsched::respawn:/usr/bin/dsmc sched > /dev/null 2>&1



Also, make sure the link in /usr/bin is correct.

Else - have you tried Harry's suggestion of using "/opt/tivoli/tsm/client/ba/bin/dsmc sched" instead of "/usr/bin/dsmc sched" ?



One more thought - when you start the scheduler by hand, is it asking you for a password each and every time?
 
Dale,

Have you tried redirecting the output to a file rather than /dev/null and then reviewing that file for the cause of the problem?

Also, Have you considered using the client acceptor daemon (dsmcad)?.

neil
 
Hello...



The correct line in /etc/inittab (if this file really exist in Linux box) is:



tsmsched::eek:nce:/opt/tivoli/tsm/client/ba/bin/dsmc sched > /dev/null 2>&1 # TSM Scheduler



Itś not recommended to use respawn for processes in /etc/inittab, unless you really worry about it.



dsmc runs okay?...Does it asks for password?...Remember that parameters like passwordaccess in configured in dsm.sys not dsm.opt.



Does MANAGEDSERVICES line exist in dsm.sys?..If so, please, remove and retest.



Best Regards,

Ala
 
the following entry in inittab works for me:



tsms:12345:eek:ne:/usr/bin/dsmc sched > /dev/null 2>&1





dsm.sys has the following in it:



SERVERNAME myserver

QUERYSCHEDPERIOD 1

MAXCMDRETRIES 6

RETRYPERIOD 5

SCHEDMODE PROMPTED

TCPCLIENTADDRESS myclient

COMMMETHOD TCPIP

TCPPORT 1500

TCPSERVER Address myserver.mydomain

passwordaccess generate





Now it works :grin:
 
Back
Top