Configuring additional Data Virtualization Manager servers

About this task

You must complete the following steps for each additional Data Virtualization Manager server you start. Sample JCL is provided in member AVZGNSUB located in the hlq.SAVZCNTL data set to assist with steps 1 - 5.

Procedure

  1. Create a VSAM data set, for the additional Data Virtualization Manager server.
  2. Make a copy of the SEF data sets for the new Data Virtualization Manager server. Copy the following data sets: 
    HLQ.ATH.SAVZEXEC
HLQ.CMD.SAVZEXEC
HLQ.EXC.SAVZEXEC
HLQ.GLV.SAVZEXEC
HLQ.PUB.SAVZEXEC
HLQ.RPC.SAVZEXEC
HLQ.SQL.SAVZEXEC
HLQ.TOD.SAVZEXEC
  3. Optional: Use the COPYMAP step that is located in the hlq.SAVZCNTL(AVZGNSUB) member.
    Map data sets can be shared across subsystems. However it is advisable to have a separate map data set for each subsystem when separating application environments. If maps are shared across subsystems, you should make manual refreshes across the other subsystems when map changes are made. Map changes are also recognized at Data Virtualization Manager server installation.
  4. Optional: Create and copy a new HTXLIB for Streams by using the COPYHTX step that is located in the hlq.SAVZCNTL(AVZGNSUB) member.
    If you run custom RPC programs, RPC data sets are required. RPCLIB.PRELOAD is an optional RPC library that you can preload RPCs into a cache.
  5. Create a new startup JCL procedure. The AVZS member of the hlq.SAVZCNTL library contains sample JCL procedures for running the Data Virtualization Manager server main address space (started task). You should place the AVZS PROC in a procedure library where the z/OS START command searches (this may be SYS1.PROCLIB). Optionally, you can change the name of the procedure to reflect the new Server you are starting. You must change the SSID parameter in the startup procedure to reflect the additional subsystem name.
  6. Define the new started task to the security product.
  7. Obtain or define a new TCP/IP port or VTAM application ID, depending on the communication protocol you are using.
  8. Create a new AVZSIN00 member. Customize this Data Virtualization Manager configuration member to configure your interfaces and run time options.
  9. Create a AVZSINEF member in the SYSEXEC concatenation where AVZS refers to the new subsystem name you are creating.
    You can make a copy of your existing AVZSINEF. This member is used for initializing global variables at Data Virtualization Manager server startup. If you modified the default AVZSINEF, you should review these changes to determine whether you want them in your new Data Virtualization Manager server. If this is not done, the REXX interpreter (SDBI or SDBX command processor) is not able to locate the specified REXX program in the data set allocated to the SYSEXEC DDNAME (for SDBI) or in the specified data set. You receive a warning message at startup of the Data Virtualization Manager server, however, you can ignore this message.
  10. If the two Data Virtualization Manager servers are running at different versions set up a new REXX/EXEC to invoke the ISPF application.
    Modify the LLIB statement in the REXX/EXEC to point to the Data Virtualization Manager server load library. This is not necessary if you are running at the same version but a different maintenance level. You may receive a warning regarding load library maintenance mismatches when entering the ISPF panels, however this message is informational only.