IBM Support

MA49115 - LIC-OTHER-WAIT VARY ON OF FLASHCOPY TARGET IASP SITS IN JOURNAL
RECOVERY STEP.

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-OTHER-WAIT VARY ON OF FLASHCOPY TARGET IASP SITS IN JOURNAL
RECOVERY STEP.

Error Description

It was discovered that a field in one of our data segment      
headers was not being forced to disk as part source IASP        
preparation during a flashcopy process. A flashcopy is viewed  
as a crash and therefore the unforced paged did not make it to  
the target system. During the vary on of the IASP on the        
flashcopy target node, the recovery code did not work as        
desired because the missing field was set to an incorrect value.
                                                               
This is only an issue for LOB (Large Objects) users and would  
only surface if a user has significant journal changes on the  
target system.                                                  
*Note - This could have also surfaced had the production system
actually crashed.                                              
                                                               
Without the fixing PTF, the target system must be re-ipl'd      
(consider capturing a MSD for verification).                    

Problem Summary

IASP vary on or IPL is stuck in the Journal Recovery step,      
SRCC6004056.                                                    

Problem Conclusion

A field in a journal receiver was not being written to disk and
could be stale as a result of a FlashCopy or system outage where
memory is not preserved. This can cause the Journal Recovery    
step of IPL or IASP vary on to not complete successfully.      
                                                               
This is only an issue when files with LOBs (Large Objects) are  
being journaled. The fix resolves the issue by writing the field
to disk as needed.                                              

Temporary Fix

Comments

Circumvention


PTFs Available

R720 MF68824  1000

R730 MF68823  2132

R740 MF68822  2125

Affected Modules


         
         

Affected Publications

Summary Information

Status............................  CLOSED PER
HIPER.............................  Yes
Component.........................  9400DG3DB
Failing Module....................  RCHMGR
Reported Release..................  R740
Duplicate Of......................  




IBM 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, 2018, 2019, 2020, 2021, 2022 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":"BU058","label":"IBM Infrastructure w\/TPS"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0; 7.3.0; 7.4.0","Product":{"code":"SWG60","label":"IBM i"},"Component":"9400DG3","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
24 May 2022