Re: XCF Recovery Process IXC247D
- From: starsoul@xxxxxxxxxxxxxx (Lizette Koehler)
- Date: 30 Sep 2007 11:01:45 -0700
Fortunately, there are no other sysplexes other than this one SCPLX1.
However, I knew that since this was the ACOUPLE datasets that were affected,
and we were running fine on the primary ones, I just went ahead and did a
delete, Define (using the utility) and then issued the SETXCF
COUPLE,ACOUPLE= command. Worked fine. I now have Primary and Alternate
data sets again.
I was just was wondering what might have happened in a SINGLE Sysplex
environment (ie no other sysplexes other than mine) if the response of U was
done.
Lizette
A reply of "U" would be acceptable in this case. It's a matter of
time-stamps not agreeing, etc. If you had a second SYSPLEX active
sharing the same DASD, then I'd be busily checking that this dataset was
not, in fact, in use by the other SYSPLEX.
----------------------------------------------------------------------
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
.
- References:
- XCF Recovery Process IXC247D
- From: Lizette Koehler
- Re: XCF Recovery Process IXC247D
- From: Rick Fochtman
- XCF Recovery Process IXC247D
- Prev by Date: Re: XCF Recovery Process IXC247D
- Previous by thread: Re: XCF Recovery Process IXC247D
- Index(es):
Relevant Pages
|
