CICS events to capture additional information from the EIB

This requirement has been re-evaluated. Looking at current plans, it is not likely that this would be implemented in the twelve months, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server

Many thanks for the additional feedback. We can certainly see the value in providing this capability in the future, so an internal work item has been raised to represent the requirement. This will be considered for possible inclusion in a future release.

Thanks for considering this enhancement.
1. Yes, we would like to both filter and capture the terminal id and,
2. the only obvious other general field that comes to mind at present is the task id (probably capture only).
many thanks

Thank you for this CICS RFE.

We will certainly give consideration to whether we can add the terminal ID as an additional item of 'context data' for events, which could then be used to filter events, and/or could be captured as data to be included in events when they are emitted.

We would be less likely to make the EIB as a whole something that could be included in capture specifications, because in that case it would be necessary to specify offsets into the structure in order to filter on or capture the required data. Although we do not often change this data area, and would probably always aim to do so in a compatible way (adding new fields to the end), it would make the capture specifications hostage to such changes. It also seems to be more user-friendly to identify the individual fields, as we currently do with EIBAID on relevant commands.

So we have a couple of questions about this request:
(1) Firstly, please can we confirm that you do want to be able to both filter by the terminal ID (i.e. use its value to decide whether or not to capture an event) and to capture the terminal ID (i.e. include it in the event data).
(2) Are there any other EIB fields which would be useful to you, and if so could you please briefly explain why? We could then look into how much of the EIB it would be useful to expose in this way.