A fix is available
APAR status
Closed as program error.
Error description
LIU Integrity Checker can break a storage area and cause system abend or other unexpected results in any environment that Integrity Checker is active. This problem can occur when all of the following conditions are met: 1. Message FABL0101I is issued that means Integrity Checker is active. 2. LIU V2 APAR PM28084 is applied. 3. LIU V1 before PK57748 level had run in your system. Before LIU V1 PK57748, Integrity Checker set values other than zero to a reserved field of an RDE record in the LICON data set. By PK57748 Integrity Checker introduced a new function of verifying IMS user exits (randomizer, segment edit/compression routine, and else). In PK57748, Integrity Checker started to use the field to keep the user exit information. At that time, Integrity Checker correctly avoided using the dirty value in the field that was created before PK57748. However, in the LIU V2 PM28084, Integrity Checker erroneously uses the dirty field, and can break unexpected storage area. It can cause system abend or unexpected result. In one case, HD Pointer Checker gets ABEND0C7. This problem can occur in any environment that Integrity Checker is active. If Integrity Checker runs in the IMS DBRC region, it can cause ABEND or any unexpected result in the IMS DBRC region and the IMS control region. A workaround is to deactivate Integrity Checker by renaming all global option modules of Integrity Checker not to start with "LIU@" nor "LIUG". Another workaround is to recreate all RDEs by LICON utility with INIT.DB command. Sample JCL for INIT.DB is here: 3.8.3 INIT.DB command http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/fabmgb11/3.8 .3?DT=20110303232532 Sample control statement for the workaround is here: //FABLIN DD * INIT.DB DBD(*) REPLACE /*
Local fix
A workaround is to deactivate Integrity Checker by renaming all global option modules of Integrity Checker not to start with "LIU@" nor "LIUG". Another workaround is to recreate all RDEs by LICON utility with INIT.DB command. Sample JCL for INIT.DB is here: 3.8.3 INIT.DB command http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/fabmgb11/3.8 .3?DT=20110303232532 Sample control statement for the workaround is here: //FABLIN DD * INIT.DB DBD(*) REPLACE /*
Problem summary
**************************************************************** * USERS AFFECTED: IMS Library Integrity Utilities for z/OS, * * Version 2 Release 1 (FMID=H27P210) users who * * use the Integrity Checker. * **************************************************************** * PROBLEM DESCRIPTION: LIU Integrity Checker can break a * * storage area and cause system abend or * * other unexpected results in any * * environment that Integrity Checker is * * active. In one case, HD Pointer Checker * * gets ABEND0C7. * * * * This problem can occur when all of the * * following conditions are met: * * 1. Message FABL0101I is issued that * * means Integrity Checker is active. * * 2. LIU V2 APAR PM28084 is applied. * * 3. LIU V1 before PK57748 level had run * * in your system. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** Before LIU V1 PK57748, Integrity Checker set values other than zero to a reserved field of an RDE record in the LICON data set. By PK57748 Integrity Checker introduced a new function of verifying IMS user exits (randomizer, segment edit/compression routine, and else). In PK57748, Integrity Checker started to use the field to keep the user exit information. At that time, Integrity Checker correctly avoided using the dirty value in the field that was created before PK57748. However, in the LIU V2 PM28084, Integrity Checker erroneously uses the dirty field, and can break unexpected storage area. It can cause system abend or unexpected result. This problem can occur in any environment that Integrity Checker is active. If Integrity Checker runs in the IMS DBRC region, it can cause ABEND or any unexpected result in the IMS DBRC region and the IMS control region. This problem can also occur when running LICON utility VERIFY command or LIST command or migrating LICON data set from the LIU Version 1 format to the LIU Version 2 format.
Problem conclusion
The following modules have been modified to correctly avoid using the dirty value in the field that was created before PK57748. FABLIL10,FABLE15A,FABLVDV0 Also, LICON utility LIST command is changed to suppress printing checksum of user exit routine when the RDE has option disabled to verify changes in user exit routine by checksum.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM53369
Reported component name
IMS LIBR INTEG
Reported component ID
5655I4200
Reported release
210
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2011-12-02
Closed date
2011-12-14
Last modified date
2012-01-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK74789
Modules/Macros
FABLE15A FABLIL10 FABLVDVA FABLVDVB FABLVDVC FABLVDV9
Fix information
Fixed component name
IMS LIBR INTEG
Fixed component ID
5655I4200
Applicable component levels
R210 PSY UK74789
UP11/12/16 P F112 «
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.
[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89N","label":"IMS Library Integrity Utilities"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0"}]
Document Information
Modified date:
04 October 2020