CF Status of Transitioning

[Michael Hall]

List,

We migrated an LPAR from one physical box to another, and one CF to another.
Displaying a structure shows one structure allocated and one in transition. I
would like to get rid of the "in transition messages" since we are not planning
to use that CF on this system and currently have no connection to it.

I am wondering if there was something that we did improperly when we
brought down the old LPAR.

Our current CF policy has old and new CF addresses in it.

Thanks for any help or anyone can point me to a manual that would answer
these questions.

Our structure status looks as follows:

D XCF,STR,STRNM=DSNPB0A_GBP0
MR0000000 BP1D 09083 10:39:51.15 DB2ADM 00000090 IXC360I
10.39.51 DISPLAY XCF 504
LR 504 00000090 STRNAME: DSNPB0A_GBP0
DR 504 00000090 STATUS: ALLOCATED
DR 504 00000090 POLICY INFORMATION:
DR 504 00000090 POLICY SIZE : 64000 K
DR 504 00000090 POLICY INITSIZE: 16000 K
DR 504 00000090 POLICY MINSIZE : 0 K
DR 504 00000090 FULLTHRESHOLD : 80
DR 504 00000090 ALLOWAUTOALT : NO
DR 504 00000090 REBUILD PERCENT: 1
DR 504 00000090 DUPLEX : ENABLED
DR 504 00000090 ALLOWREALLOCATE: YES
DR 504 00000090 PREFERENCE LIST: BA01C1
BAC1C1 BCC1C5 BCC2C5
DR 504 00000090 ENFORCEORDER : NO
DR 504 00000090 EXCLUSION LIST IS EMPTY
DR 504 00000090
DR 504 00000090 STRUCTURE IN TRANSITION
DR 504 00000090 -----------------------
DR 504 00000090 REASON IN TRANSITION:
CONNECT OR DISCONNECT IN PROGRESS
DR 504 00000090 ALLOCATION TIME:
03/22/2009 00:23:31
DR 504 00000090 CFNAME : BAC1C1
NO SYSTEMS CONNECTED TO COUPLING FACILITY
DR 504 00000090 COUPLING FACILITY:
002064.IBM.83.000000069C7C
DR 504 00000090 PARTITION:
01 CPCID: 00
DR 504 00000090 ACTUAL SIZE : N/A
DR 504 00000090 STORAGE INCREMENT SIZE:
N/A
DR 504 00000090 PHYSICAL VERSION:
C3EB3BCF B3306102
DR 504 00000090 SYSTEM-MANAGED
PROCESS LEVEL: NOT AVAILABLE

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

[Gaur]

Post by Michael Hall
List,
We migrated an LPAR from one physical box to another, and one CF to another.
Displaying a structure shows one structure allocated and one in transition. I
would like to get rid of the "in transition messages" since we are not planning
to use that CF on this system and currently have no connection to it.
I am wondering if there was something that we did improperly when we
brought down the old LPAR.
Our current CF policy has old and new CF addresses in it.
Thanks for any help or anyone can point me to a manual that would answer
these questions.
 D XCF,STR,STRNM=DSNPB0A_GBP0
 MR0000000 BP1D     09083 10:39:51.15 DB2ADM   00000090  IXC360I  
10.39.51  DISPLAY XCF 504
 LR                                        504 00000090  STRNAME: DSNPB0A_GBP0
 DR                                        504 00000090   STATUS: ALLOCATED
 DR                                        504 00000090    POLICY SIZE    : 64000 K
 DR                                        504 00000090    POLICY INITSIZE: 16000 K
 DR                                        504 00000090    POLICY MINSIZE : 0 K
 DR                                        504 00000090    FULLTHRESHOLD  : 80
 DR                                        504 00000090    ALLOWAUTOALT   : NO
 DR                                        504 00000090    REBUILD PERCENT: 1
 DR                                        504 00000090    DUPLEX         : ENABLED
 DR                                        504 00000090    ALLOWREALLOCATE: YES
 DR                                        504 00000090    PREFERENCE LIST: BA01C1
BAC1C1 BCC1C5 BCC2C5
 DR                                        504 00000090    ENFORCEORDER   : NO
 DR                                        504 00000090    EXCLUSION LIST IS EMPTY
 DR                                        504 00000090
 DR                                        504 00000090   STRUCTURE IN TRANSITION
 DR                                        504 00000090   -----------------------
CONNECT OR DISCONNECT IN PROGRESS
03/22/2009 00:23:31
 DR                                        504 00000090    CFNAME         : BAC1C1    
NO SYSTEMS CONNECTED TO COUPLING FACILITY
002064.IBM.83.000000069C7C
01   CPCID: 00
 DR                                        504 00000090    ACTUAL SIZE    : N/A
N/A
C3EB3BCF B3306102
 DR                                        504 00000090    SYSTEM-MANAGED
PROCESS LEVEL: NOT AVAILABLE
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
Search the archives athttp://bama.ua.edu/archives/ibm-main.html

why we have still old CF in preference list? PREFERENCE LIST:
BA01C1

Post by Michael Hall
BAC1C1 BCC1C5 BCC2C5

I take BAC1C1 is old?

Basically you would have to delete it..probably forcely....(the below
note I could find from Setting up sysplex manual)

Deleting Persistent Structures If the structure is persistent
(DISPOSITION: KEEP in IXC360I) and the number of connectors to the
structure in message IXC360I is greater than zero, then delete the
structure as described below. If ACTIVE connectors exist (see
connection state in IXC360I), invoke recovery procedures for the
connector, or CANCEL the connector's address space to make the
connector disconnect from the structure. Then, if the connector enters
a failed-persistent state, force the connector using the SETXCF
FORCE,CON. Then, to delete the structure, issue: SETXCF
FORCE,STR,STRNM=strname Because the MVS system does not have
connectivity to the failed coupling facility, you will receive message

IXC353I THE SETXCF FORCE REQUEST FOR STRUCTURE
strname WAS ACCEPTED:
REQUEST WILL BE PROCESSED ASYNCHRONOUSLY


Once all failed-persistent connectors are forced or the structure is
forced, the structure should enter an "in transition" state. If you
display the structure again, message IXC360I should contain the
following statements:

STRUCTURE IN TRANSITION
-----------------------
REASON IN TRANSITION: CONNECT OR DISCONNECT IN PROGRESS


When the structure enters an "in transition" state, it means that the
structure is "targeted for deletion" by CFRM. At this point, a new
instance of the structure can be allocated in another coupling
facility. Depending on the application that owns the structure, you
might need to restart the application for the structure to become
allocated in the alternate coupling facility. Note: When the
structure is allocated in an alternate coupling facility, the DISPLAY
XCF,STR,STRNAME=strname command will produce information about both
the new instance of the structure in the alternate coupling facility
and the "structure in transition" which is pending deletion from the
failed coupling facility. When the failed coupling facility is
eventually restored, XCF will resolve the "structure in transition"
condition and this information will no longer be displayed.

[Skip Robinson]

The recommended 'ideal' method to migrate from one sysplex environment to
another is completely dynamic, using SETXCF commands to empty an old CF by
rebuilding all of its structures in either a CF that stays connected before
and after the migration, or in a new CF that is already connected before
the migration. We did some migrations last year where neither option was
possible:

-- Push/pull hardware such that all old CFs are replaced by new ones in a
single outage
-- Relocate systems and (logical) CFs to another data center beyond cable
length limits

In such cases you come up with a set of brand new CFs. No matter how well
you prepare, you will still get some structures with one foot in the old
world and one the new. XCF wants to touch the old CF to clean up properly.
If that's not possible, just create a new CFRM policy that contains no
trace of the old CF. That is, the CF definition itself is gone, and all
PREFLISTs no longer contain any reference to the old CF. That policy should
implement with no problem, and structure displays will now show clean.

As long as your sysplexes are functioning with all structures active
somewhere, I'd say you did it all properly.

.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
***@sce.com



Michael Hall
<***@ATTGLOBA
L.NET> To
Sent by: IBM IBM-***@bama.ua.edu
Mainframe cc
Discussion List
<IBM-***@bama.ua Subject
.edu> CF Status of Transitioning


04/12/2009 10:20
PM


Please respond to
IBM Mainframe
Discussion List
<IBM-***@bama.ua
.edu>






List,

We migrated an LPAR from one physical box to another, and one CF to
another.
Displaying a structure shows one structure allocated and one in transition.
I
would like to get rid of the "in transition messages" since we are not
planning
to use that CF on this system and currently have no connection to it.

I am wondering if there was something that we did improperly when we
brought down the old LPAR.

Our current CF policy has old and new CF addresses in it.

Thanks for any help or anyone can point me to a manual that would answer
these questions.

Our structure status looks as follows:

D XCF,STR,STRNM=DSNPB0A_GBP0
MR0000000 BP1D 09083 10:39:51.15 DB2ADM 00000090 IXC360I
10.39.51 DISPLAY XCF 504
LR 504 00000090 STRNAME:
DSNPB0A_GBP0
DR 504 00000090 STATUS: ALLOCATED
DR 504 00000090 POLICY
INFORMATION:
DR 504 00000090 POLICY SIZE :
64000 K
DR 504 00000090 POLICY INITSIZE:
16000 K
DR 504 00000090 POLICY MINSIZE :
0 K
DR 504 00000090 FULLTHRESHOLD :
80
DR 504 00000090 ALLOWAUTOALT :
NO
DR 504 00000090 REBUILD PERCENT:
1
DR 504 00000090 DUPLEX :
ENABLED
DR 504 00000090 ALLOWREALLOCATE:
YES
DR 504 00000090 PREFERENCE LIST:
BA01C1
BAC1C1 BCC1C5 BCC2C5
DR 504 00000090 ENFORCEORDER :
NO
DR 504 00000090 EXCLUSION LIST
IS EMPTY
DR 504 00000090
DR 504 00000090 STRUCTURE IN
TRANSITION
DR 504 00000090
-----------------------
DR 504 00000090 REASON IN
TRANSITION:
CONNECT OR DISCONNECT IN PROGRESS
DR 504 00000090 ALLOCATION TIME:

03/22/2009 00:23:31
DR 504 00000090 CFNAME :
BAC1C1
NO SYSTEMS CONNECTED TO COUPLING FACILITY
DR 504 00000090 COUPLING
FACILITY:
002064.IBM.83.000000069C7C
DR 504 00000090
PARTITION:
01 CPCID: 00
DR 504 00000090 ACTUAL SIZE :
N/A
DR 504 00000090 STORAGE
INCREMENT SIZE:
N/A
DR 504 00000090 PHYSICAL
VERSION:
C3EB3BCF B3306102
DR 504 00000090 SYSTEM-MANAGED
PROCESS LEVEL: NOT AVAILABLE

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