I thought it similar also. We think the problem was caused by an MPF exit doing WTO to a non-existent console. One part about the apar that bothers me is the statement "WQEs for foreign WTORs however, will remain on the WQE chain until some event initiates queue cleanup (for exapmle responding to a local WTOR)." We've responded to many WTORs but the CURR= hasn't gone down.
Thanks Craig -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dan Ahler Sent: Thursday, November 03, 2005 1:03 PM To: [email protected] Subject: Re: IEE889I Clarification What you are describing sounds similar to this: OA13112: WQE BUFFERS FOR FOREIGN WTORS ARE NOT DECHAINED AND FREED IMMEADIATELY. A specific fix for this item is not yet available electronically This record will be updated with a link to the fix if the APAR is new. For APARs older than 365 days, contact your support center. n. APAR status Closed as program error. Error description In console restructure, below the line WQE buffers should be dechained and freed as soon as they have been processed by all receiving consoles. WQEs for foreign WTORs however, will remain on the WQE chain until some event initiates queue cleanup (for exapmle responding to a local WTOR). Additional symptoms: IEE889I message output may indicate buffers in use that do not appear queued to any console. The message will reflect these buffers as messages coming from other systems. Local fix Respond to a local WTOR to initiate queue cleanup. Problem summary ---------------------------------------------------------------------- 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
