A fix is available
APAR status
Closed as program error.
Error description
************************************ This APAR is for PMR 20404,6X2,760 ************************************ APAR PM04815 for IMU 3.20 Date reported: 02/15/2009 Severity - medium Users Affected: All IMU users of MU V3.2 and prior versions/releases Problem Description: An IMU/EZT Plus program is calling a user written program that issues a "DUMP nnn" macro to print a core dump around regis- ters at the time of error. The LE coredump program is abending when register(s) contain pointers that are not pointing to a valid memory. The user expects RC=nnn but it gets a program check. This problem occurs when TERMTHDACT(UADUMP,. . . . ) is specified in the LE options (CEEUOPT) table. Problem Summation MU ESPI routine is entered for protection/addressing exception because it is the last ESPI issued. The IMU ESPI routine does not recognize the fact that the problem is in the LE core dump routine, therefore it attempts to print program check informa- tion, returning back to the LE system for abend process. As per LE group, the IMU ESPI routine must call LE's CEE3ERP program to determine if the original problem can be handled by LE. Problem Conclusion: A call to CEE3ERRP was added to FSYESPI1 program to determine if the original problem occured in the LE routines and if the LE can handle the situation. If so, IMU resets its own ESPI trap and returns control to the system with R1 set to EPI as returned from the CEE3ERP call. Note: Note: The fix above alone does not fix the problem because, after the fix was implemented, the LE is still experiencing a problem, i.e., It abends because R14 is corrupted. The LE group is looking into this condition. The LE abend occurs when the IMU ESPI routine uses the standard linkage conventions upon entry. I.e., when SAVE (14,12) and RETURN (14,12) macros are used. The LE abend does not occur when the IMU ESPI entry is changed to save registers into it's own save area, I.e., when the ESPI routine does not use the standard linkage convention. To circumvent the LE abend, the IMU ESPI entry was changed to use its own save areas. It is important to recognize that the change circumvents the LE abend. It does not fix it. The actual fix, when it becomes available, must be provided by the LE group. ---------------------------------------------------------------- ----------------------------------------------------------------
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All IBM Migration Utility v320 users. * **************************************************************** * PROBLEM DESCRIPTION: An IMU/EZT Plus program is calling a * * user written program that issues a * * "DUMP nnn" macro to print core dump * * around registers at the time of error. * * The LE coredump program is abending * * when register(s) contain pointers that * * are not pointing to a valid memory. The * * user expects RC=nnn but it gets a * * program check. This problem occurs * * when TERMTHDACT(UADUMP,. . . . ) is * * specified in the LE options (CEEUOPT) * * table. * **************************************************************** * RECOMMENDATION: * **************************************************************** IMU ESPI routine is entered for protection/addressing exception because it is the last ESPI issued. The IMU ESPI routine does not recognize the fact that the problem is in the LE core dump routine, therefore it attempts to print program check information, returning back to the LE system for abend process. However, in the process of LE trying to recover, LE routines cause a real abend. As per LE group, IMU ESPI routine must call LE's CEE3ERP program to determine if the original problem can be handled by LE.
Problem conclusion
A call to CEE3ERRP was added to FSYESPI1 program to determine if the original problem occured in LE routines and if the LE can handle the situation. If SO, IMU resets its own ESPI trap and returns control to system with R1 set to EPI as returned from the CEE3ERP call.
Temporary fix
Comments
APAR Information
APAR number
PM04815
Reported component name
MIGRATION UTILI
Reported component ID
5697N4400
Reported release
320
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-11
Closed date
2010-02-22
Last modified date
2010-06-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FSYESPI1
Fix information
Fixed component name
MIGRATION UTILI
Fixed component ID
5697N4400
Applicable component levels
R320 PSY UK56786
UP10/05/12 P F005
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSY4B9","label":"IBM Migration Utility for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
27 October 2020