Error DB resends – how to set Format to EOF

Clovertech Forums Cloverleaf Error DB resends – how to set Format to EOF

  • Creator
    Topic
  • #119660
    Peter Heggie
    Participant

      I have a message in the Error DB whose content is a PDF. Both source and target threads have protocols set to binary. The message errored out in the OB pre-TPS UPOC.

      When I attempt to resend from the Error DB, I do not get a chance to choose the format – it is greyed out. When I resend, I get this error message:

      Input file does not contain the same number of messages as you are trying to resend

      How can I resend a message from the Error DB and select the EOF format?

      Peter

      Peter Heggie
      PeterHeggie@crouse.org

    Viewing 2 reply threads
    • Author
      Replies
      • #119661
        Charlie Bursell
        Participant

          From the docs:

          <mark class=”highlight”>resend</mark>_errordb and hcidbdump commands

          <section id=”llt1491837573460__section_7C43B0DC13254A3AB50AB331C0B67CDD” class=”section”>
          <p class=”p”>The ability to <mark class=”highlight”>resend</mark> with modified metadata also applies to error database <mark class=”highlight”>resend</mark>ing. Error database <mark class=”highlight”>resend</mark>ing is performed through hcicmd with the <mark class=”highlight”>resend</mark>_errordb command:</p>

          <ul id=”llt1491837573460__ul_hkm_xs1_j1b” class=”ul”>
          <li class=”li”><mark class=”highlight”>resend</mark>_errordb <var class=”keyword varname”>mid</var>
          <li class=”li”><mark class=”highlight”>resend</mark>_errordb <var class=”keyword varname”>mid</var> <var class=”keyword varname”>file name</var> <var class=”keyword varname”>len10|nl|eof</var>

          <p class=”p”>If only the <var class=”keyword varname”>mid</var> is supplied, the message with that <var class=”keyword varname”>mid</var> is resent directly from the error database with preserved metadata .</p>
          <p class=”p”>If three arguments are provided, the message from the file is sent with metadata from the error db for the given <var class=”keyword varname”>mid</var>. This <var class=”keyword varname”>mid</var> argument supports a range of mids in the same format as hcidbdump, and supports <mark class=”highlight”>resend</mark>ing multiple messages using this mid format:</p>

          <pre class=”pre codeblock”><code>x.y.z = only this message</code></pre>
          <pre class=”pre codeblock”><code>x.y.z1:x.y.z2 = x.y messages z1 through z2</code></pre>
          <p class=”p”>These options takes two arguments:</p>

          <pre class=”pre codeblock”><code><mark class=”highlight”>resend</mark>_errordb -m <var class=”keyword varname”>metafilename</var></code></pre>
          <p class=”p”>This <mark class=”highlight”>resend</mark>s from the error database, but with modified metadata from a file. This file takes the same format as the SMAT metadata temp file.</p>
          <p class=”p”>The mids that are used in the <mark class=”highlight”>resend</mark> come from the metadata file, meaning that when using metadata, <mark class=”highlight”>resend</mark>_errordb also supports <mark class=”highlight”>resend</mark>ing multiple messages.</p>
          <p class=”p”>Another option takes four arguments:</p>

          <pre class=”pre codeblock”><code><mark class=”highlight”>resend</mark>_errordb -m <var class=”keyword varname”>metafilename</var> <var class=”keyword varname”>msgfilename</var> <var class=”keyword varname”>len10|nl|eof</var></code></pre>
          <p class=”p”>This performs an error database <mark class=”highlight”>resend</mark> using both message data and metadata from files. As with <mark class=”highlight”>resend</mark>, if the number of messages in both files do not match, the command returns an error without <mark class=”highlight”>resend</mark>ing any messages.</p>
          <p class=”p”>If two or four arguments are used, but the first argument is not <code class=”ph codeph”>-m</code>, the command returns an error.</p>
          <p class=”p”>As <mark class=”highlight”>resend</mark>_errordb takes from one to four arguments, the full form that is called from hcicmd is as follows:</p>

          <pre class=”pre codeblock”><code>hcicmd -p <var class=”keyword varname”>process_name</var> -c “. <mark class=”highlight”>resend</mark>_errordb <var class=”keyword varname”>mid</var>”
          hcicmd -p <var class=”keyword varname”>process_name</var> -c “. <mark class=”highlight”>resend</mark>_errordb -m <var class=”keyword varname”>metafilename</var>”
          hcicmd -p <var class=”keyword varname”>process_name</var> -c “. <mark class=”highlight”>resend</mark>_errordb mid <var class=”keyword varname”>msgfilename</var> <var class=”keyword varname”>len10|nl|eof</var>”
          hcicmd -p <var class=”keyword varname”>process_name</var> -c “. <mark class=”highlight”>resend</mark>_errordb -m <var class=”keyword varname”>metafilename</var> <var class=”keyword varname”>msgfilename</var> <var class=”keyword varname”>len10|nl|eof</var>”</code></pre>
          </section><section id=”llt1491837573460__section_BB652EB058F44D7BB4FA63D6236A94FF” class=”section”>

          -n metadata_filename option

          <p class=”p”>To simplify these options, hcidbdump enables dumping metadata from the error database into a file of the necessary format. The option for this is <code class=”ph codeph”>-n metadata_filename</code>.</p>

          <pre class=”pre codeblock”><code>hcidbdump -n <var class=”keyword varname”>metadata_filename</var> -e -m <var class=”keyword varname”>mid</var> <var class=”keyword varname”>output_filename</var></code></pre>
          <p class=”p”>For example:</p>

          <pre class=”pre codeblock”><code>hcidbdump -n meta.txt -e -m 0.0.1:0.0.9999 out.txt</code></pre>
          <p class=”p”>This generates the metadata file (meta.txt in the above example) which you can modify, use as the second argument to <code class=”ph codeph”><mark class=”highlight”>resend</mark>_errordb</code>.</p>

          </section>

        • #119662
          Peter Heggie
          Participant

            Thank you – I found that documentation and figured out how to use the command line command to invoke that function. Then I figured out how to use the Remote Commands runtime IDE to issue the same command and it works as I need it to.

            I was hoping there was a way to use the Error Database IDE to resend it but it just does not work (it imposes the length10 format and specifies an optional metadata file which results in that strange error).

            So this is good – I have a way to resend from the Error Database without having to leave the Cloverleaf IDE.

            Thanks again

            Peter

            Peter Heggie
            PeterHeggie@crouse.org

          • #119671
            Robert Kersemakers
            Participant

              We are noticing the same behaviour in CL19.1: can’t resend messages from Error Database with the same error message that you mentioned.
              This seems to be a bug; confirmed by our Dutch supplier.

              Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

          Viewing 2 reply threads
          • You must be logged in to reply to this topic.