VSAM方解石 [英] Calcite for VSAM

问题描述

我正在尝试从Java的COBOL程序和外部程序中公开大型机文件，以便更动态地使用.

I am trying to expose Mainframe files for more dynamic use from both COBOL programs and external programs in Java.

我的阅读显示我可以配置COBOL以使用JDBC连接.这可能只是JCL中的配置，但我认为它更多是一个预处理过程.

My reading shows that I can configure COBOL to use a JDBC connection. This may be just configuration in the JCL but I assume it is more of a preprocess.

我还发现JzOS库可以从JAVA本身访问VSAM数据存储.

I also found the JzOS libraries will give access to the VSAM datastores themselves from JAVA.

因此，从技术上讲，我认为这是可能的，但找不到任何相关文章.我知道这将成为一种极端情况，但是我喜欢Calcite将这些作为标准JDBC对象公开的想法.

So technically I think this is possible but could not find a single post on it. I know this is getting to be an edge case but I like the idea that Calcite will expose these as standard JDBC object.

有何想法?问题 ?有问题吗?

Thoughts ? Issues ? Concerns ?

推荐答案

请理解...之间有很大的区别.

Please understand there is a big difference between...

• 技术上可行的可能性
• 商店允许的物品
• 根据您的要求，有什么可能提供健壮且可维护的解决方案

这是三件事.我们中有些人的生活经历使我们不愿回答关于技术上可行的问题，而没有提及您的商店所允许的内容或正在解决的实际业务需求.

These are three very different things. Some of us have life experiences that make us reticent about answering questions regarding what is technically possible absent any mention of what is allowed in your shop or what the actual business requirement is that is being solved.

大型机已经存在了半个多世纪，许多商店都为技术问题提供了标准的解决方案.有时解决方案是不要这样做，而这是我们 所做的."根据您的技术人员的建议或您的车间标准进行工作是职业上的限制.

Mainframes have been around for over half a century, and many shops have standard solutions to technical problems. Sometimes the solution is "don't do that, and here's what we do instead." Working against the recommendations of your technical staff, or your shop standards, is career limiting.

好的，样板问题.

VSAM不是DBMS.它具有DBMS的某些特性，但它本身并不是一个.

VSAM is not a DBMS. It has some of the characteristics of a DBMS but it isn't one itself.

共享要求可能会让您头疼. VSAM文件使用SHAREOPTIONS参数定义，该参数指示可以同时读取和写入多少个进程.请记住，自由定义这些意味着每个应用程序必须控制写入的序列化，并且所有应用程序共同负责数据的完整性.

The sharing requirements may give you a headache. VSAM files are defined with a SHAREOPTIONS parameter indicating how many processes can simultaneously read and write. Keep in mind that defining these liberally means each application must control serialization of writes and all applications are collectively responsible for data integrity.

请考虑将应用程序 编写在您的控制和知识范围之外，这些人不了解这些VSAM数据集是否有其他应用程序可以读取/写入.

Consider that applications will be written outside your control and knowledge by people who do not understand there are other applications reading/writing from/to these VSAM datasets.

我将通过通过Web服务提供访问来解决此问题.不是简单的CRUD，而是SOA风格的特定于业务的功能. CICS是您的朋友.

I would approach this by providing access via a web service. Not simple CRUD, but business-specific functions SOA-style. CICS is your friend.

考虑在大型机上使用DBMS而不是VSAM文件.

Consider using a DBMS on the mainframe instead of VSAM files.

请尝试避免内部平台效应.

此外，此问与答； A可能很有趣.

Also, this Q&A may be of interest.

这篇关于VSAM方解石的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！