Try putting the dsmc sched command in an executable file (script) and then
calling the file with nohup.

Mit freundlichen Grüßen - With best regards
Serdeczne pozdrowienia - Slan agus beannacht
Paul Baines
TSM/ADSM Consultant


-----Ursprüngliche Nachricht-----
Von: Frost, Dave [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 26. Oktober 2001 14:30
An: [EMAIL PROTECTED]
Betreff: Re: TSM scheduler stops by LOGOUT


Hi Rene,

We have also found the "nohup" is not being honoured on solaris/hpux/aix.  I
think it is something to do with the posix standards.

The best work around which somebody posted to the list some time ago (MANY
thanks whoever you are!!) is to use "at" to restart the daemon:

echo "/bin/dsmc sched >/dev/null 2>&1 </dev/null" | at now


  regards,

-=Dave=-
--
+44 (0)20 7608 7140

A bug is a feature that didn't make it into the manual.



-----Original Message-----
From: Lambelet,Rene,VEVEY,GL-IS/CIS [mailto:[EMAIL PROTECTED]]
Sent: 26 October 2001 11:17
To: [EMAIL PROTECTED]
Subject: TSM scheduler stops by LOGOUT


        Hello,

        we tried the documented command to manually load the TSM scheduler
under AIX 4.3.3. Tle scheduler runs ok, BUT will stop at the LOGOUT !
        Command used: nohup dsmc schedule 2> /dev/null &

        If we use the automatic command via inittab:
        tsm:2:once:/usr/bin/dsmc sched > /dev/null 2>&1

        it works and do not stop !
        Please give any advice...

        R. Lambelet

Nestlé SA

_____________________________________________________________________
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.

Reply via email to