OMEGAMON XE for CICS V530 Long client presentation

© 2014 IBM Corporation
IBM Tivoli OMEGAMON XE for CICS on z/OS
and OMEGAMON XE for CICS TG on z/OS
V5.3.0
OMEGAMON for CICS development

IBM Software Group | Cloud & Smarter Infrastructure
2
What this deck is
 This deck comprises several main sections, and is intended as source
material from which you can build your own presentations.
 The sections are:
• OMEGAMON XE for CICS on z/OS v530 overview
o This includes an overview of the new features of the v530 release including an
overview of history, imbedded data and some key scenarios.
• Installation and Upgrade considerations
o This section lists a variety of install considerations, including SDA and JCL-less
installs.
• CICSplex Agent Preferences
o New in v530, this section explains the CICSplex Agent Preferences feature.
• Historical Considerations
o History is a major component of the v530 release, and this section explains the
available features, including related tasks, ATF and NTH.
• OMEGAMON XE for CICS TG on z/OS
o OMCICSTG is a component of the CICS product, and is included in the install
package. This section shows what’s new in the OMCICSTG component.

3
What this deck is
 Other sources of information.
• There are an increasing number of OMEGAMON related blogs, and these can be found
at:
• https://www.ibm.com/developerworks/community/blogs/5e65990a-9690-42e2-93b1-c2267be76
• Log in, most of the blogs are tagged with OMEGAMON

4
OMEGAMON XE for CICS on z/OS Timeline
4
CICS/TS
v3.1
2005
2009
2012
2014
V410 – Exploitation of CICS/TS v3.1. CICS code rearchitected to reduce
resource consumption and made threadsafe, integration with CICS Tools.
V420 – Exploitation of CICS/TS v4.1 and introduction of CICS
Transaction Gateway monitoring
V510 – Added PARMGEN configuration and
SDA support. Enhanced 3270UI introduced for
OM CICS component. SLA is zIIP enabled.
V530 – Enhanced 3270UI
improvements include history and
Embedded Data. Bottleneck and
Region Overview zIIP enabled.
CICS/TS
v5.1
CICS/TS
v5.2
CICS/TS
v3.2
CICS/TS
v4.1
CICS/TS
v4.2

5
OMEGAMON XE for CICS on z/OS v5.3.0
• The OMEGAMON XE for CICS on z/OS enhancements include;
o Simplified requirements for JCL changes
o Increased zIIP enablement
o Improvements to task history, including CICSplex Application Trace Facility,
CICSplex historical task views
o Embedded data scenarios – CICS & Messaging, CICS & Storage, CICS & CICS
TG and CICS & z/OS
o Resource Limiting for GDSA and Container storage
• OMEGAMON XE for CICS TG on z/OS enhancements include;
o Availability of reports in the Enhanced 3270UI
 History, Embedded data etc.
o Support for multiple WebSphere servant address spaces

6
OMEGAMON XE for CICS on z/OS - integration
The main panel, KOBSTART, is populated with data from
all of the installed subsystem monitors. In this example we
see summary data sourced from the z/OS, Messaging
and CICS monitors.

7
OMEGAMON XE for CICS on z/OS - CICSplex
 Your definition of a CICSplex lets you see information about the CICS
regions that you have defined in that CICSplex, limits the queries for
information to the group of regions and allows you to limit, for example,
the FIND command or Service Level Analysis to the group you are
interested in.
• You can specify rules which categorize regions into different CICSplexes, or
use existing your existing CPSM definitions.
• You can also specify rules which determine the location of the CICSplex
agent.

8

9
 On the previous slide there are three CICSplex names;
• OMEGPLEX is the default name
• SRPLEX is a name specified in an OMEGAMON rule
• TESTPLEX is a CPSM name
 CICSplex names can be derived from any of those three sources.

10
In the example shown here, FIND PROGRAM KOCOME00 was used
to locate all defined instances across the selected CICSplex

11

12

13
OMEGAMON XE for CICS on z/OS – CICSplex Storage

14
OMEGAMON XE for CICS on z/OS – Region Overview

15
OMEGAMON XE for CICS on z/OS – related tasks
Selecting the CEMT task in the first report will result in a switch, in
context, from that task in CICS51G1 to the related task in CICS51G2

16
OMEGAMON XE for CICS on z/OS - SLA

OMEGAMON XE for CICS v530 and zIIP
 There are three components of the OMEGAMON XE for CICS on z/OS
product that are zIIP enabled
 In OMEGAMON XE for CICS on z/OS v5.1.0
• The Service Level Analysis summarization routine was zIIP enabled and has shown
significant reduction in CPU for customers using SLA.
 In OMEGAMON XE for CICS on z/OS v5.3.0
• Bottleneck Analysis was zIIP enabled
• The CICS Region Overview agent code was zIIP enabled

18
OMEGAMON XE for CICS on z/OS – Take Action
 The TEP allows for situations which take actions automatically
 The enhanced 3270 UI allows you to manually take actions
• All commands can be protected via a standard SAF call

19
OMEGAMON XE for CICS on z/OS – new
resources

20
OMEGAMON XE for CICS on z/OS – Task History

21

22

23
OMEGAMON XE for CICS on z/OS –
CICSplex Wide Trace

24
OMEGAMON XE for CICS on z/OS – Near
Term History
Each table can be configured as required,
the data will then be available for historical
analysis. . .

25
OMEGAMON XE for CICS on z/OS – Near
Term History

26
OMEGAMON XE for CICS on z/OS – Near Term History

27
OMEGAMON XE for CICS on z/OS – embedded data
These examples show embedded data,
one is data from the messaging product
displayed in the CICS Transaction
Analysis report, the second is data from
the Storage product displayed in the
CICS RLS File Details report.

28
OMEGAMON XE for CICS on z/OS –
embedded data
This example shows a new tab in the
CICS region overview report, the z/OS
Address Space. The second sub-panel
is provided by the OMEGAMON XE for
z/OS monitor.

29
OMEGAMON XE for CICS on z/OS - Startup
Optional CICS INITPARM parameters reduce the requirement for
CICS JCL changes, and add the RESTART capability.

30
 OM CICS v530 introduces support for JCL-less installs
 Prior to v530
• DFHRPL requires &hilev.xKANMOD
• RKANMODR DD card defines &hilev.xKANMOD
• KC2GLB
• RKC2XM
• RKCPXM
 In v530
• Sample JCL in &hilev.xKANSAM(KOCCSD) defines the program, transaction and a
library
• INITPARM data, specified in the CICS System Initialization Table (SIT) can specify the
required parameters, e.g.
INITPARM=(DFHDBCON='CC,IC1C',
KOCOME00='KC2_XMIT=07,KCP_XMIT=07,RETRY(20,25),KC2_GLOBAL=#')
• LIST option prints diagnostic messages

31
 V530 continued
• JCL takes precedence
o If a customer starts a CICS region with existing JCL definitions, the code will use
what’s discovered in the JCL.
 When might they use this ?
• If the customer wanted to change the globals, or any of the DD cards used in a startup
they can use OMEG REMOVE followed by OMEG INIT,KC2_GLOBAL=xx
• If they apply maintenance they can use OMEG REMOVE, discard the CICS LIBRARY
definition, modify the definition and reinstall it, and then OMEG INIT (with the LIST option
if they want to check that the new libraries were allocated)
 Any limitations ?
• The new code relies on the datasets using our naming conventions, so if KOCOME00 is
loaded from &hilev.xKANMODR the code will attempt to allocate a matching xKANMOD
dataset.
• CUSTOMER.TKANMODR.TEST1 would not work.

32
OMEGAMON XE for CICS on z/OS – Startup
RETRY(30,20) specifies that the connection to the common interface will be
retried every 30 seconds, 20 times.
KC2_XMIT=07 will attempt to allocate a DD card, RKC2XM07
KCP_XMIT=07 will attempt to allocate a DD card, RKCPXM07
KC2_GLOBAL=# will attempt to allocate a DD card, KC2GLB#
An optional parameter, LIST, will print diagnostic messages.

33
OMEGAMON XE for CICS on z/OS - startup

34
OMEGAMON XE for CICS on z/OS - startup
• OMEG CANCEL will stop attempts to reconnect when the RETRY option
is used.
• LIST can be added to an OMEG command if it is issued via a terminal
OMEG INIT, LIST
OMEG REMOVE,LIST

35
OMEGAMON XE for CICS on z/OS - RLIM
 Resource Limiting (RLIM) has been enhanced to add support for
container storage and GDSA storage.
 Note the spelling of CONTAINR
 Menu System (classic) GLOB commands support the new options,
• GLOB RLIM
• GLOB RLIM GDSA
• GLOB RLIM CONTAINR

36
OMEGAMON XE for CICS TG on z/OS
Further drilling-down leads to flow-level monitoring for an individual
transaction, whether it’s within a WebSphere Servant region or a
Gateway daemon.
Further drilling-down leads to flow-level monitoring for an individual
transaction, whether it’s within a WebSphere Servant region or a
Gateway daemon.

37
Historical Analysis

38
Slow Throughput
Compare throughput
performance on a
region-by-region
level, or by throughput
to each CICS server.
Metrics supported for
both EXCI and IPIC
connections.

39
Slow Throughput
Data from selected CICS region embedded into
CICS TG details allowing detailed analysis and
fast navigation when tracking transaction issues

40
OMEGAMON products – CICS/TS v5.2 Support
 On June 13, 2014 IBM CICS Transaction Server for z/OS V5.2 became generally available. Toleration
support is available via the service stream as follows:
 OMEGAMON XE for CICS on z/OS
APAR OA45295
PTF V420 UA73839
PTF V510 UA73840
 OMEGAMON XE for CICS TG on z/OS
APAR OA45296
PTF V420 UA73841
PTF V510 UA73842
 OMEGAMON End-to-End
APAR OA45374
PTF V620 UA74290
 ITCAM for Transactions/CICS on z/OS V730
OA45409
PTF tbd
 ITCAM for Transactions/CICS on z/OS V740
OA45444
PTF tbd
 OMEGAMON XE for IMS on z/OS
No maintenance required

41
OMEGAMON XE for CICS on z/OS
SMSVSAM maintenance for RLS imbeds
 For displaying embedded data about VSAM RLS datasets from OMEGAMON for
Storage in OMEGAMON for CICS E3270UI workspaces, please ensure that the
following DFSMS and OMEGAMON for Storage maintenance is applied to your
SMPe target libraries:
 OA41786
 OA42288
 OA42798
 OA43380
 OA43381
 OA43776
 OA44707
 OA45048
 OA44589
 This PTF list was accurate at the time the imbeds were developed. If problems are observed you should
also check for the latest status with Rocket Software’s support.

42
Scenarios
 Three brief scenarios, which were all used as input to the development process.
• CICS and Messaging
 OMEGAMON XE for CICS v530 and OMEGAMON XE for Messaging v730
• CICS and z/OS
 OMEGAMON XE for CICS v530 and OMEGAMON XE for Sysplex v530
• CICS and VSAM RLS
 OMEGAMON XE for CICS v530 and OMEGAMON XE for Storage v530 (Check required maintenance for
SMSVSAM)
 All came from customers during the Early Adopter Program meetings which were
run alongside the development of the OMEGAMON v530 products

43
Scenario – CICS and Messaging
 We are assigned to an Operations Help Desk. Calls about CICS systems are very often
passed to us for initial investigation. Our phone rings.
 SYMPTOMS - the caller is Jim, who works with one of our CICS applications teams. We
usually hear from Jim whenever there are CICS problems. Jim tells us that their CICS
region CICSDE03 on MVS LPAR SP22 has been running normally all day, but recently their
staff noticed that one of their feeder queues, ABCQ, has a queue depth of 0. This is very
unusual, there are generally some messages to be seen on this queue at all times.
 They are also receiving reports from their staff that some CICS applications are returning
MQRC=2033 error codes, meaning that there are no messages on the targeted queue.
They looked at some of their CICS application traces and noticed that the MQ error codes
all have to do with queue ABCQ.
 So Jim called the Operations Help Desk.
 The complaint is reported about a specific queue, ABCQ, connected to Queue Manager
Q721, so we begin troubleshooting by starting an OMEGAMON Enhanced 3270 UI session
to see the Queue Manager on SP22.

44

45

46

47

48

49

50

51

52
Scenario – CICS and VSAM RLS
 We are assigned to an Operations Help Desk. Calls about CICS systems are very often passed to us
for initial investigation. Our phone rings.
 SYMPTOMS - the Capacity Planning Team is looking into some issues with VSAM RLS clusters, and
they want to know if we have real-time data about any CI/CA splits charged to VSAM RLS clusters
allocated to CICS, and do we have any real-time data about the dispersal of VSAM RLS clusters among
CICS regions?
 We explain that yes, we do. We can see in real-time raw counts of CI/CA splits charged against a
VSAM RLS cluster, we can identify the regions to which that cluster is allocated, and we can see the
OPEN/CLOSE status of that cluster in each of the CICS regions. We can do this using an OMEGAMON
E3270UI session, working from OMEGAMON/CICS with embedded data from OMEGAMON/Storage.
 The Capacity Planning Team asks us to demonstrate the navigation to that data using the E3270UI for
VSAM RLS cluster TDCICST.JVT.CICSTEST.TESTVSAM. They're working with the programming staff
that's responsible for that cluster, and they want to confirm that the cluster is dispersed to the CICS
regions is as they have been told. They also know that the VSAM RLS cluster is processed in CICS and
in batch, and they want to know, in real-time, how many CI/CA splits are occurring during online
processing. There is a long-running task, JVTW, executing in CICSDE02 that processes using the
VSAM cluster in question.

53

54

55

56

57
Scenario - CICS and z/OS – High CPU
 We are assigned to an Operations Help Desk. Calls about z/OS systems
are very often passed to us for initial investigation. Our phone rings.
 SYMPTOMS – one of our applications teams reports that response times
in a CICS region, CICSDE03, on LPAR SP22 are lengthening
considerably and most tasks as not completing as they should. We on
the Help Desk have seen this sort of behavior before and it often means
that a CICS task has gone rogue, consuming so much CPU that no other
work is being done in the region.
 Working on this assumption, we engage an E3270UI session to see the
summary list of address spaces on SP22, looking to see if CICSDE03 is
consuming more CPU than would usually be expected.

58
Scenario – CICS and z/OS – High CPU

59

60

61

IBM Tivoli OMEGAMON XE for CICS on z/OS V5.3.0
Install and Upgrade Planning

63
Contents
 Install (Pristine / New)
• Requirements and Dependencies
• Packaging
• What's New
 Upgrade
• Planning an upgrade from V4.2.0
• Planning an upgrade from V5.1.0
• Staged Upgrade consideration
 Verifying the installation or upgrade
 Troubleshooting SDA with install or upgrade

• 5694-A01 z/OS V01.13.00 or higher
• 5698-A79 IBM Tivoli Monitoring V6.3.0 Fix Pack 2 or higher

V6.3.0 FP3 (GA Aug 7, 2014) is recommended for a number of APAR fixes,
including Java 6 & 7 security support and Persistent Datastore.

OA44915: MULTIPLE ABENDS DUE TO PERSISTENT DATASTORE FACILITY
OVERLAY

V6.3.0 Fix Pack 3 PTFs: UA74413, UA74414 (MGMT SERVER DS) and
UA74415 UA74416 (ITMS/ENGINE)

6.3.0-TIV-ITM-FP0003:
http://www-01.ibm.com/support/docview.wss?uid=swg24036775
• HKCI310 PARMGEN APAR OA44620 / PTF UA73688
• PARMGEN configuration support with OMEGAMON Family V5.3.0
products.
• APAR OA45024 / PTF UA73689 - First-time-User support recommended.
http://www-01.ibm.com/support/docview.wss?uid=swg1OA45024
Install – Requirements and Dependencies

65
Install - Packaging
5698-T02 IBM Tivoli OMEGAMON XE for CICS on z/OS V5.3.0
OMEGAMON Shared Component FMIDs included the Package BOM:
HKET620 End-to-End 5608A41EE
HKOB730 OMNIMON Base 5608A41OB
Product Component FMIDs included in the Package BOM:
HKC5530 OMEGAMON XE for CICS 5698A5800
HKGW530 OMEGAMON XE CICS TG 5698A9300
DVD/CD-ROM Materials included in the Package BOM (cont.):
LCD7-5139-06 IBM Tivoli OMEGAMON Application Support for z/OS V5.3.0, V5.2.0, V5.1.1, V5.1.0
DVD (z/OS common seeding CD)
- Note: Fix packs for products on this image do not require the DVD be installed before the fix pack installation.
LCD7-5138-05 IBM Tivoli OMEGAMON XE z/OS V5.3.0, V5.2.0, V5.1.1, V5.1.0 Language Pack
CDROM
5698-A79 IBM Tivoli Monitoring V6.3.0 (Prerequisite Package):
FMIDs included in the ITM Package BOM:
HKCI310 Configuration Tools (PARMGEN and ICAT) 5608A41CC
HKDS630 Tivoli Enterprise Monitoring Server on z/OS 5608A2800
HKLV630 TMS:Engine 5608A41CE

66
FMIDs and their Address Spaces

67
Pristine Install – What's New
 “Complete the Configuration” - CICS Region supports installation without
the need to modify your CICS JCL.

Dynamically open RKANMODR DD and allocate (R|T)KANMOD file during CICS initialization

Add OMEGAMON CICS Transaction and Program definitions

To use CEDA, refer to sample definitions shipped in TKANSAM(KOCCSD)
 Number of Files and Size of Persistent Datastore file increased

6 files each for OMEGAMON CICS (KC5) and CICSTG (KGW) for storing historical data

OMEGAMON CICSTG (KGW) Increased total cylinders: KGW_PD_CYL 76

OMEGAMON CICS (KC5) Increased total cylinders: KC5_PD_CYL 600

PDS files can only be allocated in the address space where the agent is configured.

68
Pristine Install – What's New
 ETE and CUA STCs are optional

These will be sunset in an upcoming release.

Avoid starting these with pristine installs.

They are configured by default but you do not have to start them.
 Enhanced 3270UI Placement (IBMTOM)

Best Practice - In it's own RTE or in an RTE with a Remote TEMS and the
OMEGAMON CICS agent.

69
Install or Upgrade – What's New
 Changes to our OMEGAMON XE for CICS and CICSTG SDA package

KppVRTMS – New TEMS Version file for z/OS agent SDA packages.

Purpose - Provides the ability to reliably determine the version of a product's application support files installed on a
z/OS TEMS.

The KppVRTMS and KppCAT files in RKANDATV are kept in sync with RTE load and with SDA processing.

The VRMF and Build level in KppVRTMS are both used during the SDA version checking process.

KppHIS - New file delivered in TKANDATV and in the KppJSTMS SDA package.

Contains the product historical tables that are eligible for Enhanced 3270UI Near term history collection.

CICS JCL changes are also new, and must be considered during install/upgrade
planning.

More details can be found in the first section of this deck.

70
Upgrade – Planning upgrade from V4.2.0 & V5.1.0
 PARMGEN is the only configuration method supported

Using ICAT for RTE configuration? - You can load the RTE to upgrade to V5.3.0 but you will not
have configuration support for new features introduced in the release.
 New Shared component version: OMNIMON V7.3.0 (HKOB730)
 OMEGAMON Subsystem (IBMCN)

STC JCL is new – If you are not running OMEGAMON XE for z/OS, you can continue to run with
the JCL generated with V4.2.0 or V5.1.0

Support for Cache Address space for OMEGAMON XE on z/OS

New VTAM applid – only needed if you use the new STC JCL.

STC security changes – applicable to OMEGAMON XE for z/OS
- Authority to issue passtickets to authenticate to RMF DDS (GPMSERVE). This security
change is not require for OMEGAMON XE for CICS.

71
 Persistent Datastore (PDS) upgrade considerations
 Review your PDS file allocations – 6 files with the new total space allocation?
 No - Delete the PDS files and follow the PARMGEN instructions for allocating and initializing the
recommended file count and sizes.
 Are your OMEGAMON XE for CICS files allocated in the TEMS and in the agent address space?
 Yes – Delete the PDS files and follow the PARMGEN instructions for allocating and initializing the
recommended file count and sizes.

72
 Persistent Datastore (PDS) upgrade considerations (cont.)
 OMEGAMON XE for CICS V5.3.0 default PDS files:

73
 OMEGAMON XE for CICS TG V5.3.0 default PDS files:

74

75
 Self-describing agents (SDA) – Best practice
 Consider using the Self-describing agents (SDA) features for installing the V5.3.0
application support files
 OMEGAMON XE for CICS V5.1.0 and V5.3.0 both support SDA
 Hub should be an HA Hub or a Hub running on a distributed platform
 Supports Pristine installs and upgrade install
 With SDA, you can start your upgrade from an OMEGAMON XE CICS V5.3.0 agent connected to a
REMOTE TEMS.
 Installation of application support files from the DVD is only required if you are planning to upgrade a
TEP Desktop Client.
 Language Packs can not be installed with SDA.
 Hub on distributed? Granular control is enabled by default.
To allow installations for all products and versions i.e. no blocking, use tacmd:
editsdainstalloptions -t default -i on

76
Upgrade – Planning upgrade from V4.2.0
 Enhanced 3270UI Considerations (IBMTOM)

Configure In it's own RTE or in an RTE with a Remote TEMS, the CICS agent and if you run
OMEGAMON z/OS, the z/OS backup proxy.

Review Enhanced 3270UI Security configuration considerations

Staged Upgrade – Enhanced 3270UI will only display data fro V5.3.0 agents
 Hub on z/OS?
 Consider creating a High Availability (HA) Hub and replacing the previously defined “full” Hub in your
RTE with a Remote TEMS.
 RKCPDEFW – in V5.1.0 and V5.3.0 this file is owned by the ITM
Framework.
 Purpose – to store persistent table data for OMEGAMON agents.
 OMEGAMON XE for CICS and OMEGAMON XE on z/OS store data in this file.
 As of ITM V6.2.3 Fix Pack 1, RKCPDEFW is allocated with the ITM Hub TEMS configuration

77
Upgrade – Staged Deployment Considerations
 Staged Upgrade deployment – deploying V5.3.0 to one or more LPARs, leaving
other LPARs running with V4.2.0 or V5.1.0 agents
 If using SDA, upgrade can start with LPAR where the agent is reporting to a
remote TEMS
• SDA will upgrade the Hub TEMS, and then the Remote TEMS application support files
 If not using SDA, i.e. manually adding application support via the TEPS, upgrade
must start with the Hub TEMS.
 Not all new V5.3.0 features will work until all agents reporting to the Hub have
completed the upgrade to V5.3.0.

For example: CICSplex historical may not work. Use the “CICSplex Agent Preferences” feature to
start the CICSPlex agent in an agent address space that is running V5.3.0.

78
Install and Upgrade Verification
 RKLVLOG of TEMS that agent is connected to:
Remote node <agentid:sysid:CPIRA> is ON-LINE (cics agent)
Remote node <agentid:sysid:GWIRA> is ON-LINE (cicstg agent)
Remote node <agentid:sysid:CEIRA> is ON-LINE (cicsplex agent)
KPDEIMN: Persistent Datastore initialization completed successfully
 CICS agent and CICSTG agent RKLVLOG:
KPDEIMN: Persistent Datastore initialization completed successfully

79
 CICSTG agent JESMSGLG:
KGW0800I: XMI CROSS MEMORY COMPONENT IS ACTIVE
KGW0023I: XAM EXCEPTION ANALYSIS MANAGER IS ACTIVE
KGW0300I: SPI STATISTICS COMPONENT IS ACTIVE
KGW0601I: XTR Transaction Retriever is active
 CICS agent JESMSGLG:
KCP0758I THE PCLASS MANAGER LOADED THE CICSPLEX RULES
KCP0809: XM INTERFACE TASK IS ACTIVE
KCP0023: XAM EXCEPTION ANALYSIS MANAGER IS ACTIVE
KCP0247: WSR - WLM COLLECTION WILL USE OMEGAMON'S SERVICE
POLICY DFLTSPOL, RULE: OMEGAMON
KCP0241: WSR - WLM COLLECTION WILL USE 00:05 HRS. AS THE
COLLECTION INTERVAL

80
Install and Upgrade Verification - KOBSDA

81
 Verifying self-describing agent processing completed successfully
• TEMS Logs:
o Verifying successful SDA processing of application support files:
 Hub TEMS JESMSGLG:
 KFASD009 Self-Describing Agent feature enabled on local TEMS.
 KFASD101 Self-Describing Install Completed Successfully for PRODUCT <CP>, VER <05300000>, ID
<TMS>, IDVER<05300000>.
 Remote and Hub TEMS RKLVLOG or equivalent TEMS log on distributed:
 KFASD101 Self-Describing Install Completed Successfully for PRODUCT <CP>, VER <05300000>, ID
<TMS>, IDVER 05300000>
 Remote TEMS RKLVLOG or equivalent TEMS log on distributed:
 KRAA0002, Self-Describing Agent Installation completed successfully for PRODUCT "CP", with TEMS
"sysid:CMS", VERSION_INFO "product_vrmf=05300000; tms_package_vrmf=05300000;
tps_package_vrmf=05300000;tpw_package_vrmf=05300000;"., Producer(SDA_Install)If you used SDA
to upgrade, application support files
 Both Hub and Remote TEMS RKLVLOG:
 KDSSA001 Seeding started for product <CP> using file <KCPSQL> with seed option <ALL>. Note:
For upgrades: <KCPSQLU> is used.

Self-Describing Agents (SDA) – troubleshooting

83
Troubleshooting (Self-describing agent)
 Restarting SDA processing for an agent, when the tacmd is not available for use
• Create two members in the RKANSQLU dataset allocated to the TEMS running on z/OS
where you wish to restart SDA processing: SDAQUERY & SDADEL
o Note: OMEGAMON CICS: PRODUCT = “CP” and OMEGAMON CICSTG: PRODUCT = “GW”
 Create member: SDAQUERY
 Run a query (SDAQUERY) to confirm that you are using the correct product code for your
SDA processing:
 SELECT $NODENAME(),PRODUCT,ID,PRODVER,SEEDSTATE,STATE,STATUS,IDVER,
 GRPID,LSTDATE,CATINSTMP,CATINSVER,CATSDA,MANUALINST
 FROM O4SRV.TAPPLPROPS
 WHERE GRPID = "5655" AND SYSTEM.PARMA("NODELIST","*ALL_CMS",8)
 AND PRODUCT = "CP" ;

84
 Restarting SDA processing for an agent, when the tacmd is not available for use
• Create member: SDADEL
 Example#1: Run a query (SDADEL) to delete all SDA installation records for the
OMEGAMON XE for CICS product component:
o DELETE FROM O4SRV.TAPPLPROPS
Ù WHERE GRPID = "5655" AND SYSTEM.PARMA("NODELIST","*ALL_CMS",8)
AND PRODUCT = "CP" ;
 Example#2: Run a query (SDADEL) to delete the SDA installation records for only TEMS
(“TMS”) SDA installation records for the OMEGAMON XE for CICSTG product component:
 DELETE FROM O4SRV.TAPPLPROPS
 WHERE GRPID = "5655" AND SYSTEM.PARMA("NODELIST","*ALL_CMS",8)
 AND PRODUCT = "GW" AND ID = “TMS”;
 Note: TEMS: ID = “TMS”, TEPS: ID = “TPS”, and TEP Client: ID = “TPW”

85
 Tivoli Enterprise Monitoring Server errors occur because an invalid
Java™ path is specified during monitoring server configuration

KFASD102 Self-Describing Install Failed with STATUS <1011> for PRODUCT <CP>,
VER <05300000>, ID <TMS>, IDVER <05300000>

Action: Check the Java path that you specified in the UNIX System.

Check the Services directory generated during configuration:
/usr/lpp/RTE_USS_RTEDIR/&rtename/kds/support/TEMS/KDSDPROF. Also check the
&hilev.&rtename.RKANDATV(KDSDPROF) allocated to the Tivoli Enterprise Monitoring Server

Correct the PARMGEN or ICAT parameter. Rerun the configuration process and then restart
the TEMS.

86
 SDA failure zFS mountpoint disk space issues. We suggest allocating 25
to 50 MB for the mountpoint disk space, then restart SDA processing.

JESMESLG:

IOEZ00078E zFS aggregate hilev.TKGWROOT.ZFS exceeds 95% full (1122/1128)
(WARNING)

IOEZ00068E zFS file system hilev.TKGWROOT.ZFS exceeds 95% full (8765/9024)
(WARNING)

RKLVLOG: KFASD102 Self-Describing Install Failed with STATUS <1011> for
PRODUCT <CP>, VER <05300000>, ID <TMS>, IDVER <05300000>.

Action: Increase the disk space of the mount point. Restart the SDA process.

87
 Errors during SDA processing because the SDA process is unable to
write to RKANDATV data set due to security authorization problems.

RKLVLOG messages:

KRAA0003, Self-Describing Agent Register/Install failed with STATUS (1014/UnKnown
Error) for PRODUCT "CP", with TEMS "BVTREM1:CMS", VERSION_INFO
"product_vrmf=05300000;tms_package_vrmf=05300000;tps_package_vrmf=05300000
;tpw_package_rmf=05300000;"., Producer(SDA_Install)

Action: Ensure that the TEMS has write authorization to the RKANDATV and USS directories. Restart the SDA processing.

88
 Errors during SDA processing because the SDA process is unable to write to
the hfs files system, due to insufficient space.

RKLVLOG messages:

KRAA0003, Self-Describing Agent Register/Install failed with STATUS ((1007/KT1 File
Transfer Error) for PRODUCT "CP", with TEMS "BVTREM1:CMS", VERSION_INFO
"product_vrmf=05300000;tms_package_vrmf=05300000;tps_package_vrmf=05300000;tpw
_package_rmf=05300000;"., Producer(SDA_Install)

Action: In your TEMS RKLVLOG, determine the name of your SDA HFS directory, find “TEMS SDM directory
/hfsdir/RTEname/kds/support/TEMS”. In a USS shell issue the “fs” command to determine how much space is left in your
HFS filesystem. Increase the filesystem size

Restart the SDA processing.

89
 Granular controls are enabled and preventing SDA processing

RKLVLOG messages:

KRAA0003, Self-Describing Agent Register/Install failed with STATUS (1024/0x400) for
PRODUCT "CP", with TEMS "BVTREM1:CMS", VERSION_INFO

(00A1-E0E4BEC3:kraaulog.cpp,755,"IRA_OutputLogMsg") Self-Describing Agent
Register/Install failed with STATUS (1024/0x400) for PRODUCT "CP", with TEMS
"HUB_nc049109", VERSION_INFO
“product_vrmf=05300000;tms_package_vrmf=05300000;tps_package_vrmf=05300000;tpw
_package_vrmf=05300000;".

Action:

tacmd listSdaInstallOptions List SDA installation status

tacmd editsdainstalloptions -t default -i on Allow installations for all products and versions without
any blocking. (This setting is essentially the default self-describing agent behavior in V6.2.3 and
V6.2.3 FP1.)

Or enter:

tacmd addSdaInstallOptions To specify the products and versions that the self-
describing agent facility is allowed to install

90
 STATE=ME - SDA processing is not retried automatically

List the product install records (CP is the OMEGAMON CICS product code):

tacmd listappinstallrecs -t CP -d

Delete the CP install record for the TEMS where SDA failed:

tacmd deleteappinstallrecs -t CP -v 05300000 -n TEMSNAME

The agent is notified and SDA processing for the agent should be re-driven

91
TEMS RKANDATV before & after SDA processing
 Before SDA processing (my RTE is loaded from the SMPE install):
• KCPATR
• KCPBAR
• KCPCAT
• KCPDOC
• KCPJSTMS
• KCPJSTPS
• KCPJSTPW
• KCPMAP
• KCPMSMAN
• KCPVRTMS

After SDA processing (my RTE is loaded from the SMPE install):
• KCPATR
• KCPBAR ** Notice timestamps are gone after SDA processing **
• KCPCAT
• KCPDOC n/c ← KppDOC not part of TMS SDA package
• KCPJSTMS n/c ← TEMS SDA package
• KCPJSTPS n/c ← TEPS SDA package
• KCPJSTPW n/c ← TEPB SDA package
• KCPMAP
• KCPMSMAN n/c ← SDA manifest file
• KCPSQL
• KCPSQLD
• KCPSQLU
• KCPVRTMS

92
SDA USS Directory before & after SDA processing
 Before SDA processing (after running the jobs to create the directories):
• /<RTE_USS_RTEDIR>/<RTENAME>/kds/support/TEMS
o KDSDPROF File (TEMS_JAVA_BINPATH=/usr/lpp/java/IBM/J6.0/bin)
o META-INF Dir (empty)
o SDMBACKUP Dir (empty)
 After SDA processing:
o cptms_support_z File
o spawn_cmd.sh File
o spawn_cmd.trc File
o KCPJSTMS.jar File
o KCPJSTPS.jar File
o KCPJSTPW.jar File
o KCPMSMAN.txt File
o KCPWICMS.lvl File
o KCPWICMS.ver File
o KDSDPROF File (TEMS_JAVA_BINPATH=/usr/lpp/java/IBM/J6.0/bin)
o META-INF Dir (MANIFEST.MF File )
o SDMBACKUP Dir (SDA_CPTMS Dir)

93
SDA USS Directory before & after SDA processing (cont.)
 After SDA processing:
o ....
o SDMBACKUP Dir (SDA_CPTMS Dir)
 The contents of sub-directory SDA_CPTMS will be equivalent to what also ends up in RKANDATV:
o cptms.ver → KCPVRTMS
o kcp.atr → KCPATR*
o kcp.baroc → KCPBAR*
o kcp.cat → KCPCAT*
o kcp.his → KCPHIS*
o kcp.map → KCPMAP*
o kcp.sql → KCPSQL*
o kcp_del.sql → KCPSQLD*
o kcp_upg.sql → KCPSQLU*
o *These were un-jarred from KCPJSTMS ← this is your TEMS jar file used on z/OS for SDA processing.

 Why Agent Preferences
 What changed in KCPPLXC “CICSplex Classification Rule
Definitions”
 Adding Preferences
 Classification Rules Review
 Agent Preferences
 Updating Preferences
 Deleting Preferences
 Troubleshooting: Who’s What Where
CICSplex Agent Preferences

 History for a CICSplex is housed in the CICSplex agent’s
address space. When the CICSplex agent moves to a
different agent address space, previously recorded CICSplex
history is no longer available.
 Customers wish to control which agent becomes the
CICSplex agent.
Why Agent Preferences

What Changed in KCPPLXC
New subpanel
in V530
New Title

9797
Adding Preferences When Adding a CICSplex Definition

9898

Either or both, SMF Identifier or XM Number, can be
specified.

The classification rule and agent preferences are saved
when the Enter key is pressed.

Adding Agent Preferences
It is also possible to add preferences for a CICSplex that has already been defined or one
that is not defined to OMEGAMON, but derived from CPSM.

In this example, preferences are being defined for
the default OMEGPLEX CICSplex.

 The OMEGPLEX default classification rules cannot be deleted:
 New OMEGPLEX rules can be added.
Classification Rules Review

 The *DFLT preferences cannot be deleted:
 Preferences can be added for existing or yet to be defined CICSplexes,
including the OMEGPLEX default CICSplex. They can all be updated or
deleted (except the *DFLT preferences).
 New preferences will take effect when the CICSplex becomes active. If
the CICSplex is already active (an agent is managing it) no change will
take place until the current CICSplex managing agent is recycled.
Agent Preferences

Updating Preferences

Deleting Preferences

Troubleshooting: Who’s What Where (first set of columns)
Type =KCPDBGPL to see all OMEGAMON
XE for CICS nodes.
Only online CICSplexes here
All online/offline CP nodes here
All CICS regions members of
currently online CICSplexes here

Troubleshooting: Who’s What Where (second set of columns)

Troubleshooting: Who’s What Where (third set of columns)

V5.3.0
CICS Historical Considerations

118
Contents
• What OMEGAMON Near Term History (NTH) is and is
not.
• Enabling NTH for collection to the PDS.
• Entering History mode.
• The different types of historical workspace.
• What if I do not see History.
• Task History.
• Application Trace.
• Region Performance Summary.

119
What Near Term History is.
• NTH will provide the customer with the ability to identify the cause of
problems that occurred in the recent past.
• NTH allows you to see snapshot data from the attribute groups
which are important for problem resolution.
• It allows consistent navigation around the product as if it were in real
time.
• It allows the viewing of Task History data.
• It allows the user to see all the places where a transaction ran within
the CICSplex.
• It allows the viewing of File Detail statistics related to a transaction.
• It allows the viewing of Application Trace including the ability to see
all trace entries for a task across the CICSplex.

120
What Near Term History is not.
• NTH is not intended to be used for trend analysis other than how
something was performing leading up to a problem.
• It is not to look back weeks ago at specific metric. It is for the recent
past.
• The recent past is defined by how much DASD space the customer
wishes to make available.
• Most of the space usage is dynamic, that is it is highly dependant
upon the workload and what is collected. As the workload can also
be incredibly variable it is not productive to try and determine the
exact size for a datastore.
o We provide an estimate for a given number of regions at a given
collection rate to achieve 3 days worth of data.
o So 15 regions at 5 minute intervals uses 600 Cyls to collect what
we suggest.

121
Enabling Near Term History
Select View and then H to
navigate to Historical
Configuration
This presents a list of products to configure

122
CICS historical configuration.

123
Creating a new configuration.
The CICS product only allows you to configure
collection at the TEMA. While this is a best
practice this is the only place we enforce it.

124
Creating a new configuration. Distribution.

125
Creating a new configuration. Continued.

126
Configuration for Task History.

127
Configuration for Application Trace.

128
Entering History Mode.
Enter a slash (/) next to any Summary display. If the
subpanel is eligible for history the History item will appear
in the Options Menu.

129
A historical summary.
The historical summary presents the selected row going
back in time. This allows you to identify periods that need
further investigation.

130
Setting time ranges.
Entering V.I allows the user to set a historical time range
for the display.

131
Crossing a day boundary.

132
A historical Snapshot.
The historical snapshot shows a workspace at a given
point in time. Any navigation for a historical summary will
result in a Historical snapshot view from the time selected.

133
What if I get No History.
If no History appears in a workspace it indicates that the table is eligible
for historical in the Enhanced 3270 User Interface but has returned no
data.
Place the cursor on the No History value or double click it for more
details.

134
What if I get No History.
This takes you to the definition of any situations for this
attribute group. It lands on the Distribution page so you
can see it is not distributed. From here a collection could
be added and distributed if permitted.

135
Not eligible subpanels.
It is possible that a workspace contains a mix of eligible and not eligible
subpanels.
In this case the product will not display the subpanels that cannot match
the primary subpanel.
Double clicking on the Not Eligible will take you to the list of attribute
groups that can be configured.

136
Task History.
No row count is displayed because the query stops when
the page is full. We could be at the last one or there could
be another 6 Million.
Paging up or down will show more rows if there are any.
The page up and down indicators are always on as we
have no way of knowing if there is more data or not. New
transactions could arrive the second we hit F7.

137
Task History Filters.
Pressing F4 or typing the Filter command presents the custom Filter
popup.
The values here are saved for the life of the session.

138
Filtered Task History.
This indicator lets you know what you are displaying has
filters applied.

139
Task History Detail.
Details for a task, shows other tasks for the same unit of
work and the regions they ran in.

140
File details for a task.
If a task has done any VSAM and it is configured for
history the file details will display against the task.
Selecting VSAM shows a breakdown of the VSAM
requests and which files were involved.

141
VSAM File detail.
For VSAM selecting the file name takes you to the file
display. Notice we are no longer in history mode. The
display will be real time if the first subpanel is not eligible.

142
CICSplex wide Application Trace.
This shows the trace entries from all the regions involved
in the task. It clearly marks the switch form one region to
another.

143
CICS Regions Performance Summary.
Shows metrics for all transactions in a region.
Is not dependent upon defined service classes.
Only shows data for regions when some transactions ran.

144
CICS Regions Summary History.

145
CICS Region Transactions Detail.
This shows a breakdown of the performance of all the
transactions in a region. Allows you to see the major wait
reasons as a percentage of response time.

146
CICS Region Transactions Detail - cont.
Also we can see all the Service Classes that ran in this
region as a part of the detail display.

147
CICS Interval Task Detail.

V5.3.0
CICS TG Support

149
Contents
 Background
• Timeline
• Architecture
 V530 Enhancements
• Enhanced 3270 UI support
• IPIC Statistics
• Monitoring for WAS on z/OS running in “Multi-Servant” mode
• Transaction Sweep Function
 PARMGEN and Configuration
 Troubleshooting
149

150
OMEGAMON XE for CICS TG on z/OS Timeline
150
CICS TG
V7.0
CICS TG
V7.1
2007
2009
2012
2014
V410 – First release of CICS TG support in OMEGAMON.
TEP UI only. Gateway daemon statistics only.
V420 – Added transaction flow support. Monitoring of
connections in WAS on z/OS added
V510 – Added PARMGEN configuration
and SDA support. 64-bit JVM support.
V530 – Enhanced
3270UI support (incl. NTH
and Embedded Data)
Added IPIC connection statistics
Monitoring of WAS on z/OS in
“multi-servant” mode
Transaction sweep function added
CICS TG
V9.0
CICS TG
V9.1
WAS V6.1 CICS TG
V8.0
WAS V7.0
WAS
V8.0
WAS V8.5

151
Current Supported Products
 CICS TG on z/OS
• V8.0
• V9.0
• V9.1 (GA in September 2014)
 WebSphere Application Server on z/OS
• V7.0
• V8.0
• V8.5.x
 Does not provide monitoring support for CICS TG on
Multiplatforms or WAS on non-z/OS operating systems
151

152
To
TEMS
Cross
Memory
TCP/IP
CICS TG Address Space
Basic Architecture
 CICS TG support is a “plain” OMEGAMON XE agent
• No classic, or other address space dependency
• Can be run stand-alone or within TEMS address space
 Data is collected from monitored systems in two ways:
• CICS TG Statistics API (Gateway daemons only, not WAS)
• Transaction data via OMEGAMON-provided exit code
152
Stats API
Port
TxnMonitor
Exit
OMEGAMON
XE for CICS TG
Agent

153
Attribute Group Source
153
Stats API Port
CICSTG_Connection_Manager_Threads (H)
CICSTG_CICS_TS_Region_Details (H)
CICSTG_CICS_TS_Regions (H)
CICSTG_Gateway_Daemon (H)
CICSTG_Region_Overview (H)
CICSTG_Worker_Threads (H)
TxnMonitor Exit
CICSTG_Client_Application_Details
CICSTG_Destination_Servers_Details
CICSTG_Transaction_Flow_Trace
CICSTG_Transaction_Response_Time_Detail
CICSTG_Transaction_Response_Time_Summary (H)
CICSTG_Active_Transaction_Analysis
CICSTG_Active_Transaction_Details
 (H) = attribute
group available for
Near-Term History
(NTH) collection
and viewing in
e3270ui

154
V530 Enhancements

155
Enhanced 3270 User Interface Support
155
CICS TG instances (Gateway daemon
and WAS) appear in separate subpanel
to CICS
For Gateway daemons: Health and
Requests Per Minute are key
performance indicators
Only regions monitored by a V530 agent
can navigate to other workspaces

156
156
Enterprise Summary
CICS TS Regions
Overview
Performance
Overview
Region Overview
Transaction
Analysis
CICS TS Regions
Details
Gateway daemons and WAS regions
Gateway daemons only
OMEGAMON for CICS workspaces
C P S T

157
157
The Region Overview varies according to
the monitored address space
Gateway daemon
WAS Servant Region

158
IPIC Support
158
 IPIC is the strategic protocol for connections into and between CICS
regions
• IP-based (hostname/port)
• Overcomes 32K COMMAREA limitations Drilling down on IPIC connection takes
you to workspace with IPIC-specific
properties

159
Gateway Daemon Resource Management
159
For Gateway daemon resource management, check to see if there have been timeouts within internal
thread pool and/or large number of Connection Manager threads waiting for Worker threads
If resource management has been determined to be the cause, consider increasing
the number of Worker threads in relation to Connection Manager thread or
increasing the the Worker Wait Timeout so connected client are not rejected too
quickly.

160
Investigate Reports of Failed Transactions
160
The Transaction Analysis workspace shows all active transactions, who they are calling, the
response time and last return codes.
The bad return codes, and if applicable CICS abend
code, are highlighted which can be used to diagnose the
issue.
A “failed transaction” is one that has given a bad return code
either from CICS, CICS TG or XA transaction coordinator

161
Analyze Slow Response Time From CICS
161
Average Response Time and Connection Failure rates can
be used to find the slow or broken connection. Next step: drill
down into connection details
CICS TS Region Overview workspace provides summary of all CICS regions this CICS TG has
connected with (or attempted to connect with) during it's lifetime

162
Integration with CICS Workspaces
162
If CICS region is also being monitored then connection details are shown from the CICS
perspective (embedded data)
Current Active Transactions using this
connection are shown Can now link directly into CICS workspaces to check
the properties to continue response time diagnosis.
Result is faster time to get from symptom to cause.

163
Near Term History
163
Performance Summary workspace allows user to see when performance
changes, then drill-down and potentially link to CICS workspaces for
further investigation
 History is stored in PDS and configured in same method as for all other
OMEGAMON agents
• View => History Configuration
• Collected data is stored at agent

164
WebSphere “Multi-Servant” Support
164
 WebSphere Application Server on z/OS users can define multiple servants
to be started automatically as part of a workload management policy
• If response times of user transactions do not meet the defined goals, the WLM can start
additional servant regions.
• New servants start with the same jobname
 CICS TG monitoring agent is enhanced to ensure transactions passing
through all servant regions are tracked
This feature is for users who have the “Multiple
Instances Enabled” property checked in their
WebSphere configuration
Also available for V510 via PTF
TEP workspace layout changes

165
Individual WebSphere servant regions are
grouped by node name on physical navigation
tree but data is now gathered for each servant
individually
Default TEP workspaces now show ASID of
monitored region to individually identify them

166
Redesigned node level workspace plots Transactions Per
Second and Response Time details for each servant with
same jobname on same charts

167
Redesigned Active Transactions workspace structure allows
user to compare performance of each servant region against
others to spot poor performance or issues
Links provided to allow drill-down to existing active
transaction and response time analysis for individual servant
regions

168
Further drilling-down leads to flow level monitoring for
individual transaction whether within a WebSphere servant
region or Gateway daemon
Improved display within Transaction Flow Trace enable
details of return codes from each flow to be more easily
understood

169
ASID also added to enhanced 3270UI workspaces. A row is
displayed for each active servant address space.

170
Details also provided for active transactions within the
selected servant region.
Drilling down takes you to address space and transaction
analysis of single servant address space

171
Transaction Sweep Function
171
CICS TG
Address Space
E1
E4
Client CICS
Transaction/flow records are created at
E1 and closed off at E4. Between these
points the transaction is “active”
If response flow is not received back
(terminated session) or commit/rollback
not seen at E4, then transaction remains
permanently “active” or orphaned
Orphaned transaction records will skew
results and are awkward to remove

172
172
 A “sweep” function has been added to periodically delete
“active” transaction records that are likely orphaned
• Users can configure how often to check (default: 1 minute) for transactions that
have seen no activity for a given time (default: 10 minutes)
• This can be switched off (never check) to revert behavior back to pre-V530
levels
08/03/14 09:42:29.545 KGWRM1999I: Starting OMEGAMON XE for CICS TG monitoring exit initialization.
08/03/14 09:42:29.549 KGWRM1998I: Build: 5.3.0.0-201309271509, TxnMonitor Level: 3
08/03/14 09:42:29.551 KGWRM1028I: Orphaned transaction sweep timeout set to 10 minutes
08/03/14 09:42:29.552 KGWRM1029I: Orphaned transaction sweep interval set to 1 minutes
08/03/14 09:42:29.570832 KGWRM0040I: XWRE140 Trace level 00 has been requested.
08/03/14 09:42:29.570845 KGWRM0100I: Initializing module GWXWR at 259710D0, V530 HKGW530 level 3.
08/03/14 09:42:29.570873 KGWRM0019I: CRATB020 Acquired the RDR at x"00000048_75800000" for a length of
x"00000000_00800000".
08/03/14 09:42:29.574 KGWRM1010I: TxnMonitor internal queue sleep time set to 1,000 ms.
08/03/14 09:42:29.574 KGWRM1009I: TxnMonitor internal queue length set to 10,000 records.
08/03/14 09:42:29.574 KGWRM1025I: TxnMonitor internal queue depth trigger set to 1,000 records.
08/03/14 09:42:29.575 KGWRM1000I: OMEGAMON XE for CICS TG monitoring exit initialization complete.

173
173
 Sweep interval and timeout set on per region basis through JVM
properties. Both property are defined in minutes
• Gateway daemon: Set in environment file in CTGSTART_OPTS
property
CTGSTART_OPTS=-j-Dcom.ibm.omegamon.kgw.rmexit.sweepTimeout=15
com.ibm.omegamon.kgw.rmexit.sweepInterval=5
• WAS: Set in server's JVM properties in Admin Console
• ###Add screenshot here
Sweep Timeout Action
10 Default Value
0 Set to default
1 – 1440 (24hrs) Set as Sweep Timeout
< 0 Set to default
> 1440 Set to default
Sweep Interval Action
1 Default Value
0 Never Sweep
(behaviour prior to this fix)
1 – 1440 (24hrs) Set as Sweep Interval
< 0 Set to default
> 1440 Set to default

174
174
 For Gateway daemons only the settings can be updated dynamically
/F <CTG Jobname>,APPL=RMEXIT,cmd=KGWSWEEPINTERVAL_n
/F <CTG Jobname>,APPL=RMEXIT,cmd=KGWSWEEPTIMEOUT_n
(where n is the new timeout or interval in minutes)
 There is no equivalent mechanism for sending requests to WAS regions.
 Example usage:
/F CTGBVT01,APPL=RMEXIT,cmd=KGWSWEEPINTERVAL_30
08/04/14 15:26:39.805 KGWRM1029I: Orphaned transaction sweep interval set to 30
minutes
/F CTGBVT01,APPL=RMEXIT,cmd=KGWSWEEPTIMEOUT_15
08/04/14 16:17:13.498 KGWRM1028I: Orphaned transaction sweep timeout set to 15
minutes

175
PARMGEN and Configuration

176
Configuration
 PARMGEN is the only supported configuration method
• Most parameters for agent setup are same as for other agents
• Prefix: KGW_
 Key specific CICS TG parameters to be aware of:
KGW_AGT_XMIT
Set to XMIT value 00-15 to limit monitoring to regions with matching value in JCL
Value is written to &hilev.RKANCMDU(KGWAGST)
KGW_SAPI_CLIENT_INTERVAL
KGW_SAPI_CLIENT_MESSAGES_TYPE
KGW_SAPI_CLIENT_MESSAGES_SYSOUT
KGW_SAPI_CLIENT_LOOP_DETECT
KGW_SAPI_CLIENT_SESSION_TIMEOUT
These define the behavior of the Stats API connections to Gateway daemons. They should
not need changing in normal circumstances. Refer to Parameter Reference guide for
more details.
176

177
Configuration
KGW_SA
Defines the start & end of a table where all monitored CICS TG regions are defined. Most
important factor is the defining the Stats API port (and if needed, hostname) so the agent
can make stats requests
Values are written to &hilev.RKANPARU(KGWSAPIP)
KGW_SAnn_ROW
Marks start of row (definition for a single region)
KGW_SAnn_CTG_DAEMON_HOST
NEW – optional hostname of the CICS TG if running on different IP stack to agent
KGW_SAnn_CTG_DAEMON_STC
Started task of the Gateway daemon or WebSphere region
KGW_SAnn_CTG_DAEMON_PORT_NUM
Stats API port number of Gateway daemon. Should match the value in that regions
configuration file (ctg.ini). For WebSphere regions this should be 00000 (not used)
KGW_SAnn_SAPI_CLIENT_CTGTRACE
Trace setting for the Stats API. Should be 0 in normal operation. Permissible values are 0-4
(full trace)
177

178
Configuration
 Example KGW_SA usage:
KGW_SA BEGIN * Table begin *
KGW_SA01_ROW 01
KGW_SA01_CTG_DAEMON_HOST "" * Example: "&SYSIPHOSTNAME."
KGW_SA01_CTG_DAEMON_STC CTGBVT01
KGW_SA01_CTG_DAEMON_PORT_NUM 25147
KGW_SA01_SAPI_CLIENT_CTGTRACE 0
KGW_SA02_ROW 02
KGW_SA02_CTG_DAEMON_HOST "" * Example: "&SYSIPHOSTNAME."
KGW_SA02_CTG_DAEMON_STC W700S01S
KGW_SA02_CTG_DAEMON_PORT_NUM 00000
KGW_SA02_SAPI_CLIENT_CTGTRACE 0
KGW_SA END * Table end *

Output:
INCLUDE=(CTGBVT01,25147,)
*SAPI_CLIENT_CTGTRACE=(START,0,CTGBVT01)
INCLUDE=(W700S01S,00000,)
*SAPI_CLIENT_CTGTRACE=(START,0,W700S01S)
178

179
Post-config of Request Exit
 Most complex part of CICS TG setup is configuring Request Exit (TxnMonitor)
 Formed of two parts:
• Java JAR installed into HFS/zFS
<install path>/usr/lpp/kan/bin/IBM/kgw_monitor.jar
• Native Modules installed into PDSE
&hilev.TKANMODP(KGWMON00)
&hilev.TKANMODP(KGWMON64)
 Gateway daemon configuration
• Updates needed to CICS TG Environment File (CTGENV)
• Add JAR to CLASSPATH
CLASSPATH=/TDCICST/c5530/dev/usr/lpp/kan/bin/IBM/kgw_monitor.jar
• Add native module library to STEPLIB
STEPLIB=DFH.V5R1M0.CICS.SDFHEXCI:TDCICS.GW530MNT.TKANMODP
• (Optional) Add configuration settings to CTGSTART_OPTS
CTGSTART_OPTS=-j-Dcom.ibm.omegamon.kgw.rmexit.sweepTimeout=15
com.ibm.omegamon.kgw.rmexit.sweepInterval=5
• Updates needed to CICS TG Configuration File (ctg.ini)
• Add TxnMonitor to RequestExits parameter
SECTION GATEWAY
RequestExits = com.ibm.omegamon.kgw.rmexit.TxnMonitor
179

180
Post-config of Request Exit
 WebSphere Application Server configuration
• Updates needed to WAS JCL
• Add JAR to CLASSPATH
CLASSPATH=/TDCICST/c5530/dev/usr/lpp/kan/bin/IBM/kgw_monitor.jar
• Updates needed to CICS Resource Adapter
• Add Class path and Path entries
• Add RequestExit to Connection Factory custom properties
180

OMEGAMON XE for CICS V530 Long client presentation

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to OMEGAMON XE for CICS V530 Long client presentation

Similar to OMEGAMON XE for CICS V530 Long client presentation (20)

More from IBM z Systems Software - IT Service Management

More from IBM z Systems Software - IT Service Management (20)

Recently uploaded

Recently uploaded (20)

OMEGAMON XE for CICS V530 Long client presentation

Editor's Notes