Db2 Tools for z/OS

Db2 Tools for z/OS

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

Multi-Schema Support in IBM Data Virtualization Manager for z/OS

By Jim Wankowski posted Thu November 10, 2022 10:17 AM

  

Introduction

Schemas are a way of logically categorizing groups of relational objects.   A schema can contain tables, views, nicknames, triggers, functions, packages, and other objects.  A schema is itself a database object which is explicitly created using the CREATE SCHEMA statement. There can be multiple schemas defined withing a database.  Schemas provide the ability to create like named objects in the same database without name collisions.  Schemas also provide a level of security, where users may be granted access to only objects within a specific schema.

Until recently IBM Data Virtualization Manager could only create virtual tables or view under the schema DVSQL.  This limited the ability for multiple organizations to define virtual tables with the same name withing a specific DVM server instance.

Multi-Schema Support

Data Virtualization Manager for z/OS now allows users to create and manage multiple schemas for tables and views.  This feature allows users to create virtual tables with like names in different schemas.  This feature provides more flexibility with the virtual objects being created under a single DVM server as well as providing better security as the user can add or define security for each schema.

Requirements

  • PTF 1.0.115 or above
  • DVM Studio 225 or above

Multi-Schema support is being introduced in multiple phases:

  • Phase 1 (August 22) – Create/Manage schemas via JCL Batch
  • Phase 2 (Q422)– Create new schemas via DVM Studio
  • Phase 3 (Q123) – Export/Edit schemas from studio

In phase 1 of DVM Schema support, all management is done via JCL.  The JCL can be found in your hlq.SAVZCNTL dataset.

Creating a Schema

AVZMSCHM 

This job will define your schema, and the associated map dataset.  Each Schema defined, must have its own unique mapping dataset.

There is currently a limitation of 200 schemas per DVM server.

 

Migrate Schemas

AVZGNMPM

This job will allow you to migrate schemas to different DVM servers (ie. TEST => PROD)

You can move virtual tables to a different schema on the same server by leaving the SOURCE, and TARGET SSID’s the same.





ISPF Interface
Once you have your schemas created you can view them from the DVM ISPF interface Data Mapping option “D.1”

 



 

Creating Virtual Tables for a specific SCHEMA.

From the DVM Studio right mouse on virtual tables and select “Create Virtual Table(s)”

 

New dropdown to select the desired schema:

 


 

 

Queries are now prefixed with the new schema name:

Conclusion

The new multi-schema support provides for greater versatility within DVM.  Multiple projects can now maintain objects with common names by using a unique schema name and securing their objects at the schema level. 
For more detailed information on how to set up multi-schema support, refer to the IBM doc here: Multiple schema support

 

       

 


#Db2Toolsforz/OS
0 comments
38 views

Permalink