My approach to such interprocess communication is to use a database (SQLite is very lightweight and suitable for this). This alleviates you from all the pesky problems of locking and gives you a convenient tool to query the status of every 3270 session and the job(s) running on it. Also, you can use the queue of jobs as a journal, so you even track which jobs (with their parameters) were run at what time, thus getting persistence.

Of course, if you plan to have the system pick up where it was on a restart, you will have to put some energy into creating "proper" job ids, so you know which parameters are needed to restart a job that was running but did not finish.

In reply to Re: Ressource dispatcher by Corion
in thread Ressource dispatcher by jeepj

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.