APAR status
Closed as program error.
Error description
Suppose the file's MY-KEY is defined as PICTURE X(26). The START KEY = MY-KEY(1:8) followed by three READ NEXT verbs retrieves the wrong records from the file. This only happens if the file is on the DB2 system. No problem if the file is managaged by any other system such as STL or VSAM or Encina SFS. It appears that the software translates the "KEY =" into the DB2 command "SELECT WHERE KEY >". Should be "SELECT WHERE KEY >=".
Local fix
Problem summary
Partial key returns the wrong records when using COBOL's START verb.
Problem conclusion
The problem is solved withfileset cobol.rte 4.1.0.2
Temporary fix
Comments
PTF UK62937 is part of cobol.rte.4.1.0.2
APAR Information
APAR number
PM24652
Reported component name
COBOL AIX RUNTI
Reported component ID
5724Z8702
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-10-18
Closed date
2010-12-09
Last modified date
2010-12-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
COBOL AIX RUNTI
Fixed component ID
5724Z8702
Applicable component levels
[{"Line of Business":{"code":"LOB17","label":"Mainframe TPS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS6SGM","label":"COBOL for AIX"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410"}]
Document Information
Modified date:
25 January 2021