Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.
APAR (Authorized Program Analysis Report) |
Abstract
OSP-MSGMCH2603-D/TQJOREAPY QJOREAPY TAKES MCH2603 EXCEPTION
WHEN TRYING TO UNLOCK A FILE IT HASN'T LOCKED.
Error Description
QJOREAPY takes an MCH5802 exception when attempting to lock a
file. The exception handling performs cleanup, then attempt to
unlock the file even though it is not locked, causing an
MCH2603 exception. This is causing issue trying to determine
the source of the error. Correct message should be CPF7007 and
CPF9803 (file/object in use).
Problem Summary
QJOREAPY takes an MCH5802 exception when attempting to lock a
file. The exception handling performs cleanup, then attempt to
unlock the file even though it is not locked, causing an MCH2603
exception. This is causing issue trying to determine the source
of the error. Correct message should be CPF7007 and CPF9803
(file/object in use).
Problem Conclusion
CPF7007 or CPF9803 will be returned with the name of the object
that had the lock conflict.
Temporary Fix
Comments
Circumvention
PTFs Available
R710 SI54129 5142
R720 SI54131 5135
Affected Modules
Affected Publications
Summary Information
Status............................................ | CLOSED PER |
HIPER........................................... | No |
Component.................................. | 5770SS1DB |
Failing Module.......................... | RCHMGR |
Reported Release................... | R710 |
Duplicate Of.............................. |
System i Support
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information
Document Information
Modified date:
30 May 2015