A fix is available
APAR status
Closed as new function.
Error description
By this APAR, LIU Integrity Checker provides exit routine verification that can detect the change of logic in exit routines using the checksum of in-core image of load modules. Supported exit routines are: - Randomizing Routine - Segment Edit/Compression Exit Routine and - Partition Selection Exit Routine.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IMS Library Integrity Utilities for Z/OS, * * Version 1 Release 1 (FMID=H27P110) users * * who use Integrity Checker * **************************************************************** * PROBLEM DESCRIPTION: LIU Integrity Checker provides new * * verification function to detect changes * * in logic of the following exit routines * * by using checksum: * * -Randomizing routine * * -Segment edit/compression exit routine * * -HALDB partition selection exit routine * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR provides the following new options for Integrity Checker: 1. Add a new option CHKRAND to specify whether Integrity Checker verifies changes in logic of randomizing routines by using checksum. 2. Add a new option CHKCOMP to specify whether Integrity Checker verifies changes in logic of segment edit/compression exit routines by using checksum. 3. Add a new option CHKPSEL to specify whether Integrity Checker verifies changes in logic of HALDB partition selection exit routines by using checksum. To enable this new function, you need to set the options to 'Y' against RDEs stored in your LICON data set by the CHANGE.DB command or re-create RDEs with the options by the INIT.DB command of the LICON utility. And you need to specify the libraries that contain the exit routines in STEPLIB DD of DBRC procedures, DLIBATCH procedures, and LICON utility jobs. When creating a global option module, you can also specify the options in the SYSIN input stream of the FABLPGEN job. The option values specified in a global option module are used in creating new RDEs.
Problem conclusion
Temporary fix
Comments
======================== = DOCUMENTATION CHANGE = ======================== IMS Library Integrity Utilities for z/OS Version 1 Release 1 User's Guide (Document Number: SC18-7025-02) should be changed as follows. ================================================================ 2.0 Integrity Checker 2.3.5 Adding DD statements to DBRC and DLIBATCH procedures 2.3.5.1 The STEPLIB DD You need first to concatenate the DD statement of the load module library in STEPLIB DD. The load module library must be APF-authorized. |If you want Integrity Checker to detect changes in logic of |randomizing routines, segment edit/compression exit routines, |or HALDB partition selection exit routines, you need to |specify the libraries that contain them in STEPLIB DD even if |the exit routines are placed in the LPA and LINKLST. 2.4.2 Running the FABLPGEN job << Add the following descriptions about the new options. >> |CHKRAND= |CHKCOMP= |CHKPSEL= | Specifies the option values to be used in creating a new RDE. | The meaning of each keyword is described in "INIT.DB". The | system default value for these parameters is N. 2.5.6 LICON utility 2.5.6.1 JCL requirements JOBLIB or STEPLIB DD Specifies the load module library, which contains the following o The LICON utility program (FABLIU00) o The global option modules (LIU@INST and LIU@imsi) o The IMS load module library o The library that contains DFSMDA dynamic allocation members for the RECON data sets. If the RECONx DD statement is omitted, the library is required (only for HALDBs) |o The library that contains randomizing routines, segment | edit/compression exit routines, or all of them when creating | a new RDE or verifying a DMB against an RDE with CHKRAND=Y, | CHKCOMP=Y, or both. Even if the exit routines are placed in | the LPA and LINKLST, it is necessary to specify the library | that contains them. 2.5.6.4 INIT.DB and 2.5.6.6 CHANGE.DB << Add the following descriptions about the new parameters. >> |CHKRAND(Y or N) | Specifies the option to determine whether to verify changes in | randomizing routines by checksum. The options are as follows: | Y Check. | N Do not check. | If CHECKON, CHECKBAT, CHECKLD, or CHECKIC is set to 'Y', this | specification is effective at each IMS environment. | |CHKCOMP(Y or N) | Specifies the option to determine whether to verify changes in | segment edit/compression exit routines by checksum. The | options are as follows: | Y Check. | N Do not check. | If CHECKON, CHECKBAT, CHECKLD, or CHECKIC is set to 'Y', this | specification is effective at each IMS environment. | |CHKPSEL(Y or N) | Specifies the option to determine whether to verify changes in | HALDB partition selection exit routines by checksum. The | options are as follows: | Y Check. | N Do not check. | If CHECKON, CHECKBAT, CHECKLD, or CHECKIC is set to 'Y', this | specification is effective at each IMS environment. Appendix B. Messages and Codes B.4 Messages B.4.1 FABL messages << Add the following descriptions about the new messages. >> FABL0208W CHECKSUM MISMATCH FOUND FOR DBD: dddddddd FABL0208W text FABL0208W mmmmmmmm Explanation: LIU integrity checker found a mismatch of the checksum values of the exit routines between RDE and either ACB or DBD for database dddddddd. Here text shows in which exit routine the mismatch was found; mmmmmmmm shows the name of the module for the exit routine. System Action: Processing continues. LIU integrity checker causes the RDE for which the mismatch was found to expire, and creates a new RDE with a checksum value of the exit routine. Programmer Response: If the mismatch is unexpected, check whether the exit routine you are using is correct. Problem Determination: None. FABL0209E CHECKSUM MISMATCH FOUND FOR DBD: dddddddd FABL0209E text FABL0209E mmmmmmmm Explanation: LIU integrity checker found a mismatch of the checksum values of the exit routine between RDE and either ACB or DBD for database dddddddd. Here text shows in which exit routine the mismatch was found; mmmmmmmm shows the name of the module for the exit routine. System Action: Processing continues. LIU integrity checker skips database dddddddd to obtain the database authorization. LIU integrity checker returns a nonzero return code for the requester of the database authorization to make the request for the database failure with the reason code $$. Programmer Response: If the mismatch is unexpected, check whether the exit routine you are using is correct. Problem Determination: None. FABL0210E MODULE NOT FOUND FOR mmmmmmmm Explanation: Module mmmmmmmm was not found in the STEPLIB concatenation. System Action: The IMS online subsystem or the IMS batch job continues processing without computing the checksum value for the module. The LICON utility ends with a return code of 8. Problem Determination: Check whether the module is provided for the STEPLIB concatenation of the job. Programmer Response: Supply the module to the STEPLIB concatenation and return the job. FABL0211E FIND FAILED FOR DDNAME: dddddddd MODULE: mmmmmmmm. RC=rr Explanation: The FIND macro failed for module mmmmmmmm from DDNAME dddddddd data sets. The return code was rr. System Action: The IMS online subsystem or the IMS batch job continues processing without computing the checksum value for the module. The LICON utility ends with a return code of 8. Problem determination: Check whether the correct data set is specified to the DD statement. Programmer response: Correct the error and rerun the job. FABL0212W CHECKSUM CALCURATION WAS SKIPPED FOR MODULE: mmmmmmmm IN DBD: dddddddd Explanation: LIU integrity checker can not calculate the checksum value for module mmmmmmmm specified in either ACB or DBD for database dddddddd. System Action: Processing continues without storing the checksum value for the module into RDE. Programmer Response: None. Problem Determination: Read the preceding messages that explain the warning conditions. FABL0213W CHECKSUM VALUE NOT FOUND FOR MODULE: mmmmmmmm IN RDE FOR DATABASE: dddddddd Explanation: LIU integrity checker found no checksum value for module mmmmmmmm in the RDE for database dddddddd because the RDE has been created without the checksum value. System Action: Processing continues without verifying the checksum value for the module. In IMS online environment or batch environment, LIU integrity checker expires the RDE in which no checksum value was stored and creates a new RDE with the checksum value. Programmer Response: None. Problem Determination: None. FABL0214W CHECKSUM VERIFICATION WAS SKIPPED FOR MODULE: mmmmmmmm IN DBD: dddddddd Explanation: LIU integrity checker skips the verification process for the checksum value for module mmmmmmmm specified in either ACB or DBD for database dddddddd. System Action: Processing continues without verifying the checksum value for the module. Programmer Response: None. Problem Determination: Read the preceding messages that explain the warning conditions. FABL0215E READ ERROR FOR DDNAME: ddname MODULE: mmmmmmmm Explanation: The READ macro failed for module mmmmmmmm from the DDNAME dddddddd data sets. System Action: The IMS online subsystem or the IMS batch job continues processing without computing the checksum value for the module. The LICON utility ends with a return code of 8. Problem determination: Check whether the correct data set is specified to the DD statement. Programmer response: Correct the error and rerun the job.
APAR Information
APAR number
PK57748
Reported component name
IMS LIBR INTEG
Reported component ID
5655I4200
Reported release
110
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-12-06
Closed date
2007-12-26
Last modified date
2008-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK32633
Modules/Macros
FABLAGOP FABLAI0 FABLAI1 FABLAI2 FABLASCD FABLAT0 FABLICCA FABLICC0 FABLICC8 FABLICC9 FABLICI0 FABLICT0 FABLIDBA FABLIDB0 FABLIDB8 FABLIDB9 FABLIL10 FABLIRD0 FABLISI0 FABLIU00 FABLLINK FABLPGIN FABLVCS0 FABLVDVA FABLVDV0 FABLVDV8 FABLVDV9 FABLVMNA FABLVMN0 FABLVMN8 FABLVMN9 FABLVRCA FABLVRC0 FABLVRC8 FABLVRC9 FABLVRDE FABLVTBA FABLVTBL FABLVTB8 FABLVTB9 FABLWMT H27P110J
| SC18702502 |
Fix information
Fixed component name
IMS LIBR INTEG
Fixed component ID
5655I4200
Applicable component levels
R110 PSY UK32633
UP07/12/27 P F712
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":"1.1.0"}]
Document Information
Modified date:
04 October 2020