[z/OS]

Choosing and using diagnosis tools and controls on z/OS

The following is a description of the types of tools and controls you can use for diagnosing and managing problems in the product environment.

Before you begin

The product uses a variety of different tools and server controls to help you collect specific types of data to determine where your servers are encountering problems. To efficiently use these tools you need to be aware of the different functions each can provide and what type of information will be available from each.
Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。

About this task

When your applications or servers are experiencing problems that may be originating from different sources, use the following tools to collect data and information on processes in your environment. Each tool has functions specific to different parts of the product, and they can be used in concert to help you better diagnose your problems.

Procedure

Use the following z/OS tools to access and work with diagnostic information.
  • z/OS console

    The console displays configuration errors that cause the termination of the product address spaces. Whatever goes to the console also goes to SYSLOG.

  • System log (SYSLOG)

    SYSLOG is the repository for all messages that have appeared on the operator console. It also contains warning and informational messages that might be helpful after a failure has occurred.

  • Job log

    The job log contains errors and warnings (non-termination) that are related to configuration. Anything that goes to the console and SYSLOG automatically goes to the job log.

  • System output (SYSOUT)

    SYSOUT is a batch log that usually contains diagnostic data from the Java™ Virtual Machine (JVM) that runs in the servant. Any messages written to stderr will end up in SYSOUT. In addition, SYSOUT might contain error messages that usually appear in the log stream, but were redirected to SYSOUT, because the log stream was not available.

  • Error log

    The error log contains messages issued through Java logging and JRas support, if any. In addition, the error log usually contains messages that are only intended for IBM use. These messages support actions, problems, or issues that are usually externalized through additional messages that are issued by other functions. When you work with IBM Support personnel, you might be asked to supply the error log so that service personnel can use these support messages to help diagnose the problem.

    Note: You must update the CFRM policy before using log streams that are CF-resident, such as the WebSphere® error log and RRS logs. See [z/OS]Updating the CFRM policy for details.
  • SYSPRINT

    SYSPRINT contains component trace (CTRACE) output for clients, and for servants when the product is configured to use SYSPRINT instead of CTRACE buffers and data sets.

  • Component trace (CTRACE) data set

    CTRACE data sets contain diagnostic trace entries for various processes, depending on the trace options configured for the product.

  • Logrec

    When an error occurs, the system records information about the error in the logrec data set or the logrec log stream. The information provides you with a history of all hardware failures, selected software errors, and selected system conditions.

  • Transaction XA Partner Log

    This log is used for recovery of XA resources. When an application accesses XA resources, the product stores information about the resource to enable XA transaction recovery. For instructions on how to use the Profile Management Tool or the zpmt command to configure the Transaction XA Partner Log see the "Customization variables: Stand-alone application server cell" topic in the installing your application serving environment section. For instructions on how to change the location of the Transaction XA Partner Log, see the transaction service settings information.

  • SDSF

    Use the SDSF DA panel to see how many application server address spaces are active, and observe at the CPU%, ECPU% and SIO rate. Use the "ENC" panel to see the enclaves running and what service classes they are running under.

  • RMF™

    See Using RMF for instructions on starting and using RMF to monitor your transactions.

  • MODIFY command

    See the getting help for the modify command example documentation for instructions on using the z/OS modify command to display information about the product servers or servants.

To find additional information about these tools, and about the process of diagnosing problems on z/OS, use the z/OS product library to access the following books:
  • z/OS MVS Diagnosis: Procedures, GA22-7587, which helps you diagnose problems in the MVS operating system, its subsystems, its components, and in applications running under the system.
  • z/OS MVS Diagnosis: Tools and Service Aids, GA22-7589, which provides detailed information about tools and service aids that can help you diagnose problems. This book contains a guide on how to select the appropriate tool or service aid for your purposes, and also provides an overview of all the tools and service aids available.

指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:17
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=ttrb_chsgtools
檔名:ttrb_chsgtools.html