SIZELIMIT SET TO THE MAXIMUM VALUE CAN CAUSE A LOOP IN SDBM
APAR Identifier ...... PI71640 Last Changed ........ 17/04/28
SIZELIMIT SET TO THE MAXIMUM VALUE CAN CAUSE A LOOP IN SDBM
Symptom ...... LP LOOP Status ........... CLOSED PER
Severity ................... 2 Date Closed ......... 16/11/02
Component .......... 5735FAL00 Duplicate of ........
Reported Release ......... 640 Fixed Release ............ 999
Component Name TCP/IP V2 FOR V Special Notice
Current Target Date .. Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 640 : UI42256 available 16/11/03 (1701 )
Parent APAR: OA51187
Child APAR list:
ERROR DESCRIPTION:
When the sizeLimit configuration option is set to the maximum
value of 2147483647 in either the global or SDBM section, this
can cause a loop in the LDAP server. Another way that the loop
could happen is by using the maximum sizeLimit on an SDBM client
request with the adminDN as the bindDN.
ANALYSIS:
The traceback will contain entries similar to this:
Entry E Offset Statement Load Mod
1 realloc +00000164 CEEEV003
2 racf_parseSearchResults2Entries
+0000038C GLDBSD31
3 doSearchAndSendResults_DN_ONLY
+000001C8 GLDBSD31
4 sdbm_search +0000094E GLDBSD31
5 sdbm_process_request
+000003D4 GLDBSD31
6 ldapbe_process_request
+00000484 GLDBSD31
7 process_backend_request
+00001DFC GLDSRV31
8 srv_process_request
+000007D8 GLDSRV31
9 receive_data+00001CDC GLDSRV31
10 process_receive
+000007AE GLDSRV31
11 worker_task +00000294 GLDSRV31
12 CEEPGTFN +0000005A CEEPLPKA
13 CEEOPCMM +00000986 CEEBINIT
LOCAL FIX:
BYPASS/CIRCUMVENTION:
Use a sizeLimit value less than the maximum of
2147483647
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: Users of z/VM LDAP Server who use SDBM. *
****************************************************************
* PROBLEM DESCRIPTION: When the sizeLimit configuration option *
* is set to the maximum value of *
* 2147483647 in either the global or SDBM *
* section, this can cause a loop in the *
* LDAP server. Another way that the loop *
* could happen is by using the maximum *
* sizeLimit on an SDBM client request *
* with the adminDN as the bindDN. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
SizeLimit set to the maximum value can cause a loop in SDBM.
PROBLEM CONCLUSION:
This APAR corrects internal value type to prevent overflow of
sizeLimit field.
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS:
GLDBCD31 GLDBGD31 GLDBIC3M GLDBLD3M GLDBSD3M GLDCHPWM GLDCLDAM
GLDCLS31 GLDCMPRM GLDCMSGA GLDCMSGS GLDDB2PM GLDDLETM GLDEXOPM
GLDGMSGA GLDGMSGS GLDLMSGA GLDLMSGS GLDMDFYM GLDMRDNM GLDPMSGA
GLDPMSGS GLDRMSGA GLDRMSGS GLDRPL3M GLDSLP31 GLDSMSGA GLDSMSGS
GLDSRCHM GLDSRV3M GLDSRV31 GLDUMSGA GLDUMSGS GLDUNL3M GLDUTP31
GLDUTS3M SDELETEM
SRLS:
NONE
RTN CODES:
CIRCUMVENTION:
MESSAGE TO SUBMITTER: