A fix is available
APAR status
Closed as program error.
Error description
You may experience an ABEND822 on z/OS 2.2, 2.3, or 2.4 depending on the setting of your IEFUSI's below 16MB region limit. This can occur only with 24-bit region requests, ie REGION= set to a value less 16MB, while - IEFUSI exit specifies a value larger then LDASIZA for the REGION LIMIT, word 5 Sub-word 3 of the exit parameters. - IEFUSI exit does not specify a value for Region Size, word 5 Sub-word 4 of the exit paramaters This causes the region size (LDAVVRG) to be set to a value of the size of private. Where previously the size of private or the region request size, whichever was smaller would be used. 0MB Region requests are not affected by Abend822 processing. VERIFICATION STEPS: For example: Verification Steps: 1. In the abend822 dump issue: ip verbx vsmdata 'nog summ' f map =======================================<- 16M Line : Global Storage : :___________________________: 900000 <- Top of Private | | | LSQA/SWA/229/230 | 900000 <- Max User Region | | Address |___________________________| 8B4000 <- LSQA Bottom | | | (Free Storage) | |___________________________| 6000 <- User Region Top | | | User Region | |___________________________| 6000 <- User Region Start : System Storage : :___________________________: 0 Input Specifications: Region Requested => 300000 REGIONX values => SZRQB: 0 SZRQA: 0 IEFUSI/SMF Specification => SMFL : 900000 SMFEL: 8000000 SMFR : FFFFFFFF SMFER: FFFFFFFF Actual Limit => LIMIT: 8FA000 ELIM : 8000000 The storage map and input specifications represent a 3MB region request (from JCL Region= or Job Class default), the SMFL value represents a 9MB Region limit defined by the IEFUSI. Since the start of the region is at x'6000', only 8FA000 bytes are available for region processing. Since the size of private is 008FA000, the IEFUSI limit of 00900000 is not honored and treated as no limit. Make note of the SMFL value, SMFR value, LIMIT value, and the Region Requested value 2. Format the LDA (ASCBLDA points to the LDA), use control block formatter ipcs command ip cbf LDA_Address str(LDA) f VVRG F SIZA VVRG..... 008FA000 SIZA..... 008FA000 3. If the SMFR (region size) value is FFFFFFFF, SMFL (region limit)value is greater then SIZA while the region requested is reasonably smaller then the size of private then this APAR describes your problem. On z.os 2.1 and earlier, you would expect to see VVRG..... 00300000 (3MB which is the Region Requested) On z/OS 2.2 up z/OS 2.4, you would expect to see VVRG..... 008FA000 (9192K, which is the entire size of region LDASIZA)
Local fix
BYPASS/CIRCUMVENTION: On the failing job step, specify a REGION=17MB or greater or Remove Limit Size specification in IEFUSI or Reduce the size of Limit Size in IEFUSI specification
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of HBB77A0 and up. * **************************************************************** * PROBLEM DESCRIPTION: * * ABEND822 region size IEFUSI after upgrade LDAVVRG SMFLIM * * * **************************************************************** * RECOMMENDATION: * **************************************************************** This problem can occur only with 24-bit region requests, ie REGION= SET to a value less than 16MB, and when the IEFUSI exit specifies a large value for Region Limit and does not specify a value for Region Size. This causes the region size (LDAVVRG) to be set to a value of the size of private. Where previously the size of private or the region request size, whichever was smaller would be used.
Problem conclusion
The code to handle 24-bit region requests and set the non-extended region size is changed. When the region request from JCL is non-zero and the region size is not set by IEFUSI exit, the code is changed to set the region size to the minimum of request and limit values.
Temporary fix
Comments
×**** PE20/12/03 FIX IN ERROR. SEE APAR OA60547 FOR DESCRIPTION ×**** PE20/11/25 FIX IN ERROR. SEE APAR OA60547 FOR DESCRIPTION
APAR Information
APAR number
OA59324
Reported component name
VSM - VIRT STOR
Reported component ID
5752SC1CH
Reported release
7B0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-03-27
Closed date
2020-09-25
Last modified date
2021-04-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ04019 UJ04020 UJ04021
Modules/Macros
IGVGVRGN
Fix information
Fixed component name
VSM - VIRT STOR
Fixed component ID
5752SC1CH
Applicable component levels
R7A0 PSY UJ04021
UP20/10/07 P F010
R7B0 PSY UJ04019
UP20/10/07 P F010
R7C0 PSY UJ04020
UP20/10/07 P F010
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"7B0"}]
Document Information
Modified date:
16 April 2021