click your heels three times and repeat, there's no place like home there's no place like home there's no place like home
:) -----Original Message----- From: Persson, Linus [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 23, 2004 8:26 AM To: [EMAIL PROTECTED] Subject: Re: TSM server down Richard, how do i get off this list? I forgot how I unregister... -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: den 23 juni 2004 13:41 To: [EMAIL PROTECTED] Subject: Re: TSM server down >My TSM server suddenly was down ... twice for the past 2 weeks ... once >was on the 17th June and the one was today ... 23rd June ... I dunno >what is wrong ... > >when I tried to log in by typing ... > >dsmadmc > >then it did ask me for my user id then ... when I typed in my user id >... i press enter and then .. it gives ... this message > >ANS1017E Session rejected: TCP/IP connection failure >ANS8023E Unable to establish session with server > >ANS8002I Highest return code was -50 ----- >I checked my dsmserv.err I think my recovery log is full it gives me > >ANR7837S Internal error LOGSEG871 detected > >how can I start to get this thing up and running ... > >how can I make some space for the recovery log ? do I use one or more of >the tapes ... ? how can I log in ? I can't get my webadmin ... to start >... and I can't log in using .. dsmadmc ... command .. urrrggghhh ... It cannot be stressed strongly enough that: 1. As part of implementing any major system, it is absolutely essential that we become familiar with it, which means having read the manuals and having become familiar with both the elements of the system and where to look up information, particularly problem handling information. 2. That the system be administered, a vital element of which is monitoring, particularly for resource shortages. 3. That we investigate early indications of problems, which allows timely remediation and prevents them from growing into calamities. It pains us to see postings like this, where a major system upon which a company is depending is needlessly falling apart. IBM, and the customers participating in this mutual-aid mailing list, make great efforts to try to assure that TSM systems do what they need to. It's disappointing to us when a customer ignores all the information and ends up in hot water. As for remediation: - Boosting the size of the Recovery Log is covered in the Admin Guide manual, under "Increasing the Size of the Database or Recovery Log" - The dsmadmc command is a client, which interacts with a server once it is up. If the server does not come up, then dsmadmc is obviously useless, and you need to deal with the server initialization command itself, which is 'dsmserv', which is covered in the Admin Guide manual under "Starting the server". The doc indicates that if you run dsmserv with the "quiet" option, then the server starts as a detached daemon - and therefore if you invoke it without that option, you are in interactive mode, where you will see all messages and thus problem indications. Please heed the lessons of this outage and do better for your employer...who is depending upon you. Richard Sims http://people.bu.edu/rbs Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
