ADSM-L

Re: 5.2.2 expiration problem

2005-09-20 15:19:13
Subject: Re: 5.2.2 expiration problem
From: "Cornett, Paul" <paul.cornett AT TYSON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 20 Sep 2005 14:01:20 -0500
Sounds like you have a stg pool with the id of 12 with problems.  I
would start there.


_______________________________________________
Paul Cornett
Sr. Systems Administrator
IS Capacity Planning
Tyson Foods, Inc.
2210 W Oaklawn Dr
Springdale, AR 72762
Email: Paul.Cornett AT Tyson DOT com <mailto:Paul.Cornett AT Tyson DOT com>
Phone: 479.290.1748
Cell:    479.871.4209

_______________________________________________




________________________________

        From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of Shannon Bach
        Sent: Friday, August 12, 2005 11:25 AM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: [ADSM-L] 5.2.2 expiration problem
        
        

        We recently upgraded our MVS/OS390 to ZOS 1.4 and our ZOS TSM
Server to 5.2.2.  When doing an expiration I noticed the following error
messages which are now filling up my Sever Activity Log.  I could not
find anything at the Support Center except something relating to an AIX
system.
        
        Has anyone run into this that can lead me in the right
direction?
        
        Thank you,
        Shannon
        
        08/12/2005 10:18:15 ANR4391I Expiration processing node BLUEP,
filespace \\bluepump\f$, fsId 2, domain MGE_PD_001, and management class
MGE_MC_WIN2000 - for BACKUP type files. (SESSION: 7034, PROCESS: 1832)

        08/12/2005 10:18:15 ANR4391I Expiration processing node BLUEP,
filespace \\bluepump\g$, fsId 3, domain MGE_PD_001, and management class
DEFAULT - for BACKUP type files. (SESSION: 7034, PROCESS: 1832)

        08/12/2005 10:18:16 ANR9999D SSALLOC(1372): ThreadId<23334>
Error locating storage pool -12.  Callchain follows:
pkShowCallChain+2E2 <- outDiagf+27E <- ssDealloc+16E <-
AfDeallocSegments+3AE <- AfDeleteBitfileFromPool+6D0 <- AfDestroyAll+328
<- bfDestroy+7D4 <- ImDeleteBitfile+DC <- imDeleteObject+CAC <-
DeleteFilesThread+78E <- pkThreadHead+4FA (SESSION: 7034, PROCESS: 1832)

        
        08/12/2005 10:18:16 ANR9999D SSALLOC(1372): ThreadId<23334>
Error locating storage pool -12.  Callchain follows:
pkShowCallChain+2E2 <- outDiagf+27E <- ssDealloc+16E <-
AfDeallocSegments+3AE <- AfDeleteBitfileFromPool+6D0 <- AfDestroyAll+328
<- bfDestroy+7D4 <- ImDeleteBitfile+DC <- imDeleteObject+CAC <-
DeleteFilesThread+1326 <- pkThreadHead+4FA (SESSION: 7034, PROCESS:
1832)
        
        08/12/2005 10:12:55 ANR4391I Expiration processing node WHATSUP,
filespace \\whatsup2\e$, fsId 4, domain MGE_PD_001, and management class
MGE_MC_WIN2000 - for BACKUP type files. (SESSION: 7034, PROCESS: 1832)

        

        08/12/2005 10:12:56 ANR4391I Expiration processing node ISCAN01,
filespace \\iscan\c$, fsId 1, domain MGE_PD_001, and management class
DEFAULT - for BACKUP type files. (SESSION: 7034, PROCESS: 1832)
        

        08/12/2005 10:12:58 ANR9999D SSALLOC(1372): ThreadId<23334>
Error locating storage pool -12.  Callchain follows:
pkShowCallChain+2E2 <- outDiagf+27E <- ssDealloc+16E <-
AfDeallocSegments+3AE <- AfDeleteBitfileFromPool+6D0 <- AfDestroyAll+328
<- bfDestroy+AA6 <- ImDeleteBitfile+DC <- imDeleteObject+CAC <-
DeleteFilesThread+78E <- pkThreadHead+4FA (SESSION: 7034, PROCESS: 1832)

        
        
        
        Madison Gas & Electric Co
        Operations Analyst -Data Center Services
        Information Management Systems
        sbach AT mge DOT com
        
        



This email and any files transmitted with it are confidential and intended 
solely for the use of the addressee. If you are not the intended addressee, 
then you have received this email in error and any use, dissemination, 
forwarding, printing, or copying of this email is strictly prohibited. Please 
notify us immediately of your unintended receipt by reply and then delete this 
email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates 
will not be held liable to any person resulting from the unintended or 
unauthorized use of any information contained in this email or as a result of 
any additions or deletions of information originally contained in this email.

<Prev in Thread] Current Thread [Next in Thread>
  • Re: 5.2.2 expiration problem, Cornett, Paul <=