MF66920 - OSP-DB-OTHER-WAIT FILE DESTROYED WHILE THERE IS STILL SOME O

TYPE PROGRAM  RELEASE   NUMBER   MIN/MAX  OPTION
---- -------- --------- -------  -------  ------
NONE



NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels.  This PTF may be a prerequisite
for future PTFs.  By applying this PTF you authorize and agree to the
foregoing.

This PTF is subject to the terms of the 'IBM License Agreement for Machine
Code', the terms of which were provided in a printed document that was
delivered with the machine.

SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.





APAR Error Description / Circumvention

-----------------------------------------------
We have background tasks that we use within the operating system
to make sure we control the order in which certain metadata we
keep for objects at the OS level are written to disk. We do this
for object recovery purposes in the event there is some kind of
system interruption/outage from which objects need to be
recovered. In this case, it looks like a file was destroyed
while there was still some outstanding work being done on it's
behalf in one of these background tasks and the timing of
everything caused the background task to be stuck in a state
where he will never be woken up so that he can send a response
to other jobs that he has completed his work. So, those other
jobs sit and wait for a confirmation that never comes.

we'll introduce some code changes that 1) may reduce the
likelihood of the occurrence of this problem, and 2) leave some
additional diagnostics for us to look at when it does occur.

CORRECTION FOR APAR MA48009 :
-----------------------------
some code changes that 1) may reduce the likelihood of the
occurrence of this problem, and 2) leave some additional
diagnostics for us to look at when it does occur.

CIRCUMVENTION FOR APAR MA48009 :
--------------------------------
None.


Activation Instructions


None.




Special Instructions


None.


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
   MF66230      SQL-RUN-WAIT APPLICATION JOB DOESN'T END
   MF61783      LIC-DB-OTHER-F/DBPMRESOURCELIBRARY-T/QDBGETMQO-MSGMCH3601 MS

Summary Information

IBM i Support