<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Mailbox message size limits. in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210322#M31151</link>
    <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Thanks for all your responses. I think given the timescales we have (always too tight), creating global section on the reply when a mailbox message will exceed the 64K limit is the way forward - at least from my point of view it provides the simplest solution.&lt;BR /&gt;&lt;BR /&gt;thanks anyway&lt;BR /&gt;&lt;BR /&gt;Brian</description>
    <pubDate>Tue, 09 Mar 2004 10:01:10 GMT</pubDate>
    <dc:creator>Brian Reiter</dc:creator>
    <dc:date>2004-03-09T10:01:10Z</dc:date>
    <item>
      <title>Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210313#M31142</link>
      <description>Hi Folks,&lt;BR /&gt;&lt;BR /&gt;I maintain a number of systems based on OpenVMS. These systems use mailboxes for inter-process communications, a new requirement imposed by the customer means that message that are sent by the processes via mailboxes are going to exceed the 64K message size limit.&lt;BR /&gt;&lt;BR /&gt;The obvious solution is to use global sections for inter-process commuication but I was wondering if any other solutions were known about.&lt;BR /&gt;&lt;BR /&gt;As the systems don't particpate as members of a cluster (they are generic units which communicate externally with PC and AIX systems) I'm not sure if the ICC_xxxx services will operate. &lt;BR /&gt;&lt;BR /&gt;For the record the systems are written entirely in Pascal and rely heavily on the AST and Event Flag mechamisms for mailbox message delivery.  &lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Brian</description>
      <pubDate>Fri, 05 Mar 2004 04:31:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210313#M31142</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2004-03-05T04:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210314#M31143</link>
      <description>If the systems are clustered then $ICC is the way to go. This can be used between processes on the same standalone (not-clustered) system. Between processes on different sysstems which are not clustered I think you are going to hit the 64K limit anyway (e.g $QIO over network links) so parhaps you should plan to split messages.</description>
      <pubDate>Fri, 05 Mar 2004 07:41:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210314#M31143</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-03-05T07:41:38Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210315#M31144</link>
      <description>So do the ICC_xxxx services require a cluster license? If they don't then using them this is probabely the easiesy solution.</description>
      <pubDate>Fri, 05 Mar 2004 08:04:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210315#M31144</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2004-03-05T08:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210316#M31145</link>
      <description>Brian,&lt;BR /&gt;&lt;BR /&gt;In your case (non-clustered systems) I could think of using socket-IO, but I'm not sure whether this will fit your (appearently asunchronous) application. It may require some re-design and re-coding.&lt;BR /&gt;Clustering may than be the nices solution (amongst other advantages ;-))</description>
      <pubDate>Fri, 05 Mar 2004 08:41:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210316#M31145</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2004-03-05T08:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210317#M31146</link>
      <description>I do not think the ICC... need a Cluster licence. You will find at &lt;A href="http://www.pi-net.dyndns.org/jfp/english/" target="_blank"&gt;http://www.pi-net.dyndns.org/jfp/english/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;some &lt;BR /&gt;Tests performances decnet, icc, mailbox&lt;BR /&gt;&lt;BR /&gt;which will let you try and compare the throuput of decnet Icc and mailboxes.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Gerard&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Mar 2004 09:07:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210317#M31146</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-03-05T09:07:25Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210318#M31147</link>
      <description>Gerard,&lt;BR /&gt;&lt;BR /&gt;Will try out the ICC_xxxxx routines on Monday. Sadly the development server is not available (we're in the throes of an office move) so can't do much at the moment.&lt;BR /&gt;&lt;BR /&gt;Should all be back and working :) on Monday, although the cynics amongst us reckon at least a week.&lt;BR /&gt;&lt;BR /&gt;I'm trying to do the work with minimum changes due to fairly tight timescales.</description>
      <pubDate>Fri, 05 Mar 2004 10:03:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210318#M31147</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2004-03-05T10:03:40Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210319#M31148</link>
      <description>Hello Brian,&lt;BR /&gt;&lt;BR /&gt;two other possibilities:&lt;BR /&gt;&lt;BR /&gt;1.) Would it be feasible to split the messages to stay below the 64k limit?&lt;BR /&gt;&lt;BR /&gt;2.) How about compressingthe message before sending it? Zou could either use a homegrown algorithm or a general purpose library like Zlib.&lt;BR /&gt;&lt;BR /&gt;Greetings, Martin</description>
      <pubDate>Fri, 05 Mar 2004 11:25:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210319#M31148</guid>
      <dc:creator>Martin P.J. Zinser</dc:creator>
      <dc:date>2004-03-05T11:25:08Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210320#M31149</link>
      <description>If you are at Vms 7.3-1 or later, you can use larger mailboxes size, see on this mirror of the doc&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.pi-net.dyndns.org/docs/openvms0731/731final/6657/6657pro_007.html" target="_blank"&gt;http://www.pi-net.dyndns.org/docs/openvms0731/731final/6657/6657pro_007.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;5.10 Larger Mailbox Buffer Quotas&lt;BR /&gt;&lt;BR /&gt;Prior to Version 7.3--1, the maximum size for the mailbox buffer quota was 64,000 bytes. OpenVMS Alpha Version 7.3--1 supports the creation of mailboxes with larger buffer quotas for improved application scaling. &lt;BR /&gt;&lt;BR /&gt;When creating a mailbox with the $CREMBX system service, you can explicitly supply a mailbox buffer quota with the BUFQUO parameter. If not, the mailbox buffer quota is implicitly supplied by the system parameter DEFMBXBUFQUO. &lt;BR /&gt;&lt;BR /&gt;Note the following: &lt;BR /&gt;&lt;BR /&gt;* Temporary mailboxes do not have a specific size limit. &lt;BR /&gt;* The size of the mailbox is subtracted from the BYTLM quota of the process. &lt;BR /&gt;* Permanent mailboxes do not consume process quota; however, any data in a mailbox consumes nonpaged pool. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Mar 2004 13:36:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210320#M31149</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-03-05T13:36:50Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210321#M31150</link>
      <description>Yes you can have larger mailbox buffer quota in V7.3-1 but not messages larger than 64K which is what was asked for. I think the application should use ICC for within a node and a network link (DECnet,TCP/IP, X.25 or whatever you like) between nodes.</description>
      <pubDate>Sat, 06 Mar 2004 17:56:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210321#M31150</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-03-06T17:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: Mailbox message size limits.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210322#M31151</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Thanks for all your responses. I think given the timescales we have (always too tight), creating global section on the reply when a mailbox message will exceed the 64K limit is the way forward - at least from my point of view it provides the simplest solution.&lt;BR /&gt;&lt;BR /&gt;thanks anyway&lt;BR /&gt;&lt;BR /&gt;Brian</description>
      <pubDate>Tue, 09 Mar 2004 10:01:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mailbox-message-size-limits/m-p/3210322#M31151</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2004-03-09T10:01:10Z</dc:date>
    </item>
  </channel>
</rss>

