You can request allocated storage information by coding the SPACE=ALLOC parameter of the VSMLIST macro. The format of the output varies according to what you specify for the SP parameter.
- SQA: 226, 239, 245, 247, 248
- CSA: 227, 228, 231, 241
- LSQA: 205, 215, 225, 255
Figure 1 shows the output the system produces when you issue the VSMLIST macro with SP=CSA or SP=SQA specified.
If you specify SP=PVT, the output consists of the allocated storage information for subpools in the private area according to the owning TCB. These subpools are 0-127, 129-132, 229, 230, 236, 237, 244, 249, 251, and 252.
Figure 4 shows the format of the allocated storage information for the private area.
If you specify a subpool list, the output consists of the allocated storage information for each of the subpools in the list. Figure 5 shows the format of the allocated storage information for a subpool list request.
- For the format of the work area that VSMLIST produces when you specify SP=LSQA, SP=CSA, or SP=SQA, see Figure 1
- For the format of the subpool descriptor, see Figure 2
- For the format of the allocated block descriptor, see Figure 3
- For the format of the allocated storage information for the private area, see Figure 4
- For the format of the allocated storage information for a subpool list, see Figure 5
- For the format of free space information ,see Figure 1
- For the format of the free space descriptor, see Figure 2
- For the format of unallocated storage information for CSA and PVT subpools, see Figure 1
- For the format of the region descriptor, see Figure 2
- For the format of the unallocated block descriptor, see Figure 3
This figure describes the work area that VSMLIST produces when you use SP=LSQA, SP=CSA, or SP=SQA. If you also specify SPACE=FREE, each allocated block descriptor is followed by free space information. If you specify SPACE=ALLOC, VSMLIST omits free space information.
- Byte
- Content
- 0
- X‘00’ to identify a subpool descriptor
- 1
- Length of subpool descriptor
- 2
- Subpool ID
- 3
- Miscellaneous flags
and storage key as follows:
- Bit
- Meaning When Set
- 0-3
- Storage key
- 4
- The TCB with which this descriptor is associated owns the storage described by this descriptor
- This is meaningful for private area storage only.
- 5
- The storage described by this descriptor is shared. This is meaningful for private area storage only.
- 6-7
- Reserved
- 4-7
- Owning TCB address (if PVT subpool), otherwise zero.
- Byte
- Content
- 0-3
- The virtual address of
the allocated block
- Bit
- Meaning When Set
- 0
- The caller specified the REAL31 option and this allocated block could be backed in central storage above (bit 0=1) or below (bit 0=0) 16 megabytes when the storage is fixed.
- 30
- The caller specified the REALPGFMSZ option and this storage can be backed in central storage by 1 megabyte pages (bit 30=1) or by 4K pages (bit 30=0) when the storage is fixed.
- 31
- The caller specified the REAL64 option and this allocated block could be backed in central storage above (bit 31=1) or below (bit 31=0) 2 gigabytes when the storage is fixed.
- 4-7
- The length of the allocated block
- The number of subpools in the private area is a 31-bit number.
- The address of the TCB is contained in a fullword.
- Figure 1 shows the format of the allocated storage information for the subpools owned by each TCB. The storage information begins at offset 0, “number of subpools” in that figure.
- If you specify SPACE=FREE, free space information follows each allocated block descriptor. Figure 1 describes the format of the free space information.
