<?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:  %SYSTEM-F-MBTOOSML in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669203#M8254</link>
    <description>Brian, I'm glad to know someone is using my software :-) Email me at the address included with the software and let me know what you think.</description>
    <pubDate>Fri, 11 Nov 2005 10:17:35 GMT</pubDate>
    <dc:creator>Ian Miller.</dc:creator>
    <dc:date>2005-11-11T10:17:35Z</dc:date>
    <item>
      <title>%SYSTEM-F-MBTOOSML</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669198#M8249</link>
      <description>In the process of moving from VAX to Alpha (OpenVMS Alpha 7.3-2).  Doing process-process communication via mailboxes.  In the system service call SYS$CREMBX setting max message size to 4096.  I'm getting mailbox too small error trying to pass about an 1100 byte message.  Thinking I've probably missed either a sysgen or account parameter (only set this up on VAX a bazillion years ago) which allows this max message size - wondering if someone has ideas on how to troubleshoot.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for your help</description>
      <pubDate>Thu, 10 Nov 2005 14:51:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669198#M8249</guid>
      <dc:creator>David Kramer_2</dc:creator>
      <dc:date>2005-11-10T14:51:00Z</dc:date>
    </item>
    <item>
      <title>Re:  %SYSTEM-F-MBTOOSML</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669199#M8250</link>
      <description>Mailboxes have a quota as well as max message size, the defaults are set by sysgen parameters DEFMBXBUFQUO (default 1056) and DEFMBXMXMSG (default 256).  Change your $crembx call or DEFMBXBUFQUO (it is a dynamic parameter).</description>
      <pubDate>Thu, 10 Nov 2005 15:20:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669199#M8250</guid>
      <dc:creator>David Jones_21</dc:creator>
      <dc:date>2005-11-10T15:20:26Z</dc:date>
    </item>
    <item>
      <title>Re:  %SYSTEM-F-MBTOOSML</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669200#M8251</link>
      <description>See HELP/MESSAGE MBTOOSML below&lt;BR /&gt;&lt;BR /&gt;Mailboxes have both a maximum message size and a buffer quota. Generally the quota should be bigger than the maximum. &lt;BR /&gt;&lt;BR /&gt;As David has noted, the SYSGEN parameters DEFMBXMXMSG and DEFMBXBUFQUO define the default values for the $CREMBX parameters MAXMSG and BUFQUO. &lt;BR /&gt;&lt;BR /&gt;IMHO any call to $CREMBX that depends on the default is incorrect! Depending on site specific SYSGEN parameter values is bad. I'm guessing that your error is just anther case supporting my opinion :-) Make sure you have explicitly set both BUFQUO and MAXMSG appropriate to your application.&lt;BR /&gt;&lt;BR /&gt;$ HELP/MESSAGE MBTOOSML&lt;BR /&gt; &lt;BR /&gt; MBTOOSML,  mailbox is too small for request&lt;BR /&gt; &lt;BR /&gt;  Facility:     SYSTEM, System Services&lt;BR /&gt; &lt;BR /&gt;  Explanation:  This message can occur under two conditions:&lt;BR /&gt;                &lt;BR /&gt;                o A write request to a mailbox failed because the message&lt;BR /&gt;                  exceeds the maximum message size specified when the mailbox&lt;BR /&gt;                  was created.&lt;BR /&gt;                &lt;BR /&gt;                o In a call to $GETQUI or $SNDJBC or upon execution of a&lt;BR /&gt;                  queuing command (such as PRINT, SUBMIT, SHOW ENTRY, or&lt;BR /&gt;                  SHOW QUEUE), your process specifies more than the maximum&lt;BR /&gt;                  allowable number of identifiers.&lt;BR /&gt;                &lt;BR /&gt; &lt;BR /&gt;  User Action:  Verify that the call is coded correctly. For a mailbox error,&lt;BR /&gt;                verify the maximum message size specified for the mailbox and&lt;BR /&gt;                increase the size if necessary. For a queuing error, limit the&lt;BR /&gt;                number of identifiers to the current maximum.&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Thu, 10 Nov 2005 20:04:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669200#M8251</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-11-10T20:04:01Z</dc:date>
    </item>
    <item>
      <title>Re:  %SYSTEM-F-MBTOOSML</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669201#M8252</link>
      <description>The mailbox quota is the limit of how many bytes can be queued in a mailbox. Changing the application as suggested would be best.&lt;BR /&gt;&lt;BR /&gt;If you are working with a program which uses mailboxes then you may find the following free programs of mine useful&lt;BR /&gt;&lt;BR /&gt;MBMON - A progam to copy messages written to a mailbox and display and/or record them for later display&lt;BR /&gt;&lt;A href="ftp://ftp.process.com/vms-freeware/fileserv/mbmon.zip" target="_blank"&gt;ftp://ftp.process.com/vms-freeware/fileserv/mbmon.zip&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;MBU - VMS mailbox utility-- show lots of detail about a mailbox, create mailbox, read, write, view messages without reading&lt;BR /&gt;&lt;A href="ftp://ftp.process.com/vms-freeware/fileserv/mbu.zip" target="_blank"&gt;ftp://ftp.process.com/vms-freeware/fileserv/mbu.zip&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Nov 2005 04:28:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669201#M8252</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-11-11T04:28:58Z</dc:date>
    </item>
    <item>
      <title>Re:  %SYSTEM-F-MBTOOSML</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669202#M8253</link>
      <description>Just a note:&lt;BR /&gt;&lt;BR /&gt;MBMON is well worth looking at. Helped a lot when tracking down a tricky interaction bug.</description>
      <pubDate>Fri, 11 Nov 2005 07:04:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669202#M8253</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2005-11-11T07:04:39Z</dc:date>
    </item>
    <item>
      <title>Re:  %SYSTEM-F-MBTOOSML</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669203#M8254</link>
      <description>Brian, I'm glad to know someone is using my software :-) Email me at the address included with the software and let me know what you think.</description>
      <pubDate>Fri, 11 Nov 2005 10:17:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/system-f-mbtoosml/m-p/3669203#M8254</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-11-11T10:17:35Z</dc:date>
    </item>
  </channel>
</rss>

