MVSFORUMS.com

spalanis · Beginner Joined: 19 Jul 2006 Posts: 32 Topics: 15

Hi All,

Our company is in the process of Enterprise COBOL migration and the only issue which we are not able to resolve is conversion of BDAM files. Our old version of COBOL uses BDAM files and Enterprise Version does not support this file type. Has anyone worked in BDAM file conversion process?. If so, please do advise or share your thoughts in this thread.

Any small help from you is highly appreciated.

Thanks,
Srini

Terry_Heinze · Posted: Thu Aug 07, 2008 11:55 pm Post subject:

Well, I'll BDAMd; someone mentions the Basic Direct Access Method. Smile

The closest file organization I can think of would be a VSAM Relative-Record Data Set (RRDS).
_________________
....Terry

jsharon1248 · Posted: Fri Aug 08, 2008 11:57 am Post subject:

Terry, good one.

Srini, tough break. Sounds like fun, but will probably wind up being a tremendous headache. Never having worked with BDAM, my initial reaction is the same as Terry's. But I'm thinking KSDS rather than RRDS. I think you could use the BDAM key (or pointer or whatever it's called) as the key for the KSDS.

Terry_Heinze · Posted: Sat Aug 09, 2008 10:39 am Post subject:

The last time I dealt with a BDAM file (late 80s), the records were accessed via a relative record number -- that's why I think an RRDS VSAM file comes closest. A design change to make use of the flexibility of KSDS might be your best bet. I believe (don't remember for sure) that we retained our BDAM files when converting from VSE to MVS and COBOL '68 to COBOL II because the BDAM files were accessed via assembler calls.
_________________
....Terry

spalanis · Beginner Joined: 19 Jul 2006 Posts: 32 Topics: 15

THanks guys for your inputs.