ADSM-L

Re: Move data in 4.2.1.8 AIX Server

2001-12-14 08:42:21
Subject: Re: Move data in 4.2.1.8 AIX Server
From: Herve CHIBOIS <herve.chibois AT FR.ABNAMRO DOT COM>
Date: Fri, 14 Dec 2001 14:37:00 +0100
Hi TSMers,

I opened a PMR for this stuff... there is an apar that SHOULD be corrected
in the .9 PTF

IThe problem is only with display, bytes are move event if some "errors"
are displayed...

Rv





Carsten Moldrup <cmoldrup AT SCA.CSC DOT COM>@VM.MARIST.EDU> on 12/14/2001
01:54:29 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: Move data in 4.2.1.8 AIX Server




I see the same in 4.2.1.0 - MVS server





"Baines, Paul" <Paul.Baines AT PARTNER.COMMERZBANK DOT COM> on 14-12-2001 
13:43:17

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Carsten Moldrup/SCA/CSC)
Subject:  Move data in 4.2.1.8 AIX Server





I upgraded to 4.2.1.8 and noticed this phenomena for Q PR on a move data:

 Process Process Description  Status

  Number
-------- --------------------
-------------------------------------------------
-------------------------------------------------
     192 Move Data            Volume F01121 (storage pool TAPEPOOL_3494     192 
Move Data            Volume F01121 (storage pool TAPEPOOL_3494),

                               Target Pool BACKUPPOOL, Moved Files: 0,
Moved

                               Bytes: 0, Unreadable Files: 0, Unreadable
Bytes:
                               1140146677. Current Physical File (bytes):

                               351,271,513

                               Waiting for mount point in device class

                               DEVC_3590 (13652 seconds).

This shows "Unreadable bytes:" as more than 0, although the MOVE DATA is
still waiting for a mount point and hasn't done anything. All the servers I
updated show a number of between 1 & 2 GB straight away after the process
starts, although "Unreadable files:" is 0. Has anyone else seen this or
have
I got a DB problem?


Mit freundlichen Grüßen - With best regards
Serdeczne pozdrowienia - Slan agus beannacht
Paul Baines
TSM/ADSM Consultant





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