Attachmate Verastream Transaction Integrator Guide


Provide Host Access to Client Operations

The system configuration file is used to set system and global mapping parameters. These parameters, when correctly set, provide host access to your client operation.

To modify the system configuration file
  1. Navigate to the Attachmate\Verastream\TransactionIntegrator\<host_type>Server\Config directory and open the CICSConnectorConfig.xml file (CICS), or IMSConnCfg.xml (IMS) in a text editor.

  2. Edit the System parameters. You may need to obtain some of these values from your system administrator.

    This <System> parameter
    <ID> The host program you want to connect to. If you are connecting to an IMS host, the system id must consist of three alpha numeric characters.
    <Datastore ID>(IMS only) The IMS Connect datastore value for the IMS system to which the target IMS Connect will connect in order to execute IMS transactions.
    <IPAddress> The Internet Protocol address of the CICS host component or IMS Connect on the target mainframe.
    <IPPort> The port at which the CICS host component is installed or of the target IMS Connect.
    <Protocol> TCP/IP is the supported protocol.
    <DefaultHostCode> The number of the code page being used by the host program. See Host Code Pages for a complete list of supported code pages.

  3. If you are using CICS, supply the necessary mapping parameters. You may need to obtain some of these values from your system administrator.

    This <Mapping> parameter
    <SystemID> The name of the internal <system> tag that defines the particulars of the host program.
    <TaskID> The name of the client operation. In an IMS configuration file, client operations are madpped using task ids. The <TaskID> entries are the client operations associated with (mapped to) the <System> definition they are associated with.

  4. Optional. Set the <globalParams> to "true" to log errors, warning, and information.

    If you use the default values, log and trace files are created in the current directory of the running server, CICSServer or IMSServer. To write these files elsewhere, change the path, as follows:

    • In a Windows environment

      <logfile>C:Documents and Settings\user_name\My Documents\cicsevents.log</logfile>

      <tracefile>C:Documents and Settings\user_name\My Documents\cicsevents.log</tracefile>

    • In a Unix environment



    Where logfile = location of logging events and tracefile = location of tracing events.

  5. Save the configuration file.
Related Topics
Bullet Setting Up the Runtime Environment
Bullet Provide Client Access to Runtime Servers
Bullet Capturing Host Data