ADSM-L

Re: unreadable bytes

2015-10-04 17:13:39
Subject: Re: unreadable bytes
From: Malbrough, Demetrius [mailto:DMalbrough AT TTIINC DOT COM]
To: ADSM-L AT VM.MARIST DOT EDU
I also found a VERY old APAR which sounds similiar:

APAR=3D PQ06541  SER=3D                            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=3D 565511901    ADSM MVS/VM SRV RREL=3D RAA1
FCOMP=3D 565511901    ADSM MVS/VM SRV PFREL=3D FAA1  TREL=3D 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.

<Prev in Thread] Current Thread [Next in Thread>