We have found following explanation: http://www-306.ibm.com/software/data/db2/db2olap/v81docs/zosinst/olapz81tfrm.htm?olapz8115.htm Programming the IEFUSI user exit Memory should not be limited by the IEFUSI user exit. IBM recommends that you bypass normal IEFUSI processing when the subsystem is OMVS. DB2 OLAP Server spawns processes for each OLAP application. According to the MVS Installation Exits manual, at the time of the IEFUSI processing, the kernel has not yet propagated the parent's region size to the child. Therefore, IEFUSI has nothing to work with. If IEFUSI modifies the region size of the child process, the kernel will honor that region size, and it will not propagate the region size from parent to child. This can result in a failure of a fork if the region size is insufficient for the storage requirements of the forked process. If you must run with the IEFUSI exit, be sure that it correctly handles the region size available to the OMVS address space. The IEFUSI exit should be coded to check for OMVS and should not set the x'80' bit in REGFLAGS for OMVS regions. The REGFLAGS x'80' bit means that you use the values that IEFUSI has set into the region size values. This can cause an inappropriate and unintended region size limit for OMVS; it is often 54 MB, but the value can vary by system. If your IEFUSI exit has not been updated in several years, it is likely that the OMVS address space runs with a 54 MB region size, even though it looks like it is not limiting the OMVS region size. When IBM added UNIX (Open Edition, then UNIX System Services), they made OMVS a special case that behaves differently from other region types and documented it as being different. Some customers did not amend their IEFUSI exits that predated the introduction of the OMVS region type and did not implement the change that IBM suggested. The suggestion became a requirement when maintenance caused IEFUSI behavior to limit the OMVS region size to 54 MB. OLAP is likely to require more memory than 54 MB and will fail to execute correctly. New variables were added to the REGION DSECT in recent years, including REGNAME, which can be used to detect the OMVS region. Here is some sample IEFUSI logic: L BASENAME,REGNAME check for region type parm CLC 0(4,BASENAMEN),=CL4'OMVS' is it OMVS region? BE Return OI REGFLAGS,X'80' SET THAT IEFUSI CONTROLS NON-OMVS REGION You can find more information about the IEFUSI exit in MVS Installation Exits and DOC APAR OW38477.
On 7/21/05, DMR-Qualitas Outsourcing <[EMAIL PROTECTED]> wrote: > Hi folks, > > we are analyzing an incident about MQBroker and we have seen that > region requested is 54M but we don't find where region is codified. > > Could you help us to find it? > > > RPT VERSION V1R2 RMF TIME 16.33.28 > > PRIVATE AREA SUMMARY > JOB NAME - Q0T1BRK3 REGION REQUESTED 54.0M > STEP NAME - STEP1 REGION ASSIGNED (BELOW 16M) 6400K > PROGRAM NAME - BPXPRFC REGION ASSIGNED (ABOVE 16M) 500M > NUMBER OF SAMPLES - 17 > > > PRIVATE STORAGE MAP > BELOW 16M EXTENDED (ABOVE 16M) > 6FFFFF ________________________ > ________________________ 7FFFFFFF > | LSQA/SWA | | LSQA/SWA | > | 229/230 276K| BOTTOM OF | 229/230 114M| > 6BB000 |_____16.33.29_________| ALLOCATED AREA > |_____16.33.29_________| 78E00000 > | UNUSED 212K| | UNUSED 304M| > 686000 |______________________| GETMAIN LIMIT > |______________________| 65E00000 > | UNUSED 6568K| | UNUSED 77.5M| > 1C000 |_____16.33.29_________| TOP OF > |_____16.33.29_________| 6107D000 > | USER | ALLOCATED AREA | USER | > | REGION 88K| | REGION | > 6000 |______________________| | 423M| > | SYSTEM REGION 16K| | | > 2000 ------------------------ > ------------------------ 46A00000 > > Thank you > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
