Get on 4.2.2.7 or higher before trying to work any problems. There are
major locking issues fixed in 4.2.2.7
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-----Original Message-----
From: Lawson, Jerry W (ETSD, IT) [mailto:jlawson AT THEHARTFORD DOT COM]
Sent: Wednesday, August 21, 2002 8:38 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: ANR0197E and ANR0538i message problems and system hangs for 4.2.2
Date: August 21, 2002 Time: 7:45 AM
From: Jerry Lawson
The Hartford Insurance Group
860 547-2960 jlawson AT thehartford DOT com
----------------------------------------------------------------------------
-
Good Morning. It has been a while since I had the opportunity to chat with
all of you, and stimulate your brains. Mine has been over stimulated this
AM.
Our guys here recently upgraded from TSM 4.2.1.9 to 4.2.2.2, and we are now
experiencing two new conditions. The first is a rash of ANR0197E messages.
I went through the archives, and saw the message threads relating to this
message that were written last spring. These seem to indicate that this
message is not a major problem, although we seemed to be getting a set of
them every time we generate a new tape - usually for our copypool. They
show the same things documented by others... a new tape - 100% full, written
this AM, with no errors, etc. I looked at the log for a 3 hour period this
AM, and we got almost 10,000 messages in that period, and in excess of 8,000
of them are either this message, or the associated anr9999E. (we have
context message text turned on)
Most of the information that we have dug out on these messages seem to just
be worried about the lack of documentation on these messages, and not the
volume, or relationship to any other problems.
The second problem is potentially more serious... For the last two mornings,
our TSM 4.2.2.2 system has been hung, with no apparent activity. When we
came in the AM, an incremental DB backup had been sitting waiting for a
scratch mount for over an hour, even though there were devices available.
Customer backup sessions were not doing anything, and yesterday morning they
were queued to the max, and new session requests were being rejected.
Yesterday we cancelled and restarted, but this morning, we spent some time
looking things over better.
While we were perusing the logs and available documentation, things all of a
sudden got better. We saw about 12 new messages - ANR0538I - also
undocumented, indicating that a "resource waiter had been aborted," then a
rash of anr9999 messages, but things seemed fine.
However, it doesn't seem as though they have stayed that way for long... we
tried to run another incremental backup (we had cancelled the first one),
and once again it seems to be waiting for a scratch mount. We checked and
found that a mount request had actually been issued, and also satisfied by
z/os.
We have seen nothing to indicate that these two conditions are related, but
the coincidence of them both showing up at the same time...
Has anyone else seen behavior like this?
----------------------------------------------------------------------------
-
Jerry
Insanity is doing the same thing over and over....and expecting the results
to be different - Anon.
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you are
not the intended recipient, please notify the sender immediately by return
email and delete this communication and destroy all copies.
|
