I'm curious to see how my SYSTEM-COLDSTART compares to others. Would
you mind showing me yours if I show you mine?

I'm running on D3 Linux 7.2.1.LINUX with ABS Patch Level 7.2.1.A96.
The system has been running fine since December 15, 2002. We are
licensed for 50 users.

Here's my SYSTEM-COLDSTART:
n
run dm,bp, cleanpibs
comment run dm,bp, cleanjobs
run dm,bp, setpib0
term-type (s
set-date-std
set-ovf-local (cgs
run dm,bp, start.rtc
run dm,bp, setupacct
transaction recover (g
run dm,bp, start.ss
init-osfi
qs.upd
:start-network (a
basic-prot-clear (n
initovf
coldstart.log
set-abs dm,abs, (s
cs.logon-lock (af
maxusers (mql
cs.reset-async
check-resizing
verify.system
run dm,bp, clear.unix.printers
syschk notify=KW39173
d3util.startup
coldstart
start-reclaim-ovf
fs-restart
coldstart-accounts
!mt -f /dev/nst0 setblk 0
!mt -f /dev/nst0 status
off


Regards,
Danny

Not sure what you are fishing around for but...

D3/linux 7.4.2 running on RHEL 3.0

n
run dm,bp, start.rtc
coldstart.log
run dm,bp, cleanpibs
run dm,bp, cleanjobs
run dm,bp, setpib0
term-type (s
set-date-std
set-ovf-local (cgs
run dm,bp, setupacct
transaction recover (g
run dm,bp, start.ss
init-osfi
qs.upd
:start-network (a
basic-prot-clear (n
initovf
set-abs dm,abs, (s
logon-lock (af
maxusers (mql
hot-backup autostart
cs.reset-async
check-resizing
verify.system
run dm,bp, clear.unix.printers
syschk start
d3util.startup
start-reclaim-ovf
fs-restart
coldstart-accounts
coldstart
off

cheseroo wrote:
I'm not fishing for anything. I was just curious as to how my
SYSTEM-COLDSTART macro compared to others just to see if I'm missing
anything useful.

Thanks for sharing your macro.


Regards,
Danny

Generally the system-coldstart should not be touched.

The user-coldstart is where application server specific item should be
entered.

I know that this may sound obvious to the regular contibutors, but I'm
just trying to ensure the that newbie's and lurkers stay informed.

Regards,

Dale

ddspell-m3 wrote:

"ddspell-m3" wrote
system-coldstart, operating upon some configuration item
somewhere. On other platforms we prefer to put plain and simple
startptr commands in the dm,md, USER-COLDSTART macro,
that's just how we've always arranged things. Sorry, I don't
recall more proplus details...

"ddspell-m3" wrote:
- SYSTEM-COLDSTART is supplied by Raining Data and should not be
changed unless you really know what you're doing.
- Your customizations go in USER-COLDSTART.
- Do NOT use the new COLDSTART-ACCOUNTS feature! I recommend deleting
that line from SYSTEM-COLDSTART.
- Copy your SYSTEM-COLDSTART and USER-COLDSTART items (and other data
from the VME DM) to an FSI account so that you can compare and restore
your customizations after patches and new releases.
- Don't overlay the SYSTEM-COLDSTART provided by RD with your own
older version unless you are sure you know what they've changed and
you know whether you need their updates. I strongly suggest "I know
better" overrides of vendor-provided patches unless you really do know
better.

If you aren't sure about what's happening in SYSTEM-COLDSTART, lookup
the commands you see in D3 Ref, or look at the MD to see what programs
are being called. Consider it a learning experience but not a target
for tweaks unless you understand what the processes are doing.

HTH