Analyzing MVS Virtual Storage
This section describes the Abend-AID Virtual Storage Analysis screens and the enhancement to the Memory Display screen. It also describes an approach for using the Abend-AID Viewer to resolve an 878-xx abend or S80A-xx.
An S878 occurs when the system tries and fails to satisfy a STORAGE request, an RU or VRU form of a GETMAIN request, or an RU form of a FREEMAIN request, and depending on the reason code, indicates an out-of-storage condition. An S80A-xx occurs when the system tries and fails to process an R form of the GETMAIN or FREEMAIN macro. The xx is the reason code that explains the error which is also found in the system diagnostic work area (SDWA) in field SDWACRC.
Programming errors that commonly cause an S878-xx or S80A-xx include the following:
- GETMAINs without subsequent FREEMAINs; that is, orphaned storage.
- A section of program code that contains a GETMAIN which is repeatedly being executed (loop). Looking at the system trace table also assists in this case.
- An invalid length specified on a GETMAIN.
Further, if the reason code indicates a GETMAIN failure for private area or local system queue area (LSQA) storage, verify that the size specified on the REGION parameter coded on the JOB or EXEC statement is large enough. The size specified on the REGION parameter is limited by the size of the private areas. The size of the private areas is determined by the size of the common areas at IPL time. In other words, storage for the common areas is set aside first and what is left over is for the private areas. The common areas include the prefixed save area (PSA); common service area (CSA); pageable, fixed, and modified link pack areas (PLPA, FLPA, and MLPA); system queue area (SQA); and the nucleus, which is fixed and non-swappable.
In order to determine the exact cause of the S878 or S80A, examine the IEA705I message in the JESMSGLG of the abending job for the xx reason code. If it is not available, the data area containing the unformatted information for the IEA705I is found in the extended nucleus. To find this area in the dump, go to the Control Blocks/Storage screen and select the CVT. Once the CVT is displayed on the Memory Display screen, select the address at offset x'10C'.
Refer to IBM informational APAR II05506 or IEA705I in the IBM messages manual for the layout of this area, which virtual storage manager (VSM) uses as a save area for error conditions. This area is in a module called IEAVMSGS in the extended read/write nucleus, which can also be found from the Nucleus Map display.
The JESMSGLG for the S878 sample created for this demonstration is shown in the following figure. The reason code is 10, which indicates the GETMAIN was for private area storage that could not be satisfied.
JESMSGLOG for the S878 Abend
COMMAND ===> SCROLL===> CSR
==>
Time Job Message
******** ******** *************************************************************
11.41.42 JOB12501 +DFHCP0102I H01AC118 CPI initialization has ended.
11.41.42 JOB12501 +DFHPR0105I H01AC118 Partner resource manager initialization
11.41.42 JOB12501 +DFHAI0102I H01AC118 AITM initialization has ended.
11.41.43 JOB12501 +DFHJC4508 H01AC118 CICS SYSTEM LOG. SECONDARY DATA SET NOW
11.41.43 JOB12501 +DFHJC4553 07/03/19 11:41:43 H01AC118 Archive job submitted
11.41.43 JOB12501 +DFHAP1204I H01AC118 COBOL2 is being initialized.
11.41.43 JOB12501 +DFHSI1517 H01AC118 Control is being given to CICS
. . . . . .
. . . . . .
. . . . . .
. . . . . .
11.42.49 JOB12501 IEA705I ERROR DURING GETMAIN SYS CODE = 878-10 CCFXC410 CICS
11.42.49 JOB12501 IEA705I 00F0C100 008C97D0 008C97D0 00377200 00008000
11.45.30 JOB12501 IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=878 REASON CODE=00000010
TIME=11.42.49 SEQ=50362 CPU=0047 ASID=007B
PSW AT TIME OF ERROR 070C1000 8155EE6E ILC 2 INTC 0D
. . . . . .
. . . . . .
******************************** BOTTOM OF DATA *********************************
Private Storage Analysis
By looking at the IEA705I, you can also see that the GETMAIN was unconditional for 32K of subpool 55 with backing storage (real) above or below 16 megabytes and virtual storage either above or below. When LOC=ANY is coded on the GETMAIN, VSM first looks to satisfy the request from above 16 megabytes. If unsuccessful, VSM then looks to satisfy the request from below 16 megabytes.
However, this does not necessarily indicate that subpool 55 was over-allocated. It just means that the virtual storage area that is constrained is the private areas that includes the LSQA. Use the Abend-AID Viewer MVS Storage Analysis function to examine the allocations in the private areas.
You can access the MVS Storage Analysis option from the MVS Information menu, which is a selection on the Report Menu for region dump analysis (Report Menu for SVC Dump Analysis). Alternatively, once you have selected a region dump, you can enter the MVSSTG fast-path command from the command line on any Abend-AID Viewer screen to directly access the MVS Storage Analysis menu, as shown in the following figure.
MVS Storage Analysis Menu
OPTION ===>
1 VSMAP Virtual Storage Map 8 SQASP SQA Subpools
2 PVTSUM Private Area Summary 9 CSASUM CSA Summary
3 PVTSP Private Subpools 10 CSASP CSA Subpools
4 LSQA LSQA Summary 11 LPAMAP LPA Map
5 LSQASP LSQA Subpools 12 NUCMAP Nucleus Map
6 ASMAP Allocated Storage Map 13 MEMOBJ Memory Objects
7 SQASUM SQA Summary 14 DSPACE Data Spaces
The Virtual Storage Map, shown in the following figure, is a good place to start for any issues regarding storage allocations because it provides an overall picture of the address space. You can access this screen by selecting menu option 1 from the MVS Storage Analysis menu, or once you have selected a region dump, you can enter the VSMAP fast-path command from the command line on any Abend-AID Viewer screen.
Virtual Storage Map Screen
COMMAND ===> SCROLL ===> DATA
The Ext User Region had reached the highest allocatable address.
The Ext CSA had no pages converted to Ext SQA.
The CSA had no pages converted to SQA.
The User Region had reached the highest allocatable address.
Starting Ending Size of Total Percent
Storage Area Address Address Area Allocated Allocated
**************** ******** ******** ********** ********** ***********
Ext Private 10300000 7FFFFFFF 1,831,936K 42,432K 2.316
Ext User Region 10300000 122FFFFF 32,768K 32,768K 100.000
Ext CSA 08540000 102FFFFF 128,768K 107,732K 83.664
Ext MLPA 0853F000 0853FFFF 4K
Ext FLPA 0853C000 0853EFFF 12K
Ext PLPA 04E2C000 0853BFFF 56,384K
Ext SQA 022FE000 04E2BFFF 44,216K 43,176K 97.648
Ext Nuc (R/W) 0165E000 022FDFFF 12,928K
Ext Nuc (R/O) 01000000 0165DFFF 6,520K
- 16Mb Line ---- -------- -------- ---------- ---------- -----------
Nucleus (R/O) 00FD9000 00FFFFFF 156K
Nucleus (R/W) 00FC3000 00FD8FFF 88K
SQA 00EA7000 00FC2FFF 1,136K 1,136K 100.000
The amount of storage allocated in each area except for the LPA and nucleus areas is displayed, along with the percentages these amounts represent. These figures are accumulated/calculated from the actual allocations found during analysis of the address space.
The analysis programs can produce messages in the Dump Analysis Message Log if errors or conditions such as invalid VSM control blocks are found. Normally you can find invalid control blocks for SQA DFEs or CSA DQEs and FQEs if the QUIESCE=NO option was specified on the SDUMP (X) request. QUIESCE=NO leaves the system dispatchable during the dumping of the SQA and CSA so that these areas can be modified (GETMAIN/FREEMAIN) such that the control blocks no longer reflect the storage dumped. Error detection is done such that processing stops only for looping conditions or broken chains, such as a DFE chain that causes the same series of DFEs to be repeatedly processed. This could significantly throw off the calculations of free areas.
From the Virtual Storage Map screen in the fixed header, you can see that both user regions had hit the highest allocatable address allowed. This information confirms that the private areas were indeed constrained, more specifically the user regions. Exactly what this indicates is described in the explanation of the Private Area Summary screen below. Also note that the SQA had reached 100 percent allocation and that any further requests for SQA subpools will have to be allocated from the CSA.
User Region Analysis
You can find further detailed information on the Private Area Summary screen, as shown in the following figure. You can navigate to this screen from the Virtual Storage Map by using the cursor-point-and-shoot feature and pressing Enter at the Ext Private, Ext User Region, Private, or User Region field under the Storage Area column. Alternatively, after you have selected a region dump, you can enter the PVTSUM fast-path command on the command line from any Abend-AID Viewer screen. This screen is also option 2 from the MVS Storage Analysis menu.
Private Area Summary Screen
COMMAND ===>
LDA Address................ 7FF15EB0
Region Size (Kbytes)....... 8,192
To view the local system queue area select LSQA
To view a list of allocated subpools select List
Extended Private Area Private Area
Maximum Address............ 7FFFFFFF Maximum Address............ 008FFFFF
Low MVS Page Address....... 7F68C000 Low MVS Page Address....... 00899000
User Region Limit Address.. 122FFFFF User Region Limit Address.. 00814FFF
High User Region Address... 122FFFFF High User Region Address... 00814FFF
Starting Address........... 10300000 Starting Address........... 00005000
Maximum Size (Kbytes)...... 1,831,936 Maximum Size (Kbytes)...... 9,196
Limit Size (Kbytes)........ 32,768 Limit Size (Kbytes)........ 8,256
Adjusted Size (Kbytes)..... 32,768 Adjusted Size (Kbytes)..... 8,192
Free Blocks Available...... Yes Free Blocks Available...... Yes
SM Block Address........... 7F80C000
SM Block Size (Kbytes)..... 7,932
This screen displays detailed information on both the extended private and private areas. The local data area (LDA) is the VSM anchor block for information specific to an address space. The first five lines under each grouping maps the private areas from the top of each area down to the start of each area. The private areas are further broken down into areas reserved for the operating system and its subsystems (MVS high private), and for user programs running in problem state (user region). The MVS high private area is where LSQA, scheduler work area (SWA), and authorized user key subpools are allocated from. These subpools are allocated from the top of the private area downward, while the user region subpools (0-127, 251, 252) are allocated from the start of the private area upward. No boundaries exist between LSQA, SWA, and authorized user key storage. They are all interspersed with each other, which can be seen on the Allocated Storage Map under the E/PVT Area column.
The user regions are limited in size depending on how the REGION parameter is coded on the JOB or EXEC statement, or whether the site chooses to override the defaults via system exit IEFUSI or IEALIMIT (controls below 16megabyte private area only). Refer to the IBM OS/390 MVS installation exits manual for default limits or for coding either of these exits. Although there may be a limit on the user region, this does not place a limit on the MVS high private area. These subpools can be allocated from below the user region limit, but not below the highest allocated user region address (or page) also known as the top of the user region. This top is dynamic as storage is allocated and freed. Therefore, the low MVS page address line may be above or below the user region limit address line.
Keep in mind that MVS recovery/termination requires LSQA below 16 megabytes; and if it cannot be acquired, the address space will be terminated. When this occurs, an SVC dump is rarely usable.
This address space had REGION=8M or 8192K coded since the Region Size (Kbytes) field has 8,192. Note that the User Region Limit and High User Region Address fields contain the same addresses, 122FFFFF and 00814FFF. Note also that both Free Blocks Available fields display Yes, indicating free blocks of storage do exist. Use the cursor-point-and-shoot feature and press Enter at the Yes field under the Extended Private Area column to display the Free Block Queue Elements screen, as shown in the following figure. The significance of the Low MVS Page Address field is further discussed in LSQA Analysis.
Free Block Queue Elements Screen, Extended Private Area
COMMAND ===> SCROLL ===> DATA
Total free storage (K)...... 1,789,500 Free Below High User (K)... 0
Maximum Address.............. 7FFFFFFF Free from User to Limit (K) 0
Low MVS Page Address......... 7F68C000 Free from Limit to MVS (K). 1,789,488
User Region Limit Address.... 122FFFFF Free Between User & MVS (K) 1,789,488
High User Region Address..... 122FFFFF Free Above Low MVS (K)..... 12
FBQE Start of End of Size of
Address Area Area Area Location
******** ******** ******** ********** **********************************
7F765778 12300000 7F68BFFF 1,789,488K Between High User Region & Low MVS
7F697358 7F68E000 7F68EFFF 4K Above the Low MVS Page Address
7F697478 7F691000 7F692FFF 8K Above the Low MVS Page Address
****************************** BOTTOM OF DATA *********************************
The Free Block Queue Elements screen displays all the blocks of unallocated storage in the extended private area. The first free block starts at 12300000 to 7F68BFFF for 1,789,488K, which means that the only free blocks are above the limit of the extended user region. In other words, the entire extended user region is allocated. Note that the Free from User to Limit (K) field in the header is 0, which could mean that the extended user region limit needs to be increased. Note also that the Free from Limit to MVS (K) field is 1,789,488K. Therefore, the extended user limit could be increased if necessary.
Press the End (PF3) key to return to the Private Area Summary screen. Use the cursor-point-and-shoot feature and press Enter at the Yes displayed in the Free Blocks Available field under the Private Area section to display the Free Block Queue Elements screen for the private area, as shown in the following figure.
Free Block Queue Elements Screen, Private Area
COMMAND ===> SCROLL ===> DATA
Total free storage (K)...... 548 Free Below High User (K)... 20
Maximum Address.............. 008FFFFF Free from User to Limit (K) 0
Low MVS Page Address......... 00899000 Free from Limit to MVS (K). 528
User Region Limit Address.... 00814FFF Free Between User & MVS (K) 528
High User Region Address..... 00814FFF Free Above Low MVS (K)..... 0
FBQE Start of End of Size of
Address Area Area Area Location
******** ******** ******** ********** **********************************
7F69FEF8 0080F000 00813FFF 20K Below the High User Region Address
7F765448 00815000 00898FFF 528K Between High User Region & Low MVS
****************************** BOTTOM OF DATA *********************************
The first free block starts at 0080F000 to 00813FFF with a size of 20K. Although the user region has some unallocated storage remaining, this amount is not enough to satisfy the GETMAIN request for 32K. There is another free block from 00815000 to 00898FFF of 528K, but it is above the user region limit. This block corresponds with the 00899000 in the Low MVS Page Address field displayed in the private area section of the Private Area Summary screen.
From the Free Block Queue Elements screen for the private areas, note that there is only 20K available in the user region below 16 megabytes, and there is nothing available in the extended user region. The GETMAIN for subpool 55 of 32K failed for this reason. The next step is to determine what subpools in the user regions if any are excessively allocated, or if the user region limits needs to be increased. If there are excessive allocations, the owner/allocator needs to be identified.
Press the END (PF3) key to return to the Private Area Summary screen. From this screen, use the cursor point-and-shoot feature and press Enter at the List field in the header to display the Allocated Private Subpools screen, as shown in the following figure. Alternatively, you can enter the PVTSP fast-path command on the command line of any Abend-AID Viewer screen once you have selected a region dump.
Allocated Private Subpools Screen
COMMAND ===> SCROLL ===> DATA
==>
Private Size (Kbytes)....................... 9,196
Extended Private Size (Kbytes).............. 1,831,936
Total Private Allocated (Kbytes)............ 8,604
Total Extended Private Allocated (Kbytes)... 33,936
To view a summary of these subpools select Summarize
To view user region subpools select User Region
To view scheduler work area subpools select SWA
To view authorized user key subpools select Authorized
TCB Allocated Percent of Allocated Percent of
Id Key Ownership Address <16Mb Total <16Mb >16Mb Total >16Mb
*** *** ********* ******** ********** *********** ********** ***********
229 0 OWN 008FE1B8 0K 0.000 0K 0.000
229 1 OWN 008FE1B8 0K 0.000 28K 0.083
229 5 OWN 008FE1B8 0K 0.000 136K 0.401
229 8 OWN 008FE1B8 0K 0.000 32K 0.094
230 0 OWN 008FE1B8 4K 0.046 32K 0.094
230 1 OWN 008FE1B8 28K 0.325 40K 0.118
230 2 OWN 008FE1B8 4K 0.046 8K 0.024
230 3 OWN 008FE1B8 4K 0.046 8K 0.024
The Allocated Private Subpools screen displays a list of allocated subpools that are chained off each task control block (TCB) found in the address space. The TCBs are processed in the order found on the TCB Summary screen. The LSQA subpools do not appear on this screen because they are not chained off the TCB. They are found from the AQATINDX and AQAT control blocks. However, the SWA and authorized user key subpools are chained off the TCB and appear here. Because it was previously determined that the user regions were constrained, use the cursor point-and-shoot feature and press Enter at the User Region field in the header to display the Allocated Private Subpools screen for the user region subpools only, as shown in the following figure.
Allocated Private Subpools Screen for User Regions
COMMAND ===> SCROLL ===> DATA
==>
Private Size (Kbytes)....................... 9,196
Extended Private Size (Kbytes).............. 1,831,936
Total Private Allocated (Kbytes)............ 8,604
Total Extended Private Allocated (Kbytes)... 33,936
To view a summary of these subpools select Summarize
To view scheduler work area subpools select SWA
To view authorized user key subpools select Authorized
TCB Allocated Percent of Allocated Percent of
Id Key Ownership Address <16Mb Total <16Mb >16Mb Total >16Mb
*** *** ********* ******** ********** *********** ********** ***********
0 0 OWN,SHR 008FDE28 0K 0.000 0K 0.000
0 8 OWN,SHR 008EC9B0 52K 0.604 1,396K 4.114
252 0 OWN 008EC9B0 0K 0.000 0K 0.000
0 8 SHR 008C9BF8
8 8 OWN 008C9BF8 0K 0.000 0K 0.000
131 8 OWN 008C9BF8 0K 0.000 0K 0.000
132 1 OWN 008C9BF8 0K 0.000 0K 0.000
132 5 OWN 008C9BF8 0K 0.000 0K 0.000
132 8 OWN 008C9BF8 24K 0.279 108K 0.318
This screen lists the total allocations for a subpool only if it is owned (OWN or OWN,SHR), but not if it is shared (SHR). Incorrect calculations would otherwise result because the descriptor queue elements (DQEs) would be counted more than once. If you select a subpool that is SHR only, the Private Subpool Detail screen displays with the owning TCB address in the header as well as the DQEs and FQEs as if the subpool of the owning TCB had been selected. User region subpools can be summarized since a subpool can appear more than once whether it is owned exclusively or shared with other TCBs. On the Allocated Private Subpools screen, use the cursor point-and-shoot feature and press Enter at the Summarize field to display the Summarized Private Subpools screen, as shown in the following figure.
Summarized Private Subpools
COMMAND ===> SCROLL ===> DATA
Private Size (Kbytes)....................... 9,196
Extended Private Size (Kbytes).............. 1,831,936
Total Private Allocated (Kbytes)............ 8,604
Total Extended Private Allocated (Kbytes)... 33,936
Allocated Percent of Allocated Percent of Total Percent of
Id <16Mb Total <16Mb >16Mb Total >16Mb Allocated <16M + >16M
*** ********** *********** ********** *********** ********** ***********
0 52K 0.604 1,396K 4.114 1,448K 3.404
1 4K 0.046 0K 0.000 4K 0.009
2 4K 0.046 20K 0.059 24K 0.056
3 4K 0.046 16K 0.047 20K 0.047
8 0K 0.000 0K 0.000 0K 0.000
55 1,948K 22.641 12,292K 36.221 14,240K 33.474
66 4K 0.046 4K 0.012 8K 0.019
82 0K 0.000 512K 1.509 512K 1.204
97 0K 0.000 20K 0.059 20K 0.047
100 0K 0.000 544K 1.603 544K 1.279
127 0K 0.000 0K 0.000 0K 0.000
131 0K 0.000 0K 0.000 0K 0.000
132 24K 0.279 108K 0.318 132K 0.310
You can sort the Summarized Private Subpools screen by any of the columns. However, because the extended area is used first for GETMAINs with LOC=ANY, sort the screen by the Allocated > 16Mb column to show what subpool is using the most amount of extended user region. Enter the SORT primary command or type SORT on the command line and press Enter at the Allocated > 16 Mb column heading. Enter the BOTTOM primary command or type MAX and press the DOWN (PF8) key to scroll to the bottom of the data, as shown in the following figure. Note that subpool 252 has the most allocated.
Summarized Private Subpools Screen, Sorted and Scrolled Down
COMMAND ===> SCROLL ===> DATA
Private Size (Kbytes)....................... 9,196
Extended Private Size (Kbytes).............. 1,831,936
Total Private Allocated (Kbytes)............ 8,604
Total Extended Private Allocated (Kbytes)... 33,936
Allocated Percent of Allocated Percent of Total Percent of
Id <16Mb Total <16Mb >16Mb Total >16Mb Allocated <16M + >16M
*** ********** *********** ********** *********** ********** ***********
127 0K 0.000 0K 0.000 0K 0.000
66 4K 0.046 4K 0.012 8K 0.019
3 4K 0.046 16K 0.047 20K 0.047
2 4K 0.046 20K 0.059 24K 0.056
97 0K 0.000 20K 0.059 20K 0.047
132 24K 0.279 108K 0.318 132K 0.310
82 0K 0.000 512K 1.509 512K 1.204
100 0K 0.000 544K 1.603 544K 1.279
0 52K 0.604 1,396K 4.114 1,448K 3.404
251 1,296K 15.063 5,288K 15.582 6,584K 15.477
55 1,948K 22.641 12,292K 36.221 14,240K 33.474
252 4,900K 56.950 12,568K 37.034 17,468K 41.063
****************************** BOTTOM OF DATA *********************************
Press the END (PF3) key to return to the Allocated Private Subpools screen for user regions only. Enter the SORT primary command, or type SORT on the command line and press Enter at the Allocated > 16 Mb column heading. Enter the BOTTOM primary command, or type MAX on the command line and press the DOWN (PF8) key to scroll to the bottom of the data, as shown in the following figure.
Allocated Private Subpools Screen, Sorted and Scrolled Down
COMMAND ===> SCROLL ===> DATA
==>
Private Size (Kbytes)....................... 9,196
Extended Private Size (Kbytes).............. 1,831,936
Total Private Allocated (Kbytes)............ 8,604
Total Extended Private Allocated (Kbytes)... 33,936
To view a summary of these subpools select Summarize
To view scheduler work area subpools select SWA
To view authorized user key subpools select Authorized
TCB Allocated Percent of Allocated Percent of
Id Key Ownership Address <16Mb Total <16Mb >16Mb Total >16Mb
*** *** ********* ******** ********** *********** ********** ***********
132 8 OWN 008C9BF8 24K 0.279 108K 0.318
82 8 OWN 008C9A60 0K 0.000 512K 1.509
100 8 OWN,SHR 008B2748 0K 0.000 544K 1.603
0 8 OWN,SHR 008EC9B0 52K 0.604 1,396K 4.114
55 8 OWN 008C97D0 1,948K 22.641 4,100K 12.082
251 8 OWN 008C9BF8 1,296K 15.063 5,288K 15.582
55 8 OWN 008C9A60 0K 0.000 8,192K 24.140
252 0 OWN 008C9BF8 4,900K 56.950 12,568K 37.034
****************************** BOTTOM OF DATA *********************************
Use the cursor point-and-shoot feature and press Enter at 252 to display the Private Subpool Detail screen for this subpool. Press the RIGHT (PF11) key to display the right-most portion of the screen, as shown in the following figure.
Private Subpool Detail Screen
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 252 SPQA Address................ 7FF15640
Key......................... 0 Allocated <16Mb (Kbytes).... 4,900
SPQE Address................ 7F765388 Allocated >16Mb (Kbytes).... 12,568
TCB Address................. 008C9BF8 Total Allocated (Kbytes).... 17,468
Ownership................... OWN Free <16Mb.................. 7,440
Free >16Mb.................. 36,528
Total Free.................. 43,968
DQE Backing Area Size of Data
Address Storage Address Area Address First 32 Bytes of Data
******** ******** ******** ********** ******** ***************************
7F6EC268 BELOW 00008000 192 000080C0 CIPT.....FP . .. ... l.
7F735DA8 BELOW 0001A000 1,592 0001A638 *DFHASV . w 0410I UN647
7F765C88 BELOW 0001B000 0001B000 CIST. ...... l.. _.."{ CF
7F6D7070 BELOW 0001F000 1,888 0001F760 00 IGZECIC .C24.003/20/
7F7359E8 ANYWHERE 0000D000 3,768 0000DEB8 ... .. ..... .. .......
7F7656B8 ANYWHERE 00080000 00080000 . >MODHEAD P.410DFHDUIO 06/
7F6EC430 ANYWHERE 001C0000 001C0000 DFHYA160 0. 00. 00 00} 00
7F6D7280 ANYWHERE 10300000 10300000 . >MODHEAD P.410DFHKEDCL10/
7F735640 ANYWHERE 103FB000 103FB000 .... ?" $8 ?a . }..}
24 103FB5E8 . {q.. . {q. .........
Not only is the DQE and FQE information displayed, but as an aid in attempting to determine the ownership of the storage, the first 32 bytes of allocated storage is displayed. Several first 32 bytes for a DQE may exist if there is free storage (FQE) within that DQE. The methods used in displaying the first 32 bytes of data are the following:
- If there is no free area within a DQE, the first 32 bytes are at the start of the DQE, or DQE area address. Data address reflects this.
- If there are FQEs, there are additional first 32 bytes after each free area as determined by adding FQE area size to FQE area address. Data address reflects this calculation.
- If the free area is at the end of the DQE, << REACHED END OF DQE AREA >> is displayed. Data address is blank.
- If the page on which the allocation is located is not contained in the SDUMP data set, << STORAGE NOT AVAILABLE >> is displayed.
Looking at these first 32 bytes of data, you see that subpool 252 contains either programs or CICS DSA data. You can select a DSA name on the CICS Environment Summary or the Dynamic Storage Area Summary to determine what subpool the DSAs are in. See Enhanced Memory Display for information about how these screens can be used along with an enhancement to the Memory Display screen.
Press the END (PF3) key to return to the Allocated Private Subpools screen again. Next, use the cursor point-and-shoot feature and press Enter at the subpool with the next most extended storage allocated, subpool 55, to display the associated Private Subpool Detail screen. Press the RIGHT (PF11) key to display the right-most portion of the screen, as shown in the following figure.
Private Subpool Detail Screen, Scrolled Right
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 55 SPQA Address................ 7F6F9400
Key......................... 8 Allocated <16Mb (Kbytes).... 0
SPQE Address................ 7F6F93E8 Allocated >16Mb (Kbytes).... 8,192
TCB Address................. 008C9A60 Total Allocated (Kbytes).... 8,192
Ownership................... OWN Free <16Mb.................. 0
Free >16Mb.................. 81,920
Total Free.................. 81,920
DQE Backing Area Size of Data
Address Storage Address Area Address First 32 Bytes of Data
******** ******** ******** ********** ******** ***************************
7F6F9418 ANYWHERE 115F7000 1,280 115F7500 >VECTTBY...................
7F6F9448 ANYWHERE 116E1000 1,280 116E1500 >VECTTBY...................
7F6F9478 ANYWHERE 11701000 1,280 11701500 >VECTTBY...................
7F6F94A8 ANYWHERE 11721000 1,280 11721500 >VECTTBY...................
7F6F94D8 ANYWHERE 11741000 1,280 11741500 >VECTTBY...................
7F6F9508 ANYWHERE 11761000 1,280 11761500 >VECTTBY...................
7F6F9538 ANYWHERE 11781000 1,280 11781500 >VECTTBY...................
7F6F9568 ANYWHERE 117A1000 1,280 117A1500 >VECTTBY...................
7F6F9598 ANYWHERE 117C1000 1,280 117C1500 >VECTTBY...................
7F6F95C8 ANYWHERE 117E1000 1,280 117E1500 >VECTTBY...................
In addition to looking at the first 32 bytes of data, watch for large size DQEs. You can see repeated allocations of 129,792 bytes, just 1,280 bytes less than 128K. All of the allocations have an eyecatcher of >VECTTBY so now you can use the TCB address to identify the owner. However, if the subpool were shared (OWN,SHR) among several TCBs, it would not be so easy to identify the owner. This situation is usually the case with subpool 0.
Press the END (PF3) key to return to the Allocated Private Subpools screen. Note that the TCB address owning subpool 55 is 008C9A60. At the command line, enter the TCBS fast-path command to display the TCB Summary screen, as shown in the following figure. Enter the BOTTOM primary command, or type MAX on the command line and press the DOWN (PF8) key to scroll to bottom of the display, where the TCB address for subpool 55 is located. Note that the program running on that TCB is VENXPGMY. Keep in mind that there may be several programs that run/ran on a TCB, but in the case of a vendor product, they will usually all be owned by that vendor.
TCB Summary Screen
COMMAND ===> SCROLL ===> DATA
==>
Job Name................. CCFXC410 Number of TCBs........... 14
Abend Date............... 03JUN2019 Number of RBs............ 19
Abend Time............... 11:42:49
R RTM2 Work Area S Save Area Trace G RB Register Contents
E TCB Storage I EPIE L TCB Load List
K Linkage Stack D TCB Detail C LE Information
TCB RB RB Interrupt Completion I
Address Abend Address Type Program Offset Code Code L
******** ***** ******** **** ******** ****** **** ***** *
008CB7D0 PRB DFHSIP 00CDD2 0001 2
_ 008CB498 008CB410 PRB DFHJCOCP 0000B6 0001 2
_ 008B20C8 PRB DFHAPSIP 001066 0006 2
_ 008B2AC8 008A2378 PRB DFHSKTSK 000000 0001 2
_ 008B2748 008B26C0 PRB CTCCJCDP 0001CA 0001 2
_ 008B2528 008B2460 PRB CTCCJVUE 0005C2 0001 2
_ 008C9A60 008C99C8 PRB VENXPGMY 0001A6 0001 2
_ 008C97D0 <TCB 008FFC10 SVRB 000C S878 2
_ RB> 008FF928 SVRB 0033 2
***************************** BOTTOM OF DATA ********************************
Now that the owning TCB is identified, the entry point address is displayed in the hope some copyright information is in the program. Note the data in the Offset column (X'1A6'), and press the RIGHT (PF11) key to display the right-most portion of the screen. Use the cursor point-and-shoot feature and press Enter at the second fullword of the data in the PSW column to display the Storage Disassembly screen, as shown in the following figure.
Storage Disassembly Screen
COMMAND ===> SCROLL ===> DATA
Address Offset Object Code Mnemonic and Operands
115C7F8E 00000000 47F0 C1C8 B 456(,R12)
115C7F92 00000004 0000 DATA
115C7F94 00000006 D4C1 C9D5 7CF8 NC 2517(194,R12),3320(R7)
115C7F9A 0000000C F0F0 0000 D4C1 SRP 0(16,R0),1217(R13),0
115C7FA0 00000012 C9D5 DATA IN
115C7FA2 00000014 7CF8 F2F0 ME R15,752(R8,R15)
115C7FA6 00000018 0000 DATA
115C7FA8 0000001A D4C1 C9D5 7CF8 NC 2517(194,R12),3320(R7)
115C7FAE 00000020 F4F0 DATA 40
115C7FB0 00000022 5830 D004 L R3,4(,R13)
115C7FB4 00000026 50F0 3010 ST R15,16(,R3)
115C7FB8 0000002A 47F0 C1DC B 476(,R12)
115C7FBC 0000002E 0000 DATA
115C7FBE 00000030 0070 DATA
115C7FC0 00000032 0000 DATA
115C7FC2 00000034 4203 5800 STC R0,2048(R3,R5)
115C7FC6 00000038 C1D4 DATA AM
115C7FC8 0000003A 181D LR R1,R13
115C7FCA 0000003C 58F0 C1D8 L R15,472(,R12)
115C7FCE 00000040 0A78 SVC 120 FREEMAIN
Use the cursor point-and-shoot feature and press Enter at the address of the PSW to display the Memory Display. At the command line, enter -1A6 to move the display back to the EPA, as shown in the following figure.
Memory Display Screen
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 115C7F8E Comment: __________________________________________
115C7DE8 area EPVT sp 251 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
115C7DE8 -000001A6 47F0F0A2 E5C5D5E7 D7C7D4E8 40F0F64B * 00sVENXPGMY 06.*
115C7DF8 -00000196 F0F64BF0 F640D7E3 C660F0F3 F0F6F940 *06.06 PTF-03069 *
115C7E08 -00000186 F0F661F2 F261F0F0 7CF0F74B F1F85C5C *06/22/00@07.18***
115C7E18 -00000176 40E5C5D5 C4D6D940 D7D9D6C4 E4C3E340 * VENDOR PRODUCT *
115C7E28 -00000166 E8404DC3 5D40F1F9 F6F06BF2 F0F0F040 *Y (C) 1960,2000 *
115C7E38 -00000156 E5C5D5C4 D6D940E7 40C3D6D9 D74B40E4 *VENDOR X CORP. U*
115C7E48 -00000146 D5D7E4C2 D3C9E2C8 C5C460D9 C9C7C8E3 *NPUBLISHED-RIGHT*
115C7E58 -00000136 E240D9C5 E2C5D9E5 C5C440E4 D5C4C5D9 *S RESERVED UNDER*
115C7E68 -00000126 40E3C8C5 40C3D6D7 E8D9C9C7 C8E340D3 * THE COPYRIGHT L*
115C7E78 -00000116 C1E6E240 D6C640E3 C8C540E4 4BE24B40 *AWS OF THE U.S. *
115C7E88 -00000106 5C5C90EC D00C18CF 47F0C0B4 00000070 *** } 0{ ... *
115C7E98 -000000F6 00004212 5800C0AC 58F0C0B0 1B110A78 *.. .{ 0{ *
115C7EA8 -000000E6 12FF4770 C1EA5010 D00850D0 100418D1 * A & } &} J*
115C7EB8 -000000D6 5080D048 41700001 47F0C0E4 00080000 *&"} . 0{U. ..*
115C7EC8 -000000C6 00006472 5800C0DC 58F0C0E0 1B110A78 *.. .{ 0{\ *
115C7ED8 -000000B6 12FF4770 C1BE1841 5040D06C D2074000 * A & }%K .*
Looking in the Storage column at the copyright text, you can see that Vendor X owns this module, and it is at release 6.6.0 with a PTF level of 03069 dated 06/22/00. Press the END (PF3) key three times to return to the Allocated Private Subpools screen. Note that there is another subpool 55 allocation, and its TCB address is 008C97D0. Enter the TCBS fast-path command to display the TCB Summary screen for this subpool. Enter the BOTTOM primary command, or type MAX on the command line and press the DOWN (PF8) key to scroll down to the TCB address for this subpool, as shown in the following figure.
TCB Summary Screen
COMMAND ===> SCROLL ===> DATA
==>
Job Name................. CCFXC410 Number of TCBs........... 14
Abend Date............... 03JUN2019 Number of RBs............ 19
Abend Time............... 11:42:49
R RTM2 Work Area S Save Area Trace G RB Register Contents
E TCB Storage I EPIE L TCB Load List
K Linkage Stack D TCB Detail C LE Information
TCB RB RB Interrupt Completion I
Address Abend Address Type Program Offset Code Code L
******** ***** ******** **** ******** ****** **** ***** *
_ 008CB498 008CB410 PRB DFHJCOCP 0000B6 0001 2
_ 008B20C8 PRB DFHAPSIP 001066 0006 2
_ 008B2AC8 008A2378 PRB DFHSKTSK 000000 0001 2
_ 008B2748 008B26C0 PRB CTCCJCDP 0001CA 0001 2
_ 008C9A60 008C99C8 PRB VENXPGMY 0001A6 0001 2
_ 008C97D0 <TCB 008FFC10 SVRB 000C S0C4 2
_ RB> 008FF928 SVRB 0033 2
_ 008A0388 PRB VENXPGMZ 0001A8 0078 2
***************************** BOTTOM OF DATA ********************************
The TCB Summary screen shows this is program VENXPGMZ, and it is also owned by the same vendor. Enter the E (TCB Storage) line command next to the TCB address to display all private area subpools allocated by the TCB, as shown in the following figure. The total amount of storage allocated below, above, and combined by the TCB is shown in the header.
Allocated Private Subpools Screen
COMMAND ===> SCROLL ===> DATA
==>
Private Size (Kbytes)....................... 9,196
Extended Private Size (Kbytes).............. 1,831,936
Total Private Allocated (Kbytes)............ 8,604
Total Extended Private Allocated (Kbytes)... 33,936
Total Allocated to TCB <16Mb (Kbytes)....... 1,980
Total Allocated to TCB >16Mb (Kbytes)....... 4,132
Total Amount Allocated to TCB (Kbytes)...... 6,112
TCB Allocated Percent of Allocated Percent of
Id Key Ownership Address <16Mb TCB <16Mb >16Mb TCB >16Mb
*** *** ********* ******** ********** *********** ********** ***********
229 0 OWN 008C97D0 0K 0.000 0K 0.000
229 5 OWN 008C97D0 0K 0.000 0K 0.000
229 8 OWN 008C97D0 16K 0.808 0K 0.000
229 10 OWN 008C97D0 0K 0.000 0K 0.000
230 0 OWN 008C97D0 4K 0.202 8K 0.194
230 1 OWN 008C97D0 0K 0.000 4K 0.097
230 5 OWN 008C97D0 8K 0.404 4K 0.097
230 8 OWN 008C97D0 4K 0.202 4K 0.097
230 10 OWN 008C97D0 0K 0.000 8K 0.194
The vendor needs to determine if this is a normal situation, and if it is, to make recommendations for increasing the limit on user region storage. If it is not normal, then the vendor needs to remedy the situation.
LSQA Analysis
If the over-allocated storage was in MVS high private (LSQA, SWA, or authorized user subpool), it would be difficult to identify the culprit since these subpools are allocated indirectly by calls to system/subsystem services. For example, issuing an ATTACH macro allocates subpool 255 storage for the TCB, or an OPEN macro allocates subpool 230 storage for the DEB. However, the Virtual Storage Map and the Private Area Summary screens indicate if MVS high private is over-allocated.
Select the VSMAP option (1) from the MVS Storage Analysis menu or enter the VSMAP fast-path command from any Abend-AID screen after you have selected the region dump. The Virtual Storage Map is displayed, as shown in the following figure. Note that neither user region had hit the highest allocatable address, yet an 878-10 abend had occurred in this address space. Looking at the Ext Private area, which includes MVS high private, note that it is only 3.049 percent allocated. The Ext User Region does have a limit of 131,584K, but is only 33.375 percent allocated, so there is no problem in extended private.
Virtual Storage Map Screen
COMMAND ===> SCROLL ===> DATA
The Ext User Region had not reached the highest allocatable address.
The Ext CSA had no pages converted to Ext SQA.
The CSA had no pages converted to SQA.
The User Region had not reached the highest allocatable address.
Starting Ending Size of Total Percent
Storage Area Address Address Area Allocated Allocated
**************** ******** ******** ********** ********** ***********
Ext Private 13100000 7FFFFFFF 1,784,832K 54,420K 3.049
Ext User Region 13100000 1B17FFFF 131,584K 43,916K 33.375
Ext CSA 0C2C5000 130FFFFF 112,876K 80,084K 70.949
Ext MLPA 00000000 00000000 0K
Ext FLPA 0C2C2000 0C2C4FFF 12K
Ext PLPA 08A3E000 0C2C1FFF 57,872K
Ext SQA 026AD000 08A3DFFF 101,956K 100,724K 98.792
Ext Nuc (R/W) 0165F000 026ACFFF 16,696K
Ext Nuc (R/O) 01000000 0165EFFF 6,524K
- 16Mb Line ---- -------- -------- ---------- ---------- -----------
Nucleus (R/O) 00FD9000 00FFFFFF 156K
Nucleus (R/W) 00FC9000 00FD8FFF 64K
SQA 00CDE000 00FC8FFF 2,988K 2,988K 100.000
Enter the BOTTOM primary command, or type MAX and press the DOWN (PF8) key to scroll down to display the data for below the line, as shown in the following figure. Looking at the private area, you will see that it is 99.462 percent allocated, so the problem is below the line. More importantly, the user region is also limited at 7,680K, yet is only 26.719 percent allocated. This data indicates that the MVS high private is consuming 74.351 percent of the private area (8128K - 2052K = 6076K; 6076K/8172K = 74.351 percent).
Virtual Storage Map Screen
COMMAND ===> SCROLL ===> DATA
The Ext User Region had not reached the highest allocatable address.
The Ext CSA had no pages converted to Ext SQA.
The CSA had no pages converted to SQA.
The User Region had not reached the highest allocatable address.
Starting Ending Size of Total Percent
Storage Area Address Address Area Allocated Allocated
**************** ******** ******** ********** ********** ***********
- 16Mb Line ---- -------- -------- ---------- ---------- -----------
Nucleus (R/O) 00FD9000 00FFFFFF 156K
Nucleus (R/W) 00FC9000 00FD8FFF 64K
SQA 00CDE000 00FC8FFF 2,988K 2,988K 100.000
PLPA 00BB0000 00CDDFFF 1,208K
FLPA 00BAF000 00BAFFFF 4K
MLPA 00000000 00000000 0K
CSA 00800000 00BAEFFF 3,772K 1,600K 42.418
Private 00005000 007FFFFF 8,172K 8,128K 99.462
User Region 00005000 00784FFF 7,680K 2,052K 26.719
System Region 00001000 00004FFF 16K
PSA 00000000 00000FFF 4K
****************************** BOTTOM OF DATA *********************************
Enter the PVTSUM fast-path command to display the Private Area Summary screen, as shown in the following figure.
Private Area Summary Screen
COMMAND ===>
LDA Address................ 7FF14EB0
Region Size (Kbytes)....... 7,168
To view the local system queue area select LSQA
To view a list of allocated subpools select List
Extended Private Area Private Area
Maximum Address............ 7FFFFFFF Maximum Address............ 007FFFFF
Low MVS Page Address....... 7F532000 Low MVS Page Address....... 0020E000
User Region Limit Address.. 1B17FFFF User Region Limit Address.. 00784FFF
High User Region Address... 15C69FFF High User Region Address... 0020DFFF
Starting Address........... 13100000 Starting Address........... 00005000
Maximum Size (Kbytes)...... 1,784,832 Maximum Size (Kbytes)...... 8,172
Limit Size (Kbytes)........ 131,584 Limit Size (Kbytes)........ 7,680
Adjusted Size (Kbytes)..... 131,072 Adjusted Size (Kbytes)..... 7,168
Free Blocks Available...... Yes Free Blocks Available...... Yes
SM Block Address........... 7F83A000
SM Block Size (Kbytes)..... 7,744
The Private Area Summary screen reveals the storage amounts consumed using addresses. Note the sequence of the User Region Limit Address and Low MVS Page Address, indicating that MVS high private storage has gone below the user region limit. Also note that it could go no lower because the high user region address is right up against it, nor could the user region go any higher. However, what is significant is how far below the user region limit address the low MVS page address has gone.
Use the cursor point-and-shoot feature and press Enter at the LSQA field in the header to display the LSQA Summary screen, as shown in the following figure.
LSQA Summary Screen
COMMAND ===> SCROLL ===> DATA
LDA Address................ 7FF14EB0
To view a summary of LSQA subpools select Summarize
AQATINDX +---------- DFE Queue Origins -----------+
Sp Address Addr <16M Addr >16M Size <16M Size >16M
*** ******** ******************************************
255 7FF15C00 7FF14400 7FF14460 7FF14400 7FF14460
205 7FF15000 -------- 7FF14580 -------- 7FF14580
215 7FF15400 -------- 7FF14520 -------- 7FF14520
225 7FF15800 -------- 7FF144C0 -------- 7FF144C0
****************************** BOTTOM OF DATA *********************************
For a description of the DFE Queue Origins, See SQA Analysis. Use the cursor point-and-shoot feature and press Enter at the Summarize field in the header to display the Summarized LSQA Subpools screen, as shown in the following figure.
Summarized LSQA Subpools Screen
COMMAND ===> SCROLL ===> DATA
Private Size (Kbytes)....................... 8,172
Extended Private Size (Kbytes).............. 1,784,832
Total LSQA Allocated (Kbytes)............... 5,624
Total Extended LSQA Allocated (Kbytes)...... 1,192
Allocated Percent of Allocated Percent of Total Percent of
Id <16Mb Total <16Mb >16Mb Total >16Mb Allocated <16M + >16M
*** ********** *********** ********** *********** ********** ***********
255 5,624K 100.000 292K 24.497 5,916K 86.796
205 0K 0.000 768K 64.430 768K 11.268
215 0K 0.000 120K 10.067 120K 1.761
225 0K 0.000 12K 1.007 12K 0.176
****************************** BOTTOM OF DATA *********************************
Note that subpool 255 has 5624K or 92.560 percent of the 6076K MVS high private allocated below 16M. Use the cursor point-and-shoot feature and press Enter at subpool 255 to display the LSQA Subpool Detail screen, as shown in the following figure.
LSQA Subpool Detail Screen
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 255 Allocated <16Mb (Kbytes).... 5,624
AQATINDX Address............ 7FF15C00 Allocated >16Mb (Kbytes).... 292
Non-zero AQATINDX Entries... 3 Total Allocated (Kbytes).... 5,916
Free <16Mb................. 363,576
Free >16Mb................. 21,896
Total Free................. 385,472
Page DFE Size of DFE AQAT AQAT Index Data
Address Address DFE Area Area Count Address Entry Entry Addr
******** ******** ******** ********* ****** ******** ****** ****** ****
0020F000 7F57B748 0020F000 256 1 7FF16314 32 0 0020
00212000 7F57B6A0 00212000 256 1 7FF16314 33 0 0021
00213000 7F57B760 00213000 1,400 1 7FF16314 33 0 0021
00214000 7F57B778 00214000 256 1 7FF16314 33 0 0021
00215000 7F57B790 00215000 256 1 7FF16314 33 0 0021
0021D000 7F57B6E8 0021D000 256 1 7FF16314 33 0 0021
0021E000 7F57B388 0021E000 256 1 7FF16314 33 0 0021
0021F000 7F57B670 0021F000 256 1 7FF16314 33 0 0021
00220000 7F57B5E0 00220000 256 1 7FF16314 34 0 0022
00221000 7F57B688 00221000 256 1 7FF16314 34 0 0022
00222000 7F57B550 00222000 256 1 7FF16314 34 0 0022
This screen displays an LSQA page, a DFE address, DFE area, size of area, DFE count (if the LSQA page has free storage), AQAT information, data address (of first 32 bytes), and the first 32 bytes of used storage. Having the first 32 bytes of data for each page may aid in determining what kind of data is being stored in the allocated storage. Press the DOWN (PF8) key several times to display subsequent pages for data allocated above the 16Mb boundary. Press the RIGHT (PF11) key to display the right-most portion of the screen. Enter RTM2 in the first four positions of the mask line under the First 32 Bytes of Data column heading to display the multiple RTM2 work areas, as shown in the following figure.
LSQA Subpool Detail Screen, Masked
COMMAND ===> SCROLL ===> DATA
<==
Subpool..................... 255 Allocated <16Mb (Kbytes).... 5,624
AQATINDX Address............ 7FF15C00 Allocated >16Mb (Kbytes).... 292
Non-zero AQATINDX Entries... 3 Total Allocated (Kbytes).... 5,916
Free <16Mb................. 363,576
Free >16Mb................. 21,896
Total Free................. 385,472
Page DFE AQAT Index Data
Address Address Entry Entry Address First 32 Bytes of Data
******** ******** ****** ****** ******** RTM2****************************
7F537000 7F5320D0 83 254 7F537050 RTM2" & . . " .' . h..k"dg".
7F539000 7F57BE80 83 254 7F539050 RTM2" & . . " .#`Y. ..k"dg".
7F53A000 7F57BBF8 83 254 7F53A050 RTM2" & . . " .' . ..k"dg".
7F574000 7F57B970 87 254 7F574050 RTM2" & . . " .#`Y."8 ..k"dg".
7F57C000 7F57B700 87 254 7F57C050 RTM2" {& . . " .#`Y."9 ..k"dg".
7F5B0000 7F57BE38 91 254 7F5B0050 RTM2"$.& . . " .#`Y." ..k"dg".
7F5B2000 7F57BB38 91 254 7F5B2050 RTM2"$ & . . " .#@0." ..k" g".
****************************** BOTTOM OF DATA *********************************
Use the cursor point-and-shoot feature and press Enter at the Data Address 7F537050 field to display the RTM2WA on the Memory Display, as shown in the following figure.
Memory Display Screen
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 7F537050 Comment:
7F53706D area EPVT sp 255 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
7F53706D +0000001D 87800000 00000000 00000000 00000000 *g"..............*
7F53707D +0000002D 00000000 7D212800 21388800 FBFA3081 *....' . h. a*
7F53708D +0000003D 4648B284 87800000 00000000 E192807F * dg".......k""*
7F53709D +0000004D F1300000 00000500 00000400 00087800 *1 .... ... .. .*
7F5370AD +0000005D 00001001 463D907F 5388A012 BD998881 *.. " h rha*
7F5370BD +0000006D 4648B27F F1300881 4648B200 00001007 * "1 a ... *
7F5370CD +0000007D 0C100081 4648C400 02000D00 00000000 * .a D. . .....*
7F5370DD +0000008D 00000000 00000000 00000000 00000000 *................*
7F5370ED +0000009D 00000000 00000000 00000000 00000000 *................*
7F5370FD +000000AD 00000000 00000010 04000100 00000000 *....... . .....*
7F53710D +000000BD 00000000 0000007F 71020000 00000100 *......." .... .*
7F53711D +000000CD 213E5000 00000000 00000000 00000000 * &.............*
7F53712D +000000DD 00000000 00000000 00000000 00000000 *................*
7F53713D +000000ED 00000000 00000000 00000000 00000000 *................*
7F53714D +000000FD 00000000 00000000 00000000 00000000 *................*
7F53715D +0000010D 0000007F 53761800 0000007F 53770800 *..." ...." .*
Enter +1D at the command line. The RTM2CC at +1D indicates an 878 abend, as do all the other RTM2 work areas listed after masking for RTM2. Because there were seven 878 abends, look at IEAVMSGS in the nucleus. Enter the NUCMAP fast-path command on the command line to display the Nucleus Map screen, as shown in the following figure.
Nucleus Map Screen
COMMAND ===> SCROLL ===> DATA
NUCMAP Address........................ 01649470
Nucleus suffix (IEANUC0x)............. 1
Number of Read/Write CSECTs........... 76
Number of Read Only CSECTs............ 87
Number of Ext Read Only CSECTs........ 1,614
Number of Ext Read/Write CSECTs....... 121
Entry CSECT CSECT
Point Name Length Amode Storage Area
******** ******** ******** ***** ****************
00FC9000 IGC217 000000B0 24 Nucleus (R/W)
00FC90B0 IGC238 00000AA8 24 Nucleus (R/W)
00FC9B58 IGC241 000000E0 24 Nucleus (R/W)
00FC9C38 IGC243 00000088 24 Nucleus (R/W)
00FC9CC0 IGC251 00000AA8 24 Nucleus (R/W)
00FCA768 IECVDDT7 0000004C 24 Nucleus (R/W)
00FCA7B8 IECVOPTB 00000118 24 Nucleus (R/W)
00FCA8D0 IECVPRNT 000004F8 31 Nucleus (R/W)
00FCADC8 IRDVDDT 00000048 24 Nucleus (R/W)
00FCAE10 CBROPDDT 0000004C 24 Nucleus (R/W)
00FCAE60 IECVDDTR 0000021C 24 Nucleus (R/W)
Next, enter IEAVMSGS in the mask line under the CSECT Name column heading to locate IEAVMSGS. Use the cursor point-and-shoot feature and press Enter at the Entry Point address to display the Memory Display screen, starting at 01686858, as shown in the following figure.
Memory Display Screen
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 01686858 Comment:
01686858 area ENUC-R/W Mod key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
01686858 +00000000 01686B2C 00E19280 007B79E8 00FEBF80 * , ..k".#`Y. "*
01686868 +00000010 00050878 10000000 00E19280 007B79E8 *. .....k".#`Y*
01686878 +00000020 007B79E8 00141200 00008170 00000000 *.#`Y. ...a ....*
01686888 +00000030 00000000 00E19280 007B7CF0 00FEBF80 *......k".#@0. "*
01686898 +00000040 00050878 10000000 00E19280 007B7CF0 *. .....k".#@0*
016868A8 +00000050 007B7CF0 007F1200 000049C0 00000000 *.#@0." ... {....*
016868B8 +00000060 00000000 00E19280 007B79E8 00FEBF80 *......k".#`Y. "*
016868C8 +00000070 00050878 10000000 00E19280 007B79E8 *. .....k".#`Y*
016868D8 +00000080 007B79E8 00E51200 000009D8 00000000 *.#`Y.V ... Q....*
016868E8 +00000090 00000000 00E19280 007B79E8 8A4F14D4 *......k".#`Y | M*
016868F8 +000000A0 00050878 10000000 00E19280 007B79E8 *. .....k".#`Y*
01686908 +000000B0 007B79E8 00E61200 00002000 00000000 *.#`Y.W ... .....*
01686918 +000000C0 00000000 00E19280 007D2128 00FEBF80 *......k".' . "*
01686928 +000000D0 00050878 10000000 00E19280 007D2128 *. .....k".' *
01686938 +000000E0 007D2128 00E61200 00002000 00000000 *.' .W ... .....*
01686948 +000000F0 00000000 00E19280 007B79E8 811F4BE8 *......k".#`Ya .Y*
Each entry of the IEA705I message variables is x'30' bytes long. Examining the contents of each entry using the IBM OS/390 MVS system messages manual indicates GETMAIN failures for subpools 20, 127, 229, 230, 230, and 229, all below 16M. Although examining IEAVMSGS may be helpful, it doesn't always indicate the subpool that is over-allocated.
Press the END (PF3) key three times to return to the masked LSQA Subpool Detail screen. Enter the RESET primary command on the command line to reset the masking and to redisplay all of the pages. Press the LEFT (PF10) key to display the left-most portion of the screen, as shown in the following figure.
LSQA Subpool Detail Screen
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 255 Allocated <16Mb (Kbytes).... 5,624
AQATINDX Address............ 7FF15C00 Allocated >16Mb (Kbytes).... 292
Non-zero AQATINDX Entries... 3 Total Allocated (Kbytes).... 5,916
Free <16Mb................. 363,576
Free >16Mb................. 21,896
Total Free................. 385,472
Page DFE Size of DFE AQAT AQAT Index Data
Address Address DFE Area Area Count Address Entry Entry Addr
******** ******** ******** ********* ****** ******** ****** ****** ****
0020F000 7F57B748 0020F000 256 1 7FF16314 32 0 0020
00212000 7F57B6A0 00212000 256 1 7FF16314 33 0 0021
00213000 7F57B760 00213000 1,400 1 7FF16314 33 0 0021
00214000 7F57B778 00214000 256 1 7FF16314 33 0 0021
00215000 7F57B790 00215000 256 1 7FF16314 33 0 0021
0021D000 7F57B6E8 0021D000 256 1 7FF16314 33 0 0021
0021E000 7F57B388 0021E000 256 1 7FF16314 33 0 0021
0021F000 7F57B670 0021F000 256 1 7FF16314 33 0 0021
00220000 7F57B5E0 00220000 256 1 7FF16314 34 0 0022
00221000 7F57B688 00221000 256 1 7FF16314 34 0 0022
00222000 7F57B550 00222000 256 1 7FF16314 34 0 0022
Scrolling down the list of allocated pages, note that many have a DFE area address at the beginning with an area size equal to 256. Enter 256 in the last three positions of the mask line under the Size of Area column heading to reveal that 1354 out of 1479 pages have the first 256 bytes free, a suspicious pattern, as shown in the following figure.
LSQA Subpool Detail Screen, Masked
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 255 Allocated <16Mb (Kbytes).... 5,624
AQATINDX Address............ 7FF15C00 Allocated >16Mb (Kbytes).... 292
Non-zero AQATINDX Entries... 3 Total Allocated (Kbytes).... 5,916
Free <16Mb................. 363,576
Free >16Mb................. 21,896
Total Free................. 385,472
Page DFE Size of DFE AQAT AQAT Index Data
Address Address DFE Area Area Count Address Entry Entry Addr
******** ******** ******** ******256 ****** ******** ****** ****** ****
0020F000 7F57B748 0020F000 256 1 7FF16314 32 0 0020
00212000 7F57B6A0 00212000 256 1 7FF16314 33 0 0021
00214000 7F57B778 00214000 256 1 7FF16314 33 0 0021
00215000 7F57B790 00215000 256 1 7FF16314 33 0 0021
0021D000 7F57B6E8 0021D000 256 1 7FF16314 33 0 0021
0021E000 7F57B388 0021E000 256 1 7FF16314 33 0 0021
0021F000 7F57B670 0021F000 256 1 7FF16314 33 0 0021
00220000 7F57B5E0 00220000 256 1 7FF16314 34 0 0022
00221000 7F57B688 00221000 256 1 7FF16314 34 0 0022
00222000 7F57B550 00222000 256 1 7FF16314 34 0 0022
00223000 7F57B580 00223000 256 1 7FF16314 34 0 0022
Press the RIGHT (PF11) key to display the right-most portion of the screen. Use the cursor point-and-shoot feature and press Enter at 0020F100 in the Data Address column to display the Memory Display, as shown in the following figure.
Memory Display Screen
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 0020F100 Comment:
0020F100 area PVT sp 255 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
0020F100 +00000000 0020F130 134D8E1A 10000000 8065A098 *. 1 ( ..." q*
0020F110 +00000010 0380DB00 0020F118 00C00000 00000000 * " .. 1 .{......*
0020F120 +00000020 00000000 1590ED20 00000000 7F6F6158 *.... ...."?/ *
0020F130 +00000030 0020F160 134D8E1A 10000000 8065A098 *. 1- ( ..." q*
0020F140 +00000040 0380DB00 0020F148 00C00000 00000000 * " .. 1 .{......*
0020F150 +00000050 00000000 1590ED20 00000000 7F6F6158 *.... ...."?/ *
0020F160 +00000060 0020F190 134D8E1A 10000000 8065A098 *. 1 ( ..." q*
0020F170 +00000070 0380DB00 0020F178 00C00000 00000000 * " .. 1 .{......*
0020F180 +00000080 00000000 1590ED20 00000000 7F6F6158 *.... ...."?/ *
0020F190 +00000090 0020F1C0 134D8E1A 10000000 8065A098 *. 1{ ( ..." q*
0020F1A0 +000000A0 0380DB00 0020F1A8 00C00000 00000000 * " .. 1y.{......*
0020F1B0 +000000B0 00000000 1590ED20 00000000 7F6F6158 *.... ...."?/ *
0020F1C0 +000000C0 0020F1F0 134D8E1A 10000000 8065A098 *. 10 ( ..." q*
0020F1D0 +000000D0 0380DB00 0020F1D8 00C00000 00000000 * " .. 1Q.{......*
0020F1E0 +000000E0 00000000 1590ED20 00000000 7F6F6158 *.... ...."?/ *
0020F1F0 +000000F0 0020F220 134D8E1A 10000000 8065A098 *. 2 ( ..." q*
At 0020F100 is the address 0020F130; at 0020F130 is 0020F160, and so on. These addresses appear to be a chain of control blocks x'30' in length. At 0020F104 is a pointer (address) into a vendor program. Upon contacting the vendor, they identified it as an ESTAE routine. The chain of control blocks were SCBs created when the vendor repeatedly issued the ESTAE macro without deactivation in between.
Enhanced Memory Display
The enhancement to the Abend-AID Memory Display allows you to determine the storage subpools of the CICS dynamic storage areas (DSAs). From the command line of any region dump screen, enter DSA to display the Dynamic Storage Area Summary screen, as shown in the following figure .
Dynamic Storage Area Summary Screen
COMMAND ===> SCROLL ===> DATA
First Task Subpool SCA.... 1151CD7C First Domain Subpool SCA.... 1152C674
Last Task Subpool SCA..... 1152EAAC Last Domain Subpool SCA..... 1152D674
D Domain Subpool Summary
DSA Total Pages
Name DSA Size Available
***** ******** ********
CDSA 768K 192
UDSA 256K 64
SDSA 256K 64
RDSA 512K 128
ECDSA 4096K 1024
EUDSA 1024K 256
ESDSA 0K 0
ERDSA 3072K 768
***************************** BOTTOM OF DATA ********************************
Use the cursor point-and-shoot feature and press Enter at any of the CICS DSA names to display the Dynamic Storage Area Detail screen, as shown in the following figure.
Dynamic Storage Area Detail Screen
COMMAND ===> SCROLL ===> DATA
DSA Name............ CDSA Free Page Low Water Mark.... 0
DSA Size (Kilobytes) 768 "NOSTG" Returned Count...... 0
Number of Pages..... 192 Total Number of Suspends.... 0
PPA Address......... 103E9580 Current Number Suspended.... 0
Access.............. CICS High Water Mark Suspended... 0
Currently SOS....... NO SOS Cushion Released Count.. 0
SOS Count........... 0 Storage Violation Count..... 0
Time Spent SOS...... 00:00:00.000
The following extents are allocated to the DSA:
Start End
Size Address Address
******** ******** ********
256K 00040000 0007FFFF
256K 00100000 0013FFFF
256K 00140000 0017FFFF
****************************** BOTTOM OF DATA *********************************
Use the cursor point-and-shoot feature and press Enter at any extent starting address to display the Memory Display screen, as shown in the following figure.
Memory Display Screen, Page
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 00140000 Comment:
00140000 area PVT sp 251 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
00140000 +00000000 5CC4C6C8 D1C3D640 40801400 20F0F4F1 **DFHJCO " . 041*
00140010 +00000010 F0C90814 0917E4D8 F0F9F2F7 F8401400 *0I UQ09278 .*
00140020 +00000020 58D0021C 58D0D0D0 58D0D014 58D0D008 * } }}} }} }} *
00140030 +00000030 58C0D04C 50E0C034 58E0C010 90FDE010 * {}<&\{ \{ \ *
00140040 +00000040 D203E00C C0340DB0 4120B388 48020004 *K \ { h . *
00140050 +00000050 58FC01A4 0DEF41F0 06B841E1 00801B00 * u 0 .." .*
00140060 +00000060 1B110EE0 5810C010 0DB041A0 BFFE4130 * \ { *
00140070 +00000070 AFFE1891 5870C0D4 58807028 41100232 * j {M " *
00140080 +00000080 18F14100 937041E0 37020E0E 5810D08C * 1 .l \ } *
00140090 +00000090 D2019374 80589501 80024780 B040D207 *K l " n " " K *
001400A0 +000000A0 93823572 D201938A 93744100 95045000 *lb K l l .n &.*
001400B0 +000000B0 939C4100 938C5000 93A84100 93CC5000 *l .l &.ly .l &.*
001400C0 +000000C0 91944100 94345000 91984100 949C5000 *jm .m &.jq .m &.*
001400D0 +000000D0 919C9280 91A09280 91949280 91989280 *j k"j k"jmk"jqk"*
001400E0 +000000E0 919C9200 700B9140 70094710 B0A89120 *j k. j yj *
001400F0 +000000F0 80184710 B0C49110 80194710 33AC9118 *" Dj " j *
Note the line of data below the Start Addr: field in the header. Whatever address is displayed in the Start Addr: field initially is echoed as well as matches the first line under the Address column. If you subsequently enter +32, -210, and so on, the address on this line is updated to reflect the offset specified following the plus/minus sign (+/-). The bytes remaining value is also updated, but in the direction opposite the plus/minus sign. For example, if you enter +23, the following lines are displayed. The address in this line now echoes the first line under the Address column, but the Start Addr: remains the same as it always has, as shown in the following figure
Memory Display Screen
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 00140000 Comment:
00140023 area PVT sp 251 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
00140023 +00000023 1C58D0D0 D058D0D0 1458D0D0 0858C0D0 * }}} }} }} {}*
00140033 +00000033 4C50E0C0 3458E0C0 1090FDE0 10D203E0 *<&\{ \{ \ K \*
00140043 +00000043 0CC0340D B04120B3 88480200 0458FC01 * { h . *
00140053 +00000053 A40DEF41 F006B841 E100801B 001B110E *u 0 .." . *
00140063 +00000063 E05810C0 100DB041 A0BFFE41 30AFFE18 *\ { *
00140073 +00000073 915870C0 D4588070 28411002 3218F141 *j {M " 1 *
00140083 +00000083 00937041 E037020E 0E5810D0 8CD20193 *.l \ } K l*
00140093 +00000093 74805895 01800247 80B040D2 07938235 * " n " " K lb *
001400A3 +000000A3 72D20193 8A937441 00950450 00939C41 * K l l .n &.l *
001400B3 +000000B3 00938C50 0093A841 0093CC50 00919441 *.l &.ly .l &.jm *
001400C3 +000000C3 00943450 00919841 00949C50 00919C92 *.m &.jq .m &.j k*
001400D3 +000000D3 8091A092 80919492 80919892 80919C92 *"j k"jmk"jqk"j k*
001400E3 +000000E3 00700B91 40700947 10B0A891 20801847 *. j yj " *
001400F3 +000000F3 10B0C491 10801947 1033AC91 18801A47 * Dj " j " *
00140103 +00000103 E033AC91 09700947 10B0C447 F033AC95 *\ j D 0 n*
00140113 +00000113 49700947 7033A491 18801A47 E033A491 * uj " \ uj*
If the offset goes past the bytes remaining in the allocation or before the start of the allocation, the subpool/key is updated. For example, if you enter +7FFF0, the following line is displayed, as shown in the following figure.
Memory Display Screen
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 00140000 Comment:
001C0013 area PVT sp 252 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
001C0013 +00080013 0458F0F0 D058F0F0 1458F0F0 0C58FF00 * 00} 00 00 .*
001C0023 +00080023 0C07FF00 00000000 000000C9 C7E9C3D7 * ........IGZCP*
001C0033 +00080033 C3C34042 00C3F2F4 4BF0F0F1 61F0F661 *CC .C24.001/06/*
001C0043 +00080043 F9F340F2 F24BF0F9 404040D5 00000000 *93 22.09 N....*
001C0053 +00080053 00801C4D 08801C48 F0801C47 08801C45 *." ( " 0" " *
001C0063 +00080063 20000000 00000000 00000000 00801C82 * ............" b*
001C0073 +00080073 58801C50 C0801C0D D8000000 00801C85 * " &{" Q...." e*
001C0083 +00080083 38801C34 28000000 00801C40 A8801C21 * " ...." y" *
001C0093 +00080093 F8000000 00000000 00000000 00000000 *8...............*
001C00A3 +000800A3 00000000 00000000 00801C7A 28801C79 *........." : " `*
001C00B3 +000800B3 48801C65 40801C11 08000000 00801C81 * " " ...." a*
001C00C3 +000800C3 60801C59 C0801C55 10801C54 B0000000 *-" {" " ...*
001C00D3 +000800D3 00000000 00000000 00000000 00801C01 *............." *
001C00E3 +000800E3 48000000 00801C7C 78000000 00000000 * ...." @ .......*
001C00F3 +000800F3 00801C4F 78FFFFFF FFFFFFFF FFFFFFFF *." | *
001C0103 +00080103 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF * *
If the new address traverses a VSM area, the area is updated. Enter the PVTSUM fast-path command to display the Private Area Summary screen, as shown in the following figure.
Private Area Summary Screen
COMMAND ===>
LDA Address................ 7FF15EB0
Region Size (Kbytes)....... 8,192
To view the local system queue area select LSQA
To view a list of allocated subpools select List
Extended Private Area Private Area
Maximum Address............ 7FFFFFFF Maximum Address............ 008FFFFF
User Region Limit Address.. 7FFFFFFF User Region Limit Address.. 008FFFFF
Low MVS Page Address....... 7F68C000 Low MVS Page Address....... 00899000
High User Region Address... 122FFFFF High User Region Address... 00814FFF
Starting Address........... 10300000 Starting Address........... 00005000
Maximum Size (Kbytes)...... 1,831,936 Maximum Size (Kbytes)...... 9,196
Limit Size (Kbytes)........ 32,768 Limit Size (Kbytes)........ 8,256
Adjusted Size (Kbytes)..... 32,768 Adjusted Size (Kbytes)..... 8,192
Free Blocks Available...... Yes Free Blocks Available...... Yes
SM Block Address........... 7F80C000
SM Block Size (Kbytes)..... 7,932
Note that the extended private area started at 10300000. Use the cursor point-and-shoot feature and press Enter at this address to display the Memory Display screen, as shown in the following figure.
Memory Display Screen, page 1
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 10300000 Comment:
10300000 area EPVT sp 252 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
10300000 +00000000 00486ED4 D6C4C8C5 C1C403D7 00F4F1F0 *. >MODHEAD P.410*
10300010 +00000010 C4C6C8D2 C5C4C3D3 F1F061F1 F161F9F6 *DFHKEDCL10/11/96*
10300020 +00000020 7CF1F44B F4F40001 00000000 E4D5F9F6 *@14.44. ....UN96*
10300030 +00000030 F4F7F640 FFFFFFFF 00000001 00000400 *476 ... .. .*
10300040 +00000040 00008000 00000008 07000700 07000700 *..".... . . . .*
10300050 +00000050 07000700 07000700 07000700 07000700 * . . . . . . . .*
10300060 +00000060 07000700 07000700 07000700 07000700 * . . . . . . . .*
10300070 +00000070 07000700 07000700 07000700 07000700 * . . . . . . . .*
10300080 +00000080 90EDD00C 183D18E0 98453050 88E00006 * } \q &h\. *
10300090 +00000090 182089E0 00088920 0002416E 52085892 * i\. i . > k*
103000A0 +000000A0 523058A0 40305820 904058D0 A0605800 * } - .*
103000B0 +000000B0 6010418D 20005980 402C4720 F0FE50D0 *- . " 0 &}*
103000C0 +000000C0 40301F77 91805100 4780F070 9108403C * j" . "0 j *
103000D0 +000000D0 4710F070 9120403C 4780F064 58706018 * 0 j "0 - *
103000E0 +000000E0 47F0F070 91405100 4780F070 58706014 * 00 j . "0 - *
103000F0 +000000F0 9023D000 904AD050 50D04018 91025055 * }. ¢}&&} j & *
Enter -1 at the command line to display the screen with the VSM area updated to ECSA, as shown in the following figure.
Memory Display Screen, page 2
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 10300000 Comment:
102FFFFF area ECSA sp 241 key 0 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
102FFFFF -00000001 0000486E D4D6C4C8 C5C1C403 D700F4F1 *.. >MODHEAD P.41*
1030000F +0000000F F0C4C6C8 D2C5C4C3 D3F1F061 F1F161F9 *0DFHKEDCL10/11/9*
1030001F +0000001F F67CF1F4 4BF4F400 01000000 00E4D5F9 *6@14.44. ....UN9*
1030002F +0000002F F6F4F7F6 40FFFFFF FF000000 01000004 *6476 ... .. *
1030003F +0000003F 00000080 00000000 08070007 00070007 *...".... . . . *
1030004F +0000004F 00070007 00070007 00070007 00070007 *. . . . . . . . *
1030005F +0000005F 00070007 00070007 00070007 00070007 *. . . . . . . . *
1030006F +0000006F 00070007 00070007 00070007 00070007 *. . . . . . . . *
1030007F +0000007F 0090EDD0 0C183D18 E0984530 5088E000 *. } \q &h\.*
1030008F +0000008F 06182089 E0000889 20000241 6E520858 * i\. i . > *
1030009F +0000009F 92523058 A0403058 20904058 D0A06058 *k } - *
103000AF +000000AF 00601041 8D200059 80402C47 20F0FE50 *.- . " 0 &*
103000BF +000000BF D040301F 77918051 004780F0 70910840 *} j" . "0 j *
103000CF +000000CF 3C4710F0 70912040 3C4780F0 64587060 * 0 j "0 -*
103000DF +000000DF 1847F0F0 70914051 004780F0 70587060 * 00 j . "0 -*
103000EF +000000EF 149023D0 00904AD0 5050D040 18910250 * }. ¢}&&} j &*
For an address in the LPA or Nucleus, a module name is displayed. Also note that if the address is not found in the SVC dump data set, the text “is not found in the SDUMP data set” is displayed instead of the text “is not allocated storage” because you can now determine if the storage is logically not allocated versus physically not dumped. The new line represents the logical allocation, while the line below the column heading now represents the physical status, as shown in the following figure.
Memory Display Screen, page 3
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 04E2C3C8 Comment:
04E2C3C8 area EPLPA sp 251 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
04E2C3C8 :065CEFF is not found in the SDUMP dataset
065CF000 +017A2C38 05F047F0 F01C16C9 C5C6C4C2 F4F0F040 * 0 00 IEFDB400 *
065CF010 +017A2C48 F0F0F0F2 F740E4E6 F6F7F1F2 F60005C0 *00027 UW67126. {*
065CF020 +017A2C58 4130CFFF 185F18A1 186041F0 00E65800 * ¬ ~ - 0.W .*
065CF030 +017A2C68 3D75B20B 0000B20A 00105800 3D7147F0 * .. . . 0*
065CF040 +017A2C78 C0280700 00FFFFFF 41100001 131141F0 *{ .. . 0*
065CF050 +017A2C88 0FA018E0 54E0C024 19EF4720 C058181D * \ \{ { *
065CF060 +017A2C98 58F0C050 070005EF 47F0C068 47F0C05C * 0{& . 0{ 0{**
065CF070 +017A2CA8 065D1244 065D1262 41E00000 0A0A120E * ) ) \.. *
065CF080 +017A2CB8 58F0C054 4770C046 18B1181A 180650D0 * 0{ { &}*
065CF090 +017A2CC8 B0044220 BE4218F5 18DB5040 B0EC58A0 * 5 & *
065CF0A0 +017A2CD8 40005860 A0245070 B0AC181A 1FAABFA7 * . - & x*
065CF0B0 +017A2CE8 101D181A D200B430 10111F00 4300B430 * K. . . *
065CF0C0 +017A2CF8 1F224320 3C001402 4200B430 91801014 * . . j" *
065CF0D0 +017A2D08 47E0C0BC 9680B3D0 47F0C0C0 947FB3D0 * \{ o" } 0{{m" }*
065CF0E0 +017A2D18 9180B3D0 4770C0CC 54603BBD 50D0B0D4 *j" } { - &} M*
If an address lies between allocations, the text not allocated is displayed and the bytes remaining reflects the number of bytes before the next allocation, as shown in the following figure.
Memory Display Screen, page 4
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 04E2C3C8 Comment:
04E2C3C7 area EPLPA sp 251 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
04E2C3C7 :065CEFF is not found in the SDUMP dataset
065CF000 +017A2C38 05F047F0 F01C16C9 C5C6C4C2 F4F0F040 * 0 00 IEFDB400 *
065CF010 +017A2C48 F0F0F0F2 F740E4E6 F6F7F1F2 F60005C0 *00027 UW67126. {*
065CF020 +017A2C58 4130CFFF 185F18A1 186041F0 00E65800 * ¬ ~ - 0.W .*
065CF030 +017A2C68 3D75B20B 0000B20A 00105800 3D7147F0 * .. . . 0*
065CF040 +017A2C78 C0280700 00FFFFFF 41100001 131141F0 *{ .. . 0*
065CF050 +017A2C88 0FA018E0 54E0C024 19EF4720 C058181D * \ \{ { *
065CF060 +017A2C98 58F0C050 070005EF 47F0C068 47F0C05C * 0{& . 0{ 0{**
065CF070 +017A2CA8 065D1244 065D1262 41E00000 0A0A120E * ) ) \.. *
065CF080 +017A2CB8 58F0C054 4770C046 18B1181A 180650D0 * 0{ { &}*
065CF090 +017A2CC8 B0044220 BE4218F5 18DB5040 B0EC58A0 * 5 & *
065CF0A0 +017A2CD8 40005860 A0245070 B0AC181A 1FAABFA7 * . - & x*
065CF0B0 +017A2CE8 101D181A D200B430 10111F00 4300B430 * K. . . *
065CF0C0 +017A2CF8 1F224320 3C001402 4200B430 91801014 * . . j" *
065CF0D0 +017A2D08 47E0C0BC 9680B3D0 47F0C0C0 947FB3D0 * \{ o" } 0{{m" }*
065CF0E0 +017A2D18 9180B3D0 4770C0CC 54603BBD 50D0B0D4 *j" } { - &} M*
Common Storage Analysis
Like the private areas, the common storage areas -- common service area (CSA) and system queue area (SQA) -- can also be over-allocated. The anchor block used by VSM for the CSA and SQA is the global data area (GDA). The CSA contains data addressable by all active virtual storage address spaces. The size of the CSA is directly specified. The SQA is like the LSQA except on a global basis. It contains tables and queues relating to the entire system, but unlike the LSQA, its size is directly specified. If the SQA becomes 100 percent allocated, pages are borrowed or converted from CSA storage. Such pages are flagged with > for SQA pages converted from CSA, and with < for ESQA pages converted from ECSA. See the discussion of the Allocated Storage Map in Allocated Storage Map for information on how to locate these converted pages. Since a shortage of SQA causes borrowing of CSA, you may also experience a CSA shortage.
The S878 and S80A abend codes also pertain to CSA and SQA, but are indicated using different reason codes. Requests for VSM services that fail due to a common storage shortage are indicated by an SC78 abend code. Ownership of common storage is at the address space level, as opposed to the task (TCB) level for private storage. Identifying ownership requires that common storage tracking be active. The VSM TRACK parameter in the DIAGxx member of SYS1.PARMLIB is used to control common storage tracking.
The SVC dump used in this example was reported as a CSA storage creep; that is, CSA storage was being GETMAINed without being FREEMAINed. The best place to start is the Virtual Storage Map, which you can access from the MVS Storage Analysis menu or by entering the VSMAP fast-path command from any command line, once you have selected the dump, as shown in the following figure. Enter the BOTTOM primary command, or type MAX and press the Down (PF8) key to display the data for the CSA that is below the 16 Mb boundary.
Virtual Storage Map Screen
COMMAND ===> SCROLL ===> DATA
The Ext User Region had not reached the highest allocatable address.
The Ext CSA had pages converted to Ext SQA.
The CSA had pages converted to SQA.
The User Region had not reached the highest allocatable address.
Starting Ending Size of Total Percent
Storage Area Address Address Area Allocated Allocated
**************** ******** ******** ********** ********** ***********
Ext CSA 05597000 0B7FFFFF 100,772K 79,584K 78.974
Ext MLPA 05497000 05596FFF 1,024K
Ext FLPA 05494000 05496FFF 12K
Ext PLPA 02988000 05493FFF 44,080K
Ext SQA 019E4000 02987FFF 16,016K 19,392K 121.079
Ext Nuc (R/W) 0151F000 019E3FFF 4,884K
Ext Nuc (R/O) 01000000 0151EFFF 5,244K
- 16Mb Line ---- -------- -------- ---------- ---------- -----------
Nucleus (R/O) 00FDB000 00FFFFFF 148K
Nucleus (R/W) 00FC8000 00FDAFFF 76K
SQA 00E98000 00FC7FFF 1,216K 1,980K 162.829
PLPA 00C6C000 00E97FFF 2,224K
FLPA 00C69000 00C6BFFF 12K
In the header on the Virtual Storage Map, note that both the extended CSA and CSA had pages converted to extended SQA and SQA. From the scrollable area, the extended SQA is at 121.079 percent, and the SQA is at 162.829 percent allocated. Because CSA pages are converted to SQA when required, the percentages of E/SQA can be greater than 100 percent. You need to add these converted pages to the total allocated for extended CSA and CSA to determine the true amounts of extended CSA and CSA allocated.
To determine the number of converted CSA pages, use the cursor point-and-shoot feature and press Enter at either the Ext SQA or SQA field under the Storage Area column, or enter the SQASUM fast-path command on any command line to display the SQA Summary screen, as shown in the following figure.
SQA Summary Screen
Row 000001 of 000005
COMMAND ===> SCROLL ===> DATA
GDA Address................ 021E41A0
SM Block Address........... 021E4000
SM Block Size (Kbytes)..... 40
SQA Tracking Status........ Active
To view a summary of SQA subpools select Summarize
Extended System Queue Area System Queue Area
Maximum Address (defined).. 02987FFF Maximum Address (defined).. 00FC7FFF
Defined Size (Kbytes)...... 16,016 Defined Size (Kbytes)...... 1,216
Starting Address........... 019E4000 Starting Address........... 00E98000
ECSA to ESQA (Kbytes)...... 4,120 CSA to SQA (Kbytes)........ 764
AQATINDX +---------- DFE Queue Origins -----------+
Sp Address Addr <16M Addr >16M Size <16M Size >16M
*** ******** ******************************************
226 021E73B0 021EAF44 -------- 021EAF44 --------
239 021E6FB0 021EAA94 021EACEC 021EAA94 021EACEC
245 021E6BB0 021EA5E4 021EA83C 021EA5E4 021EA83C
247 021E77B0 -------- 021EB19C -------- 021EB19C
248 021E7BB0 -------- 021EB3F4 -------- 021EB3F4
In the header on the SQA Summary screen, note the amounts of ECSA converted to ESQA and CSA converted to SQA. These may or may not equal the difference between the allocated amounts and sizes of the SQA areas. The amount of extended CSA converted to extended SQA is 4,120K, and the amount of CSA converted to SQA is 764K. Adding 4,120K to the 79,584K allocated to extended CSA gives 83,704K. Dividing that by the size of the extended CSA at 100,772K reveals the extended CSA is 83.063 percent allocated. Adding 764K to the 3,668K allocated to CSA gives 4,432K or 100 percent of the CSA is allocated. What appeared to be a CSA shortage had actually been caused by the borrowing of CSA pages for SQA. Had a true CSA shortage occurred, the amounts of converted CSA would be none at all. The following sections describe ways to determine the SQA allocators and allocations.
Common Storage Users
The address of the global data area (GDA) is displayed in the header on the SQA Summary screen. This area is the VSM anchor block that contains information on system-related virtual storage -- in particular, the SQA and CSA subpools. The SQA tracking status is listed as either Active or Inactive at the time the SVC dump was taken. If Active, a list of address spaces that had allocated SQA is available. Use the cursor point-and-shoot feature and press Enter at the Active field to display the Common Storage Users screen, as shown in the following figure. You can also use the Common Storage Users screen for a CSA shortage, providing CSA tracking is active. You can also access the Common Storage Users screen from the Common Service Area Summary screen.
Common Storage Users Screen
COMMAND ===> SCROLL ===> DATA
==>
Total CSA Total SQA Total ESQA Total ECSA
System 18,312 789,056 13,176,976 3,302,432
Active 3,027,288 621,960 5,030,624 72,545,872
Owner Gone 372,400 439,856 509,136 4,399,848
------------------ ------------ ------------ ------------ ------------
Totals from CAUBs 3,418,000 1,850,872 18,716,736 80,248,152
Totals from GDA 3,418,000 1,850,872 18,716,736 80,248,152
Differences 0 0 0 0
ASID Name Id Status Total CSA Total ECSA Status Total SQA Tot
**** ******** ******** ****** ********** ********** ****** ********** ***
0000 *SYSTEM* 18,312 3,302,432 789,056 13,
0000 *UNKNOW* 0 0 0
0001 *MASTER* 127,784 2,200,552 193,104 2,
0002 PCAUTH 0 0 80
0003 RASP 0 0 0
0004 TRACE 0 0 0
0005 DMSAR STC03675 0 336 0
0005 DUMPSRV 0 144 0
0006 XCFAS 0 2,184 160
0007 GRS 0 0 936
In the header, note the summary of the amounts of allocated common storage found in the common area user blocks (CAUBs). It lists amounts for system-owned, for active CAUBs found, and for owner-gone (terminated address space) CAUBs found. The Differences data are the difference between the amounts from the CAUBs and the amounts from fields found in the GDA. The CAUB cell pool address is the first cell (block) of storage that contains the CAUBs, of which there are five types.
- The system CAUB describes storage owned by the system, which occurs when it would not be possible or would be misleading to assign ownership to the job running in the home address space. Also, when some operating system components GETMAIN storage, they explicitly indicate that ownership should be assigned to the system.
- An address space CAUB describes storage obtained by an initiator address space during the time it is between jobs.
- A job CAUB describes storage obtained when the address space in which the job is running is the home address space. These can be further classified as active or gone.
- An owner gone CAUB describes storage obtained without being freed before the address space terminated. These are linked together on the "unowned" queue and can futher be classified as job or address space.
- The no detail CAUB describes storage that was in use when CSA tracking was being either turned on or off.
Address spaces that allocated CSA and/or SQA are listed in the scrollable area of the screen. By default the screen is sorted by ASID. Any given ASID can appear more than once because ASCBs are reused when address spaces initialize and terminate. The job or started task name from the ASCB is listed, as is the job ID from the JSAB. The job ID is null for entities started under the master scheduler subsystem. The amounts of E/CSA and E/SQA (total) are listed, which you can sort to find address spaces allocating the most of each area. The date (0YYYYDDD) and time (HHMMSSth) of termination are listed for address spaces that terminated without freeing their common storage allocations. You can use the job ID, date/time of termination, along with a system log to determine the reason for termination.
Because the CSA had been 100 percent allocated, the primary concern is SQA and then extended SQA. To locate the address space allocating the most SQA, sort on the Total SQA column heading by entering the SORT primary command or typing SORT on the command line and pressing Enter at the Total SQA column heading. Because the sort order is low to high, enter the BOTTOM primary command, or type MAX on the command line and press the DOWN (PF8) key to scroll down to the bottom to see the address spaces using the most SQA, as shown in the following figure.
Common Storage Users, Sorted by Total SQA
COMMAND ===> SCROLL ===> DATA
==>
Total CSA Total SQA Total ESQA Total ECSA
System 18,312 789,056 13,176,976 3,302,432
Active 3,027,288 621,960 5,030,624 72,545,872
Owner Gone 372,400 439,856 509,136 4,399,848
------------------ ------------ ------------ ------------ ------------
Totals from CAUBs 3,418,000 1,850,872 18,716,736 80,248,152
Totals from GDA 3,418,000 1,850,872 18,716,736 80,248,152
Differences 0 0 0 0
ASID Name Id Status Total CSA Total ECSA Status Total SQA Tot
**** ******** ******** ****** ********** ********** ****** ********** ***
00B7 PDSM00 STC00413 368 123,072 15,424
00A3 NETVIEW STC00312 5,408 132,384 20,824
00C1 CA7ONL STC01094 6,736 3,216 25,856
00A6 OMIIETE STC00318 72 12,352 29,552
0090 MIMSDSI STC00214 5,568 10,208 55,016
0001 *MASTER* 127,784 2,200,552 193,104 2,
0122 NPM STC02207 50,856 669,728 213,056
00AE FXC01 STC00366 0 0 291,088
0000 *SYSTEM* 18,312 3,302,432 789,056 13,
****************************** BOTTOM OF DATA *********************************
As expected, *SYSTEM* and *MASTER* own most of the storage allocated to the SQA. However, there are two other address spaces with large amounts of SQA allocated. FXC01, which is no longer active, looks suspicious (Abend-AID?), as does NPM, which is still active. Use the cursor-point-and-shoot feature and press Enter at the ASID field for FXC01 to display the Common Storage Allocations screen, as shown in the following figure.
Common Storage Allocations Screen
COMMAND ===> SCROLL ===> DATA
==>
Total CSA Total SQA Total ESQA Total ECSA
Totals from GQEs 0 291,088 7,616 0
Totals from CAUB 0 291,088 7,616 0
Differences 0 0 0 0
CAUB Address................. 0268B3B8
Name of Address Space........ FXC01
Status of Address Space...... Gone
Address Size Area Return GQE Date Time First 32
******** ********** **** ******** ******** ********* ********* *********
00EB3000 4,096 SQA 80F4B344 06B5A2C8 31JAN2002 07:48:57 . . 1 8
00EAF000 4,096 SQA 80F4B344 06B5A340 31JAN2002 07:45:02 . {. ! 8
00835000 4,096 SQA 80F4B344 0831BCA0 31JAN2002 08:10:28 . . 8 8
00EB6000 4,096 SQA 80F4B344 01ABF148 31JAN2002 07:52:39 .6}. ! 8
00F6D000 4,096 SQA 80F4B344 01ABFAC0 31JAN2002 07:51:23 . . ! 8
008D1000 4,096 SQA 80F4B344 01AA1B50 31JAN2002 08:09:13 . . ! 8
00EBC000 4,096 SQA 80F4B344 01AA1F88 31JAN2002 07:43:47 . . ! 8
00EA9000 4,096 SQA 80F4B344 0672F478 31JAN2002 07:47:33 .7 . ! 8
00907000 4,096 SQA 80F4B344 0672FC28 31JAN2002 08:07:57 .j . 8
00801000 4,096 SQA 80F4B344 07EE9118 31JAN2002 08:12:54 . &. 8
00EA6000 4,096 SQA 80F4B344 07EE98C8 31JAN2002 07:53:54 . -. ! 8
The Common Storage Allocations screen displays the individual allocations of E/CSA and E/SQA by the selected address space. This screen is not initially sorted, but can be sorted by address, size, return address, date or time. The header contains information carried over from the Common Storage Users screen, but adds totals for E/CSA and E/SQA found in the GQEs. Use the RIGHT (PF11) key to display the right-most portion of the screen and the first 32 bytes of data, as shown in the following figure.
Common Storage Allocations Screen
COMMAND ===> SCROLL ===> DATA
<==
Total CSA Total SQA Total ESQA Total ECSA
Totals from GQEs 0 291,088 7,616 0
Totals from CAUB 0 291,088 7,616 0
Differences 0 0 0 0
CAUB Address................. 0268B3B8
Name of Address Space........ FXC01
Status of Address Space...... Gone
Address Size Area Date Time First 32 Bytes of Data
******** ********** **** ****** ********* ********************************
00EB3000 4,096 SQA AN2003 07:48:57 . . 1 8 ... .MFDCATLGSYSV.CICS
00EAF000 4,096 SQA AN2003 07:45:02 . {. ! 8 ... .MFDCATLGSYSV.CICS
00835000 4,096 SQA AN2003 08:10:28 . . 8 8 ... .MFDCATLGSYSV.CICS
00EB6000 4,096 SQA AN2003 07:52:39 .6}. ! 8 ... .MFDCATLGSYSV.CICS
00F6D000 4,096 SQA AN2003 07:51:23 . . ! 8 ... .MFDCATLGSYSV.CICS
008D1000 4,096 SQA AN2003 08:09:13 . . ! 8 ... .MFDCATLGSYSV.CICS
00EBC000 4,096 SQA AN2003 07:43:47 . . ! 8 ... .MFDCATLGSYSV.CICS
00EA9000 4,096 SQA AN2003 07:47:33 .7 . ! 8 ... .MFDCATLGSYSV.CICS
00907000 4,096 SQA AN2003 08:07:57 .j . 8 ... .MFDCATLGSYSV.CICS
00801000 4,096 SQA AN2003 08:12:54 . &. 8 ... .MFDCATLGSYSV.CICS
00EA6000 4,096 SQA AN2003 07:53:54 . -. ! 8 ... .MFDCATLGSYSV.CICS
The first 32 bytes of data column reveals many occurrences of an Abend-AID shared directory name. The resolution is discussed in the next section, SQA Analysis. If SQA tracking had been inactive, you would need to follow the steps described in that section to determine the problem. That approach is more difficult to determine the offending address space.
Continue by pressing the END (PF3) key to return to the Common Storage Users screen. The amount allocated by address spaces that terminated is generally of concern unless it was intentionally left allocated for other address spaces. To find the address spaces that terminated, press the RIGHT (PF11) key to display the right-most portion of the Common Storage Users screen and enter gone in the masking line under the CAUB Type column heading. Enter the SORT primary command, or type SORT on the command line and press Enter at the TOTAL ESQA column heading. Next, enter the BOTTOM primary command, or type MAX on the command line and press the DOWN (PF8) key to scroll down to the bottom to display the terminated address spaces leaving the largest amount of ESQA as shown in the following figure.
Common Storage Users Screen, Sorted by Total ESQA
COMMAND ===> SCROLL ===> DATA
<==
Total CSA Total SQA Total ESQA Total ECSA
System 18,312 789,056 13,176,976 3,302,432
Active 3,027,288 621,960 5,030,624 72,545,872
Owner Gone 372,400 439,856 509,136 4,399,848
------------------ ------------ ------------ ------------ ------------
Totals from CAUBs 3,418,000 1,850,872 18,716,736 80,248,152
Totals from GDA 3,418,000 1,850,872 18,716,736 80,248,152
Differences 0 0 0 0
ASID To Status Total SQA Total ESQA CAUB CAUB Type Date Time
**** ** ****** ********** ********** ******** GONE****** ******** ********
00AE 0 291,088 7,616 0268B3B8 Gone.. A/S 02003031 04273548
0018 64 3,328 8,160 02492718 Gone.. A/S 02003031 03574058
0055 0 0 8,192 02492D90 Gone.. Job 02003025 05582000
0022 0 0 8,448 02506DD8 Gone.. Job 02003025 04472457
00B8 0 560 14,184 0268B718 Gone.. A/S 02003028 17504867
0057 0 10,280 15,320 0268BB50 Gone.. A/S 02003031 04140523
0090 08 55,016 18,744 0274C958 Gone.. A/S 02003026 01141117
00B0 0 1,296 35,568 0268B490 Gone.. A/S 02003025 01434366
00A6 52 29,552 220,784 0268B130 Gone.. A/S 02003031 04140295 ****************************** BOTTOM OF DATA *********************************
Sort the display by total SQA by entering the SORT primary command or typing SORT on the command line and pressing Enter at the Total SQA column heading. Enter the BOTTOM primary command, or type MAX on the command line and press the DOWN (PF8) key to display the terminated address spaces leaving the largest amount of SQA, as shown in the following figure.
Common Storage Users Screen, Sorted by Total SQA
COMMAND ===> SCROLL ===> DATA
<==
Total CSA Total SQA Total ESQA Total ECSA
System 18,312 789,056 13,176,976 3,302,432
Active 3,027,288 621,960 5,030,624 72,545,872
Owner Gone 372,400 439,856 509,136 4,399,848
------------------ ------------ ------------ ------------ ------------
Totals from CAUBs 3,418,000 1,850,872 18,716,736 80,248,152
Totals from GDA 3,418,000 1,850,872 18,716,736 80,248,152
Differences 0 0 0 0
ASID To Status Total SQA Total ESQA CAUB CAUB Type Date Time
**** ** ****** ********** ********** ******** GONE****** ******** ********
015F 0 4,096 0 084AF058 Gone.. Job 02002026 00385916
0050 0 4,096 8 086078C8 Gone.. A/S 02002031 04140550
0166 0 4,096 328 084AF5B0 Gone.. Job 02002026 01143073
0069 0 4,096 0 085CF0E8 Gone.. Job 02002026 01572168
0057 0 10,280 15,320 0268BB50 Gone.. A/S 02002031 04140523
007D 0 10,544 752 0268B298 Gone.. A/S 02002031 04140522
00A6 52 29,552 220,784 0268B130 Gone.. A/S 02002031 04140295
0090 08 55,016 18,744 0274C958 Gone.. A/S 02003026 01141117
00AE 0 291,088 7,616 0268B3B8 Gone.. A/S 02003031 04273548 ****************************** BOTTOM OF DATA *********************************
SQA Analysis
If SQA tracking was not active, you need to examine the SQA allocations by subpool. Press the END (PF3) key to return to the SQA Summary screen. Use the cursor point-and-shoot feature and press Enter at the Summarize field in the header to display the Summarized SQA Subpools screen, as shown in the following figure. The percentages are calculated on the total amount allocated for SQA, ESQA, and SQA+ESQA. They are not calculated on the amounts defined to these areas.
Summarized SQA Subpools Screen
COMMAND ===> SCROLL ===> DATA
SQA Size (Kbytes)........................... 1,216
Extended SQA Size (Kbytes).................. 16,016
Total SQA Allocated (Kbytes)................ 1,980
Total Extended SQA Allocated (Kbytes)....... 19,392
Allocated Percent of Allocated Percent of Total Percent of
Id <16Mb Total <16Mb >16Mb Total >16Mb Allocated <16M + >16M
*** ********** *********** ********** *********** ********** ***********
245 1,540K 77.778 12,568K 64.810 14,108K 66.012
226 244K 12.323 0K 0.000 244K 1.142
239 196K 9.899 3,508K 18.090 3,704K 17.331
247 0K 0.000 436K 2.248 436K 2.040
248 0K 0.000 2,880K 14.851 2,880K 13.476
****************************** BOTTOM OF DATA *********************************
Use this screen to narrow down which subpools in SQA have large allocations. This screen shows that subpool 245 is 77.778 percent of total SQA allocated. It would also help to know what are the normal allocations for each SQA subpool. Use the cursor point-and-shoot feature and press Enter at any of the subpool numbers under the Id column heading to display the SQA Subpool Detail screen, as shown in the following figure. You can also display this screen from the SQA Summary screen.
SQA Subpool Detail Screen
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 245 Allocated <16Mb (Kbytes).... 1,540
AQATINDX Address............ 021E6BB0 Allocated >16Mb (Kbytes).... 12,568
Non-zero AQATINDX Entries... 17 Total Allocated (Kbytes).... 14,108
Free <16Mb................. 155,168
Free >16Mb................. 1,018,648
Total Free................. 1,173,816
Page CSA DFE Size of DFE AQAT AQAT Index
Address Page Address DFE Area Area Count Address Entry Entry
******** ***** ******** ******** ********* ****** ******** ****** *****
00801000 Yes 0 021E84A8 0
00826000 Yes 07FC9AF0 00826000 3,072 1 021E84A8 2
00827000 Yes 0 021E84A8 2
00828000 Yes 0 021E84A8 2
00829000 Yes 0 021E84A8 2
0082A000 Yes 07FC9448 0082A000 3,072 1 021E84A8 2
0082B000 Yes 0 021E84A8 2
0082C000 Yes 0 021E84A8 2
0082D000 Yes 0 021E84A8 2
00832000 Yes 08429EB0 00832000 128 4 021E84A8 3
00835000 Yes 0 021E84A8 3
This screen has the same format as the LSQA Subpool Detail screen shown in the following figure. Another field is added for SQA, the CSA Page indicator. If the page is a converted CSA page, Yes is displayed in this column. Also, it may take longer to display because of the considerably more pages (entries). For this reason, only the first DFE (free area) of each page is displayed. To see additional free areas, use the cursor point-and-shoot feature and press Enter at the DFE Count field to display the DFEs for Specific Pages screen, as shown in the following figure.
DFEs for Specific Pages Screen
COMMAND ===> SCROLL ===> DATA
Subpool.................. 245 Total Free.................. 2,648
Subpool Location......... SQA <16M Page Address................ 00832000
DFE Size of Data
Address DFE Area Area Address First 32 Bytes of Data
******** ******** ********* ******** ********************************
08429EB0 00832000 128 00832080 ASCB. ". C......"7 .. "........
09A45DA8 00832400 80 00832450 . .....................: -....
07686358 008324F8 2,056 00832D00 ASCB.6m". "....."9.. Q ........
01D47748 00832E80 384 00833000 << REACHED END OF PAGE >>
****************************** BOTTOM OF DATA *********************************
This screen is also the same as for LSQA except that the Subpool Location field reflects SQA. This screen displays the page and all its free areas.
Press the END (PF3) key to return to the SQA Subpool Detail screen. Scroll down using the DOWN (PF8) key, and press the RIGHT (PF11) key to display the right-most portion of the screen. Note the many pages with MFDCATLGSYSV.CICS in the First 32 Bytes of Data column. Entering MFDCATLG in the mask line in the same column positions for First 32 Bytes of Data reveals there are 71 such pages in subpool 245, as shown in the following figure.
SQA Subpool Detail Screen, Masked
COMMAND ===> SCROLL ===> DATA
<==
Subpool..................... 245 Allocated <16Mb (Kbytes).... 1,540
AQATINDX Address............ 021E6BB0 Allocated >16Mb (Kbytes).... 12,568
Non-zero AQATINDX Entries... 17 Total Allocated (Kbytes).... 14,108
Free <16Mb................. 155,168
Free >16Mb................. 1,018,648
Total Free................. 1,173,816
Page CSA AQ AQAT Index Data
Address Page Ad Entry Entry Address First 32 Bytes of Data
******** ***** ** ****** ****** ******** ***************MFDCATLG*********
00801000 Yes A8 0 1 00801000 . &. 8 ... .MFDCATLGSYSV.CICS
00835000 Yes A8 3 1 00835000 . . 8 8 ... .MFDCATLGSYSV.CICS
008A9000 Yes A8 10 1 008A9000 . . ! 8 ... .MFDCATLGSYSV.CICS
008AB000 Yes A8 10 1 008AB000 . \. ! 8 ... .MFDCATLGSYSV.CICS
008AD000 Yes A8 10 1 008AD000 . . r 8 ... .MFDCATLGSYSV.CICS
008AE000 Yes A8 10 1 008AE000 . . ! 8 ... .MFDCATLGSYSV.CICS
008AF000 Yes A8 10 1 008AF000 . {. ! 8 ... .MFDCATLGSYSV.CICS
008B0000 Yes A8 11 1 008B0000 .k . ! 8 ... .MFDCATLGSYSV.CICS
008CE000 Yes A8 12 1 008CE000 . . 8 ... .MFDCATLGSYSV.CICS
008D1000 Yes A8 13 1 008D1000 . . ! 8 ... .MFDCATLGSYSV.CICS
008D2000 Yes A8 13 1 008D2000 . \. ! 8 ... .MFDCATLGSYSV.CICS
Each page has no free areas (DFEs). Press the DOWN (PF8) key once to scroll the display downward. Use the cursor point-and-shoot feature and press Enter at 008D7000 in the Data Address column to display the Memory Display screen, as shown in the following figure .
Memory Display Screen for Data Address
COMMAND ===> SCROLL ===> DATA
Clip Prev Next Lock
Start Addr: 008D7000 Comment:
008D7000 area SQA > sp 245 key 8 ASID 0053 EBCDIC
Address Offset Word 1 Word 2 Word 3 Word 4 Storage
008D7000 +00000000 0090C000 0F5A0FF8 06000000 12FE00D4 *. {. ! 8 ... .M*
008D7010 +00000010 C6C4C3C1 E3D3C7E2 E8E2E54B C3C9C3E2 *FDCATLGSYSV.CICS*
008D7020 +00000020 4BC1C1C6 E74BE2C5 D9E5C3F0 F14BE2C8 *.AAFX.SERVC01.SH*
008D7030 +00000030 D9C4C9D9 40404040 404040E2 C3C3F3F0 *RDIR SCC30*
008D7040 +00000040 F30000C4 C5E2C3D9 C9D7E3E2 C8C1D9C4 *3..DESCRIPTSHARD*
008D7050 +00000050 C4C9D9E2 C8C1D9C4 C4C9D900 00000900 *DIRSHARDDIR... .*
008D7060 +00000060 00000000 00000000 00000000 00000000 *................*
008D7070 +00000070 00000000 00000000 00000000 00000000 *................*
008D7080 +00000080 00000000 00000000 00000000 00000000 *................*
008D7090 +00000090 00000000 00000000 00000000 00000000 *................*
008D70A0 +000000A0 00000000 00000000 00000000 00000000 *................*
008D70B0 +000000B0 00000000 00000000 00000000 00000000 *................*
008D70C0 +000000C0 00000000 00000000 00000000 00000000 *................*
008D70D0 +000000D0 00000000 00000000 00000000 00000000 *................*
008D70E0 +000000E0 00000000 00000000 00000000 00000000 *................*
008D70F0 +000000F0 00000000 00000000 00000000 00000000 *................*
Once the entire page is displayed, it reveals an Abend-AID enqueue name for the shared directory. Note the SERVC01 in the name, which reflects the FXC01 address space from the Common Storage Users screen that had terminated, leaving SQA storage allocated. This is the reason the SVC dump was reported to Abend-AID Technical Support. Once it was researched at BMC, it was determined to be a known problem with a resource serialization product leaving partial enqueue data in SQA.
Enter the SQASUM fast-path command to display the SQA Summary screen, as shown in the following figure.
SQA Summary Screen
COMMAND ===> SCROLL ===> DATA
GDA Address................ 021E41A0
SM Block Address........... 021E4000
SM Block Size (Kbytes)..... 40
SQA Tracking Status........ Active
To view a summary of SQA subpools select Summarize
Extended System Queue Area System Queue Area
Maximum Address (defined).. 02987FFF Maximum Address (defined).. 00FC7FFF
Defined Size (Kbytes)...... 16,016 Defined Size (Kbytes)...... 1,216
Starting Address........... 019E4000 Starting Address........... 00E98000
ECSA to ESQA (Kbytes)...... 4,120 CSA to SQA (Kbytes)........ 764
AQATINDX +---------- DFE Queue Origins -----------+
Sp Address Addr <16M Addr >16M Size <16M Size >16M
*** ******** ******************************************
226 021E73B0 021EAF44 -------- 021EAF44 --------
239 021E6FB0 021EAA94 021EACEC 021EAA94 021EACEC
245 021E6BB0 021EA5E4 021EA83C 021EA5E4 021EA83C
247 021E77B0 -------- 021EB19C -------- 021EB19C
248 021E7BB0 -------- 021EB3F4 -------- 021EB3F4
****************************** BOTTOM OF DATA *********************************
The DFE Queue Origins for SQA subpools are available. DFEs represent available storage (free) in a 64K block of storage represented by an address queue anchor table (AQAT) address. Each AQAT contains 128 entries that consist of an array of queue headers into L/SQA DFE (by address) queues and 16 allocation bits that represent storage allocated in an L/SQA subpool. Each AQAT entry is 6 bytes long and describes 64K of storage.
The address of the AQAT is found from an entry in an AQATINDX table. Each L/SQA subpool has its own AQATINDX, addressed from either the GDA (SQA) or LDA (LSQA). Each AQATINDX has 256 entries, each representing 8M of storage.
Tab selecting the addresses of the DFE queue origins displays the list of DFEs as described in the column heading:
- Sorted by address below 16Mb boundary
- Sorted by address above 16Mb boundary
- Sorted by size below 16Mb boundary
- Sorted by size above 16Mb boundary.
Because DFEs are on 8-byte boundaries, VSM places dummy DFEs at each boundary denoted by an area (address) and size equal to zeroes. Use the cursor point-and-shoot feature and press Enter at 021EAA94 under the Size < 16M column for subpool 239 to display the DFEs in Size Queue Order screen, as shown in the following figure
DFEs in Size Queue Order Screen
COMMAND ===> SCROLL ===> DATA
Subpool.................. 239 Total Free.................. 17,936
Subpool Location......... SQA <16M
DFE Size of
Address DFE Area Area Error
******** ******** ********* ***** ********************************
021EAA94 00000000 0 This is a Dummy DFE
021EB9AC 00FA5000 8
028DE5F8 00FAC000 8
028DE430 00FB3000 8
028DE358 00F95000 8
028DE280 00FA2000 8
021EAAAC 00000000 0 This is a Dummy DFE
07D22B08 00F8ED90 16
0789C6A0 00F89D00 16
028DE568 00F7EFA0 16
021EAAC4 00000000 0 This is a Dummy DFE
01B7ECB8 00F7E000 24
021EAADC 00000000 0 This is a Dummy DFE
021EAAF4 00000000 0 This is a Dummy DFE
021EAB0C 00000000 0 This is a Dummy DFE
CSA Analysis
After selecting a region dump, enter the CSASUM fast-path command on any command line or select the CSASUM option (9) on the MVS Storage Analysis menu to display the Common Service Area Summary screen, as shown in the following figure.
Common Service Area Summary Screen
COMMAND ===>
GDA Address................ 021E41A0
SPT Address................ 028D09F8
CSA Tracking Status........ Active
To view a summary of CSA subpools select Summarize
Extended Common Service Area Common Service Area
Maximum Address............ 0B7FFFFF Maximum Address............ 00C53FFF
Maximum Size (Kbytes)...... 100,772 Maximum Size (Kbytes)...... 4,432
Starting Address........... 05597000 Starting Address........... 00800000
ECSA to ESQA (Kbytes)...... 4,120 CSA to SQA (Kbytes)........ 764
Free Blocks Available...... Yes Free Blocks Available...... No
The global data area (GDA) address is contained in the header. This address is the VSM anchor block that contains information on system-related virtual storage; in particular, the CSA and SQA subpools. The CSA tracking status is listed as either Active or Inactive at the time the SVC dump was taken. If Active, a list of address spaces that had allocated CSA is available. For more information about the Common Storage Users screen, see Common Storage Users.
Also in the header is the address of the subpool table ( SPT), which contains the DQE chains for the CSA subpools. As on the SQA Summary screen, the amounts of ECSA converted to ESQA and CSA converted to SQA are listed. These may or may not equal the difference between the allocated amounts and sizes of the SQA areas. The amount of extended CSA converted to extended SQA is 4,120K, and the amount of CSA converted to SQA is 764K. Adding 4,120K to the 79,584K allocated to extended CSA gives 83,704K. Dividing that by the size of the extended CSA at 100,772K reveals the extended CSA is 83.063 percent allocated. Adding 764K to the 3,668K allocated to CSA gives 4,432K or 100 percent of the defined size of the CSA.
An important indicator is whether there are free blocks of storage available in the extended CSA or the CSA. If there are, use the cursor point-and-shoot feature and press Enter at Yes to display the FBQEs with the address and size of each free block. If there are no free blocks available, No is displayed, which is not selectable. As expected, there are no free blocks available because the CSA was 100 percent allocated. The extended CSA does have free blocks, so press Enter at Yes to display the CSA Free Block Queue Elements screen, as shown in the following figure.
CSA Free Block Queue Elements Screen
COMMAND ===> SCROLL ===> DATA
Total free storage (Kbytes)...... 17,068
FBQE Start of End of Size of
Address Area Area Area
******** ******** ******** **********
02285F28 05597000 06519FFF 15,884K
01D47F58 065D0000 065D0FFF 4K
01AB5E08 065D7000 065DBFFF 20K
024A8520 065DE000 065E2FFF 20K
07499388 065E4000 065E8FFF 20K
02786610 065EA000 065EAFFF 4K
06A83E98 065EC000 065ECFFF 4K
02786D90 065F4000 065F8FFF 20K
088D9FD0 06604000 06604FFF 4K
02784B80 06606000 0660AFFF 20K
06AA3730 0662B000 0662FFFF 20K
02786880 06632000 06632FFF 4K
0789CA60 0663E000 0663EFFF 4K
02788CA0 06642000 06646FFF 20K
08579298 06648000 0664CFFF 20K
06D718C8 06651000 06651FFF 4K
Press the END (PF3) key to return to the Common Service Area Summary screen. Use the cursor point-and-shoot feature and press Enter at the Summarize field to display the Summarized CSA Subpools screen, as shown in the following figure
Summarized CSA Subpools Screen
COMMAND ===> SCROLL ===> DATA
==>
CSA Size (Kbytes)........................... 4,432
Extended CSA Size (Kbytes).................. 100,772
Total CSA Allocated (Kbytes)................ 3,668
Total Extended CSA Allocated (Kbytes)....... 79,584
Allocated Percent of Allocated Percent of Total Percent of
Id <16Mb Total <16Mb >16Mb Total >16Mb Allocated <16M + >16M
*** ********** *********** ********** *********** ********** ***********
227 44K 1.200 2,404K 3.021 2,448K 2.940
228 324K 8.833 5,292K 6.650 5,616K 6.746
231 984K 26.827 32,956K 41.410 33,940K 40.768
241 2,316K 63.141 38,932K 48.919 41,248K 49.546
****************************** BOTTOM OF DATA *********************************
The Summarized CSA Subpools screen is very much like the Summarized Private Subpools screen with the addition of the DQE Errors and FQE Errors columns. These are indicators if there were any errors found processing CSA DQEs or FQEs. Unless QUIESCE=YES is specified on the SDUMP macro or set via the CHNGDUMP command, the CSA and SQA remain dynamic while they are being dumped. This situation likely causes DQE and/or FQE chaining errors. Refer to the CHNGDUMP command in the IBM OS/390 MVS system commands manual for information on precedence between the SDUMP macro and the CHNGDUMP command.
The total allocations calculated for a subpool may be inaccurate if there are DQE errors. Processing for a subpool/key stops for certain DQE errors. The Abend-AID Dump Analysis Message Log and viewing server FDBDLOG show messages indicating the nature of the errors. The total allocated amounts in the header do not include the amounts (if any) converted to E/SQA. The percentages are calculated using the total allocated E/CSA amounts. Use the cursor point-and-shoot feature and press Enter at one of the subpool numbers under the Id column to display the CSA Subpool Allocations screen, as shown in the following figure.
CSA Subpool Allocations Screen
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 241
Allocated <16Mb (Kbytes).... 2,316 Free <16Mb (Kbytes)......... 195
Allocated >16Mb (Kbytes).... 38,932 Free >16Mb (Kbytes)......... 756
Total Allocated (Kbytes).... 41,248 Total Free (Kbytes)......... 951
Allocated Percent of Allocated Percent of Total Percent of
Key <16Mb Total <16Mb >16Mb Total >16Mb Allocated <16M + >16M
*** ********** *********** ********** *********** ********** ***********
0 1,416K 61.140 14,072K 36.145 15,488K 37.548
1 32K 1.382 672K 1.726 704K 1.707
2 36K 1.554 0K 0.000 36K 0.087
3 12K 0.518 304K 0.781 316K 0.766
4 12K 0.518 3,152K 8.096 3,164K 7.671
5 56K 2.418 1,880K 4.829 1,936K 4.694
6 40K 1.727 14,680K 37.707 14,720K 35.687
7 640K 27.634 3,560K 9.144 4,200K 10.182
8 52K 2.245 216K 0.555 268K 0.650
10 20K 0.864 396K 1.017 416K 1.009
****************************** BOTTOM OF DATA *********************************
This screen breaks down the CSA subpool allocations by key. The DQE and FQE error indicators apply to the subpool/key combination. If no errors were reported on the Summarized CSA Subpools screen, there should be none here. Use the cursor point-and-shoot feature and press Enter at one of the numbers under the Key column heading to display the CSA Subpool Detail screen, as shown in the following figure.
CSA Subpool Detail Screen
COMMAND ===> SCROLL ===> DATA
==>
Subpool..................... 241 Allocated <16Mb (Kbytes).... 1,416 Key......................... 0 Allocated >16Mb (Kbytes).... 14,072
SPT Entry Address........... 028D0E7C Total Allocated (Kbytes).... 15,488
Free <16Mb.................. 55,032
Free >16Mb.................. 441,376
Total Free.................. 496,408
DQE Backing Area Size of DQE FQE FQE Area Size of
Address Storage Address Area Errors Errors Address Address Area
******** ******** ******** ********** ****** ****** ******** ******** ******* 024C8F88 BELOW 00802000 12K No No 01AB5190 00802000 1,4
0672EC10 BELOW 00805000 8K No No 082560D0 00805000 3,0
024F6868 BELOW 00807000 4K No No 09A45DC0 00807000
084290B8 BELOW 00823000 12K No No 02782130 00823000 1,6
024C8F28 BELOW 0082F000 12K No No 06DDB5E0 0082F000 8
027A92F8 BELOW 00873000 12K No No 0672E8B0 00873000 1,4
06D71958 BELOW 00886000 12K No No 01AB52E0 00886000 1,6
0672EB08 BELOW 0088E000 12K No No 027ABBF8 0088E000 8
06D1BFB8 BELOW 00896000 8K No No 06D1B118 00896000 2,9
0672ED48 BELOW 0089F000 16K No No 02788910 0089F000 3,0
0256CDD8 BELOW 008B5000 12K No No 06D71B98 008B5000 3,3
The address of the SPT for this subpool/key, which is composed of several DQE chains, is displayed in the header. The remainder of the screen is similar to the Private Subpool Detail screen with the addition of the FQE Errors column. This column indicates if there were any FQE errors detected for a particular DQE. If Yes, the Free amounts in the header may be inaccurate. It takes longer to display the CSA Subpool Detail screen for a subpool/key with a large amount of storage allocated because the first 32 bytes of data need to be retrieved.
Press the RIGHT (PF11) key to display the right-most portion of the screen. In addition to looking at the first 32 bytes of data, watch for large (size) DQEs. From the First 32 Bytes of Data column, note that many modules are loaded into SP241 key 0 storage. Enter DFS in the mask line starting in the sixth position under the First 32 Bytes of Data column heading to display some of the IMS modules loaded into CSA storage, as shown in the following figure.
CSA Subpool Detail Screen, Masked
COMMAND ===> SCROLL ===> DATA
<==
Subpool..................... 241 Allocated <16Mb (Kbytes).... 1,416 Key......................... 0 Allocated >16Mb (Kbytes).... 14,072
SPT Entry Address........... 028D0E7C Total Allocated (Kbytes).... 15,488
Free <16Mb.................. 55,032
Free >16Mb.................. 441,376
Total Free.................. 496,408
DQE Backing Area Size Data
Address Storage Address Area Address First 32 Bytes of Data
******** ******** ******** ***** ******** *****DFS************************
024C8F88 BELOW 00802000 1,488 008025D0 00 DFSFXC10-410-06/27/95PN7215
0672EC10 BELOW 00805000 3,056 00805BF0 00 DFSLDTR0-410-04/10/93PTQ072
024F6868 BELOW 00807000 16 00807010 00 DFSDRCL0+S203+SP42+410+11/0
027A92F8 BELOW 00873000 1,488 008735D0 00 DFSFXC10-410-06/27/95PN7215
08AC1070 BELOW 0095A000 1,488 0095A5D0 00 DFSFXC10-410-06/27/95PN7215
08AC1088 BELOW 0095D000 3,056 0095DBF0 00 DFSLDTR0-410-04/10/93PTQ072
08CB06D0 BELOW 0095F000 16 0095F010 00 DFSDRCL0+S203+SP42+410+10/3
08BEF178 BELOW 00990000 352 00990160 00 DFSSBT10+410+04/10/93+04.55
88 009BD148 00 DFSFDLF0-410-10/30/96-08.41
0250CDF0 BELOW 009BF000 8 009BF008 00 DFSDRCL0+S203+SP53+510+05/1
2,424 009F1FC8 00 DFSIAFP0-S203-SP31-510-08/0
These modules may be loaded here because of specification in the IEAFIXxx or IEALPAxx members in SYS1.PARMLIB ; that is, the FLPA or MLPA. You can verify this from the Link Pack Areas Map.
Link Pack Areas
After you have selected the dump, enter the LPAMAP fast-path command on any command line or select the LPAMAP option (11) from the MVS Storage Analysis menu to display the Link Pack Areas Map screen, as shown in the following figure.
Link Pack Areas Map Screen
COMMAND ===> SCROLL ===> DATA
==>
PLPA Directory Address...... 00CA0000
F/MLPA Queue Address........ 00FD37C8
Dynamic LPA Queue Address... 00F0F400
Entry Extent Extent Load CDE/LPDE
Point Name Address Length Module Amode Address LPA Queue
******** ******** ******** ******** ******** ******* ******** *********
00BC8000 CTSPM 00BC8000 00002C00 AMODE31 00F1B010 F/MLPA
00BC8000 TMSPM CTSPM AMODE31 00F15B00 F/MLPA
00BCB478 TMSSECUR 00BCB478 00002B88 AMODE24 00F0A550 F/MLPA
00BCE758 TMSLABEL 00BCE758 000028A8 AMODE31 00F8D150 F/MLPA
00BD1148 CTSDATE 00BD1148 00003EB8 AMODE31 00F93040 F/MLPA
00BD1148 TMSDATE CTSDATE AMODE31 00F12200 F/MLPA
00BD51E0 TMSOSI26 00BD51E0 00002E20 AMODE31 00F920D0 F/MLPA
00BDE350 TMSOCE43 00BDE350 00004CB0 AMODE24 00F92150 F/MLPA
00BEC210 TMSTMVT 00BEC210 00001DF0 AMODE24 00F1B070 F/MLPA
00BEE010 CASMINIT 00BEE010 00000730 AMODE31 00F0DC40 F/MLPA
00BEFD88 CAS9SAFC 00BEFD88 00002278 AMODE31 00F12008 F/MLPA
00BF2088 TMSUX2S 00BF2088 000003C8 AMODE24 00F0DC70 F/MLPA
00BF2450 TMSQSTS 00BF2450 00000B10 AMODE24 00F15B50 F/MLPA
00BF91A0 TMSUX2E 00BF91A0 000003A8 AMODE31 00F0DCA0 F/MLPA
The addresses of the LPA directories or queues of the modules are displayed in the header. Depending on the version of OS/390, there is a dynamic LPA queue address. This address is a pointer to a chain of CDEs representing modules defined on LPA statements coded in PROGxx members of SYS1.PARMLIB.
This screen is sorted by entry point address. The entry point may be highlighted if it lies outside the boundaries of the the extent (XTLMSBAD+XTLMSBLN for CDEs or LPDEXTAD+LPDEXTLN for LPDEs). This situation usually indicates an OEM vendor replacement or "hook" module for an operating system function. The LPA queue identifies from which directory or queue the named module was located. The storage area identifies in which virtual storage area the entry point lies. LPA modules residing in the E/CSA or E/SQA are not identified on the Memory Display because the underlying E/CSA or E/SQA subpool is identified.
Press the RIGHT (PF11) key to display the right-most portion of the Link Park Areas Map screen. Enter PLPA in the first four positions of the mask line under the Storage Area column heading to display only modules located in the PLPA, as shown in the following figure.
Link Pack Areas Map Screen, Masked
COMMAND ===> SCROLL ===> DATA
<==
PLPA Directory Address...... 00CA0000
F/MLPA Queue Address........ 00FD37C8
Dynamic LPA Queue Address... 00F0F400
Entry E Extent Load CDE/LPDE
Point A Length Module Amode Address LPA Queue Storage Area
******** * ******** ******** ******* ******** ********* PLPA************
00CB5428 8 000000C0 AMODE24 00CA1568 PLPA PLPA
00CB54E8 8 000000B8 AMODE24 00CA1838 PLPA PLPA
00CB55A0 0 000000E0 AMODE24 00CAF988 PLPA PLPA
00CB5680 0 000000E0 AMODE24 00CA2300 PLPA PLPA
00CB5760 0 000000B8 AMODE24 00CA4F10 PLPA PLPA
00CB5818 8 000001E8 AMODE24 00CA34A8 PLPA PLPA
00CB5A00 0 00000190 AMODE24 00CA7850 PLPA PLPA
00CB5B90 0 00000158 AMODE24 00CA13B0 PLPA PLPA
00CB5CE8 8 00000180 AMODE24 00CA1388 PLPA PLPA
00CB5E68 8 00000198 AMODE24 00CA15B8 PLPA PLPA
00CB6000 0 00000008 AMODE24 00CA9538 PLPA PLPA
00CB6000 IEFRSTRT AMODE24 00CA93D0 PLPA PLPA
00CB6008 8 000001E8 AMODE24 00CA18D8 PLPA PLPA
00CB61F0 0 00000158 AMODE24 00CA6EA0 PLPA PLPA
Another way to list only modules in the PLPA is to use the cursor point-and-shoot feauture and press enter at the Starting Address of PLPA on the Virtual Storage Map screen. However, doing so does not display the same number of entries on the Link Pack Areas Map because the Allocated Storage Map includes only complete extents (load modules) from the PLPA. Enter the RESET primary command on the command line to reset the display. Enter F/MLPA in the first six positions of the mask line under the LPA Queue column heading to display only modules located in the FLPA/MLPA queue, as shown in the following figure.
Link Pack Areas Map Screen, Masked
COMMAND ===> SCROLL ===> DATA
<==
PLPA Directory Address...... 00CA0000
F/MLPA Queue Address........ 00FD37C8
Dynamic LPA Queue Address... 00F0F400
Entry E Extent Load CDE/LPDE
Point A Length Module Amode Address LPA Queue Storage Area
******** * ******** ******** ******* ******** F/MLPA*** ****************
00BC8000 0 00002C00 AMODE31 00F1B010 F/MLPA CSA
00BC8000 CTSPM AMODE31 00F15B00 F/MLPA CSA
00BCB478 8 00002B88 AMODE24 00F0A550 F/MLPA CSA
00BCE758 8 000028A8 AMODE31 00F8D150 F/MLPA CSA
00BD1148 8 00003EB8 AMODE31 00F93040 F/MLPA CSA
00BD1148 CTSDATE AMODE31 00F12200 F/MLPA CSA
00BD51E0 0 00002E20 AMODE31 00F920D0 F/MLPA CSA
00BDE350 0 00004CB0 AMODE24 00F92150 F/MLPA CSA
00BEC210 0 00001DF0 AMODE24 00F1B070 F/MLPA CSA
00BEE010 0 00000730 AMODE31 00F0DC40 F/MLPA CSA
00BEFD88 8 00002278 AMODE31 00F12008 F/MLPA CSA
00BF2088 8 000003C8 AMODE24 00F0DC70 F/MLPA CSA
00BF2450 0 00000B10 AMODE24 00F15B50 F/MLPA CSA
00BF91A0 0 000003A8 AMODE31 00F0DCA0 F/MLPA CSA
Nucleus Areas
After you select the dump, enter the NUCMAP fast-path command from any command line or select the NUCMAP option (12) from the MVS Storage Analysis menu to display the Nucleus Map screen, as shown in the following figure.
Nucleus Map Screen
COMMAND ===> SCROLL ===> DATA
NUCMAP Address........................ 016487B0
Nucleus suffix (IEANUC0x)............. 1
Number of Read/Write CSECTs........... 75
Number of Read Only CSECTs............ 87
Number of Ext Read Only CSECTs........ 1,613
Number of Ext Read/Write CSECTs....... 121
Entry CSECT CSECT
Point Name Length Amode Storage Area
******** ******** ******** ***** ****************
00FC3000 IECVPRNT 000004F8 31 Nucleus (R/W)
00FC34F8 IECVAFP1 00000780 31 Nucleus (R/W)
00FC3C78 CBROPDDT 0000004C 24 Nucleus (R/W)
00FC3CC8 IECVDDTR 0000021C 24 Nucleus (R/W)
00FC3EE8 IECVDDT5 0000004C 24 Nucleus (R/W)
00FC3F38 IOSVDDTD 0000004C 24 Nucleus (R/W)
00FC3F88 IOSVDDTE 0000004C 24 Nucleus (R/W)
00FC3FD8 IOSVDDTS 0000004C 24 Nucleus (R/W)
00FC4028 IGGDDT01 00000282 24 Nucleus (R/W)
00FC42B0 IECDPERF 0000014C 24 Nucleus (R/W)
00FC4400 IRDVDDT 00000048 24 Nucleus (R/W)
The suffix of the IEANUC0x module used to IPL the system, the address of the NUCMAP, and total CSECTs found in the four nucleus areas are displayed in the header. This screen is sorted by Entry Point address. If you know the name of a nucleus CSECT, but do not know where it is located, you can enter the name in the mask line under the CSECT Name column heading to find it. For example, if you want to locate all IGC CSECTs, enter IGC in the first three positions of the mask line, as shown in the following figure.
Nucleus Map Screen, Masked
COMMAND ===> SCROLL ===> DATA
NUCMAP Address........................ 016487B0
Nucleus suffix (IEANUC0x)............. 1
Number of Read/Write CSECTs........... 75
Number of Read Only CSECTs............ 87
Number of Ext Read Only CSECTs........ 1,613
Number of Ext Read/Write CSECTs....... 121
Entry CSECT CSECT
Point Name Length Amode Storage Area
******** IGC***** ******** ***** ****************
00FC4740 IGC247 00001A30 ANY Nucleus (R/W)
00FC6170 IGC246 00000048 ANY Nucleus (R/W)
00FC98A8 IGC234 00000B51 24 Nucleus (R/W)
00FCA400 IGC231 00000B59 24 Nucleus (R/W)
00FCAF60 IGC214 00000A80 24 Nucleus (R/W)
00FCB9E0 IGC203 00000A98 24 Nucleus (R/W)
00FD3A38 IGC037 000000DC 24 Nucleus (R/W)
00FD3B18 IGC117 000005A8 24 Nucleus (R/W)
00FEE718 IGC123 00000E70 31 Nucleus (R/O)
00FF6578 IGC043 00000190 ANY Nucleus (R/O)
00FFB7F0 IGC111 000000DD 24 Nucleus (R/O)
Enter the RESET primary command on the command line to reset the display. Enter Ext Nuc (R/O) in the mask line under the Storage Area column heading to display only modules located in the extended read-only nucleus, as shown in the following figure.
Nucleus Map Screen, Masked
COMMAND ===> SCROLL ===> DATA
NUCMAP Address........................ 016487B0
Nucleus suffix (IEANUC0x)............. 1
Number of Read/Write CSECTs........... 75
Number of Read Only CSECTs............ 87
Number of Ext Read Only CSECTs........ 1,613
Number of Ext Read/Write CSECTs....... 121
Entry CSECT CSECT
Point Name Length Amode Storage Area
******** ******** ******** ***** EXT*NUC*(R/O)***
01000000 IECVXURS 000000F0 31 Ext Nuc (R/O)
010000F0 IECVXURT 00000028 31 Ext Nuc (R/O)
01000118 IOSVEOSC 00000510 31 Ext Nuc (R/O)
01000628 CBROPDSE 000001D8 31 Ext Nuc (R/O)
01000800 IECTTRAP 000006D8 31 Ext Nuc (R/O)
01000ED8 IECVXT6S 00000450 31 Ext Nuc (R/O)
01001328 IECVXT6U 00000228 31 Ext Nuc (R/O)
01001550 IGGSNS02 00000EF0 31 Ext Nuc (R/O)
01002440 IECTDSRV 00001EB8 31 Ext Nuc (R/O)
010042F8 IECTDSR2 00002450 31 Ext Nuc (R/O)
01006748 IECVTMIH 000003E0 31 Ext Nuc (R/O)
Another way to list only modules in the extended read-only nucleus is to use the cursor point-and-shoot feature and press Enter at the Starting Address field for the extended nucleus (R/O) on the Virtual Storage Map screen. However, doing so does not display the amode information on the Nucleus Map because the Allocated Storage Map with modules from the extended read-only nucleus is displayed, as shown in the following figure.
Allocated Storage Map Screen
COMMAND ===> SCROLL ===> DATA
==>
Starting Ending Number E/PVT Sp TCB
Address Address of Pages Area Area Id Key Ownership Address
******** ******** ******** *********** ***** *** *** ********* *******
01000000 010000EF Ext Nuc-R/O
010000F0 01000117 Ext Nuc-R/O
01000118 01000627 Ext Nuc-R/O
01000628 010007FF Ext Nuc-R/O
01000800 01000ED7 Ext Nuc-R/O
01000ED8 01001327 Ext Nuc-R/O
01001328 0100154F Ext Nuc-R/O
01001550 0100243F Ext Nuc-R/O
01002440 010042F7 Ext Nuc-R/O
010042F8 01006747 Ext Nuc-R/O
01006748 01006B27 Ext Nuc-R/O
01006B28 010079B7 Ext Nuc-R/O
010079B8 01007BBF Ext Nuc-R/O
01007BC0 01007C67 Ext Nuc-R/O
01007C68 01007CBF Ext Nuc-R/O
01007CC0 01008AD7 Ext Nuc-R/O
01008AD8 01008ED7 Ext Nuc-R/O
01008ED8 01009077 Ext Nuc-R/O
Allocated Storage Map
The Allocated Storage Map displays all allocated storage through x'7FFFFFFF', including the nucleus and link pack areas providing the nucleus map and/or LPA queues are included in the SVC dump data set. After you select the dump, enter the ASMAP fast-path command on any command line or select the ASMAP option (6) from the MVS Storage Analysis menu to display all allocated storage, as shown in the following figure. All virtual storage areas are included.
Allocated Storage Map Screen
COMMAND ===> SCROLL ===> DATA
==>
Starting Ending Number E/PVT Sp TCB
Address Address of Pages Area Area Id Key Ownership Address
******** ******** ******** *********** ***** *** *** ********* *******
00005000 00005FFF 1 Private USER 0 7 OWN,SHR 007FDE8
00006000 00007FFF 2 Private USER 251 7 OWN 007E2D9
00008000 00008FFF 1 Private USER 252 0 OWN 007E2D9
00009000 00009FFF 1 Private USER 251 7 OWN 007E2D9
0000A000 0000AFFF 1 Private USER 0 7 OWN,SHR 007FDE8
0000B000 0000CFFF 2 Private USER 251 7 OWN 007E2D9
0000D000 00011FFF 5 Private USER 0 7 OWN,SHR 007FDE8
00012000 0001FFFF 14 Private USER 251 7 OWN 007E2D9
00020000 0005AFFF 59 Private USER 0 7 OWN,SHR 007FDE8
0005B000 0005FFFF 5 Private USER 251 7 OWN 007E2D9
00060000 00060FFF 1 Private USER 127 7 OWN 007E2D9
007C0000 007C1FFF 2 Private SWA 236 1 OWN,SHR 007FDE8
007C4000 007CCFFF 9 Private SWA 236 1 OWN,SHR 007FDE8
007CD000 007CDFFF 1 Private AUTH 230 7 OWN 007E2D9
007CE000 007CEFFF 1 Private LSQA 255
007CF000 007CFFFF 1 Private AUTH 230 0 OWN 007E2D9
007D0000 007D0FFF 1 Private LSQA 255
007D1000 007D1FFF 1 Private AUTH 230 5 OWN 007FDE8
Alternatively, selecting a virtual storage area’s starting address on the Virtual Storage Map displays only that area’s entries from the map. For example, use the cursor point-and-shoot feature and press Enter at the Starting Address field for extended SQA to display a subset of the Allocated Storage Map including only allocated storage for extended SQA, as shown in the following figure.
Allocated Storage Map Screen for Extended SQA
COMMAND ===> SCROLL ===> DATA
==>
Number of ESQA entries...... 794 Number of ESQA pages.... 4,848
Starting Ending Number E/PVT Sp TCB
Address Address of Pages Area Area Id Key Ownership Address
******** ******** ******** *********** ***** *** *** ********* *******
019E4000 019EBFFF 8 Ext SQA 245
01A9C000 01AC1FFF 38 Ext SQA 245
01AC2000 01AC2FFF 1 Ext SQA 248
01AC3000 01B30FFF 110 Ext SQA 245
01B31000 01B34FFF 4 Ext SQA 247
01B35000 01B35FFF 1 Ext SQA 239
01B36000 01B36FFF 1 Ext SQA 245
01B37000 01B37FFF 1 Ext SQA 239
01B38000 01B39FFF 2 Ext SQA 245
01B3A000 01B3CFFF 3 Ext SQA 248
01B3D000 01B3EFFF 2 Ext SQA 245
01B3F000 01B7DFFF 63 Ext SQA 248
01B7E000 01B7FFFF 2 Ext SQA 245
01B80000 01B89FFF 10 Ext SQA 247
01B8A000 01B8BFFF 2 Ext SQA 248
01B8C000 01B8FFFF 4 Ext SQA 245
The number of pages found allocated in the Extended SQA is displayed in the header. Multiplying these by 4096 and then dividing by 1024 equals the amount listed under the column for extended SQA on the Virtual Storage Map. Because the Allocated Storage Map is sorted by starting address, enter the BOTTOM primary command, or type MAX on the command line and then press the DOWN (PF8) key to display the highest addresses allocated to the extended SQA. Because the defined extended CSA starting address is after the ending address of the extended SQA, all of the converted extended CSA pages are at the end of the extended SQA, as shown in the following figure.
Allocated Storage Map Screen for Extended SQA
COMMAND ===> SCROLL ===> DATA
==>
Number of ESQA entries...... 794 Number of ESQA pages.... 4,848
Starting Ending Number E/PVT Sp TCB
Address Address of Pages Area Area Id Key Ownership Address
******** ******** ******** *********** ***** *** *** ********* *******
09BE4000 09BE9FFF 6 Ext SQA < 245
09BF4000 09BF4FFF 1 Ext SQA < 245
09BF8000 09BF8FFF 1 Ext SQA < 239
09D1A000 09D1AFFF 1 Ext SQA < 245
09E1E000 09E1EFFF 1 Ext SQA < 239
0A085000 0A085FFF 1 Ext SQA < 245
0A358000 0A358FFF 1 Ext SQA < 245
0A37B000 0A37BFFF 1 Ext SQA < 245
0A5E3000 0A5E3FFF 1 Ext SQA < 245
0A5E9000 0A5E9FFF 1 Ext SQA < 245
0A661000 0A66EFFF 14 Ext SQA < 245
0B1C4000 0B1C4FFF 1 Ext SQA < 245
0B1D3000 0B1D3FFF 1 Ext SQA < 245
0B1F8000 0B1F8FFF 1 Ext SQA < 245
0B228000 0B22BFFF 4 Ext SQA < 245
****************************** BOTTOM OF DATA *********************************
You can use masking and sorting on the Allocated Storage Map screen. Enter Ext SQA < in the mask line under the Area column heading to display only converted CSA pages in the extended SQA, as shown in the following figure. Now that only converted extended SQA pages are listed, enter the SORT primary command, or type SORT on the command line and press Enter at the Number of Pages column heading. Total the number of pages and multiply by 4096. Next, divide by 1024 for the amount of extended CSA converted in kilobytes. This amount should equal the amount displayed on the Common Service Area Summary screen or the SQA Summary screen.
Allocated Storage Map Screen, Masked
Row 000573 of 000587
COMMAND ===> SCROLL ===> DATA
==>
Number of ESQA entries...... 794 Number of ESQA pages.... 4,848
Starting Ending Number E/PVT Sp TCB
Address Address of Pages Area Area Id Key Ownership Address
******** ******** ******** EXT*SQA*<** ***** *** *** ********* *******
09BE4000 09BE9FFF 6 Ext SQA < 245
09BF4000 09BF4FFF 1 Ext SQA < 245
09BF8000 09BF8FFF 1 Ext SQA < 239
09D1A000 09D1AFFF 1 Ext SQA < 245
09E1E000 09E1EFFF 1 Ext SQA < 239
0A085000 0A085FFF 1 Ext SQA < 245
0A358000 0A358FFF 1 Ext SQA < 245
0A37B000 0A37BFFF 1 Ext SQA < 245
0A5E3000 0A5E3FFF 1 Ext SQA < 245
0A5E9000 0A5E9FFF 1 Ext SQA < 245
0A661000 0A66EFFF 14 Ext SQA < 245
0B1C4000 0B1C4FFF 1 Ext SQA < 245
0B1D3000 0B1D3FFF 1 Ext SQA < 245
0B1F8000 0B1F8FFF 1 Ext SQA < 245
0B228000 0B22BFFF 4 Ext SQA < 245