Update the CTG environment file
The CICS Transaction Gateway must point to the UNIX file system where the MainView for CICS monitoring code resides.
The file system:
- is provided by BMC as an SMP/E file system during installation of MainView for CICS in a data set named hlq.BDRZFS
- should be treated as a load library and be shared only by systems that receive MainView for CICS maintenance at the same time
- should not be combined with any other data set, including any other BMC product file
- has to be mounted and accessible to the CICS Transaction Gateway address space
Update the CTG environment file to include the path to hlq.BDRZFS, which contains the code that implements the MainView for CICS CTG request exit.
- The environment file is a PDS member pointed to by the setting of the STDENV DD statement in the startup JCL for the CTG daemon.
Update the CLASSPATH to include the path to the UNIX file (BDRZFS) that contains the MainView for CICS Oracle Java exit.
Format: CLASSPATH=classpath for mvcics.jar; classpath2...
Update the LIBPATH to include the path to the UNIX file (BDRZFS) that contains the MainView for CICS C++ code.
Format: LIBPATH=libpath for mvcics libraries ; libpath2...
The UNIX file must be mounted and accessible to the gateway.
In the following example, notice that the CLASSPATH and LIBPATH statements refer to the same directory:
/var/BCVM/CMR62/bmc/bdr/v62/MVCICSctg.jar:/
/usr/lpp/ctg/classes/ctgclient.jar:/
/usr/lpp/ctg/classes/ctgserver.jar:/
/usr/lpp/ctg/classes/ctgsamples.jar
LIBPATH=/var/BCVM/CMR62/bmc/bdr/v62/
Related topic