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?
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?