I solved this SMTP log cleanup by some other means as I too saw that TCPIP was not patient enough for log cleanup by a startup exit. With the REXX compiler, one can compile an ordinary REXX EXEC into a MODULE. The MODULE can be NUXCLOADed as Immediate command. If my memory serves me well: I created a solution based on that. I can have a look at this next week at my customer's office. Personally, I find it frustrating that so many servers provided e.g. by IBM don't come with built-in housekeeping routines/exits. Every customer has to reinvent the wheel, not once, but again and again for each server. My most recent finding: PERFSVM keeps ever-growing FCXTREND files until the A-disk gets 100% full and then nothing happens.
2007/8/29, Aria Bamdad <[EMAIL PROTECTED]>: > > Hi, > > I have a local exit defined in my DTCPARMS file for my SMTP servers. > When a server is started the exit is called with the 'BEGIN' parameter. > During this time, the server will process the log files that exist on > it's A disk. However, this may take some time and at times, the server > does not finish before TCPIP notices that the server is not listening > and force/autologs the server. This messes up the log processing routine! > > Is there a way to prevent TCPIP from restarting servers for a window of > time to allow for server exit processing to complete. > > Thanks in advance. > -- Kris Buelens, IBM Belgium, VM customer support
