It sounds like you should concentrate on automating this manual or semi-manual process first!

Start using your new process and then see what happens. It didn't sound to me that the problem is that the process produces incorrect results, but rather than it can "abend", fail at some point. And you want to predict or stop that from happening.

I would highly recommend doing some empirical analysis (testing) to see what the issues really are before diving off into writing a lot of code that may or may not do something useful.

It could very well be that your efforts should be spent on what is called a "kick the tires" test. Meaning run a quickie test that takes one minute, but is highly predictive of whether the 10 hour process is going to fail. Ideally, this is not special code but a super abbreviated version of the "real thing". This test uses the "real software" but the test is organized so that when it passes, it means that the .ini file, the config file, the local db file, the connection with the remote host can be established, etc. In other words, passing this one minute thing is very predictive that the 10 hour test will run.

In reply to Re: How to make check process more elegant by Marshall
in thread How to make check process more elegant by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.