This chapter describes where Application Performance Analyzer for z/OS messages are logged, and lists the message IDs and descriptions.
The Application Performance Analyzer for z/OS started task logs informational, error and diagnostic messages to various JES destinations The contents of these output files are described here by their ddnames:
REQ#request_number
DATWrequest_number
ESDErequest_number
HVXTrequest_number
Where request_number represents
the sampling request number. 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.
Messages are sorted in alphanumeric order.
This is a general parsing error for the NEW command. It describes an error detected for a keyword's value.
The command fails.
Review the syntax for the keyword in error and correct its contents based on the error description.
An equal sign (=) did not immediately follow a keyword. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
A value expression delimiter ("'~) was encountered and not expected. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
An unexpected open parenthesis was encountered. An open parenthesis is used to begin a list of positional values for a keyword. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
An unexpected close parenthesis was encountered. A close parenthesis is used to terminate a list of positional values for a keyword. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
An unexpected comma was encountered. Commas are used to separate positional values. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The end of an expression was encountered prior to encountering an expected closing delimiter. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
A character other than 0-9 or 'abcdefABCDEF' was encountered inside a hex specification (that is, X'abcd') or end of expression was encountered before the end apostrophe. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
A new keyword was specified after a value expression without the required blank, comma or closing parenthesis. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
A positional value expression was encountered after a keyword value expression. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
A keyword value expression specified within parentheses was missing one or more closing parenthesis. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
A hexadecimal expression was specified with an odd number of characters. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
A keyword expression was encountered that is not part of the syntax for the statement. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression specified a value that contained non-numeric data where a numeric value is required. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression specified a numeric value that resolved to a number consisting of more than 18 significant digits. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression specified a value that consisted of more characters than the maximum length allows for the expression. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The Input expression specified a value that was not one of the allowable values for the expression. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression specified a decimal numeric value. The number of digits to the right of the decimal point was greater than that permitted for the expression. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression specified a keyword more times than allowed by the syntax for the expression. keyword represents the keyword in the error. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression specified a keyword without a required positional value. keyword represents the keyword in error. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression did not specify a required positional value. This message will be issued for required positional values that are to appear prior to any keywords. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression did not specify a required keyword expression. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
The expression did not specify a required keyword expression. This message will appear for a lower level keyword (that is, one with a parent keyword such as ParKwd=(ReqKwd=value).). keyword represents the required keyword from the associated Template Map Keyword entry. parent represents the parent keyword. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
A statement specified a positional parameter after the first keyword expression has been specified. Positional parameters must precede any keyword parameters. Messages AJT0198I and AJT0199I display details of the portion of the statement that is in error.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
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. See the example at the end of AJT0199I.
None.
None.
CAZC0030, CAZC0035, CAZC0390
This message contains a single asterisk to point to where the syntax error described by message AJT0198I occurred. See the example at the end of this section.
Command is terminated.
None.
CAZC0030, CAZC0035, CAZC0390
Example of AJT0198I and AJT0199I
In the example below, message AJT0102E describes the cause of a syntax error in a CONFIG statement. AJT0198I displays the portion of the statement in error, and AJT0199I points to the portion of the statement (described by AJT0198I) that is in error.
AJT0102E Misplaced equal sign
AJT0198I SystemId==CAZ1
AJT0199I *
This is an internal error. An attempt to create a new data space failed because Application Performance Analyzer has created too many data spaces in this address space. Creation of another data space would have caused an overflow of an internal table. nnnn represents the maximum number of data spaces allowed.
The process abends with abend code U4080.
Contact product support.
The DSPSERV function named by function_code has failed. return_codeXand reason_codeX represent the hexidecimal return and reason codes respectively. See the return and reason codes in the MVS Programming: Authorized Assembler Services Reference for the DSPSERV macro.
The process abends with abend code U4080.
Contact product support.
The ALESERV function named by function_code has failed. return_codeX represent the hexidecimal return and reason code.
The process abends with abend code U4080.
Contact product support.
This is an internal error. An attempt to extend a data space failed because Application Performance Analyzer could not identify the original "owner" of the data space. A possible cause for this problem is a storage overlay. id_1 and id_2 are diagnostic data for product support.
The process abends with abend code U4080.
Contact product support.
An attempt to extend a reporting data space beyond its maximum size failed. The report named by aaa might be incomplete.
Application Performance Analyzer continues processing.
Contact product support.
An I/O error was detected while processing data set specified by aaaa. Message AJT0206I follows to provide details of the error.
Operation is cancelled.
Refer to message AJT0206I for more information.
This message provides details of the I/O error described by message AJT0205E.
None.
Attempt to resolve the error based on the information provided here. Contact product support if you are not able to resolve the problem.
An error was detected while processing data set specified by aaaa. Message AJT0208I follows to provide details of the error.
Operation is cancelled.
Refer to message AJT0208I for more information.
This message provides details of the I/O error described by message AJT0207E.
None.
Attempt to resolve the error based on the information provided here. Contact product support if you are not able to resolve the problem.
During the initialization of the main task, the version and release numbers are reported as numbers.
Application Performance Analyzer for z/OS® continues initialization.
None.
CAZ00001 was executed in TSO foreground.
Application Performance Analyzer terminates.
Application Performance Analyzer must be run in a batch region or started task.
During initialization, the message logging module CAZ00085 could not be loaded.
Application Performance Analyzer terminates.
This is probably caused by an incorrect library concatenation in STEPLIB. Correct the JCL and resubmit.
During initialization, the module CAZ00002 could not be loaded.
Application Performance Analyzer terminates.
This is probably caused by an incorrect library concatenation in STEPLIB. Correct the JCL and resubmit.
CAZ00001 terminated because it was not APF authorized.
Application Performance Analyzer 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 CAZ00001 load module.
During initialization, CAZ00001 was unable to establish an ESTAE exit routine. The return code and reason code from the ESTAEX macro are reported as X'return_code' and X'reason_code'.
Application Performance Analyzer 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.
This message is issued at startup and lists the Application Performance Analyzer features (feature_1...feature_n) that this current system is licensed for.
Application Performance Analyzer continues initialization.
None.
A previous error occurred during sysplex initialization and is preventing Application Performance Analyzer from completing initialization.
Application Performance Analyzer terminates.
Refer to messages prior to this one for more information about the cause of the error.
A measurement request was submitted to measure an active job at some future date and time. At the time the measurement request was submitted, the selected job was executing under an ASID. When the date and time arrived to start the measurement session, the original job had terminated and a new job with the same job_name was running, but under a different ASID.
Application Performance Analyzer marks the request "Failed."
Resubmit a new request and delete the failed request.
Application Performance Analyzer has detected that you are running another instance of Application Performance Analyzer with the same group name on the same system. You can only run one instance of Application Performance Analyzer with the same group name on the same system.
Application Performance Analyzer terminates.
The named component of Application Performance Analyzer has ended abnormally (ABEND).
Application Performance Analyzer terminates.
Refer to messages prior to this one for more information about the cause of the error.
Application Performance Analyzer has detected that another Application Performance Analyzer member of the same sysplex group, is using a different checkpoint file name. All members of the same group must use the same checkpoint file name.
Application Performance Analyzer terminates.
Change the checkpoint file names in the configuration of sysplex members member_name, file_name, or both so that they match, and then stop and restart these tasks.
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 .
Application Performance Analyzer continues initialization.
None.
During initialization, another started task instance of Application Performance Analyzer 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 started task.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
Application Performance Analyzer has detected that it is executing on a level of the operating system that Application Performance Analyzer does not support. Refer to message CAZ0004D for more information about operating system level.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Program Directory for information about the product levels supported.
Application Performance Analyzer has detected that it is executing on a non-JES2 system. SYSOUT data sets will not be sampled and therefore the I/O reports will lack SYSOUT information. System action: Application Performance Analyzer continues initialization.
None.
You have requested Application Performance Analyzer to execute in sysplex mode and Application Performance Analyzer has determined that sysplex is not available on the MVS™ image.
Application Performance Analyzer terminates.
Either change this started task to run in non-sysplex mode, or run it on an MVS image where sysplex is available.
A measurement request was submitted to measure an active job that is no longer executing under the selected address space ID.
Application Performance Analyzer marks the request failed.
Resubmit a new request and delete the failed request.
Application Performance Analyzer is shutting down and has detected active sampling sessions. The started task must wait for these sessions to complete. The estimated wait time is represented by minutes:seconds; where mmmm represents minutes and ss represents seconds.
Application Performance Analyzer waits.
This message indicates that an operator has entered STOP command requesting the Application Performance Analyzer started task to shut down.
Application Performance Analyzer terminates.
Correct the value of SPXGroupName in CONFIG BASIC and restart Application Performance Analyzer.
Application Performance Analyzer has attempted to join a SYSPLEX group but has detected that it has joined the wrong group. A possible cause for this is an incorrect SPXGroupName value was specified.
Application Performance Analyzer terminates.
Correct the value of SPXGroupName in CONFIG BASIC and restart Application Performance Analyzer.
This message indicates that while initializing in a sysplex group, this instance of Application Performance Analyzer has detected that it is using a security mode that does not match the other members of the sysplex group.
All members of the sysplex group must use the same security mode. Refer to the SECURITY keyword in the 'CONFIG BASIC' statement of started tasks configuration settings for more information.
Application Performance Analyzer terminates.
Ensure that all sysplex members are configured to use the same security type.
An ALESERV ADD failed for the HFS SYSZBPX2 data space.
Processing continues, but no HFS data can be extracted for any observation request.
Contact product support
IBM Application Performance Analyzer timed out waiting for OMVS to start. If OMVS is not running, Application Performance Analyzer cannot obtain HFS file statistics.
Application Performance Analyzer terminates.
Restart Application Performance Analyzer after OMVS has started.
IBM Application Performance Analyzer detected that it was assigned to service class: aaaa. If this service class is at a lower priority than SYSSTC, then Application Performance Analyzer TSO users may experience poor response and timeouts.
None.
Assign the Application Performance Analyzer started task to service class SYSSTC.
Application Performance Analyzer has detected that another Application Performance Analyzer member of the same SYSPLEX group is using a different CDS file name. All members of the same group must use the same CDS file name.
Application Performance Analyzer terminates.
Change the CDS File names in the configuration of sysplex members so they match and then stop and restart these tasks.
Application Performance Analyzer issued a Global Name/Token services request (to IEANTRT) that failed. This could indicate a system environmental problem.
Application Performance Analyzer terminates.
Examine the reported return code return_code and analyze the reason why IENTRT might have failed.
Application Performance Analyzer issued a Global Name/Token services request (to IEANTRT) which failed. This could indicate a system environmental problem.
Application Performance Analyzer terminates.
Examine the reported return code return_code an analyze the reason why IENTRT might have failed.
During initialization, Application Performance Analyzer 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 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 maximum number of Application Performance Analyzer 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 terminates.
Stop an instance of Application Performance Analyzer that is currently not in use and try to restart the failed instance.
One of two problems might have occurred:
Application Performance Analyzer terminates.
If the error was caused by option 1, 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, then perform the following:
PABENTReset=YES
Application Performance Analyzer has started a new subtask to initiate a sampling session. The name of the job being measured is indicated by job_name and request_number is the request number.
None.
None.
Application Performance Analyzer has completed a sampling session for job job_name, request number request_number. The subtask that was attached to process this session has ended and has been detached.
None.
None.
This indicates Application Performance Analyzer has started sampling for request number nnnn in started task ssss.
None.
None.
This indicates Application Performance Analyzer has ended sampling for request number nnnn in started task ssss.
None.
None.
This message is displayed with message CAZ0073I to indicate the data set name of the sample file created.
The step is complete.
None.
The Application Performance Analyzer started task CONFIG file specified a value for MaxUSSCM (aaaa) that is greater than the original value specified when the started task was first brought up after an initial program load (IPL).
Application Performance Analyzer continues initialization.
In order for the new, higher MaxUSSCM value to take effect you must restart (re-IPL) your system.
Application Performance Analyzer completed its initialization. The system is now ready to process sampling.
None.
None.
An attempt to create a new scheduling record for request number request_number failed. The value of record_type indicates what kind of record was being created:
The new scheduling request fails.
The most likely cause of this error is that the checkpoint file is full. Delete some old requests to make room for new ones.
Performance Analysis Reporting was attempting to access the file described in file-type. The attempt failed because the file could not be opened.
The ISPF dialog is terminated.
Refer to any MVS system messages that might have been issued at the time of the error to determine a problem resolution.
While attempting to load the sample file, reporting detected that the system was running low on auxiliary storage.
The sample is not loaded, and the user is returned to the R02 panel.
Request that your system programmer add more page data sets.
While attempting to load a sample file, reporting detected a "data space full" condition and could not finish loading the data space. The aaaa value represents the current size of the data space in bytes.
The sample is not loaded, and the user is returned to the R02 panel.
If the size value aaaa is 2 gigabytes, the sample is too large and can not be loaded by reporting. Try re-running the sample request with either a shorter duration or sampling frequency. If the size value aaaa is less then 2 gigabytes, the most likely cause is that your installation is restricting the maximum data space size to this value. Request your system programmer adjust this maximum value in the IEFUSI exit.
When attempting to create a report, Application Performance Analyzer detected a "data space full" condition. The data for this report has filled the dataspace and the dataspace cannot be extended.
There is too much data in the sample file for this report. Report creation is terminated and the user is returned to the R02 panel.
Use the R or S command again to display the reports menu for this observation, and try creating other reports to get similar data in a summary format. You can also try running the sample request again with either a shorter duration or sampling frequency.
The Application Performance Analyzer-started task was unable to serialize an internal resource required to perform an intercept function. Another Application Performance Analyzer started task was holding the resource for the same reason. The problem occurs when multiple instances of the Application Performance Analyzer started task are starting at the same time, each attempting to acquire the resource. Only one will succeed, the rest will fail.
The function was not performed. If this problem occurred during startup, then the started task will terminate.
Restart the started task.
The Application Performance Analyzer started task was unable to perform an intercept function because there were other Application Performance Analyzer started tasks executing. An intercept function can only be performed when all other Application Performance Analyzer started tasks are down.
The function was not performed. If this problem occurred during startup, then the started task will terminate.
Stop all Application Performance Analyzer started tasks and then retry the function.
The SRB that is used to install and uninstall the DB2®, IMS™ or WLM intercept failed.
The function was not performed. If this problem occurred during startup, then the started task will terminate.
Record the information in this message. Check for a possible dump in the *MASTER* address space, save the dump and then contact product support.
The component identified by #### could not find the load module specified by aaaaaaaa. The following standard search order was used:
Depends on the Component ID:
Ensure that the specified load module is available in either STEPLIB or LINKLIST.
IEAMSCHD was unable to schedule an SRB for the reason given in the RC field.
The function was not performed. If this problem occurred during startup, then the started task will terminate.
Record the information in this message, then refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The SRB or IRB used to install and uninstall the DB2, IMS or WLM intercept ended abnormally (ABEND).
The function was not performed. If this problem occurred during startup, then the started task will terminate.
A mini diagnostic dump will be produced under the ddname DUMP0001. Save this dump and contact product support.
The SRB or IRB used to install and uninstall the intercept detected input parameters that are not valid and could not proceed.
The function is terminated.
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 SRB used to install and uninstall the intercept detected an invalid internal control block and could not proceed.
The function is terminated.
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 program used to manage the DB2 (CAZ00004), IMS (CAZ00006) or WLM (CAZ00007) intercept detected an abend and has recovered but the function could not proceed.
The function is terminated and a dump will be produced.
Save the dump and contact product support.
The IRB that is used to install and uninstall the intercept could not be scheduled because the *MASTER* address space's job step TCB could not be found.
The function is terminated.
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 request to uninstall the DB2, DDF, IMS or WLM intercept completed successfully. DB2, DDF, IMS or WLM calls will no longer be intercepted on this MVS system.
None
None.
The request to install the DB2, DDF, IMS or WLM intercept completed successfully. DB2, DDF, IMS or WLM calls will now be intercepted on this MVS system.
None
None.
The request to update the DB2 or IMS intercept code could not be completed because Application Performance Analyzer determined that the intercept is currently in use by one or more sampling sessions. Wait for the sampling session(s) to complete before retrying this function.
None.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ for more information.
The request to uninstall the DB2, IMS or WLM intercept failed for the reason specified by reason_code. Possible values for reason_code are:
None.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ for more information.
The request to reset the DB2 or IMS intercept control data was not possible for the reasons specified by reason_code. Possible values for reason_code are:
None.
Refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ form more information.
During startup, the Application Performance Analyzer started task determined that a newer version of the DB2, DDF, IMS or WLM intercept is available. It will attempt to refresh the intercept. Refresh involves uninstalling the current intercept and then installing the new one. All other Application Performance Analyzer started tasks must be down in order for this process to complete successfully.
Intercept will be refreshed
None
During startup, the Application Performance Analyzer started task determined that a newer version of an internal stub is available. It will attempt to refresh the stub.
IMS stub will be refreshed.
None
During startup, the Application Performance Analyzer started task determined that a newer version of an internal IMS stub was available and that it was refreshed successfully.
None
None
The component identified by #### experienced a BLDL error while processing aaaaaaaa. The BLDL return code and reason code are given by rc and rsn.
Depends on the Component ID.
Correct the problem based on the BLDL return and reason codes.
The program named in module_name has detected an abend and produced an SVC dump.
Processing continues
Save the dump and contact Application Performance Analyzer support.
The action described by bbbb was not taken due to the reason given by aaaa.
None.
None.
The action described by aaaa was not possible because another vendor, whose jobname is represented by bbbb, is already intercepting WLM.
None.
None.
The action described by bbbb has been successfully completed for aaaa.
None.
None.
The user is attempting to issue a WLMI command with an undefined function or operand.
None.
Correct the command and reissue it.
The user is attempting a WLMI activate or deactivate function but the WLM intercept was never installed. The intercept may only be activated or deactivated if the intercept is first installed.
None.
None.
Application Performance Analyzer initiated its shutdown process.
None.
None.
The Application Performance Analyzer started task was unable to initialize an internal control block because there were other Application Performance Analyzer started tasks executing. This control block can only be initialized when all other Application Performance Analyzer started tasks are down. "s1, s2, s3,..." represent the IDs of the Application Performance Analyzer started tasks that are still executing.
The started task will terminate.
Stop all Application Performance Analyzer started tasks and restart the started task.
This message is reported when Application Performance Analyzer has completed its shutdown process and is about to terminate.
None.
None.
During initialization, Application Performance Analyzer was unable to load module xxxxxxxx. The value in R01 is the abend code from the load and the value in R15 is the reason code.
Application Performance Analyzer terminates.
Find the abend code in the Systems Codes manual, correct the error and restart the Application Performance Analyzer started task.
The IEFUSI exit module specified by module_name was found in the currently active linklist specified by linklist_name in the data set specified by data_set_name.
None.
None.
The IEFUSI exit module specified by module_name could not be found in the currently active linklist.
Application Performance Analyzer terminates.
Ensure that the named module is in a linklist data set and then restart Application Performance Analyzer.
Application Performance Analyzer detected a CSVDYNL error while attempting search the currently active linklist specified by linklist_name for the IEFUSI exit module specified by module_name. The CSVDYNL return code and reason code are specified by return_code and reason_code respectively.
Application Performance Analyzer terminates.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the CSVDYNL error codes. Correct the problem and then restart Application Performance Analyzer.
This message indicates that while initializing in a sysplex group, this instance of Application Performance Analyzer detected that it is running with internal security rules.
Application Performance Analyzer cannot guarantee the accuracy of security authorizations if performs using internal rules. Users might be unintentionally authorized for actions.
It is recommended that an installation's external security system be used when Application Performance Analyzer is running as part of a sysplex group.
This is a warning, no further action is taken. All processing will continue as normal.
Consider migrating Application Performance Analyzer to your installation's external security system.
This message indicates that while initializing in a sysplex group, this instance of Application Performance Analyzer detected that it is running with external security rules in compatibility mode.
Application Performance Analyzer cannot guarantee the accuracy of security authorizations if performs under these conditions. Users might be unintentionally authorized for actions.
It is recommended that an installation's external security system be used in native mode when Application Performance Analyzer is running as part of a sysplex group.
Compatibility mode should only be used temporarily while the installation updates its security rules to use the MVS system name instead of the STCid of the Application Performance Analyzer started task as the first node of the resource profile.
This is a warning, no further action is taken. All processing will continue as normal.
None.
The module specified by aaaaaaaa was found in the currently active link list specified by cccccccc in the data set specified by bbbbbbbb.
None
None.
The module specified by aaaaaaaa could not be found in current LNKLST.
Application Performance Analyzer terminated.
Ensure that the named module is in a link list data set and then restart Application Performance Analyzer.
Application Performance Analyzer detected a CSVDYNL error while attempting to search the currently active link list specified by aaaa for the module specified by bbbb. The CSVDYNL return code and reason code are specified by cccc and dddd respectively.
Application Performance Analyzer terminates.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the CSVDYNL error codes. Correct the problem and then restart Application Performance Analyzer.
During initialization, this message reports the maximum size of the sampling buffers used during a measurement request.
None.
None.
During initialization, this message reports the interval of time between each Application Performance Analyzer "pulse" during which it checks for work to be dispatched. The value time_interval is in units of 1/100 seconds.
None.
None.
During initialization, this message reports a value that either was specified in the CONFIG member or was set to its default. The value seconds is the default number of seconds of duration for a sampling session.
None.
None.
During initialization, this message reports a value that either was specified in the CONFIG member or was set to its default. The value samples is the default number of samples to be taken during a sampling session.
None.
None.
During initialization, this message reports a value that either was specified in the CONFIG member or was set to its default. The value sampling_rate is the minimum duration, in milliseconds, that is allowed to be specified as a sampling rate.
None.
None.
During initialization, this message reports a value that either was specified in the CONFIG member or was set to its default. The value primary_allocation_units is the number primary allocation units for the log data set.
None.
None.
During initialization, this message reports a value that either was specified in the CONFIG member or was set to its default. The value allocation_unit is the allocation unit for the log data set: T=TRK, C=CYL, B=BLK.
None.
None.
During initialization, this message reports a value that either was specified in the CONFIG member or was set to its default. The value name is the DASD UNIT name for allocation of new data sets.
None.
None.
During initialization, this message reports the name of the data set (data_set_name) Application Performance Analyzer will use for checkpoint functions.
None.
None.
During initialization, this message reports the number of records (records) (excluding header records) specified for the Checkpoint File. This value is meaningful only if no Checkpoint File exists and Application Performance Analyzer creates one.
None.
None.
During initialization in sysplex mode, the Application Performance Analyzer started task has detected that its HLQ does not match that of at least one other Application Performance Analyzer started task in the same sysplex group.
Application Performance Analyzer terminates.
This is an information message that indicates whether this instance of Application Performance Analyzer successfully joined the sysplex group. A return code value of either 0 or 4 indicates a successful operation. A return code greater than 4 indicates a problem with the join operation. The message is written to the sysout_file. The MVS_system refers to the MVS system on which Application Performance Analyzer is running.
Application Performance Analyzer will terminate if the return code is greater than 4 and this message will be followed by message CAZ0014E.
Refer to the MVS Programming: Sysplex Services Reference for an explanation of the return and reason codes for IXCJOIN and take corrective action.
This message is only used by product support for diagnostic purposes.
None.
Contact product support.
This message is only used by product support for diagnostic purposes.
None.
Contact product support.
This message is only used by product support for diagnostic purposes.
None.
Contact product support.
This message is only used by product support for diagnostic purposes.
None.
Contact product support.
The logger subtask has started and is in the process of initializing.
Application Performance Analyzer continues initialization.
None.
The logger subtask has completed initialization and is now ready for work.
Application Performance Analyzer continues initialization.
None.
A dynamic allocation error occurred while attempting to allocate a new log filed 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 terminates.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and then restart Application Performance Analyzer.
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 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 the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and if necessary restart Application Performance Analyzer.
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 terminates.
Refer to the DFSMSdfp Advanced Services for information about the above error codes. Correct the problem and then restart Application Performance Analyzer.
The logger subtask has started its shutdown process.
None.
None.
The logger subtask has completed its shutdown process and is about to terminate.
None.
None.
The command processor subtask has started and is in the process of initializing.
Application Performance Analyzer continues initialization.
None.
An operator attempted to enter an Application Performance Analyzer modify command specified by command_name that was not permitted.
Command is discarded.
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 JCL.
Application Performance Analyzer terminates.
Add the appropriate COMMANDS DD statement to the Application Performance Analyzer JCL.
The command processor subtask has completed initialization and is now ready for work.
Application Performance Analyzer continues initialization.
None.
The module module_name for the MVS installation exit named by exit_name has already been defined.
Application Performance Analyzer will use the existing definition.
None.
The command processor subtask has started its shutdown process.
None.
None.
The command processor subtask has completed its shutdown process and is about to terminate.
None.
None.
The MVS installation exit named by exit_name has been successfully defined to MVS.
None.
None.
The MVS installation exit named by exit_name has been defined to MVS by another application.
Application Performance Analyzer will use the existing definition.
None.
Application Performance Analyzer was unable to define the MVS installation exit named by exit_name. return_code and reason_code represent the return and reason codes returned by CSVDYNEX.
If the problem occurs during initialization, Application Performance Analyzer will terminates. Otherwise no action is taken.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the CSVDYNEX return and reason codes. Correct the problem and restart Application Performance Analyzer if necessary.
Application Performance Analyzer was unable to add the module module_name to the MVS installation exit named by exit_name. return_code and reason_code represent the return and reason codes returned by CSVDYNEX.
If the problem occurs during initialization, Application Performance Analyzer will terminate, otherwise not action is taken.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the CSVDYNEX return and reason codes. Correct the problem and restart Application Performance Analyzer if necessary.
The module module_name was successfully added to the MVS installation exit named by exit_name.
None.
None.
Application Performance Analyzer was unable to list the MVS installation exit points. return_code and reason_code represent the return and reason codes returned by CSVDYNEX.
Application Performance Analyzer will terminate.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the CSVDYNEX return and reason codes. Correct the problem and restart Application Performance Analyzer.
The exit point defined by task_name was not active for the reason specified in reason_code. Application Performance Analyzer is not able to add an exit routine to that exit point. For reason codes less than or equal to 4 this is an informational message.
For reason codes greater than 4 this a warning message and users will not be able to sample non active started tasks: (task_name = "SYSSTC.IEFUSI") or TSO logons: (task_name = "SYSTSO.IEFUSI").
Values for task_name:
Values for reason_code are:
Application Performance Analyzer continues initialization.
For reason codes greater than 4 contact your system programmer and verify the status of the SMF exit points. Refer to the chapter describing SMFPRMxx in MVS Initialization and Tuning Reference for information about defining the exit point. Correct the problem and restart Application Performance Analyzer.
Application Performance Analyzer determined that one of the following exit points was not active: SYS.IEFUSI, SYSJES2.IEFUSI, (or SYSJES3.IEFUSI in JES3 environments). These exit points must be active in order for Application Performance Analyzer to sample scheduled jobs. Refer to message CAZ1225W for more information.
Application Performance Analyzer will terminate.
Contact your system programmer and verify the status of the SMF exit point: SYS.IEFUSI and SYSJES2.IEFUSI or SYSJES3.IEFUSI. Refer to the chapter describing SMFPRMxx in MVS Initialization and Tuning Reference for information about defining the exit. Correct the problem and restart Application Performance Analyzer.
The Application Performance Analyzer exit routine (routine_name) has already been added by another instance of Application Performance Analyzer. Values for task_name:
Application Performance Analyzer continues initialization.
None.
The Exit Point defined by aaaa was not defined to the system. Application Performance Analyzer might not be able to sample USS address spaces properly.
Application Performance Analyzer continues initialization.
Determine why the Exit Point was not defined. Define it and restart the Application Performance Analyzer STC.
Application Performance Analyzer was attempting to determine the status of the Exit Point described by cccc via the CSVDYNEX LIST function. This function failed with return and reason codes described by aaaa and bbbb. Application Performance Analyzer might not be able to sample USS address spaces properly.
Application Performance Analyzer continues initialization.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the CSVDYNEX return and reason codes. Correct the problem and restart the Application Performance Analyzer STC.
Application Performance Analyzer was attempting to add a module (aaaa) to the Exit Point described by bbbb via the CSVDYNEX ADD function. This function failed with return and reason codes described by cccc and dddd. Application Performance Analyzer might not be able to sample USS address spaces properly.
Application Performance Analyzer continues initialization.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the CSVDYNEX return and reason codes. Correct the problem and restart the Application Performance Analyzer STC.
The Application Performance Analyzer sysplex messaging system detected an error while receiving a message from a group member.
none.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem..
The module named by module_name has been deleted from memory. This message is a result of the PROMOTE operator command.
None.
None.
The module named by module_name was not defined to Application Performance Analyzer. This message is a result of the PROMOTE operator command.
PROMOTE command terminates.
Check to ensure that you have typed the module name correctly and retry the command.
The module named by module_name is not eligible for promotion. This message is a result of the PROMOTE operator command.
PROMOTE command terminates.
Check to ensure that you have typed the module name correctly and retry the command.
The module named by module_name was successfully loaded into CSA at location location. This message is a result of the PROMOTE operator command.
None.
None.
The module named by module_name could not be loaded into CSA. This message is a result of the PROMOTE operator command.
PROMOTE command terminates.
Record the values for R01 and R15, then refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Data Extractor Module Resolution User Exit was enabled by the CONFIG SAMPLE DEXMR=YES parameter. However, the Application Performance Analyzer started task was not able to locate and load the CAZDEXMR load module.
None. The Exit will not be called during sampling.
Ensure that the CAZDEXMR load module is either in a dataset concatenated to the started task's STEPLIB or in linklist.
The Data Extractor Module Resolution User Exit was enabled by the CONFIG SAMPLE DEXMR=YES parameter. However, the Application Performance Analyzer started task was not able to locate and load the CAZDEXMR load module.
None. The Exit will not be called during sampling.
Ensure that the CAZDEXMR load module is either in a dataset concatenated to the started task's STEPLIB or in linklist.
An error occurred processing the command specified by aaaa. The reason is given by bbbb.
None.
Correct the command based on the reason provided and retry the command. If it fails again, contact product support.
This is a fatal error.
Command is terminated and the Application Performance Analyzer started task carries on normal processing.
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.
User user_ID attempted the specified action when request request_number no longer existed.
Command is terminated.
None.
User attempted to delete a request that was either currently active or already deleted.
Command is terminated.
None.
User user_ID attempted to delete request request_number. The request failed because the associated Sample File was in use by another user.
The request is not deleted.
Try the delete request later.
User user_ID attempted to add a new sampling request that is a duplicate of one already added by the same user. job_name and request_number represent the job name and request number of the request that is already queued.
The request is not added.
Redefine the request with different parameters.
User attempted to cancel a request that was either not currently active or already cancelled.
Command is terminated.
None.
A KEEP command was issued for an observation request that does not exist.
Command processing terminates.
Report the error to the system administrator.
A KEEP command was issued for an observation request that is in either Active, Sched, Future, or Thresh status.
The KEEP command is ignored.
Wait for the request to end before issuing the KEEP command.
Request nnnn is a Schedule, Multi-step, Threshold Monitor, USS, Collateral DB2 master request record or IMS Multiple Region master request record. This type of request record represents a list of subsidiary requests. This type of record cannot be deleted by using the batch command interface.
Command is rejected.
Use the ISPF interface to delete this type of request.
The scheduling entry for date date and time time is more than 366 days from the date and time of the request. Application Performance Analyzer allows future-dated requests up to 1 year from the current date and time.
Command is rejected.
Correct and resubmit the scheduling request.
The keyword ASID must not be specified for a future-dated scheduling request with ACTIVE=YES.
Command is rejected.
Correct and resubmit the scheduling request.
The keyword ASID must not be specified for a request without ACTIVE=YES.
Command is rejected.
Correct and resubmit the scheduling request.
A command was issued without a required keyword: keyword.
Command is rejected.
Correct and resubmit the command.
A command was issued with a keyword: keyword that contained a value that was inappropriate for the keyword.
Command is rejected.
Correct and resubmit the command.
A command was issued with a keyword: keyword that contained a numeric value that was out of range. value_range describes the valid range for the keyword.
Command is rejected.
Correct and resubmit the command.
A command was issued with mutually exclusive keywords. keyword describes the keywords in error.
Command is rejected.
Correct and resubmit the command.
This message indicates that either a new observation request was added or an existing observation request was updated and the request specified a target system name of asterisk (*). Under these conditions the request could not be authorized using the external security system since the target system name is unknown. The request has been provisionally accepted and will be authorized at the time the job starts. When the job starts, the system will be known. It is possible, however, for the request to fail at that time.
None.
If this is a critical observation request, then ensure that your user ID has the proper measurement authority on all systems in this Application Performance Analyzer sysplex group.
A NEW or MODIFY command was issued with the CTRAN keyword containing a syntactically incorrect CICS® transaction name or mask: transaction_name.
Command is rejected.
Correct and resubmit the command.
A NEW or MODIFY command was issued with the FEATURES keyword containing an unknown feature value: feature_name.
Command parsing continues, the invalid feature is ignored.
Correct and resubmit the command if necessary.
An access error occurred while processing a NEW or MODIFY command. The text of the message describes the access error.
Command is rejected.
Contact your system administrator for assistance with the problem. Refer to the Application Performance Analyzer Customization Guide for information regarding defining access rules.
A severe access error occurred while processing a NEW or MODIFY command. return_code represent the return code.
Command is rejected.
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 keyword SCHDSPAN can be specified only if ACTIVE=NO is specified for a future-dated scheduling request.
Command is rejected.
Correct and resubmit the scheduling request.
A NEW or MODIFY command was issued with the LIBS keyword specifying too many data set names.
Command parsing continues.
Correct and resubmit the command if necessary.
Request=request_number : Userid=user_ID for JOB job_name and STEP step_name.
Request=request_number : Userid=user_ID for JOB job_name and STEP step_name and PROCSTEP proc_step_name.
Request=request_number : Userid=user_ID for JOB job_name and PROGRAM program_name.
Request=request_number : Userid=user_ID for JOB job_name and PROGRAM program_name and PROCSTEP proc_step_name.
Request=request_number : Userid=user_ID for JOB job_name and STEP step_number.
Request=request_number : Userid=user_ID for JOB job_name. nn steps.
Request=request_number : Userid=user_ID for JOB job_name. xxx future dates.
Request=request_number : Userid=user_ID for JOB job_name. nn steps and xxx future dates.
A NEW or MODIFY command was successfully issued. The message describes the selection parameters specified for this request.
The command is accepted.
None.
The scheduling entry for date date and time time is overlapped by the time span of the previous entry or the scheduling entry for date time overlapped by RUNAGAIN time span.
Command is rejected.
Correct and resubmit the scheduling request.
STEP entry number step_number has mutually exclusive step identification values. A step can be identified by only one of the following:
Command is rejected.
Correct and resubmit the scheduling request.
The keyword RETRYAFTER can be specified only if ACTIVE=YES is specified for a future-dated scheduling request.
Command is rejected.
Correct and resubmit the scheduling request.
This is an internal error found during command processing.
Command processing completes.
Report the error to the system administrator.
An external component of Application Performance Analyzer called the Application Performance Analyzer started task to perform a function. The started task detected a mismatch between itself and the external component.
The function could not be completed and is terminated.
Report the error to the system administrator.
The action is based on the value specified in caller_name.
If caller_name specifies "IEFUSI" then the Application Performance Analyzer Step Initiation Exit is back leveled with the version of the Application Performance Analyzer started task. Follow the instructions in the Application Performance Analyzer Customization Guide to upgrade the IEFUSI exit.
If caller_name specifies "ISPF CMD" then upgrade the Application Performance Analyzer/ISPF interface.
If caller_name specifies "SPX" then one or more members of the Application Performance Analyzer sysplex group is back leveled. Ensure that all members of the group are at the same Application Performance Analyzer version or higher.
A NEW or MODIFY command was successfully issued. The message describes the sampling parameters specified for this request.
The command is accepted.
None.
No matching job could be found for a request for an active job with job name job_name.
Command is rejected.
Correct and resubmit the scheduling request.
No matching job could be found for a request for an active job with job name job_name and ASID identifier.
Command is rejected.
Correct and resubmit the scheduling request.
When RETRYAFTER=(mm,FOR=nn) is specified, the value of mm multiplied by nn must be greater than zero.
The command is rejected.
Correct and resubmit the scheduling request.
This is an internal error.
Request is failed.
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.
User user_ID has attempted to measure or monitor a job of type:
and with a job name of job_name. request_number is the request number of the failed request. The user is not authorized to request this type of measurement request based on the rules defined to Application Performance Analyzer.
The measurement request is failed. The job continues executing normally.
Refer to the Application Performance Analyzer Customization Guide for information regarding defining access rules.
Application Performance Analyzer cannot accept new sampling request as all available request number have been exhausted.
Request is failed.
If you have old requests that are not longer needed then delete one or more of them and resubmit your request. Otherwise, contact your system administrator for assistance.
A NEW or MODIFY command was issued with a valid that is not valid for either the SDATE or STIME keywords. The value caused CONVTOD to fail with return code: return_code.
Command parsing continues, and the feature that is not valid is ignored.
Retry the request.
A cccc command was issued with the REQNUM keyword. REQNUM is not valid for a cccc command.
Command is ignored.
Resubmit the command without specifying REQNUM keyword.
An attempt to modify request request_number failed because it could not be found. Probable cause: another user deleted the request.
Command is ignored.
Determine whether the request was deleted. If it was not deleted, retry the MODIFY command.
An attempt to modify a request that is no longer scheduled. Probable cause: the request has changed status while the Modify request was being processed.
Command is ignored.
None.
A severe error occurred while attempting to create a new sampling request.
Command is rejected.
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.
A severe error occurred while attempting to create a new sampling request.
Command fails.
the missing keyword resubmit the command.
The user: user_id specified a keyword: keyword_name for which he is not authorized. This most likely an attempt by the user to specify a keyword reserved for internal use only by Application Performance Analyzer.
Command fails.
Remove the keyword and resubmit the command.
The NEW command specified the CICS feature without the associated CTRAN keyword. You must specify one or more transaction codes or * for all transactions when the CICS feature is selected.
The step is terminated.
Specify the CTRAN keyword, and resubmit the job.
The keyword denoted by keyword, is not permitted when Application Performance Analyzer is executing stand-alone. That is: not part of a sysplex group.
Command is rejected.
Correct and resubmit the scheduling request.
A request for a list of job names to the system identified by system_name failed.
The new scheduling request fails.
Check the system log for additional messages or an SVC dump.
There are too many job names in the system identified by system_name that match the requested job name.
The new scheduling request fails.
If possible, provide a more unique job name.
You cannot specify step information for an active job request. The currently executing step is the only one that can be measured.
Command is rejected.
Correct and resubmit the scheduling request.
The keyword RUNAGAIN might not be specified if ACTIVE=YES is specified.
Command is rejected.
Correct and resubmit the scheduling request.
You have specified only one of the two required parameters for the RUNAGAIN keyword. Or you have specified a non-zero value for one of the parameters and zero for the other.
Command is rejected.
Ensure that both parameters contain non-zero values in the appropriate ranges of values.
The userid specified by user_ID is not authorized to perform the function specified by function_name for the sampling request specified by request_number. function_name might be either 'DELETE' or 'KEEP'
Command is rejected.
Refer to the Application Performance Analyzer Customization Guide for information regarding defining access rules.
A step number value of zero was specified in a STEP keyword.
Command is rejected.
Correct and resubmit the scheduling request.
A STEP keyword has specified the same step number as another STEP keyword.
Command is rejected.
Correct and resubmit the scheduling request.
A NEW or MODIFY request attempted to select a feature that has not been enabled in Application Performance Analyzer. The feature that has not been enabled is identified in feature_variable.
None.
The Application Performance Analyzer configuration settings have not been enabled for this feature. Refer to the "Started Task Configuration Settings" section in the Application Performance Analyzer Customization Guide for instructions on how to enable this feature.
A NEW or MODIFY request attempted to select a feature that could not be activated in Application Performance Analyzer. The feature that is not activated is identified in feature_variable.
None.
Refer to the MAIN sysout data set in the started task for error messages that describe the reason the feature could not be activated.
You have entered sequence schedule dates/times where the interval between two consecutive entries is less than or equal to the sampling duration. This is not permitted for a sampling request for an active job since it would cause two sampling sessions to overlap each other.
Command is rejected.
Correct and resubmit the scheduling request.
A NEW or MODIFY command was issued with _keyword_ keyword (where _keyword_ is either: ITRAN, IPROG, or IUSER) containing a syntactically incorrect IMS transaction name, program name or userid; or associated mask_value.
Command failed.
Correct and resubmit the command.
A NEW or MODIFY command was issued with conflicting keywords. The command processor detected the presence of both IMS keywords (ITRAN, IPROG, and/or IUSER) as well as CICS keywords (CTRAN, CTERM, etc.). These sets of keywords are mutually exclusive.
Command failed.
Correct and resubmit the command.
The user attempted to convert a Triggering request for schedule job to sample an active job. This is not allowed.
Command is terminated.
None.
The user attempted to create a Triggered request to sample either multiple steps in the job; or assign the request run-again or scheduling attributes. This is not allowed.
Command is terminated.
None.
The user attempted to add or modify a Triggered request where the associated Triggering request is not in the correct status. This error occurs when the Triggering request status is no 'Sched'.
aaaa = added or modified
Command is terminated.
None.
The user attempted to add or modify a Triggered request against a Triggering request that is sampling an active address space.
aaaa = added or modified
Command is terminated.
None.
The user attempted to add or modify a Triggered request against a Triggering request that is already associated with a Triggered request. This is not allowed.
aaaa = added or modified
Command is terminated.
None.
The user attempted to add or modify a Triggered request against a Triggering request that no longer exists.
aaaa = added or modified
bbbb = request number of triggering request
Command is terminated.
None.
The user attempted to add a Triggered request to a request that is itself a Triggered request. Triggered requests cannot be chained together.
aaaa = request number of triggering request
Command is terminated.
None.
The user attempted to add a Triggered request to a Triggering request and both requests specified the same jobname. This is redundant and not allowed since it would cause two observation requests to sample the same address space at the same time.
aaaa = request number of triggering request
Command is terminated.
None.
The keyword represented by 'aaaa', is not permitted when a jobname pattern is also specified since it may trigger multiple requests.
Command is rejected.
Correct and resubmit the scheduling request.
The user attempted to specify multiple scheduled events for a request whose job name also specified a pattern. This is not permitted, since it would trigger multiple requests.
Command is rejected.
Correct and resubmit the scheduling request.
The Application Performance Analyzer IEFUSI exit has abended too many times and has disabled itself to prevent further abends. New observation requests for non-active jobs will not be accepted until the exit is re-enabled.
None.
Search the system log for message ID CAZ9013E. Note the times of these messages, produce a logrec report, and contact product support.
A jobname of '-' indicates a specific DB2 stored procedure or user-defined function request, but not all required parameters were entered. Retry the request with all required parameters.
None.
None.
The user attempted to add or modify a specific stored procedure or user-defined function request. An option provided in the request is invalid. aaaa represents the invalid option.
Command is terminated.
None.
The parameter or feature represented by aaaaaaaa is required and must be specified on the NEW command for an IMS Multiple Region Request.
Command is rejected.
Correct and resubmit the command.
The parameter or feature represented by aaaaaaaa cannot be specified on the NEW command for an IMS Multiple Region Request.
Command is rejected.
Correct and resubmit the command.
The parameter ACTIVE=Y must be specified on the NEW command for an IMS Multiple Region Request.
Command is rejected.
Correct and resubmit the command.
A MODIFY command was entered for an IMS Multiple Region request. The MODIFY command is not valid for an IMS Multiple Region Request.
Command is rejected.
To change an existing IMS Multiple Region Request, delete/cancel the existing request and re-enter it.
You cannot specify ALL in the SYSTEMS keyword for an IMS Multiple Region Request. IMS Multiple Region Requests can only be created for a single system in the sysplex.
Command is rejected.
Correct and resubmit the command.
An IMS Multiple Region request was submitted for the specified IMS subsystem and no dependent regions were eligible to schedule the specified tran code.
Command is rejected.
Verify that the IMS subsystem has at least one dependent region available to schedule the specified tran code and that the user has the required authority to measure the region(s).
This is a general information message used for diagnostic purposes by product support. The text of the message will vary depending on the diagnostic data to be presented.
None.
None.
The value or mask vvvvvvvv specified for DDF filter parameter DDF_filter_parameter is invalid for one of the following reasons:
Command is rejected.
Correct the parameters and resubmit the command.
A NEW or MODIFY command was issued with conflicting keywords. The DDF filter keywords (CORRID, EUSERID, and/or WKSTNID) have been specified with the IMS keywords (ITRAN, IPROG, and/or IUSER) or the CICS keywords (CTRAN, CTERM, and so on.). These sets of keywords are mutually exclusive.
Command is rejected.
Correct the parameters and resubmit the command.
This message indicates that the Checkpointer subtask has started and is in the process of initializing.
Application Performance Analyzer continues initialization.
None.
An attempt to allocate a new Checkpoint File failed. Additional information is reported in CAZ2004E and CAZ2005E messages.
Application Performance Analyzer terminates.
Attempt to resolve the problem based on the information available in the message and restart the job.
An attempt to allocate the Checkpoint File to ddname CHKPT failed. Additional information is reported in CAZ2004E and CAZ2005E messages.
Application Performance Analyzer terminates.
Attempt to resolve the problem based on the information available in the message and restart the job.
An OPEN of the Checkpoint File of the indicated dsname failed during initialization of Application Performance Analyzer. This probably indicates that the data set existed with incorrect characteristics. The Checkpoint File should be a physical sequential (PS) data set with unblocked, LRECL=1024 records.
Application Performance Analyzer terminates.
Attempt to resolve the problem based on the information available in the message and restart the job.
This is a secondary information message that provides qualifying information to a separate error message. This message reports a data set name dsname and DD Name ddname for which an allocation attempt failed. This is accompanied by message CAZ2005E or CAZ3943E.
Application Performance Analyzer terminates.
Attempt to resolve the problem based on the information available in the message and restart the job.
This is a secondary information message that provides qualifying information to a separate error message. It reports an error reason and error information code, in hexadecimal, returned from Dynamic Allocation (SVC 99) services.
Application Performance Analyzer terminates.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Attempt to resolve the problem based on the information available in the message and restart the job.
This error occurs when there are too many updates pending for a checkpoint file.
Application Performance Analyzer STC terminates with a S0C3.
Verify that all Application Performance Analyzer STCs with the same sysplex group name (SPXGroupName=xxxxxxxx) have the same checkpoint file defined in their CONFIG files. Also verify that the checkpoint file has not also been defined in a CONFIG file to a non-sysplex Application Performance Analyzer STC. Once the CONFIG files have been corrected, bring down and restart all Application Performance Analyzer STC's.
I/O error reading checkpoint file, attempting initialization. An I/O error on the checkpoint file was detected during started task initialization. The checkpoint file was being verified and the read failed. The started task assumes a corrupt checkpoint file and will attempt to initialize it.
This message will be followed message: CAZ2011E, which provides diagnostics on the I/O error.
Application Performance Analyzer initialization continues.
None.
The message follows: CAZ2010E and provides diagnostic data the I/O error.
Message insert description:
Application Performance Analyzer initialization continues.
None.
This message indicates that the Checkpointer subtask has completed initialization and is now ready for work.
Application Performance Analyzer continues initialization.
None.
This message is reported when the Checkpointer subtask has started its shutdown process.
None.
None.
This message is reported when the Checkpointer subtask has completed its shutdown process and is about to terminate.
None.
None.
This message indicates that the named component of Application Performance Analyzer has ended abnormally (ABEND). This message will be followed by a dump.
Application Performance Analyzer terminates.
This message indicates that a CPU usage constraint has been applied to the request, and the sampling rate has been reduced. This is controlled by the MaxMIPPercent parameter in your installation’s configuration. The user will also get a warning message in the S01 Session Statistics report.
None.
None.
This message indicates that a CPU usage constraint has been applied to the request, and the request has been cancelled. This is controlled by the MaxMIPPercent parameter in your installation’s configuration. The user will see that the request’s status has been set to Stopped.
None.
None.
This message indicates that a CPU usage constraint has been applied to the request, and the sampling rate has been reduced to nnnn. This message applies only to sampling Java 5.0 or higher. Note that this constraint is not controlled by the MaxMIPPercent parameter in your installation configuration.
The sampling rate is reduced to the number indicated.
None.
There are not enough CPUs on the system to support Java sampling. This message applies only to sampling Java 5.0 or higher.
Sampling continues, but no Java sampling is done.
None.
This message indicates that a data writer subtask has started. A new data writer subtask is started each time Application Performance Analyzer starts sampling a job. request_number is the request number and job_name is the name of the Job, STC, or TSU that the data writer has been assigned to.
None.
None.
This message indicates a dynamic allocation error occurred while the data writer was attempting to allocate the sample file (dsn) for the request request_number. error_code, information_code, and reason_code represent the dynamic allocation error code, information code and SMS reason code respectively.
The sampling request is terminated and all sample data is lost.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and resubmit the sampling request.
Application Performance Analyzer has detected that a user has cancelled an active sampling request. An abbreviated sample has been created for this request
None.
None.
The data writer assigned to request rrrr was unable to attach the Host Variable Extractor subtask. This subtask resolves SQL host variable names as requested by the user on the Measurement Options panel (DB2V - SQL Variables option).
Sampling continues without SQL host variable name resolution. Reports containing SQL text will not display host variable names.
Record the return code aaaa and refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
This is an information message indicating that the data writer has successfully allocated a new sample file (dsn) with a primary and secondary allocation of primary_allocation and secondary_allocation tracks respectively.
None.
None.
The data writer assigned to request request_number was unable to attach an ESD subtask
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports. Sampling will proceed for this request, but ESD information will not be available to reporting.
Record the return code return_code and refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
Application Performance Analyzer has detected the absences of a Coupling facility. reason represents the reason text for this message.
Coupling Facility sampling data will not be collected during any sampling sessions.
You can ignore this message if your system is operating without Coupling Facility support. Otherwise, you might wish to review the cause of the error based on the text provided.
The message indicates that an unexpected error occurred while sampling the coupling facility.
Coupling Facility sampling data will not be available, sampling continues for this request.
If the message persists, record the values for aa and bbbbbb and refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
Application Performance Analyzer has detected an IXLMG error during Coupling Facility sampling. return_code and reason_code represent the return code and reason code from the IXLMG call.
Coupling Facility sampling data will not be collected during the sampling session.
If the message persists, record the values for RC and RSN and refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
Application Performance Analyzer has detected an IXCQUERY error during Coupling Facility sampling. return_code and reason_code represent the return code and reason code from the IXCQUERY call.
Coupling Facility sampling data will not be collected during the sampling session.
If the message persists, record the values for RC and RSN and refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
A required DB2 load module could not be loaded from STEPLIB.
Processing continues but some or all DB2 plan and package timestamp data might not be present in the sample file.
Add the DB2 load library to the STEPLIB concatenation in the Application Performance Analyzer Started Task JCL.
The Application Performance Analyzer started task detected an error while performing a DB2 function.
Processing continues but some or all DB2 plan and package timestamp data might not be present in the sample file.
Refer to the IBM® DB2 Universal Database™: Message Reference, Volume 1 or IBM DB2 Universal Database: Message Reference, Volume 2 for an explanation of the reason code and associated corrective for action.
The Application Performance Analyzer started task detected an error while accessing a DB2 catalog.
This message will be followed by one or more CAZ1799 messages that contain DB2 issue messages (DSN*).
Processing continues but some or all DB2 plan and package timestamp data might not be present in the sample file.
Refer to the IBM DB2 Universal Database: Message Reference, Volume 1 or IBM DB2 Universal Database: Message Reference, Volume 2 for an explanation of the DB2 message and associated corrective for action.
This message indicates that the data writer subtask assigned to request request_number has completed initialization and is now ready for work.
None.
None.
The DataWriter's attempt to attach an ESD extractor subtask timed out. aaaa represents the request number associated with this DataWriter.
The DataWriter continues processing but no ESD (CSECT) information is written out to the sample file.
Contract product support.
The data writer assigned to request request_number detected an EDTINFO error while analyzing a data set from the sampled region. device_type is the UCB device type, return_code and reason_code are the return and reason codes respectively from EDTINFO.
None. Sampling continues, but the user might notice missing data when viewing the DASD reports.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the EDTINFO return and reason codes. Correct the problem and resubmit the sample request.
The data writer assigned to request request_number detected a UCBLOOK error while analyzing a data set from the sampled region. device_type is the UCB device type, return_code and reason_code are the return and reason codes respectively from UCBLOOK.
None. Sampling continues, but the user might notice missing data when viewing the DASD reports.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the UCBLOOK return and reason codes. Correct the problem and resubmit the sample request.
This indicates that the sampling request had a severe error. This message is always accompanied by message CAZ3390E that gives the request number and an error code.
The sampling request is terminated and marked as "Failed".
Contact product support with the post code (post_code) from the accompanying CAZ3390E message as well as the complete FFO STC output.
This indicates that the sampling request has unexpectedly stopped sampling. This might be because the target address space has terminated. This message is always accompanied by message CAZ3390E that gives the request number and an error code.
The sampling request is terminated and marked as "Failed".
Contact product support with the post code (post_code) from the accompanying CAZ3390E message as well as the complete FFO STC output.
Application Performance Analyzer was unable to extend a sampling data space. return_code and reason_code represent the return and reason codes returned by DSPSERV EXTEND.
The sampling request will be terminated and the sampling data set might be unusable.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the DSPSERV EXTEND return and reason codes. Correct the problem then resubmit the sampling request.
Application Performance Analyzer detected an error while attempting to create a work dataspace for use by the compression routines. RC=aaaaaaaa and RSN=bbbbbbbb are the DSPSERV CREATE return and reason codes, respectively.
Creation of the sample file continues but without compression.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the DSPSERV CREATE return and reason codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to create a work dataspace for use by the compression routines. RC=aaaaaaaa and RSN=bbbbbbbb are the DSPSERV CREATE return and reason codes, respectively.
Creation of the sample file continues but without compression.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the DSPSERV CREATE return and reason codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to add an ALET for a work dataspace used by the compression routines. RC=aaaaaaaa is the ALESERV ADD return code.
Creation of the sample file continues but without compression.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the ALESERV ADD return codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to add an ALET for a work dataspace used by the compression routines. RC=aaaaaaaa is the ALESERV ADD return code.
Creation of the sample file continues but without compression.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the ALESERV ADD return codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to delete an ALET for a work dataspace. RC=aaaaaaaa is the ALESERV return code and ALET=bbbbbbbb is the ALET.
Normal processing continues.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the ALESERV DELETE return codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to delete an ALET for a work dataspace. RC=aaaaaaaa is the ALESERV return code and ALET=bbbbbbbb is the ALET.
Normal processing continues.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the ALESERV DELETE return codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to delete a work dataspace used for compression. RC=aaaaaaaa and RSN=bbbbbbbb are the DSPSERV DELETE return and reason codes, respectively.
Normal processing continues.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the DSPSERV DELETE return and reason codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to delete a work dataspace used for compression. RC=aaaaaaaa and RSN=bbbbbbbb are the DSPSERV DELETE return and reason codes, respectively.
Normal processing continues.
Refer to the MVS Programming: Authorized Assembler Services Reference for information on the DSPSERV DELETE return and reason codes. If the problem persists, contact IBM support.
Application Performance Analyzer detected an error while attempting to compress the sample file.
Normal processing continues without compression.
If the problem persists, contact IBM support.
This message is reported when the data writer subtask assigned to request request_number has started its shutdown process. The POST code post_code might be ignored. It would be used by product support diagnosis in the event of an error condition.
None.
None.
This message is reported when the data writer subtask assigned to request request_number and Job job_name, has completed its shutdown process and is about to terminate.
None.
None.
This message indicates that a ESD extractor subtask has started. A new ESD extractor subtask is started each time Application Performance Analyzer starts sampling a job. request_number is the request number and job_name is the name of the Job, STC, or TSU that the data writer has been assigned to.
None.
None.
This message indicates that the ESD extractor subtask assigned to request request_number has completed initialization and is now ready for work.
None.
None.
This message indicates an ISITMGD error occurred while the ESD extractor was attempting determine if data set dsn for the request request_number, was SMS managed. return_code and reason_code represent the ISITMGD return and reason codes.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the Macro Instructions for Data Sets for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a dynamic allocation error occurred while the ESD extractor was attempting to allocate a load library (dsn) for module analysis during processing of request request_number. error_code, information_code, and reason_code represent the dynamic allocation error code, information code and SMS reason code respectively.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and resubmit the sampling request.
This message indicates a FIND error occurred while the ESD extractor was attempting to find the member member_name in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for FIND.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Macro Instructions for Data Sets for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND STARTD error occurred while the ESD extractor was preparing to extract ESD information from modules in load library dsn during processing of request request_number. return_code and rason_number represent return and reason codes for IEWBIND STARTD.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND CREATEW error occurred while the ESD extractor was preparing to extract ESD information from modules in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for IEWBIND CREATEW.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a LOAD error occurred while the ESD extractor was preparing to extract ESD information from modules in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for LOAD, cccccccc represents the load module.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the MVS Programming: Assembler Services Reference, Volume 1 or MVS Programming: Assembler Services Reference, Volume 2 for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a CSVQUERY error occurred while the ESD extractor was preparing to extract ESD information from module module_name in load library dsn during processing of request request_number. return_code represents return code for CSVQUERY.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the MVS Programming: Assembler Services Reference, Volume 1 or MVS Programming: Assembler Services Reference, Volume 2 for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates an IEWBIND error occurred while processing function ffff. The ESD extractor was extracting ESD information from modules in load library dsn allocated to ddnduring processing of request rrrr.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports.
Refer to the z/OS MVS Program Management: Advanced Facilities for information about the return and reason codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND GETE error occurred while the ESD extractor was extracting ESD information from module module_name in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for IEWBIND GETE.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND GETE error occurred while the ESD extractor was extracting ESD information from module module_name in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for IEWBIND GETE.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND GETE error occurred while the ESD extractor was extracting ESD information from module module_name in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for IEWBIND GETE.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND GETD error occurred while the ESD extractor was extracting ESD information from module module_name in load library dsn during processing of request request_number. module_name, return_code, and reason_code represent return and reason codes for IEWBIND GETE.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND GETD error occurred while the ESD extractor was extracting ESD information from module module_name in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for IEWBIND GETE.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND GETD error occurred while the ESD extractor was extracting ESD information from module module_name in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for IEWBIND GETE.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates a IEWBIND GETD error occurred while the ESD extractor was extracting ESD information from module module_name in load library dsn during processing of request request_number. return_code and reason_code represent return and reason codes for IEWBIND GETE.
None. Sampling continues, but the user might notice missing load module CSECT information in some of the reports
Refer to the DFSMS Program Management for information about the above error codes. Correct the problem and resubmit the request if necessary.
This message indicates that the ESD IRB detected invalid input parameters and could not proceed.
Sampling continues, but the user might notice missing load module CSECT information in some of the reports. The IRB will be abended.
Refer to the z/OS MVS Program Management: Advanced Facilities for information about the return and reason codes. Correct the problem and resubmit the request if necessary.
The identified HFS file could not be loaded into storage.
Processing continues, but no CSECT names, function names or compile time stamp information can be extracted.
Lookup the return code and reason code values in the z/OS UNIX System Services Messages and Codes manual to determine the reason for the failure.
A CSVQUESRY issued against the identified HFS file failed.
Processing continues, but no CSECT names, function names or compile time stamp information can be extracted.
Report this error to Application Performance Analyzer support.
The identified HFS file could not be deleted from storage.
Processing continues, but the program remains in memory in the started task address space.
Lookup the return code and reason code values in the z/OS UNIX System Services Messages and Codes manual to determine the reason for the failure.
Application Performance Analyzer attempted to open for input the file named by dsn, to extract external symbol information. The open failed due to a security violation. For more information, refer to the joblog for other system related messages.
Application Performance Analyzer continues processing the sample request. No symbol information will be available for any modules loaded from this file.
If external symbol information is required, grant read access to the affected file.
The ESD Extractor has detected an abend while processing a load module and will be terminating.
Application Performance Analyzer continues processing the sample request. Symbol information might be missing from some or all modules observed during this sample session.
Save both the dump and all started task output and then contact customer support.
XML documents can only be generated in the English language, and cannot be generated for the language indicated in language.
None. The XML document is not generated.
Either remove the LANG=language setting from the CONVERT statement, or change language to ENU and resubmit the print job.
This message is reported when the ESD extractor subtask assigned to request request_number has completed its shutdown process and is about to terminate.
None.
None.
Application Performance Analyzer detected an error while attempting to create a sampling data space for to request request_number. return_code and reason_code represent the DSPSERV CREATE return and reason codes.
The sampling request will not proceed.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the DSPSERV CREATE return and reason codes. Correct the problem and resubmit the sampling request.
Application Performance Analyzer detected an error while attempting to add a sampling data space ALET for to request request_number. return_code represents the ALESERV ADD return code.
The sampling request will not proceed.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the ALESERV ADD return and reason codes. Correct the problem and resubmit the sampling request.
A Host Variable Extractor subtask has started. This subtask resolves SQL host variable names as requested by the user on the Measurement Options panel (DB2V - SQL Variables option). The value for rrrr is the request number that the data writer has been assigned. The value for jjjjjjjj is the name of the Job, STC, or TSU being measured.
None.
None.
The SQL Host Variable Extractor subtask assigned to request rrrr has completed initialization and is now ready for work.
None.
None.
A required DB2 CAF load module could not be loaded from STEPLIB. mmmm - Message CAZmmmm has been issued for this error. Refer to this message for additional error information.
Sampling continues without SQL variable name resolution. Reports containing SQL text will not display host variable names.
Refer to message CAZmmmm for operator response.
An unexpected SQLCODE value was returned by DB2 for a SQL call made by Application Performance Analyzer during SQL host variable resolution.
Additional information is displayed after this message to identify the SQL error. aaaaaaaaaaaa identifies the SQL call that received the error.
Sampling continues. Depending on the SQL error, reports containing SQL text might not display host variable names.
Record the error location and the SQL error information that follows this message and contact product support.
This is a general information message used for diagnostic purposes by product support. The text of the message will vary depending on the diagnostic data to be presented.
None.
None.
During SQL host variable resolution, no corresponding rows were found in the DB2 catalog table SYSPACKSTMT for the SQL statement number identified by ssssssss. rrrr is the request number.
Sampling continues. Reports containing the SQL statement text for statement number ssssssss will not display host variable names.
Record the statement number and request number, and contact product support.
During SQL host variable resolution, no corresponding rows were found in the DB2 catalog table SYSSTMT for the SQL statement number identified by ssssssss. rrrr is the request number.
Sampling continues. Reports containing the SQL statement text for statement number ssssssss will not display host variable names.
Record the statement number and request number, and contact product support.
The data writer was unable to write one or more sample records to the sample data space. The data space was in the process of being expanded while the sample records were being added to the data space. These records were dropped to avoid overflowing the data space.
Sampling continues. Reports containing SQL text might not display all host variable names.
Record the statement number and request number, and contact product support.
The Host Variable Extractor (HVXT) subtask has exceeded its abend threshold. The subtask will detect and recover from an abend situation. This sequence of recovery will continue until the subtask reaches a threshold point, at which time the subtask will terminate.
Sampling continues, but the HVXT subtask terminates. Reports containing SQL text will may not display host variable names.
Collect failure information and contact product support.
The Host Variable Extractor (HVXT) subtask has detected an abend situation and cannot continue. A dump is produced and the subtask terminates.
Sampling continues, but the HVXT subtask terminates. Reports containing SQL text will may not display host variable names.
Collect failure information and contact product support.
The Host Variable Extractor (HVXT) subtask has detected a recurring error identified by error message aaaaaaaa. To prevent excessive output from being generated, the error message is suppressed.
See message aaaaaaaa.
See message aaaaaaaa.
This message is reported when the Host Variable Extractor subtask has completed its shutdown process and is about to terminate.
None.
None.
An error occurred while attempting to open the SYSPRINT data set. Possible cause: user omitted the SYSPINT DD statement from the JCL.
The step is terminated.
Review the job output for possible system messages related to this DD statement.
An error occurred while attempting to open the SYSIN data set. Possible cause: user omitted the SYSIN DD statement from the JCL.
The step is terminated.
Review the job output for possible system messages related to this DD statement.
An invalid EXEC parameter string was detected. Currently the only valid parameter is the STCID keyword and value.
The step is terminated.
Review the EXEC parameters to ensure that only an STCID keyword value pair is specified, for example: 'STCID=CAZ0'.
End of file was reached on the SYSIN data set prior to detecting the end of a command string.
Processing continues to the next command string.
Review the command string that preceded this message and ensure that it is terminated with a semicolon.
The command string that precedes this message contains a syntax error. Possible cause: command name that was not specified or the command name is not a known command.
Processing continues to the next command string.
Review the command string that preceded this message for errors.
No valid command strings were detected in the SYSIN input data set. This is a warning message and indicates that the Batch Interface did not find any valid commands to process.
The step is terminated.
Review the SYSPRINT output for error messages that might precede this message.
A SYSIN data set was specified but was found to be empty.
The step is terminated.
Ensure the SYSIN data set contains valid command strings.
The command that precedes this message has been successfully processed by the Application Performance Analyzer started task.
Processing continues to the next command string.
None.
The user did not specify an Application Performance Analyzer ID ('STCID=xxxx') keyword value pair and the Batch Interface attempted to use the Application Performance Analyzer ID that was currently active on the system. This was not possible since there were more than one active Application Performance Analyzer IDs on this system.
This message is followed by a list of active Application Performance Analyzer IDs. For example:
STCID | Version |
---|---|
CAZ1 | 1.100A |
CAZ2 | 1.100B |
CAZ3 | 1.100B |
CAZ4 | 1.100B |
The step is terminated.
Specify an STCID keyword value in the EXEC parameters.
The user specified an Application Performance Analyzer ID of aaaa. This ID was not active at the time the Batch Interface ran.
The step is terminated.
Ensure that Application Performance Analyzer started task is active when running the Batch Interface.
The user did not specify an STCID key value pair EXEC parameter; and the system had no Application Performance Analyzer ID defined to it for which the Batch Interface could use as a default ID.
The step is terminated.
Ensure that Application Performance Analyzer started task is active when running the Batch Interface.
The command that precedes this message failed to process successfully.
Processing continues to the next command string.
This message will be preceded by diagnostic messages that describe the cause of the failure.
This message indicates that the Batch Interface has completed processing and is terminating. return_code represents the highest return code detected during processing.
The step is terminated.
None.
The command string that precedes this message is too long for CAZBATCH's internal command buffer and cannot be processed.
Processing continues to the next command string.
Reduce the size of the command string by combining multiple input records for this command string into fewer records.
This message indicates that the Batch Import has completed and is terminating. return_code represents the highest return code detected during processing.
The step is terminated.
None.
An error condition was detected during the batch import. error_message can be one of the following:
The step is terminated.
Check that the data set being imported as the SAMPIN DD in the JCL is either a valid exported sample file or a valid sample file.
This is an informational diagnostic message indicating that the Common Dataset Store function: aaaa is starting.
None.
None.
The batch Import utility created an entry in the observation list for the import file, but was unable to open the data set for output to create the sample file.
The step is terminated.
Check for related error messages and security errors in the batch Import utility.
This message indicates a dynamic allocation error occurred while attempting to allocate the dataset_name for the Import function.
The step is terminated.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and resubmit the Import request.
SMS messages related to message CAZ3928E
The step is terminated.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and resubmit the Import request.
The Import request was successful for the named data set into request_number of the observation list.
The step is complete.
Use the Application Performance Analyzer ISPF front end to view the imported request.
Process aaaa detected an abend while processing the function described by bbbb. The function has failed, but the process has recovered successfully. The log will contain details of the abend and a dump might also have been produced.
None.
Report the problem to your systems programmer.
The import operation for the sample file described by input data set name: bbbb has begun. The requesting user is: aaaa. Whether the input data set will be deleted is indicated by c (Y/N).
None.
None.
A sample file described in message CAZ3933I has been successfully imported into Application Performance Analyzer. The sample file has been assigned to request number specified by aaaa.
None.
None.
An error was detected while processing the dataset specified by the DDName aaaa. bbbb describes the reason for the error.
The action related to this error message is failed.
Correct the dataset error described by the reason information.
An abend was detected while processing the Import request and an SVC dump was produced. Refer to the dump for the cause of the abend.
The Import request is failed.
Report the problem to your systems programmer.
The Import function is not supported by the STC whose ID is: aaaa. This is an internal error and user abend U4076 reason code 4 is generated.
The Import request is failed.
Report the problem to your systems programmer.
This is an informational diagnostic message indicating that the Common Dataset Store function: aaaa is has completed.
None.
None.
The Import request completed successfully. The original input Import dataset described by aaaa was successfully deleted as requested by the user.
None.
None.
An attempt to rename dsn-1 to dsn-2 failed with the return code specified by aaaa.
None. The operation causing the rename failed.
Contract product support.
During initialization, this message reports the name of the data set (dsn) Application Performance Analyzer will use for Common Data Store functions.
None.
None.
This is a generic message to describe internal errors. mod_name represents the module issuing the message and error_text represents the error that was detected.
Operation failed.
Contact product support.
A dynamic allocation error occurred while attempting to allocate the Common Data Store file. error_code, information_code, and reason_code represent the dynamic allocation error code, information code and SMS reason code, respectively.
The Common Data Store is disabled and unavailable.
Refer to the MVS Programming: Authorized Assembler Services Guide for information about the above error codes. Correct the problem and then restart Application Performance Analyzer.
This is a generic message that describes a file related error (in error_text) that occurred while accessing the Common Data Store.
The Common Data Store is disabled and unavailable.
Correct the problem based on the information provided by the error_text and then restart Application Performance Analyzer.
An open error occurred while attempting to open the dataset specified by dsn.
None.
Refer to the joblog for messages issued by the system. Correct the problem and restart Application Performance Analyzer.
This is an information message indicating that the PDSE specified by dsn is empty.
None.
None.
An error occurred while reading the dataset specified by dsn and member_name. return_code contains a internal error code that describes the error.
None.
Contact product support.
This is an information message indicating that the member specified by member_name, in dataset dsn, is empty.
None.
None.
An attempt to add a new member to the Common Data Store failed because the in core Common Data Store table is full.
None.
Contact product support.
A user attempted to access the Common Data Store member whose member name is mem-name, for which the user does not have access. All users can access members that match their TSO user IDs. Administrators can access all Common Data Store members.
The access is denied and the function is terminated.
Ensure that the user is authorized to access the member.
As part of a sample file Import function, the user also requested that the input dataset be deleted once the import was completed. However, the Application Performance Analyzer started task determined that it could not be deleted for the reason give in reason-text. The r1 and r2 values are internal codes used by product support. The input sample file will have been successfully created.
None.
Attempt to correct the problem based on the information provided in the reason-text and any additional message found in the job log. If this fails, then contact product support and provide them with the reason-text, r1, r2 values and any additional messages found in the STC's joblog.
This is an information message indicating the action that was applied to member: mem-name. The named action may be: 'added', 'replaced', or 'deleted'. The Common Data Store dataset is name by: dsn. The number of variables processed is specified by count.
None.
None.
An error was detected while performing the named Error_action: 'adding', 'replacing', or 'deleting' to the member: mem-name in the Common Data Store dataset: dsn. The STOW macro's return code and reason code are returned in rc and rsn, respectively.
The update operation is failed.
Correct the error based on the STOW return code and reason code.
An error was detected while reading the Common Data Store. The error is indicated by the return code (rc) and reason code (rsn). The failing program is indicated by Module (mod-name).
The operation is failed.
Check the Common Data Store SYSOUT dataset of the Application Performance Analyzer started task for additional error messages and contact product support.
An error was detected while writing the Common Data Store. The error is indicated by the return code (rc) and reason code (rsn). The failing program is indicated by Module (mod-name).
The operation is failed.
Check the Common Data Store SYSOUT dataset of the Application Performance Analyzer started task for additional error messages and contact product support.
The Application Performance Analyzer started task specified by ssss was unable to launch a J9VM for Java support, for the reason indicated by nnnn. This message is only displayed if J9VMEnable=YES is specified in the CONFIG file.
Processing continues but without J9VM support.
Contact product support.
This is a generic diagnostic message for J9VM support. These messages are displayed only when the DiagLevel configuration option is set to 9.
None.
None.
The Application Performance Analyzer JVMTI agent was unable to fetch the executable program named by xxxxxxxx.
The Application Performance Analyzer JVMTI agent terminates.
Ensure that the named Application Performance Analyzer module is in a link list dataset.
The Application Performance Analyzer JVMTI agent received an unexpected return value from its Assembler service module.
The Application Performance Analyzer JVMTI agent terminates.
Contact product support.
The Application Performance Analyzer JVMTI agent was invoked by more than one sampling request at the same time. Only one sampling request per address space is supported.
The Application Performance Analyzer JVMTI agent terminates.
Limit Java sampling requests to one per address space.
The Application Performance Analyzer JVMTI agent was invoked during the load phase of the Java VM. This is not supported. The agent must be loaded as a result of an attach request by the Application Performance Analyzer started task.
The JVM terminates.
Do not specify the Application Performance Analyzer JVMTI agent in the startup options of your Java job.
The Application Performance Analyzer JVMTI agent was unable to open a diagnostic file.
Sampling continues, but without JVMTI agent diagnostics.
Ensure that the /tmp directory exists and has appropriate permissions and available space.
The J9VM support subtask has been started. This occurs only if J9VMEnable=YES is specified in the configuration file.
None.
None
The J9VM support subtask is terminating.
None.
None
The USS file mode creation mask has been set to the hex value xxxxxxxx.
None.
None.
A request to change the USS current working directory has failed. The return code is aaaaaaaa and the reason code is bbbbbbbb.
The J9VM subtask terminates.
Lookup the return code and reason code in the UNIX System Services Messages and Codes manual. Determine if the error is a result of Application Performance Analyzer J9VM installation problems or incorrect parameters in the configuration file.
A USS request to spawn CAZJNI01 has failed. The return code is aaaaaaaa and the reason code is bbbbbbbb.
The J9VM subtask terminates.
Lookup the return code and reason code in the UNIX System Services Messages and Codes manual. Determine if the error is a result of Application Performance Analyzer J9VM installation problems or incorrect parameters in the configuration file. Make sure that CAZJNI01 has the APF authorization extended attribute set on.
A request to wait for CAZJNI01 to finish has failed. The return code is aaaaaaaa and the reason code is bbbbbbbb.
The J9VM subtask terminates.
Lookup the return code and reason code in the UNIX System Services Messages and Codes manual. Determine if the error is a result of Application Performance Analyzer J9VM installation problems or incorrect parameters in the configuration file. Make sure that the Application Performance Analyzer started task has the required USS permissions.
A request to clean up USS kernel resources failed. The return code is aaaaaaaa and the reason code is bbbbbbbb. This error can occur only when the Application Performance Analyzer started task is terminating.
The J9VM subtask continues its termination.
Lookup the return code and reason code in the UNIX System Services Messages and Codes manual. Determine if the error is a result of Application Performance Analyzer J9VM installation problems or incorrect parameters in the configuration file. Make sure that the Application Performance Analyzer started task has the required USS permissions.
Application Performance Analyzer was unable to reschedule a sampling SRB in the target address spaced specified by job job_name. return_code represents the IEAMSCHD return code.
The sampling request will be terminated. The sample might be unusable.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the IEAMSCHD return and reason codes. Correct the problem and resubmit the sampling request.
Application Performance Analyzer was unable to reschedule a sampling SRB in the target address spaced specified by job job_name and ASID identifier. Application Performance Analyzer has detected that the address space has terminated.
The sampling request will be terminated. The sample might be unusable.
Resubmit the sampling request.
Application Performance Analyzer was unable to reschedule a sampling SRB in the target address spaced specified by job job_name due to a system abend return_code. Abend summary information will follow in Message:
The sampling request will be terminated. The sample might be unusable.
Resubmit the sampling request.
This message contains abend summary information useful to product support. This message will be preceded by message CAZ4702S.
None.
Record these error messages and refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sampling SRB detected an error while attempting to add a sampling data space ALET. return_code represents the ALESERV ADD return code.
The sampling request will not proceed.
Refer to the MVS Programming: Authorized Assembler Services Reference for information about the ALESERV ADD return and reason codes. Correct the problem and resubmit the sampling request.
The sampling session attempted to establish a Resource Manager. The request failed for the reason describe by the RESMGR return coded specified by the hex value: aaaaaaaax.
Sampling continues, however under rare conditions sampling may be marked "incomplete" if sampling could not perform end of sampling functions.
Retry the sample request. Contact product support if the problem persists.
Application Performance Analyzer's Resource Manager has abended, recovered and terminated.
Normal step termination continues.
Save the SVC dump and contact product support.
The Data Extractor Module Resolution User Exit failed. The exit's return code (rc) and reason codes (rsn) are displayed in the message text. This message is displayed in the REQ#nnnn SYSOUT dataset in the Application Performance Analyzer started task. nnnn is the observation request number associated with the error. This error message may be accompanied by message: CAZ4881I.
None. Sampling continues. The user exit may not be called again, depending on the severity of the error.
Refer to Appendix D of the Application Performance Analyzer for z/OS Customization Guide for an explanation of the return and reason codes.
Optional error message text provided by the Data Extractor Module Resolution User Exit. This text describes the error reported by message: CAZ4880E. This message is displayed in the REQ#nnnn SYSOUT dataset in the Application Performance Analyzer started task. nnnn is the observation request number associated with the error.
None.
Contact the programmer who developed this program for an explanation of the return and reason codes.
This is an internal error.
The sampling request will not proceed.
If this problem persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
This is an internal error.
The sampling request will not proceed.
If this problem persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The version of CICS is not supported, Application Performance Analyzer cannot measure this CICS region.
The sampling request will not proceed.
Refer to the Application Performance Analyzer Program Directory to see which versions of CICS are supported.
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 terminates.
Correct the CONFIG DD statement or the configuration file.
Errors were encountered in CONFIG statements in the CONFIG file. Details of the error(s) follow in separate messages.
Application Performance Analyzer 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 error should also be accompanied by an AJTnnnn message providing additional details as well as a CAZ5205E message.
Processing 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.
Processing 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 CAZ5203E message and indicates which CONFIG object (object_name) was being processed when the error occurred.
Processing 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 CAZ5204E message and indicates which CONFIG object (object_name) was being processed when the error occurred.
Processing terminates.
Report the problem to product support.
This indicates that all statements in the CONFIG file were processed successfully.
Application Performance Analyzer continues initialization.
None.
The group name specified for SPXGroupName is the same as the name used to identify your Sysplex. This value is not allowed as an Application Performance Analyzer group name.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Customization Guide for information how to code this keyword value.
The parameter specified by aaaaaaaa was required and missing for the keyword specified by cccccccc in the CONFIG object named by bbbbbbbb.
Application Performance Analyzer terminates.
Correct the error in the CONFIG file and restart Application Performance Analyzer.
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 will also be accompanied by a CAZ5202E message.
Application Performance Analyzer 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 which provide information about the error.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Customization Guide for information about defining started task configuration settings.
This message indicates that a subsystem value of "*" was specified in other than the first occurrence of the DB2Explain keyword. If the DB2Explain keyword specifies a subsystem value of "*", then no further occurrences of the DB2Explain keyword are permitted.
Application Performance Analyzer teminates.
Correct the error in the CONFIG file and restart Application Performance Analyzer.
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 continues initialization.
None.
The record number indicates a CONFIG file record in which unrecognizable statement was encountered. A statement with the following syntax was expected: CONFIG jobname ...
Application Performance Analyzer terminates.
Correct the error in the CONFIG file and restart the job.
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 appear at the end of the expression.
Application Performance Analyzer terminates.
Correct the error in the CONFIG file and restart the job.
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 will be specified by value. This message might optionally display the invalid_value.
Application Performance Analyzer terminates.
Correct the error in the CONFIG file and restart Application Performance Analyzer.
The value specified for the UNIT keyword in the CONFIG BASIC object is not defined to the system.
Application Performance Analyzer terminates.
Correct the error in the CONFIG file and restart the job.
An EDTINFO error occurred validating the CONFIG BASIC UNIT value.
Application Performance Analyzer 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.
LogHLQ does not conform to DSN standards.
Application Performance Analyzer terminates.
Correct the LogHLQ parameter in the CONFIG file and restart the job.
This message indicates that a subsystem value of "*" was specified in other than the first occurrence of the DB2Explain keyword. If the DB2Explain keyword specifies a subsystem value of "*", then no further occurrences of the Explain keyword are permitted.
Application Performance Analyzer terminates.
Correct the error in the CONFIG file and restart Application Performance Analyzer.
This error can occur while attempting to extract source program mapping information from an assembly ADATA file. It indicates that no source type records (type X'0030') were found in the ADATA file or no Job ID (type X'0000') record was found. Either of these conditions probably indicate an invalid ADATA file.
The ISPF dialog is terminated.
Recreate the ADATA file by reassembling the program in error and retry the operation.
This error is raised if the requested map type is not recognized.
The ISPF dialog is terminated.
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 error is raised if a PROGRAM-ID statement could not be found in the requested COBOL source file. Application Performance Analyzer is unable to determine the CSECT name of the program if a PROGRAM-ID statement can not be found.
The ISPF dialog is terminated.
Ensure that a valid COBOL source listing was associated with the program. If not, correct the definition and retry the operation.
This error is raised if a compiler listing is empty or incomplete.
The ISPF dialog is terminated.
Ensure that a valid compiler listing was associated with the program. If not, correct the definition and retry the operation.
This error is raised if the type or version of the compiler cannot be recognized from the listing.
The ISPF dialog is terminated.
Ensure that a valid compiler listing was associated with the program. If not, correct the definition and retry the operation.
This error is raised if a compiler listing does not have the required options listed. For example, a COBOL program must be compiled with the SOURCE and (MAP or LIST) options.
The ISPF dialog is terminated.
Refer to the Application Performance Analyzer User's Guidefor information regarding the correct compiler options. Recompile your program with these options and retry the operation.
A PRINT control statement contained errors. record_number represents the input line number of the statement in error. This message will be followed by message CAZ5232E.
PRINT processing is terminated.
Correct the CAZCTL input and rerun the job.
A PRINT control statement specified an unknown report code in the SECTION statement. This message follows message: CAZ5231E.
PRINT processing is terminated.
Correct the CAZCTL input and rerun the job.
A PRINT control statement specified omitted the report code in the SECTION statement. This message follows message: CAZ5231E.
PRINT processing is terminated.
Correct the CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility
- CAZPRINT.
During its prescan of records specified to ddname CAZCTL,
CAZPRINT did not find any valid statements.
PRINT processing is terminated.
Correct the CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility
- CAZPRINT.
No PROFILE statement was found in the CAZCTL input file.
At least one PROFILE statement is required. A PROFILE statement specifies
a measurement file from which the report is to be produced.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. No SECTION statement was found in the CAZCTL input file. At least one SECTION statement is required. A SECTION statement specifies a section to be included in the performance analysis report.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility
- CAZPRINT.
No PRINT or CONVERT statement was found in the CAZCTL
input file. At least one PRINT or CONVERT statement is required PRINT
or CONVERT specifies a destination for the performance analysis report.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility
- CAZPRINT.
A SECTION statement was encountered in the CAZCTL input
file which was not preceded by a PROFILE statement. A PROFILE statement
specifies a measurement file from which the report is to be produced
and must appear before any corresponding SECTION statements.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility
- CAZPRINT.
A MAP statement was encountered in the CAZCTL input file
which was not preceded by a PROFILE statement. A PROFILE statement
specifies a measurement file from which the report is to be produced
and must appear before any corresponding MAP statements.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility
- CAZPRINT.
A PRINT statement was encountered in the CAZCTL input
file which was not preceded by a SECTION statement.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A PROFILE statement record_number, specified a slot number slot_number (01 to 99) which was already specified in a previous PROFILE statement. Each PROFILE statement must specify a unique slot value.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A SECTION statement record_number, specified a slot number (in its PROFILE=slot_number parameter) which was not previously specified in a PROFILE statement. A SECTION statement with the PROFILE=slot_number parameter omitted defaults to slot 01.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. The output file with the indicated ddname could not be opened. The ddname is specified in a PRINT statement and a corresponding DD statement must be included in the JCL.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A PRINT statement was encountered for which no corresponding SECTION statements were processed. SECTION statements must precede the PRINT statement.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. The output file with the indicated ddname could not be opened. The ddname is specified in a CONVERT statement and a corresponding DD statement must be included in the JCL.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A CONVERT statement was encountered for which no corresponding SECTION statements were processed. SECTION statements must precede the CONVERT statement.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A MAP statement record_number, specified a slot number slot_number in PROFILE=slot_number for which there was no corresponding PROFILE statement.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. The DSN parameter in a MAP statement specified a data set name which is syntactically incorrect.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. The MEMBER parameter in a MAP statement specified a PDS member name which is syntactically incorrect.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. The data set specified in the DSN parameter of a MAP statement was not found in the catalog.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A MAP statement specified a data set with an incorrect organization. This error can occur if the specified data set is partitioned and no MEMBER was specified in the MAP statement or if the data set is not partitioned and a MEMBER was specified in the MAP statement.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A MAP statement specified a source mapping data set which has already been processed by a previous MAP statement.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A map statement specified a PDS member which was not found in the specified library.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. Allocation of the data set specified in a MAP statement failed.
PRINT processing is terminated.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. This is an information message. It indicates that the source mapping data described in a MAP statement was successfully loaded and mapped to the indicated CSECT in the measurement data.
None.
None.
This message is issued by the printed report formatting facility - CAZPRINT. This message is a warning It indicates that source mapping data specified in a MAP statement was successfully loaded, but no data exists in the measurement file for program(s) mapped by this data.
None.
None.
This message is issued by the printed report formatting facility - CAZPRINT. This is a normal informational message indicating the initial prescan of CAZCTL statements was successful.
None.
None.
This message is issued by the printed report formatting facility - CAZPRINT. This is a normal informational message indicating the CAZCTL statements were syntax checked and no errors were found.
None.
None.
This message is issued by the printed report formatting facility - CAZPRINT. This message is a warning. A SECTION statement for source mapping reporting specified a program name in its PROGRAM= parameter for which no measurement data was found.
None.
Correct the JCL or CAZCTL input and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. This message is a warning. A SECTION statement for source mapping reporting specified a program name in its PROGRAM= parameter for which no source mapping data was specified in a MAP statement. This message is a warning.
None.
None.
This message is issued by the printed report formatting facility - CAZPRINT. This message is informational. It indicates that a report section section_name specified in a SECTION statement was omitted because the specific type of data pertaining to that report section does not exist in the measurement file. For example, a DB2 report section was specified but no DB2 activity was measured.
None.
None.
This error is raised during processing of a COBOL compile listing file. A line containing the text 'OPTIONS IN EFFECT:' or '*OPTIONS IN EFFECT*' in col 1 could not be found. This is the heading expected on a page containing information about compile options. The matching of this text is not case sensitive.
The COBOL compile listing file cannot be processed.
Check that the COBOL compile listing file is valid.
This error is raised during processing of a COBOL compile listing file. A line containing the text 'OPTIONS IN EFFECT:' or '*OPTIONS IN EFFECT*' was found and compile option information was extracted. Source lines were expected to be found in the listing file after the option information but no such records were found. The file might have been truncated in the middle of the compile options section. The end of this section is recognized by a record containing blanks in columns 1 to 4.
The COBOL compile listing file cannot be processed.
Check that the COBOL compile listing file is valid.
This error is raised during processing of a COBOL compile listing file. A line containing the text 'LINE # HEXLOC VERB' in col 1 could not be found in the listing file. This is the heading expected on a page containing PMAP offset information. The matching of this text is not case sensitive.
The COBOL compile listing file cannot be processed.
Check that the COBOL compile listing file is valid.
This error is raised during processing of a COBOL compiler listing file. A PMAP heading record containing 'LINE # HEXLOC VERB' was found, but EOF was encountered unexpectedly while processing PMAP detail lines. The file might have been truncated.
The COBOL compile listing file cannot be processed.
Check that the COBOL compile listing file is valid.
EOF was encountered in a COBOL source listing file within the first 3 records.
The COBOL compile listing file cannot be processed.
Check that the COBOL compile listing file is valid.
This error is raised during the prescan of a COBOL listing file if no line containing ' LINEID PL SL ' in col 1 is found. This is the heading expected on a page containing COBOL source statements. The matching is not case sensitive.
The COBOL compile listing file cannot be processed.
Check that the COBOL compile listing file is valid.
This message is the first a two part message. It indicates a validation error with class name specified by class_name. Refer to message CAZ5303E for details on this error.
Application Performance Analyzer terminates.
See message CAZ5303E.
This message accompanies CAZ5302E and provides details of the problem. Application Performance Analyzer attempted to verify the existence of the class name specified by Keyword: SecurityClassName by issuing the RACROUTE REQUEST=STAT service. This service failed with the errors specified.
Refer to the z/OS SecureWay Security Server External Security Interface (RACROUTE) Macro Reference for details on the following error codes:
Application Performance Analyzer terminates.
Correct the error based on the information provided by the error codes.
The named data set is not in the catalog, or the data set is in the catalog but not on the volume specified by the catalog entry.
The started task does not initialize.
Correct the data set name specified and restart the started task.
Parm ExtractorsOnByDefault in CAZCNFG0 member has an invalid extractor coded.
Application Performance Analyzer terminates.
Correct or remove the invalid parameter in ExtractorsOnByDefault and restart the Application Performance Analyzer started task. See the installation guide for valid extractor values.
Parm ExtractorsOnByDefault has DB2+ coded, but DB2I has not been enabled.
Application Performance Analyzer terminates.
Either set DB2I=Yes in the configuration or remove DB2+ from ExtractorsOnByDefault, then restart the Application Performance Analyzer started task.
Parm ExtractorsOnByDefault has DB2V coded, but DB2I has not been enabled.
Application Performance Analyzer terminates.
Either set DB2I=Yes in the configuration or remove DB2+ from ExtractorsOnByDefault, then restart the Application Performance Analyzer started task.
Parm ExtractorsOnByDefault has IMS+ coded, but IMSI has not been enabled.
Application Performance Analyzer terminates.
Either set IMSI=Yes in the configuration or remove IMS+ from ExtractorsOnByDefault, then restart the Application Performance Analyzer started task.
This message is issued by the printed report formatting facility - CAZPRINT. A CONVERT statement was encountered in the CAZCTL input file, which was not preceded by a SECTION statement.
CAZPRINT processing is terminated.
Correct the JCL or CAZCTL statements and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A PRINT statement was encountered in the CAZCTL input file after a CONVERT FORMAT=XML statement. A print file and XML document file cannot be requested in the same execution of the CAZPRINT facility.
CAZPRINT processing is terminated.
Correct the JCL or CAZCTL statements and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A CONVERT FORMAT=PDF statement was encountered in the CAZCTL input file after a CONVERT FORMAT=XML statement. A PDF file and XML document file cannot be requested in the same execution of the CAZPRINT facility.
CAZPRINT processing is terminated.
Correct the JCL or CAZCTL statements and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A CONVERT FORMAT=XML statement was encountered in the CAZCTL input file after a PRINT statement. An XML document file and a print file cannot be requested in the same execution of the CAZPRINT facility.
CAZPRINT processing is terminated.
Correct the JCL or CAZCTL statements and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A CONVERT FORMAT=XML statement was encountered in the CAZCTL input file after a CONVERT FORMAT=PDF statement. An XML document file and a PDF file cannot be requested in the same execution of the CAZPRINT facility.
CAZPRINT processing is terminated.
Correct the JCL or CAZCTL statements and rerun the job.
This message is issued by the printed report formatting facility - CAZPRINT. A CONVERT statement was encountered in the CAZCTL input file at record number record_number which specified an invalid value in its FORMAT parameter. The FORMAT parameter value specifies the format of the output file being requested. Valid formats are PDF (Portable Document Format) and XML (Extensible Markup Language).
CAZPRINT processing is terminated.
Correct the JCL or CAZCTL statements and rerun the job.
Explanation: Parm ExtractorsOnByDefault has CDB2 coded, but WLMI and DB2I have not been enabled.
Application Performance Analyzer terminates.
Either set both WLMI=Yes and DB2I=Yes in the configuration or remove CDB2 from ExtractorsOnByDefault, then restart the Application Performance Analyzer started task.
This message is issued by the printed report formatting facility CAZPRINT. It is a generic message that describes an error in the data specified in the indicated statement.
Step is terminated with a return code of 8.
Correct the statement in error and resubmit the job.
This message is issued by the printed report formatting facility CAZPRINT. It indicates that mutually exclusive keywords were specified in the indicated statement.
Step is terminated with a return code of 8.
Correct the statement in error and resubmit the job.
This message is issued by the printed report formatting facility CAZPRINT. It indicates that a required keyword was not specified in the indicated statement.
Step is terminated with a return code of 8.
Correct the statement in error and resubmit the job.
This message is issued by the printed report formatting facility CAZPRINT. It indicates that an attempt to open a file with a DDName of aaaa failed. Refer to the JES log for system related messages explaining this error.
Step is terminated with a return code of 8.
Correct the statement in error and resubmit the job.
This message is issued when an attempt to extend a dataspace failed. The reason code indicated by nnnn describes the failure.
The operation responsible for the error is terminated.
Contact product support.
Parm ExtractorsOnByDefault has CICS+ coded, but CICSI has not been enabled.
Application Performance Analyzer terminates.
Either set CICSI=Yes in the configuration or remove CICS+ from ExtractorsOnByDefault, then restart Application Performance Analyzer.
A maximum of 20 observations can be tagged for variance reporting. The JCL contains more than 20 tagged observations.
CAZPRINT processing is terminated.
Correct the JCL so the maximum of 20 TYPE=TAGGED PROFILE statements is not exceeded and resubmit the job.
This message is issued by CAZPRINT when called by the GUI to format and return detail report information. It indicates that an invalid internal value (ITAG) bbbb was specified. The record number on which the error occurred is aaaa.
The GUI request is failed.
None.
The keyword specified by aaaa was required and missing from the CONFIG object named by bbbbbbbb.
Application Performance Analyzer terminates.
Correct the error in the CONFIG file and restart Application Performance Analyzer.
Java sampling has been disabled for this request. Java sampling only permits one active Java sample session per address space at any one time. All other Java sample sessions will continue to sample but without the Java extractor enabled. The request number specified by aaaaa, represents the sample session that is currently actively sampling Java in the target address space.
None.
Wait until request aaaaa has completed, then resubmit your request. If the problem persists contact product support.
Java sampling has been disabled for this request. The concurrent number of active Java sampling sessions for the system has reached the architected limited. Your sample session will continue to sample but without the Java extractor enabled.
None.
Wait until one of the other Java sampling sessions has completed then resubmit your request. If the problem persists contact product support.
Application Performance Analyzer did not detect the presence of a Java Virtual Machine during sampling.
None.
Verify that Application Performance Analyzer has been configured to enable Java sampling. Verify that the target job is in fact a Java job. If not then turn off the Java Extractor on your sample request.
The JVMTI agent did not terminate as expected.
None.
Refer to target job's output or the Application Performance Analyzer started task output for any messages that may indicate a cause for the error. If the problem persists contact product support.
Upon completion of sampling no Java samples were taken. One possible reason may be that the JVMTI agent failed to load.
None.
Refer to target job's output or the Application Performance Analyzer started task output for any messages that may indicate a cause for the error. If the problem persists contact product support.
This message indicates that the XRS subtask has started the process of initializing.
Application Performance Analyzer continues initialization.
None.
This message indicates that the XRS subtask has completed initialization and is ready for work.
Application Performance Analyzer continues initialization.
None.
This message indicates that the XRS subtask has started its shutdown process.
None.
None.
This message indicates that the XRS subtask has completed its shutdown process and is terminating.
None.
None.
This message is reported when the XRS subtask has exceeded its abend threshold. The subtask will detect and recover from an abend situation. This sequence of recovery will continue until the subtask reaches a threshold point, at which time the subtask will terminate. At this point, reporting requests for DB2 EXPLAIN will fail until the start task is recycled.
None.
None.
The EXPLAIN request was for a SQL statement that belongs to a stored procedure. The EXPLAIN request did not identify the invoker of the stored procedure.
The request fails.
Report this error to Application Performance Analyzer support.
The EXPLAIN request did not identify a DB2 plan and did not identify a DB2 package for the SQL statement.
The request fails.
Report this error to Application Performance Analyzer support.
An unexpected SQLCODE value was returned by DB2 for a SQL call made by Application Performance Analyzer during the processing of an EXPLAIN request. Additional information is displayed after this message to identify the SQL error. If the error is for D0601 EXEC, then the requested SQL statement might not be valid for EXPLAIN processing.
The request fails.
Determine if the requested SQL statement is valid for EXPLAIN processing. Contact product support if you believe that the error is caused by Application Performance Analyzer.
The EXPLAIN request was for a SQL statement that runs on the DB2 subsystem identified by SQL_statement. This subsystem has not been listed for EXPLAIN processing in the configuration parameters of the started task.
The request fails.
Contact your system administrator to determine why the identified DB2 subsystem is not listed for EXPLAIN processing by Application Performance Analyzer.
The EXPLAIN request was for a SQL statement that belongs to a stored procedure. The EXPLAIN request did not identify the stored procedure name.
The request fails.
Report this error to Application Performance Analyzer support.
No corresponding row was found in the catalog table identified by row_identifier for the SQL statement specified in an EXPLAIN request.
The request fails.
Determine if the requested SQL statement is still valid for EXPLAIN processing. If the observation request identified by request_variable is old, the required row might no longer exist in the catalog. Contact product support if you believe Application Performance Analyzer caused the error.
The SQL statement selected for EXPLAIN exceeds the maximum size supported by Application Performance Analyzer.
The request fails.
None.
This message is reported when the XRS subtask detects that the requestors message version is incompatible with the servicing XRS. This error can occur when the ISPF front end requesting the DB2 Explain is at a different version than the Application Performance Analyzer started task servicing the request. Both components must be running at the same version level.
The values specified in the Diag keyword are as follows:
The request fails.
Contact your system administrator.
There is no PLAN_TABLE defined for the qualifier specified by qualifier_variable. If the qualifier is for the Application Performance Analyzer started task, then the installation of Application Performance Analyzer has not been completed properly. If the qualifier is for the statement being explained, then Application Performance Analyzer has been configured without automatic PLAN_TABLE creation for the DB2 subsystem to which the requested SQL statement belongs.
The request fails.
Notify your system administrator.
The EXPLAIN request did not identify a CURRENT PATH for the SQL statement.
The request fails.
Report this error to Application Performance Analyzer support.
The DB2 Explain Request Server subtask has detected an abend and recovered from it. The following diagnostic information is provided in the message:
The EXPLAIN request is failed.
Report this error to product support.
You are attempting to perform an EXPLAIN request for an SQL statement that executed on a system other than the one your are currently connected to through Application Performance Analyzer. This instance of Application Performance Analyzer is not part of a sysplex group and therefore cannot communicate your EXPLAIN request to the target for processing.
The request fails.
Report this error to your system administrator.
The sysplex output processor for the instance of Application Performance Analyzer that you are currently connected to is down and cannot process your request. The most likely cause for this message is that the OUTPUT processor has abended and could not recover.
The request fails.
Report this error to your system administrator.
The EXPLAIN request did not identify a USER AuthID for the SQL statement.
The request fails.
Report this error to Application Performance Analyzer support.
The EXPLAIN request was for a SQL statement that runs on the DB2 subsystem identified by aaaa, and the user submitting the request is identified by bbbbbbbb. The request was failed due to an error in the XRS subtask that occurred prior to this request being issued.
Typically this message indicates that a severe error has occurred in the XRS subtask and prevents it from processing any further work. Review error messages prior to this error message for the root cause.
None.
Contact your systems programmer.
This message indicates that the named component of Application Performance Analyzer has completed initialization and is ready for work.
Application Performance Analyzer continues initialization.
None.
This message is issued whenever the URSS subtask detects an abend. It contains abend summary information useful to product support.
The URSS subtask will attempt to recover from the abend.
Record these error messages and refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
This message indicates that the URSS subtask has started the process of initializing.
Application Performance Analyzer continues initialization.
None.
This message is reported when the URSS subtask has started its shutdown process.
None.
None.
This message is reported when the URSS subtask has completed its shutdown process and is about to terminate.
None.
None.
This message is reported when the URSS subtask has exceeded its abend threshold. The subtask will detect and recover from an abend situation. This sequence of recovery will continue until the subtask reaches a threshold point, at which time the subtask will terminate. This message will be preceded by numerous CAZ6106S messages.
Application Performance Analyzer terminates.
Attempt to restart Application Performance Analyzer.
The message indicates that the Sampling Request Monitor Subtask (SRMS) has started the process of initializing.
Application Performance Analyzer continues initializing.
None.
The message indicates that the Sampling Request Monitor Subtask (SRMS) has started the process of initializing.
Application Performance Analyzer continues initializing.
None.
The message indicates that the Sampling Request Monitor Subtask (SRMS) has started its shutdown process.
None.
None.
The message indicates that the Sampling Request Monitor Subtask (SRMS) has completed its shutdown process and is about to terminate.
None.
None.
The message indicates that the Sampling Request Monitor Subtask (SRMS) has exceeded its abend threshold. The subtask will detect and recover from abend situations. This sequence of recovery will continue until the subtask reaches a threshold point, at which time the subtask will terminate. At this point Threshold Monitoring will cease until the started task is recycled.
None.
Report this error to Application Performance Analyzer support.
During initialization, the Sampling Request Monitor Subtask (SRMS) detected a size mismatch of one of its internal structures. SRMS will terminate. At this point Threshold Monitoring will cease until the started task is recycled.
None.
Report this error to Application Performance Analyzer support.
The Sampling Request Monitor subtask (SRMS) detected a syntax error with the contents of the TMSEL keyword for a newly added monitor request. Due to this error the monitoring request could not be added. Refer to message CAZ6207E for details of the parsing error.
None.
Report this error to Application Performance Analyzer support.
This message accompanies message: CAZ6206E and contain diagnostic information detailing the cause of the parsing error.
Refer to CAZ6206E.
Refer to CAZ6206E.
The message indicates that the Sampling Request Monitor Subtask (SRMS) has an abend situation from which it cannot recover. SRMS will terminate with a dump. At this point Threshold Monitoring will cease until the started task is recycled.
None.
Report this error to Application Performance Analyzer support.
The message indicates that the Sampling Request Monitor Subtask (SRMS) has detected an error with one of its internal processes. This message might be followed by one or more AJT messages. SMRS will terminate. At this point Threshold Monitoring will cease until the started task is recycled.
None.
Report this error to Application Performance Analyzer support.
The Application Performance Analyzer command processor detected a syntax error with the contents of the TMSEL keyword from the TNEW or TMOD command. One or more messages will follow this message and will provide details on the parsing error.
None.
Correct the parsing error, resubmit the command.
This message indicates that the sysplex input message subtask has started the process of initializing.
Application Performance Analyzer continues initialization.
None.
This message indicates that the named component of Application Performance Analyzer has completed initialization and is ready for work.
Application Performance Analyzer continues initialization.
None.
The Application Performance Analyzer sysplex messaging system has received a message from another member of the group. The message is not compatible with this version of Application Performance Analyzer.
The message is rejected.
Ensure that all members of the Application Performance Analyzer group are at the correct release levels.
Application Performance Analyzer could not validate an input message from another SYSPLEX group member. A possible cause for this is that Application Performance Analyzer has joined the wrong group.
Application Performance Analyzer teriminates.
Correct the value of SPXGroupName in CONFIG BASIC and restart Application Performance Analyzer.
The Application Performance Analyzer sysplex messaging system has received a message with an unsupported MNPLTYPE.
The message is rejected.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system has received a solicited message.
The message is rejected.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system detected an incorrect record type in the MNPL structure.
The message is rejected.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system detected an incorrect Target/Response type in the data record.
The message is rejected.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system detected a Data record with no Target/Response entries.
The message is rejected.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system detected that the MNPL message control field did not contain the address of an XMsg Response Message.
The message is rejected.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system detected that the MNPL message did not contain any Data Records.
The message is rejected.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system either received no response or a partial response. A message was sent to one or more members of a Application Performance Analyzer sysplex group and the message was timed out before all members could respond. Or, a system replied with a partial response due to the volume of data. This problem might occur if any of the targeted members was down.
The message is accepted.
Ensure that the Application Performance Analyzer member is running on the named system(s).
The Application Performance Analyzer sysplex messaging system either received no response or a partial response. A message was sent to one or more members of a Application Performance Analyzer sysplex group and the message was timed out before any member could respond. Or, a system replied with a partial response due to the volume of data. This problem might occur if all of the targeted members were down.
none.
Ensure that the Application Performance Analyzer member is running on all intended systems.
This message is reported when the sysplex input message subtask has started its shutdown process.
None.
None
This message is reported when the sysplex input message subtask has completed its shutdown process and is about to terminate.
None.
None.
This message indicates that the sysplex output message has started the process of initializing.
Application Performance Analyzer continues initialization.
None.
This message indicates that the named component of Application Performance Analyzer has completed initialization and is ready for work.
Application Performance Analyzer continues initialization.
None.
A sysplex message could not be sent to other instances of Application Performance Analyzer within the sysplex group because other instances were not active. aaaaaaaa is the target system or systems to receive the request.
The message is rejected.
If all other instances of Application Performance Analyzer within the sysplex group are active and the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system detected an error while sending a message to one or more group members.
Nne.
If the message persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
The Application Performance Analyzer sysplex messaging system detected a timeout while attempting to send a response message to a requesting member. The receiving member might be missing data.
None.
If the error persists contact Application Performance Analyzer support.
This message is reported when the sysplex output message subtask has started its shutdown process.
None.
None
This message is reported when the sysplex output message subtask has completed its shutdown process and is about to terminate.
None.
None.
This message indicates that the named component of Application Performance Analyzer has abnormally ended (ABEND). This message will be followed by a dump.
Application Performance Analyzer terminates.
The data write was unable to write one or more sample records to the sample data space. The data space was in the process of being expanded while the sample records were being added to the data space. These records were dropped to avoid overflowing the data space. module_name represents the module that detected this condition.
None. Sampling continues, but the user might possibly notice sampling errors in some of the reports only if this message appeared continuously throughout the sampling session.
If this problem persists, refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
This is an internal error. An unexpected error occurred in module CAZC0006.
Application Performance Analyzer terminates.
Record the return code return_code, then refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
This a warning message advising the user that Application Performance Analyzer will expire soon.
None.
Under normal circumstances, a new password will be supplied by your local IBM Sales Representative in plenty of time to prevent product expiry warning messages being issued. Therefore, if this occurs, it usually means that a password has already been supplied but not yet applied, or a password has been applied incorrectly. In such cases, the following should be checked:
Is the product running on the CPU for which it was generated? This is especially relevant when running under the VM operating system. IBM software only checks the last four digits of the CPU id, so the first two digits might be used to retain uniqueness.
If the password is applied by updating a parameter list, is there a duplicate statement containing the old password? If so, delete it. Has the new password supplied by IBM been applied correctly?
Application Performance Analyzer Product license has expired. Your system programmer will have to contact product support for a new password.
Application Performance Analyzer terminates.
Contact your system programmer for a new password.
A password CVSET value could not be found in the configuration module.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Customization Guide for information about installation-level configuration settings.
A password CVSET value specified in the configuration module was not valid. Probable cause is an incorrect password.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Customization Guide for information about Installation-level configuration settings.
Your are attempting to execute Application Performance Analyzer on a CPU for which you are not licensed. Contact your system programmer to determine the CPU for which Application Performance Analyzer is licensed. If the CPU is licensed then verify that the password value specified in the configuration module is correct.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Customization Guide for information about Installation-level configuration settings.
Your are attempting to use a Application Performance Analyzer feature for which you are not licensed. Verify that the password value specified in the configuration module is correct. feature_n represents the feature(s) not licensed.
Application Performance Analyzer terminates.
Refer to the Application Performance Analyzer Customization Guide for information about Installation-level configuration settings.
An internal error was detected while validating the Application Performance Analyzer product license.
Application Performance Analyzer terminates.
Record the reason code value, then refer to the Application Performance Analyzer technical support Web site at www.ibm.com/software/awdtools/apa/support/ to find possible solutions to this problem.
While sampling an address space, the sampling engine detected that system wide auxiliary storage utilization has exceeded a tolerable threshold (60%) and the sampling session is terminated.
The sampling engine records measurement data to a data space while sampling is active. A sampling data space can grow to a maximum size of 2GB, which is backed by auxiliary storage. Auxiliary storage shortages can cause severe performance degradation. The sampling engine monitors auxiliary storage utilization from the start of sampling. If at any time during sampling the threshold is exceeded, sampling is terminated.
Application Performance Analyzer sampling monitors system wide auxiliary storage utilization, therefore exceeding the threshold might or might not be the result of a sampling session. If the error occurs early on in the sampling session then it is very likely that auxiliary storage utilization was near or at the threshold at the time sampling started.
The sampling request is terminated and marked as "Cancel".
Request that your system programmer add more page data sets.
An internal table used to capture sampling information has exceeded the maximum size of 16MB. For diagnostic purposes the table name is given by: aaaa.
The sampling request is terminated and marked as "Failed".
Reduce the sampling duration and rate to attempt to avoid the situation.
The Application Performance Analyzer IEFUSI exit has abended too many times and has disabled itself to prevent further abends. The exit will tolerate three abends before disabling itself.
Application Performance Analyzer can no longer sample non-active jobs.
Search the system log for message ID: CAZ9013E. Note the times of these messages, produce a logrec report, and contact product support.
The Application Performance Analyzer IEFUSI exit has abended and recovered. The job step will not be affected. However, if this job was targeted for sampling then it may not be sampled.
None.
Note the time of this message, produce a logrec report, and contact product support.
[ Top of Page | Previous Page | Next Page | Contents ]