dbTalk Databases Forums  

D3/NT automated shutdown

comp.databases.pick comp.databases.pick


Discuss D3/NT automated shutdown in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Bill H
 
Posts: n/a

Default Re: D3/NT automated shutdown - 01-07-2006 , 08:09 PM






Mark:

One should be able to use the "d3tcl" command from the script to log onto
the 'DM' account then run the "shutdown" command. It should be fairly easy
to do.

And, if one wants to get fancy, the "d3tcl" command could run a D3
proc/macro/program to send a message to users, log them off, whatever, then
shutdown D3.

Bill

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote

Quote:
I would suggest that it is NEVER a good idea to simply stop the D3 service.
That will NOT force memory to flush or processes to log off properly.

If at all possible, it will always be better if you get a port logged on
to do a proper "shutdown". Even something as simple as:

for i = 1 to system(18)
execute "logoff ":i:" (z"
next i
data "Y"
chain "shutdown"

This will at least force the ports to all logoff, giving up their
workspace to overflow. Some steps actually writing to filespace will not
allow themselves to be broken, so this will keep you from creating GFEs
automatically.

Using the STOP to stop the service simply kills D3 and if it's in the
middle of pulling up a group or updating the overflow table, you're just
out of luck.


"Brian Bond" <brian (AT) XYZXYZXYZXYZbonanzapress (DOT) com> wrote in message
news:11rm2hq4cndca31 (AT) corp (DOT) supernews.com...
In conjunction with the UPS monitoring software that comes with Windows
2000, I have set up a script that is executed when the power has been off
for three minutes. The script consists of "net stop D3vme", and then
blat.exe to send me email notification (all comm gear is on the UPS).
After the script is run, the UPS software then shuts down the computer.

I understand that the D3Tray program can also be used to automate this
procedure, but it appears that the console must be logged on in order for
that to work, and our console is typically not left logged on.

I don't know if my setup qualifies as a "best practice", but I certainly
do not want it to be a "worst practice". Is there any else or anything
different that I should be doing?

thanks









Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.