Sorry, I mean that in the properties file I coded Audit.metadata.file.size = 8192 (8MB). At which time it will roll over to a new filename and start over. The only downfall of the current setup is that when the rollover file reaches max size, it reverts back to the original. Too bad they didn't set this up to just rename with a date, and start fresh.
Regarding your observations about one home per instance, that is correct, there is not much to share that is not updated. One thing we did that is different than documented, is that we put up another separate copy of JAVA. Since EKM code is delivered with JAVA, in the JAVA filesystem, we wanted additional stability of only updating EKM when we chose too, and not when another PTF reloaded JAVA. Between that, and the fact that EKM requires customization in the SMPE controlled JAVA filesystem, I didn't want to go mucking about in SMPE controlled area's. So, once *could* mount the EKM instance of JAVA READ only or Shared, and then have a separate home for the configuration, and logs. Regarding your comments about no need for one config file per ekm instance that is incorrect, *assuming* you have more than one EKM server for redundancy purposes. There are settings in the config file that define how each instance talks to the other via tcpip. Dave _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G p 616.653.8429 f 616.653.8497 -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hunkeler Peter (KIUK 3) Sent: Wednesday, January 21, 2009 6:39 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Unix File names EKM and dates >[snip] In our case, I have turned off all AUDIT >recording except for errors, and made the metadata.xml >files 8 MB, [snip] Out of interest, what do you mean you made the metadata.xml files 8 MB? You don't allocate storage when you create a UNIX file. It grows as programs write to it. I've got some offline communication with Lizette and from that I conclude that even in a sysplex shared file system environment each EKM instance will need its own "home" directory to store such data as the metadata.xml, the audit log, the debug files. If this is correct, one will need to treat the "EKM home" like /etc, /var, /tmp, so there is no need to have one config file per EKM instance. It seems that all may access identically named files (symlinks as per my previous suggestion) in their respective "home". -- Peter Hunkeler Credit Suisse ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
