IdleBat setting in .ini file

[clk430]

6.7.1 win2k

Alright, hopefully some one can shed some light on this. In the old production environment, there an "idleBat" setting in the .ini:

IdleBAT=60
SLimBAT=30
;HLimBAT=0
;KeepBAT=0
;MinBAT=0

After IBM support looked at my .ini file, they said that resource management of this type does NOT work for the batch adapter. There is no listener or client connection that would be opened.

So, deleted it. However, on our new server, I experimented and placed it back in the .ini file and on the management console, under configuration-adpater connections, it actually shows that it is a valid setting -
Apapter - BAT
Idle Time - 1:00
etc.

This threw me off. If it is not a valid parameter, how come it shows up in the MC just like the ZIP-FTP etc. adapters?

 

[BocaBurger]

Zip shouldn't be there either.
MC just gets/displays info from the .ini.
Code not present to do anything with the setting.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

What are the negative ramifications of having it there when it's not supposed to? And while you are in the generous mood of helping me out so much Can you look over the rest of my settings to see if something looks out of whack?

IdleDB=60
SLimDB=30
;HLimDB=0
;KeepDB=0
;MinDB=0

IdleBAT=60
SLimBAT=30
;HLimBAT=0
;KeepBAT=0
;MinBAT=0

;IdleMQS=0
;SLimMQS=0
;HLimMQS=0
;KeepMQS=0
;MinMQS=0

;IdleMQSC=0
;SLimMQSC=0
;HLimMQSC=0
;KeepMQSC=0
;MinMQSC=0

;IdleMSMQ=0
;SLimMSMQ=0
;HLimMSMQ=0
;KeepMSMQ=0
;MinMSMQ=0

;IdleRV=0
;SLimRV=0
;HLimRV=0
;KeepRV=0
;MinRV=0

;IdleRVTX=0
;SLimRVTX=0
;HLimRVTX=0
;KeepRVTX=0
;MinRVTX=0

;IdleAQ=0
;SLimAQ=0
;HLimAQ=0
;KeepAQ=0
;MinAQ=0

;IdleTUX=0
;SLimTUX=0
;HLimTUX=0
;KeepTUX=0
;MinTUX=0

;IdleTUXMT=0
;SLimTUXMT=0
;HLimTUXMT=0
;KeepTUXMT=0
;MinTUXMT=0

;IdleROMA=0
;SLimROMA=0
;HLimROMA=0
;KeepROMA=0
;MinROMA=0

;IdleFSMGR=0
;SLimFSMGR=0
;HLimFSMGR=0
;KeepFSMGR=0
;MinFSMGR=0

;IdleALNC=0
;SLimALNC=0
;HLimALNC=0
;KeepALNC=0
;MinALNC=0

;IdleALE=0
;SLimALE=0
;HLimALE=0
;KeepALE=0
;MinALE=0

;IdleBDC=0
;SLimBDC=0
;HLimBDC=0
;KeepBDC=0
;MinBDC=0

;IdleBAPI=0
;SLimBAPI=0
;HLimBAPI=0
;KeepBAPI=0
;MinBAPI=0

;IdleBWSB=0
;SLimBWSB=0
;HLimBWSB=0
;KeepBWSB=0
;MinBWSB=0

IdleEMAIL=60
;SLimEMAIL=0
;HLimEMAIL=0
;MinEMAIL=0

IdleFTP=1
;SLimFTP=0
;HLimFTP=0
;MinFTP=0

;IdleHTTP=0
;SLimHTTP=0
;HLimHTTP=0
;KeepHTTP=0
;MinHTTP=0

;IdleJMS=0
;SLimJMS=0
;HLimJMS=0
;KeepJMS=0
;MinJMS=0

;IdleSOCKET=0
;SLimSOCKET=0
;HLimSOCKET=0
;KeepSOCKET=0
;MinSOCKET=0

;IdleJCA=0
;SLimJCA=0
;HLimJCA=0
;KeepJCA=0
;MinJCA=0

;IdleCORBA=0
;SLimCORBA=0
;HLimCORBA=0
;KeepCORBA=0
;MinCORBA=0

;IdleCICS=0
;SLimCICS=0
;HLimCICS=0
;MinCICS=0

;IdleJNDI=0
;SLimJNDI=0
;HLimJNDI=0
;MinJNDI=0

;IdleSNMP=0
;SLimSNMP=0
;HLimSNMP=0
;MinSNMP=0

;IdlePSCI=0
;SLimPSCI=0
;HLimPSCI=0
;KeepPSCI=0
;MinPSCI=0

;IdleAXION=0
;SLimAXION=0
;HLimAXION=0
;MinAXION=0

 

[janhes]

I was advised to use
IdleDB=10
;SLimDB=0
;HLimDB=0
KeepDB=5
;MinDB=0

For Oracle

 

[BocaBurger]

IdleDB=60
SLimDB=30 <- Slim really doesn't do much. If you have to limit the number of connections (check with your DBA) use HLim.
Keep is a good idea if there are potential connection problems with the DB. Idle is set to drop connections when the system is less busy, but save the connection when busy so you don't waste time creating new connection. Keep tests the idle connection before used.

IdleFTP of 1 could be to short. Most FTP server's defualt timeout is 5 minutes, so IdleFTP could be 3 or 4 minutes.

Not sure what settings that are not used could do. If the code ignores it, nothing, but if at some point the code is changed, there could be an impact.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!