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.
Subtópicos
A client program does not work
Incluindo Configurações de Log e Rastreio para o Ambiente de Lote
O ambiente em lote usa a criação de log e o sistema de rastreio do WebSphere® Application Server.Administration and administrative console troubleshooting
Mensagens de Auditoria Administrativa em Logs do Sistema
O produto fornece mensagens de auditoria administrativa em logs do sistema que contêm algumas informações de auditoria. As mensagens de auditoria descritas nesse tópico são parte do fluxo de auditoria do produto padrão e não fornecem informações de auditoria de evento administrativo como quem alterou arquivos.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.Dicas de Resolução de Problemas de Implementação do Aplicativo
Ao testar ou executar pela primeira vez um aplicativo implementado, você pode encontrar problemas.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.Problemas de Inicialização do Aplicativo
Quando um aplicativo não iniciar ou iniciar com erros, o problema pode provir de diversas origens.Application uninstallation problems
When you try to uninstall an application or node, you might encounter problems. This topic suggests ways to resolve uninstallation problems.Suporte à Auditoria
Esse tópico fornece uma visão geral de como utilizar o suporte para auditoria.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
This log file describes the business grid statistics cache.BusinessGridStatsCache log file
This log file describes the business lote 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.Alterar Configurações do Modo de Log e de Rastreio
Use esta página para escolher o modo que seu sistema usa para criação de log e rastreio.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.Configurações do Serviço de Visualizador do Carregador de Classes
Utilize essa página para configurar o servidor para iniciar o serviço de visualizador do carregador de classes quando o servidor for iniciado. O Visualizador do Carregador de Classes ajuda a diagnosticar problemas com carregadores de classes.Configurações do Class Loader Viewer
Use esta página para examinar os carregadores de classes visíveis para um módulo da Web (arquivo .war) ou enterprise bean (módulo .ejb) em um aplicativo corporativo instalado. Esta página o ajuda a determinar quais carregadores de classes carregaram arquivos de um módulo e a diagnosticar problemas com os carregadores de classes.Exceções de Carregamento de Classe
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).Dados de Configuração
Utilize esse painel para visualizar os dados de configuração atuais para um Fornecedor de Diagnósticos em um servidor ou cluster selecionado. Não aparece necessariamente cada dado de configuração, mas aparecem os dados que podem ser úteis na determinação do problema.Seleção de Servidor ou Link Rápido de Dados de Configuração
Utilize esse painel para selecionar um servidor Fornecedor de Diagnóstico para visualizar dados de configuração do tempo de execução.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.Códigos Secundários CORBA
Os aplicativos que utilizam serviços CORBA geram códigos menores para indicar a causa subjacente de uma falha. Esses códigos são gravados na pilha de exceção. Procure "código secundário" na pilha de exceções para localizar essas exceções.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.Detalhes do Serviço de Depuração
Utilize essa página para visualizar e modificar as definições utilizadas pelo Serviço de Depuração.DeploymentTargetStatsHistoricCache
This log file contains historic information on the deployment target statistics historic cache.Detailed state specification
Use this panel to view the attributes and descriptions of the Diagnostic Provider that you have selected.Diagnosticando e Corrigindo Problemas: Recursos para Aprendizagem
Além do centro de informações, há vários recursos baseados na Web para pesquisar e resolver problemas relacionados ao WebSphere Application Server.Diagnostic Provider Extensible Markup Language
Some conventions to follow for Diagnostic Provider (DP) Extensible Markup Language (XML) declarations.Fornecedores de Diagnósticos (Seleção)
Utilize esse painel para selecionar um Fornecedor de Diagnósticos no servidor ou cluster selecionado.Diagnostic Provider XML example
Here is an example of the Diagnostic Provider Extensible Markup Language (XML).Definições de Diagnóstico do Serviço de Rastreio
Utilize essa página para configurar definições do serviço de rastreio de diagnóstico.Dump control settings
Use these settings to manage the dump control configuration in WebSphere Application Server.Controles de Dump para o Serviço IBM
Utilize esses controles para reunir informações que possam ser utilizadas pelo serviço IBM®.Topologia do Aplicativo Corporativo
Utilize esta página para visualizar onde os módulos residem em uma topologia de aplicativos corporativos. Saber onde um módulo reside o ajuda a determinar qual carregador de classes carregou um módulo e a diagnosticar problemas com os carregadores de classes.Interface Error Dump and Cleanup
A interface Error Dump and Cleanup (BBORLEXT) existe para chamar o WebSphere Application Server para z/OS em um ambiente de recuperação para permitir que ele solicite um dump e para limpar seus recursos.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
This log file contains fine grained power and work consumption data. A record is written for every transaction class module and server instance. This action creates a record for every middleware application, module, transaction class, and server instance that has had work routed through an on demand router (ODR). Additional fields exist that hold relationship information such as the cluster to which the server belongs, the node group with which the cluster is associated, and the service policy with which the transaction class is associated.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.Definições de Configuração de Log de HPEL
Use esta página para configurar as definições de log de High Performance Extensible Logging (HPEL).Configurações de Log e Rastreio de HPEL
Use esta página para visualizar e configurar as definições de log e rastreio de High Performance Extensible Logging (HPEL) para o servidor.Definições de Configuração do Log de Texto de HPEL
Use esta página para configurar as definições de High Performance Extensible Logging (HPEL) para o log de texto.Definições de Configuração de Rastreio de HPEL
Use esta página para configurar as definições de rastreio de High Performance Extensible Logging (HPEL).Configurações dos Logs de Erros HTTP, de FRCA e de Acesso NCSA
Utilize essa página para configurar as definições globais do log de erros HTTP e do log de acesso NCSA (Center for Supercomputing Applications) para um canal de entrada HTTP. Se você estiver executando o produto no z/OS, também poderá utilizar essa página para configurar as definições globais do log do FRCA (Fast Response Cache Accelerator) para um canal de entrada HTTP. Um log do FRCA é um formulário especializado de um log do NCSA e somente pode ser criado em um ambiente z/OS.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.Configurações de Log de Serviço IBM
Use esta página para configurar o log de serviço IBM, também conhecido como log de atividade.Definir Informações do Cliente Implicitamente
Se você rastrear informações no banco de dados, poderá escolher uma de duas maneiras de transmitir os dados do cliente do WebSphere Application Server nas conexões com o banco de dados.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: performance logs
You can use log files to help with performance monitoring, accounting and problem determination.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.Coleção de Dumps e Núcleos Java
Use esta página para gerar vários dumps e núcleos Java a partir do console administrativo.Configurações de Log da JVM (Java Virtual Machine)
Utilize essa página para visualizar e modificar as configurações dos logs System.out e System.err da JVM (Java Virtual Machine).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.Configurações de Registro e Rastreio
Utilize essa página para visualizar e configurar as definições de registro e rastreio para o servidor.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.Níveis de Log
Os níveis controlam quais eventos são processados pela criação de log Java. O WebSphere Application Server controla os níveis de todos os criadores de log no sistema.Definições de Nível do Registro
Utilize este tópico para configurar e gerenciar configurações no nível do registro.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.Ferramenta de Linha de Comandos LogViewer
Use o comando LogViewer para consultar o conteúdo dos repositórios de log e rastreio High Performance Extensible Logging (HPEL). Também é possível usar o comando LogViewer para visualizar novas entradas do repositório de log e rastreio conforme o servidor grava conteúdo neles.Configurações do Visualizador de Log
Use esta página para visualizar o conteúdo do log, do rastreio, de System.out e de System.err de High Performance Extensible Logging (HPEL).Gerenciando o Roteamento de Mensagem do Operador
Utilize os recursos de roteamento de mensagens do produto para controlar o fluxo de tráfego do servidor.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.Detalhes da Mensagem
Utilize o painel Detalhes da Mensagem do console administrativo para visualizar as informações detalhadas sobre erros, avisos e mensagens informativas.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
Este arquivo de registro contém informações de histórico sobre o cache de estatísticas do nó.Rastreio de Comunicações do Object Request Broker
O rastreio de comunicações do ORB (Object Request Broker), geralmente referido como CommTrace, contém a sequência de mensagens GIOP (General InterORB Protocol) enviadas e recebidas pelo ORB quando o aplicativo está em execução.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.Logs do processo
Os processos do WebSphere Application Server contêm dois fluxos de saída que estão acessíveis para código nativo em execução no processo. Esses fluxos são stdout e stderr. O código nativo, incluindo as JVMs (Java virtual machines), podem gravar dados nesses fluxos de processo. Além disso, os fluxos System.out e System.err fornecidos pela JVM também podem ser configurados para gravar seus dados nesses fluxos.Definições de logs de processos
Utilize esta página para exibir ou alterar definições para especificar os arquivos nos quais são gravados os fluxos de saída padrão e de erro padrão.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.Recuperando com Gerenciadores JTA XAResource
Quando um gerenciador JTA XAResource é registrado em uma transação global, ele não pode expressar interesse no z/OS Resource Recovery Services UR (Unit of Recovery) como pode um gerenciador de recursos RRS. Em vez disso, o serviço de transações do produto salvará informações no interesse de seu RRS, indicando que um Gerenciador de Recursos JTA foi registrado na transação.RRS automation and recovery scenarios
Use this table for RRS automation and recovery scenarios.Eventos do Tempo de Execução
Utilize as páginas Evento do Tempo de Execução do console administrativo para visualizar os eventos publicados pelas classes do servidor de aplicativos.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.Configurações de Procura
Use esta página para procurar por informações sobre os carregadores de classes visíveis para um módulo da Web (arquivo .war) ou enterprise bean (arquivo .ejb) em um aplicativo corporativo instalado. Esta página o ajuda a diagnosticar problemas com os carregadores de classes.Selecione um servidor para configuração de registro e rastreio:
Utilize essa página para selecionar o servidor para o qual você deseja configurar as definições de registro e de rastreio.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
This file is a consolidation of the FineGrainedPowerConsumptionStatsCache at the server level with some additional server data.ServerStatsCache
This log file describes the server statistics cache.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.Link Rápido de Dados de Estado ou Seleção de Servidor
Utilize esse painel para selecionar um servidor ou um cluster para visualizar dados de estado coletados ou para configurar dados de estado para coletar para um Fornecedor de Diagnóstico.StrfTime format conversions
The format used when using the %{format}t log parameter is based on the non-extended BSD strftime(3) time conversion functions. The parameters that are specifically supported, and sample output, are listed in the following table.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
This log file describes the transaction class module instance cache.TCModuleStatsCache
This log file contains information about the transaction class module cache.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.Seleção de Servidor ou Link Rápido de Testes
Utilize esse painel para selecionar um servidor do Fornecedor de Diagnóstico para testes de diagnóstico.TierStatsCache
This log file describes the tier statistics cache.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.Configurações de Controle do Rastreio
As opções de rastreio a seguir permitem capturar as informações necessárias para detectar problemas.Controles de Rastreio para o Suporte IBM
Utilize estas configurações para visualizar ou modificar suas definições de rastreio.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.Arquivo de Log do Servidor da Web
Utilize essa página para visualizar o arquivo de log de seu servidor da Web.Web server plug-in troubleshooting tips
The following topics might help you diagnose problems with the web server plug-ins.Dicas de Resolução de Problemas do Gateway de Serviços da Web
Este conjunto de dicas específicas para ajudá-lo a resolver problemas encontrados ao usar o gateway de serviços da web.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.A Carga de Trabalho Não Está Sendo Distribuída
Estas informações podem ser úteis para diagnosticar o problema se estiver tendo um problema de distribuição de cargas de trabalho.Dicas de resolução de problemas do componente de gerenciamento de carga de trabalho
Se o componente de gerenciamento de carga de trabalho não estiver distribuindo a carga de trabalho corretamente pelos servidores na configuração com vários nós, utilize as opções a seguir para isolar o problema.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
Nome do arquivo: welc_ref_trb_file.html