Yep seen that one too, but the bytes are around 140,000,000 (140 megs!), but the move data is still showing completed successfully.
I have opened a call just to make sure.. Joe -----Original Message----- From: Malbrough, Demetrius [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 02, 2002 2:11 PM To: [EMAIL PROTECTED] Subject: Re: unreadable bytes I also found a VERY old APAR which sounds similiar: APAR= PQ06541 SER= IN INCORROUT QUERY PROC SHOWS NUMBER OF UNREADABLE BYTES > 0 BUT < 10 FOR TAPE TO TAPE MIGRATION Status: CLOSED Closed: 07/18/97 Apar Information: RCOMP= 565511901 ADSM MVS/VM SRV RREL= RAA1 FCOMP= 565511901 ADSM MVS/VM SRV PFREL= FAA1 TREL= T SRLS: NONE Return Codes: Applicable Component Level/SU: RAA1 PSY UQ13726 UP98/02/26 P 9802 Error Description: ADSM AIX Server QUERY PROCESS returns a value > 0 but < 10 (only a 1 digit number) for UNREADABLE BYTES during tape to tape migration. The number displayed for UNREADABLE BYTES is always the last digit of CURRENT FILE (BYTES). Seems to be the output buffer is not cleared. This only happens for migration from tape stg to tape stg. Local Fix: Ignore the number of unreadable bytes if it is less than 10 and increasing/decreasing between 0 and 9 during one migration process. Problem Summary: **************************************************************** * USERS AFFECTED: * All ADSM servers. **************************************************************** * PROBLEM DESCRIPTION: * Ouput from QUERY PROCESS for migration to tape shows incorrect value for ERROR BYTES. **************************************************************** * RECOMMENDATION: * Apply PTF when available. **************************************************************** Correct values now show for ERROR BYTES. Temporary Fix: Comments: MODULES/MACROS: NONE Problem Conclusion: None. -----Original Message----- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 02, 2002 1:07 PM To: [EMAIL PROTECTED] Subject: unreadable bytes Happy new year all... I was freeing up some tapes today and noticed the unreadable bytes number was not zero. Is there any way to determine what files had a problem. The move data's are completing successfully according to the act log. Thanks Joe Cascanette The Cumis Group Limited Server - 4.2.0.6 windows2000 6 Move Data Volume DIX098 (storage pool OFFSITE_DRP), Target Pool OFFSITE_DRP, Moved Files: 1533, Moved Bytes: 5,445,197,341, Unreadable Files: 0, Unreadable Bytes: 152427809. Current Physical File (bytes): 771,036 Current input volume: DIX098. Current output volume: DIX022.
