Skip to main content

DB2 for Mainframe

Configuration

It is necessary to configure DB2 for Mainframe databases for both the Masker and Discover IDPs.

  1. Create a Z/OS user id to be used as the DB2 user id for masking (for example, "dguser").

  2. From a Windows Db2 Command Line (on the PK Protect Server) prompt, perform pre-installation steps:

    1. Run dg_db2_pre_install_ZOS.cmd

      Usage:   dg_db2_pre_install_ZOS.cmd <SUBSYSTEM_NAME> <SYSADM USERID> <SYSADM PASSWORD> <MASKER USER ID> <MASKER SCHEMA> <DG DB NAME> <STOGROUP> <BUFFERPOOL> <INDEXBP>

      Example: dg_db2_pre_install_ZOS.cmd DALLAS9        

      ibmuser         mypassword        dguser            DGUSER          DG           stogrp1    bp32k        bp0

      1. <SUBSYSTEM_NAME> The name of the db where masking will take place.

      2. <SYSADM USERID> The name of the db2 sysadm user id (required for tablespace and bufferpool creation).

      3. <SYSADM PASSWORD> The db2 sysadm password.

      4. <MASKER USER ID> The user id that will be used in DgMasker to connect to the database for masking. Recommendation is ‘dguser’.

      5. <MASKER SCHEMA> The name of the DgMasker schema to be used for creating the DG tables. Recommendation is ‘DG’.

      6. <DG DB Name> IP Address of DB server.

      7. <STOGROUP> The storage group where the dg objects database will be created.

      8. <BUFFERPOOL> The name of the buffer pool that will be used for the dg objects database

      9. <INDEXBP> The name of the index buffer pool that will be used for the dg objects database.

        Check the output file for errors in dg_db2_pre_install.log from a Linux Db2 Command Line (on the DG Server) and perform the appropriate grants.

  3. To mask a table in a subsystem the "dguser" id must have ALTER, INDEX, SELECT, REFERENCES, UPDATE, and TRIGGER privileges. To grant privileges to all tables in the Subsystem, run the following steps:

    From a Linux Db2 Command Line (on the DG Server), perform the following grants.

    Usage:   dg_db2_grants.cmd <DB_NAME> <DB2 SYSADM USERID> <DB2 SYSADM PASSWORD> <DGUSER ID>

    Example: dg_db2_grants.cmd SUBSYSTEM  ibmuser             password              dguser

  4. A Z/OS WLM Address Space for Java is required for DgMasker functions.

*Note: If you already have a WLM Address Space for Java, you may skip this step. 

  1. If you do not have a WLM Address Space for Java, please refer to IBM documentation for assistance in creating the WLM Address Space for Java.

Masking is now ready to be run from the DgMasker application. On the GUI, make sure to set the Package Schema. "Set Config Parameters" --> Package Schema = DGUSER. More details on Setting the Package Schema can be found in the User Guides chapter on Masker tasks.

Discover

To configure the Discover IDP, you must bind the DB2 and set up the user account with the necessary permissions.

  1. On the machine hosting the DB2 Connect client, open a DB2 command window and navigate to the SQLLib/bnd directory. The default directory is:
    /opt/IBM/sqllib/bnd

  2. Connect with a userid that has SYSADMIN authority or has BINDADD authorization. Enter the following commands:

    CODE
    db2 terminate
    db2 CONNECT TO <dbname> user <USERID> using <PASSWORD>
    db2 BIND db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE 
    db2 BIND @db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD 
    db2 BIND @db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD 
    db2 terminate
    
    Where:
    <dbname> is the database subsystem.
    <userid> is the DB2 userid.g
    <password> is the DB2 userid password.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.