A fix is available
APAR status
Closed as program error.
Error description
IIUSRTVx received ICE046A SORT CAPACITY EXCEEDED because the FILSZ value specified was too small. This can occur when few secondary indexes are defined, in this case 6. The COMPLETION CODE=794 NUM OF RECORDS MISMATCH: SECONDARY INDEX received for each index was incorrect.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS Index Builder for z/OS, * * Version 3 Release 1 (FMID=H22O310) * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes the following problems: * * * * 1. The IIUSRTVx sorts running in the IB * * sequential scan process fails because * * the FILSZ parameter value is too small * * to build two or more secondary indexes * * of non-HALDB. * * (Completion Code=722 or 794) * * * * 2. Index buffered sort fails because * * the FILSZ parameter value is too small. * * (IIUB050E/Reason=A26) * * * * 3. After an IIUSRTxx sort fails in the * * IB sequential scan process and * * IIUB059W WARNING: SORT ABEND EVIDENCED * * is printed, the index sort continues * * and COMPLETION CODE=00 is shown for * * a secondary index erroneously. This * * occurs when APAR PM09522 is applied. * * * * 4. The IIURDFLT SORTFSZ entry should * * be added to the runtime parameters * * module (IIURPRMS). * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR fixes the problems listed in the Problem Description field.
Problem conclusion
This APAR fixes the problems listed in the Problem Description field. To fix the problems, some of the current behaviors of Index Builder have been adjusted by this APAR: - The FILSZ value of each IIUSRTVx sort is increased when the length of index record is shorter than 94 bytes, or two or more secondary indexes are built - The FILSZ value of each index buffered sort is increased when the length of index record is shorter than 94 bytes. The FILSZ value is estimated based on the following VSAM characteristics for each index; - the record length - the primary space allocation size - the secondary space allocation size When the estimated FILSZ value is small, increasing the allocation size is recommended. ======================== = Documentation Change = ======================== IBM IMS Index Builder for z/OS, V3R1, User's Guide (SC18-9101-01) should be changed as follows: ================================================================ 2.4 Defining runtime parameters (The IIURDFLT SORTFSZ entry is added.) IIURPRMS CSECT IIURPRMS RMODE 31 DC CL52'IIURPRMS' module start * alternate sort procedure name DC CL52'IIURSORT IIUSAS ' * run time default parameters * DC CL52'IIURDFLT APIP IIUAPIFC' * DC CL52'IIURDFLT CLASS IIU.STRIPE ' * DC CL52'IIURDFLT ITKBSRVR SRVRNAME' DC CL52'IIURDFLT SCAN IIUSCNAS' DC CL52'IIURDFLT SORTP IIUSRTAS' | * DC CL52'IIURDFLT SORTFSZ 2000000' * DC CL52'IIURDFLT SIDXBUF 64,64,64' * DC CL52'IIURDFLT TMRWAIT 300' * DC CL52'IIURDFLT VIC YES,IIU.UIC.UDATA' * DC CL52'IIUREND' module end * END IIURPRMS Figure 18. Example of IMS Index Builder runtime parameters module : | Using IIURDFLT SORTFSZ | Use the IIURDFLT SORTFSZ entry to specify striped sort mode | and the number of records in each sort stripe. | For details, see the description of the SORTFSZ statement | in "2.2.2 IMS Index Builder input control statements". | | This value can be changed also by the SORTFSZ control | statement for each job. ---------------------------------------------------------------- 3.3 IMS Index Builder reason codes 3.3.5 IMS Index Builder processing phase failure reason codes ---------------------------------------------------------------- | 744 PRIME DB DATA SET POINT FAILURE | | Explanation: | The POINT macro failed and scan could not continue. | | Programmer Response: | Provide diagnostic documentation. If the problem persists, | contact IBM Software Support. ---------------------------------------------------------------- | 745 PRIME DB DATA SET GET FAILURE | | Explanation: | The GET macro failed and scan could not continue. | | Programmer Response: | Provide diagnostic documentation. If the problem persists, | contact IBM Software Support. ---------------------------------------------------------------- | 748 COMMON SCAN FAILURE ABEND | | Explanation: | Scan could not continue. | | Programmer Response: | Provide diagnostic documentation. If the problem persists, | contact IBM Software Support. ---------------------------------------------------------------- | 749 COMMON SORT FAILURE ABEND | | Explanation: | A IIUSRTxx sort processing failed during sequential scan. | User response: | See the explanation of IIUB059W message. ---------------------------------------------------------------- A26 SORT PROCESSING FAILURE Explanation: | An index sort processing error occurred. | User response: | See the explanation of IIUB059W message. (Delete) Programmer Response: (Delete) Review the MVS log. Provide run documentation to IBM (Delete) Software Support. ---------------------------------------------------------------- 3.4 IMS Index Builder messages | IIUB059W WARNING: SORT ABEND EVIDENCED - PLEASE CHECK IIUSOUT | | Explanation: | A sort processing ended with an error. The IIUSOUT data set | contains the messages that were issued by the sort program. | System Action: | If the scan process has not completed, IMS Index Builder | processing stops. Otherwise, IMS Index Builder continues to | process other indexes. | User response: | Check and correct the error. | When the work space capacity for sort has exceeded, consider | increasing the value of the following options: | - The JCL REGION option of the main and subordinate address | spaces | - The sort DYNSPC option | - The primary allocation size of the VSAM data set, which | is used to estimate the value of the sort FILSZ option | when the sort SORTIN option is not specified. | When an internal program error has occurred, provide | diagnostic documentation to IBM Software Support. ================= End of Documentation Change ==================
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM12486
Reported component name
IMS INDEX BUILD
Reported component ID
5655E2400
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-04-16
Closed date
2010-05-18
Last modified date
2012-01-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK57053
Modules/Macros
IBCD IIUBIDCM IIUBMSGS IIUBSCTL IIUDRVRX IIUGENEQ IIUIFS3 IIUIFS3A IIUIFS3B IIUIFS39 IIUSCA01 IIUSCA11 IIUSCA12 IIUSIN01 IIUSMP10 IIUXTMS SIBCD
SC18910101 |
Fix information
Fixed component name
IMS INDEX BUILD
Fixed component ID
5655E2400
Applicable component levels
R310 PSY UK57053
UP10/05/20 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.
[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89M","label":"IMS Index Builder"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]
Document Information
Modified date:
04 October 2020