- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- RMS$_SEQ error
Operating System - OpenVMS
1819847
Members
2637
Online
109607
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2005 07:13 PM
тАО08-31-2005 07:13 PM
Hi,
I met following problem:
I have variable length indexed file (dir/full information for this file is attached).
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.
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.
Everything I found on RMS$_SEQ error is (from comments to sys$connect service):
OpenVMS documentation on sys$put mentiones that RMS$_SEQ can occur but says nothing when and why.
I feel that problem is not about coding bugs (of course I may be wrong) but about configuration.
Thank you
Sergejus
I met following problem:
I have variable length indexed file (dir/full information for this file is attached).
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.
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.
Everything I found on RMS$_SEQ error is (from comments to sys$connect service):
For indexed files, RMS verifies that the first record is inserted in the proper sort
order. If the record cannot be inserted in the proper sort order because of user
action, RMS returns a sequence error (RMS$_SEQ).
OpenVMS documentation on sys$put mentiones that RMS$_SEQ can occur but says nothing when and why.
I feel that problem is not about coding bugs (of course I may be wrong) but about configuration.
Thank you
Sergejus
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2005 07:23 PM
тАО08-31-2005 07:23 PM
Solution
Sergejus,
$ HELP/MESSAGE SEQ/FACILITY=RMS
SEQ, primary key out of sequence (SEQ access)
Facility: RMS, OpenVMS Record Management Services
Explanation: An RMS $PUT service specifies sequential access, but the
primary key value of the record is less than the previous
record entered. $PUT operations in sequential access mode must
be in ascending order of primary key value.
User Action: Modify the program, if necessary, to detect and respond to
the condition. Use the $PUT system service to put records in
ascending order of the primary key value.
The above would tend to indicate that you are accessing
the file in sequential access mode rather than
random access mode. Are you setting the correct
attributes for the open?
Dave
$ HELP/MESSAGE SEQ/FACILITY=RMS
SEQ, primary key out of sequence (SEQ access)
Facility: RMS, OpenVMS Record Management Services
Explanation: An RMS $PUT service specifies sequential access, but the
primary key value of the record is less than the previous
record entered. $PUT operations in sequential access mode must
be in ascending order of primary key value.
User Action: Modify the program, if necessary, to detect and respond to
the condition. Use the $PUT system service to put records in
ascending order of the primary key value.
The above would tend to indicate that you are accessing
the file in sequential access mode rather than
random access mode. Are you setting the correct
attributes for the open?
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2005 08:02 PM
тАО08-31-2005 08:02 PM
Re: RMS$_SEQ error
Many thanks to David.
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 :).
Have a nice day.
Sergejus
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 :).
Have a nice day.
Sergejus
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP