April 25, 2005 at 1:37 pm
Hello
Did anyone tried to retrieve row level data from Mainframe VSAM files using Host Integration Server?
I have a problem with that, I am already established the connection (
Any help will be appreciated.
Best Regards
M A
April 27, 2005 at 3:58 am
If you are accessing native VSAM, as opposed to VSAM used for IMS or DB2 databases, you need a VSAM ODBC driver installed on the mainframe. Talk to your mainframe support people about this.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 28, 2005 at 6:14 pm
Thanks 4 ur replay.
Actually now i can connect 2 the MF side even openning a recordset to a file but the problem now is that i got a garbig data
I dont know how to navigate across VSAM file records
Any help or Example will be appreciated.
Regards
April 29, 2005 at 3:21 am
The 'garbage' may be due to the mainframe data being in EBCDIC while Windows works in ASCII. It is possible to automatically convert from one format to the other.
You will need to find out the record structure of your VSAM data. In the same way as a SQL Server table has a record structure that allows programs to see (say) bits 1 to 24 as a date and bits 25 to 78 as a name, the same applies to a VSAM file. The problem is that the SQL record structure is held in the database and applied automatically, but the VSAM structure is documented outside of VSAM and is interpreted by each program that uses the VSAM file. You will need to ask the mainframe programmers to let you have a copy of the record structure. This is normally in the form of a COBOL copybook. You can then code that record structure either into Host Connect or directly into your application.
When you have the VSAM file structure, it should then be possible to make a automatic conversion from EBCDIC to ASCII.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply