Hi,

In the past we too have seen problems with the scheduler daemon not
honouring a nohup under Solaris, HPUX, and AIX.  We have found that using
"at" on unix-type systems causes the least problems.

So, our (ksh) startup files tend to look something like this, and can be
called during init, or from the command line...

if ! pgrep -f "dsmc sched -se.*=$server" >/dev/null 2>&1
then
        print "/bin/dsmc sched -se=$server >/dev/null 2>&1 </dev/null" | at
now
        print "started dsmc sched through 'at'"
fi

(pgrep is Solaris specific.  Amend as required)

Regards,

-=Dave=-
Sungard Vaulting Services
+44 (0) 20 7608 7140




                      "Warren, Matthew
                      (Retail)"                   To:       ADSM-L AT VM.MARIST 
DOT EDU
                      <Matthew.Warren@POWE        cc:
                      RGEN.CO.UK>                 Subject:  Re: AIX startup of 
TSM scheduler
                      Sent by: "ADSM: Dist
                      Stor Manager"
                      <ADSM-L AT VM.MARIST DOT ED
                      U>


                      07/01/2004 10:15
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






Hello,

Under AIX I don't think I've ever had any trouble with;

#>nohup dsmc sched 2>&1 >/dev/null &
#>exit
#>bg
#>exit

But I would be interested if anyone can tell me why

#>nohup dsmc sched 2>&1 >/dev/null &
#>bg
#>exit

doesn't work...    why do you _have_ to say

#>exit
#>bg
#>exit

?

Thanks,

Matt.

                -----Original Message-----
                From: David McClelland
<David.McClelland AT REUTERS DOT COM>@EME
                Sent: Wednesday, January 07, 2004 9:23 AM
                To: ADSM-L AT VM.MARIST DOT EDU
                Subject: Re: AIX startup of TSM scheduler


                Jack,

                Getting a manually invoked nohup-ed TSM scheduler to
stick around in AIX
                has caused a few problems in the past - a look in the
archives will
                probably reveal that. There's some funny thing that I
seem to remember
                about redirected stdout nohup-ed processes dying - I
recall that this
                seemed to work for me in the past:

                # nohup dsmc sched </dev/null > /dev/null 2>&1 &

                Or, manually open a new shell:

                # ksh
                # nohup dsmc sched > /dev/null 2>&1 &
                # exit

                And just check with a `ps -ef` to ensure the dsmc sched
is still
                present...

                Hope this helps,

                Rgds,

                David McClelland
                Global Management Systems
                Reuters
                85 Fleet Street
                London EC4P 4AJ

                -----Original Message-----
                From: Coats, Jack [mailto:Jack.Coats AT BANKSTERLING DOT COM]
                Sent: 07 January 2004 01:46
                To: ADSM-L AT VM.MARIST DOT EDU
                Subject: AIX startup of TSM scheduler


                Ok, I am showing my old age/lack of memory/in-experience
in this area,
                but:

                   I need to reset the passwords for a couple AIX
clients.

                Where do I start up the scheduler on these machines?
(AIX 4.3.3)

                How do I do an elequent kind of thing to do:
                        nohup dsmc sched

                or whatever to restart the scheduler by hand (rather
than rebooting)?

                ... TIA ... JC



--------------------------------------------------------------- -
                        Visit our Internet site at
http://www.reuters.com

                Get closer to the financial markets with Reuters
Messaging - for more
                information and to register, visit
http://www.reuters.com/messaging

                Any views expressed in this message are those of  the
individual
                sender,  except  where  the sender specifically states
them to be
                the views of Reuters Ltd.


___________________________ Disclaimer Notice __________________________
This message and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended recipient,
please contact us, delete the message from your computer and destroy any
copies. Any distribution or copying without our prior permission is
prohibited.

Internet communications are not always secure and therefore the Powergen
Group does not accept legal responsibility for this message. The recipient
is responsible for verifying its authenticity before acting on the
contents. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the Powergen Group.

Registered addresses:

Powergen UK plc, 53 New Broad Street, London, EC2M 1SL
Registered in England & Wales No. 2366970

Powergen Retail Limited,  Westwood Way, Westwood Business Park,
Coventry CV4 8LG.
Registered in England and Wales No: 3407430

Telephone     +44 (0) 2476 42 4000
Fax           +44 (0) 2476 42 5432