IBM Support

MA44507 - LIC-INCORROUT subset switched to full MSD copy corrupted.

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.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 APAR (Authorized Program Analysis Report)

Abstract

LIC-INCORROUT subset switched to full MSD copy corrupted.

Error Description

During the copy of a compressed subset main store data to the  
system ASP, if an exception occurs the MSDMgr will switch to a  
full dump and restart the copy. The restart doesn't initialize  
correctly and causes the main store data to overlay the        
hypervisor data, this makes the MSD unusable.                  

Problem Summary

****************************************************************
* PROBLEM: (MA44507) Licensed Program = 5761999 for i 6.1.1    *
*                                     = 5770999 for i 7.1 and  *
*                                       i 7.2                  *
*           Usability of a Product's MAJOR Function            *
*            A main store dump can be lost.                    *
****************************************************************
* USERS AFFECTED: All IBM i operating system users.            *
****************************************************************
* RECOMMENDATION: Apply LIC PTF MF59970 for i 6.1.1.           *
*                 Apply LIC PTF MF59968 for i 7.1.             *
*                 Apply LIC PTF MF59967 for i 7.2.             *
****************************************************************
=======                                                        
During the copy of a compressed subset main store data to the  
system ASP, if an exception occurs the MSDMgr will switch to    
full dump and restart the copy. The restart doesn't initialize  
correctly and causes the main store data to overlay the        
hypervisor data, this makes the MSD unusable.                  

Problem Conclusion

The LIC for the MSDMgr was changed to correctly initialize when
switching to a full dump.                                      
                                                               
The problem can be circumvented in a few different ways.        
1. The MSD copy options can be set to full dump.                
2. The MSD copy options can be set to not compress the dump    
data.                                                          
3. The MSD can be copied to media.                              
                                                               
Also, if the preventions steps aren't performed then while the  
copy is in progress there is still opportunity to verify the    
copy and start a second copy if necessary. During the copy,    
change the Operator panel to Manual mode and also navigate to  
the copy status screen. These steps should prevent an automatic
reIPL.                                                          
                                                               
                                                               
                                                               
To determine if the problem occurred look at the SRC history, if
the subset status SRC C6xx4404 switches to a full status SRC    
C6xx1404, then likely the problem occurred. Wait until receiving
the message "Copy completed normally." then perform the        
following procedures as needed.                                
                                                               
                                                               
                                                               
VERIFY DUMP COPY                                                
If the SRC history is not available, the dump can be verify by  
these steps.                                                    
1.Navigate to the Work with Copies of Main Storage Dumps Screen
2.On the last dump just copied enter 5 for Display/Print and    
Press enter.                                                    
3.If you quickly get an error message  " Data transfer error."  
then the MSD is corrupt.                                        
                                                               
                                                               
                                                               
                                                               
RECOVERY STEPS                                                  
1.To recover, navigate to the  1. Work with current main storage
dump (MSD)                                                      
2. Select 3. Copy to ASP                                        
3. On the next screen, where you enter the dump description you
will get a message                                              
  "Current main storage dump already copied to ASP. "          
4. Enter a new description and Press enter to continue.        
The new copy will automatically be a full dump.                

Temporary Fix

                       *********                                
                       * HIPER *                                
                       *********                                

Comments

Circumvention


PTFs Available

R611 MF62143 PTF Cover Letter   1000
R710 MF59968 PTF Cover Letter   5142
R720 MF59967 PTF Cover Letter   5135

Affected Modules

         
         

Affected Publications

Summary Information

Status............................................ CLOSED PER
HIPER........................................... Yes
Component.................................. 9400DG300
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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15Q","label":"APARs - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V6R1M1;V7R1M0;V7R2M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16B","label":"APARs - i5\/OS V6R1 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V6R1M1;V7R1M0;V7R2M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16C","label":"APARs - IBM i 7.1 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V6R1M1;V7R1M0;V7R2M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16E","label":"APARs - IBM i 7.2 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V6R1M1;V7R1M0;V7R2M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
07 June 2016