Fix pak 5.3.3.2 is now out. See if that fixes your issue.




Andrew Ferris <aferris AT MRL.UBC DOT CA>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/06/2006 12:11 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
[ADSM-L] ANR9999D






Hello All,

TSM Server 5.3.3.0 on Windows. My daily report had this abnormal section
in it:

2006-07-06 05:00                 ANR2111W                BACKUP STGPOOL:
There is no data to process for ARCHIVEPOOL.(SESSION: 34889)
2006-07-06 05:01                 ANR9999D                pvrntp.c(2853):
ThreadId<36> Invalid read call for volume ICA183L2.(SESSION: 34889,
PROCESS: 935)
2006-07-06 05:01                 ANR9999D                ThreadId<36>
issued message 9999 from: (SESSION: 34889, PROCESS: 935)
2006-07-06 05:01                 ANR1227E                BACKUP STGPOOL:
Process 935 terminated - internal server error detected.(SESSION: 34889,
PROCESS: 935)
2006-07-06 05:01                 ANR9999D                ThreadId<29>
issued message 1227 from: (SESSION: 34889, PROCESS: 935)

This occurred during a BACKUP STGPOOL. Here's some more info on the
volume:

tsm: TSM_SERVER1>q vol ICA183L2 f=d

                   Volume Name: ICA183L2
             Storage Pool Name: ARCHIVETAPE
             Device Class Name: LTO2
            Estimated Capacity: 381,468.0
       Scaled Capacity Applied:
                      Pct Util: 1.1
                 Volume Status: Filling
                        Access: Read/Write
        Pct. Reclaimable Space: 0.0
               Scratch Volume?: Yes
               In Error State?: No
      Number of Writable Sides: 1
       Number of Times Mounted: 32
             Write Pass Number: 1
     Approx. Date Last Written: 07/01/2006 00:01:48
        Approx. Date Last Read: 07/06/2006 05:01:39
           Date Became Pending:
        Number of Write Errors: 0
         Number of Read Errors: 0
               Volume Location:
Volume is MVS Lanfree Capable : No
Last Update by (administrator):
         Last Update Date/Time: 06/22/2006 16:54:20
          Begin Reclaim Period:
            End Reclaim Period:

This looks very similar to APAR number IC48731. The only difference I can
see is the APAR talks of pvrntp.c(2840) versus pvrntp.c(2853) in my error.
Should I apply the fixpack (5.3.3.1)?

Andrew Ferris
Network Support Analyst
iCAPTURE Research Centre
University of British Columbia