A fix is available
APAR status
Closed as new function.
Error description
New function to: 1) Improve Tracking results in combined IMS/IMS Connect Extensions environment. 2) Support RDDS Header record. 3) Minor KM updates for improved formatting of several record types. 4) Utilize the unique message correlator in the OTMA OMHDRTIM field for a transaction using SendOnly protocol, which was implemented via IMS Connect APAR PI60128. This will help Problem Investigator more reliably associate the IMS and IMS Connect Extensions records when returning the result set for a combined transaction.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IMS Problem Investigator V2.4 * **************************************************************** * PROBLEM DESCRIPTION: New Function to: * * 1. Improve Tracking results in a * * combined IMS/IMS Connect Extensions * * environment. * * 2. Support RDDS Header record. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. APAR PI60128 for IMS Connect provides a unique message correlator in the OTMA OMHDRTIM field for a transaction using SendOnly protocol. IMS PI Tracking(TX or TU tracking command) will utilize the OMHDRTIM field value to more reliably associate the IMS and IMS Connect Extensions records when returning the result set for a combined transaction. When a Resume Tpipe command is issued by IMS Connect to process the Hold Queue data from an IMS transaction, the message correlator in the MHDRTIM field will be used to associate the IMS Connect originating transaction, the resultant IMS transaction and the Resume Tpipe transaction in the result set. (However, where the original IMS Connect transaction is from a persistent socket connection there is no way to reliably connect the returned message with a specific sequence of event records from the Resume Tpipe transaction, therefore all records for the Resume Tpipe transaction are returned in the result set.). 2. Improve end-to-end reporting of ODBM transactions in a combined IMS/IMS Connect Extensions environment. 3. Add a new Knowledge Module to format RDDS Header record. 4. Minor KM updates for improved formatting of several record types.
Problem conclusion
Temporary fix
Comments
1. APAR PI60128 for IMS Connect provides a unique message correlator in the OTMA OMHDRTIM field for a transaction using SendOnly protocol. IMS PI Tracking(TX or TU tracking command) will utilize the OMHDRTIM field value to more reliably associate the IMS and IMS Connect Extensions records when returning the result set for a combined transaction. When a Resume Tpipe command is issued by IMS Connect to process the Hold Queue data from an IMS transaction, the message correlator in the MHDRTIM field will be used to associate the IMS Connect originating transaction, the resultant IMS transaction and the Resume Tpipe transaction in the result set. (However, where the original IMS Connect transaction is from a persistent socket connection there is no way to reliably connect the returned message with a specific sequence of event records from the Resume Tpipe transaction, therefore all records for the Resume Tpipe transaction are returned in the result set.). 2. Improve end-to-end reporting of ODBM transactions in a combined IMS/IMS Connect Extensions environment. 3. Add a new Knowledge Module to format RDDS Header record. 4. Minor KM updates for improved formatting of several record types.
APAR Information
APAR number
PI85319
Reported component name
IMS PROBLEM INV
Reported component ID
5655K5000
Reported release
240
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2017-08-01
Closed date
2017-08-09
Last modified date
2018-11-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI49433
Modules/Macros
ALZA0A19 ALZA0A29 ALZA0A39 ALZA0A49 ALZA0A69 ALZA0419 ALZA0429 ALZA0459 ALZBRAPI ALZBRFMT ALZC4C6F ALZLCAT ALZLFMER ALZTRACK ALZTUTRK ALZ0B01S ALZ01A ALZ01B ALZ01C ALZ01D ALZ01E ALZ01F ALZ0701S ALZ0702S ALZ31A ALZ31B ALZ31C ALZ31D ALZ31E ALZ31F ALZ32A ALZ32B ALZ32C ALZ32D ALZ32E ALZ32F ALZ35A ALZ35B ALZ35C ALZ35D ALZ35E ALZ35F ALZ36A ALZ36B ALZ36C ALZ36D ALZ36E ALZ36F ALZ37A ALZ37B ALZ37C ALZ37D ALZ37E ALZ37F ALZ38A ALZ38B ALZ38C ALZ38D ALZ38E ALZ38F ALZ400DA ALZ400DB ALZ400DC ALZ400DD ALZ400DE ALZ400DF ALZ400FA ALZ400FB ALZ400FC ALZ400FD ALZ400FE ALZ400FF ALZ4003A ALZ4003B ALZ4003C ALZ4003D ALZ4003E ALZ4003F ALZ4004A ALZ4004B ALZ4004C ALZ4004D ALZ4004E ALZ4004F ALZ4005A ALZ4005B ALZ4005C ALZ4005D ALZ4005E ALZ4005F ALZ4006A ALZ4006B ALZ4006C ALZ4006D ALZ4006E ALZ4006F ALZ4007A ALZ4007B ALZ4007C ALZ4007D ALZ4007E ALZ4007F ALZ4008A ALZ4008B ALZ4008C ALZ4008D ALZ4008E ALZ4008F ALZ4010A ALZ4010B ALZ4010C ALZ4010D ALZ4010E ALZ4010F ALZ4014A ALZ4014B ALZ4014C ALZ4014D ALZ4014E ALZ4014F ALZ4021A ALZ4021B ALZ4021C ALZ4021D ALZ4021E ALZ4021F ALZ4024A ALZ4024B ALZ4024C ALZ4024D ALZ4024E ALZ4024F ALZ4028A ALZ4028B ALZ4028C ALZ4028D ALZ4028E ALZ4028F ALZ4029B ALZ4029C ALZ4029D ALZ4029E ALZ4029F ALZ4030A ALZ4030B ALZ4030C ALZ4030D ALZ4030E ALZ4030F ALZ4031A ALZ4031B ALZ4031C ALZ4031D ALZ4031E ALZ4031F ALZ6701A ALZ6701B ALZ6701C ALZ6701D ALZ6701E ALZ6701F ALZ6705A ALZ6705B ALZ6705C ALZ6705D ALZ6705E ALZ6705F ALZ70A ALZ70B ALZ70C ALZ70D ALZ70E ALZ70F H28T240J
Fix information
Fixed component name
IMS PROBLEM INV
Fixed component ID
5655K5000
Applicable component levels
R240 PSY UI49433
UP17/08/12 P F708
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.4.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A4","label":"IMS Problem Investigator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.4.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
06 November 2018