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-INCORROUT CRTPFRDTA missing QAPMDISK data
Error Description
The customer has 2128 multipath disk units on a system with 2
paths for each disk unit, for a total of 4256 paths. There are
1886 configured disk units, for a total of 3772 paths. This
exceeds the system limit of 2800 paths. When CRTPFRDTA runs on
the system, there is no data output in the QAPMDISK file.
Problem Summary
CRTPFRDTA does not write any records to file QAPMDISK if the
system limit for combined disk arms and redundant connections
(paths) to disk units is exceeded.
Problem Conclusion
An internal table used by CRTPFRDTA was not large enough to
process disk data if the system limit was exceeded, so
processing of the data stopped with no data written to file
QAPMDISK. This fix is a circumvention that increases the size of
the internal table. It does not guarantee the accuracy of the
collected disk data if the system limit is exceeded.
Temporary Fix
Comments
Circumvention
PTFs Available
Affected Modules
Affected Publications
Summary Information
Status............................................ | CLOSED PER |
HIPER........................................... | No |
Component.................................. | 5770SS100 |
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:
16 November 2013