Validation Automation

[ptc-924238]

Hi, part of my job is to validate lots of files in the shortest amount of time. I am usually dealing with thousands of files. So up until now I've been using AutoIT to "control" Epic. But when doing this, I have to shut down Epic completely for each file to clear up the memory, otherwise it gets too big quickly. I think I should be using an ACL script instead so I came up with; Edit -OK [filename];Check_completeness -Full output=[filename];file_close();wait 1 So what I do is create an ACL script with one line as above per file to validate. But then, I get into the same issue: the memory gets too big quickly, and Epic usually can only do 50-60 files before it gets too slow. I am using a recent Dell Precision (Quad6700) with 4 GB RAM. How do I modify this line so the memory clears up after each file closes?

[ptc-1153309]

Since it seems all you do is "checking for completeness", you could simply validate the XML against your DTD or Schema, using for instance a Xerces-J in Java or some .NET classes, it's just a few lines of code, or you might even find some precompiled validator.exe somewhere on the web.

[ptc-924238]

Hi Lech, Thanks for your reply. I should have mentioned that I have to use Epic most of the time. This is a client requirement, and in most of the cases, given that their environment is usually highly customized, it also makes sense. I am aware of all the other possibilities out there to validate XML files. But I have to validate using Epic. I came up yesterday with a new way using Powershell -becuase it can act on processes-, but it's not what I want; I'd rather have a good ACL script.