"R Hey" <[email protected]> wrote in message
news:<listserv%[email protected]>...
> Hi,
> 
> My client had 2 CF on Z9 : CF01, CF02.
> They replaced CF01 with another one on a Z10.
> 
> They did:
> move data to old CF02:
>  SETXCF START,REBUILD,CFNAME=(CF01),LOCATION=OTHER
> activate a new CFRM Policy to say CF01 was on Z10.
> move back data to new CF01:
>  SETXCF START,REBUILD,POPCF=CF01 
> 
> 
> Now the plan was to get rid of CF02.
> 
> 6 STR were on CF02.
> These were moved from CF02 to CF01 (new z10):
>  SETXCF START,REBUILD,STRNAME=....,LOCATION=OTHER
> D XCF showed they were on CF01 (no pending MSG).
> 
> Then a new CFRM Policy was activated, having PREFLIST changed:
>                                      
> old : 
> 
> STRUCTURE NAME(HZS_HEALTHCHKLOG)            
>   SIZE(20000)                               
>   FULLTHRESHOLD(90)                         
>   INITSIZE(12000)                           
>   PREFLIST(CF02,CF01)                       
>      
> new:
> 
> STRUCTURE NAME(HZS_HEALTHCHKLOG)            
>   SIZE(20000)                               
>   FULLTHRESHOLD(90)                         
>   INITSIZE(12000)                           
>   PREFLIST(CF01,CF02) 
>                  
> Then D XCF showed all the above 6 STR in :  POLICY CHANGE PENDING - 
> CHANGE
> 
> -D XCF,STR,STRNAME=HZS_HEALTHCHKLOG        
>  IXC360I  14.43.15  DISPLAY XCF 271        
>  STRNAME: HZS_HEALTHCHKLOG                 
>   STATUS: ALLOCATED                        
>           POLICY CHANGE PENDING - CHANGE   
>   EVENT MANAGEMENT: POLICY-BASED           
>   TYPE: LIST                               
>   POLICY INFORMATION:                      
>    POLICY SIZE    : 20000 K                
>    POLICY INITSIZE: 12000 K                
>    POLICY MINSIZE : 0 K                    
>    FULLTHRESHOLD  : 90                     
>    ALLOWAUTOALT   : NO                     
>    REBUILD PERCENT: N/A                    
>    DUPLEX         : DISABLED               
>    ALLOWREALLOCATE: YES                    
>    PREFERENCE LIST: CF02     CF01          
>    ENFORCEORDER   : NO                     
>    EXCLUSION LIST IS EMPTY                 
>   PENDING POLICY INFORMATION:              
>    PREFERENCE LIST: CF01     CF02          
> 
> It seems it is pending PREF-list chng.
> 
> It was moved to CF01 already, so why pending?
> 
> TIA,
> Rez
> 

I think, the new PREFLIST is not known by the structure untill a rebuild
is done, similar to changing other parameters of a structure. In this
case is seems only cosmetic and administrative/bureaucratic, because to
get the pending change effected in de structure, you need to rebuild it
and that causes it to be rebuilt in CF01, but with the correct
adminstration.

Kees.
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to