× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



FYI - found a solution to this.

The system was an IBM i Guest Partition running V6R1 (Host partition on V7R1).
I found PTF SI50072, not included in any cumulative PTF package, that described this exact situation, inability to delete a damaged logical file.
After installing I was able to delete the damaged logical.

PTF info:
http://www-01.ibm.com/support/docview.wss?uid=nas2a1d613caa67e7a6586257b60003c702d

 
APAR SE55628 shows this only applies to V6R1:
http://www-912.ibm.com/n_dir/nas4apar.nsf/c79815e083182fec862564c00079d117/a1d613caa67e7a6586257b60003c702d


Neil Palmer, Waterloo, Ontario, Canada


(This account not monitored for personal mail,
remove the last two letters before @ for that)


________________________________
From: Neil Palmer <neilpalmer400mr@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Saturday, October 12, 2013 12:25:59 PM
Subject: Can't get rid of a damaged logical file


I have a damaged logical file in a customer data library that I can't get rid of.

Trying to DLTF I get:

 Message ID . . . . . . :   MCH1668       Severity . . . . . . . :   40         
 Message type . . . . . :   Escape                                              
 Date sent  . . . . . . :   10/12/13      Time sent  . . . . . . :   11:40:44   
                                                                                
 Message . . . . :   System object BLCUSTL9 partially damaged. Internal dump ID 
   01006774. Error class 2, device number X'0001'.                              
 Cause . . . . . :   This partially damaged system object BLCUSTL9 has an error 
   class 2 and a device number X'0001'.  Error class indicates how damage was   
   detected:                                                                    
   0002-logically invalid device sector;                                           


Message ID . . . . . . :   CPF8160      
Severity . . . . . . . :   20        
Message type . . . . . :   Information                                         
Date sent 
. . . . . . :   10/12/13      Time sent 
. . . . . . :   11:39:01  
                                                                              
Message . . . . :   Partial
damage on BLCUSTL9 type X'1901'.                   
Cause . . . . . :   Object BLCUSTL9 type X'1901' is damaged and
may no longer 
  be
usable. The owner of the object is FRED. No owner means the object is
  a
temporary object. The VLOG dump identifier is 01006772.                   


Could not DLTLIB or CLRLIB or move the damaged file to another library, or rename the library with the damaged object either (MCH1668 & CPF8160 again).                                  


I tried to restore the library from a backup and get:

Message ID . . . . . . :   CPF3819       Severity . . . . . . . :   20       
Message type . . . . . :   Diagnostic                                        
Date sent  . . . . . . :   10/12/13      Time sent  . . . . . . :   11:57:49 
                                                                             
Message . . . . :   Damaged object FILE BLCUSTL9 not restored.               


Does anyone have an ideas as to how I can get rid of this damaged object - or is it time for a RCLSTG ?
 
 
Neil Palmer, Waterloo, Ontario, Canada


(This account not monitored for personal mail,
remove the last two letters before @ for that)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.