All, Just a heads up. I wasn’t aware that we had any old programs left in production using the ISAM Interface (surprise), but there is currently an open APAR against it due to IBM internal compiler issue. We only upgraded half of our prod lpars, so we have a workaround. The IBM module lives in LPA. Not sure when the fixing PTF comes out, if there will be a dynamic activation option or if I’ll be forced to re-ipl the affected systems.
APAR Identifier ...... OA59229 Last Changed ........ 20/04/16 ABEND0C1 IN IDAIIPM3 WHEN TRYING TO READ/WRITE USING THE ISAM INTERFACE 20/04/16 PTF PECHANGE Symptom ...... AB ABEND0C1 Status ........... CLOSED PER Severity ................... 3 Date Closed ......... 20/04/16 Component .......... 5695DF106 Duplicate of ........ Reported Release ......... 240 Fixed Release ............ 999 Component Name DFSMS VSAM Special Notice PE Current Target Date ..20/05/15 Flags SCP ................... Platform ............ Status Detail: ANALYSIS - APAR is being investigated or debugged. PE PTF List: UJ02054 PTF List: Release 240 : UJ02664 not available yet Parent APAR: Child APAR list: ERROR DESCRIPTION: ABEND0C1 in IDAIIPM3+08 when trying to READ/WRITE using the indexed sequential access method (ISAM) KNOWN IMPACT: READ/WRITE macros don't work for ISAM in 2.4 PE Information: The original APAR (OA58976) and associated PTF (UJ02054) to address the ABEND0C1 in IDAIIPM3+08 did not correct that issue LOCAL FIX: PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: * * All VSAM users of the ISAM interface who use BISAM macros at * * z/OS 2.4. * **************************************************************** * PROBLEM DESCRIPTION: * * ABEND0C1 because of a bad address for the READ and WRITE * * macros in the DCB. * **************************************************************** * RECOMMENDATION: * * Apply PTF. * **************************************************************** A change in the compiler level changed the offsets of the entry points for READ and WRITE causing an ABEND0C1 due to a bad branch. PROBLEM CONCLUSION: The compiler level has been changed back. TEMPORARY FIX: ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
