>From an internal note:
======= Begin quote ===========
[A colleague] came up to me this morning saying that a dataset he had
recalled from ML2 last Wednesday on [lparname] and had added a member to
was back on ML2 this morning.
When he recalled it again, the member that he had added was missing.
I checked through SMF and saw the activity. The fact that the dataset
([data.set.name]) was on [volser] (a NONSMS volume) complicates matters
a little.
What bothers me about this is the HSM log for yesterday morning. The
message ARC0734I was issued for the dataset being sent to ML2 with an
action of MIG-RCN. This is a new keyword to me, and means that the
dataset was reconnected to its ML2 copy.
Call me Chicken Little, but I don't like the sound or look of this.
======== End quote ===========
Between last Wednesday and this morning we migrated [physically] to a
new data center. The full-volume dumps taken for the physical move were
started a little after midnight (i.e., "wee hours" Thursday morning)
after the LPAR had been shut down. All of the HSM tapes were physically
transported to the new data center and loaded into the tape subsystem
there (same hardware as the old data center). The full-volume dumps
were restored onto the DASD at the new data center (just like a D/R
exercise). The sysplex IPLed successfully at the new data center, and
exhaustive verification activities failed to detect any problems or
other "issues".
Anybody have any idea why the new member in this one dataset vanished?
-jc-
----------------------------------------------------------------------
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
