hasposters.blogg.se - How to edit tems log file

#How to edit tems log file zip file#

Let’s pick /tmp and the TEMS is installed at the default directory.

#How to edit tems log file zip file#

Unpack the most recent zip file and copy the and testaud.ini files to a convenient location where Perl is installed and on the system where a TEMS is running. Sometimes you want immediate results and to heck with the details. In recent months there have been several advisories and/or report sections added each month. The source in every case is based on diagnosing a specific customer issue and when possible adds an advisory or report section which would speed the diagnostic effort – even allowing the customer to correct the condition whenever possible.

Each report section is documented along with needed traces.

The separate word file documents have been eliminated and information added here, revised and extended.

The program can be viewed to see each advisory explanation.

The TEMS Audit report itself includes an explanation of each advisory and that is not duplicated in this document.

At level 1.64000 the documentation has been reworked for simplicity and clarity. Since the last published version 1.37000 38 new advisories have been added and many report sections to explain the environment further. In March 2011, I published the process and tool as a technical note and it is now widely used. The customer was convinced, made the changes and those six systems dropped to 10% utilization. I wrote a Perl program to summarize the results in a spreadsheet file.

The solution was presented but the customer was unconvinced. Some 6 months later in Dec 2010 I had a customer with six AIX servers running at 95% utilization and all from remote TEMS processing. That was probably the single most expensive PMR I ever worked on. The customer decided to recycle the affected remote TEMSes once a week.

The conclusion was that a certain type of situation caused a severe storage fragmentation and a TEMS failure in 10-12 days. In 2008 I began work on a year-old customer problem that took until Spring 2010 to resolve. In addition, there may be important error messages in the diagnostic log. Situations are the most common workload but SOAP calls, historical data collection and Portal Client workspaces can be involved. This condition is usually caused by workloads, configuration or environmental conditions. In some cases, the TEMS experienced a steady storage growth and failure after some days. Version 2.34000 18 August 2021 John Alvord, IBM Corporation have been cases every year where a TEMS was running with high enough CPU/Storage resource usage that the customer was concerned.