Enhance data returned by IARV64 REQUEST=LIST to improve tracking of memory object creation history.

Shared memory objects are commonly used in system software and can be accessed by multiple system address spaces and components. Diagnosis for memory problems where large shared memory objects are involved would be made easier by enhanced ownership information returned by callers of IARV64 REQUEST=LIST (for example the “JMO” action in SDSF) and also the RSMDATA HVSHRDATA IPCS command. We have seen real world examples where DB2 has multiple large memory objects shared with the TCPIP address space, and it took too long to realize the ownership geography when debugging the problem situation.

Currently the TRACKINFO=YES keyword on IARV64 REQUEST=LIST can provide the requestor with a V64WADIAGDATA structure that contains the following fields for appropriate memory objects :

Creation time (STCK)

Caller ASID that issued create request

Home ASID at time of creation

Primary ASID at time of creation

Owner ASID at time of creation

Return program address

Jobname of owner

JobID of owner

Date and time of when owner terminated (not STCK (!))

Currently the V64WADIAGDATA is only fully populated for COMMON memory objects, whereas SHARED memory objects only have the creation time, caller ASID and program return address.

This request asks that the IARV64 REQUEST=LIST service be enhanced so that SHARED memory objects also return fully populated V64WADIAGDATA structures.