Log and trace file descriptions
This reference information describes the location, syntax, and usage of log and trace files generated by the product.
You can also search for log and trace file descriptions by title or by using keywords.
次主題
A client program does not work
Adding log and trace settings to the batch environment
The batch environment uses the WebSphere® Application Server logging and tracing system.Administration and administrative console troubleshooting
Administrative audit messages in system logs
The product provides administrative audit messages in system logs that contain some audit information. The audit messages described in this topic are part of the standard product audit stream and do not provide administrative event auditing information such as who changed files.Administrative console - browser connection problems
This topic describes problems that you can have when logging into the administrative console from a browser.Administrative console does not start even though installation completes
This topic discusses problems that you can encounter when you attempt to access the console.Administrative problems with the wsadmin scripting tool
Use this information if you are having problems starting or using the wsadmin tool.APPC automation and recovery scenarios
This page contains scenarios and information on the automation and recovery of APPC.Application deployment problems
You might encounter problems when deploying, installing, or promoting applications. This topic suggests ways to resolve the problems.Application deployment troubleshooting tips
When you first test or run a deployed application, you might encounter problems.Application Server start or restart problems
If a server process does not start or starts with errors, the following topics might help you to diagnose the problem.Application startup errors
Use this information for troubleshooting problems that occur when starting an application.Application startup problems
When an application is not starting or starting with errors, the problem could be from one of various sources.Application uninstallation problems
When you try to uninstall an application or node, you might encounter problems. This topic suggests ways to resolve uninstallation problems.Audit support
This topic gives an overview of how to use audit support.Automation and recovery scenarios and guidelines
The following section provides information on how to monitor and recover WebSphere Application Server for z/OS® and the subsystems it uses.Bus-enabled web services troubleshooting tips
Use this set of specific tips to help you troubleshoot problems you experience with service integration bus-enabled web services.BusinessGridStatsCache
這個日誌檔說明商業網格統計資料快取。BusinessGridStatsCache log file
This log file describes the business batch statistics cache.Cannot restart the Deployment Manager monitoring policy
The Deployment Manager monitoring policy is permanently set to STOPPED and cannot be changed. Therefore, if the Deployment Manager fails it will never be restarted by WebSphere Application Server monitoring.CEEDUMPs in the job log
An error caught by LE or the Java™ runtime can result in the production of a CEEDUMP, which is written to a separate CEEDUMP specification in the job log.Change log and trace mode settings
Use this page to choose the mode your system uses for logging and tracing.Change state specification
Use this panel to add a Diagnostic Provider and its attributes to the specification for collecting state data.Choosing a Diagnostic Provider name
To ensure consistency when choosing Diagnostic Provider names to use with your components, you should consider the guidelines that follow.CICS automation and recovery scenarios
This article explains different scenarios for CICS® automation and recovery.Class loader viewer service settings
Use this page to configure the server to start the class loader viewer service when the server starts. The Class Loader Viewer helps you diagnose problems with class loaders.Class loader viewer settings
Use this page to examine the class loaders visible to a web module (.war file) or enterprise bean (.ejb file) in an installed enterprise application. This page helps you to determine which class loaders loaded files of a module and to diagnose problems with class loaders.Class loading exceptions
collector command - summary option
WebSphere Application Server products include an enhancement to the collector tool, known as the collector summary option.Collector tool output
Use the collector tool to gather and analyze output from WebSphere Application Server.Command-line tool problems
Troubleshoot a variety of problems relating to using command-line tools.Common Base Event content handler
Content handlers populate data into Common Base Events when the Common Base Event complete method is invoked. You can associate content handlers with Common Base Event templates, which provide default information to transfer into each Common Base Event.Common Base Event factory
Use event factories to create Common Base Events and complete event properties with associated content handlers.Common Base Event factory context
The event factory context provides a service to look up event factory homes. Retrieve the event factory context using a call to the EventFactoryContext.getInstance method.Common Base Event factory home
Event Factory homes provide Event Factory instantiation that is based on a unique factory name.Common Base Event structure
A Common Base Event is a common structure for an event. It defines common fields, the values that these fields can take, and the exact meanings of these values for an event.Common header information
Format and use header fields for problem determination events. These fields clarify and extend the information provided in the other documents.Component identification for source and reporter
The component identification fields in the Common Base Event are used to indicate which component in the system is experiencing the condition that is described by the event (the sourceComponentID) and which component emitted the event (the reporterComponentID).Configuration data
Use this panel to view the current configuration data for a Diagnostic Provider on a selected server or cluster. Not necessarily every piece of configuration data appears, but data that can be helpful in problem determination is shown.Configuration data quick link or server selection
Use this panel to select a Diagnostic Provider server for viewing run time configuration data.convertlog command
The convertlog command is used to convert the message IDs in log entries from the old standard to the new standard, or the new standard back to the old.CORBA minor codes
Applications that use CORBA services generate minor codes to indicate the underlying cause of a failure. These codes are written to the exception stack. Look for "minor code" in the exception stack to locate these exceptions.CTRACE to collect trace data for Java server applications
Applications that run in WebSphere Application Server for z/OS can use JRas to provide tracing support that is consistent with WebSphere tracing.DB2 automation and recovery scenarios
This article provides scenarios for automation and recovery of DB2® resources.Debugging Service details
Use this page to view and modify the settings used by the Debugging Service.DeploymentTargetStatsHistoricCache
這個日誌檔包含部署目標統計資料歷程快取的相關歷程資訊。Detailed state specification
Use this panel to view the attributes and descriptions of the Diagnostic Provider that you have selected.Diagnosing and fixing problems: Resources for learning
In addition to the information center, there are several Web-based resources for researching and resolving problems related to the WebSphere Application Server.Diagnostic Provider Extensible Markup Language
Some conventions to follow for Diagnostic Provider (DP) Extensible Markup Language (XML) declarations.Diagnostic Providers (selection)
Use this panel to select a Diagnostic Provider from the selected server or cluster.Diagnostic Provider XML example
Here is an example of the Diagnostic Provider Extensible Markup Language (XML).Diagnostic trace service settings
Use this page to configure diagnostic trace service settings.Dump control settings
Use these settings to manage the dump control configuration in WebSphere Application Server.Dump controls for IBM service
Use these controls to gather information that can be used by IBM® service.Enterprise application topology
Use this page to see where modules reside in a topology of enterprise applications. Knowing where a module resides helps you to determine which class loader loaded a module and to diagnose problems with class loaders.Error Dump and Cleanup interface
The Error Dump and Cleanup (BBORLEXT) interface exists to call WebSphere Application Server for z/OS in a recovery environment to allow it to request a dump and to clean up its resources.Error log stream record output
This article provides two samples of error log stream output and explains the various attributes they contain.Example: Adjusting the thread monitor to affect server hang detection
The hang detection policy affects how the application server responds to a thread that is not being processed correctly.Extended data
The Common Base Event provides several methods for including this additional data, including extending the Common Base Event schema or supplying one or more ExtendedDataElement elements within the Common Base Event, which is the preferred approach.FineGrainedPowerConsumptionStatsCache
這個日誌檔包含精細的電源和工作使用情況資料。 對於每個交易類別模組和伺服器實例,都會寫一則記錄。 這個動作會建立已透過隨需應變路由器 (ODR) 來遞送工作的每個中介軟體應用程式、模組、交易類別和伺服器實例的記錄。 另外還有其他欄位會保留關係資訊,例如,伺服器所屬的叢集、與叢集相關聯的節點群組,以及與交易類別相關聯的服務原則。Generate Common Base Event content with the default event factory
A default Common Base Event content handler populates Common Base Events with WebSphere Application Server runtime information. This content handler can also use a Common Base Event template to populate Common Base Events.Header/self-defining section
These tables describe the header/self-defining section of an SMF record.Hexadecimal conversion of Java error codes
Occasionally, Java will take an WebSphere Application Server for z/OS error code (C9C2xxxx in hexadecimal) and convert it to a very large negative number. If you get a very large negative number, try converting it back to hexadecimal to find the correct code.HPEL log configuration settings
Use this page to configure High Performance Extensible Logging (HPEL) log settings.HPEL logging and trace settings
Use this page to view and configure High Performance Extensible Logging (HPEL) logging and trace settings for the server.HPEL text log configuration settings
You can configure High Performance Extensible Logging (HPEL) settings for text log.HPEL trace configuration settings
Use this page to configure High Performance Extensible Logging (HPEL) trace settings.HTTP error, FRCA, and NCSA access log settings
Use this page to configure the global HTTP error log, and National Center for Supercomputing Applications (NCSA) access log settings for an HTTP inbound channel. If you are running the product on z/OS, you can also use this page to configure the global Fast Response Cache Accelerator (FRCA) log settings for an HTTP inbound channel. A FRCA log is a specialized form of a NCSA log and can only be created in a z/OS environment.IBM service call preparation
When you report a problem to IBM service, you will need to provide as much information as possible to help service personnel quickly resolve the problem.IBM service log settings
Use this page to configure the IBM service log, also known as the activity log.Implicitly set client information
If you track client information in your database, you can choose one of two ways to pass WebSphere Application Server client data on database connections.IMS automation and recovery scenarios
This article provides scenarios for IMS™ automation and recovery.Intelligent Management: application placement controller logs
You can use the log files to troubleshoot issues with the application placement controller, such as the placement of new instances.Intelligent Management: application placement controller logs
Use the log files to review the status of the application placement controller.Intelligent Management:效能日誌
您可以利用日誌檔來協助監視效能、記錄帳戶資訊及判斷問題。Internal tracing tips for WebSphere for z/OS
WebSphere Application Server traces can be extremely helpful in detecting and diagnosing problems.IPCS CTRACE subname query
If the trace data set is an SVC dump, the trace subname must also be specified. This subname is the aggregation of the address space's jobname with its ASID (address space identifier), in printable hexadecimal.IPCS VERBEXIT subcommand to display diagnostic data
The interactive problem control system (IPCS) is a tool that provides formatting and analysis support for dumps and traces produced by WebSphere Application Server for z/OS and the applications that it hosts.java.util.logging -- Java logging programming interface
The java.util.logging.Logger class provides a variety of methods with which data can be logged.Java dump and core collection
Use this page to generate various Java dumps and cores from within the administrative console.Java virtual machine (JVM) log settings
Use this page to view and modify the settings for the Java virtual machine (JVM) System.out and System.err logs.JDBC trace configuration
If your application displays JDBC-related exception messages, activate the JDBC trace service. The resulting log text can help you identify the problem.JRas extension classes
WebSphere Application Server provides a base set of implementation classes that are collectively referred to as the JRas extensions. Many of these classes provide the appropriate implementations of loggers, handlers, and formatters for use in a WebSphere Application Server environment.JRas Extensions
JRas extensions are the collection of implementation classes that support JRas integration into the WebSphere Application Server environment.JRas messages and trace event types
The basic JRas message and event types are not the same as those natively recognized by WebSphere Application Server, so the JRas types are mapped onto the types that are native to the runtime environment. You can control the way JRas message and trace events are processed using custom filters and message controls.JRas programming interfaces for logging (deprecated)
The JRas framework described in this task and its sub-tasks is deprecated. However, you can achieve similar results using Java logging.JRas resource bundles
You can create resource bundles in several ways. The best and easiest way is to create a properties file that supports a PropertiesResourceBundle resource bundle. This sample shows how to create such a properties file.JVM log interpretation
View the JVM log files to determine problems within application environments.Log and Trace extensions
The High Performance Extensible Logging (HPEL) capability in the application server provides a way for developers to add extension fields to log and trace records, and a corresponding way for you to filter log and trace records by extension value.Log and trace settings
Use this page to view and configure logging and trace settings for the server.Logger.properties file
Use the Logger.properties file to set logger attributes for your component.Logger.properties file for configuring logger settings
Use the Logger.properties file to set logger attributes for specific loggers.Logging Common Base Events in WebSphere Application Server
The following practices ensure consistent use of Common Base Events within your components, and between your components and WebSphere Application Server components.Log levels
Levels control which events are processed by Java logging. WebSphere Application Server controls the levels of all loggers in the system.Log level settings
Use this topic to configure and manage log level settings.Log output destinations and characteristics
Use these variables to control log output destinations and characteristics.Logstream size considerations
You might need to modify the size of the logstream record size if the application server is attempting to write messages that are too large. If a message is too large, you will receive an error message that will be written to the job log.LogViewer command-line tool
Use the LogViewer command to query the contents of the High Performance Extensible Logging (HPEL) log and trace repositories. You can also use the LogViewer command to view new log and trace repository entries as the server writes content to them.Log viewer settings
Use this page to view your High Performance Extensible Logging (HPEL) log, trace, System.out, and System.err content.Managing operator message routing
Use the product message routing capabilities to control server traffic flow.MessageConverter class
The com.ibm.websphere.logging.MessageConverter class provides a method to convert a message ID at the front of a String into either a new message ID or an old message ID. The direction of the conversion is controlled with the conversionType argument.Message data
All problem determination Common Base Events must provide human readable text that describes the specific reported event within the msg field of the Common Base Event.Message details
Use the Message Details panel of the administrative console to view detailed information about errors, warnings, and informational messages.Message location best practices
Use this information for configuring messaging locations.Multiserver environment errors
Use this information to troubleshoot problems with setting up multiserver environments.NodeStatsHistoricCache
這個日誌檔包含節點統計資料快取的相關歷程資訊。Object Request Broker communications trace
The Object Request Broker (ORB) communications trace, typically referred to as CommTrace, contains the sequence of General InterORB Protocol (GIOP) messages sent and received by the ORB when the application is running.osgiCfgInit script
The Equinox OSGi framework is used to manage class loading and relationships between server component bundles. In some cases, the cached bundle data, which is maintained on a per-profile basis and has a separate cache at the WAS_HOME level for installation-wide processes, can become out of sync with the actual binaries on the server. You can use the osgiCfgInit script to clear and recreate the OSGi cache.Performance diagnosis information
The following report options are listed here for information. IBM Service may request that you run one or more of these reports while assisting you with diagnosis. You do not need to collect this data unless it is requested by IBM Service.Process logs
WebSphere Application Server processes contain two output streams that are accessible to native code running in the process. These streams are the stdout and stderr streams. Native code, including Java virtual machines (JVM), might write data to these process streams. In addition, JVM provided System.out and System.err streams can be configured to write their data to these streams also.Process logs settings
Use this page to view or change settings for specifying the files to which standard out and standard error streams write.Product section
These tables describe the product section of an SMF record.RACF automation and recovery scenarios
This table provides scenarios for RACF® automation and recovery.Record environment and mapping
This page provides information on record environments and record mapping.Recovering with JTA XAResource managers
When a JTA XAResource manager is enlisted in a global transaction, it cannot express an interest in the z/OS Resource Recovery Services unit of recovery (UR) like an RRS resource manager can. Instead, the product transaction service will save information in its RRS interest indicating that a JTA Resource Manager was enlisted in the transaction.RRS automation and recovery scenarios
Use this table for RRS automation and recovery scenarios.Runtime events
Use the Runtime event pages of the administrative console to view the events published by application server classes.Sample Common Base Event instance
This XML document is an example of a Common Base Event instance that is generated by a WebSphere Application Server application.Sample Common Base Event template
The content handler uses template information to fill in blanks in the Common Base Event when the Common Base Event complete method is called.Sample JCL to display WebSphere for z/OS trace data
Use this sample JCL to display trace data for WebSphere Application Server for z/OS.Search settings
Use this page to search for information about class loaders visible to a web module (.war file) or enterprise bean (.ejb file) in an installed enterprise application. This page helps you diagnose problems with class loaders.Select a server to configure logging and tracing
Use this page to select the server for which you want to configure logging and trace settings.Server hangs during shutdown if it creates a Java core dump (Red Hat Linux)
When you run the stopServer.sh script on Red Hat Linux Advanced Server Version 2.1 with the latest operating system patches, it creates a Java core dump and hangs the terminal.ServerPowerConsumptionStatsCache
這個檔案是伺服器層次的 FineGrainedPowerConsumptionStatsCache 與某些其他伺服器資料的合併。ServerStatsCache
這個日誌檔說明伺服器統計資料快取。Service integration bus security: Troubleshooting tips
Use this set of specific tips to help you troubleshoot problems you experience when working with a secure service integration bus.Showlog commands for Common Base Events
The showlog command converts the service log from binary format into plain text.Situation information
The situation information is used to classify the condition that is reported by an event into a common set of situations.SMF record splitting
Since most of the WebSphere Application Server SMF records are used to describe variable-length data structures (for example, there might be hundreds of classes by container and hundreds of methods by class), the SMF records may be larger than the maximum record size supported by SMF (32KB). In this case, the logical records need to be split into several physical records.SMF record type 120: overview
Information resulting from the SMF data gathering process for WebSphere Application Server for z/OS is held in SMF record type 120.SMF record type 120 (78) - WebSphere Application Server performance statistics
WebSphere Application Server writes record type 120 to collect WebSphere Application Server performance statistics.SMF settings
Configure SMF records to collect job information to tune application server performance.SMF Subtype 1: Server activity record
The server activity SMF record is used to record activity that is running inside a WebSphereApplication Server for z/OS. This record can be used to perform basic charge-back accounting and to profile your applications to determine, in detail, what is happening inside the WebSphereApplication Server transaction server.SMF Subtype 10: Outbound Request record
The purpose of the Outbound Request SMF record is to record requests that go outbound. This record is produced whenever an optimized local adapter request goes outbound.SMF Subtype 3: Server interval record
The purpose of the server interval SMF record is to record activity that is running inside a WebSphereApplication Server for z/OS. This record is produced at regular intervals and is an aggregate of the work that ran inside the server instance during the interval.SMF Subtype 5: J2EE container activity record (Version 2)
The purpose of the J2EE container activity SMF record is to record activity within a J2EE container that is located inside the WebSphereApplication Server transaction server.SMF Subtype 6: J2EE container interval record (Version 2)
The purpose of the J2EE container interval SMF record is to record activity within a J2EE container that is located inside the WebSphereApplication Server transaction server.SMF Subtype 7: WebContainer activity record (Version 2)
The purpose of the WebContainer activity SMF record is to record activity within a WebContainer running inside a WebSphereApplication Server for z/OStransaction server.SMF Subtype 8: WebContainer interval record (Version 2)
The purpose of the WebContainer interval SMF record is to record activity within a WebContainer running inside a WebSphereApplication Server for z/OStransaction server.SMF Subtype 9: Request Activity record
The purpose of the Request Activity SMF record is to record activity that is running inside the product. This record is produced whenever a server receives a request.State data
Use this panel to view the current state data for a Diagnostic Provider on a selected server or cluster.State Data Quick Link or Server Selection
Use this panel to select a server or cluster to either view collected state data, or to configure state data to collect for a Diagnostic Provider.StrfTime 格式轉換
使用 %{format}t 日誌參數時所用的格式是以非延伸的 BSD strftime(3) 時間轉換函數為基礎。 下表列出具體支援的參數及輸出範例。SVC dumps
A SVC dump is a core dump initiated by the operating system generally when a programming exception occurs. SVC dump processing stores data in dump data sets that you pre-allocate, or that the system allocates automatically as needed.System performance when logging messages and trace data
Using message logging and trace data can affect system performance depending on your system configuration.TCModuleInstanceStatsCache
這個日誌檔說明交易類別模組實例快取。TCModuleStatsCache
這個日誌檔包含交易類別模組快取的相關資訊。TCP/IP automation and recovery scenarios
This table provides automation and recovery scenarios for TCP/IP configurations.Test result details
Use this panel to see additional attributes for the selected test result.Test Results
Use this panel to see the results from the server or cluster members for the selected test.Test selection
Use this panel to select one of the tests that are available for the chosen Diagnostic Provider on the chosen server or cluster.Tests Quick Link or Server Selection
Use this panel to select a Diagnostic Provider server for diagnostic tests.TierStatsCache
這個日誌檔說明層級統計資料快取。Timeout condition resolutions
This topic gives an overview of how to resolve timeout conditions.Timeout conditions: analyzing diagnostic data
The following guidelines provide instructions for finding diagnostic data in an SVC dump that can help you determine what timeout condition occurred.Timeout conditions - possible causes and fixes
This file lists common timer variables and tools for monitoring these timeout conditionsTimeout values: guidelines for altering timeout values
This file lists common timer variables and tools for monitoring these timeout conditionsTimer overview
Timers define a limit to the amount of time that is required for a specific operation to complete. The type of operation a timer controls determines when the time period, that is set for that timer, starts to elapse.Tivoli Access Manager loggers
The Java Authorization Contract for Containers (JACC) provider for Tivoli® Access Manager uses the JLog logging framework as does the Java runtime environment for Tivoli Access Manager. You can enable tracing and messaging selectively for specific JACC providers for Tivoli Access Manager components.Trace control settings
The following trace options allow you to capture the information needed to detect problems.Trace controls for IBM Support
Use these settings to view or modify your trace settings.Trace log stream record output
View an example of the trace log stream output, with an explanation of the various attributes it contains.Triplets
You can use triplets to build self-describing SMF records that contain various types of data sections and a varying number of each of these sections.Types of configuration variables
You can configure a variety of configuration variables to control the behavior of WebSphere Application Server for z/OS.UNIX System Services automation and recovery scenarios
This table provides automation and recovery scenarios for using UNIX System Services.Web resource is not displayed
Use this information to troubleshoot problems that occur when attempting to display a resource in a browser.Web server (servlet) automation and recovery scenarios
This table provides scenarios for web server (or servlet) automation and recovery.Web 伺服器日誌檔
請利用這個頁面來檢視 Web 伺服器的日誌檔。Web server plug-in troubleshooting tips
The following topics might help you diagnose problems with the web server plug-ins.Web services gateway troubleshooting tips
Use this set of specific tips to help you troubleshoot problems you experience when using the web services gateway.WebSphere Application Server for z/OS (Daemon) automation and recovery scenarios
This article provides some scenarios for automation and recovery of WebSphere Application Server for z/OS.WLM automation and recovery scenarios
This table provides scenarios for automation and recovery of WLM enabled systems.Workload is not getting distributed
This information might help you diagnose the trouble if you are having a workload distribution problem.Workload management component troubleshooting tips
If the workload management component is not properly distributing the workload across servers in multi-node configuration, use the following options to isolate the problem.z/OS display command
Use either the WebSphere Application Server administrative console or the z/OS MVS™ console to accomplish many operations tasks related to WebSphere Application Server for z/OS servers. Entering the z/OS display or modify commands through the MVS console can provide information or perform tasks that are useful for diagnosing problems.


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=welc_ref_trb_file
檔名:welc_ref_trb_file.html