<?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: RMS$_SEQ error in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/rms-seq-error/m-p/3616592#M32679</link>
    <description>Sergejus,&lt;BR /&gt;&lt;BR /&gt;$ HELP/MESSAGE SEQ/FACILITY=RMS&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; SEQ,  primary key out of sequence (SEQ access)&lt;BR /&gt;&lt;BR /&gt;  Facility:     RMS, OpenVMS Record Management Services&lt;BR /&gt;&lt;BR /&gt;  Explanation:  An RMS $PUT service specifies sequential access, but the&lt;BR /&gt;                primary key value of the record is less than the previous&lt;BR /&gt;                record entered. $PUT operations in sequential access mode must&lt;BR /&gt;                be in ascending order of primary key value.&lt;BR /&gt;&lt;BR /&gt;  User Action:  Modify the program, if necessary, to detect and respond to&lt;BR /&gt;                the condition. Use the $PUT system service to put records in&lt;BR /&gt;                ascending order of the primary key value.&lt;BR /&gt;&lt;BR /&gt;The above would tend to indicate that you are accessing&lt;BR /&gt;the file in sequential access mode rather than&lt;BR /&gt;random access mode. Are you setting the correct&lt;BR /&gt;attributes for the open?&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
    <pubDate>Thu, 01 Sep 2005 02:23:02 GMT</pubDate>
    <dc:creator>David B Sneddon</dc:creator>
    <dc:date>2005-09-01T02:23:02Z</dc:date>
    <item>
      <title>RMS$_SEQ error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rms-seq-error/m-p/3616591#M32678</link>
      <description>Hi,&lt;BR /&gt;I met following problem:&lt;BR /&gt;I have variable length indexed file (dir/full information for this file is attached).&lt;BR /&gt;This file is opened by group of processes (at this moment 5), that sometimes append and update records. To open, append and update operations processes use only RMS servises: sys$open, sys$connect, sys$update, sys$put - not fopen and fwrite.&lt;BR /&gt;During tests I sometimes find that sys$put service fails with code RMS$_SEQ (1500 successfull appends and 40 randomly distributed failures). I printed record fields that I append and it seems everything is ok.&lt;BR /&gt;&lt;BR /&gt;Everything I found on RMS$_SEQ error is (from comments to sys$connect service):&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;For indexed files, RMS verifies that the first record is inserted in the proper sort&lt;BR /&gt;order. If the record cannot be inserted in the proper sort order because of user&lt;BR /&gt;action, RMS returns a sequence error (RMS$_SEQ).&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;OpenVMS documentation on sys$put mentiones that RMS$_SEQ can occur but says nothing when and why.&lt;BR /&gt;I feel that problem is not about coding bugs (of course I may be wrong) but about configuration.&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;Sergejus</description>
      <pubDate>Thu, 01 Sep 2005 02:13:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rms-seq-error/m-p/3616591#M32678</guid>
      <dc:creator>Sergejus Zabinskis</dc:creator>
      <dc:date>2005-09-01T02:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: RMS$_SEQ error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rms-seq-error/m-p/3616592#M32679</link>
      <description>Sergejus,&lt;BR /&gt;&lt;BR /&gt;$ HELP/MESSAGE SEQ/FACILITY=RMS&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; SEQ,  primary key out of sequence (SEQ access)&lt;BR /&gt;&lt;BR /&gt;  Facility:     RMS, OpenVMS Record Management Services&lt;BR /&gt;&lt;BR /&gt;  Explanation:  An RMS $PUT service specifies sequential access, but the&lt;BR /&gt;                primary key value of the record is less than the previous&lt;BR /&gt;                record entered. $PUT operations in sequential access mode must&lt;BR /&gt;                be in ascending order of primary key value.&lt;BR /&gt;&lt;BR /&gt;  User Action:  Modify the program, if necessary, to detect and respond to&lt;BR /&gt;                the condition. Use the $PUT system service to put records in&lt;BR /&gt;                ascending order of the primary key value.&lt;BR /&gt;&lt;BR /&gt;The above would tend to indicate that you are accessing&lt;BR /&gt;the file in sequential access mode rather than&lt;BR /&gt;random access mode. Are you setting the correct&lt;BR /&gt;attributes for the open?&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Sep 2005 02:23:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rms-seq-error/m-p/3616592#M32679</guid>
      <dc:creator>David B Sneddon</dc:creator>
      <dc:date>2005-09-01T02:23:02Z</dc:date>
    </item>
    <item>
      <title>Re: RMS$_SEQ error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rms-seq-error/m-p/3616593#M32680</link>
      <description>Many thanks to David.&lt;BR /&gt;Of course it was my fault. I found the place where I am swithing to RAB$C_SEQ without restoring RAB$C_KEY ! It was the good lesson for me :).&lt;BR /&gt;&lt;BR /&gt;Have a nice day.&lt;BR /&gt;Sergejus</description>
      <pubDate>Thu, 01 Sep 2005 03:02:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rms-seq-error/m-p/3616593#M32680</guid>
      <dc:creator>Sergejus Zabinskis</dc:creator>
      <dc:date>2005-09-01T03:02:29Z</dc:date>
    </item>
  </channel>
</rss>

