We have the following question on the implementation of a data masking solution using IBM Optim (z/OS version 7.1):
While creating access definitions for extraction and loading, the Subsystem name is not being configured (The panel does not have that option). But during a typical implementation where production data is copied to test with masking, where would the Optim components reside (Access definitions, table maps, column maps etc.)
Is it always that the Optim objects have to be split between the LPARs for a vanilla implementation (Access definitions for tables in Production LPAR sit on production LPAR and those for the tables in test LPAR reside in test LPAR)?
In other words, can Optim access definition created on a production LPAR access the tables in the test LPAR (and vice versa)? The overall idea here is to have the entire solution (Including all Optim objects) reside in production for moving production data to test with masking. Will this work? If it will, how?
This topic has been locked.
1 reply Latest Post - 2012-02-14T22:07:24Z by SystemAdmin
Pinned topic IBM Optim for z/OS - Access definitions and LPARs
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-02-14T22:07:24Z at 2012-02-14T22:07:24Z by SystemAdmin
SystemAdmin 110000D4XK31 PostsACCEPTED ANSWER
Re: IBM Optim for z/OS - Access definitions and LPARs2012-02-14T22:07:24Z in response to GanshOptim definitions are stored in a DB2 database. If the DB2 subsystem is shared across several LPARs, you can use the same common Optim definitions in each LPAR. If not, you will need to export the Optim definitions from one DB2 subsystem and import them into another Optim database in the second DB2 subsystem. If the LPARs have shared DASD, they can also use the same Optim libraries.