Before using this information and the product it supports, read the information in Appendix. Notices.
This edition applies to WebSphere Studio Asset Analyzer for Multiplatforms version 4.1.0 and to all subsequent releases and modifications until otherwise indicated in new editions.
You can order publications through your IBM(R) representative or the IBM branch office serving your locality.
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
This book contains the messages returned by various components of WebSphere Studio Asset Analyzer. It explains each message, the action the system takes when the message is issued, and the action users should take in response to each message.
This book is organized into two parts:
Messages and Codes is designed to be used by anyone using WebSphere Studio Asset Analyzer and requiring more detailed information about returned messages.
This book assumes that you are familiar with the functions of the operating system where WebSphere Studio Asset Analyzer is installed. You can use the information contained in this book to identify an error or problem and resolve the problem using the appropriate recovery action. This information can also be used to understand where messages are generated and logged.
WebSphere Studio Asset Analyzer messages consist of a message identifier followed by message text. The message identifier consists of a three-character message prefix, a four-digit message number and a single letter describing the severity of the message: XXXnnnnS.
Information provided for each message includes the following:
When running other programs on the system, you might receive messages with prefixes other than those mentioned in this reference. For information on these messages, refer to the publications that you received for that program product.
This chapter describes all messages and codes generated by the WebSphere Studio Asset Analyzer MVS components.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
An error occurred while reading from file filename. Improper file access authority is the likely cause.
The scanner skips the current file, and processing continues.
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
Unsupported syntax has been found at token in line number.
Scanning terminates for the current file, and processing continues.
Correct the source file for proper PL/I or COBOL syntax; reattempt the analysis.
COBOL and PL/I scanner
Unsupported syntax has been found at token in line number of copy or include file filename.
Scanning terminates for the current file, and processing continues.
Correct the copy or include file for proper COBOL or PL/I syntax; reattempt the analysis.
COBOL and PL/I scanner
An assignment to something that is not a data item, such as a figurative constant, has been found on line number. This message occurs for COBOL components only.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
This is an internal error of the application.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The specified source file cannot be opened.
Check that the file name is correct; reattempt the analysis.
COBOL and PL/I scanner
The data item used in line number of the source file is not declared within the DATA DIVISION. This message occurs for COBOL components only.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
The source program doesn't have any executable statements.
Scanning terminates for the current file, and processing continues.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
The PROCEDURE division of the file cannot be located. This message occurs for COBOL components only.
Scanning terminates for the current file and processing continues.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
Unsupported syntax has been found in line number of the source file filename.
Correct the syntax in the source file; reattempt the analysis.
COBOL and PL/I scanner
Unsupported syntax has been found in line number of the copy or include file filename. This message occurs for PL/I components only.
Correct the syntax in the copy or include file; reattempt the analysis.
COBOL and PL/I scanner
On line number in the source program, there is an assignment to a name that is not declared as a data item. This message occurs for COBOL components only.
The scanner ignores this assignment and continues processing.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
The copy file (for COBOL components) or include file (for PL/I components) filename could not be found. This error may be caused by an incorrect analysis option or a network problem.
Check the copy file extension or search directory specification of the analysis option. Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
The copy file (for COBOL components) or include file (for PL/I components) referred to in line number could not be found. This error may be caused by an incorrect analysis option.
Check the copy file extension or search directory specification of the analysis option. Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
The name defined as the call interface on line number has been used, but there is no parameter corresponding to the defined function parameter.
This scanner ignores the call and continues processing.
Correct the call interface definition; reattempt the analysis.
COBOL and PL/I scanner
The size of the data item declared on line number cannot be calculated. The data item is assumed to be 1 byte.
The scanner assumes a size of 1 byte for the data item and continues processing.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
Line number defines a redefinition of the data item specified, but there is no data item. This redefinition will be disregarded. This message occurs for COBOL components only.
The scanner ignores the REDEFINES clause and continues processing.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
The process procedure name on line number has been referenced, but name cannot be found. This message occurs for COBOL components only.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
The built-in function or routine used in line number cannot be processed. The function name or routine name may be incorrect.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
The include file filename could not be found. This error may be caused by an incorrect analysis option. This message occurs for PL/I components only.
Check the include file extension and the search directory specification of the analysis option. Correct the problem; reattempt the analysis.
COBOL and PL/I scanner
The include file referred to in line number could not be found. This problem may be caused by an incorrect analysis option. This message occurs for PL/I components only.
Check the include file extension and the search directory specification of the analysis option. Correct the problem; reattempt the analysis.
COBOL and PL/I scanner
The definition of name cannot be processed. This message occurs for PL/I components only.
The source file may be wrong. Correct the syntax, if necessary, and reattempt the analysis.
COBOL and PL/I scanner
The line indicated contains an EXEC statement other than EXEC SQL, EXEC CICS, or EXEC DLI.
The scanner ignores the EXEC statement and continues processing.
None
COBOL and PL/I scanner
This is an internal error of the application.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
Multiple declarations for the data item referenced in line number have been found. This message occurs for PL/I components only.
Correct the source program; reattempt the analysis.
COBOL and PL/I scanner
File filename has been referenced, but there is no DD name for it. This message occurs for COBOL components only.
Correct the source program; reattempt the analysis.
COBOL and PL/I scanner
The file filename is not declared. This message occurs for COBOL components only.
Correct the source program; reattempt the analysis.
COBOL and PL/I scanner
An element that is not a data item or an array element has been specified in the DEFINE clause of the data item shown. This message occurs for PL/I components only.
The scanner ignores the DEFINE clause and continues processing.
If, during impact analysis, you find that the data item shown in the message is affected, you should check the above item. Correct the DEFINE statement; reattempt the analysis.
COBOL and PL/I scanner
A token of more than 256 characters has been found on line number. Probably the closing apostrophe ( ' ) in the literal has been omitted.
Correct the source file; reattempt the analysis.
COBOL and PL/I scanner
This is an internal error of the application.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner has begun the parsing process for program name at the time indicated.
The system is functioning normally.
None
COBOL and PL/I scanner
The scanner has successfully completed the parsing process for program name at the time indicated.
The system is functioning normally.
None
COBOL and PL/I scanner
The scanner has completed the parsing process for program name at the time indicated, but the scanner has issued a warning.
Investigate the warning message, and, if necessary, reattempt the analysis. This warning message means that the analysis was completed; therefore you can display charts and other information.
COBOL and PL/I scanner
The parsing process for program name has failed in mid-execution at the time indicated.
Investigate the specific cause from other reported error messages. Correct the syntax; reattempt the analysis.
COBOL and PL/I scanner
The start parameter shown is wrong.
Correct the error; reattempt the analysis.
COBOL and PL/I scanner
There is an error in the specification of the source file that is the analysis target in the start parameter of the analysis program.
Correct the specification of the target; reattempt the analysis.
COBOL and PL/I scanner
The file shown cannot be opened. Possible causes are:
Correct the cause; reattempt the analysis.
COBOL and PL/I scanner
An error occurred while reading the file shown. This error may be caused by network problems.
Correct the cause; reattempt the analysis.
COBOL and PL/I scanner
An error occurred while reading the analysis option file. This error may be caused by a network problem or a syntax error in the analysis option file. This error occurs only on the Windows version of WebSphere Studio Asset Analyzer.
Processing stops.
Correct the problem; reattempt the analysis
COBOL and PL/I scanner
Either a language level for the extension of the file shown has not been specified or the specification is wrong.
Correct the analysis option; reattempt the analysis.
COBOL and PL/I scanner
An error occurred while reading the interface information file of the program shown. This error may be caused by a network problem.
The scanner skips the current file and processing continues.
Resolve the problem; reattempt the analysis
COBOL and PL/I scanner
The source file shown could not be found.
Correct the source program specification; reattempt the analysis.
COBOL and PL/I scanner
An error occurred in writing the interface information file of program name to a file. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred in writing the detailed information of program name to a file. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred while reading the detailed information of program name from a file. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred while writing the analysis summary information of program name to a file. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred while reading the analysis summary information of program name from a file. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
The directory specified could not be created. Possible causes of this error include:
This error occurs only on the Windows version of WebSphere Studio Asset Analyzer.
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred while reading the program list information of the program shown from a file. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred while writing the analysis option file. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
The entry name defined in program name1 is also defined in program name2. This error occurs only on the Windows version of WebSphere Studio Asset Analyzer.
The analysis result of program name1 is cancelled because it is overwritten.
Analyze the two programs as separate groups.
COBOL and PL/I scanner
An error has occurred while creating the import file directory. Possible causes of this error include:
This error occurs only on the Windows version of WebSphere Studio Asset Analyzer.
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred while writing the list of programs. Possible causes of this error include:
Resolve the problem; reattempt the analysis.
COBOL and PL/I scanner
An error has occurred while writing the import file. This error may have occurred because the application does not have proper authority to access the directory.
Resolve the problem; reattempt the analysis.
BMS macro definition scanner, File classification scanner, Impact analysis, JCL scanner
This message provides white space when a series of messages is generated, allowing the messages to be more easily read.
The system is functioning normally.
None
BMS macro definition scanner, JCL scanner
This message is the first in a series of six that report a copyright notice.
The system is functioning normally.
None
BMS macro definition scanner, JCL scanner
This message is the second in a series of six that report a copyright notice.
The system is functioning normally.
None
BMS macro definition scanner, JCL scanner
This message is the third in a series of six that report a copyright notice. The message text variable year indicates the copyright year(s).
The system is functioning normally.
None
BMS macro definition scanner, JCL scanner
This message is the forth in a series of six that report a copyright notice.
The system is functioning normally.
None
BMS macro definition scanner, JCL scanner
This message is the fifth in a series of six that report a copyright notice.
The system is functioning normally.
None
BMS macro definition scanner, JCL scanner
This message is the sixth in a series of six that report a copyright notice.
The system is functioning normally.
None
JCL scanner
This message occurs in debug mode only. The string pointer is null, and the job has stopped due to an assert error.
Processing stops.
Contact your IBM technical-support representative.
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
Code extraction, Impact analysis, JCL scanner
This message is an informational echo of parameter(s), user data, return code, and so on. This message provides additional information for interpreting other error messages.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
Analysis queue processor, DB2 catalog scanner
This message is informational status data.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
Impact analysis
This message is an informational banner.
The system is functioning normally.
None
DB2 catalog scanner, Impact analysis, Import record loader, Queue processor
Connect to database failed.
Processing stops.
Verify the database name, user ID and password are correct; try the operation again.
Impact analysis
Following disconnect from the database, a CONNECT RESET request failed.
The system is functioning normally.
Locate message DMH1101I for SQLSTATE information.
Impact analysis
This message provides a return code from DB2 following an SQL operation.
SQLCODE values can be the following:
The system is functioning normally.
Refer to the DB2/SQL messages and codes reference for more information.
Impact analysis
This message is an informational banner.
The system is functioning normally.
None
DB2 catalog scanner, Impact analysis, Import record loader, Queue processor
Unexpected error messages were returned from DB2; processing will continue, however.
The system is functioning normally.
None. It is recommended, however, that you check the local log file and review the error message(s) reported between the report header (DMH1110) and footer (DMH1114) messages.
Impact analysis
This is an informational message indicating CONNECT TO DATABASE name has been issued.
The system is functioning normally.
None
Impact analysis
This is an informational message indicating CONNECT TO DATABASE name was successful.
The system is functioning normally.
None
Impact analysis
This is an informational message indicating CONNECT RESET has been issued.
The system is functioning normally.
None
DB2 catalog scanner, Import record loader
This message provides informational status data.
The system is functioning normally.
None. When paired with message DMH2114, this message provides additional detail data.
File classification scanner
Analysis of key words and other file characteristics has identified the file to be of type filetype. Valid types include: COBOL, PLI, ASM, ASM (BMS macro), ASM (DBDGEN), ASM (PSBGEN), Easytrieve, and JCL.
The system is functioning normally.
None
File classification scanner
This message provides informational status indicating the container and file currently being processed.
The system is functioning normally.
None
File classification scanner
Based on analysis of key words and other file characteristics, the file type could not be automatically determined. filetype will generally be identified as UNKNOWN in the message text. Additionally, from the browser interface, on the File details page, UNK? will be indicated in the Language/type field and Incomplete in the Analysis status field. Other valid types for this message include EMPTY (the file contained zero records) and GONE (the file was not found in the container).
The system is functioning normally.
Review the file and determine the language. From the browser interface, on the File details page, select Assign new language from the Actions drop-down list to update the file's language.
File classification scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
File classification scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
File classification scanner
The file cannot be opened. Possible causes are:
The scanner skips the current file, and processing continues.
Verify and correct the cause; try the operation again.
File classification scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
File classification scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
BMS macro definition scanner, File classification scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
File classification scanner
This is an internal error of the application.
Processing is stopped.
Contact your IBM technical-support representative.
File classification scanner
This is an internal error of the application.
Processing is stopped.
Contact your IBM technical-support representative.
File classification scanner
This is an internal error of the application.
Processing is stopped
Contact your IBM technical-support representative.
BMS macro definition scanner, File classification scanner, IMS DBD scanner, IMS PSB scanner
The file cannot be opened. The DD statement for ATTRBOUT is a temporary data set established to hold WebSphere Studio Asset Analyzer import records. Possible causes are:
Processing is stopped.
Verify and correct the cause; try the operation again.
Code extraction, File classification scanner
This message occurs in debug mode only. While reading the input file, WebSphere Studio Asset Analyzer found an invalid character on the line and in the column specified. The invalid characters (usually within literal strings) are converted to a period (.) character to allow scanning to continue. On z/OS, the set of invalid characters are 0x00 through 0x3F and 0xFF. On the workstation, the only invalid character is 0x00. This character corresponds to the same set found on z/OS when using the FIND P'.' command in ISPF.
Scanning terminates for the current file, and processing continues.
Correct the file; try the operation again.
JCL scanner
WebSphere Studio Asset Analyzer supports the following container name maximum lengths: MVS = 44, workstation = 254.
Scanning terminates for the current file, and processing continues.
Reduce the length of the container name; try the operation again.
JCL scanner
WebSphere Studio Asset Analyzer supports the following file name length maximums: MVS = 10, workstation = 254.
Scanning terminates for the current file, and processing continues.
Reduce the length of the file name; try the operation again.
JCL scanner
No JCLLIB statement was specified in the JCL, or the data set specified for JCL INCLUDEs or procedures could not be opened. WebSphere Studio Asset Analyzer will use its own default JCLLIB concatenation list (for example, DD DUMMY).
Processing continues.
No action is required if there are no INCLUDEs or procedures named in EXEC statements to be found. Otherwise, identify a valid concatenation set and try the operation again. Concatenation sets are located in &hlq.USER.INCL2, where &hlq represents the high-level qualifier for WebSphere Studio Asset Analyzer user data sets specified at the time of installation. Contact your WebSphere Studio Asset Analyzer administrator.
JCL scanner
The WebSphere Studio Asset Analyzer container concatenation maximum is 32. The number of containers specified for JCLLIB DD * exceeds this limit.
Scanning terminates for the current file, and processing continues.
Reduce the number of containers; try the operation again.
JCL scanner
WebSphere Studio Asset Analyzer supports the following container name maximum lengths: MVS = 44, workstation = 254.
Scanning terminates for the current file, and processing continues.
Reduce the length of the container name; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer container concatenation maximum is 32. The number of containers specified in the JCLLIB ORDER= statement cannot exceed this limit.
Scanning terminates for the current file, and processing continues.
Reduce the number of containers listed in the JCLLIB ORDER= statement; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer nested source file limit is 15. The processing of INCLUDE statements has exceeded this limit.
Scanning terminates for the current file, and processing continues.
Reduce the nesting level; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer include and procedure source file maximum is 200. The number of unique referenced source files cannot exceed this limit.
Scanning terminates for the current file, and processing continues.
Reduce the number of unique referenced source files; try the operation again.
JCL scanner
WebSphere Studio Asset Analyzer supports the following file name length maximums: MVS = 10, workstation = 254.
Scanning terminates for the current file, and processing continues.
Reduce the length of the file name; try the operation again.
JCL scanner
The JCL scanner detected a reference to an INCLUDE or PROC named name, and it was not found by searching the JCLLIB concatenation set of containers, if specified, or the user concatenation set of containers, if specified. This condition can also result if no explicit concatenation set was specified and more than one existing concatenation set could resolve the file reference. If that is the case, this message would be preceded by DMH1776W.
The scanner continues processing.
Verify the location of the named INCLUDE or PROC and ensure its container is represented in a concatenation set known to WebSphere Studio Asset Analyzer. This representation can be accomplished either by using a JCLLIB concatenation set of containers in the JCL or by identifying a user concatenation set of containers assigned to the container or file being processed.
BMS macro definition scanner, JCL scanner
The container name was not found in the input parameters, or it is an invalid container name.
The scanner skips the current file, and processing continues.
Contact your IBM technical-support representative.
BMS macro definition scanner, JCL scanner
The file name was not found in the input parameters, or it is an invalid file name.
The scanner skips the current file, and processing continues.
Contact your IBM technical-support representative.
JCL scanner
The container and member specified for the INFILE DD could not be opened. Possible causes are:
The scanner skips the current file, and processing continues.
Verify and correct the cause; try the operation again.
JCL scanner
An expected comment continuation was not found. The JCL being analyzed included a comment continuation flag in column 72, but the next statement was not a valid comment.
Scanning terminates for the current file, and processing continues.
Verify the JCL comment statement is continued correctly. To continue a comment:
Verify and correct the syntax; try the operation again.
JCL scanner
An expected continuation of comment was not found. The last statement in the JCL contained a comment continuation flag.
Scanning terminates for the current file, and processing continues.
Verify the JCL comment statement should be continued. To continue a comment:
Verify and correct the syntax; try the operation again.
JCL scanner
An expected continuation of the parameter field was not found. The parameter field ended with a comma, but the parameter was not continued on the next non-comment line.
Scanning terminates for the current file, and processing continues.
Verify the parameter field is continued correctly. To continue a parameter field:
Verify and correct the syntax; try the operation again.
JCL scanner
An expected continuation of the parameter field was not found. The continuation of a parameter field was not found by column 16, and is therefore invalid.
Scanning terminates for the current file, and processing continues.
Verify the parameter field is continued correctly. To continue a parameter field:
Verify and correct the syntax; try the operation again.
JCL scanner
Expected continuation for parameter fields enclosed in apostrophes was not found. A parameter enclosed in apostrophes was continued and the continuation record is less than 16 characters.
Scanning terminates for the current file, and processing continues.
Verify the parameter field is continued correctly. To continue a parameter field enclosed in apostrophes:
Verify and correct the syntax; try the operation again.
JCL scanner
The DLM=delimiter did not specify the required two characters to indicate the end of this data set in the input stream.
Scanning terminates for the current file, and processing continues.
Verify the DLM=delimiter subparameter specifies two characters. Enclose special characters--any character that is neither alphanumeric nor national--in apostrophes. If the delimiter contains an ampersand or an apostrophe, code each ampersand or apostrophe as two consecutive ampersands or apostrophes. Each pair counts as one character. Verify and correct the syntax; try the operation again.
JCL scanner
The DLM=delimiter did not specify the required two characters to indicate the end of this data set in the input stream.
Scanning terminates for the current file, and processing continues.
Verify the DLM=delimiter subparameter specifies two characters. Enclose special characters--any character that is neither alphanumeric nor national--in apostrophes. If the delimiter contains an ampersand or an apostrophe, code each ampersand or apostrophe as two consecutive ampersands or apostrophes. Each pair counts as one character. Verify and correct the syntax; try the operation again.
JCL scanner
The DLM=delimiter did not specify the required two ampersands.
Scanning terminates for the current file, and processing continues.
Verify the DLM=delimiter subparameter contains a pair of ampersands for each intended single occurrence. Each pair of ampersands counts as one character. Verify and correct the syntax; try the operation again.
JCL scanner
The JOB statement is expected to be the first statement to mark the beginning of a job.
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax; try the operation again.
JCL scanner
The scanner encountered unexpected syntax while processing a procedure definition. The PROC statement marks the beginning of a procedure. Syntax of the PROC statement is as follows:
//[name] PROC [parameter [comments]] //[name] PROC
//name PROC [parameter [comments]] //name PROC
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax of the procedure; try the operation again.
JCL scanner
The scanner encountered unexpected syntax while processing an include group. Include groups cannot contain the following JCL statements:
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax of the include group; try the operation again.
JCL scanner
A PEND statement was identified and no corresponding procedure invocation was found.
Scanning terminates for the current file, and processing continues.
Locate any missing files; try the operation again. Otherwise, verify and correct the syntax; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer include nesting maximum is 15. The nesting of INCLUDEs exceeds this limit.
Scanning terminates for the current file, and processing continues.
Reduce the include nesting; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer JCL name length maximum is 8. The symbolic name fields must not exceed this limit.
Scanning terminates for the current file, and processing continues.
Reduce the length of the symbolic name; try the operation again.
JCL scanner
More than one JOB card was detected. WebSphere Studio Asset Analyzer does not support multiple JOB cards; only a single job per file is allowed.
Scanning terminates for the current file, and processing continues.
Split multiple (nested) JOBs into single files; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer parameter maximum is 400. The number of JCL parameters passed to a step exceeded this limit.
Scanning terminates for the current file, and processing continues.
Reduce the number of parameters; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer nesting maximum is 20. You can nest the delimiters up to the maximum.
Scanning terminates for the current file, and processing continues.
Reduce the delimiter nesting level; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer IF nesting level maximum is 16. The nesting of IF statements exceeds this limit. You can nest IF/THEN/ELSE/ENDIF statement constructs up to the maximum. The steps that execute in a THEN clause and an ELSE clause can be another IF/THEN/ELSE/ENDIF statement construct.
Scanning terminates for the current file, and processing continues.
Reduce the IF nesting level; try the operation again.
JCL scanner
An ENDIF statement was identified and no corresponding IF statement was located. The IF statement is always followed by a relational expression and a THEN clause. Optionally, an ELSE clause can follow the THEN clause. An ENDIF statement always follows the ELSE clause, if present, or the THEN clause. The ENDIF statement indicates the end of the IF/THEN/ELSE/ENDIF statement construct and must be coded for each construct.
Scanning terminates for the current file, and processing continues.
Verify and correct the IF/THEN/ELSE/ENDIF syntax; try the operation again.
JCL scanner
The scanner detected that a symbol value pair was found without a SET statement, or a symbol value pair was missing an equal sign. SET defines and assigns initial values to symbolic parameters used when processing JCL statements. Syntax of the SET statement is as follows:
//[name] SET symbol=value [comments]
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax of the SET statement parameter(s); try the operation again.
JCL scanner
The scanner detected a JCLLIB statement, but no ORDER= keyword parameter was found. The JCLLIB statement identifies and orders the libraries that the system uses for the job when searching for procedures and INCLUDEs. Syntax of the JCLLIB statement is as follows:
//[name] JCLLIB ORDER=(library[,library]...) [comments]
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax of the JCLLIB statement; try the operation again.
JCL scanner
The scanner detected an EXEC statement, but no positional parameter (for example, PGM, PROC or procedure name) was found. The EXEC statement identifies the program or cataloged or in-stream procedure that this job step is to execute. Syntax of the EXEC statement is as follows:
//[stepname] EXEC positional_parm[,keyword_parm]...[,symbol_parm=value]... [comments]
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax of the EXEC statement; try the operation again.
JCL scanner
The scanner detected an EXEC statement with a positional parameter PGM=, but no program name was found. The PGM parameter names the program that the system is to execute. The syntax of the PGM parameter is as follows:
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax of the PGM= parameter; try the operation again.
JCL scanner
The scanner was processing a DD concatenation and found no corresponding job step, JOBLIB or JOBCAT.
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax; try the operation again.
JCL scanner
The JOB statement is expected to be the first statement to mark the beginning of a job. The JOB statement was not found, or an incomplete JOB card was detected (for example, a JOB statement was identified but an expected continuation of the JOB card was not found).
Scanning terminates for the current file, and processing continues.
Verify and correct the JCL to include a JOB card; try the operation again.
JCL scanner
The scanner encountered an unexpected DD statement. The scanner expects to find JOBLIB, JOBCAT, and/or PROCLIB statements following the JOB card. There should be no intervening EXEC or other DD statements.
Verify and correct the syntax; try the operation again.
JCL scanner
The scanner supports one JOBCAT per job, appearing after the JOB statement, following the JOBLIB, if coded, and before the first EXEC.
Scanning terminates for the current file, and processing continues.
Verify and correct the JCL to use a single JOBCAT; try the operation again.
JCL scanner
The scanner supports one JOBLIB per job, appearing after the JOB statement, before the JOBCAT, if coded, and before the first EXEC.
Scanning terminates for the current file, and processing continues.
Verify and correct the JCL to utilize a single JOBLIB; try the operation again.
JCL scanner
WebSphere Studio Asset Analyzer encountered an unknown statement while processing the syntax of the procedure. Syntax of the PROC statement is as follows:
//[name] PROC [parameter [comments]] //[name] PROC
//name PROC [parameter [comments]] //name PROC
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax of the procedure; try the operation again
JCL scanner
The WebSphere Studio Asset Analyzer PROC nesting maximum is 15. In a procedure, an EXEC statement can invoke another procedure, which can contain an EXEC statement to invoke another procedure, and so on. Cataloged and in-stream procedures can invoke other procedures up to 15 levels of nesting.
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax; try the operation again.
JCL scanner
This is an internal error of the application.
Scanning terminates for the current file, and processing continues.
Contact your IBM technical-support representative.
JCL scanner
This is an internal error of the application.
Scanning terminates for the current file, and processing continues.
Contact your IBM technical-support representative.
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message is an informational banner.
The system is functioning normally.
None
JCL scanner
This message provides the status of a JCL statement being processed.
The system is functioning normally.
None
JCL scanner
This message provides the status of a JCL statement being substituted.
The system is functioning normally.
None
JCL scanner
The WebSphere Studio Asset Analyzer JOB step maximum is 255. You enter a program into the operating system as a job step. A job step consists of the job control statements that request the resources needed to run the program and is identified by an EXEC statement. A job can be simple or complex; it can consist of one step or of many steps, up to 255.
Scanning terminates for the current file, and processing continues.
Reduce the number of steps in the job; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer StepName.DDName length maximum is 18. While processing an override, the string for //stepname.ddname exceeded this limit.
Reduce the StepName.DDName length; try the operation again.
JCL scanner
An override statement explicitly named a step that was not found in the expanded procedure.
Scanning terminates for the current file, and processing continues.
Locate any missing files; try the operation again. Otherwise, verify and correct the syntax; try the operation again.
JCL scanner
The DD override was not added to inventory. The scanner attempted to default to override the first step, which was not found, possibly due to all expanded steps invoking nested procedures.
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax; try the operation again.
JCL scanner
This message provides the status of a JCL statement; a DD statement was added.
The system is functioning normally.
None
JCL scanner
This message provides the status of a JCL statement; a DD statement was overridden.
The system is functioning normally.
None
JCL scanner
This message reports a fatal error while processing a JCL statement.
Scanning terminates for the current file, and processing continues.
Contact your IBM technical-support representative.
Code extraction, Impact analysis
This message reports a return value from DB2 following an SQL operation.
Processing stops.
Refer to the DB2/SQL messages and codes reference.
JCL scanner
The WebSphere Studio Asset Analyzer JCL statement label length maximum is 18 (for example, StepName.DDNameXX).
Scanning terminates for the current file, and processing continues.
Reduce the length of the statement label; try the operation again.
JCL scanner
The WebSphere Studio Asset Analyzer JCL statement parameter length maximum is 8192. The parameter text length exceeds this limit.
Scanning terminates for the current file, and processing continues.
Reduce the length of the statement parameter text string; try the operation again.
JCL scanner
An in-stream procedure definition has no name in its PROC statement.
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax; try the operation again.
JCL scanner
An end of file was reached, and no corresponding PEND statement was located for the in-stream procedure being processed. In-stream procedures must end with a PEND statement.
Scanning terminates for the current file, and processing continues.
Verify and correct the syntax; try the operation again.
Code extraction, Impact analysis, JCL scanner
This message reports the status of input parameters being processed.
The system is functioning normally.
None
JCL scanner
This is an internal error of the application.
Scanning terminates for the current file, and processing continues.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the container. The container is not inserted in the DMH_CONTAINER table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the file. The file is not inserted in the DMH_FILE table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer supports the following data set name maximum lengths: MVS = 58, workstation = 510. The data set name exceeds this limit.
The loader skips the current asset and continues processing.
Reduce the length of the data set name; try the operation again.
Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the run unit. The run unit is not inserted in the DMH_RUN_UNIT table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
DB2 catalog scanner, Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the site. The site is not inserted in the DMH_SITE table.
Processing stops.
Contact your IBM technical-support representative.
PDS Member List Processing
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
JCL analyzer - DMH4000
The JCL analyzer has encountered an INCLUDE statement but was unable to detect the statement's MEMBER= phrase. This statement has two valid formats:
The JCL analyzer reports this message and ignores the INCLUDE statement.
Validate the INCLUDE statement by verifying that it matches one of the above formats. If it does not, correct the statement's syntax and reprocess the JCL file. If it does, contact your IBM technical-support representative.
JCL scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
JCL scanner
The scanner recognizes batch invocation of TSO (IKJEFT1A) and will look for SYSTSIN DD on the job step to identify the actual DB2 run unit name. If SYSTSIN DD is not coded, does not specify RUN PROG(name), or the data can not be read, no run unit name substitution is available.
Processing continues.
None
JCL scanner
The scanner could not open the filename specified for SYSTSIN DD. The scanner attempts to open this file in order to identify the DB2 system specified on the DSN SYSTEM(sysname) parameter and the run unit name specified on the RUN PROG(progname) parameter. This message can be paired with DMH1443W.
Processing continues.
Verify the status and location of the file specified for the SYSTSIN DD; make corrections, if any, and try the operation again if the file is available.
JCL scanner
WebSphere Studio Asset Analyzer could not generate a unique ID for the data set. The data set was not inserted in the DMH_DATASET table.
Scanning terminates for the current file, and processing continues.
Contact your IBM technical-support representative.
JCL scanner
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit and PSB name. When run unit DSNMVT01 is detected in the parameter data, the scanner will also look for DDITV02 DD to identify the actual DB2 run unit name. The scanner did not find DDITV02 DD on the job step.
Processing continues.
None
JCL scanner
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit. When DSNMVT01 is detected in the parameter data, the scanner will also look for DDITV02 DD on the job step to identify the actual DB2 run unit name. DDITV02 DD was found but the read failed.
Processing continues.
None
JCL scanner
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit. When DSNMVT01 is detected in the parameter data, the scanner will also look for DDITV02 DD on the job step to identify the actual DB2 run unit name. If DDITV02 DD is not found, does not specify a DSN= parameter, or the DSN specified is a temporary file, no run unit name substitution is available. This message can be paired with DMH1447W or DMH1448W.
Processing continues.
None
Analysis queue processor, JCL scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
JCL scanner
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit. No PARM= statement was found. DFSRRC00 is the run unit assigned to the job step.
Processing continues.
None
JCL scanner
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit and PSB name. The scanner did not find a PSB name coded.
Processing continues.
None
JCL scanner
This is an internal error of the application.
Scanning terminates for the current file, and processing continues.
Contact your IBM technical-support representative.
JCL scanner
Scanning terminates for the current file, and processing continues.
Contact your IBM technical-support representative.
Import record loader
The loader did not find the required MEMB import record for processing a file.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Code extraction, Impact analysis
DB2 returned an -811 SQLCODE when attempting to locate the data element.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
The loader did not find the required MAPS import record for processing a BMS mapset.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the BMS mapset. The mapset is not inserted in the DMH_MAPSET table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the BMS map. The map is not inserted in the DMH_MAP table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer does not support multiple BMS mapsets with the same name.
The loader skips the current asset and continues processing.
None
Import record loader
The loader could not open the file specified for MEMLIST DD.
Processing stops.
Contact your IBM technical-support representative.
BMS macro definition scanner
The file cannot be opened. Possible causes are:
The scanner skips the current file, and processing continues.
Verify and correct the cause; try the operation again.
Impact analysis
Impact analysis was unable to insert a row into the DMH_CHANGE_IMPACT table.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
An OPEN request for cursor DMHD224, DMHD225 or DMHD226 failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis, IMS analysis
An OPEN request for cursor DMHD221 failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
An OPEN request for cursor DMHD227A-E or DMHD364B-C failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
An OPEN request for cursor DMHD228 failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
Impact analysis was unable to record the impact. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
An OPEN request for cursor DMHD222A or DMHD223D failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
An OPEN request for cursor DMHD223 failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
Impact analysis was unable to update a row in the DMH_CHANGE_FOCUS table.
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
An OPEN request for cursor DMHD229A, DMHD229B or DMHD364A failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
File classification scanner, Import record loader
An open failed for the FILELIST DD file (file classification scanner) or the INFILE DD file (import record loader).
Processing stops.
Contact your IBM technical-support representative.
Impact analysis
An OPEN request for cursor DMHD261 failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
The loader detected an inconsistency while processing the sequence number for a control transfer.
The loader skips the current asset and processing continues.
Contact your IBM technical-support representative.
BMS macro definition scanner, Code extraction, Impact analysis, Import record loader
Processing detected a character string value was longer than expected; value was shortened as required for database processing (for example, UPDATE, INSERT).
Processing continues.
None
Import record loader
The loader detected that the region ID was set to the default value of -1; the region ID was not reset by processing a valid REGION import record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the region. The region is not inserted in the DMH_ONLINE_REGION table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
WebSphere Studio Asset Analyzer could not generate a unique ID for the transaction. The transaction is not inserted in the DMH_TRANSACTION table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
The loader was unable to insert a row into the DMH_COMPILE_UNIT table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
BMS macro definition scanner, File classification scanner, Import record loader, JCL scanner
Processing detected an invalid parameter.
For most cases, the invalid parameter is skipped and processing continues. Refer to message DMH1730I for further information. The exception is when DMH1721I is reported without a corresponding DMHI1730I; processing stops.
Refer to message DMH1730I for further information.
Import record loader
The loader was unable to update a row in the DMH_COMPILE_UNIT table.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
BMS macro definition scanner, File classification scanner, JCL scanner
This message reports the status of a parameter string.
The system is functioning normally.
None
Import record loader
This message is an informational banner.
The system is functioning normally.
None
Import record loader
The loader found no matching container type in the DMH_CONT_TEMPLATE table.
Processing skips the current record and continues.
Contact your WebSphere Studio Asset Analyzer administrator.
Import record loader
The loader detected a mismatch between the input container type and the container type available in the DMH_CONT_TEMPLATE table.
Processing continues.
Contact your WebSphere Studio Asset Analyzer administrator.
Import file loader
The loader could not insert a row for the referenced SQL component type.
sqlcomponent types:
Processing skips the current record and continues.
Contact your IBM technical-support representative.
DMHU010 - Site processor
The site processor could not retrieve valid site information.
returncode values:
Processing stops.
Contact your WebSphere Studio Asset Analyzer administrator.
DMHU010 - Site processor
The site processor could not retrieve valid site information.
Processing stops.
Refer to message DMH1740I for further information. Contact your WebSphere Studio Asset Analyzer administrator.
DMHU010 - Site processor
This message reports status; extraneous data is ignored.
The system is functioning normally.
None
DMH0700 - Batch update
WebSphere Studio Asset Analyzer does not support multiple sites for z/OS assets.
Processing skips the current record and continues.
Contact your IBM technical-support representative.
DMHU010 - Site processor
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Analysis queue processor
An OPEN request for cursor cursorname failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
Analysis queue processor
A postprocessing queue entry to resolve dynamic references contains an internal CALL statement identifier that is invalid.
The postprocessing queue entry is deleted, and postprocessing continues with next queue entry.
Contact your IBM technical-support representative. Retain the postprocessing job output.
Analysis queue processor
A postprocessing queue entry to resolve dynamic references contains an internal LITERAL identifier that is invalid.
The postprocessing queue entry is deleted, and postprocessing continues with next queue entry.
Contact your IBM technical-support representative. Retain the postprocessing job output.
Analysis queue processor
WebSphere Studio Asset Analyzer is attempting to build a dynamic concatenation set to satisfy COPY or INCLUDE references. An internal limit using data from the DMH_INCLUDE_CONCAT table has been reached; no concatenation set is generated.
Processing continues.
Verify the location of any missing COPY or INCLUDE files, as reported on the File details page, and ensure their owning container(s) are represented in a concatenation set known to WebSphere Studio Asset Analyzer. This can be accomplished by identifying an existing user concatenation set of containers that is deemed appropriate, or creating a new concatenation set, and assigning the concatenation set to the container or file being processed. Explicitly assigning the appropriate concatenation set to the file or container will resolve the COPY/INCLUDE reference(s). Use Assign default concatenation sets during inventory collection, the Assign default concatenation sets option from the Actions drop-down list on the Container details page, or the Assign concatenation set option from the Actions drop-down list on the File details page.
Analysis queue processor
This is an internal error or the application.
Processing stops.
Contact your IBM technical-support representative.
Analysis queue processor
WebSphere Studio Asset Analyzer is attempting to build a dynamic concatenation set to satisfy COPY or INCLUDE references. No concatenation set was generated. This message will be paired with DMH1769W.
Processing continues.
Verify the location of any missing COPY or INCLUDE files, as reported on the File details page, and ensure their owning container(s) are represented in a concatenation set known to WebSphere Studio Asset Analyzer. This can be accomplished by identifying an existing user concatenation set of containers that is deemed appropriate, or creating a new concatenation set, and assigning the concatenation set to the container or file being processed. Explicitly assigning the appropriate concatenation set to the file or container will resolve the COPY/INCLUDE reference(s). Use Assign default concatenation sets during inventory collection, the Assign default concatenation sets option from the Actions drop-down list on the Container details page, or the Assign concatenation set option from the Actions drop-down list on the File details page.
Analysis queue processor
WebSphere Studio Asset Analyzer could not automatically determine the appropriate concatenation set to apply to resolve COPY or INCLUDE references, likely due to multiple files with the same name captured in the inventory or multiple concatenation sets that could satisfy the references.
Processing continues.
Verify the location of any missing COPY or INCLUDE files, as reported on the File details page. Review the existing inventory of concatenation sets and identify the appropriate set as the default for the container or file being processed. Explicitly assigning the appropriate concatenation set to the file or container will resolve the COPY/INCLUDE reference(s). Use Assign default concatenation sets during inventory collection, the Assign default concatenation sets option from the Actions drop-down list on the Container details page, or the Assign concatenation set option from the Actions drop-down list on the File details page.
DBDGEN scanner, PSBGEN scanner
This message reports processing status.
The system is functioning normally.
None
DBDGEN scanner, PSBGEN scanner
While processing control cards, the scanner found invalid parameter data parameter. No expected keyword was recognized.
Processing stops.
None. This function is not active in the current release of the product.
DBDGEN scanner, PSBGEN scanner
The scanner detected a system control card that was non-numeric.
Processing stops.
None. This function is not active in the current release of the product.
Import record loader
At the start of loading import records for an IMS program specification block (START PSBLIB), the loader detected a missing PSB container name. There was no active ACB container to override the condition.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
At the start of loading import records for an IMS database definition (START DBDLIB), the loader detected a missing DBD container name. There was no active ACB container to override the condition.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
While processing import records for an IMS access control block (START ACBLIB), the loader detected a missing ACB container name.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected a missing DBD ID for segment segmentname on the DSEG record.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
While processing the import records for imscomponenttype, the loader detected a zero length for componentname. The length must be greater than zero.
The current record is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected that a required parameter from a paired set was missing on a DSEG record. For a logical segment, these attributes describe the source segment from which the logical segment has been derived.
If the sourcedbdname name 1 is specified, the source segment name 1 is required.
If the sourcedbdname 2 is specified, the source segment name 2 is required.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected a missing segment ID for fieldname,segmentname on the IFLD record.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected a field position for fieldname,segmentname with a value of zero on the IFLD record. The field position must be greater than zero.
The current record is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected a missing PSB ID for segment segmentname on the PSEG record.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing import records, the loader detected a missing PSB ID for PCB psbbname,pcbsequence,pcbtype on the IPCB record.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing import records, the loader failed to successfully insert a row for imscomponenttype componentname in the DMH_IMS_* table of interest.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing import records, the loader detected DD name ddname was longer than 8 characters. ddname was truncated to 8 characters and inserted into table DMH_IMS_DBD_DD.
Processing continues.
None
Import record loader
While processing import records, the loader detected a missing DBD ID on the IDDN record.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing import records, the loader was unsuccessful at inserting a row in table DMH_IMS_DBD_DD for DD name ddname.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
DBDGEN scanner, PSBGEN scanner
While processing control cards, the scanner found a non numeric subsys value.
Processing stops.
None. This function is not active in the current release of the product.
IMS scanner - DMHSTG2
The scanner skips the current record and continues processing.
Contact your IBM technical-support representative.
IMS scanner - DMHDIST
Processing stops.
Contact your IBM technical-support representative.
IMS scanner - DMHMDA
This message reports processing status.
The system is functioning normally.
None
IMS scanner - DMHMDA
This message reports processing status.
The system is functioning normally.
None
IMS scanner - DMHMDA
Processing stops.
Contact your IBM technical-support representative.
IMS scanner - DMHMDA
Processing continues.
Contact your IBM technical-support representative.
IMS scanner - DMHMDA
This message reports processing status.
The system is functioning normally.
None
IMS scanner - DMHMDA
This message reports processing status
The system is functioning normally.
None
Analysis queue processor
This message reports processing status.
The system is functioning normally.
None
Analysis queue processor
No matching entry point was found for the transfer target entrypointname. The run unit is identified as unresolved.
Processing continues.
Locate source code for entry point entrypointname. Collect inventory for the file to resolve run unit status.
Analysis queue processor
The current asset is skipped, and processing continues.
Analysis queue processor
Multiple entry points matched the transfertargetentrypointname. The run unit is identified as unresolved.
Processing continues.
Analysis queue processor
The processor was unsuccessful at retrieving the run unit name for run unit ID rununitid from the DMH_RUN_UNIT table.
Processing continues.
Analysis queue processor
Processing failed to successfully open the load module alias file DMHALIAS.
Processing continues.
Verify that the user has authority to read the load module alias file found in data set &hlq.SDMHDATA;, especially if the user intends to use aliases documented in this file for the run unit builder's call resolution. If the condition persists, contact yourWebSphere Studio Asset Analyzer administrator.
Analysis queue processor
An attempt to build a linked list failed. This is an internal error of the application.
Contact your IBM technical-support representative.
Analysis queue processor
Contact your IBM technical-support representative.
Analysis queue processor
An attempt to build a linked list failed. This is an internal error of the application.
Contact your IBM technical-support representative.
Analysis queue processor
An attempt to add an item to a linked list failed. This is an internal error of the application.
Contact your IBM technical-support representative.
Analysis queue processor
This is an internal error of the application.
Contact your IBM technical-support representative.
Analysis queue processor
An error was detected while processing the first field in the record on line number linenumber in the load module alias file.
Processing continues.
Verify the record layout in the load module alias file DMHALIAS, found in data set &hlq.SDMHDATA;, is correct; reattempt postprocessing.
Analysis queue processor
An error was detected while processing the second field in the record on line number linenumber in the load module alias file.
Processing continues.
Verify the record layout in the load module alias file DMHALIAS, found in data set &hlq.SDMHDATA;, is correct; reattempt postprocessing.
Analysis queue processor
An error was detected while processing the third field in the record on line number linenumber in the load module alias file.
Processing continues
Verify the record layout in the load module alias file DMHALIAS, found in data set &hlq.SDMHDATA;, is correct; reattempt postprocessing.
Analysis queue processor
An error was detected while processing the fourth field in a record on line number linenumber in the load module alias file.
Processing continues.
Verify the record layout in the load module alias file DMHALIAS, found in data set &hlq.SDMHDATA;, is correct; reattempt postprocessing.
Analysis queue processor
This message reports processing status indicating successful run unit resolution.
The system is functioning normally.
None
Analysis queue processor
Processing failed to successfully open the utility program list file DMHUTIL.
Processing continues
Verify that the user has authority to read the utility program list file found in data set &hlq.SDMHDATA.. This file is used for the run unit builder's call resolution for standard utility programs. If the condition persists, contact your WebSphere Studio Asset Analyzer administrator.
Analysis queue processor
This message reports processing status.
The system is functioning normally.
None
Analysis queue processor
This message reports processing status indicating the number of records read from either the load module alias file (DMHALIAS) or utility program list file (DMHUTIL).
The system is functioning normally.
None
Analysis queue processor
This message reports processing status indicating successful open and read of the alias substitution file ddname.
The system is functioning normally.
None
Analysis queue processor
This message reports processing status indicating successful run unit resolution.
The system is functioning normally.
None
Analysis queue processor
This message reports processing status indicating successful run unit resolution.
The system is functioning normally.
None
Analysis queue processor
No matching entry point was found for the transfertargetentrypointname. The run unit is identified as unresolved.
Processing continues.
Locate source code for entry point transfertargetentrypointname; collect inventory for the file to resolve run unit status.
Analysis queue processor
This message appears in debug mode only. It reports processing status.
The system is functioning normally.
None
Analysis queue processor
This message appears in debug mode only. It reports processing status.
The system is functioning normally.
None
DMHMINTF - Interface to LE messaging
This is an internal error of the application.
Contact your IBM technical-support representative.
DMHMINTF - Interface to LE messaging
This is an internal error of the application.
Contact your IBM technical-support representative.
REXX - DMHGTSTE
An attempt to retrieve the site information failed or the data was invalid. The default value for the site, NAME (*default*), and PLATFORM_ID = 1, corresponding to "MVS or OS/390", will be used.
Processing continues.
Contact your IBM technical-support representative.
REXX - DMHI630Z
Assembler source analysis for file filename failed. The analysis status for the compile unit is Error.
Processing continues.
Locate message DMH1929W for return code data. Resolve the error and try the operation again.
REXX - DMHI630Z
Assembler analysis for BMS file filename failed with return code returncode. The analysis status for the compile unit is Error.
Processing continues.
Resolve the error and try the operation again.
Assembler, BMS, COBOL and PL/I scanner
Return code returncode was raised by scantype analysis. The analysis status for the compile unit will be Error.
Processing continues.
Resolve scanning errors; try the operation again.
Assembler scanner
The IBM assembler did not produce any output for analysis.
The current asset is skipped, and processing continues.
Verify the file is valid assembler source and the ADATA option is enabled; reattempt the analysis. If the problem continues, contact your IBM technical-support representative.
Assembler scanner
The ADATA file being processed by the assembler analyzer is not from the assembler translator.
The current asset is skipped, and processing continues.
Verify the IBM translator is being used by the assembler scanner; reattempt the analysis. If the problem continues, contact your IBM technical-support representative.
Assembler scanner
The ADATA file produced by the assembler analyzer is not from a supported version.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Assembler scanner
The assembler analyzer is unable to allocate SYS1.MACLIB.
Processing stops.
Verify SYS1.MACLIB is available and the user has the proper authority to access the container; reattempt the analysis. If the problem continues, contact your IBM technical-support representative.
Assembler scanner
The assembler scanner is unable to allocate the input source file.
Processing stops.
Verify the input source file is available and the user has the proper authority to access the container; reattempt the analysis. If the problem continues, contact your IBM technical-support representative.
REXX - DMHI610Z
Processing stops.
CICS region analyzer
An OPEN request for file filename failed. The reported status code is statuscode.
Processing stops.
CICS region analyzer
A close request for file filename failed. The reported status code is statuscode.
Processing stops.
CICS region analyzer
An attempt to write a record to file filename failed. The reported status code is statuscode.
Processing stops.
CICS region analyzer
An attempt to sort file filename failed. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The CICS region analyzer calls the JCL scanner to process the CICS start JCL. This message indicates that the JCL scanner analyzed number data sets, as identified in the CICS start JCL Step executing PGM=DFHSIP.
The system is functioning normally.
None
CICS region analyzer
The analyzer detected a missing control record. SITE and CREG are required.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
WebSphere Studio Asset Analyzer uses the CICS system definition utility program (DFHCSDUP) to gather data from the CICS system definition (CSD). The OBJECTS option of the EXTRACT command is required to gather all resource definition attributes. The analyzer has detected that the OBJECTS option is missing. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The CICS region analyzer calls the JCL scanner to process the CICS start JCL. JCL analysis did not find a job step that specified EXEC PGM=DFHSIP. This error can occur if the user specified an incorrect start JCL container or if the CICS start is wrapped (for example, DFHSIP is passed as a parameter). The JCL scanner does not currently provide analysis support for the second scenario.
Processing continues
Confirm that EXEC PGM=DFHSIP is the format used in the start JCL. Verify that the user supplied the correct data set name for the CICS region start JCL file; reattempt CICS region analysis.
CICS region analyzer
The CICS region analyzer calls the JCL scanner to process the CICS start JCL. While processing the JCL, an internal table limit was exceeded before the end of file was reached.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The CICS region analyzer calls the JCL scanner to process the CICS start JCL. While processing the output records from the JCL analysis, an unexpected end of file was encountered.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
While processing file information, a duplicate record for the same file was found. Duplicates can occur when both the CSD and FCT each contain entries for the same file. However, this message is reporting unexpected duplicate entries from the same source. WebSphere Studio Asset Analyzer is attempting to resolve data stores (files) and data sets.
The current file record is skipped, and processing continues.
Contact your IBM technical-support representative.
CICS region analyzer
This message reports processing status indicating that the data set resolution for file name was from the CICS start JCL.
The system is functioning normally.
None
CICS region analyzer
This message reports processing status indicating that the data set resolution for file name was from the CICS system definition (CSD).
The system is functioning normally.
None
CICS region analyzer
This message reports processing status indicating that the data set resolution for file name was from the CICS dynamically allocated data sets (FCT).
The system is functioning normally.
None
CICS region analyzer
No corresponding data set for file name was discovered in the start JCL, CSD or FCT.
Processing continues.
CICS region analyzer
This message reports processing status.
The system is functioning normally.
None
CICS region analyzer
The analyzer encountered an unexpected error processing the GRP control record. By default, all groups in the CSD are examined.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The analyzer encountered an unexpected error processing the CSD control record for the region analysis.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The analyzer encountered an unexpected error processing the REGN control record for the region analysis.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The analyzer encountered multiple CSD control records; only one CSD per region is supported.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The analyzer encountered multiple LIST control records. Only one LIST record per region is supported.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The analyzer encountered multiple FCT control records. Only one FCT record per region is supported.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The analyzer encountered multiple SJCL (start JCL) control records. Only one SJCL record per region is supported.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
The analyzer found that a temporary work file was previously allocated.
Processing stops.
Locate data set datasetname and delete it. Reattempt CICS region analysis.
CICS region analyzer
The analyzer found that a temporary work file was previously allocated, and it has been deleted.
Processing continues.
None
CICS region analyzer
The analyzer could not allocate a required temporary work file datasetname.
Processing stops.
Ensure system resources are available, and verify that the user has authority to create a sequential data set named datasetname with the following attributes:
Reattempt CICS region analysis. If the condition persists, contact your IBM technical-support representative.
CICS region analyzer
This message reports processing status indicating the analyzer detected a PROC data set control record with no corresponding SJCL (start JCL) control record. The CICS region start JCL PROC data set is ignored.
Processing continues.
A PROC control record, indicated by the user supplying a CICS region start JCL PROC data set name, implies the start JCL invokes procedure(s). Verify that the user supplied the correct data set name for the CICS region start JCL file. Reattempt CICS region analysis. If the condition persists, contact your IBM technical-support representative.
CICS region analyzer
This message reports processing status indicating the return code from the JCL scanner invoked to process the CICS start JCL.
The system is functioning normally.
None
CICS region analyzer
This message reports processing status indicating the return code from the import record builder used to create CICS region import records.
The system is functioning normally.
None
CICS region analyzer
The analyzer encountered a fatal error during processing, as indicated by return code returncode.
Processing stops.
Contact your IBM technical-support representative.
CICS region analyzer
This message reports processing status indicating the return code from the CICS region analyzer.
The system is functioning normally.
None
CICS region analyzer
This message reports processing status indicating that the CICS system definition utility program (DFHCSDUP) is being used to gather group and list object information.
The system is functioning normally.
None
CICS region analyzer
This message reports processing status indicating the return code from reading from the CICS system definition file (CSD) using the CICS system definition utility program (DFHCSDUP).
The system is functioning normally.
None
CICS region analyzer
The analyzer could not allocate a required temporary work file for processing the load library for CICS dynamically allocated data sets, FCT name.
Processing stops.
Contact your IBM technical-support representative.
SCM processor - DMHSCMI
While processing SCM call parameters, an unexpected call type was detected. Valid call types are:
Processing stops.
Contact your IBM technical-support representative.
SCM processor - DMHSCMI
While processing SCM call parameters, an unexpected SCM type was detected. Valid call types are:
Processing stops.
Contact your IBM technical-support representative.
SCM processor - DMHSABLL
While processing a ChangeMan request, the processor encountered an unexpected condition.
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHCLIST, DMHFLIST
While processing the output from the SCLM DBUTIL service, the processor encountered an unexpected condition.
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHCLIST, DMHFLIST
The processor could not allocate required output file filename.
Processing stops.
Ensure system resources are available, and verify that the user has authority to create a data set named filename with the following attributes:
Reattempt the job. If the condition persists, contact your IBM technical-support representative.
SCLM processor - DMHCLIST, DMHFLIST
The processor encountered an unexpected write error while processing the SCLM output for updated records.
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHCLIST, DMHFLIST
The processor failed to locate any input parameters for the SCLM task. Expected parameters are as follows:
For Change List:
For Full List:
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHCLIST, DMHFLIST
The processor is expecting to find parameter=value pairs but detected a missing value while processing the input parameters. Expected parameter=value pairs are as follows:
For Change List:
For Full List:
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHFLIST
The processor is expecting to find a known set of keyword parameters but detected an unknown keyword while processing the input parameters for a Full List request. Expected keyword parameters are as follows:
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHFLIST
This message reports processing status indicating that the processor detected an unexpected error while verifying the PROJECT, ALTPROJ, and/or GROUP input keyword parameters for a Full List request.
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHFLIST
This message reports processing status indicating that the processor detected an unexpected error while verifying the PROJECT input parameter keyword for a Full List request.
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHCLIST
Data set datasetname, containing the full scan output from module SPYFLIST, was not found.
Processing stops.
You may need to process a Full List request in order to proceed. Contact your IBM technical-support representative.
SCLM processor - DMHCLIST
The processor is expecting to find a known set of keyword parameters but detected an unknown keyword while processing the input parameters for a Change List request. Expected keyword parameters are as follows:
Processing stops.
Contact your IBM technical-support representative.
SCLM processor - DMHCLIST
The processor detected an unexpected error while verifying the PROJECT and/or FRMDATE input parameter keywords for a Change List request.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
This message appears in debug mode only. It reports processing status indicating the database has been successfully updated.
The system is functioning normally.
None
Import record loader
The loader experienced a fatal error while attempting to update the database.
The loader skips the current asset and continues processing.
Contact your IBM technical-support representative.
Import record loader
Locate message DMH2103E and prior message entries leading up to it to identify potential cause of the error condition.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected an invalid tool ID value on the TOOL record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader did not detect a required FMT record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected an invalid value for the format version on the FMT record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected an invalid value for the format name on the FMT record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
The database has been updated with asset type file filename data.
The system is functioning normally.
None
CICS region analyzer
While processing the input parameters, the analyzer is expecting to find a known set of keyword parameters but detected an unknown keyword parameter. Expected keyword parameters are as follows:
Processing stops.
Contact your IBM technical-support representative.
Import record loader
A problem detected while processing the MAIN, MEMB, FILE and/or START import records has raised an error condition. Import records will be displayed on DMH1119I messages.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing import records, the loader detected an unknown record type recordtype.
The invalid record is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader did not detect a required TOOL record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader, DMH0700 - Batch update
This message appears in debug mode only. The message for the import record loader displays a line count for the number of records read from the input buffer. The message for DMH0700 display the actual record as read from the input buffer.
The system is functioning normally.
None
Import record loader
The loader was unable to update column LANGUAGE_CD in table DMH_FILE.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
CICS region analyzer
While processing input parameters, the analyzer did not detect a required SITE record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected an invalid value for the site name on the SITE record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
While processing the import records, the loader detected an invalid value for the container name on the LIBR record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
While processing import records, the loader did not detect a required LIBR record.
Processing stops.
Contact your IBM technical-support representative.
Import record loader
The load module translator translatorstring was successfully inserted in table DMH_TRANSLATOR.
The system is functioning normally.
None. This function is not active in the current release of the product.
Import record loader
The load module translator translatorstring failed to be inserted in table DMH_TRANSLATOR.
The current record is skipped, and processing continues.
None. This function is not active in the current release of the product.
Import record loader
While processing a batch job STEP record, the loader detected a missing procedure name, implying that an earlier PROC record was either invalid or not found. The analysis status will be reported as Error.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing a batch job component (for example, DD concatenation, invoke run unit, PSB, job step), the loader detected a missing JOB ID, implying that an earlier JOB START record was either invalid or not found. The analysis status will be reported as Error.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing a compile unit component (for example, control transfer, include, literal, data element, data store, entry point), the loader detected a missing compile unit ID, implying that an earlier CU START record was either invalid or not found. The analysis status will be reported as Error.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
The loader failed to successfully insert a row in table DMH_CU_STMT while processing a STMT record.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
The loader failed to successfully insert a row in table DMH_CU_DATA_USE while processing a REF record.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
The loader detected a missing data element ID, implying that a DEA record was either invalid or not found. The analysis status will be reported as Error.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
This message appears in debug mode only. It echos the import record type and value being processed.
The system is functioning normally.
None
Import record loader
This message appears in debug mode only. It echos the work data being processed.
The system is functioning normally.
None
Import record loader
While attempting to insert a row into a table, the loader was notified that a row with the same primary key already existed in the table.
The current record is skipped, and processing continues.
Import record loader
The loader automatically outputs this message while processing an END LOMD record.
The system is functioning normally.
None. This function is not active in the current release of the product.
Import record loader
The loader automatically outputs this message while processing a START LOMD record.
The system is functioning normally.
None. This function is not active in the current release of the product.
Import record loader
Row(s) in the DMH_MEMBER_ALIAS table have been deleted for the load module file being processed on the START LOMD record.
The system is functioning normally.
None. This function is not active in the current release of the product.
Import record loader
Row(s) in the DMH_MEM_CHAR_ATTR table have been deleted for the load module file being processed on the START LOMD record.
The system is functioning normally.
None. This function is not active in the current release of the product.
Import record loader
Row(s) in the DMH_CSECT_INFO table have been deleted for the load module file being processed on the START LOMD record.
The system is functioning normally.
none. This function is not active in the current release of the product.
Import record loader
The loader failed to successfully insert a row in table DMH_APPLICATION for application applicationname while processing an APP record.
The current record is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader
While processing an APP record, the loader detected more than one parent application containing a child application applicationname. The loader will use the first child application ID encountered in the DMH_APPLICATION table.
The system is functioning normally.
None
Import record loader
While processing an APP record, the loader was unsuccessful at locating a corresponding parent application, as indicated by the presence of a parentapplicationid, and will instead use application childapplicationname as the primary application.
The system is functioning normally.
None
Import record loader
A row has been inserted in the DMH_ATTR_NAME table for a new user-supplied attribute with type ID attributetypeid.
The system is functioning normally.
None
Import record loader
While processing a FILE record, the loader detected missing data in a required attribute field: resource manager type, container name, file name, or language.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
Import record loader, DMH0700 - Batch update
An attempt to locate resource manager resourcemanagertype in the DMH_RESOURCE_MNGR table failed.
Contact your WebSphere Studio Asset Analyzer administrator.
REXX - DMHANLIB
A return code returncode was raised for a failed library/member list processing request for type type using criteria criteria.
REXX - DMH650Z
Changes were not successfully written to the database, as indicated by return code returncode.
The current asset is skipped, and processing continues.
Contact your IBM technical-support representative.
REXX - DMH630Z
No containers and files were found in the scan request file.
Processing is stopped.
Contact your IBM technical-support representative.
REXX - DMH5206
Processing detected an unsupported language and environment combination. Assembler scanning is supported on the z/OS machine only.
Use WebSphere Studio Asset Analyzer on z/OS to assemble and scan Assembler source.
REXX - DMH610Z
For PDS, expecting 1; For workstation NTFS, expecting 1; For SCLM, expecting ???
REXX - DMH610Z
REXX - DMH610Z
DMH0700 - Batch update
Processing was unable to insert a row into the DMH_ANALYSIS_QUEUE table.
Processing skips the current record and continues.
Contact your IBM technical-support representative.
DMH0700 - Batch update
Processing successfully inserted a row into the DMH_ANALYSIS_QUEUE table.
The system is functioning normally.
None
DMH0700 - Batch update
Processing successfully inserted a row into the DMH_ANALYSIS_QUEUE table.
The system is functioning normally.
None
DMH0700 - Batch update
The referenced application was not found for the SCM. Batch reanalysis does not support queuing a new SCM application, container, and file.
Processing skips the current record and continues.
Verify and correct the input record supplied for &hlq.SDMHCNTL member DMHJCLBU; resubmit the job.
DMH0700 - Batch update
Batch reanalysis does not support queuing a new container.
Processing skips the current record and continues.
Use the Inventory function from the browser interface to add the new container to the database.
DMH0700 - Batch update
Processing detected an invalid action type parameter on the input record.
Processing skips the current record and continues.
Verify and correct the input record supplied for &hlq.SDMHCNTL member DMHJCLBU; resubmit the job.
DMH0700 - Batch update
Processing detected that the referenced site name does not exist in the DMH_SITE table. This message may be paired with DMH2234W, and it identifies the rejected record using the unknown site.
Processing skips the current record and continues.
Verify and correct the input record supplied for &hlq.SDMHCNTL member DMHJCLBU; resubmit the job.
DMH0700 - Batch update
Processing detected a delete request for a file that does not exist in the referenced container.
Processing skips the current record and continues.
None
DMH0700 - Batch update
Processing detected an error or missing parameter on the input record.
Processing skips the current record and continues.
Verify and correct the indicated input record. Refer to valid format information in &hlq.SDMHCNTL member DMHJCLBU; resubmit the job.
DMH0700 - Batch update
Open failure for the INFILE DD data set.
Processing is stopped.
Verify and correct the data set information for the INFILE DD specified in &hlq.SDMHCNTL member DMHJCLBU; resubmit the job.
DMH0700 - Batch update
Processing successfully inserted a row into the DMH_ANALYSIS_QUEUE table.
The system is functioning normally.
None
DMH0700 - Batch update
Batch reanalysis does not support queuing a new SCM file.
Processing skips the current record and continues.
Use the Inventory function from the browser interface to add the SCM file to the database.
DB2 catalog scanner
This message is an informational banner.
The system is functioning normally.
None
DB2 catalog scanner
This message is an informational banner.
The system is functioning normally.
None
COBOL and PL/I scanner
The program file name was not passed to the scanner. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The parameter passed to the scanner is invalid. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to open the options file.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to read the options file.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to open the SYSADATA file. The compiler may fail to generate the SYSADATA file.
Processing stops.
Verify the source program can be compiled. If not, fix the compile errors and run the inventory again.
COBOL and PL/I scanner
The scanner failed to close the SYSADATA file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to read the SYSADATA file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner found invalid contents in the SYSADATA file.
Processing stops.
Verify the source program can be compiled. If not, fix the compile errors and run the inventory again. If the source program can be compiled, contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner found invalid contents in the SYSADATA file.
Skip the invalid contents and continue the processing.
Verify the source program can be compiled. If not, fix the compile errors and run the inventory again.
COBOL and PL/I scanner
The scanner found that the source program includes syntax of Object Oriented COBOL. This message occurs for COBOL components only.
Processing stops.
None. Object Oriented COBOL is not supported.
COBOL and PL/I scanner
The scanner found that another program structure starts after a program structure ends. This message occurs for COBOL components only.
Continue processing for the first program.
None
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to open the import file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to close the import file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to write the import file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The parameter of the scanner is invalid. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The parameter passed to the scanner is invalid. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to open the file.
Processing stops.
Verify the file exists. If the file is a copy or include file, verify that the correct concatenation set is specified.
COBOL and PL/I scanner
The scanner failed to close the file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to read the file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner failed to read the file.
Processing stops.
Run the inventory again. If the same error occurs again, contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner found invalid syntax in the macro definition file.
Processing stops.
Correct the invalid syntax in the macro definition file and then execute the inventory again.
COBOL and PL/I scanner
The scanner found invalid information in the mapping file. This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
Found invalid data for EXEC statement in ADATA.
Skip the EXEC statement and continue processing.
Verify the source program can be compiled. If not, fix the compile errors and run the inventory again.
COBOL and PL/I scanner
The program refers COPY or INCLUDE members, but serah path information is empty.
Processing stops.
Verify the concatenation set of the program. If not, set the correct concatenation set and run the inventory again.
COBOL and PL/I scanner
The program refers COPY or INCLUDE member, but the scanner can not find the member.
Processing stops.
Verify the concatenation set of the program. If not, set the correct concatenation set and run the inventory again.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner found unsupported syntax in an EXEC statement at the location indicated by token.
Ignore the EXEC statement and continue the processing.
Correct the EXEC statement if it is not valid. If the statement is valid, contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner found an invalid ending of an EXEC statement.
Ignore the EXEC statement and continue the processing.
Correct the EXEC statement if it is not valid. If the statement is valid, contact your IBM technical-support representative.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner found an undeclared data element in an EXEC statement.
Processing continues
Correct the EXEC statement if it is not valid.
COBOL and PL/I scanner
This is an internal error of the application.
Processing stops.
Contact your IBM technical-support representative.
COBOL and PL/I scanner
The scanner found a token that is too long.
The token is truncated and processing continues.
None
COBOL and PL/I scanner
The label in an EXEC statement was not found.
Processing continues.
Correct the EXEC statement if it is not valid.
This chapter describes all messages and codes generated by the WebSphere Studio Asset Analyzer distributed program modules.
WsaaJar
An attempt was made to analyze a resource, such as a file system or a configuration-management system, that is null or empty.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Verify the correct path with your system administrator and ensure that it is specified correctly in /assetloc/config/admin.cfg. The resource path must be active and accessible to WebSphere Studio Asset Analyzer.
WsaaJar
At least one error occurred while loading and parsing the contents of 'filename'.
Stop request processing.
Check the log file for the list of errors.
WsaaJar
The code attempted to retrieve an object of name 'name' and type 'type' which wasn't created during static initialization. Possible causes include 1) a problem loading external configuration files, 2) a misconfigured database, or 3) a syntax error in the code.
Stop request.
Check the log file for more information.
WsaaJar
The annotation text submitted was successfully added to the component.
The annotation text has been updated in the database.
None
WsaaJar
The annotation text is too long.
Processing stops and the annotation text is not added to the component.
Rewrite the annotation text to have less than maximum annotation length characters and submit the annotation again.
WsaaJar
Application names can contain uppercase letters, numbers, and the characters #, @, _ and $.
Processing stops. The user is prompted again for the application name.
Remove the "invalid character" character from the application name and try your operation again.
WsaaJar
A concatenation set requires a name.
Processing stops. The user is prompted again for the concatenation set name.
Try your operation again after specifying a name for the concatenation set.
WsaaJar
Concatenation set names can contain uppercase letters, numbers, and the characters #, @, and $.
Processing stops. The user is prompted again for the concatenation set name.
Try your operation again after removing the invalid characters from the concatenation set name.
WsaaJar
Concatenation set names cannot start with a number.
Processing stops. The user is prompted again for the concatenation set name.
Try your operation again after removing the invalid characters from the concatenation set name.
WsaaJar
Concatenation set names must be unique.
Processing stops. The user is prompted again for a unique concatenation set name.
Try your operation again after specifying a unique concatenation set name.
WsaaMain
The scanner cannot access the specified resource from the zip file.
Scanning of the current asset is skipped, and processing continues with the next asset. The error is logged.
Verify that the zip file is not corrupted.
WsaaJar
Information required to fully display graphics is not available from the database.
The database is in an inconsistent state. Contact your IBM technical-support representative.
Processing stops and some or all of the graphic cannot be displayed.
WsaaJar
Information required to fully display graphics is not available from the database.
Processing stops and some or all of the graphic cannot be displayed.
The database is in an inconsistent state. Contact your IBM technical-support representative.
WsaaJar
An exception occurred while processing the request.
Request processing stopped.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred while interacting with the database.
Request processing stopped.
Contact your IBM technical-support representative.
WsaaJar
In the inventory wizard, the MVS library was not specified.
Processing stops and the user is prompted again for the location to be inventoried.
Enter in the location of data to be inventoried and try your operation again.
WsaaJar
Data set name must start with:
Processing stops and the user is prompted again for the location to be inventoried.
Verify that the data set name starts with a valid character and try your operation again.
WsaaJar
Data set name must only contain:
The user is prompted again for the location to be inventoried.
Verify that the data set name only contains valid characters and try your operation again.
WsaaJar
An I/O error occurred while trying to analyze the Java resource specified by name.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Verify that the file is a valid syntax file (for example, that it is a valid Java class) and that the proper permissions for reading the file are in place.
WsaaMain
Informational message logged to indicate that the appropriate scanner is being loaded so that scanning can begin.
The system is functioning normally.
None
WsaaMain
An unexpected error occurred during the initialization of the schema or during the scanning operation itself. The exact error is indicated.
The scanning process is stopped for the current asset, and processing does not continue. The error is logged.
Check the error logs for an indication of what caused the error. If the cause is related to database access of schema initialize, attempt to fix the problem and start the scanning operation again. Contact your IBM technical-support representative if more help is required.
WsaaMain
A problem was encountered during the scanning operation while trying to access the specified resource or file. The problem could be related to an invalid or unavailable scanning root, resource, or configuration-management system; a file that cannot be read because the content is invalid; or some undetermined error accessing the file, directory, or resource.
Verify that the specified scanning root, directory, file, or resource is available, defined correctly, accessible, and contains valid content. Try the scanning operation again.
The scanning process ends for the specified scanning root. The error is logged, and scanning will continue on the next scanning root.
WsaaMain
This is an informational message directing the user to the error logs for more information. This message will be displayed when the problem encountered requires more extensive information from the log files. These problems include the inability to access a specified resource (for example, PVCS or CMVC), problems with database access, or problems during scanning and analysis.
The system is functioning normally.
View information in one of several error and information log files on the distributed server in the <dmh>\log directory. You may have to contact your system administrator, depending upon the problems described in the logs. After the errors are fixed, try the scanning operation again.
WsaaMain
WebSphere Studio Asset Analyzer requires that a unique scanner letter be specified for each scanner identified in /assetloc/config/Scanners.cfg. This error occurs when the scanner letter specified is already in use for a scanner identified to WebSphere Studio Asset Analyzer. This error typically occurs after a new scanner has been added.
The scanner specified cannot be instantiated, so scanning stops for any scanning roots associated with this scanner. Processing continues with the next scanning root that has a valid scanner specified.
Ensure that you have correctly defined the specified scanner in /assetloc/config/Scanners.cfg and attempt the scanning operation again.
WsaaJar
The filter cannot have an inner wildcard.
The user is prompted again for the filter of the inventory.
Remove the wildcard asterisk (*) from the middle of the filter and submit again.
WsaaMain
This is an unexpected error in which a scanner defined in /assetloc/config/Scanners.cfg could not be instantiated. The error may be related to problems with the scanner specification itself or to an inconsistency in the WebSphere Studio Asset Analyzer installed code, or to the environment classpath. This error typically occurs when a new scanner has been added incorrectly.
Scanning stops for the scanning root associated with the scanner specified. The error is logged and processing continues with the next scanning root that has a valid scanner specified.
Ensure that you have correctly defined the specified scanner in the configuration file. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An unexpected I/O error occurred while trying to read the specified resource. This error can be due to incorrect file permissions or corrupt data in the resource itself.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Check the file permissions for the specified resource to ensure that the file can be opened and read. Also verify that the content is as expected. Attempt the scanning operation again after correcting the problems.
WsaaMain
This is an informational message written to the logs indicating that old resources are being deleted from the database prior to writing new resources.
The system is functioning normally.
None
WsaaJar
An error was encountered while attempting to parse the specified resource. This error can occur if data encountered during parsing is unexpected or not supported by the source code language represented by the resource type.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Verify that the resource specified can be compiled using the resource type's compiler and attempt the scanning operation again after correcting any compiler errors. If more help is required, capture all logs related to the error and contact your IBM technical-support representative.
WsaaMain
This is an informational message written to the logs indicating that the log files themselves were successfully created.
The system is functioning normally.
None
WsaaMain
This is an informational message written to the logs indicating that the distributed scanner successfully initialized the WebSphere Studio Asset Analyzer database so that processing can continue.
The system is functioning normally.
None
WsaaMain
This is an informational message written to the logs indicating that the distributed scanner has been successfully initialized.
The system is functioning normally.
None
WsaaMain
An unexpected error has occurred during parsing, which can be caused by the occurrence of an unsupported character in the specified resource.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Examine the resource for any unsupported characters and attempt the scanning operation again after correcting the error.
WsaaMain
The specified configuration file could not be read for any of the following reasons:
The scanning process stops for all assets. The scanner will not be able to function until the error is fixed.
Ensure that all installation steps have been performed correctly according to the Configuration and Migration Guide. The wsaaHome property value must be set and correctly refer to the location of your installed WebSphere Studio Asset Analyzer application. Additionally, the configuration files must be accessible in /assetloc/config off of your wsaaHome directory, and the file permissions must be set for read access. If you have changed the configuration files, verify that your changes are syntactically correct.
WsaaJar
An unexpected error has occurred while trying to create the log directory required for WebSphere Studio Asset Analyzer. An attempt is made to create the log directory off of the WebSphere Studio Asset Analyzer root installation directory, in <dmhInstall>\log.
The scanning process stops for all assets. The scanner will not be able to function until the error is fixed.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to directions in the Configuration and Migration Guide and that adequate space exists to create the log directory and the logs themselves during WebSphere Studio Asset Analyzer runtime. The directory in which WebSphere Studio Asset Analyzer is installed must have the correct permissions so that WebSphere Studio Asset Analyzer can create the directory and the logs. The directory name must be set in common.cfg using the logDir parameter.
WsaaJar
An unexpected error has occurred while trying to create the logs required for WebSphere Studio Asset Analyzer. An attempt is made to create the logs in the location specified by the user in the logDir parameter of the Common.cfg file.
The scanning process stops for all assets. The scanner will not be able to function until the error is fixed.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to directions in the Configuration and Migration Guide and that adequate space exists to create the logs during WebSphere Studio Asset Analyzer runtime. The directory in which WebSphere Studio Asset Analyzer is installed must have the correct permissions so that WebSphere Studio Asset Analyzer can create the logs and Common.cfg must point to the correct log directory.
WsaaJar
An unexpected error occurred while trying to connect to the WebSphere Studio Asset Analyzer database. The logs will contain more specific information about the error.
The scanning process stops for all assets. The scanner will not be able to function until the error is fixed.
Examine the error logs for DB2-related exceptions. Check the database user name and password in the Common.cfg file. Attempt the scanning operation again after correcting any errors.
WsaaJar
An unexpected exception has occurred during the scanning and analysis of the specified resource. This error usually indicates an corrupted asset. Specific information related to this exception can be found in the WebSphere Studio Asset Analyzer logs.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Refer to the WebSphere Studio Asset Analyzer logs for specific information on the analysis problems encountered, correct any errors and attempt the scanning process again. Contact your IBM technical-support representative if problems identified cannot be corrected locally.
WsaaJar
An unexpected error has occurred during the scanning process. The cause may be related to initialization and setup activities, problems removing existing resources from the WebSphere Studio Asset Analyzer database, or problems scanning the resources themselves. More detailed information can be found in the WebSphere Studio Asset Analyzer logs.
If the error is related to a specific asset, the scanning of that asset is skipped. If the error is related to a specific scanner, scanning of all asset types associated with that scanner is skipped. Processing continues with the next asset or scanner type. The error is logged.
Refer to the WebSphere Studio Asset Analyzer logs to determine the problems, correct them, and attempt the scanning operation again. Contact your IBM technical-support representative if the problems persist.
WsaaJar
An unexpected error was encountered while attempting to write metadata about the specified resource to the WebSphere Studio Asset Analyzer database. More information about this error can be found in the WebSphere Studio Asset Analyzer logs.
Analysis of the current asset is skipped, and processing continues for the next asset. The error is logged.
Refer to the WebSphere Studio Asset Analyzer logs for information related to this error, correct any problems, and attempt the scanning operation again. Contact your IBM technical-support representative if the problems persist and cannot be corrected.
WsaaJar
This is an information message documenting the status of the scanning process.
The system is functioning normally.
None
WsaaJar
This is an informational message documenting the status of the scanning process.
The system is functioning normally.
None
WsaaJar
An exception occurred due to an unexpected interruption of the scanner while it is in sleep mode or otherwise paused by a user.
The scanning process, even in sleep mode, is stopped.
To schedule the scanning operation, you must restart the scanner. It will then be in sleep mode again as indicated by the configuration file settings. Refer to the WebSphere Studio Asset Analyzer logs for further information and attempt the scanning operation again.
WsaaJar
This is an informational message indicating that the ShouldUseTimer property in /assetloc/config/Admin.cfg is set to false so that scanning begins immediately upon invocation.
The system is functioning normally. The scanning will begin processing upon invocation.
If you wish to delay scanning, you must set the ShouldUseTimer property to true and set a value for the TimeToCrawl property.
WsaaJar
This is a warning message written to the WebSphere Studio Asset Analyzer logs indicating that while the ShouldUseTimer property in /assetloc/config/Admin.cfg is set to true, there is no value set for the associated TimeToCrawl property. Therefore, scanning begins immediately upon invocation.
The system is functioning normally. Scanning will begin upon invocation.
If you wish to delay scanning, you must set the ShouldUseTimer property to true and set a value for the TimeToCrawl property.
WsaaJar
This is a warning message written to the WebSphere Studio Asset Analyzer logs indicating an invalid value was specified for the TimeToCrawl property in /assetloc/config/Admin.cfg so that the time for the scanner to begin cannot be computed. As a result, scanning begins immediately upon invocation.
The system is functioning normally. Scanning will begin upon invocation.
If you wish to delay scanning, ensure that you have correctly specified the value for the TimeToCrawl property.
WsaaJar
This is an informational message indicate whether the scanner will be running in GUI or non-GUI mode. In GUI mode, a user interface dialog opens for the user to initiate scanning; otherwise, no user interface will be provided, and scanning will begin.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that a resource is currently being scanned.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that a resource is currently being analyzed.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that a resource has been analyzed.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that the scanning process has completed.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that the analysis process has been skipped for a resource type that is not supported.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that the analysis process on a resource has been skipped due to an invalid resource exception. The details of the exception can also be found in the log.
The current asset is skipped, and scanning continues with the next asset.
Determine if the asset skipped is corrupted and attempt to correct it. If the problem persists, contact your IBM technical-support representative.
WsaaJar
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that a softlink on a Linux platform was encountered in a resource during scanning will not be processed because it does not refer to a resource that can be accessed.
The softlink asset is skipped, and scanning resumes with the next asset.
None
WsaaMain
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that the specified resource is being extracted for analysis.
The system is functioning normally.
None
WsaaMain
This is an unexpected error in which an extractor for use in obtaining resources of a specific type supported by WebSphere Studio Asset Analyzer could not be instantiated. The error is related to an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Scanning on the current set of assets for an extractor is skipped, and the error is logged. Processing continues for the set of assets associated with a different extractor.
Verify that WebSphere Studio Asset Analyzer was installed properly and that the file EColabraApplication.cfg contains the correct extractors section with the correct extractor for the specific asset. If the problem persists, capture all logs related to the error and contact your IBM technical-support representative.
WsaaMain
An invalid resource, or one that cannot be accessed or read, has been encountered during the extraction step in the scanner. This message, along with any pertinent details, can be found in the WebSphere Studio Asset Analyzer logs.
Scanning on the current asset is skipped, and the error is logged. Processing continues for the next asset.
Refer to the WebSphere Studio Asset Analyzer logs for details on the exception, correct any errors, and attempt the scanning operation again. Contact your IBM technical-support representative if the problem persists.
WsaaMain
An exception was encountered during the extraction of a particular asset during the scanning process.
Extraction and scanning of the current asset is skipped, and the error is logged. Processing continues for the next asset.
Refer to the WebSphere Studio Asset Analyzer logs for specific details on the extraction process that encountered the error. Correct the problem, if possible, and attempt the scanning operation again.
WsaaJar
During scanning of resources in a ClearCase repository, a view has been specified or encountered that is not a valid directory.
Scanning of the current view is stopped, and the error is logged. Processing continues with the next scanning root.
Refer to the WebSphere Studio Asset Analyzer logs for more detail and correct the problem, if possible. Consult your WebSphere Studio Asset Analyzer administrator or your ClearCase repository administrator for more information.
WsaaJar
During scanning of resources in a ClearCase repository, an unexpected I/O error occurred or the process was interrupted while trying to invoke the ClearCase lsview command.
The error is logged and the system tries to create the view as if it did not exist. The scanning process continues as if the view did not exist.
Refer to the WebSphere Studio Asset Analyzer logs for more detail and correct the problem, if possible. Consult your WebSphere Studio Asset Analyzer administrator or your ClearCase repository administrator for more information.
WsaaJar
During scanning of resources in a ClearCase repository, an unexpected I/O error occurred or the process was interrupted while trying to invoke the ClearCase mkview command.
Scanning of the current view is stopped, and the error is logged. Scanning resumes with the next view.
Refer to the WebSphere Studio Asset Analyzer logs for more detail and correct the problem, if possible. Consult your WebSphere Studio Asset Analyzer administrator or your ClearCase repository administrator for more information.
WsaaJar
During scanning of resources in a ClearCase repository, the ClearCase mkview command was issued but failed to complete successfully, returning the specified error code.
Scanning of the current view is stopped, and the error is logged. Scanning resumes with the next view.
Refer to the WebSphere Studio Asset Analyzer logs or consult your ClearCase documentation for more information on the specific error code. Consult your WebSphere Studio Asset Analyzer administrator or your ClearCase repository administrator for more information.
WsaaJar
During scanning of resources in a ClearCase repository, the ClearCase setcs command was issued but failed to complete successfully due to an exception.
Scanning of the current view is stopped, and the error is logged. Scanning resumes with the next view.
Refer to the WebSphere Studio Asset Analyzer logs for more detail and correct the problem, if possible. Consult your WebSphere Studio Asset Analyzer administrator or your ClearCase repository administrator for more information.
WsaaJar
During scanning of resources in a ClearCase repository, the ClearCase setcs command was issued but failed to complete successfully, returning the specified error code.
Scanning of the current view is stopped, and the error is logged. Scanning resumes with the next view.
Refer to the WebSphere Studio Asset Analyzer logs or consult your ClearCase documentation for more information on the specific error code. Consult your WebSphere Studio Asset Analyzer administrator or your ClearCase repository administrator for more information.
WsaaJar
During scanning of resources in a ClearCase repository, WebSphere Studio Asset Analyzer was unable to create the views target directory specified.
Scanning of the current view is stopped, and the error is logged. Scanning resumes with the next view.
Refer to the WebSphere Studio Asset Analyzer logs or consult your ClearCase documentation for more information on the specific error code. Consult your WebSphere Studio Asset Analyzer administrator or your ClearCase repository administrator for more information.
WsaaJar
This is an informational message indicating that the scanning process has completed.
The system is functioning normally.
None
WsaaJar
During initialization of the scanner, WebSphere Studio Asset Analyzer was unable to retrieve host information for the location of the WebSphere Studio Asset Analyzer host system.
The scanning process cannot be initialized and is stopped. The error must be corrected before scanning can function properly.
Verify that you have correctly installed WebSphere Studio Asset Analyzer, specifying all valid host information according to the instructions in the Configuration and Migration Guide. Correct the problem and attempt the scanning operation again.
WsaaJar
An invalid module type, as specified, was encountered during analysis of an ear file. Valid module types are war or Web modules, ejb files, or java client files.
Analysis of the current asset is skipped, and the error is logged. Processing continues with the next asset.
Ensure that the resources being scanned contain valid modules. Correct any problems and attempt the scanning operation again.
WsaaJar
An attempt was made to create a temporary file with contents from a resource being scanned, but the temporary file could not be created. Possible causes are: I/O errors, such as space or directory permission problems, or WebSphere Studio Asset Analyzer exceptions while attempting to read or parse the resource.
Analysis of the current asset is skipped, and processing continues with the next asset.
Ensure that your WebSphere Studio Asset Analyzer Windows server has adequate space for creating temporary files and that the appropriate directory and file permissions exist. Your WebSphere Studio Asset Analyzer logs may contain more detailed information about the exception. Contact your IBM technical-support representative if the problem persists.
WsaaJar
An attempt was made to open a temporary file created to contain archive file (ear, war, java, ejb) contents. Possible causes are insufficient space or incorrect file permissions.
Analysis of the current asset is skipped, and processing continues with the next asset.
Ensure that the temporary file exists and can be accessed. Consult the WebSphere Studio Asset Analyzer logs for more detailed information on the error.
WsaaJar
The type of archive containing a resource being scanned is incorrect or cannot be determined. The load strategy refers to either a resource in an archive (ear, war) or a directory, but the strategy detected is neither of those.
Analysis of the current asset is skipped, and processing continues with the next asset.
This error reflects an unusual condition in the WebSphere Studio Asset Analyzer scanner. Consult the WebSphere Studio Asset Analyzer logs for more details on the exception. Contact your IBM technical-support representative if the problem persists.
WsaaJar
An exception occurred during scanning of the specified resource because an EJB was expected but the resource is not an EJB file.
Analysis of the current asset is skipped, and processing continues with the next asset.
Make sure that WebSphere Studio Asset Analyzer is properly installed and the classpath is set correctly.
WsaaJar
During initialization of the scanner, WebSphere Studio Asset Analyzer was unable to site information that should already exist in the database system. The process cannot continue.
The scanning process cannot be initialized and is stopped. The error must be corrected before scanning can function properly.
Verify that you have correctly installed WebSphere Studio Asset Analyzer, specifying all database access information according to the instructions in the Configuration and Migration Guide. Correct the problem and attempt the scanning operation again. Consult the WebSphere Studio Asset Analyzer logs for more information.
WsaaJar
An exception has occurred during the scanning process related to database metadata persistency. This is an unexpected condition indicating that an inconsistency exists between expected results and data stored in the database.
The scanning process cannot be initialized and is stopped. The error must be corrected before scanning can function properly.
Consult the WebSphere Studio Asset Analyzer logs for more information related to possible database communications errors. Contact your IBM technical-support representative.
WsaaJar
An exception was encountered during postprocessing because required analyzers could not be accessed. The most likely cause is that the analyzers are not configured properly.
Processing for the specified postprocessor is skipped, and the error is logged. Processing continues for the next postprocessor.
Verify that you have properly configured all analyzers for the resources you are attempting to analyze and try the scanning operation again. The analyzers are configured by the administrator in /assetloc/config/analyzers.cfg.
WsaaJar
An exception was encountered during postprocessing because required postprocessors could not be accessed. The most likely cause is that the postprocessors were not configured properly.
Processing for the specified postprocessor is skipped and the error is logged. Processing continues for the next postprocessor.
Verify that you have properly configured all postprocessors for the resources you are attempting to analyze and try the scanning operation again. The postprocessors are configured by the administrator in /assetloc/config/EColabraApplication.cfg. This file is not routinely updated by users, so contact your IBM technical-support representative for more information.
WsaaJar
During postprocessing, an exception occurred while attempting to categorize the resources analyzed.
Postprocessing is skipped for the categorization type specified, and the error is logged. Processing continues for the next categorizer.
Consult your WebSphere Studio Asset Analyzer administrator or your IBM technical-support representative.
WsaaJar
During postprocessing, categorization was not performed because it was not activated.
The system is functioning normally. Categorizer postprocessors are skipped.
If you want the categorizer postprocessors to run, set the Java virtual machine property Categorizer to true.
WsaaJar
The file pattern cannot contain blanks.
The user is prompted again for the file pattern.
Remove the blanks from the file pattern and submit again.
WsaaJar
An exception was thrown that cannot be processed.
The exception is logged and displayed to the user. Current processing stops.
Contact your IBM technical-support representative.
WsaaJar
The SQL statement did not have the verb SELECT in it.
The SQL query was not executed.
Contact your IBM technical-support representative.
WsaaJar
Valid containers must exist.
Processing stops. The user is prompted again for the container names.
Try your operation again after adding only containers that exist.
WsaaJar
A container name must be specified.
Processing stops. The user is prompted again for the container names.
Add a valid container name or click the cancel button.
WsaaJar
The application name is required if the inventory is to be added to a new application.
Processing stops. The user is prompted for the application name.
Specify a new application name, an existing application, or do not add the inventory to an application at this time.
WsaaJar
Impact analysis is being performed.
The system is functioning normally.
None
WsaaJar
An unexpected exception was thrown.
Impact analysis processing has halted.
Contact your IBM technical-support representative.
WsaaJar
The concatenation set has been assigned.
The system is functioning normally.
None
WsaaJar
The default concatenation sets for the component have been updated.
The system is functioning normally.
None
WsaaJar
The scanning request has been queued and will be run when the scans in front of it have finished.
The system is functioning normally.
None
WsaaJar
Impact analysis names must be unique.
Processing stops. The user is prompted again for a unique impact analysis name.
Try your operation again after specifying a unique impact analysis name.
WsaaJar
The impact analysis has been renamed.
The system is functioning normally.
None
WsaaJar
The new impact analysis name must not be blank, must not be the old name, and must be unique.
Processing stops. The user is prompted again for a new impact analysis name.
Try your operation again after specifying a unique impact analysis name.
WsaaJar
The description of the impact analysis has been updated.
The system is functioning normally.
None
WsaaJar
The type of asset to be analyzed has changed.
The system is functioning normally.
None
WsaaJar
The impact analysis has been created.
The system is functioning normally.
None
WsaaJar
The impact analysis "ia name" has already been created.
The impact analysis name is prompted for again.
Update the name to create a new impact analysis. Click button to continue with the impact analysis.
WsaaJar
There was an error while trying to create the impact analysis. This is most likely due to duplicate name for the current user.
Processing stops. The impact analysis was not created successfully.
Contact your IBM technical-support representative.
WsaaJar
The description for the impact analysis cannot be updated.
Processing stops. The description of the impact analysis remains the same.
Contact your IBM technical-support representative.
WsaaJar
The impact analysis requires a nonblank name.
Processing stops. The user is prompted again for an impact analysis name.
Try your operation again after specifying an impact analysis name.
WsaaJar
The impact analysis has a character that is not allowed in the name.
Processing stops. The user is prompted again for an impact analysis name.
Verify that the impact analysis name only contains valid characters and try your operation again.
WsaaJar
Description is required for the impact analysis
Processing stops. The user is prompted again for an impact analysis description.
Enter a description and try your operation again.
WsaaJar
Asset type is required for the impact analysis.
Processing stops. The user is prompted again for an asset type.
Fill in the asset type and try your operation again.
WsaaJar
Impact analysis names must be less than or equal to 64 characters long.
Processing stops. The user is prompted again for an impact analysis name.
Try your operation again after specifying a shorter impact analysis name.
WsaaJar
Impact analysis description must be less than or equal to 256 characters long.
Processing stops. The user is prompted again for an impact analysis description.
Try your operation again after specifying a shorter impact analysis description.
WsaaJar
During analysis, an unexpected SQL error has occurred while trying to add references between two assets managed by WebSphere Studio Asset Analyzer. The assets that could not be related are specified.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Consult the WebSphere Studio Asset Analyzer logs for more details on the SQL error. Ensure that you have installed WebSphere Studio Asset Analyzer properly according to the Configuration and Migration Guide. Contact your IBM technical-support representative for more information.
WsaaJar
The system property wsaaHome must be defined. It points to the WebSphere Studio Asset Analyzer installation root directory and is set during installation of the product. The value can be found in /config/Common.cfg as well as in the JVM properties for WebSphere Application Server.
The scanning process stops for all assets. The scanner will not be able to function until the error is fixed.
Verify that you have successfully installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide. If you cannot verify that, check the value of wsaaHome in your /config/Common.cfg file on MVS as well as on your Windows server. Also check for a valid value in your WebSphere Application Server configuration file on MVS (WAS V4) or in the JVM properties for your WAS Server using the Administration Console. If you must update the value, remember to restart your HTTP or WAS server.
WsaaJar
This is an unexpected error in which an analyzer defined in /assetloc/config/Analyzers.cfg could not be instantiated. The error may be related to errors in specifying the postprocessor, or an inconsistency in the WebSphere Studio Asset Analyzer installed code, or the environment classpath.
Analysis stops for any assets associated with the analyzer that cannot be loaded. The error is logged, and processing continues for the next valid set of asset types.
Ensure that you have correctly defined the specified analyzer in the configuration file. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An analyzer for the specified type does not exist because it has not been defined in /assetloc/config/Analyzers.cfg.
Analysis using this analyzer will not be performed. The error is logged, and processing continues for the next set of valid assets.
Add the analyzer definition to the Analyzers.cfg file and perform the scanning operation again.
WsaaJar
This is a warning indicating that multiple analyzers have been defined in /assetloc/config/Analyzers.cfg for the same resource type.
The first analyzer encountered will be used, and subsequent analyzers will be ignored. Processing continues normally.
Ensure that you have correctly defined the analyzers and their resource type mappings and perform the scanning operation again.
WsaaJar
An unexpected error has been encountered while attempting to run the specified postprocessor. The specific cause of the error will be found in the WebSphere Studio Asset Analyzer error logs.
Postprocessing is stopped for the specified postprocessor. The error is logged and processing continues.
Refer to the WebSphere Studio Asset Analyzer error logs for specific information on the error. Correct any problems and perform the scanning operation again.
WsaaJar
This is an unexpected error in which a postprocessor defined in /assetloc/config/EColabraApplication.cfg could not be instantiated. The error may be related to errors in specifying the postprocessor or an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Postprocessing is stopped for the specified postprocessor. The error is logged and processing continues. Other postprocessors that depend on the one that could not be loaded may be affected.
Ensure that you have correctly defined the specified postprocessor in the configuration file. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
This is an informational message indicating that the specified postprocessor has started.
The system is functioning normally.
None
WsaaJar
An unexpected error has occurred during postprocessing for the specified postprocessor. More specific information about the error can be found in the WebSphere Studio Asset Analyzer error logs.
Postprocessing is stopped for the specified postprocessor. The error is logged and processing continues.
Consult the WebSphere Studio Asset Analyzer error logs for specific information on the error. Contact your IBM technical-support representative if you cannot resolve the problems.
WsaaJar
While preparing to run a postprocessor, the process encountered an analyzer that was set as a precondition for the postprocessor. The analyzer has not been defined, has not been configured to run, or had problems running. The analyzer in error is specified. Analyzers are defined in /assetloc/config/Analyzers.cfg.
The postprocessor that caused the error is stopped. The error is logged and processing continues.
Ensure that you have correctly specified all required analyzers in the configuration file and perform the scanning operation again.
WsaaJar
While running postprocessing, the specified postprocessor is required but not configured in /assetloc/config/EColabraApplicaiton.cfg. Postprocessing cannot continue.
Postprocessing is stopped for the specified postprocessor. The error is logged and processing continues.
Ensure that you have correctly specified all required postprocessors in the configuration file and perform the scanning operation again.
WsaaJar
The definition of the specified postprocessor is incorrect in /assetloc/config/EColabraApplication.cfg. Postprocessing cannot continue.
Postprocessing is stopped for the dependent. The error is logged and processing continues.
Ensure that you have correctly specified the postprocessors in the configuration file and perform the scanning operation again.
WsaaJar
During postprocessing, a dependent postprocessor failed to complete successfully. Details about the error can be found in the WebSphere Studio Asset Analyzer error logs.
Postprocessing is stopped for the dependent postprocessor. The error is logged and processing continues.
Ensure that you have correctly specified the postprocessors in the configuration file. Consult the WebSphere Studio Asset Analyzer error logs for more detailed information, correct any errors, and perform the scanning operation again. Consult your IBM technical-support representative if you cannot resolve the issue.
WsaaJar
This is a warning message written to the WebSphere Studio Asset Analyzer logs indicating that the analyzer specified for the indicated resource type will not be used for analysis. This is either because another analyzer is already defined for the specified resource type or the analyzer specified cannot be found or instantiated. This message always follows DMH5134W or DMH5135W.
Analysis of the current asset is skipped, and processing continues with the next asset. The error is logged.
Ensure that you have correctly specified one, and only one, analyzer per resource type in the /assetloc/config/Analyzers.cfg file and attempt the scanning process again.
WsaaJar
This is an informational message indicating that old resources will be deleted prior to rescanning those resources. Deletion of old resources occurs when the auto delete flag is set to true in the /assetloc/config/Scanners.cfg file.
The system is functioning normally.
None
WsaaJar
This is a warning message that occurs when the scanning process has completed and attempts to notify the WebSphere Studio Asset Analyzer servlet. The exceptioncode provides the reason for the unavailability.
The scanner signals to the servlet by way of the database; when the servlet is run it tries to read the value from the database. The system continues to function normally.
None
WsaaJar
An attempt was made to run the distributed scanner for a site specified by server1when it has already been run for a different site specified by WebSphere Studio Asset Analyzer does not support multiple sites at this time. Scanning must be performed on a single WebSphere Studio Asset Analyzer Windows server.
Perform the scanning operation again on the WebSphere Studio Asset Analyzer Windows server used previously as specified in the database.
The scanning process is stopped.
WsaaJar
Invalid first character in the file field.
The user is prompted again for the file.
Correct the file name and submit again.
WsaaJar
Valid characters are only upper case letters, numbers, special characters (#, @, and $), and the asterisk (*).
The user is prompted again for the file.
Correct the file name and submit again.
WsaaJar
This is an unexpected error indicating that the proper initializations could not be performed to initiate the distributed scanning processor. This error may be caused by a WebSphere Studio Asset Analyzer installation error or a problem with the classpath.
The scanning process is stopped, and the error is logged.
Consult your WebSphere Studio Asset Analyzer error logs and contact your IBM technical-support representative if the issue cannot be resolved.
WsaaJar
This is an unexpected error in which a scanner defined in /assetloc/config/Scanners.cfg could not be instantiated. The error may be related to errors in specifying the postprocessor, or an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Scanning is stopped for the process related to the specified retriever. The error is logged, and scanning continues for the next retriever to be loaded.
Ensure that you have correctly defined the specified scanner in the configuration file. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
File names can only be eight characters.
The user is prompted again for the file.
Correct the file name and submit again.
WsaaJar
Application names must be unique.
The user is prompted again for the application name.
Type in a unique application name and try again.
WsaaJar
The application name must be less than 64 characters.
The user is prompted again for the application name.
Please type a shorter application name.
WsaaJar
No ChangeMan SERNET ids were found when searching the WebSphere Studio Asset Analyzer applications.
The system is functioning normally.
None
WsaaJar
The container specified during inventory collection cannot be found on the target system.
Processing stops.
Verify that the container specified exists, or specify an existing container, and try your operation again.
WsaaJar
A required field was not filled in.
The user is prompted for the required information.
Fill in the required field and submit the form again.
WsaaJar
The date has the wrong format or is invalid. Make sure the date format is YYYY-MM-DD.
The user is prompted for the date again.
Fill in the date in the required format.
WsaaJar
The date has two many dashes. The format should be YYYY-MM-DD.
The user is prompted for the date again.
Fill in the date in the required format.
WsaaJar
Date is required.
The user is prompted for the date again.
Fill in the date in the required format.
WsaaJar
During postprocessing, an unexpected error has occurred while attempting to delete relationships from the metadata stored in the inventory database. Details about the errors may be found in the WebSphere Studio Asset Analyzer error logs.
The error is logged, and processing continues. It is likely that relationships have not been deleted from the database.
Consult the WebSphere Studio Asset Analyzer error logs for details on possible DB2 connection or access problems. Consult your IBM technical-support representative if the issues cannot be resolved.
WsaaJar
An unexpected error has occurred during postprocessing. Details about the error can be found in the WebSphere Studio Asset Analyzer error logs.
Postprocessing has stopped, and the error is logged.
Consult the WebSphere Studio Asset Analyzer error logs. Fix any problems and attempt the scanning operation again. Contact your IBM technical-support representative if you cannot resolve the issue.
WsaaJar
Concatenation set names must be unique.
The existing concatenation set properties are displayed and the user can update those properties.
Continue updating the concatenation set or click cancel to quit the wizard.
WsaaJar
The concatenation set has been created.
The system is functioning normally.
None
WsaaJar
Lines must start with // or /*.
The error is presented to the user.
Correct the problem and submit again.
WsaaJar
An error was encountered during queue processing for inventory collection because JCL was encountered with one or more statements that exceed 80 characters. MVS JCL cannot contain statements longer than 80 characters.
Queue processing continues with the next asset to be inventoried. The inventory being processed when the error was encountered is not processed.
Correct the problem and try your inventory collection process again.
WsaaJar
An error was encountered during queue processing for inventory collection because JCL was encountered that does not contain a job card.
Queue processing continues with the next asset to be inventoried. The inventory being processed when the error was encountered is not processed.
Correct the problem and try your inventory collection process again.
WsaaJar
This is an informational message displayed when a user has selected the action to start postprocessing when it is already running.
Processing continues normally.
None
WsaaJar
The postprocessing has been started.
The user is notified of the status.
None
WsaaJar
Impact analysis process has been intentionally canceled. Results may be incomplete.
None
The system is functioning normally.
WsaaJar
An error was encountered during queue processing for inventory collection because JCL was encountered that contains more than 4 lines in the job card.
Queue processing continues with the next asset to be inventoried. The inventory being processed when the error was encountered is not processed.
Correct the problem and try your inventory collection process again.
WsaaJar
The concatenation set has been updated.
The concatenation set has been updated.
None
WsaaJar
An error occurred while attempting to store metadata about scanned resources to the DB2 database. The DB2 table, resource name, and identifier are specified.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Consult the WebSphere Studio Asset Analyzer error logs for potential problems with DB2 communications or access. Fix any problems and attempt the scanning process again. Consult your IBM technical-support representative if the issue cannot be resolved.
WsaaJar
An attempt was made to store metadata into a nonexistent column in the DB2 schema. This error reflects a possible inconsistency between the level of WebSphere Studio Asset Analyzer installed and the schema defined to DB2 for the WebSphere Studio Asset Analyzer database.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to the Configuration and Migration Guide. The schema is created during installation unless you have an existing database with the same name. Verify that the correct schema for the level of WebSphere Studio Asset Analyzer installed exists in the WebSphere Studio Asset Analyzer database. DDL used to create the database can be found in the /ddl directory.
WsaaJar
An attempt was made to store metadata into the DB2 table specified, but the semantics of the columns are not consistent with the expectations of the distributed scanner. This error is caused by an internal system problem.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to the Configuration and Migration Guide. The schema is created during installation unless you have an existing database with the same name. Verify that the correct schema for the level of WebSphere Studio Asset Analyzer installed exists in the WebSphere Studio Asset Analyzer database. DDL used to create the database can be found in the /ddl directory.
WsaaJar
An attempt was made to store metadata into a nonexistent table in the DB2 schema. This error reflects a possible inconsistency between the level of WebSphere Studio Asset Analyzer installed and the schema defined to DB2 for the WebSphere Studio Asset Analyzer database.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to the Configuration and Migration Guide. The schema is created during installation unless you have an existing database with the same name. Verify that the correct schema for the level of WebSphere Studio Asset Analyzer installed exists in the WebSphere Studio Asset Analyzer database. DDL used to create the database can be found in the /ddl directory.
WsaaJar
The user is not authorized to perform the action or the credentials are incorrect.
The user is not allowed to perform the specified action.
Type in the correct credentials to perform the action.
WsaaJar
The application name is a required field.
The user is prompted again for the application name.
Type in the application name and submit again.
WsaaJar
An unexpected error has occurred while attempting to instantiate the scanner and analyzer managers to begin the scanning process. This reflects an inconsistency in the installed WebSphere Studio Asset Analyzer application.
The initialization of the distributed servlet cannot continue. This problem will cause errors starting your HTTP server if you are running WAS on MVS. If you are running WAS on Windows, the WAS server will likely start but the WebSphere Studio Asset Analyzer distributed servlet will not be properly initialized. You must resolve the initialization issue before you can use the distributed scanner function.
Capture all pertinent WebSphere Studio Asset Analyzer logs and contact your IBM technical-support representative.
WsaaJar
During the scanning process, an unexpected error has occurred while attempting to delete existing resources from the metadata stored in DB2 for the container being scanned. Details about the errors may be found in the WebSphere Studio Asset Analyzer error logs.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset or scanning root.
Consult the WebSphere Studio Asset Analyzer error logs for details on possible DB2 connection or access problems. Consult your IBM technical-support representative if the issues cannot be resolved.
WsaaJar
An unexpected error has occurred during initialization of the distributed scanner processes. This reflects an inconsistency in the installed WebSphere Studio Asset Analyzer application.
The initialization of the distributed servlet cannot continue. This problem will cause errors starting your HTTP server if you are running WAS on MVS. If you are running WAS on Windows, the WAS server will likely start but the WebSphere Studio Asset Analyzer distributed servlet will not be properly initialized. You must resolve the initialization issue before you can use the distributed scanner function.
Capture all pertinent WebSphere Studio Asset Analyzer logs and contact your IBM technical-support representative.
WsaaJar
While attempting to delete resources from the database, an analyzer was referenced but could not be found. A possible reason for this error is that the specified analyzer is not defined properly in the /assetloc/config/Analyzers.cfg configuration file.
Deletion of the assets associated with the specified analyzer stops. Deletion continues for the next set of assets associated with a valid analyzer.
Ensure that you have correctly defined the specified analyzer in the configuration file. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
Application names must be unique.
The user is prompted again for an application name.
Type in a unique application name and submit again
WsaaJar
The field full name is not allowed to be empty.
The user is prompted for the full name of the application
Type the full application name into the field and submit again.
WsaaJar
The assets selected have been queued.
The assets selected have been queued. Distributed assets were ignored.
None
WsaaJar
Only text MVS assets can be queued for analysis.
The text MVS assets have been queued for postprocessing analysis. Any distributed assets or binary assets have been ignored.
None
WsaaJar
An attempt was made to get information for the specified component, but metadata was not found in the WebSphere Studio Asset Analyzer database.
Processing stops and some or all of information cannot be displayed.
The database is in an inconsistent state. Contact your IBM technical-support representative.
WsaaJar
An attempt was made to get information for the specified component, but metadata was not found in the WebSphere Studio Asset Analyzer database.
Processing stops and some or all of information cannot be displayed.
The database is in an inconsistent state. Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve the identifier assigned to the specified asset in DB2. The process expects an identifier to have been assigned. This may reflect an inconsistency between the installed WebSphere Studio Asset Analyzer application and the WebSphere Studio Asset Analyzer database.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Consult the WebSphere Studio Asset Analyzer error logs for potential problems with DB2 communications or access. Fix any problems and attempt the scanning process again. Consult your IBM technical-support representative if the issue cannot be resolved.
WsaaJar
This is an unexpected error during WebSphere Studio Asset Analyzer processing that could indicate an inconsistency in the installed product. The error occurs while trying to load configuration files packaged with WebSphere Studio Asset Analyzer in the specified module.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that you do not have any obsolete product code on your system. Contact your IBM technical-support representative if you cannot correct the problem.
WsaaJar
An exception occurred while attempting to analyze elements in the specified module. The cause of this exception can be found in the WebSphere Studio Asset Analyzer error logs.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Consult the WebSphere Studio Asset Analyzer error logs to determine the cause of the problem and potential solutions. Contact your IBM technical-support representative if the error persists.
WsaaJar
The resource type specified is not a valid type handled by the WebSphere Studio Asset Analyzer scanner. The error was encountered while attempting to analyze resources in the specified module. Consult the WebSphere Studio Asset Analyzer online help for a complete list of resources supported by the distributed scanner.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Attempt the scanning operation again after removing the invalid resources from the scanning roots specified for the scanner.
WsaaJar
An unexpected I/O error has occurred while attempting to read the specified resource in the module indicated. Likely causes are an invalid or empty resource or a resource with incorrect permissions for read access.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that the specified resource is valid, non-empty, and has the correct permissions for read access. After making corrections, attempt the scanning operation again.
WsaaJar
An unexpected error occurred while attempting to scan or analyze the specified resource in the module indicated. The exact cause of the error is indicated.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Determine whether the cause of the analysis error can be corrected on site. Contact your IBM technical-support representative if the problem cannot be resolved locally.
WsaaJar
This is an unexpected error that could indicate an inconsistency in the installed product. The error occurs while trying to load configuration files packaged with WebSphere Studio Asset Analyzer in the specified module.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that you do not have any obsolete product code on your system. Contact your IBM technical-support representative if you cannot correct the problem.
WsaaJar
An unexpected error occurred while trying to analyze the specified element of a resource in the module indicated.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to read the specified configuration file but either it could not be found or it could not be opened for read access.
Processing stops and the error is displayed.
Ensure that the specified file exists and WebSphere Studio Asset Analyzer has the sufficient rights to access the file.
WsaaMain
An attempt was made to initiate an action that is not recognized by WebSphere Studio Asset Analyzer.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaJar
An invalid resource was encountered. The resource must be a file or a directory.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Verify that the resource specified is a valid type and attempt the scanning operation again.
WsaaMain
An error occurred during the submission or processing of JCL. The return code is specified.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaMain
An attempt was made to submit a JCL job on the Windows platform. Windows does not use JCL to start processes.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaMain
An attempt was made to perform processing that involves an ALLOC of a PDS or PDSE, but the ALLOC command failed. The return code is specified. This could be caused by the container name being blank. For more information, the DYNALLOC return codes are described in the z/OS MVS Programming: Authorized Assembler Services Guide, SA22-7608.
Processing stops and the error is displayed.
Resolve the error and try your operation again. Refer to the z/OS MVS user documentation for more help in resolving the issue.
WsaaMain
An attempt was made to perform processing that involves a data set specified, but that data set name is invalid. Either the data set does not exist, or the name is invalid.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaMain
If the high-order 4 digits are 1708, then DYNALLOC couldn't find the data set in the catalog. For more information, the DYNALLOC return codes are described in the z/OS MVS Programming: Authorized Assembler Services Guide, SA22-7608.
Processing stops and the error is displayed.
Resolve the error and try your operation again. Refer to the z/OS MVS user documentation for more help in resolving the issue.
WsaaMain
The data set is not a partitioned data set because the data set does not have directory information.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaMain
An attempt was made to inventory assets from a ChangeMan system, but ChangeMan as a valid asset management system is not enabled.
Processing stops and the error is displayed. ChangeMan features are disabled.
If you intend to use ChangeMan as a source for inventory collection, you must configure that product on your MVS system via the &hlq.SDMHREXX(DMHINSTL) Option 4 dialogs and try your operation again.
WsaaMain
If the high-order 4 digits are 1708, then DYNALLOC couldn't find the data set in the catalog. For more information, the DYNALLOC return codes are described in the z/OS MVS Programming: Authorized Assembler Services Guide, SA22-7608.
Processing stops and the error is displayed.
Resolve the error and try your operation again. Refer to the z/OS MVS user documentation for more help in resolving the issue.
WsaaMain
An attempt was made to perform processing that requires information from the specified configuration file but that file is empty.
Processing stops and the error is displayed.
Ensure that the file exists and has content and try your operation again.
WsaaJar
A common field was not defined for the specified analyzer. User-defined columns are not supported for the tables defined by WebSphere Studio Asset Analyzer.
The initialization of the distributed servlet cannot continue. This problem will cause errors starting your HTTP server if you are running WAS on MVS. If you are running WAS on Windows, the WAS server will likely start but the WebSphere Studio Asset Analyzer distributed servlet will not be properly initialized. You must resolve the initialization issue before you can use the distributed scanner function.
Ensure that the table identified for the specified analyzer is consistent with respect to the WebSphere Studio Asset Analyzer schema installed. Consult your IBM technical-support representative for further assistance.
WsaaJar
The table defined as being associated with the specified analyzer in /assetloc/config/Analyzers.cfg does not exist in the WebSphere Studio Asset Analyzer database.
The initialization of the distributed servlet cannot continue. This problem will cause errors starting your HTTP server if you are running WAS on MVS. If you are running WAS on Windows, the WAS server will likely start but the WebSphere Studio Asset Analyzer distributed servlet will not be properly initialized. You must resolve the initialization issue before you can use the distributed scanner function.
Ensure that you have correctly defined your analyzer in the configuration file and verify that the table indicated exists in the WebSphere Studio Asset Analyzer schema. Attempt the scanning operation again after fixing the inconsistency.
WsaaJar
The class defined as being associated with the specified analyzer in /assetloc/config/Analyzers.cfg does not exist in the WebSphere Studio Asset Analyzer application.
The initialization of the distributed servlet cannot continue. This problem will cause errors starting your HTTP server if you are running WAS on MVS. If you are running WAS on Windows, the WAS server will likely start but the WebSphere Studio Asset Analyzer distributed servlet will not be properly initialized. You must resolve the initialization issue before you can use the distributed scanner function.
Ensure that you have correctly defined your analyzer in the configuration file and verify that the implementing class indicated exists in WebSphere Studio Asset Analyzer. Attempt the scanning operation again after fixing the inconsistency.
WsaaJar
There is no tableName defined for the specified analyzer in the /assetloc/config/Analyzers.cfg file. Each analyzer must have all properties defined.
The initialization of the distributed servlet cannot continue. This problem will cause errors starting your HTTP server if you are running WAS on MVS. If you are running WAS on Windows, the WAS server will likely start but the WebSphere Studio Asset Analyzer distributed servlet will not be properly initialized. You must resolve the initialization issue before you can use the distributed scanner function.
Ensure that you have correctly defined the specified analyzer in the configuration file and attempt the scanning operation again.
WsaaMain
An attempt was made to access the specified member, but either the member or the containing PDS could not be found or accessed. This could be due to RACF or another type of security.
Ensure that the data set exists and WebSphere Studio Asset Analyzer has access to it.
Processing stops and the error is displayed.
WsaaMain
An attempt was made to access the specified data set, but either the data set could not be found or it could not be access. DYNALLOC couldn't find the data set in the catalog: the high-order 4 digits are 1708. For more information, the DYNALLOC return codes are described in the z/OS MVS Programming: Authorized Assembler Services Guide, SA22-7608.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaMain
An attempt was made to access the specified sequential data set but that data set could not be found or could not be accessed.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaMain
An attempt was made to access the specified file, but it cannot be found.
Processing stops and the error is displayed.
Ensure that the file exists and can be read by WebSphere Studio Asset Analyzer.
WsaaMain
An attempt was made to perform an action requiring the specified exit, but that exit does not exist so file contents cannot be extracted to the temp data set.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to access information via the Web browser using the specified URL, but that URL is invalid. This could also be caused by bad authorization.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred during an attempt to write the URL mapping for the specified resource to the DB2 metadata database. The WebSphere Studio Asset Analyzer logs should have more specific information about the error.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Consult the WebSphere Studio Asset Analyzer error logs for any information related to DB2 communications or access. Attempt the scanning operation again after fixing any problems or contact your IBM technical-support representative for issues that cannot be resolved.
WsaaJar
An attempt was made to access the specified host via the Web browser, but that host cannot be found or resolved.
Processing stops and the error is displayed.
Verify hostname is correct and the resolving service is functioning properly.
WsaaJar
An attempt was made to access a Web page but the server specified denied the request.
Processing stops and the error is displayed.
Verify that the WebSphere Studio Asset Analyzer server has authorization.
WsaaJar
An attempt was made to send XML as part of a Web browser request but the server failed to send XML over the connection.
Processing stops and the error is displayed.
Contact your IBM technical-support representative.
WsaaJar
The search Go button was pressed but no search criteria was entered.
No search is performed. The user is prompted for a search constraint.
Type a search constraint into the search field and press the Go button.
WsaaJar
Impact analysis has finished.
The system is functioning normally.
None
WsaaJar
Impact analysis is in progress...
The system is functioning normally.
None
WsaaJar
The assets chosen for the impact analysis have been updated.
The system is functioning normally.
None
WsaaJar
Asset will be added to the impact analysis.
The system is functioning normally.
None
WsaaJar
Asset will be removed from the impact analysis.
The system is functioning normally.
None
WsaaJar
Impact analysis requires at least one asset to analyze.
Processing stops. The user is prompted again for the asset to be analyzed
Add an asset to the impact analysis and try your operation again.
WsaaJar
An internal error has occurred
The scanner skips the current asset and continues processing.
Contact your IBM technical-support representative.
WsaaJar
An internal error has occurred
The scanner skips the current asset and continues processing.
Contact your IBM technical-support representative.
WsaaJar
The scanning root is not valid
The scanner skips the current scanning root and continues processing.
Fix the problematic scanning root and try again
WsaaJar
An internal error has occurred
The scanner skips the current asset and continues processing.
Contact your IBM technical-support representative.
WsaaJar
An internal error has occurred
The scanner skips the current asset and continues processing.
Contact your IBM technical-support representative.
WsaaConfigMgr
The attribute attribute is unsupported by the asset type
The attribute can not be retrieved
Contact your IBM technical-support representative.
WsaaJar
A soft link resource was encountered
The resource will be skipped and the scanning will continue to the next resource
Fix the scanning roots that have soft links in them, this includes the XML files of the WAS scanning roots
WsaaJar
An asset of type type and id id was requested but does not exists in database
Stop processing this asset
Contact your IBM technical-support representative.
WsaaJar
The application requested a parameter of type attrRequest but the attribute contains type of attrType
The exception is thrown and logged
Contact your IBM technical-support representative.
WsaaJar
An exception has occurred during scanning because an asset was encountered with the .ear file extension but it does not represent a valid EAR file supported by WebSphere Studio Asset Analyzer. Either the EAR file contents do not represent an EAR file or the EAR is an unsupported version.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Verify that the asset specified is a valid EAR file and a version supported by WebSphere Studio Asset Analyzer, and attempt the scanning operation again.
WsaaJar
An exception has occurred during the analysis of an EAR file archive because the contents do not coincide with the context in which the scanner has been initiated. This exception might occur because the EAR file refers to J2EE assets outside the boundaries set by the scanner process.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that the specifications for the scanner, for example, the scanning root itself, contain all nested archives that are likely to be encountered and attempt the scanning operation again. Contact your IBM technical-support representative for further assistance.
WsaaJar
An exception has occurred during the analysis of the EAR file indicated because multiple modules are defined with the same context root specified. This is an invalid EAR file.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that the EAR file specified is a valid archive and attempt the scanning operation again.
WsaaJar
The application tried to set duplicate fieldName in DataObject metadata: fieldValue
The exception is thrown and logged
Contact your IBM technical-support representative.
WsaaJar
The requested index index is out of bound for the key of size size
An exception is thrown and processing is stopped for this asset
Contact your IBM technical-support representative.
WsaaJar
The value is not of the type it is expected to be.
An exception is thrown and processing is stopped for this asset.
Contact your IBM technical-support representative.
WsaaJar
There is no metadata support for type type.
This request is discarded.
Contact your IBM technical-support representative.
WsaaJar
An compatible value of type valueType was tried to assign to Attribute of type attributeType.
The asset will be ignored.
Contact your IBM technical-support representative.
WsaaJar
Impact Analysis asset for asset of type type does not exists.
This asset will be ignored.
Contact your IBM technical-support representative.
WsaaJar
Class className can not be found or instantiated.
The asset is been ignored and the error is logged.
Contact your IBM technical-support representative.
WsaaJar
The full path name of the asset can not be retrieved. The ID of the asset is id and its name is name.
The path name will not be retrieved.
Contact your IBM technical-support representative.
WsaaJar
The data source name must be specified correctly in WebSphere Application Server's configuration.
The exception stack trace is displayed to the user.
Ensure that WebSphere Application Server is set up correctly.
WsaaJar
The rules manager for the analyzer is set to null.
The rule set will not be reset for the analyzer. The analyzer for the JSP will not be initialized.
Contact your IBM technical-support representative.
WsaaJar
The pattern name patternName is not listed in the patterns list.
This pattern will be ignored.
Contact your IBM technical-support representative.
WsaaJar
A ContextRegionContainer object contains a ContextRegionContainer object, which is not legal.
Analyzing is stopped for the JSP. The error is logged, and processing continues for the next file.
Verify that the JSP is well formed. Contact your IBM technical-support representative.
WsaaJar
An exception has occurred during scanning because an asset was encountered with the .rar file extension but it does not represent a valid RAR file supported by WebSphere Studio Asset Analyzer. Either the RAR file contents do not represent an RAR file or the RAR is an unsupported version.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Verify that the asset specified is a valid RAR file and a version supported by WebSphere Studio Asset Analyzer, and attempt the scanning operation again.
WsaaJar
The relationship has at least one null value.
Analysis for the EJB specified stops, and the error is logged. Analysis continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
For a string to be compared, it must be defined (not null). This is likely due to a corrupt asset.
Processing of the current SGML-based tag stops. Processing continues on the next tag.
Make sure that the SGML-based asset is valid. If the asset is valid, please contact your IBM technical-support representative.
WsaaJar
An unsupported link type was requested.
The error will be logged and continue to process next asset.
Contact your IBM technical-support representative.
WsaaJar
The process state can not be retrieved from the database or updated in the database.
The state will not be updated or retrieved.
Verify there is a database connection and the database is up and running. Contact your IBM technical-support representative.
WsaaJar
No assets were found for the impact analysis project.
The system is functioning normally.
If assets were supposed to be analyzed, try correcting the specification of the impact analysis. Otherwise, no action is required.
WsaaJar
Inserting a impact analysis project into the database failed.
The database is rolled back; the project is not saved.
Examine the SQL and attempt to fix any problems. Try adding the project again or contact your IBM technical-support representative for assistance.
WsaaJar
The SQLCODE is detailed in the DB2 manual. The SQLSTATE is detailed in the XOPEN SQL spec.
The database is rolled back; the project is not saved.
Examine the SQL error and attempt to fix any problems. Try the save again or contact your IBM technical-support representative for assistance.
WsaaJar
The original cause of the failed impact analysis project save is logged.
The database is rolled back; the project is not saved.
Examine the error and attempt to fix any problems. Try the save again or contact your IBM technical-support representative for assistance.
WsaaJar
The original cause of the failed impact analysis project update is logged.
The database is rolled back; the project is not updated.
Examine the error and attempt to fix any problems. Try the save again or contact your IBM technical-support representative for assistance.
WsaaJar
An error occurred during the analysis of the impacted assets.
Processing for the current seed stops.
Check logs for detailed messages. If further help is needed, contact your IBM technical-support representative.
WsaaJar
The user requested the analysis to be stopped.
Processing for the current seed stops.
None
WsaaJar
The maximum number of levels of analysis were reached before the asset was fully analyzed.
Processing for the current seed stops. The impact analysis project is saved.
None
WsaaJar
An unexpected error has been encountered because a method that should not be invoked for the specified asset was invoked. This could reflect an inconsistency in the installed WebSphere Studio Asset Analyzer product, or an environment or classpath problem.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have installed WebSphere Studio Asset Analyzer correctly according to instructions in the Configuration and Migration Guide. Consult your IBM technical-support representative if the problem cannot be resolved.
WsaaJar
The asset type is not valid as a starting point for impact analysis.
Processing for the current impact analysis stops.
Specify a valid starting point for impact analysis and start the analysis again.
WsaaJar
Saving the impact analysis project failed.
The database is rolled back to the previous state.
Check logs for detailed messages. If further help is needed, contact your IBM technical-support representative.
WsaaJar
An error occurred during the analysis of the impacted assets.
Processing for the current seed stops.
Check logs for detailed messages. If further help is needed, contact your IBM technical-support representative.
WsaaJar
The project save failed.
The database transaction will be rolled back.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The project save failed.
The database transaction will be rolled back.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred while trying to delete the project.
The project will remain in the database.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred while trying to delete the project.
The project will remain in the database.
Contact your IBM technical-support representative.
WsaaJar
The project save failed.
The database transaction will be rolled back.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The project save failed.
The database transaction will be rolled back.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The activity log could not be removed.
The database transaction will be rolled back. The activity log will remain in the database.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The activity log could not be removed.
The database transaction will be rolled back. The activity log will remain in the database.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The database transaction will be rolled back. The impacts will remain in the database.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The database transaction will be rolled back. The impacts will remain in the database.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The database transaction will be rolled back. The impact seeds will remain in the database.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The database transaction will be rolled back. The impact seeds will remain in the database.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The current processing will stop.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The current processing will stop.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The database transaction will be rolled back. The timestamp will remain unchanged.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The database transaction will be rolled back.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
An exception occurred during this database transaction.
The database transaction will be rolled back.
Verify the database connection and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The asset could not be found.
The asset is not added to a project.
Contact your IBM technical-support representative.
WsaaJar
A request to create a run unit for program program name has been added to the analysis queue.
The request is added to the analysis queue.
Since the request has only been added to the analysis queue, you must also run the postprocessing if you want to actually build the run unit now.
WsaaJar
User initiated the distributed postprocessor on the runtime.
Distributed postprocessor started in a separate thread.
None
WsaaJar
User initiated the distributed postprocessor on the runtime, but the distributed postprocessor was already running.
Ignore request.
Retry at a later time.
WsaaJar
User successfully initiated the [action] action.
Action performed.
None
WsaaJar
An invalid GET parameter was passed to the servlet.
URL processing aborted.
Fix the URL.
WsaaJar
User queried for the distributed postprocessor status.
None
None
WsaaJar
The impact asset could not be found.
The impact asset is not added to an analysis.
Contact your IBM technical-support representative.
WsaaJar
The asset's value does not exist.
The impact asset is not added to the Impact Analysis.
Contact your IBM technical-support representative.
WsaaJar
The asset is not a scanned-in asset.
Current processing stops. The impact asset is not created.
Contact your IBM technical-support representative.
WsaaJar
The asset's name could not be retrieved.
Current processing stops. The data object cannot be accessed.
Contact your IBM technical-support representative.
WsaaJar
The asset cannot be accessed.
The data object will not be accessed.
Verify sufficient authority and try again.
WsaaJar
The asset is not a scanned-in asset.
Current processing stops.
Contact your IBM technical-support representative.
WsaaJar
The impact asset could not be found or the asset factory could not be found.
Current analysis stops.
Contact your IBM technical-support representative.
WsaaJar
The impact analysis project has completed.
The system is functioning normally.
Check logs for any errors.
WsaaJar
There was a stopping error while performing the impact analysis.
The impact analysis is not complete.
Check logs for errors and fix as necessary. If further assistance is needed, contact your IBM technical-support representative.
WsaaJar
There was a stopping error while performing the asset analysis.
The asset analysis is not complete
Check logs for errors and fix as necessary. If further assistance is needed, contact your IBM technical-support representative.
WsaaJar
There is a problem communicating with the database.
The database transaction will be rolled back.
Verify the database configuration and connection.
WsaaJar
An exception has occurred during scanning because an asset was encountered with the .war file extension, but it does not represent a valid WAR file supported by WebSphere Studio Asset Analyzer. Either the WAR file contents do not represent a WAR file or the WAR is an unsupported version.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Verify that the asset specified is a valid WAR file and a version supported by WebSphere Studio Asset Analyzer and attempt the scanning operation again.
WsaaJar
An exception has occurred during scanning of a WAR file resource because the defined context has already been defined in this WAR file. This problem may be caused by an invalid or unexpected WAR file definition.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that the specified resource is a valid WAR file and attempt the scanning process again after correcting any errors.
WsaaJar
There is a problem communicating with the database.
The database transaction will be rolled back.
Verify the database configuration and connection.
WsaaJar
The currently set impact analysis factory is not valid.
Current analysis stops.
Contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard encountered an error while initializing the page.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
During scanning and analysis of a servlet, an attempt was made to obtain the URL space value, but none was found. The servlet definition may be invalid.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Consult the WebSphere Studio Asset Analyzer logs to determine the context of the error and verify the correct content of all servlets within that context. Attempt the scanning operation again after correcting any errors.
WsaaJar
An unexpected error has occurred while attempting to write metadata about the servlet being analyzed to the DB2 table specified. Check the WebSphere Studio Asset Analyzer error logs for information related to DB2 communications problems.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Verify that the specified DB2 table exists. If it does not, you must ensure that you properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide, including the step for creating the database. If the table does exist, examine the WebSphere Studio Asset Analyzer error logs for information related to DB2 access problems. Attempt the scanning operation again after correcting any errors.
WsaaJar
The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly. The project is not finalized.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
There was a problem while rendering the page. The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
There was a problem while initializing the page. The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
There was a problem while processing the page. The Impact Analysis wizard may not be set up correctly.
The Impact Analysis wizard may display incorrectly. The impact analysis might not be initialized.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard encountered an error while processing the page.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard encountered an error while rendering the page.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
There was a problem accessing the details of an asset. This could be caused by a corrupt asset or a database inconsistency.
The Impact Analysis wizard may display incorrectly.
Contact your IBM technical-support representative.
WsaaJar
The Impact Analysis wizard encountered an error while initializing the page.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
This is an unexpected error during WebSphere Studio Asset Analyzer processing that could indicate an inconsistency in the installed product.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that you do not have any obsolete product code on your system. Contact your IBM technical-support representative if you cannot correct the problem.
WsaaJar
This is an unexpected error during WebSphere Studio Asset Analyzer processing that could indicate an inconsistency in the installed product.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that you do not have any obsolete product code on your system. Contact your IBM technical-support representative if you cannot correct the problem.
WsaaJar
The Impact Analysis wizard encountered an error while rendering the page.
The Impact Analysis wizard may display incorrectly.
Start the wizard again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
Unsupported source container type: type, the supported types are EJB, EJB JAR and WAR.
This pattern will be ignored.
Contact your IBM technical-support representative.
WsaaJar
Illegal number of asset1 mapped to the asset2 in name : size There should be only 1:1 mapping.
The inference for the current pattern will be ignored.
Contact your IBM technical-support representative.
WsaaJar
The servlet did not receive the parameter AssetTypeIdProp.
Processing of the current request stops.
Contact your IBM technical-support representative.
WsaaJar
During initialization of the servlet, an exception occurred.
The servlet will not display.
Correct the problem and restart the WebSphere Studio Asset Analyzer Web application.
WsaaJar
The XML variable was not formatted correctly in the XML file.
Current request processing stops.
Contact your IBM technical-support representative.
WsaaJar
The field number is greater than the number of fields.
Current request processing stops.
Contact your IBM technical-support representative.
WsaaJar
During computation of EJB ref, the system had a problem.
Contact your IBM technical-support representative.
This reference computation will be ignored.
WsaaJar
An information message about the postprocessor activity after completion.
The system is functioning normally.
None
WsaaJar
An information message about the postprocessor starting
The system is functioning normally.
None
WsaaJar
There was an error in storing a record of data into the database.
Please refer to the log for more details, and contact your IBM technical-support representative.
The data did not get stored.
WsaaJar
An error occurred while trying to perform code extraction.
The code extraction action is canceled.
Have a WebSphere Studio Asset Analyzer administrator check the log for the code extraction error and make any needed configuration changes.
WsaaJar
The main logger initialization caused an exception.
Initialization failed. Processing will stop.
Verify the configuration is correct and try again. If the problem persists, contact your IBM technical-support representative.
WsaaJar
Initializing the database caused an exception.
Initialization failed. Processing will stop.
Verify the configuration is correct and verify the database is properly set up and configured. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The system is functioning normally.
This is an informational message written to the WebSphere Studio Asset Analyzer log indicating that a postprocessor is starting.
None
WsaaJar
The system was unable to retreive a table from the database. This error could be caused by the database going down.
Processing stops. The user will not be allowed to log in.
Check the database status and try the request again.
WsaaJar
The system was unable to store a resource into the database, the resource is probably too long, or located too deep inside the scanning root defined.
The resource will not get scanned into the system. Processing continues with the next resource.
Try to shorten the path name of the resource or the scanning root, or place the resource in the different location within the scanning root. If the problem persists, contact your IBM technical-support representative.
WsaaJar
The postprocessor might affect the results.
The system is functioning normally.
Wait for the operation to complete for accurate results.
WsaaJar
There is a problem storing a value in a prepared statement.
The store of this record will be skipped and the error is logged.
Contact your IBM technical-support representative.
WsaaJar
The postprocessor might affect the results.
The system is functioning normally.
Wait for the operation to complete for accurate results.
WsaaJar
The scanner might affect the results.
The system is functioning normally.
Wait for the operation to complete for accurate results.
WsaaJar
The node was not of type element or text. No other node types are supported.
This node is ignored. The error is logged.
Contact your IBM technical-support representative.
WsaaJar
An unexected SQL exception occurred. SQL: sql.
The current action is stopped.
Contact your IBM technical-support representative.
WsaaJar
The user-entered query returned an SQL exception: sql.
The current action is stopped.
Re-enter the query.
WsaaJar
The bookmark was created successfully.
The system is functioning normally.
None
WsaaJar
The custom query was created successfully.
The system is functioning normally.
None
WsaaJar
The bookmark create failed.
The action is stopped.
None
WsaaJar
The custom query create failed.
The action is stopped.
None
WsaaJar
An unexpected exception occurred while trying to instantiate the specified object type. Exception msg=[msg].
The action is stopped.
None
WsaaJar
The specified delete operation succeeded.
The system is functioning normally.
None
WsaaJar
The specified delete operation succeeded.
The system is functioning normally.
None
WsaaJar
An unexpected exception was encountered.
The action is stopped.
Contact your IBM technical-support representative.
WsaaJar
The only legal values in Assetlocator.cfg, bytecodeImpactAnalysisPrecision parameter are 'Coarse', 'Medium' and 'Fine'.
This Impact Analysis will be ignored.
Fix the paramter, then stop and start WAS.
WsaaJar
The site "name was successfully created and is now available for use.
The site is added to the database and available for use.
None
WsaaJar
The details of site "name were successfully updated.
The site definition is updated in the database and available for use.
None
WsaaJar
There were distributed count distributed and binary count files selected for this action. Since you can only change the language of MVS text files, these distibuted and binary assets will be ignored.
The distributed and binary assets are not included in the list of files to be updated.
None
WsaaJar
A site cannot be created without a name.
The site is not created.
Specify the site name and retry the operation.
WsaaJar
This is an unexpected error during WebSphere Studio Asset Analyzer processing that could indicate an inconsistency in the installed product.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that you do not have any obsolete product code on your system. Contact your IBM technical-support representative if you cannot correct the problem.
WsaaJar
The site name already exists in the database.
The site is not created.
Specify a unique site name and retry the operation.
WsaaJar
The results of searching for assets that match the search argument are too many to display.
The system is functioning normally.
Specify a more restrictive search argument.
WsaaJar
The range of statements to be analyzed has changed.
The system is functioning normally.
None
WsaaJar
The impact analysis has a non-numeric statement start or end value, or the statement start is beyond the statement end in the file.
Processing stops. The user is prompted again for a valid statement range.
Verify that the values entered for the impact analysis statement range start and end are positive numeric values and that the end value is greater than or equal to the start value. Try the operation again.
WsaaJar
Problems occurred as the assets selected for impact analysis were being displayed. This error may indicate that another user is modifying the impact analysis or that the server has been interrupted in the process of creating or updating the impact analysis. Specific information related to the problem may be found in the WebSphere Studio Asset Analyzer logs.
The impact analysis may be modified or remain unchanged.
Exit the impact analysis creation or modification process and try to access and update the impact analysis again. Refer to the WebSphere Studio Asset Analyzer logs for specific information on the asset selection problem encountered. Correct any errors and attempt the analysis process again. Contact your IBM technical-support representative if problems identified cannot be corrected locally.
WsaaJar
The scanning root was changed from its original access string. Only adding or removing scanning roots is allowed.
The scanning root will be ignored.
To change a scanning root, please change the scanning root name also. This will cause the system to remove the old scanning root and define a new one with the new access path string. If you do not want to remove the scanning root, then return the access string to its original value.
WsaaJar
The specified annotation type was found in the database, but not in wsaa-annotation-types.xml. No ill effects will occur from this problem.
Show warning message.
Add the missing annotation type to wsaa-annotation-types.xml.
WsaaJar
The directory may not exist or you may not be authorized to create a file in the directory.
The temporary file is not created, so the current action that involves getting an MVS file is not successful.
Have the system administrator check WSAA's settings using the DMHINSTL command. Ensure that the directory specified for temporary HFS files exists and that all WSAA users have the authority to create files there. Once corrected, retry this action.
WsaaJar
During analysis of the links among resources being scanned, the specified invalid link type was encountered. This is an unexpected error that could signal an inconsistency in the installed WebSphere Studio Asset Analyzer product.
Analysis for the asset stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that you do not have any obsolete product code on your system. Contact your IBM technical-support representative if you cannot correct the problem.
WsaaJar
The specified DB2 table name is invalid or is not defined in the WebSphere Studio Asset Analyzer database.
Analysis for the asset associated with the specified table stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that the WebSphere Studio Asset Analyzer database was created successfully. If the specified table name is not in the WebSphere Studio Asset Analyzer schema, ensure that you have specified the correct table name in /assetloc/config/Analyzers.cfg. Contact your IBM technical-support representative for more help.
WsaaJar
The specified field name for a DB2 column in the DB2 table indicated is not found in the WebSphere Studio Asset Analyzer database.
Analysis for the asset associated with the specified table and field stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that the WebSphere Studio Asset Analyzer database was created successfully. If the specified table name is not in the WebSphere Studio Asset Analyzer schema or the column indicated does not exist for that table, ensure that you have specified the correct table name in /assetloc/config/Analyzers.cfg. Contact your IBM technical-support representative for more help.
WsaaJar
An attempt was made to access or store data in the specified field name for a DB2 Column in the DB2 table indicated, but the data type is invalid for that column.
Analysis for the asset associated with the specified table and field stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that the WebSphere Studio Asset Analyzer database was created successfully. If the specified table name is not in the WebSphere Studio Asset Analyzer schema or the column indicated does not exist for that table, ensure that you have specified the correct table name in /assetloc/config/Analyzers.cfg . Contact your IBM technical-support representative for more help.
WsaaJar
This is an unexpected error during WebSphere Studio Asset Analyzer processing that could indicate an inconsistency in the installed product.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have properly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide and that you do not have any obsolete product code on your system. Contact your IBM technical-support representative if you cannot correct the problem.
WsaaJar
The DB2 exception specified has been encountered while attempting to add the JNDI mappings to the WebSphere Studio Asset Analyzer database. The WebSphere Studio Asset Analyzer logs may contain more information on the context of this exception.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that the WebSphere Studio Asset Analyzer application can correctly communicate with DB2 to write information to the database. Correct any issues and attempt the scanning operation again.
WsaaJar
This is an unexpected error related to an inconsistency in the defined WebSphere Studio Asset Analyzer schema or the code that attempts to access DB2 tables defined in that schema. The error may be related to the incorrect installation and configuration of WebSphere Studio Asset Analyzer during creation of the WebSphere Studio Asset Analyzer database.
Analysis for the asset specified stops, and the error is logged. Analysis continues for the next asset.
Ensure that you have correctly installed and configured WebSphere Studio Asset Analyzer according to the instructions in the Configuration and Migration Guide. Capture all logs related to the error and contact your IBM technical-support representative.
WsaaMain
This is an informational message alerting the user that an exception occurred during scanning of the specified resource, requiring all database changes to be rolled back.
The error is logged, and the next asset is scanned. The WebSphere Studio Asset Analyzer error logs contain information on the state of the scanner. The system is functioning normally.
Consult the WebSphere Studio Asset Analyzer logs for information on the errors encountered during scanning. Correct all problems and attempt the scanning operation again.
WsaaMain
This is an informational message alerting the user that an exception occurred during analysis of the specified resource, requiring all database changes to be rolled back.
The error is logged, and the next asset is scanned. The WebSphere Studio Asset Analyzer error logs contain information on the state of the scanner. The system is functioning normally.
Consult the WebSphere Studio Asset Analyzer logs for information on the errors encountered during analysis. Correct all problems and attempt the scanning operation again.
WsaaMain
This is an informational message written to the WebSphere Studio Asset Analyzer logs indicating that the scanning process has been invoked for a resource that already exists in the WebSphere Studio Asset Analyzer database. The information stored in the database related to that resource will be updated.
The system is functioning normally.
None
WsaaMain
This is an informational message written to the WebSphere Studio Asset Analyzer logs indicating that the scanning process has started for the specified resource.
The system is functioning normally.
None
WsaaMain
An attempt was made to scan the specified resource, but the resource cannot be found within the scanning root indicated in the /assetloc/config/Admin.cfg configuration file.
Scanning on the specified resource is stopped. Processing continues for the next scanner.
Ensure that the resource exists within the scope of the scanning root indicated in /assetloc/config/Admin.cfg and attempt the scanning operation again.
WsaaJar
An attempt was made to obtain resources directly from a ClearCase repository, but that function is not yet supported by WebSphere Studio Asset Analyzer. The error may indicate an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Scanning is stopped. Processing continues for the next scanner.
Ensure that you have correctly installed and configured the WebSphere Studio Asset Analyzer product according to instructions in the Configuration and Migration Guide. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An attempt was made to obtain resources directly from a CMVC repository, but that function is not yet supported by WebSphere Studio Asset Analyzer. The error may indicate an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Scanning is stopped. Processing continues for the next scanner.
Ensure that you have correctly installed and configured the WebSphere Studio Asset Analyzer product according to instructions in the Configuration and Migration Guide. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An exception occurred during scanning of resources in a CMVC repository while attempting to extract data from CMVC. Details about why the extract operation failed can be found in the WebSphere Studio Asset Analyzer error logs. It may be that the WebSphere Studio Asset Analyzer application cannot communicate with CMVC or that user logon information is incorrect.
Scanning is stopped for the specified resource. The error is logged, and processing continues for the next scanning root.
Consult the WebSphere Studio Asset Analyzer error logs for information on why the CMVC extract failed. Ensure you can communicate with CMVC using the user logon information specified for the machine on which the scanning operation is performed and attempt that operation again.
WsaaJar
A key allowing WebSphere Studio Asset Analyzer access to CMVC resources for scanning could not be created or accessed. The key specified is composed of a CMVC family, port number, and release, all of which must be valid for the system being accessed.
Scanning is stopped for the specified resource. The error is logged, and processing continues for the next scanning root.
Ensure that CMVC can be accessed for the family, port, and release specified and attempt the scanning operation again.
WsaaJar
This is an informational message indicating that an attempt was made to scan a CMVC repository for the scanning root specified, but either CMVC cannot be accessed or the scanning root does not exist in your CMVC system.
Scanning is stopped for the specified resource. The error is logged, and processing continues for the next scanning root.
Ensure you have correctly specified the CMVC scanning root in /assetloc/config/Admin.cfg and attempt the scanning operation again.
WsaaJar
An attempt was made to obtain resources directly from a CVSS repository, but that function is not yet supported by WebSphere Studio Asset Analyzer. The error may indicate an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Scanning is stopped. Processing continues for the next scanner.
Ensure that you have correctly installed and configured the WebSphere Studio Asset Analyzer product according to instructions in the Configuration and Migration Guide. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An exception occurred during scanning of resources in a CVSS repository while attempting to check out data. Details about why the checkout operation failed can be found in the WebSphere Studio Asset Analyzer error logs. It may be that the WebSphere Studio Asset Analyzer application cannot communicate with CVSS or that user logon information is incorrect.
Scanning is stopped for the specified resource. The error is logged, and processing continues for the next scanning root.
Consult the WebSphere Studio Asset Analyzer error logs for information on why the CVSS checkout failed. Ensure you can communicate with CVSS using the user logon information specified for the machine on which the scanning operation is performed and attempt the operation again.
WsaaJar
A key allowing WebSphere Studio Asset Analyzer access to CVSS resources for scanning could not be created or accessed. The key specified is composed of the CVSS resource name, which must be a valid name in the CVSS repository.
Scanning is stopped for the specified resource. The error is logged, and processing continues for the next scanning root.
Ensure that CVSS can be accessed for the resource name specified and attempt the scanning operation again.
WsaaJar
An attempt was made to scan a file system but the specified file was not found in the scanning root.
Scanning is skipped for the asset indicated. Processing continues for the next asset.
Ensure that the specified file exists within the scanning root identified for file system scanning in /assetloc/config/Admin.cfg and attempt the operation again.
WsaaJar
An unexpected error occurred while attempting to retrieve metadata for an asset from the table specified using the identifier specified because multiple instances exist for this same identifier. WebSphere Studio Asset Analyzer expects a single instance to be returned. This error may indicate an inconsistency in the metadata stored for WebSphere Studio Asset Analyzer.
Scanning is skipped for the asset associated with the table and ID indicated. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred while attempting to retrieve metadata for an asset specified by path, file, and scanner identifier in the WebSphere Studio Asset Analyzer database because multiple instances exist matching these criteria. WebSphere Studio Asset Analyzer expects a single instance to be returned. This error may indicate an inconsistency in the metadata stored for WebSphere Studio Asset Analyzer.
Scanning is skipped for the asset associated with the specified search criteria. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred while attempting to retrieve metadata for an asset with the database identifier specified in the WebSphere Studio Asset Analyzer database because the asset has an associated parent, but no parent asset was specified during the retrieval process. This error may mean the parent asset could not be found in the database and may indicate an inconsistency in the metadata stored for WebSphere Studio Asset Analyzer.
Scanning is skipped for the asset associated with the specified search criteria. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred while attempting to retrieve metadata for an asset with the database identifier specified. The asset has an associated parent with an identifier that is different from the identifier used to retrieve the asset. This error may indicate an inconsistency in the metadata stored for WebSphere Studio Asset Analyzer.
Scanning is skipped for the asset associated with the specified search criteria. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single site instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one site was returned. WebSphere Studio Asset Analyzer expects only a single site with the same IP address, name, and platform identifier. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
The distributed servlet cannot be initialized, so processing is stopped. The errors are logged.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single container instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching asset was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning is skipped for the asset currently being processed. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single scanner instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching scanner was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning is skipped for the asset currently being processed by this scanner. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single scanner instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching scanner was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning is skipped for the asset currently being processed by this scanner. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single asset instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching asset was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning is skipped for the asset currently being processed. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single asset instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching asset was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning is skipped for the current scanner being used. The error is logged, and processing continues for the next scanner.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single asset instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching asset was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning is skipped for the current scanning root. The error is logged, and processing continues for the next scanning root.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single asset instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching asset was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning is skipped for the current scanning root. The error is logged, and processing continues for the next scanning root.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single asset instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one matching asset was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning of the asset or scanning root associated with this application is skipped. This error can cause the entire scanning root to be skipped or just a single asset, depending on the location of the exception in the code. The error is logged, and processing continues for the next asset or scanning root.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to retrieve a single platform instance from the WebSphere Studio Asset Analyzer database using the specified search criteria, but more than one platform was returned. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
The distributed servlet and scanner cannot be initialized, so processing is stopped. The errors are logged.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error has occurred during scanning of file assets because some assets are found in the WebSphere Studio Asset Analyzer database without containing parent assets. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database.
Scanning of these assets is skipped. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
This message indicates an internal error that may be caused by incompatible combination of classes or an internal problem. The error may indicate an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Scanning of the asset is skipped. Processing continues for the next asset. This error message may recur for all assets associated with the scanner.
Ensure that you have correctly installed and configured the WebSphere Studio Asset Analyzer product according to instructions in the Configuration and Migration Guide. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An exception occurred during scanning of resources in a PVCS repository while attempting to extract data from PVCS. Details about why the extract operation failed can be found in the WebSphere Studio Asset Analyzer error logs. It may be that the WebSphere Studio Asset Analyzer application cannot communicate with PVCS or that user logon information is incorrect.
Scanning is stopped for the specified scanning root. The error is logged, and processing continues for the next scanning root.
Consult the WebSphere Studio Asset Analyzer error logs for information on why the PVCS extract failed. Ensure you can communicate with PVCS using the user logon information specified for the machine on which the scanning operation is performed and attempt the operation again.
WsaaJar
An attempt was made to retrieve a key manager for the PVCS scanner from the WebSphere Studio Asset Analyzer database, but it was not found. This error may indicate an inconsistency in the WebSphere Studio Asset Analyzer database or an internal code error.
The error is logged, and processing continues for the next scanning root.
Ensure that PVCS can be accessed for the scanning root as specified in /assetloc/config/Admin.cfg and attempt the scanning operation again. Contact your IBM technical-support representative.
WsaaJar
This is an informational message indicating that the PVCS scanning root does not fit the required PVCS scanning root format or the scanning root does not exist in your PVCS system.
Scanning is stopped for the specified scanning root. The error is logged, and processing continues for the next scanning root or scanner.
Ensure you have correctly specified the PVCS scanning root in /assetloc/config/Admin.cfg and attempt the scanning operation again.
WsaaJar
An attempt was made to extract a release to the base directory, but failure was reported.
The error is logged, and processing continues for the next scanning root.
Ensure that PVCS can be accessed for the scanning root as specified in /assetloc/config/Admin.cfg and attempt the scanning operation again. Contact your IBM technical-support representative.
WsaaJar
An attempt was made to execute the XMLConfig command from the specified WAS, but an error occurred. An incorrect WAS directory may have been specified during installation or configuration of WebSphere Studio Asset Analyzer.
Scanning is skipped for the WAS4AE scanning root. The error is logged, and processing continues with the next scanning root.
Ensure that the XMLConfig command can be issued by verifying the correct WAS directory is being used or fixing any other problem identified in the WebSphere Studio Asset Analyzer or WAS error logs. Verify that the correct WAS directory is specified in /config/Common.cfg. Attempt the scanning operation again.
WsaaJar
An error occurred while attempting to access or parse the configuration file specified while scanning WAS for the scanning root specified in /assetloc/config/Admin.cfg. Either the WAS directory specified during installation or the scanning root specified are incorrect, or the configuration file is not located in the scanning root or has an invalid format.
Scanning for the WAS scanning root is skipped. The error is logged, and processing continues for the next scanning root.
Look in /config/Common.cfg to ensure that the correct WAS directory was specified during installation and configuration of WebSphere Studio Asset Analyzer. Verify that the correct scanning root is specified in /assetloc/config/Admin.cfg and that the specified configuration file can be found and has the correct format. Attempt the scanning operation again.
WsaaJar
This is an informational message indicating that an attempt was made to scan a WAS server for the scanning root specified, but scanning root does not have the correct format.
Scanning is stopped for the specified scanning root. The error is logged, and processing continues for the next scanning root or scanner.
Ensure you have correctly specified the scanning root in /assetloc/config/Admin.cfg and that the scanning root file has the correct format. Attempt the scanning operation again.
WsaaJar
An error has occurred while attempting to find the specified XMLConfig file. This error could indicate a problem with the WAS directory specified during installation and configuration of WebSphere Studio Asset Analyzer, or it may indicate that the file does not exist in the specified scanning root.
Scanning is skipped for the specified scanning root. The error is logged, and processing continues for the next scanning root or scanner.
Ensure that you have correctly specified the location of WAS on your WebSphere Studio Asset Analyzer server and that the XMLConfig file exists in the location specified. Examine the settings in /config/Common.cfg to determine what you have specified for WAS. Examine the specified scanning root file to ensure the correct location of the XMLConfig file.
WsaaJar
This message indicates an internal error caused by an incompatible combination of classes or an internal code error. The error may indicate an inconsistency in the WebSphere Studio Asset Analyzer installed code or the environment classpath.
Scanning of the asset is stopped. Processing continues for the next asset. This error is likely to recur for all assets associated with this scanner.
Ensure that you have correctly installed and configured the WebSphere Studio Asset Analyzer product according to instructions in the Configuration and Migration Guide. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
This is an informational message indicating that an attempt was made to set a URL context that already exists.
The message is logged, and analysis continues normally.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred. The specified context could not be found or is not defined for the current analysis process.
Analysis is skipped for the current asset. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
This is an unexpected error indicating that a method that should not have been invoked has been called for the class specified. This error could indicate an inconsistency in your WebSphere Studio Asset Analyzer installation.
The scanning process is stopped.
Contact your IBM technical-support representative.
WsaaJar
This is an unexpected error indicating that an Integer value was expected, but the specified object type was used instead. This error could indicate an inconsistency in your WebSphere Studio Asset Analyzer installation.
The scanning process is stopped.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error has been encountered because a method that should not be invoked was called. This error could reflect an inconsistency in the installed WebSphere Studio Asset Analyzer product, or an environment or classpath problem.
The scanning process is stopped, and the error is logged.
Ensure that you have installed WebSphere Studio Asset Analyzer correctly according to instructions in the Configuration and Migration Guide. Consult your IBM technical-support representative if the problem cannot be resolved.
WsaaJar
Some messages might not be fully loaded into memory. When a message cannot be accessed, DMH5841E will be logged instead.
Reading the XML message file has been aborted.
Make sure that the XML message file (xmlfile) is accessible to WebSphere Studio Asset Analyzer.
WsaaJar
The message details for message number msgnum was not found in memory. This could be caused by a failed load of the message XML file.
The message number and message parameters will be logged, but no other details will be logged.
Make sure that the XML message file is accessible.
WsaaJar
A DB2 exception has occurred while attempting to create reference links in the metadata as a result of postprocessing.
Postprocessing is skipped for the current link, and the error is logged. Processing continues for the next defined link.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access that can be fixed locally and attempt the process again. Contact your IBM technical-support representative for further assistance.
WsaaJar
This is an informational message indicating that a pattern has been found during pattern detection postprocessing. This message is displayed only when the system is run in debug level 3 or above.
This message is logged. The system is functioning normally.
None
WsaaJar
An attempt was made to access the temporary directory specified by the tempDir parameter in /config/Common.cfg, but no value has been specified for that property.
Postprocessing cannot continue. The error is logged.
Ensure that you have specified a valid and accessible temporary directory value in /config/Common.cfg.
WsaaJar
An error occurred while attempting to extract assets from the file specified.
Postprocessing for the current processor is skipped, and the error is logged. Processing continues for the next postprocessor.
Verify that the specified command is available for execution in your environment and that the indicated file and directory exist with the appropriate permissions. Correct any problems and attempt the operation again.
WsaaJar
An unexpected error occurred because the same resource has been found to be the source for multiple target references in the metadata. WebSphere Studio Asset Analyzer expects this source to be referenced by only one target. This error may indicate an inconsistency in the metadata stored in the WebSphere Studio Asset Analyzer database. This message displays only when the system is run in debug level 3 or above.
Postprocessing for the specified resource is skipped. The error is logged, and processing continues for the next asset. The system continues to function normally.
None Contact your IBM technical-support representative for further assistance.
WsaaJar
An error occurred while attempting to retrieve the URL space for a WAR table asset. The source or target component is not found.
Postprocessing for the specified pattern is skipped. The error is logged, and processing continues for the next pattern.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access problems. Consult your IBM technical-support representative if further assistance is required.
WsaaMain
An unexpected error occurred while attempting to retrieve metadata for the asset specified. This asset should already exist in the database as a result of the scanning and analysis process.
Postprocessing for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access problems. Consult your IBM technical-support representative if further assistance is required.
WsaaMain
An unexpected error occurred attempting to retrieve metadata for an asset from the field or column specified in the asset's associated DB2 table. This serious error indicates that the WebSphere Studio Asset Analyzer schema may not have been created correctly during installation and configuration of the product.
Postprocessing for the current asset is skipped, and processing continues for the next asset. The error is logged.
Verify whether your WebSphere Studio Asset Analyzer schema contains the specified column within the set of distributed tables. Ensure that the database was properly created during installation and configuration of the product. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred attempting to retrieve the identifier in DB2 for the asset stored in the database. This asset should already exist in the database as a result of the scanning and analysis process.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access problems. Consult your IBM technical-support representative if further assistance is required.
WsaaMain
An unexpected error occurred attempting to retrieve the identifier in DB2 for the asset stored in the database. This asset should already exist in the database as a result of the scanning and analysis process.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access problems. Consult your IBM technical-support representative if further assistance is required.
WsaaMain
An unexpected error occurred attempting to retrieve metadata for an asset from the field or column specified in the asset's associated DB2 table. The error occurred because no value was found in this metadata when a value was expected.
Postprocessing for the current asset is skipped, and processing continues for the next asset. The error is logged.
Examine your WebSphere Studio Asset Analyzer logs for an indication of a DB2 access or communications problem. Ensure that the database was properly created during installation and configuration of the product. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred attempting to retrieve the identifier in DB2 for the asset stored in the database. This asset should already exist in the database as a result of the scanning and analysis process.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access problems. Consult your IBM technical-support representative if further assistance is required.
WsaaJar
An unexpected error occurred while trying to find the implementing class for a servlet in DB2. WebSphere Studio Asset Analyzer expects the class to be found in the database.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access problems. Consult your IBM technical-support representative if further assistance is required.
WsaaJar
An unexpected error occurred while trying to find the implementing class for a component (servlet, EJB, or tag) in DB2. This error may indicate an inconsistency in the metadata stored in the WebSphere Studio Asset Analyzer database.
Pattern detection for the specified resource is skipped. The error is logged, and processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred while trying to retrieve the identifier for the specified asset from the WebSphere Studio Asset Analyzer database. WebSphere Studio Asset Analyzer expects the asset to be in the database.
Pattern detection for the specified asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred while trying to retrieve metadata for an asset during postprocessing. The cause of the exception is indicated.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred while trying to retrieve metadata for an asset during postprocessing. The asset was expected to be in the location indicated.
Postprocessing for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred while trying to retrieve metadata for an EAR file related to the specified asset during postprocessing. The cause of the exception is indicated.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred trying to retrieve metadata for the resource identifier in the specified table. WebSphere Studio Asset Analyzer expects the cell to exist in the metadata. This message likely indicates an error in the WAS topology link postprocessor.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred trying to resolve the JNDI name associated with the specified reference in the WebSphere Studio Asset Analyzer database.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred attempting to retrieve a metadata identifier from the specified DB2 table, but that table is not defined in the WebSphere Studio Asset Analyzer schema.
Pattern detection for the current asset is skipped. Processing continues for the next asset.
Ensure that you have correctly installed and configured WebSphere Studio Asset Analyzer according to instructions in the Configuration and Migration Guide and that the WebSphere Studio Asset Analyzer database was created successfully. If the specified table exists in the schema, contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected DB2 exception has occurred while attempting to retrieve metadata for EJB JAR file assets that have been previously scanned and analyzed.
Postprocessing for the current processor is skipped. The error is logged, and processing continues for the next postprocessor.
Examine the WebSphere Studio Asset Analyzer logs for errors related to DB2 access that can be corrected locally and attempt the operation again. Contact your IBM technical-support representative for further assistance.
WsaaJar
An error occurred while attempting to determine the set of analyzable runtime servers defined in the WebSphere Studio Asset Analyzer database. No servers have been defined, or they do not exist in the database.
Pattern detection is skipped for the current asset. Processing continues for the next asset, and the error is logged.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred while trying to instantiate an analyzable server based on the server analyzer class name specified. The name is retrieved from the WebSphere Studio Asset Analyzer database, so it should be valid. This error may indicate an inconsistency in the installed WebSphere Studio Asset Analyzer product, the environment, or the metadata.
Pattern detection is skipped for the current asset, and the error is logged. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2 or by an inappropriate classpath or other path environment setting. Ensure that you have correctly installed and configured WebSphere Studio Asset Analyzer according to instructions in the Configuration and Migration Guide. Contact your IBM technical-support representative for further assistance.
WsaaJar
An exception occurred while attempting to retrieve an analysis server name for the specified table. WebSphere Studio Asset Analyzer expects a name to be associated with this table.
Pattern detection is skipped for the current asset. Processing continues for the next asset, and the error is logged.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
The setting 'Database.url' in Common.cfg does not appear to be a valid database.
Servlet initialization is stopped.
Fix the specified configuration setting and restart the web application.
WsaaJar
The setting 'Database.username' and/or 'Database.password' in Common.cfg does not appear to be valid.
Servlet initialization is stopped.
Fix the specified configuration setting(s) and restart the web application.
WsaaJar
The setting 'Database.username' in Common.cfg does not refer to a database user with permissions necessary for WebSphere Studio Asset Analyzer.
Servlet initialization is stopped.
Refer to the documentation on the permissions required, fix the specified configuration setting, and restart the web application.
WsaaJar
An unknown error condition occurred while trying to create a connection to the database.
Servlet initialization is stopped.
Check the log file for more information. Restart the web application after the problem has been fixed.
WsaaJar
An unexpected error occurred attempting to retrieve node metadata for the specified resource when node data is expected.
Pattern detection is skipped for the current asset. Processing continues for the next asset, and the error is logged.
Examine the WebSphere Studio Asset Analyzer logs to determine if the problem was caused by an unexpected error accessing DB2. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred because a null or invalid logger was used to initialize the specified Bridge Manager. This error could indicate an inconsistency in the installed WebSphere Studio Asset Analyzer product.
Pattern detection is skipped for this set of assets. Processing continues for the postprocessor defined.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to access the temporary directory specified in tempDir parameter of the /config/Common.cfg file, but no value has been specified for that property.
The pattern detector cannot continue. The error is logged.
Ensure that you have specified a valid and accessible temporary directory value in /config/Common.cfg.
WsaaJar
An unexpected error occurred because a null or invalid scanning root was used to initialize the Bridge Manager. This error could indicate an inconsistency in the installed WebSphere Studio Asset Analyzer product.
Postprocessing is skipped for this set of assets. Processing continues for the postprocessor defined.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred because a null or invalid configuration object was used to initialize the specified Bridge Manager. This error could indicate that the runtime configuration in admin.cfg is not defined correctly or does not exist.
Pattern detection is skipped for this set of assets. Processing continues for the postprocessor defined.
Review your runtime declaration configuration in admin.cfg and the runtime configuration definition. Attempt to scan the assets again.
WsaaJar
An unexpected error occurred because the scanning root used to initialize the Bridge Manager did not have a location defined. This error could indicate an inconsistency in the installed WebSphere Studio Asset Analyzer product.
Pattern detection is skipped for this set of assets. Processing continues for the postprocessor defined.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred because the configuration object used to initialize the Server Bridge did not have a classpath defined. This error could indicate an incorrect runtime configuration definition.
Pattern detection is skipped for this set of assets. Processing continues for the postprocessor defined.
Correct the runtime configuration file, define the classpath for the runtime, and attempt to scan the assets again.
WsaaJar
An unexpected error occurred because the Server Bridge was initialized without a location for the scanning root. This error could indicate an inconsistency in the installed WebSphere Studio Asset Analyzer product.
Pattern detection is skipped for this set of assets. Processing continues for the postprocessor defined.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to set a null value for a column specified in the indicated table when a null value is not allowed.
The metadata resulting from postprocessing for the current asset cannot be completed and will be skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine if the error is related to the asset itself. Contact your IBM technical-support representative if the problem cannot be resolved.
WsaaJar
An unexpected error occurred while trying to retrieve metadata for a specific asset in the WebSphere Studio Asset Analyzer database. Multiple results were returned when only one result was expected.
Scanning or analysis for the current asset is skipped. Processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred because the specified column does not exist in the table indicated in the WebSphere Studio Asset Analyzer schema. This error could indicate an inconsistency in the installed WebSphere Studio Asset Analyzer product.
Scanning or analysis for the current asset is skipped. Processing continues for the next asset.
Ensure that you have correctly installed and configured the WebSphere Studio Asset Analyzer product according to instructions in the Configuration and Migration Guide. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred during an attempt to retrieve metadata from the WebSphere Studio Asset Analyzer database because no column name was specified.
Scanning or analysis for the current asset is skipped. Processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred while attempting to communicate with the DB2 database for WebSphere Studio Asset Analyzer because the connection was not opened.
Scanning or analysis for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access that can be fixed locally and attempt the process again. If the database is on a remote system, verify that there is a network connection to that system and that the database is accessible. Contact your IBM technical-support representative for further assistance.
WsaaJar
An error occurred during an attempt to start a DB2 transaction because one or more DB2 transactions are still active.
Scanning or analysis for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access that can be fixed locally and attempt the process again. Contact your IBM technical-support representative for further assistance.
WsaaJar
An error occurred during an attempt to set or retrieve values from the WebSphere Studio Asset Analyzer database. The specific SQL exception is indicated.
Scanning or analysis for the current asset is skipped. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs for any errors related to DB2 access that can be fixed locally and attempt the process again. Contact your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error occurred because the specified column does not exist in the table indicated in the WebSphere Studio Asset Analyzer schema. This error could indicate an inconsistency in the installed WebSphere Studio Asset Analyzer product.
Scanning or analysis for the current asset is skipped. Processing continues for the next asset.
Ensure that you have correctly installed and configured the WebSphere Studio Asset Analyzer product according to instructions in the Configuration and Migration Guide. If the error cannot be corrected, capture all logs related to the error and contact your IBM technical-support representative.
WsaaJar
An exception occurred because the specified invalid filter was used to query metadata in the WebSphere Studio Asset Analyzer database.
Scanning or analysis on the current asset is skipped. Processing continues for the next asset.
Examine the filter specified and the WebSphere Studio Asset Analyzer logs to determine why the filter is invalid. Contact your IBM technical-support representative if the problem is unrelated to DB2 access problems.
WsaaJar
An exception occurred during an attempt to store the specified value in the column indicated because the value exceeds the allowable size of the column.
The string is truncated and inserted into the database.
None
WsaaJar
The /assetloc/config/EColabraApplication.cfg configuration file cannot be found or opened for read access.
Scanning or analysis cannot continue because the persistency framework cannot be initialized. The scanning process ends.
Ensure that the EColabraApplication.cfg file exists with the correct file permissions for read access.
WsaaJar
The persistency help specified cannot be instantiated using the indicated class defined for that persistency helper in the /assetloc/config/EColabraApplication.cfg configuration file.
Scanning or analysis cannot continue because the persistency framework cannot be initialized. The scanning process ends.
Ensure that you have correctly defined the persistency helper in the EColabraApplication.cfg file.
WsaaJar
An unexpected error occurred during an attempt to store metadata in the WebSphere Studio Asset Analyzer database.
Analysis for the existing asset is skipped. Processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred during postprocessing because multiple links were found between a tag and a tag library. This is an invalid state of the metadata that may indicate an inconsistency.
Postprocessing is skipped for the current asset. Processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred while attempting to create a reference link in the WebSphere Studio Asset Analyzer database because one of the linked assets has an invalid identifier.
Postprocessing is skipped for the current asset. Processing continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
An invalid scope space for an asset was specified during postprocessing.
Postprocessing is skipped for the current asset. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine whether the asset scoping is invalid as specified by the scanning root for the scanning process. Contact your IBM technical-support representative for assistance.
WsaaJar
An exception occurred during postprocessing because multiple targets used for analysis were found in the WebSphere Studio Asset Analyzer metadata database. This error may indicate that the data being analyzed is invalid or that there is an unexpected inconsistency in the database.
Postprocessing on the current asset is stopped. The exception is logged, and postprocessing continues for the next asset.
Examine the log for information on the asset being analyzed. Consult your IBM technical-support representative if the problem cannot be corrected locally.
WsaaJar
The specified class found in the archive manifest being analyzed was not found among the set of assets already analyzed. WebSphere Studio Asset Analyzer expects that this class has been analyzed within the scope of the archive.
Postprocessing for the current asset is stopped. The error is logged, and processing continues for the next asset.
Examine the log for details about the asset being analyzed and the error itself. Ensure that the archive is correct and try the operation again.
WsaaJar
An exception occurred during postprocessing because an asset has no associated scope space as expected. This error may indicate that the data being analyzed is invalid or that there is an unexpected inconsistency in the database.
Postprocessing for the current asset is stopped. The error is logged, and processing continues for the next asset.
Examine the log for details about the asset being analyzed and the error itself. Consult your IBM technical-support representative if the problem cannot be corrected locally.
WsaaJar
An exception occurred during postprocessing for the specified EJB asset because more than one class was found to be associated with this EJB.
Postprocessing for the specified asset is stopped. The error is logged, and processing continues for the next asset.
Examine the logs for details about the error. Ensure that your EJB is valid and has only one class associated with it and thy the process again.
WsaaJar
An invalid scope space for the specified EJB asset was used during postprocessing.
Postprocessing is skipped for the current asset. Processing continues for the next asset.
Examine the WebSphere Studio Asset Analyzer logs to determine whether the asset scoping is invalid as specified by the scanning root for the scanning process. Contact your IBM technical-support representative for assistance.
WsaaJar
An exception occurred during postprocessing for the specified asset because a scope for analysis was defined but not found.
Postprocessing for the specified asset is stopped. The error is logged, and processing continues for the next asset.
Examine the logs for information regarding this specific problem. Ensure that the scope indicated is defined for the analysis process you are running and try the operation again.
WsaaJar
An exception occurred during postprocessing for the specified asset because a scope for analysis was defined but not found.
Postprocessing for the specified asset is stopped. The error is logged, and processing continues for the next asset.
Examine the logs for information regarding this specific problem. Ensure that the scope indicated is defined for the analysis process you are running and try the operation again.
WsaaJar
An exception occurred during postprocessing for the specified asset. The JSP specified as implementing this asset cannot be found in the set of metadata for WebSphere Studio Asset Analyzer. Either the JSP asset has not been analyzed or it has been analyzed under a different asset name.
Postprocessing for the specified asset is stopped. The error is logged, and processing continues for the next asset.
Ensure that the specified JSP is part of the set of assets being analyzed and try the operation again.
WsaaJar
This is an informational message signalling that the postprocessor has completed.
The system is functioning normally.
None
WsaaJar
This is an informational message indicating that the postprocessor is running.
The system is functioning normally.
None
WsaaJar
This is an informational message signalling that the postprocessor has started.
The system is functioning normally.
None
WsaaJar
This is an informational message indicating that the WAS 4 pattern detector is running.
The system is functioning normally.
None
WsaaJar
This message indicates that postprocessing will not continue because there are no WAS 4 servers accessible for analysis.
Postprocessing stops for this asset type. Processing continues for the next type of asset.
Ensure that the WAS 4 server you intend to analyze is accessible and can be reached by your WebSphere Studio Asset Analyzer Windows server and try the operation again. Make sure that the WebSphere Studio Asset Analyzer scanner is configured to scan the proper WAS assets and that there were no errors during the analysis phase of scanning.
WsaaJar
This is an informational message indicating that the WAS 5 pattern detector is running.
The system is functioning normally.
None
WsaaJar
This is an informational message indicating that the developed assets pattern detector is running.
The system is functioning normally.
None
WsaaJar
Postprocessing for developed assets has stopped because no assets were identified for processing.
Postprocessing stops for this set of assets. The error is logged, and processing continues for the next postprocessor.
Examine the log to determine which postprocessor did not have any assets identified. Ensure that assets exist within the scope being analyzed and try the operation again.
WsaaJar
Postprocessing for developed assets has stopped because no scanning roots were identified for processing.
Postprocessing stops for this set of assets. The error is logged, and processing continues for the next postprocessor.
Examine the log to determine which postprocessor did not have any scanning roots identified. Ensure that one or more valid scanning roots are specified in /assetloc/config/Admin.cfg and that they are properly bound to a development or assembled environment. Try the operation again.
WsaaJar
Postprocessing for developed assets has stopped because no patterns were specified for detection during postprocessing in the development environment bound to the scanning root processed.
Postprocessing stops for this set of assets. The error is logged, and processing continues for the next postprocessor.
Examine the log to determine which postprocessor did not have any patterns identified. Consult your IBM technical-support representative for help diagnosing and correcting the problem.
WsaaJar
This is an informational message indicating that the assembled assets pattern detector is running.
The system is functioning normally.
None
WsaaJar
Postprocessing for developed assets has stopped because no patterns were specified for detection during postprocessing in the assembled environment bound to the scanning root processed.
Postprocessing stops for this set of assets. The error is logged, and processing continues for the next postprocessor.
Examine the log to determine which postprocessor did not have any scanning roots identified. Ensure that one or more valid scanning roots are specified in /assetloc/config/Admin.cfg and try the operation again.
WsaaJar
Postprocessing for developed assets has stopped because no patterns were specified for detection in the assembled environment bound to the scanning root processed.
Postprocessing stops for this set of assets. The error is logged, and processing continues for the next postprocessor.
Examine the log to determine which postprocessor did not have any patterns identified. Consult your IBM technical-support representative for help diagnosing and correcting the problem.
WsaaJar
Postprocessing for developed assets has stopped because no resources could be found under the specified scanning root for pattern detection.
Postprocessing stops for this set of assets. The error is logged, and processing continues for the next postprocessor.
Examine the log to determine which postprocessor did not have any assets identified for the given scanning root. Ensure that the specified scanning root has assets to be analyzed and attempt the operation again.
WsaaJar
The specified invalid asset type was encountered while validating the scanning roots indicated for postprocessing in the WebSphere Studio Asset Analyzer configuration files.
Postprocessing on the particular asset type is stopped. The error is logged, and postprocessing continues for the next asset in the scanning root.
Examine the logs for the asset type(s) that are invalid and ensure that you have correctly specified this asset type for postprocessing in the Crawl_Root_Bindings section of the Admin.cfg configuration file. Attempt the operation again after fixing the configuration file or removing the invalid assets from the scanning root(s) being processed.
WsaaJar
During an attempt to add links to metadata during postprocessing, the specified DB2 table could not be found in the WebSphere Studio Asset Analyzer metadata schema. This error could be due to an invalid specification in the postprocessor configuration file, an inconsistency in the WebSphere Studio Asset Analyzer database, or an error in the user input specification defined by the user.
The updates to the metadata were not made. The error is logged, and postprocessing continues on the current asset.
Ensure that you have correctly created your WebSphere Studio Asset Analyzer database and that the table names specified in the postprocessor configuration files are accurate. Check the user input specification to verify that all data is correct and supported by the WebSphere Studio Asset Analyzer version installed. Attempt the operation again after correcting the problem.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the SQL= parameter was not specified on the URL.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify the SQL= parameter. Try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the SQL= parameter was specified but did not contain a valid value. The invalid value is indicated in the error message.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid SQL= parameter. Try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the ANALYZER= parameter was specified but contained either a null or invalid value for this parameter. The invalid value is indicated in the error message.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid ANALYZER= parameter. Try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, an SQL=SIGNAL or SQL=LIST was encountered in the URL but the associated FLAG or TYPE parameter specified a value as indicated that is invalid for this URL.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid TYPE= or FLAG= parameter. Try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the SQL=DESCRIBE was used but the OPTION= parameter specified is invalid.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid OPTION= parameter. Try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the PROCESSOR= parameter specified contains the value for a results processor that is not defined in the /assetloc/config/AssetLocator.cfg file.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid PROCESSOR= parameter and the value must be defined in the /assetloc/config/AssetLocator.cfg file. Either specify a valid value or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the QUERY= parameter specified contains the value for a query processor that is not defined in the /assetloc/config/AssetLocator.cfg file.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid QUERY= parameter and the value must be defined in the /assetloc/config/AssetLocator.cfg file. Either specify a valid value or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the QUERY= parameter specified contains the value for a query processor defined in the /assetloc/config/AssetLocator.cfg file, but the associated class could not be instantiated. This is likely due to an invalid specification of the query processor in the configuration file.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid QUERY= parameter and the value must be defined correctly in the /assetloc/config/AssetLocator.cfg file. Either specify a valid value or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to invalid URL parameters. In this particular case, the PROCESSOR= parameter specified contains the value for a results processor defined in the /assetloc/config/AssetLocator.cfg file, but the associated class could not be instantiated. This is likely due to an invalid specification of the results processor in the configuration file.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a valid RESULTS= parameter and the value must be defined correctly in the /assetloc/config/AssetLocator.cfg file. Either specify a valid value or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to a missing value for the parameter specified.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify a value for the specified parameter in the URL you are attempting to execute. Either specify a valid value or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
During execution of a query from the browser by a URL, an invalid column name was used, but that column is forbidden for use in the query.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must remove the invalid column from the URL and execute the query again, or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
During execution of a query from the browser by a URL, an invalid JOIN value was specified. Valid values are INNER and LEFT.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify JOIN=INNER or JOIN=LEFT and execute the query again, or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
During execution of a query from the browser by a URL, an invalid ELIMINATEDUPLICATES value was specified. Valid values are TRUE and FALSE.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, you must specify ELIMINATEDUPLICATES=TRUE or ELIMINATEDUPLICATES=FALSE and execute the query again, or try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet because an attempt was made to access a DB2 table in the WebSphere Studio Asset Analyzer metadata schema but the required table could not be accessed. The specifics of the error are specified. This is likely due either to an invalid specification in one of the WebSphere Studio Asset Analyzer configuration files for an analyzer or scanner, or to an invalid specification on the URL itself.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, check the specific error to determine whether the problem is with an invalid URL parameter value or an incorrect specification on one of the configuration files. You can also try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred while executing a distributed query requesting information about a scanner for which no scanner manager has been defined. The scanner is indicated in the exception. The likely cause is an invalid specification for this scanner in the /assetloc/config/Scanners.cfg file.
The distributed functionality cannot be invoked from the browser. The error is displayed.
If you have manually updated the URL in the browser, ensure that you have specified the correct value for CRAWLER= on the URL and that this scanner is completely and accurately defined in the /assetloc/config/Scanners.cfg file. You can also try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An attempt was made to retrieve the contents of file specified, but the file could not be found or does not exist within the scope of WebSphere Studio Asset Analyzer.
The browser action to retrieve the file contents is stopped and the error is displayed.
Ensure that the file exists and can be accessed from the Windows server where WebSphere Studio Asset Analyzer is installed, and try the operation again.
WsaaJar
An attempt was made to execute a distributed query URL that requests a language taxonomy be described, but this feature is not yet implemented. The URL in question contains SQL=DESCRIBE and TAX_FOR_LANG= parameter specifications.
The query cannot be run. The error is displayed.
Use the browser's Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An attempt was made to execute a distributed query URL with an invalid value for either the NUM_RESULTS= or START_RESULT= parameter. Valid values are greater than or equal to 0 or 1, respectively.
The browser action is stopped, and the error is displayed.
If you have manually updated the URL in the browser, ensure that you have specified the correct value for NUM_RESULTS= or START_RESULT= on the URL and execute the process again. You can also try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
During initialization of the distributed query servlet, the logs could not be created properly.
Processing continues as usual, but errors cannot be logged.
Examine other error logs for information that may be pertinent to this error. It could be that the directory in which the postprocessing logs are kept is not accessible or does not have the proper authority. Consult your IBM technical-support representative for assistance.
WsaaJar
During initialization of the distributed query servlet, an exception occurred while trying to initialize the database, scanner manager, or analyzer manager identified in the configuration files.
Processing stops. The query servlet cannot be initialized, thus preventing the WebSphere Studio Asset Analyzer product itself from being loaded when the HTTP or WAS servers are started. This is a critical error preventing any operation of the product.
Examine the error logs for information on the configuration of the scanner or analyzer managers, or any issues with connecting to the database itself. Consult your IBM technical-support representative for assistance.
WsaaJar
During initialization of the distributed query servlet, an exception occurred while trying to read the forbiddenQueryColumns located in the /assetloc/config/EColabraApplication.cfg file.
Processing stops. The query servlet cannot be initialized, thus preventing the WebSphere Studio Asset Analyzer product itself from being loaded when the HTTP or WAS servers are started. This is a critical error preventing any operation of the product.
If you have inadvertently updated the value in the /assetloc/config/EColabraApplication.cfg configuration file, you must reset it to its original content and try the operation again. Ensure that the configuration file exists and can be accessed. Consult your IBM technical-support representative for assistance.
WsaaJar
An exception occurred during execution of a query from the distributed user interface.
The query execution is stopped, and the error is displayed in the browser.
Examine the WebSphere Studio Asset Analyzer logs for any information related to the query exception. Use the browser Back button to return to a valid state in the browser and try the operation again after fixing any problems. Consult your IBM technical-support representative for more assistance.
WsaaJar
An attempt was made to execute a distributed query URL that requests a language taxonomy be described, but this feature is not yet implemented. The URL in question contains SQL=DESCRIBE and TAX_FOR_LANG= parameter specifications.
The query cannot be run. The error is displayed.
Use the browser's Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during invocation of the distributed query servlet due to a request to query views using the SQL=VIEW parameter, but the View Manager is not activated.
The distributed functionality cannot be invoked from the browser. The error is displayed.
Use the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An exception occurred during execution of a distributed table because the DB2 table associated with a scanner or analyzer could not be found in the WebSphere Studio Asset Analyzer metadata schema. Either the table names are incorrectly specified in the /assetloc/config/Scanners.cfg or /assetloc/config/Analyzers.cfg configuration files or the database was created incorrectly.
The distributed query cannot be executed. The error is displayed.
Ensure that you have correctly identified the DB2 tables associated with your scanners and analyzers by verifying the definitions in the Scanners.cfg and Analyzer.cfg configuration files. Also, ensure that the tables identified in these configuration files exist in the WebSphere Studio Asset Analyzer database. Try the operation again after correcting any errors. Consult your IBM technical-support representative for further assistance.
WsaaJar
During execution of a distributed query, an invalid date format was specified for the DATE= URL parameter. A valid date value must in the format yyyy/MM/dd.
The distributed query cannot be run. The error is displayed.
If you have manually updated the URL in the browser, ensure that you have specified the correct value for DATE= in the format expected. You can also try using the browser Back button to return to a valid state in the browser and allow WebSphere Studio Asset Analyzer to issue the URLs correctly by selecting a link from the user interface. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected exception has occurred while attempting to run a distributed search because one or more column names specified for that search are not valid for the asset type.
The search request is stopped. The error is displayed.
If you have manually updated the /assetloc/config/Framework.xml file, you must ensure that valid column names are specified. Revert back to the original copy of Framework.xml shipped with the product and try your search request again.
WsaaJar
An unexpected exception has occurred while attempting to run a distributed search because one or more search values specified are not valid.
The search request is stopped. The error is displayed.
If you have manually updated the /assetloc/config/Framework.xml file, you must ensure that valid column names are specified. Revert back to the original copy of Framework.xml shipped with the product and try your search request again. Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected exception has occurred while attempting to run a distributed search either because there is no analyzer defined or because the DB2 table associated with that analyzer cannot be found in the WebSphere Studio Asset Analyzer metadata schema.
The search request is stopped. The error is displayed.
Ensure that you have correctly identified the DB2 tables associated with your analyzers by verifying the definitions in the /assetloc/config/Analyzer.cfg configuration file. Also, ensure that the tables identified in this configuration file exist in your WebSphere Studio Asset Analyzer database. Try the operation again after correcting any errors. Consult your IBM technical-support representative for further assistance.
WsaaJar
An unexpected error has occurred while executing a distributed search because the boolean operators specified are invalid.
The search is stopped. The error is displayed.
Consult your IBM technical-support representative for assistance.
WsaaJar
An unexpected exception has occurred while attempting to run a distributed search because one or more column names specified for that search are not valid for the asset type.
The search request is stopped. The error is displayed.
If you have manually updated the /assetloc/config/Framework.xml file, you must ensure that valid column names are specified. Revert back to the original copy of Framework.xml shipped with the product and try your search request again.
WsaaJar
This message is displayed among the set of search results when a type for a column value represented in DB2 cannot be presented on the browser as a string value. The message is displayed instead of the value itself.
The system is functioning normally. Search results are returned, but values that cannot be presented properly have this message displayed.
None
WsaaJar
An exception occurred while trying to view source from a ClearCase repository, because the path name specified for access is not a valid ClearCase path name.
The source cannot be retrieved, so processing stops. The error is displayed.
This error could occur when a previously scanned ClearCase repository is no longer valid or accessible for the path indicated. Verify that the path specified is valid and points to a ClearCase repository that can be access by WebSphere Studio Asset Analyzer. Also verify that source exists at that path. Try the operation again after fixing any problems.
WsaaJar
The JDBC driver class specified by the 'Database.driver' setting in Common.cfg could not be loaded by the JVM.
Servlet initialization is stopped.
Update the specified setting, or add the JDBC driver to classpath, and restart the web application.
WsaaJar
An exception occurred while attempting to initialize a scanner based on information specified in the /assetloc/config/AssetLocator.cfg file. The scanner specified cannot be instantiated.
The scanning process is stopped. The error is displayed.
Ensure that you have correctly specified the set of scanners in the /assetloc/config/AssetLocator.cfg file. If necessary, revert back to the copy of this configuration file shipped with the WebSphere Studio Asset Analyzer product.
WsaaJar
An exception occurred while trying to view the source specified. The source could not be found using that path name.
The source cannot be retrieved, so processing stops. The error is displayed.
This error occurs because an asset has been scanned using the specified path, and that asset cannot be located from a browser request to view the source. Either the source no longer exists or the path cannot be accessed. Ensure that the specified path name can be found and try the operation again.
WsaaJar
This a warning indicating that postprocessing for assets being queried or searched in the browser has not yet completed. Results of exploration through the browser may not be accurate.
The system is functioning normally, but all results are not yet committed, because scanning and analysis are not complete.
Wait for postprocessing to finish for the assets you are exploring in the browser before continuing the exploration.
WsaaJar
An exception occurred during a search for assets from the browser because too many columns were selected as search criteria.
The search cannot be performed. The error is displayed.
Select fewer columns for the search criteria and attempt the search again.
WsaaJar
An exception occurred during a search for assets from the browser because of an SQL error. The exact error is shown.
The search cannot be performed. The error is displayed.
Examine the SQL error and attempt to fix any problems. Try the search again or contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred while attempting to initialize the product tables used during WebSphere Studio Asset Analyzer processing. These tables are used during the scanning, analysis, postprocessing, and exploration activities.
The process being run at the time of the exception is stopped. Processing can continue, although it is likely that this error will occur again, requiring that it be resolved before WebSphere Studio Asset Analyzer can function normally. The errors are logged.
Examine the logs for causes of the exception as specified in the error message and try the operation again. Contact your IBM technical-support representative if the problems cannot be resolved.
WsaaJar
During postprocessing, an invalid attempt was made to add reference links because multiple parameters were specified when only one was expected.
Postprocessing for the current asset is stopped. Processing continues for the next asset.
Contact your IBM technical-support representative for assistance.
WsaaJar
During postprocessing, an invalid attempt was made to add reference links because a parameter was specified that was not a string. A string type was expected.
Postprocessing for the current asset is stopped. Processing continues for the next asset.
Contact your IBM technical-support representative for assistance.
WsaaJar
An exception occurred during postprocessing while attempting to find the container for the asset being processed. Multiple containers were found when only one is expected.
Postprocessing for the current asset is stopped. Processing continues for the next asset.
Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during postprocessing because the specified table could not be found in the WebSphere Studio Asset Analyzer metadata schema in the database.
Postprocessing for the current asset is stopped. Processing continues for the next asset.
Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected error occurred during postprocessing because the specified table could not be found in the WebSphere Studio Asset Analyzer metadata schema in the database.
Table initialization fails and postprocessing for the current asset is stopped. The error is logged, and processing continues for the next asset.
Contact your IBM technical-support representative for assistance.
WsaaJar
An unexpected database error has occurred while attempting to determine the next valid identifier to use for a URL space to be stored in the database.
Initialization fails and analysis and postprocessing stops for the current asset. The error is logged, and processing continues for the next asset.
Consult the logs to determine if the database error is a result of access or communications problems and try the operation again after solving the problem. Contact your IBM technical-support representative for assistance.
WsaaJar
During postprocessing for an EAR or WAR file asset, an invalid containment for the URL was encountered.
Storing of the asset fails. Analysis continues for the next asset.
Contact your IBM technical-support representative.
WsaaJar
This is an informational message indicating that there is no Java Processor Layer Manager running, but a request to stop it has been issued.
The system is functioning properly.
None
WsaaJar
During initialization of the Java processor, a failure occurred while validating the data for initialization.
Processing stops for the current pattern detector. Processing continues with the next pattern detector.
Validate that the pattern detector configuration files and the runtime environment are correct. Try to reactivate WebSphere Studio Asset Analyzer. Contact your IBM technical-support representative.
WsaaJar
An exception occurred while running the specified pattern detector during postprocessing.
Processing stops for the current pattern detector instance. Processing continues with the next pattern detector instance.
Contact your IBM technical-support representative.
WsaaJar
This is an informational message logged when the specified pattern detector engine is started.
The system is functioning normally.
None
WsaaJar
This is an informational message logged when the specified pattern detector engine is finished.
The system is functioning normally.
None
WsaaJar
This is an informational message logged when the pattern detector server is started.
None
The system is functioning normally.
WsaaJar
This is an informational message logged when the pattern detector server is finished.
The system is functioning normally.
None
WsaaJar
This is an informational message logged when entering the scope of a pattern detection operation.
The system is functioning normally.
None
WsaaJar
This is an informational message logged when entering the scope of a pattern detection operation.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the log indicating that a pattern was found during pattern detection processing. More information on the results follows this message in the log.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the log indicating that the specified JAR file or directory was found to contain a pattern instance undergoing pattern detection processing.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the log indicating that the specified class was found to contain a pattern instance undergoing pattern detection processing.
The system is functioning normally.
None
WsaaJar
An exception occurred while attempting to retrieve the servers for processing using the pattern detector. There were no servers to retrieve.
Processing stops for the current pattern detector instance. Processing continues with the next pattern detector instance.
Ensure that you have properly configured the system to perform pattern detection by specifying servers for processing. Try the operation again or contact your IBM technical-support representative for further assistance.
WsaaJar
During postprocessing analysis, a signal was received to stop processing.
The system is functioning normally. Processing is stopped and the message is logged.
None
WsaaJar
An error was encountered during pattern detector analysis.
The current server analysis using the pattern detector is stopped and the error is logged. Processing continues with the next server.
Examine the error logs to determine if the issue can be resolved locally and try the operation again. Contact your IBM technical-support representative for assistance.
WsaaJar
An error was encountered during pattern detector analysis.
The current server analysis using the pattern detector is stopped, and the error is logged. Processing continues with the next server.
Examine the error logs to determine if the issue can be resolved locally and try the operation again. Contact your IBM technical-support representative for assistance.
WsaaMain
An unexpected error occurred when an attempt was made to set parent information where it is not allowed.
Processing for the current scope using the pattern detector is stopped. Processing continues with the next scope.
Contact your IBM technical-support representative.
WsaaJar
An unexpected error occurred because a method was called during pattern detection postprocessing but this method is not supported for the class specified.
Postprocessing is stopped for the current asset, and the error is logged. Processing continues for the next asset.
Consult your IBM technical-support representative.
WsaaJar
An unexpected error occurred because a method was called during pattern detection postprocessing, but this method is not supported for the class specified.
Postprocessing is stopped for the current asset, and the error is logged. Processing continues for the next asset.
Consult your IBM technical-support representative.
WsaaMain
An unexpected error occurred because an attempt was made to find a class in WebSphere Studio Asset Analyzer during pattern detection postprocessing, but the class name is invalid or the class does not exist.
Postprocessing is stopped for the current asset, and the error is logged. Processing continues for the next asset.
Consult your IBM technical-support representative.
WsaaJar
An error occurred during pattern detection postprocessing while attempting to report a pattern found.
Postprocessing is stopped for the current asset, and the error is logged. Processing continues for the next asset.
Consult your IBM technical-support representative.
WsaaJar
An error occurred during pattern detection postprocessing while attempting to find the source component for a found pattern.
The pattern detector is stopped for the current asset, and the error is logged. Processing continues for the next asset.
Consult your IBM technical-support representative.
WsaaJar
An error occurred during pattern detection postprocessing while attempting to find the target component for a found pattern.
The pattern detector is stopped for the current asset, and the error is logged. Processing continues for the next asset.
Consult your IBM technical-support representative.
WsaaJar
An error occurred during pattern detection postprocessing while attempting to store a found link in the WebSphere Studio Asset Analyzer database.
Postprocessing is stopped for the current asset, and the error is logged. Processing continues for the next asset.
Verify database access. Consult your IBM technical-support representative.
WsaaMain
An error occurred while attempting to load information from the pattern detector configuration file. This configuration file defines the patterns to detect. The specifics of the error are included in the message.
The postprocessor for pattern detection cannot be initialized. Processing is stopped, and the error is logged. Processing continues for the next postprocessor.
Ensure that the pattern detection configuration files located in /assetloc/config/patterns exist and are accessible to WebSphere Studio Asset Analyzer. Consult your IBM technical-support representative for further assistance.
WsaaMain
An error occurred during pattern detection postprocessing because the specified pattern has not been defined.
Postprocessing is stopped, and the error is logged. Processing continues for the next asset.
Consult your IBM technical-support representative.
WsaaMain
An error occurred during pattern detection postprocessing because the specified class name was defined as a verifier for the component locator, but it is not defined or cannot be found in WebSphere Studio Asset Analyzer.
Postprocessing is stopped, and the error is logged. Processing continues for the next asset.
If you have manually updated the pattern detection configuration files in /assetloc/config/patterns, ensure that you have correctly specified the verifier class names. You may need to revert back to the configuration files shipped with WebSphere Studio Asset Analyzer. Consult your IBM technical-support representative.
WsaaMain
An error occurred during pattern detection postprocessing because the specified pattern has already been defined in another pattern configuration file.
Postprocessing is stopped, and the error is logged. Processing continues for the next asset.
If you have manually updated the pattern detection configuration files in /assetloc/config/patterns, ensure that you have correctly specified the patterns for detection and that each pattern occurs once. You may need to revert back to the configuration files shipped with WebSphere Studio Asset Analyzer. Consult your IBM technical-support representative.
WsaaJar
An error occurred during postprocessing for pattern detection because the specified WAR file details cannot be accessed by WebSphere Studio Asset Analyzer or the data in the database is in an inconsistent state.
Postprocessing is stopped for the current asset. Processing continues for the next asset.
Contact your IBM technical-support representative for further assistance.
WsaaJar
An error occurred during postprocessing for pattern detection because the location of the EAR is not correct. The scope for pattern detection cannot be established for the current asset.
Postprocessing is stopped for the current asset. Processing continues for the next asset.
Contact your IBM technical-support representative for further assistance.
WsaaJar
An error occurred during postprocessing for pattern detection because the specified EJB JAR file details cannot be accessed by WebSphere Studio Asset Analyzer or the data in the database is in an inconsistent state.
Postprocessing is stopped for the current asset. Processing continues for the next asset.
Contact your IBM technical-support representative for further assistance.
WsaaJar
An exception occurred while attempting to retrieve the servers for processing using the pattern detector. There were no servers to retrieve.
Processing stops for the current pattern detector instance. Processing continues with the next pattern detector instance.
Ensure that you have properly configured the system to perform pattern detection by specifying servers for processing. Try the operation again or contact your IBM technical-support representative for further assistance.
WsaaJar
During postprocessing analysis, a signal was received to stop processing.
The system is functioning normally. Processing is stopped and the message is logged.
None
WsaaJar
An error was encountered during pattern detector analysis.
The current server analysis using the pattern detector, and the error is logged. Processing continues with the next server.
Examine the error logs to determine if the issue can be resolved locally and try the operation again. Contact your IBM technical-support representative for assistance.
WsaaJar
An error has occurred while parsing the pattern detection XML during postprocessing. The reason for the error is specified.
Postprocessing is stopped for the current asset. Processing continues for the next asset.
Examine the logs for information on why the error occurred. It may be that the XML file is invalid. If you have updated the configuration files in /assetloc/config/patterns, revert back to the original files shipped with WebSphere Studio Asset Analyzer and try the operation again. Consult your IBM technical-support representative for further assistance.
WsaaJar
An error has occurred while attempting to access a pattern detection XML configuration file specified during postprocessing.
Postprocessing is stopped for the current asset. Processing continues for the next asset.
Examine the logs for information on why the error occurred. It may be that the configuration file cannot be accessed or opened or that it is invalid XML. If you have updated the configuration files in /assetloc/config/patterns, revert back to the original files shipped with WebSphere Studio Asset Analyzer and try the operation again. If you use the developed or assembled pattern detector, verify that the runtime configuration files in the pattern detector definition are correct. Consult your IBM technical-support representative for further assistance.
WsaaJar
This is an informational message written to the log indicating that the pattern detector has started preparing the structure.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the log indicating that the pattern detector has finished preparing the structure.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the log indicating that the pattern detector has finished searching patterns.
The system is functioning normally.
None
WsaaJar
This is an informational message written to the log indicating that the pattern detector has started searching patterns.
The system is functioning normally.
None
WsaaJar
An unexpected exception occurred while attempting to read configuration information during analysis of Java assets.
Postprocessing for the set of Java assets is stopped. Processing continues with the next postprocessor.
Contact your IBM technical-support representative.
WsaaJar
A general exception occurred in the Java analyzer while analyzing scopes during pattern detection processing. The specific cause of the error is contained in the message.
Pattern detection for the current scope is stopped. Processing continues with the next pattern detector scope.
Examine the logs to determine whether the error can be resolved and try the operation again. Consult your IBM technical-support representative for further assistance.
WsaaJar
During pattern detection processing within the Java analyzer, an exception occurred because the Java classes specified were encountered but are not within the scope defined for the analysis process.
Pattern detection for the current scope is stopped. Processing continues with the next pattern detector scope.
Ensure that the set of classes identified exists and can be accessed for the scope defined to WebSphere Studio Asset Analyzer during pattern detection processing. Try the operation again. If you use the development or runtime pattern detector, verify that those classes are in the runtime configuration. If you use the runtime pattern detector, ensure that the classes are in one of the directories of WS_EXT_DIR of the scanning root definition. Consult your IBM technical-support representative for further assistance.
WsaaJar
During initialization of the configuration for the Java analyzer used by the pattern detector, an error occurred because an export type was identified that is not a valid class in WebSphere Studio Asset Analyzer.
Pattern detection for the scope is stopped. Processing continues with the next scope.
Contact your IBM technical-support representative.
WsaaJar
An unexpected internal error occurred during Java analysis pattern detection.
Pattern detection for the set of Java assets is stopped. Processing continues with the next scope.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred during initialization of the pattern detector process for Java because the configuration does not specify any extractors. The cause of the exception is detailed in the message.
Postprocessing for the set of Java assets is stopped. Processing continues with the next postprocessor.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred during initialization of the pattern detector process for Java because the configuration does not contain a value for the property specified. The cause of the exception is detailed in the message.
Pattern detection for the set of Java assets is stopped. Processing continues with the next scope.
Contact your IBM technical-support representative.
WsaaJar
An exception occurred during initialization of the pattern detector process for Java because the configuration could not be created. The cause of the error is included in the message.
Postprocessing for the set of Java assets is stopped. Processing continues with the next postprocessor.
Contact your IBM technical-support representative.
WsaaMain
During Java pattern detection processing, the specified method was not found when expected within the call graph.
The error is logged and postprocessing continues for the current asset. The resulting information may not be complete.
Examine the error log to determine whether the correct source is being analyzed and the specified method exists as expected. Resolve the errors if possible and try the operation again. Contact your IBM technical-support representative for further assistance.
WsaaMain
During Java pattern detection processing, a method was found, but it was not a valid method type as expected.
The error is logged and postprocessing continues for the current asset. The resulting information may not be complete.
Examine the error log to determine whether the correct source is being analyzed and the specified method exists as expected. Resolve the errors if possible and try the operation again. Contact your IBM technical-support representative for further assistance.
WsaaMain
During Java pattern detection processing, a node specified was found with an invalid type.
The error is logged and postprocessing continues for the current asset. The resulting information may not be complete.
Contact your IBM technical-support representative.
WsaaJar
An attempt was made to construct a pattern from information in the pattern configuration file, but the pattern could not be created based on existing information. The cause of the error is included in the message.
Processing continues, but no results will be produced for the current pattern because it cannot be constructed.
Contact your IBM technical-support representative.
WsaaJar
During construction of a pattern based on information in the pattern detection configuration file, multiple sequences were found, but only one sequence per pattern is supported at this time. The configuration for this pattern is invalid and cannot be constructed.
Processing continues, but no results will be produced for the current pattern because it cannot be constructed.
Contact your IBM technical-support representative.
WsaaJar
The specified operand type was found during construction of a pattern based on information in the pattern detection configuration file, but this operand is not supported.
Processing continues, but no results will be produced for the current pattern because it cannot be constructed.
Contact your IBM technical-support representative.
WsaaJar
The following SQL query was supposed to return 1 row, but instead returned 0 rows.
The servlet request is stopped.
Contact your IBM technical-support representative.
WsaaJar
One or more SQL errors occurred while trying to retrieve data for this page.
The servlet request is stopped.
Try running distributed postprocessing. If the problem persists, contact your IBM technical-support representative.
WsaaJar
This message records the fact that a pattern was not resolved during pattern detection processing.
The system is functioning normally.
None
WsaaMain
During construction of the scopes for pattern detection, an attempt was made to add a class loader to the set of existing class loaders used to define the scope, but the new class loader is already in the chain.
Postprocessing is stopped for the current pattern detector operation, and the error is logged. Processing continues with the next postprocessor.
Contact your IBM technical-support representative.
WsaaMain
During construction of the scopes for pattern detection, an existing class loader was detected within the chain of new class loaders.
Postprocessing is stopped for the current pattern detector operation, and the error is logged. Processing continues with the next postprocessor.
Contact your IBM technical-support representative.
WsaaJar
The specified log file could not be created.
Processing continues without the logging function.
The message specifies the error encountered while attempting to create the indicated file. This could be an I/O or other accessibility error. Ensure that the path in which the logs are being created exists and can be accessed by WebSphere Studio Asset Analyzer. Contact your IBM technical-support representative for further assistance.
WsaaJar
An attempt was made to obtain write access to WebSphere Studio Asset Analyzer log files but an error occurred.
Processing continues without the logging function.
The message specifies the error encountered while attempting to access the log files. This could be an I/O or other accessibility error. Ensure that the path in which the logs are being created exists and can be accessed by WebSphere Studio Asset Analyzer. Contact your IBM technical-support representative for further assistance.
WsaaDbUtil
An exception occurred while attempting to search for an asset. The number of columns specified in the search is zero.
Processing for the current asset is stopped, and the errors are logged. Processing continues for the next asset.
Examine the logs for more information on the error and try the operation again after correcting the problems. Contact your IBM technical-support representative if the issue cannot be resolved.
WsaaDbUtil
An exception occurred while attempting to search on WebSphere Studio Asset Analyzer metadata, because the specified table name is invalid or cannot be found in the WebSphere Studio Asset Analyzer database schema.
Processing for the current asset is stopped, and the errors are logged. Processing continues for the next asset.
Examine the logs for more information on the error. Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to instructions in the Configuration and Migration Guide. If the table does exist in the schema, you may have inaccurate information in one or more of the WebSphere Studio Asset Analyzer configuration files. Contact your IBM technical-support representative for further assistance.
WsaaDbUtil
An exception occurred while attempting to search on WebSphere Studio Asset Analyzer metadata because the specified column in the table indicated is invalid or cannot be found in the WebSphere Studio Asset Analyzer database schema.
Processing for the current asset is stopped, and the errors are logged. Processing continues for the next asset.
Examine the logs for more information on the error. Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to instructions in the Configuration and Migration Guide. If the table does exist in the schema with the column specified, you may have inaccurate information in one or more of the WebSphere Studio Asset Analyzer configuration files. Contact your IBM technical-support representative for further assistance.
WsaaDbUtil
An exception occurred while attempting to search on WebSphere Studio Asset Analyzer metadata because the specified column in the table indicated is found to have an invalid data type or one that is not recognized by WebSphere Studio Asset Analyzer.
Processing for the current asset is stopped, and the errors are logged. Processing continues for the next asset.
Examine the logs for more information on the error. Ensure that you have correctly installed WebSphere Studio Asset Analyzer according to instructions in the Configuration and Migration Guide. If the table does exist in the schema with the column specified, and the type of column is valid, contact your IBM technical-support representative for further assistance.
WsaaDbUtil
An unexpected error occurred while attempting to search for the asset specified in the table indicated. WebSphere Studio Asset Analyzer expects a single result, but multiple results were returned. This error could indicate an inconsistency in the metadata.
Processing for the current asset is stopped, and the errors are logged. Processing continues for the next asset.
Examine the logs for more information on the error. Contact your IBM technical-support representative for further assistance.
WsaaDbUtil
An unexpected error occurred while attempting to search for the asset specified in the table indicated. WebSphere Studio Asset Analyzer expects that metadata for this asset has already been created in the database, but none was found. This error could indicate an inconsistency in the metadata.
Processing for the current asset is stopped, and the errors are logged. Processing continues for the next asset.
Examine the logs for more information on the error. Contact your IBM technical-support representative for further assistance.
WsaaJar
During initialization of the analyzers for processing, WebSphere Studio Asset Analyzer was unable to instantiate the specified class associated with an analyzer as identified in /assetloc/config/Analyzers.cfg.
Analysis processing associated with the invalid class will not be performed. Processing continues normally.
Ensure that you have correctly specified the implementingClass value for analyzers in /assetloc/config/Analyzers.cfg and try the operation again.
WsaaJar
An error occurred during analysis because an invalid XML node was encountered in the specified path.
Analysis for the current asset is stopped. Processing continues with the next asset.
The format of the XML file being processed may be invalid. Check the format of the WAS4AE developed or assembled environment definition XML files specified in the assetloc\config\Admin.cfg configuration file. Contact your IBM technical-support representative for assistance.
WsaaJar
An error occurred during analysis because of an exception while processing the XML file specified. The cause of the error is contained in the message.
Analysis for the current asset is stopped. Processing continues with the next asset.
The format of the XML file being processed may be invalid. Check the format of the WAS4AE developed or assembled environment definition XML files specified in the assetloc\config\Admin.cfg configuration file. Contact your IBM technical-support representative for assistance.
WsaaJar
An error occurred during analysis because of an exception while parsing an XML file. The cause of the error is contained in the message.
Analysis for the current asset is stopped. Processing continues with the next asset.
The format of the XML file being processed may be invalid. Contact your IBM technical-support representative for assistance.
WsaaJar
While attempting to construct a message for logging or display on the browser, a null message identifier was passed to the message framework.
The message cannot be displayed properly, but information is logged.
Contact your IBM technical-support representative.
WsaaJar
While attempting to construct a message for logging or display on the browser, an invalid message identifier specified was passed to the message framework.
The message cannot be displayed properly but information is logged.
Contact your IBM technical-support representative.
WsaaJar
Scope Space id id was not found.
The links computation for this scope space will be ignored.
Contact your IBM technical-support representative.
WsaaJar
No scope space was found for a given asset asset type even though there should be one.
The links computation for this scope space will be ignored.
Contact your IBM technical-support representative.
WsaaJar
An element of an object array was not the same as all the other element in the array.
Processing stops. The object arrays cannot be concatenated.
Contact your IBM technical-support representative.
WsaaJar
Error while trying to search class class name for patterns, skipping it. A candidate for pattern has an error in it therefore it will not be processed.
The class will not be considered in the pattern detector calculation.
Contact your IBM technical-support representative.
WsaaJar
Unable to load required file fileName for configuration.
This is a severe error and the Pattern Detector needs to stop.
Verify your installation. Contact your IBM technical-support representative.
WsaaJar
Only WAS version 4 and 5 are supported at this time.
The Pattern detector for this server will be skipped.
Change the configuration to only scan WAS version 4 or version 5 servers.
WsaaJar
Cannot create ClassLoader for Ear: ear location, skipping it.
This Ear will be skipped for pattern detector
Contact your IBM technical-support representative.
WsaaJar
File retrieval error, retriever not supported for Scanner type scanner type.
The asset will not be retrieved.
Contact your IBM technical-support representative.
WsaaJar
Link type type does not exist between assets source asset and target asset This might be as a result of incompatible configuration or an error in WebSphere Studio Asset Analyzer installation
This link will not be added to the metadata repository.
Verify your installation. Contact your IBM technical-support representative.
WsaaJar
Error while trying to run Pattern Detector on Cell [cell], skipping it for pattern detection.
This cell will be skipped for pattern detection and the next cell will start.
Contact your IBM technical-support representative.
WsaaJar
A cell requires a server to be analyzed. The cell [cell] has no server and is skipped.
The WAS cell will not be processed.
None
WsaaJar
RAR files require only one manifest file; the application found more.
The RAR will be skipped.
Contact your IBM technical-support representative.
WsaaJar
Informational message for status.
Runs all the postprocessors that belong to this runtime and that are not incremental.
None
WsaaJar
The postprocessor does not support incremental postprocessing but is defined to be incremental in the configuration file.
The postprocessor will be skipped.
Change the incremental attribute for this postprocessor in eColabraApplication.cfg.
WsaaJar
The change flag is unknown.
The state will be set to changed to force the postprocessor to run next time a scan is performed.
Contact your IBM technical-support representative.
WsaaJar
System is functioning normally.
Postprocessing has started.
None
WsaaJar
The query to get all the scanning roots in order to perform postprocessing on them has an Exception
The postprocessing will abort
Verify that you have Database connection. Contact your IBM technical-support representative.
WsaaJar
Since the collection's type isn't a string of some sort, the mapping to the database is illegal.
The asset will not be stored in the database
Contact your IBM technical-support representative.
WsaaJar
Can't get Web modules (WAR) for server [server resource].
The Pattern Detector for this server will stop.
Verify the runtime configuration in the scanning root.
WsaaJar
Can't get EJB JAR modules for server [server resource].
The Pattern Detector for this server will stop.
Verify the runtime configuration in the scanning root.
WsaaJar
Initializing server bridge [server resource] failed, skipping it.
The server will be skipped for Pattern Detection.
Verify that the configuration files for the scanning root and runtime is correct and try to run the scan again.
WsaaJar
Couldn't create Classloader and Scope for EJB Jar [file location], skipping it.
This EJB JAR will be skipped for pattern detection.
Verify that the configuration files for the scanning root and runtime is correct and try to run the scan again.
WsaaJar
No deployed ears found for the current EAR.
This Ear will be skipped for pattern detection.
Contact your IBM technical-support representative.
WsaaJar
Multiple deployed ears found for the current EAR.
Continue processing with the first deployed EAR.
Contact your IBM technical-support representative.
WsaaJar
The extracted resource is a collection. It is most likely a directory.
The resource will be skipped.
Contact your IBM technical-support representative.
WsaaJar
The extracted resource is not a collection. It is most likely a file.
Resource will be skipped.
Contact your IBM technical-support representative.
WsaaJar
Can not create a resource in order to analyze it. This is usually as a result of illegal XML file as a scanning root definition in WAS scanners.
The scanning root is ignored and processing is done for the next scanning root.
Verify the WAS scanning root definition.
WsaaJar
The XML config scanning root file should be in the database, but it is not.
The scanning root is ignored and processing continues to the next asset.
Contact your IBM technical-support representative.
WsaaJar
A resource type was different than what was expected.
Resource will be skipped.
Contact your IBM technical-support representative.
WsaaJar
The resource is not a file. It is most likely a directory.
Resource will be skipped.
Contact your IBM technical-support representative.
WsaaJar
The resource is not a directory. It is most likely a file.
Resource will be skipped.
Contact your IBM technical-support representative.
WsaaJar
The resource passed is a non-file-system resource, It is probably belongs to another scanner.
Resource will be skipped.
Contact your IBM technical-support representative.
WsaaJar
The resource passed is a non-ClearCase resource, It is probably belongs to another scanner.
Resource will be skipped.
Contact your IBM technical-support representative.
WsaaJar
The ClearCase scanning root definition is not correct or the ClearCase client is not installed correctly.
The scanning root will be skipped.
Correct the configuration and scan again.
WsaaJar
The implementation class for the scanner is missing.
The scanner will be skipped.
Contact your IBM technical-support representative.
WsaaJar
There is a parsing error when trying to parse the Java part of the JSP file.
The Java information from the JSP will not be collected.
Verify if this JSP is well formed. If so then contact your IBM technical-support representative.
WsaaJar
Unable to add filter to SRVLMAP table.
The resource is skipped.
Verify that configuration is correct and database connection is working correctly.
WsaaJar
Transaction type, message selector, acknowledge mode, subscription durability, subscription durability, or destination type is unknown.
The resource is skipped.
Verify sources are valid.
WsaaJar
EjbAnalyzer expected for an EjbDescriptor but got another descriptor.
The resource is skipped.
Contact your IBM technical-support representative.
WsaaJar
The column was not found for a rule of HTML/JSP analyzer and thus the rule is not legal.
The rule is skipped for all resources.
Contact your IBM technical-support representative.
WsaaJar
The column was not found for a rule of HTML/JSP analyzer and thus the rule is not legal.
The rule is skipped for all resources.
Contact your IBM technical-support representative.
WsaaJar
An illegal implementation for rule in HTML/JSP analyzer.
The rule is skipped for all resources.
Contact your IBM technical-support representative.
WsaaJar
An illegal implementation for of one of the parts in HTML/JSP analyzer rules.
The rule is skipped for all resources.
Contact your IBM technical-support representative.
WsaaJar
A declared external table was not found and thus the data can not be set in it.
All resources of the external table's asset will be skipped.
Contact your IBM technical-support representative.
WsaaJar
An illegal implementation for rule in HTML/JSP analyzer.
The rule is skipped for all resources.
Contact your IBM technical-support representative.
WsaaJar
A parsing error occurred in one of the HTML/JSP tags.
The tag will be skipped.
Verify that the tag is well formed.
WsaaJar
Illegal type of attribute tries to put in a column in external asset table
The asset is skipped.
Contact your IBM technical-support representative.
WsaaJar
The method was called in illegal state.
The resource is skipped.
Contact your IBM technical-support representative.
WsaaJar
One of the dependent analyzers and/or dependent postprocessors does not exist.
The postprocessor will be skipped.
Verify dependencies in eColabraApplication.cfg. Contact your IBM technical-support representative.
WsaaJar
The dependent postprocessor did not succeed because a dependent analyzer or postprocessor did not exist or failed.
This postprocessor will not be run.
Contact your IBM technical-support representative.
WsaaJar
A dependent postprocessor does not exists or not activated as a result another postprocessor will not run.
This postprocessor will not be run.
Verify the dependency in eColabraApplication.cfg. Contact your IBM technical-support representative.
WsaaJar
A dependent Analyzer does not exists as a result the postprocessor will not run.
This postprocessor will not be run.
Verify the dependency in eColabraApplication.cfg. Contact your IBM technical-support representative.
WsaaJar
The active property in the postprocessor section of the configuration is not set to "true".
The postprocessor will be skipped.
If the postprocessor should be run, update the configuration. If the postprocessor was intended to be skipped, the system is functioning normally and no action is required.
WsaaJar
The section number for this postprocessor does not exist in the configuration.
Processing stops.
Add the required section to the postprocessor configuration.
WsaaJar
Each postprocessor should run either in the 'scanner' or the 'servlet' but this postprocessor is not defined as either of them in eColabraApplication.cfg
The postprocessor will be skipped.
Correct configuration to only have valid postprocessor section.
WsaaJar
This is a message used in development and debug. The message is meant for the developer and therefore not translated. The user should only see this message when logging is set to the debug level.
The system is being run with logging set to the debug level.
Turn the logging level to a lower level if you do not want this message logged.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1099
U.S.A
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1099
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. @copy; Copyright IBM Corp. 2001, 2003. All rights reserved.
Programming interface information is intended to help you create application software using this program.
General-use programming interfaces allow the customer to write application software that obtain the services of this program's tools.
However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.
Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.
The following terms are trademarks of International Business Machines Corporation in the United States, or other countries, or both:
CICS
CICS Connection
CICS/ESA
DB2
DB2 Universal Database
IBM
IMS
IMS/ESA
Language Environment
MVS
Net.Data
OS/390
QMF
RACF
S/390
VisualAge
VTAM
WebSphere
z/OS
Domino is a trademark of Lotus Development Corporation in the United States, or other countries, or both.
Tivoli and NetView are trademarks of Tivoli Systems Inc. in the United States, other countries, or both.
Active Accessibility, Microsoft, Windows, Windows NT, Wizard and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States, or other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, or other countries, or both.
UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
Other company, product, and service names, which may be denoted by a double asterisk(**), may be trademarks or service marks of others.