You seem to be the expert in this topic.
In reading previous posts on this board I am of the belief that you have successfully set up and accessed your Unisys DMS using OLEDB.
I am an Oracle/SQL Server guy who has been tasked with creating a consolidated database (small warehouse) where one of the data sources is sitting on a unisys mainframe.
What I would LIKE to do is to create a SQL Server linked server to the mainframe and create a series of views to feed the warehouse. The type of access would be single user, read-only and the queries, though large (relative term), would be run on a scheduled basis.
All that I have read, so far, would lead me to believe that this would be a good solution.
I have made several requests to get the mainframe administrator to configure the system for OLEDB access so we could do some testing but I am getting a lot of pushback (filtered through several layers of bureaucracy). The gist of what I am hearing is that it won't work, is not a good product, it will adversly affect performance of existing systems...
I have already contacted a person who is using ODBC access to drive a web enabled application. I would really like to get input from someone who is using OLEDB.
I am generally interested in the size of your Mainframe DMS, what you are using the OLEDB layer for, The generic configuration, the volume of traffic that you are placing on it, and, in particular, the performance impact that it has on your mainframe (since this seems to be the crux of the official argument).
I have already read:
--Network Database OLE DB Data Provider for ClearPath OS 2200 Users Guide
--Data Access Modeller Users Guide.
As you can likely tell, I am simply trying to build an argument to TRY this and I need to get the others excited about the possibilities.
Anyway, sorry for the long post. Any help, advice, pointers on successful implementations would be greatly appreciated.