Re: Cleanup a unconnected Coupling Facility



There are probably outstanding failed persistent connections to the CF
that you need to delete. Use the command

d xcf,cf,cfname=CF2

to get a list of structures that XCF thinks is allocated on that CF. Then
you can use the command

d xcf,str,strname=<strname>

to get a list of connections to that structure. There will probably be
some that are marked failed persistent. These are what are preventing the
change.

Optionally, depending on what release of z/OS you're running, you can
issue the command

d xcf,str,status=polchg

assuming you've tried activating a new policy that doesn't contain the CF.

You can use the command

setxcf force,connection,strname=<strname>,conname=<connectionname>

Obviously, be very careful you're forcing the correct connections.

Once all the structures have been deallocated to the CF from an XCF point
of view, you should be able to remove that CF via a CFRM policy update.

That should work; we have to go through that process on the test floor
once or twice a month.

Kevin McKenzie

External Phone: 845-435-8282, Tie-line: 8-295-8282
z/OS BCP SVT, Dept FXKA, Bldg 706/2D38



From:
Cwi Jeret <cwi_jeret@xxxxxxxxx>
To:
IBM-MAIN@xxxxxxxxxxx
Date:
05/11/2008 02:47 AM
Subject:
Cleanup a unconnected Coupling Facility



We migrated our 2094 to 2097 .
We prepared A new CFRM policy containing the new 2097 definition on the
two
CF lpars, CF2 and CF3.
Now, after the migration we have CF3 defined on 2097 with active
structures,
but CF2 has still definitions of the old structures and remained pending
with its
2094 definition and with "NO SYSTEMS CONNECTED to this CF"

How can we CLEANUP the remaining Structures in CF2 so that the new 2097
difinition will take place so that we will be able to use the CF ??

C. Jeret Bank- Hapoalim T.A.

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

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

.



Relevant Pages

  • AW: I need Coupling Facility Structure information.
    ... I see the command but never the response. ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)
  • RE: CA7 Question
    ... batch job that triggers a start command... ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ... intended recipient, you are hereby notified that you are strictly ...
    (bit.listserv.ibm-main)
  • Re: Coupling Facility -- needed?
    ... If you use the GUI program Hardware Configuration Manager, you give him the two CHPIDs you want to configure, and how many devices you want genned, and he automatically does all fo the devices for you along with their interconnects. ... I ran GRS in a 4-system ring using only ESCON CTC connections and never ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)
  • Betr.: Identify Paging Datasets
    ... The command D ASM will give you the information. ... Can anyone tell me how to identify what the paging datasets are? ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)
  • Re: SDSF REXX problem
    ... When looping the returned isfrows after ISFEXEC ST command, ... Trace N ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)