We've seen this before. It means that MQ thinks there is something it needs to keep track of from that date. It could be a dead or orphaned message. Try re-cycling (stop/start) the queue manager to free up the datasets, and then manually delete the datasets (if MQ hasn't). If the re-cycle doesn't do it, try poking around the queues to see if there is a stale message causing the archieve logs to be held for so long. There are lots of tools around - IBM has free downloads available.
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
