A fix is available
APAR status
Closed as program error.
Error description
Two issues being addressed: 1. IMS log type x'6701' for Sync callout events has 'USER SGM' section that is incorrectly interpreted as an IMS Connect HWSOMUSR structure when the environment is not IMS Connect. 2. IMS log type x'4040' incorrectly formats fields UOWIMSST and UOWCQSST. Keywords: TYPE6701 TYPE4040 6701 4040 Additional three issues addressed: 1) In the detail display for a CEX journal 0042 record (Message received from OTMA), IMS PI shows most fields that are STCK timestamp in local date/time format. CERE_42_SVTTOKN is only displayed in dump format. It is a STCK timestamp so it should also be formatted showing local date and time. 2) When IMS Problem Investigator 2.3 formats the header of a type01 record for an OTMA message, the LUY_ASYNC_TOKEN field (and also LUY_TOKEN) in the PTMA message prefix data is displayed in dump format. These are STCK timestamps so IMS PI should display the timestamp in local date/time format. 3) In tracking a transaction lifecycle we currently track based on the contents of the IMS x'08' User Token(LINTTOKN) but only if the region type is set as AER/ODBA. We need to make the contents of the LINTTOKN available for tracking regardless of region type.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IMS Problem Investigator V2.3 * **************************************************************** * PROBLEM DESCRIPTION: Adjust handling of IMS Log Type X'6701' * * and X'4040' records in certain cases * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR is addressing the following issues: 1. IMS log type x'6701' for Sync callout events has 'USER SGM' section that is incorrectly interpreted as an IMS Connect HWSOMUSR structure when the environment is not IMS Connect. 2. IMS log type x'4040' incorrectly formats fields UOWIMSST and UOWCQSST. 3. CEX records that include SVTTOKN not formatted as timestamp in Zoom mode. 4. Some IMS log records that include an OTMA section may have fields that contain a STCK value that are not formatted as timestamp in Zoom mode. 5. Tracking may not produce a complete result set where records may be correlated by a User Token.
Problem conclusion
The following changes have been made for the above issues: 1. In IMS x'6701' record if the 'USER SGM' section is not for IMS Connect then it is dumped. 2. In IMS x'4040' record fields UOWIMSST and UOWCQSST are formatted as 2-byte flag fields. 3. Changed the formatting of SVTTOKN in CEX records when in Zoom mode to format SVTTOKN as an STCK timestamp instead of a hex value. The change in formatting does not change the fact that SVTTOKN is a TOKEN value and may not always be a valid STCK timestamp. 4. Changed the formatting of certain fields in the IMS OTMA section to display as timestamps when in Zoom mode. 5. IMS PI only propagated the contents of the x'08' user Token field (LINTTOKN) if the region type was identified as AER/ODBA. As a result of this change the contents of LINTTOKN are made available for tracking regardless of the x'08' region type. 6. Provide knowledge module for new CEX event 173 added for ACEE cache cleanup reporting.
Temporary fix
Comments
APAR Information
APAR number
PI09155
Reported component name
IMS PROBLEM INV
Reported component ID
5655K5000
Reported release
230
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-01-08
Closed date
2014-01-28
Last modified date
2014-02-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI14570
Modules/Macros
ALZA0AD9 ALZA0109 ALZA0119 ALZA0129 ALZA0139 ALZA0149 ALZA0159 ALZA0169 ALZA0179 ALZA02A9 ALZA02B9 ALZA02C9 ALZA02D9 ALZA0299 ALZA03E9 ALZA0389 ALZA0399 ALZA0419 ALZA0429 ALZA0439 ALZA0449 ALZA0589 ALZA06A9 ALZA0629 ALZA0699 ALZA07B9 ALZA0749 ALZA0779 ALZA0789 ALZBRAPI ALZCXDRV ALZE0803 ALZE0804 ALZLCAT ALZSDAPI ALZSDCXG ALZTRACK ALZTUTRK ALZ0B01S ALZ01A ALZ01B ALZ01C ALZ01D ALZ019 ALZ0701S ALZ0702S ALZ08A ALZ08B ALZ08C ALZ08D ALZ089 ALZ31A ALZ31B ALZ31C ALZ31D ALZ319 ALZ32A ALZ32B ALZ32C ALZ32D ALZ329 ALZ35A ALZ35B ALZ35C ALZ35D ALZ359 ALZ36A ALZ36B ALZ36C ALZ36D ALZ369 ALZ37A ALZ37B ALZ37C ALZ37D ALZ379 ALZ38A ALZ38B ALZ38C ALZ38D ALZ389 ALZ4040A ALZ4040B ALZ4040C ALZ4040D ALZ40409 ALZ6701A ALZ6701B ALZ6701C ALZ6701D ALZ67019 H28T230J
Fix information
Fixed component name
IMS PROBLEM INV
Fixed component ID
5655K5000
Applicable component levels
R230 PSY UI14570
UP14/01/30 P F401
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.3.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.3.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 February 2014