Hi All,
Today we met with a situation where one of the change with the XCF Dataset
move did not go well and we had a system running with default WLM Policy &
we starting conference to go back to the "Old XCF WLM dataset" say the
situation was like this.
Current/Active Sysplex WLM dataset
Primary : CDS04
Alternate : CDS05
Old/Inactive Sysplex WLM Dataset
Primary : CDS01
Alternate : CDS02
Now following things were tried to make dynamic changes back to CDS01/CDS02.
1. SETXCF COUPLE,TYPE=WLM,PCOUPLE=(CDS01,1D0SX7) However it came with
message
IXC309I SETXCF COUPLE,PCOUPLE REQUEST FOR WLM WAS ACCEPTED
IXC285I COUPLE DATA SET 276
SYS1.xxxx.xxx.CDS04,
VOLSER xxxxx, IS ALREADY IN USE FOR WLM ON SYSTEM
The above commond was issued keeping in mind we can replace the primary
with the one we give with the setxcf command however as shown didn't work.
Now we got the following idea.
1.
Issue the following command
SETXCF CPL,TYPE=WLM,ACOUPLE=SYS1.xxx.xxx.CDS01
and hence we will have following output
PRIMARY DSN: SYS1.xxx.xxx.CDS04
ALTERNATE DSN: SYS1.xxx.xxx.CDS01 ======> new alternate.
However biggest issue I saw with this strategy was "It's going to copy the
policy from the CDS04 to CDS01 with the overwrite" hence we will have bad
thing in CDS01 ...
Which really will make our life in mess hence we decided to go back with
the IPL and with the Change backout plan..
However being honest I am sure there must be a way to overcome this
situation..since I have done it in my shop some how years back and now to
make sure it's possible haven't have access to perform this activity on
Test system..
Can some of you guys please share your view on this..
Thanks in advance.!!!Ravi
----------------------------------------------------------------------
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
