I agree it's a NONO to free these memory allocation, but it seems some are listed as OG because the getmain/storage obtain was done while running in HASN<>PASN and the missing OWNER=PRIMARY cause those memory to be owned by a TSO user or Batch job instead of a STC (server task).
Most time an eyecatcher helps to identify the "real" owner and as Chris said the IGVCAUB and the return info in the IGVGQE will help to identify the "real" owner. Of course CSA and SQA tracking should be ON in your DIAGxx member. Roland -----Ursprüngliche Nachricht----- Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag von john gilmore Gesendet: Montag, 18. Juli 2005 01:01 An: [email protected] Betreff: Re: VSMLIST OWNCOMM DETAIL Since Shane's junior did in fact own up to his sins, it was appropriate not to use thumb screws on that occasion. About certain ISVs who use single short-lived ASs to start subsystems, I'm more ambivalent; maybe thumb screws would be appropriate for them. The 'wasted' ASIDs are now recoverable, but subsystems that use one instead of two startup ASs are not themselves nearly so robust as they should be. ---------------------------------------------------------------------- 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
