A fix is available
APAR status
Closed as program error.
Error description
(750) If CRD file output file record size is smaller than IFCID length, then abend 0C4 occurs
Local fix
Use default record size of 32k
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - ISPF Monitoring dialogs * **************************************************************** * PROBLEM DESCRIPTION: Running the OMPE-OLM CRD-6a task for * * a DB2 V10 subsystem and using a CRD * * output dataset with 4k record length, * * ABEND 0C4 occurs sometimes if the * * IFCID record is greater than 4k. * * * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: Running the OMPE-OLM CRD-6a task for a DB2 V10 subsystem and using a CRD output dataset with 4k record length, ABEND 0C4 occurs sometimes if the IFCID record is greater than 4k. PROBLEM CONCLUSION: If the current IFCID record is greater than the record length of the CRD output dataset, message "FPEM0806W <V1> records are not written to '<V2>'. The maximum record length of one of these records is <V3>" is written to the CRD message log. This message shows the number of IFCID records skipped and the maximum IFCID record length. A new CRD output dataset with a greater record length can be allocated to avoid this record skipping.
Problem conclusion
If the current IFCID record is greater than the record length of the CRD output dataset, message "FPEM0806W <V1> records are not written to '<V2>'. The maximum record length of one of these records is <V3>" is written to the CRD message log. This message shows the number of IFCID records skipped and the maximum IFCID record length. A new CRD output dataset with a greater record length can be allocated to avoid this record skipping. KEYWORDS: OMPE-OLM CRD-6A-TASK ABEND0C4 FPEM0806W
Temporary fix
Comments
APAR Information
APAR number
PM46171
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-22
Closed date
2011-11-11
Last modified date
2011-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK73785 UK73786
Modules/Macros
DGOMABEG DGOMACMD DGOMACON DGOMACSR DGOMAEND DGOMAIO0 DGOMASTA DGOMATIE DGOMATIM DGOMATRI DGOMAXAE DGOMAXA0 DGOMAX00 DGOMEGST DGOMGISP FPEFWENU FPEFWJPN FPEMGDCD FPEMMAIN FPEMMAI2 FPEMMAI3 FPEMMEND FPEMMSTH HKDB420J HKDB510J KDB420J KDB510J
| GC19250600 | GH12692300 |
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 December 2011