I still believe this should never happen and if so the storage should be really "orphaned" in terms of z/OS. If not the product violates the z/OS rules tracking storage.
At first DB2 development ask for a DCR but after some discussion they accept a FIN APAR PK10031 for this issue. The same issue for WMQ is still open but it seem to be same problem (HASN <> PASN). Awaiting results RRS accept a fin APAR OW57028 and fixed it in z/OS R5. Non IBM products StorageTek V5. Verify with new version At least VSMLIST OWNCOMM DETAIL should be free of OD "Owner Gone" storage even it`s not a really orpan allocation. Mostly this happen when the product miss the OWNER keyword for macro GETMAIN or STORAGE OBTAIN. Regards Roland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
