Until recently, IBM Data Virtualization Manager for z/OS (DVM) could only create virtual tables or views under the default schema DVSQL. This limited the ability for multiple organizations to define virtual tables with the same name within a specific DVM server instance. However, in a previous blog post Multi-Schema Support in IBM Data Virtualization Manager for z/OS, by my colleague, Jim Wankowski, we saw how DVM was enhanced with the first phase of changes to support multiple schema created by using JCL batch files and a DVM utility.
Multiple Schema Support – Phase 2
December 2022 saw the delivery of Phase 2 of multiple schema support, which now allows you to create and manage multiple schema using the DVM Studio.
You can create multiple virtual tables with the same names in different schema. Different departments or functions in an organization can have tables with the same or similar names. The virtual tables with the same name can also point to different data sources.
After creating schema, you can view the new and existing schema using the DVM studio, and you can create new virtual tables under the required schema, as well as viewing any available virtual tables within any schema known to the DVM server.
Support for multiple schema can enhance security by giving you granular control, allowing you to configure the security at a schema level instead of just at the table level.
You can now additionally configure the security at the schema level and at the schema data set level. You can configure a schema, such that only specified users can run queries from the Studio, JDBC, ODBC, DVM DSClient on the tables that are part of that schema. You can secure the data set of a schema so that only specified users can create virtual tables or have read access to the virtual tables.
Watch this short video to see how to simply create a new user-defined schema using the DVM Studio
More information can be found in the IBM Documentation Centre by clicking this link => IBM Data Virtualization Manager for z/OS Users Guide