A fix is available
APAR status
Closed as program error.
Error description
ABEND0C9 occurred at DIVIDE instruction of EKYZM10X +838 in EKYZ130X. The date of the input record may be 2012/04/12, and this DPROP execution date is 2013/03/26. The GAP is very large between the running date of the Apply BMP and the date of a DPROP MQ message being processed. A divide instruction results an overflow condition and ABEND0C9 occurred.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the IMS DataPropagator Version 3 * * Release 1 MQSeries based Asynchronous * * Propagation Apply program. * **************************************************************** * PROBLEM DESCRIPTION: The Apply program may terminate after * * an ABENDS0C9. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** The IMS DataPropagator MQ asynchronous Apply program may fail following an S0C9 ABEND. This problem may be encountered when processing an MQSeries message that was created by the Capture program from more than 248 days prior to running the Apply program. This problem is thus not expected to occur during normal processing situations where near real-time propagation and message latency is more typical.
Problem conclusion
The reported problem occurred as a result of an overflow condition which may arise when an incoming Capture message to the Apply program is approximately 248 days or older. Modules have been changed to trap and avoid this potential overflow condition for the type of extremely old message described previously. The number of seconds reported in the "DELAY" section of the Apply statistics has been increased to seven digits from the original five digits. This expansion allows reporting up to a maximum "delay" of over 115 days. If a delay of more than 9999999.99 seconds is encountered a new message will be issued as follows: EKYI422W UPDATE DELAY COMPUTATION RESULTS IN EXTREMELY LARGE VALUE WITH NUMERICAL OVERFLOW WHICH CANNOT BE REPORTED. Note that delay statistics reported that are within the overflow state will be displayed as follows: ------------ DELAY ------------- AVG MIN MAX 9999999.99 9999999.99 9999999.99 When delay statistics fall below the overflow threshold during the Apply that encountered an overflow, normal reporting will resume, for example: ------------ DELAY ------------- AVG MIN MAX 1.01 1.01 1.01 ------------ DELAY ------------- AVG MIN MAX 0.25 0.25 0.25 Final summary statistics will not (can not) contain reliable values for the entire queue processing once an overflow has occurred. Thus any reported summary delay will ignore overflow and only consider otherwise valid delay times. For example using the above example: ------------ DELAY ------------- AVG MIN MAX 0.63 0.25 1.01
Temporary fix
Comments
APAR Information
APAR number
PM90159
Reported component name
IMS DATA PROPAG
Reported component ID
5655E5200
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-05-30
Closed date
2013-09-12
Last modified date
2013-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK97476
Modules/Macros
EKYI420X EKYI430X EKYZI25E EKYZM10X
GC27121302 |
Fix information
Fixed component name
IMS DATA PROPAG
Fixed component ID
5655E5200
Applicable component levels
R310 PSY UK97476
UP13/09/17 P F309
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":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 October 2013