Cloning Environment Libraries

You can use and update the cloned environment either of the following methods depending on your need.

Multiple Set of Libraries - Use this method when requiring a separate and independent product installation to manage environments. This solution requires maintenance to be applied for each set of libraries and DB2 subsystem Websync files and scripts.
Single Set of Libraries - Use this method when you do not need to work in an independent manner and are using the same set of libraries for all the DB2 subsystem with the Data Express Knowledge base installed. This solution requires maintenance to a single set of libraries but multiple applications of Websync scripts for each DB2 subsystem.

Multiple Set of Libraries

To create different Data Express installations, you must copy the entire library set, change the names, and create a new PARAMETERs file.

Copy all the libraries created at the end of the installation procedure, changing the names after copying by adding the text NEW to the end of the copy file string.
For example, URADAR.DATA.* should be changed to URADAR.DATANEW.* when copied.
Create a new PARAMETER FILE describing the new DB2 subsystem parameters. You must copy the original PARAMETER FILE into new one with a different name, then include it into new CLIST created under the newly created libraries.
For example, URADAR.SEQ.KBPARAM should be copied to URADAR.SEQ.KBPARAM.NEW.

Once copied, change the following DB2 related information included in the new parameter file.
- DSN on which the cloned database was created
- Name of the cloned storage group
- Name of the cloned DB2 database
- Name of the cloned owner of the cloned DB2 tables
- Name of the cloned plan and cloned collection
- Names of the cloned buffer pools for data and indexes
- Plan of the cloned DB2 system DSNTIAD
- Plan of the cloned DB2 system DSNTIAUL
- Names of the DB2 system libraries (RUNLIB and SDSNLOAD)
- Name of the new parameter file for the cloned environment.

Check and modify the CLIST(MFDATA) to contain the references to new libraries.

      PROC 0 URPROJ  (URADAR)          +
      URGROUP (SV41)            +
      URGRPTF (SV41WRK)         +
      URGRPER (SV41PER)         +
      URSEQPAR (URADAR.SV41.SEQ.KBPARAM)

Check and if needed modify the following skeletons containing job cards:
- KURJBLIB
- KURJBLPK
- KURJBNAM
- KURJBNPC
- KURJBNPK
At the end of the copying process, create and execute BIND packages. See Create the Database for information on creating and executing BIND packages.

Single Set of Libraries

To create a single Data Express installation managing different DB2 subsystems, you must create a new CLIST and PARAMETER FILE starting from the Data Express 4.0 existing libraries.

This phase allows the copying and the editing of the parameter's procedure file.

Copy the original CLIST MFDATA into a new CLIST with a different name.
For example: URADAR.DATA.CLIST(MFDATA)* should be copied to URADAR. DATA.CLIST(MFDATA2)
Create a new PARAMETER FILE describing the new DB2 subsystem parameters. you must copy the original PARAMETER FILE into new one with different name, then include it into new CLIST created under the newly created libraries.
For example, URADAR.SEQ.KBPARAM should be copied to URADAR.SEQ.KBPARAM.NEW.
Once copied, change the following DB2 related information included in the new parameter file.
- DSN on which the cloned database was created
- Name of the cloned storage group
- Name of the cloned DB2 database
- Name of the cloned owner of the coned DB2 tables
- Name of the cloned plan and cloned collection
- Names of the cloned buffer pools for data and indexes
- Plan of the cloned DB2 system DSNTIAD
- Names of the DB2 system libraries (RUNLIB and SDSNLOAD)
- Name of the new parameter file for the cloned environment
At the end of the copying process, create and execute BIND packages. See Create the Database for information on creating and executing BIND packages.