z Open Dataz Open Data
Overview
  • odp-elastic-samples
  • odp-prometheus-samples
  • cics-performance-analyzer-elastic
  • ims-performance-analyzer-elastic
  • transaction-analysis-workbench-elastic
  • ims-connect-extensions-analysis-splunk
  • Db2 Query Monitor Starter Dashboards
  • Instana Configuration Topics
GitHub
Overview
  • odp-elastic-samples
  • odp-prometheus-samples
  • cics-performance-analyzer-elastic
  • ims-performance-analyzer-elastic
  • transaction-analysis-workbench-elastic
  • ims-connect-extensions-analysis-splunk
  • Db2 Query Monitor Starter Dashboards
  • Instana Configuration Topics
GitHub
  • IMS Connect Extensions Splunk starter applications

    • Overview

      • Introduction
      • Requirements
    • Configuring IMS Connect Extensions feed

      • Configuring the feed job for OTMA workloads
      • Configuring the feed job for Open Database workloads
    • Installing IMS Connect Extensions Splunk starter applications

      • IMS Connect transaction analysis
      • IMS Connect Open Database analysis
      • Using the application

Configuring the feed job for Open Database workloads

You need to configure IMS Connect Extensions feed job in order to send Open Database requests from IMS Connect.

The following JCL example defines a feed that forwards data from three IMS Connect systems: ICONP01, ICONP02, and ICONP03. The feed consists of selected fields in JSON Lines format sent over unsecure TCP/IP (no SSL/TLS) to port 1616 on the host named analytics.

NOTE

cexpre.SCEXLINK is an SMP/e target library of IMS Connect Extensions.

//UIDCEX   JOB NOTIFY=&SYSUID
//CEXCA20  EXEC PGM=CEXCA20P
//STEPLIB  DD DISP=SHR,DSN=cexpre.SCEXLINK
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
HWSID=ICONP01,ICONP02,ICONP03
DESTINATION=JSON
  HOST=analytics PORT=1616
  FIELDS(hwsname,
  ipaddress,
  port,
  userid,
  logontk,
  safelap,
  resptime,
  odbuowct,
  odbsvrcod,
  odbsecchk,
  odbcorrtoken,
  odbodbmname,
  odbin_alias,
  odbin_psbname,
  odbout_alias,
  odbout_odbname,
  odballocpsbelap,
  odbdeallocpsbelap,
  odbmsgelapsed,
  dlifunction,
  dliuowsq,
  dlicount,
  dlirows,
  dlicommitted,
  dlirolledback,
  dlisvrcod,
  dlipcbname,
  dlidatabase,
  dlimsgelapsed,
  dliuowelapsed,
  zostoken
  )
/*

The list of fields in this example JCL matches the fields used by the Splunk app mentioned later in this recipe.

Example output line:

{"time":"2024-1-01T15:25:03.123456Z","type":"ims-ca20-od","hwsname":"ICONP01","resptime":0.654321, ...}

For more details, see the feed JCL and list of feed fields in the IMS Connect Extensions documentation in IBM Knowledge Center.

Last Updated: 3/13/24, 8:05 AM
Contributors: Hiroyuki Fuchiue
Prev
Configuring the feed job for OTMA workloads