- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: RMS indexed file with no record layout availab...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
тАО03-17-2009 01:13 PM
тАО03-17-2009 01:13 PM
RMS indexed file with no record layout available
Is there a way to determine the position and a length of a field in the record of an RMS indexed file without having the record map?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2009 01:20 PM
тАО03-17-2009 01:20 PM
Re: RMS indexed file with no record layout available
Welcome to the ITRC OpenVMS Forum!
Strictly speaking, there is no record layout meta data stored about RMS files with the file itself, other than the layouts of the keys (and the keys can be partial or composites of different fields).
Other than the actual data structure maps used with a file, about the only options are to use DUMP to look at the contents, or to disassemble the code.
Admittedly, neither is a particularly attractive option. Reverse engineering record structures is a bit of a black art (having done it some times).
That said, reports generated from the data are extremely useful.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2009 01:28 PM
тАО03-17-2009 01:28 PM
Re: RMS indexed file with no record layout available
Thanks for such a quick reply. The dump does not show much, all binary. You have mention a disassembler. Do you know of any. Will it work on *.exe files ? I do not even have the *.obj files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2009 04:05 PM
тАО03-17-2009 04:05 PM
Re: RMS indexed file with no record layout available
Failing that, I'd start with DUMP and looking at what's in the file. You'll be looking for date values, floating point values or whatever it is that you think is stored in the file. As you've found, the key definitions can help.
If you're willing to disassemble the associated VAX or Alpha executable code and assuming that disassembly and reverse-engineering is permissible within your environment (check with the corporate legal folks, etc), the old VAX disassembler is DISM32, and it's been available around the network. (It was at the SAIC archives, but they went offline a month or two back.) With Alpha, the srm_check tool is a potential option here.
And if you think the dump shows binary, a disassembler provides you with assembler code. No comments. No structure. Probably also an instruction sequence that has been through an optimizer after having been compiled from the original source code. (Unless the source code was originally VAX Macro32 Assembler and you're working with VAX code, but that's fairly rare.)
I've done file-level reverse engineering in the past. It can take weeks to fully figure out what you're looking at in a moderately complex file. And that's presuming the original programmers didn't do something weird.
If you're moving forward from OpenVMS VAX to Alpha or from OpenVMS Alpha to OpenVMS I64 on Integrity, then you might be able to run the executable through one of the image translation tools. That (usually) avoids having to reverse-engineer the data files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2009 12:04 AM
тАО03-18-2009 12:04 AM
Re: RMS indexed file with no record layout available
May be someone saved the sources/libraries. In a save set. Or zip file. Or .tlb. Or even compilation listings (.lis).
Or may be in the datatrieve setup (sorry but my head is empty on the subject, it's 20 been years that I used DTR).
fwiw
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2009 02:48 AM
тАО03-18-2009 02:48 AM
Re: RMS indexed file with no record layout available
No luck huh? Ascii columns are often easy to line up, binary data much less so.
Just to be sure... By default DUMP does a BLOCK dump, which for an indexed file starts with a few block of binary looking data more often than not with data bucket following at block 3 or 4. But that data has binary bucket headers and record headers and possibly compression.
So you must request a record dump. For example:
$ DUMP/RECORD=COUNT=5
You may also try an editor to look at the data. Sometimes it helps to first extract the
record to a width restricted, padded sequential file:
$CONVERTPAD/TRUN/FDL=SYS$INPPUT tmp.idx tmp.seq
RECORD; FORM FIXED; SIZE 64
Good luck!
Hein.