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
HASM-HA-F/RMSLLOCKCHECK-T/QYASPDDDTA-MSGMCH2601 RETRIEVING
DEVICE DOMAIN DATA VIA QYASPDDDTA FAILS DURING SAVCFG.
Error Description
Applications that use API QYASRTVDDD to retrieve device domain
data at the same time as a SAVCFG is occurring may experience
an MCH2601.
Code will be enhanced to handle the condition better and more
gracefully distinguish between an entry not existing and an
entry that is "in use"
Work around:
Do not make a call to QYASRTVDDD while a SAVCFG is occurring.
Problem Summary
Applications that use API QYASRTVDDD to retrieve device domain
data at the same time as a SAVCFG is occurring may experience an
MCH2601.
Code will be enhanced to handle the condition better and more
gracefully distinguish between an entry not existing and an
entry that is "in use"
Work around:
Do not make a call to QYASRTVDDD while a SAVCFG is occurring.
Problem Conclusion
QYASRTVDDD will be enhanced to give a better reason code.
Temporary Fix
Comments
Circumvention
PTFs Available
R710 SI64097 7192
R720 SI64154 7290
R730 SI64167 7283
Affected Modules
Affected Publications
Summary Information
Status............................................ | CLOSED PER |
HIPER........................................... | No |
Component.................................. | 5770SS100 |
Failing Module.......................... | RCHMGR |
Reported Release................... | R720 |
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:
28 October 2017