This chapter describes where the Application Performance Analyzer Listener messages are logged and lists the message IDs and descriptions. The Application Performance Analyzer Listener started task logs informational, error and diagnostic messages to various JES destinations. The contents of these output files are described here by their DDnames:
All critical messages are displayed in JES Message Log. If the started task fails to start successfully, look in JES Message Log for messages reporting the failure.
Any commands processed by the started task (external or internal) are logged to this file. The command text is displayed here, as well any message associated with the command.
Each of these represents a single subtask attached by the Application Performance Analyzer Listener started task and contains messages logged by that task. These are primarily informational messages and during normal operations you need not be concerned with the contents of these files. They can be useful during problem diagnosis.
There is one LISTn000 DD per active Listener subtask in the started task, where n=1 to 9. This contains messages logged by the subtask. The messages are primarily informational and during normal operation you need not be concerned with the contents of the files. They can be useful during problem diagnosis.
There is one LSRVnxxx DD per active client connection connected to LISTn000, where xxx=001 to 999. These contain messages logged for each session. The messages are primarily informational and during normal operation you need not be concerned with the contents of the files. They can be useful during problem diagnosis.
Messages are sorted in alphanumeric order.
During initialization, CAZL0001 was unable to establish an ESTAE exit routine. The return code and reason code from the ESTAEX macro are reported as ’return_code’x and ’reason_code’x.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
Application Performance Analyzer Listener initiated its shutdown process.
None.
None.
This message is reported when Application Performance Analyzer Listener has completed its shutdown process and is about to terminate.
None.
None.
During the initialization of the main task, the version and release numbers are reported as vv.
Application Performance Analyzer Listener continues initialization.
None.
Application Performance Analyzer Listener has detected that it is executing on a level of the operating system that Application Performance Analyzer does not support. Refer to message CAZ0007D for more information about operating system level.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Program Directory for information about the product levels supported.
Application Performance Analyzer Listener issued a Global Name/Token services request (to IEANTRT) that failed. This could indicate a system environmental problem.
Application Performance Analyzer Listener terminates.
Examine the reported return code return_code and analyze the reason why IENTRT might have failed.
Application Performance Analyzer Listener issued a Global Name/Token services request (to IEANTRT) that failed. This could indicate a system environmental problem.
Application Performance Analyzer Listener terminates.
Examine the reported return code return_code and analyze the reason why IENTRT might have failed.
This is a general information message used for diagnostic purposes by product support. The text of the message varies depending on the diagnostic data to be presented.
None.
None.
One of two problems might have occurred:
Application Performance Analyzer Listener terminates.
If the error was caused by option 1 above, then refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings. If the error was caused by option 2 above, then perform the following:
PABENTReset=YES
The maximum number of Application Performance Analyzer or Application Performance Analyzer Listener started tasks is already executing. You must stop one or more of these instances before it is possible to start a new one.
Application Performance Analyzer Listener terminates.
Stop an instance of Application Performance Analyzer or Application Performance Analyzer Listener that is currently not in use and try to restart the failed instance.
During initialization, Application Performance Analyzer Listener established access to an existing Application Performance Analyzer Anchor Block (PAB), but the length of this existing PAB was not valid. This is an internal error.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
During initialization, another started task instance of Application Performance Analyzer Listener was executing and was using the same high level qualifier. high_level_qualifier indicates the HLQ and task_ID is the ID of the other Application Performance Analyzer Listener started task.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
During initialization of the main task, this message reports the high level qualifier (high_level_qualifier) used for any new data sets created by this instance of Application Performance Analyzer Listener.
Application Performance Analyzer Listener continues initialization.
None.
Application Performance Analyzer Listener completed its initialization. The system is now ready to process sampling.
None.
None.
This message indicates that an operator has entered the STOP command requesting the Application Performance Analyzer Listener started task to shut down.
Application Performance Analyzer Listener terminates.
None.
The subtask subtask-name has started and is in the process of initializing.
Application Performance Analyzer Listener continues initialization.
None.
The subtask subtask-name has completed initialization and is now ready for work.
Application Performance Analyzer Listener continues initialization.
None.
A dynamic allocation error occurred while attempting to allocate a log SYSOUT data set specified by ddname. error_code, information_code, and reason_code represent the dynamic allocation error code, information code and SMS reason code, respectively.
None.
Refer to theMVS™ Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and, if necessary, restart Application Performance Analyzer Listener.
A dynamic allocation error occurred while attempting to allocate a new log file specified by dsn. error_code, information_code, and reason_code represent the dynamic allocation error code, information code and SMS reason code, respectively.
Application Performance Analyzer Listener terminates.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and, if necessary, restart Application Performance Analyzer Listener.
This is an information message indicating that the logger subtask has allocated a new log file with the data set name specified by dsn.
None.
None.
A DEVTYPE error occurred while attempting to determine the device type for the log data set allocated to the DDname specified by ddname. return_code and reason_code represent the DEVTYPE return code and reason code, respectively.
Application Performance Analyzer Listener terminates.
Refer to the DFSMSdfp Advanced Services for information about the above error codes. Correct the problem and then restart Application Performance Analyzer.
The subtask subtask-name has started its shutdown process.
None.
None.
The subtask subtask-name has completed its shutdown process and is about to terminate.
None.
None.
The command processor subtask was not able to open the data set or SYSOUT allocated to the COMMANDS ddname. Probable cause: the COMMANDS DD statement is missing from the Application Performance Analyzer Listener JCL.
Application Performance Analyzer Listener terminates.
Add the appropriate COMMANDS DD statement to the Application Performance Analyzer Listener JCL.
This is an information message indicating the number of TCP/IP instances that are defined on this system. The Application Performance Analyzer Listener attempts to establish a connection with each active TCP/IP instance.
None.
None.
INITAPI indicated that it was not able load the required API module.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
INITAPI failed to due to errors.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
GETIBMOPT failed to due to errors.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
The Application Performance Analyzer Listener was unable to find any defined instances of TCP/IP.
Application Performance Analyzer Listener terminates.
Ensure at least one instance of TCP/IP is running prior to starting Application Performance Analyzer Listener.
The Application Performance Analyzer Listener has attached a subtask by the name of: subtask-name, to handle communications with the instance of TCP/IP identified by the procedure name of: proc-name, and by the port number: port-number.
None.
None.
The Application Performance Analyzer Listener subtask has determined that TCP/IP instance identified by proc-name is currently not active. The subtask sleeps until that instance of TCP/IP becomes active.
None.
None.
The Application Performance Analyzer Listener subtask: subtask-name detected an error in the INITAPI call. The subtask terminates.
None.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
The Application Performance Analyzer Listener subtask: subtask-name was not able load the required API module. The subtask terminates.
None.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
This is an information message indicating that an Application Performance Analyzer listener subtask has successfully established communications with TCP/IP Stack: ip-stackname, on IP address: ip-addr, Port: port-num. The subtask is now listening for connections.
None.
None.
A TCP/IP error was detected while processing function: function-name. errno contains the error number returned by the function. socket and port describe where the error happened. The Application Performance Analyzer Listener subtask: subtask-name terminates.
Communications to the IP address assigned to the subtask will no longer be possible.
Refer to the z/OS Communications Server IP Sockets Application Programming Interface Guide and Referencefor an explanation of the errno returned by the failing function. Correct the problem and then restart the started task.
A TCP/IP error was detected while processing function: function-name. errno contains the error number returned by the function. socket and port describe where the error happened.
None.
Refer to the z/OS Communications Server IP Sockets Application Programming Interface Guide and Reference for an explanation of the errno returned by the failing function to correct the problem.
A TCP/IP error was detected while processing function: function-name. errno contains the error number returned by the function. socket and ip-address describe where the error happened. The Application Performance Analyzer Client Server subtask: subtask-name terminates.
Communications to the IP address assigned to the subtask will no longer be possible.
Refer to the z/OS Communications Server IP Sockets Application Programming Interface Guide and Reference for an explanation of the errno returned by the failing function to correct the problem.
The Application Performance Analyzer Client Server subtask with socket: lsocket has successfully taken the client socket: csocketfrom Application Performance Analyzer listener subtask. The client IP address is: cip-address, and the host IP address is: hip-address.
None.
None.
The Application Performance Analyzer Client Server subtask is closing communications with the client socket: csocket at IP address: ip-address.
None.
None.
The Application Performance Analyzer Client Server subtask is idle a waiting for work.
None.
None.
The application known by the internal name: appl-name has terminated due to a lost connection with the client. The connection could have been lost due a communications error or the client simply closing the connection.
None.
None.
The application known by the internal name: appl-name has abended with the abend completion and reason codes given by: completion-code, reason-code.
The application terminates with a dump.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
The application known by the internal name: appl-name has started and is now communicating with the client. The application subtask tcb address is given by: tcb-address.
None.
None.
The Application Performance Analyzer Client Server subtask has successfully recovered from an abend. The subtask enters an idle state and waits for work.
None.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
The Application Performance Analyzer Client Server subtask as successfully handed off communications to the subtask named by: appl-name.
None.
None.
The application subtask named by: appl-name has terminated successfully.
None.
None.
The application subtask named by: appl-name has terminated conversation with the client. This is due to the client failing to communicate with the application subtask for a period of time longer than the session time out value described by the configuration parameter: SessionTimeOut of the CONFIG BASIC section.
None.
Review the problem with the user and increase the SessionTimeOut if necessary.
A client with socket: csocket and IP adderss: ip-address attempted to connect to the Application Performance Analyzer Listener subtask. The listener failed this request because the Listener subtask was already servicing the maximum number of concurrent client connections allowed.
The connection is denied.
Use the DISPLAY SERVERS command to list the status of each client connection. Then use the LSTOP command to a server if required.
User attempted a command on one or more Application Performance Analyzer Client Server subtasks. No active servers were found matching the input from the user.
The command is not processed.
Check the command parameters for accuracy and retry if necessary.
User attempted to alter application tracing in one or more Application Performance Analyzer Client Server subtasks. No active Listener subtasks were found matching the input from the user.
The command is not processed.
Check the command parameters for accuracy and retry if necessary.
User entered a command specifying an invalid number to identify the target Application Performance Analyzer Listener subtask. The number must be in the range of 1 to 9.
The command is not processed.
Check the command parameters for accuracy and retry if necessary.
An Application Performance Analyzer Client Server subtask was shutdown by the operator by using the LTOP command.
None.
None.
The program identified by: program-name has abended with completion code: cccc.
None.
Check the system log for abend and error messages. Also check for a dump. Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
The application subtask named by: appl-name is terminating because the Application Performance Analyzer Listener Client Server subtask is shutting down. This might be due to a normal shutdown request for the started task or an abend condition in the server subtask.
None.
Check the system log for abend. Also check for a dump. If present, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
The application subtask named by: appl-name failed and is terminating due to errors.
None.
Report the problem to product support.
The Application Performance Analyzer Client Server subtask named: server failed to complete the START command for client at IP Address: ip-address. The reason for the failure follows in messages: CAZL077I and CAZL078I. This error should never happen, but if it does, it might indicate that the Application Performance Analyzer Listener is being probed for a possible attack. It might also indicate an incompatible version of the workstation code is attempting to communicate with this listener.
None.
Ensure that the workstation code is compatible with the Application Performance Analyzer Listener. If they are, note the IP address in the message and attempt to validate it.
This message follows message: CAZL076E. It displays the command string that caused the error.
None.
None.
This message follows message: CAZL076E. It displays the reason that caused the error.
None.
None.
The Application Performance Analyzer Listener attempted to attached a subtask by the name of: subtask-name, to handle communications with the instance of TCP/IP identified by the procedure name of: proc-name. The subtask failed to initialize and has come down.
None.
Refer to error messages produced in the SYSOUT dataset with a DDName of: subtask-name for more information.
The Application Performance Analyzer Listener started task is currently unable to connect to any TCP/IP instance. All listener subtasks have been brought down and the started task is in an idle state. This typically occurs when all TCP/IP instances are down.
None.
Start TCP/IP and then issue the START LISTENER command to start the listener subtask for the TCP/IP instance.
The command described by command-name completed successfully.
None.
None.
The command described by command-name was specified without the mandatory keyword keyword.
The command is not processed.
Retry the command with the required keyword.
The STOP LISTENER command was issued for a listener subtask that was managing active server subtasks, for example, server subtasks that are connected to Application Performance Analyzer GUI clients.
The command is not processed.
Either wait for all clients to terminate before reissuing the STOP command or terminate all client connections for this listener by reissuing the STOP command specifying the FORCE=YES operand.
The STOP SERVER command was issued for a server subtask that is currently connected to an Application Performance Analyzer GUI client.
The command is not processed.
Either wait for the client to terminate before reissuing the STOP command, or reissue the STOP command specifying the FORCE=YES operand.
A command was issued with a keyword: aaaa that contained a value that is invalid for the keyword.
None.
Correct the error and resubmit the command.
The Application Performance Analyzer Listener started task could not start any Listener subtasks since no valid TCP/IP stacks were identified. The GUI will not be able to connect. There are several possible reasons for this warning:
None.
Depending on the situation:
The user attempted to start another Listener subtask, but the Application Performance Analyzer Listener started is currently running the maximum number of supported Listener subtasks.
None.
None.
The stack named: aaaaaaaa is not defined as a valid TCP/IP currently active on the system. The GUI will not be able to connect to the specified stack.
None.
Verify that the values of CONFIG BASIC keyword pair: ListenTo= and Stack= is correct. If not, correct the values and recycle the Application Performance Analyzer Listener started task.
This message indicates there is an internal error detected while attempting to process a normal error message.
None.
Report the problem to product support.
This message indicates there is an internal error detected while attempting to process a normal error message.
None.
Report the problem to product support.
The configuration file OPEN failed. This file is allocated (in JCL) to DDNAME=CONFIG. This error occurs if the CONFIG DD statement is missing or the file is not a sequential FB LRECL=80 data set.
Application Performance Analyzer Listener terminates.
Correct the CONFIG DD statement or the configuration file.
This message indicates the record number record_number of a CONFIG statement in the CONFIG file. The object specified on this CONFIG statement is invalid. This error is also accompanied by a CAZL911E message.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
This message indicates that an error was encountered while parsing a CONFIG statement. The record number indicates the CONFIG file record where the CONFIG statement begins. The actual error might have been detected on a continuation record. One or more error messages are issued by the parser in the form AJTnnnnE and CAZLnnnI, which provide information about the error.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
This message provides details of error messages about syntax errors. variable text contains the portion of a statement or command expression that is in error.
Command is terminated.
None.
This message contains a single asterisk to point to where the syntax error described by message CAZL905I occurred.
Command is terminated.
None.
The record number indicates a record in the CONFIG file at which a CONFIG statement begins. This indicates that the CONFIG statement was processed successfully.
Application Performance Analyzer Listener continues initialization.
None.
The record number indicates a CONFIG file record in which an unrecognizable statement was encountered. A statement with the following syntax was expected: CONFIG OPER ...
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
The record number indicates a CONFIG file record at which a CONFIG statement begins. End of file on the CONFIG file was encountered before the end of the CONFIG statement. This is probably caused by a missing semicolon delimiter, which should be displayed at the end of the expression.
Application Performance Analyzer Listener terminates.
Correct the error in the CONFIG file and restart the job.
This indicates that all statements in the CONFIG file were processed successfully.
Application Performance Analyzer Listener continues initialization.
None.
Errors were encountered in CONFIG statements in the CONFIG file. Details of the error(s) follow in separate messages.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
This is an internal error and can occur only if certain internal templates are syntactically invalid. This message accompanies a CAZL913E message and indicates the CONFIG object (object_name) that was being processed when the error occurred.
Application Performance Analyzer Listener terminates.
Report the problem to product support.
This is an internal error and can occur only if certain internal templates are syntactically invalid. This error should also be accompanied by an AJTnnnn message providing additional details as well as a CAZL912E message.
Application Performance Analyzer Listener terminates.
Report the problem to product support.
This is an internal error and can occur only if certain internal templates are syntactically invalid. This message accompanies a CAZL915E message and indicates the CONFIG object (object_name) that was being processed when the error occurred.
Application Performance Analyzer Listener terminates.
Report the problem to product support.
This is an internal error and can occur only if certain internal templates are syntactically invalid. This error should also be accompanied by an AJTnnnn message.
Application Performance Analyzer Listener terminates.
Report the problem to product support.
A value for the CONFIG object named by object_name contained a keyword name by: keyword that specified an invalid value. If the keyword supports multiple positional parameters, then the numeric position is specified by value. This message might optionally display the invalid_value.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
LogHLQ does not conform to DSN standards.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
The value specified for the UNIT keyword in the CONFIG BASIC object is not defined to the system.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
An EDTINFO error occurred validating the CONFIG BASIC UNIT value.
Application Performance Analyzer Listener terminates.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find a possible resolution to this problem.
The dynamic allocation error occurred while attempting to allocate the CONFIGSO SYSOUT data set. error_code, information_code and reason_code represent the hexidecimal dynamic allocation error code, information code and SMS reason code, respectively.
None.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes.
The CONFIGSO SYSOUT data set could not be opened due to errors.
None.
Refer to the JOB log for accompanying error messages that describe the reason for open failure.
During initialization, module module-name could not be loaded.
Application Performance Analyzer Listener terminates.
This is probably caused by an incorrect library concatenation in STEPLIB. Correct the JCL and resubmit.
CAZL0001 was executed in TSO foreground.
Application Performance Analyzer Listener terminates.
Application Performance Analyzer must be run in a batch region or started task.
CAZL0001 terminated because it was not APF authorized.
Application Performance Analyzer Listener terminates.
Verify that the product load library is APF authorized and that no unauthorized libraries are included in the STEPLIB concatenation. Verify the AC=1 attribute for the CAZL0001 load module.
[ Top of Page | Previous Page | Next Page | Contents ]