Hi Richard and Maria,
Thanks for your info. I believe I should set it EXPInterval to 0 to
eliminate the problem.
Phillip
tsm: UTSLC01>q option
Server Option Option Setting Server Option Option
Setting
----------------- -------------------- ----------------- -------
-------------
CommTimeOut 500 IdleTimeOut 15
BufPoolSize 2048 LogPoolSize 512
DateFormat 1 (mm/dd/yyyy) TimeFormat 1
(hh:mm:ss)
NumberFormat 1 (1,000.00) MessageFormat 1
Language en_US MaxSessions 25
ExpInterval 24 ExpQuiet No
EventServerLoggi- Yes MirrorRead DB Normal
ng
MirrorRead LOG Normal MirrorWrite DB
Sequential
MirrorWrite LOG Parallel TxnGroupMax 40
MoveBatchSize 40 MoveSizeThresh 500
StatusMsgCnt 10 RestoreInterval 1,440
UseLargeBuffers Yes DisableScheds No
NOBUFPREfetch No AuditStorage Yes
REQSYSauthoutfile Yes SELFTUNEBUFpools- No
ize
SELFTUNETXNsize No DBPAGEShadow No
DBPAGESHADOWFile dbpgshdw.bdt QueryAuth None
LogWarnFullPerCe- 90 ThroughPutDataTh- 0
nt reshold
ThroughPutTimeTh- 0
reshold
TCPPort 1500 HTTPPort 1580
HTTPSPort 1543 TCPWindowsize 0
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Richard Sims
Sent: Monday, September 25, 2000 12:26 PM
To: [EMAIL PROTECTED]
Subject: Re: strange expiration process
>We didn't set the EXPInterval, I think it is 0, am I right?
The Force is not that strong in this advisor, Phillip: you'll have
to do a Query OPTions in your server and tell me. According to the
server Admin Ref, the default is 24 (hours) these days.
Richard
