Configuring a local mode topology

The configuration tasks required for a local mode topology.

About the local mode topology

The local mode topology on z/OS® is typically used with WebSphere® Application Server, using the ECI resource adapter to connect directly to a CICS® server. However, it is also possible to use a Java™ client application from UNIX System Services. Both situations require the same configuration settings but differ in where those configuration settings are specified. Configuration settings also vary depending on whether or not the EXCI protocol might be used to connect to CICS. If the EXCI protocol is not required, the only configuration required is for the native library path.

For more information about how to define the local mode configuration settings in WebSphere Application Server for z/OS see Deploying the ECI resource adapter on WebSphere Application Server for z/OS.

The sample JCL job SCTGSAMP(CTGTESTL) provides an example of configuring local mode for EXCI.

Local mode configuration settings

Configure the library path by setting the LIBPATH environment variable to the product /bin directory. For example, the following entry might be set in the STDENV section of the CTGTESTL job:
LIBPATH=/usr/lpp/cicstg/ctg910/bin

When using the EXCI protocol to connect with CICS, the following additional environment variables must be set:

Environment variables to configure local mode to use the EXCI protocol:

  • CTG_EXCI_INIT determines whether or not EXCI is loaded (default is YES if undefined).
  • CTG_PIPE_REUSE determines how allocated EXCI pipes are reused.
  • DFHJVPIPE defines the name of the pipe that CICS Transaction Gateway uses for EXCI calls.
  • DFHJVSYSTEM_nn defines the name and description of an EXCI connected CICS server to be returned in response to a request for the CICS_EciListSystems function.
  • STEPLIB identifies the library containing the default EXCI options and the EXCI load modules.

Path to include Java command:

When using a local mode Java client from UNIX System Services, the PATH might require updating to include the java command. For example, the following entry might be set in the STDENV section of the CTGTESTL job: 
PATH=<java_path>/bin
For more information about these environment variables see STDENV file.
Parent topic: Configuring
Related information:
Setting environment variables

Information Information
Feedback


Timestamp icon Last updated: Wednesday, 27 August 2014


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//configuring/topics/locgate.html