IMS itself does not take any action automatically. Since the logs are as close to a complete audit trail for any user interaction with the IMS system, they might need special handling from a retention stand point. From a database recovery perspective, if the DBRC RECON data set for the IMS no longer has the log data set name recorded in it, it would probably be safe to delete. An IMS utility can execute a DELETE.LOG INACTIVE LIST command which should produce a list of log data sets still listed in the RECON data set that are no longer needed to recover a database, at which point a formal process to actually delete the unneeded log from that list could be run using your favored utility.
On 1/17/2017 5:05 PM, Tony Thigpen wrote: > Can someone point me in the right direction? > > I am reviewing the system VTOCs and I see a lot of IMS log files that > contain a date/timestamp in their names. I know they are created by > the IMS system using the skeleton proc member ARCHJCL. What I am > seeing is that the file was created with a retention period of 45 days. > > //DFSSLOGP DD DSN=IMSVS.SLDSP.%SSID.D%ARDATE.T%ARTIME.V%ARVERS, > // DISP=(NEW,CATLG,DELETE),RETPD=45, > // UNIT=3390,VOL=SER=SIMS00,SPACE=(CYL,(1,1)) > > But, I have daily files going back almost 2 years. > > My conclusion is that something stopped cleaning up the files "back > when". > > Is the clean-up of expired files something normally handled within IMS > or outside of IMS? > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
