Messages and Codes - IBM

Rational Asset Analyzer 

 

Messages and Codes 

Version 6 Release 1 

GC27-5448-00

Note 

Before using this information and the product it supports, read the information in “Notices,” on page 157. 

This edition applies to version 6.1 of Rational Asset Analyzer and to all subsequent releases and modifications until 

otherwise indicated in new editions. 

© Copyright IBM Corporation 2011, 2013. 

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract 

with IBM Corp.

Contents 

Introduction to messages . . . . . . . 1 

Other Message Sources . . . . . . . . . . . 1 

Messages begining with AES . . . . . . . . . 2 

Messages begining with DMH . . . . . . . . 9 

Trademarks and service marks . . . . . . . 159 

Index . . . . . . . . . . . . . . . 161 

Appendix. Notices . . . . . . . . . 157 

Programming interface information . . . . . . 159 

© Copyright IBM Corp. 2011, 2013 iii

iv 

Messages and Codes

Introduction to messages 

This book assumes that you are familiar with the functions of the operating system 

where Rational 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. 

Rational 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. 

XXX 

nnnn 

S 

Represents the message prefix. Rational Asset Analyzer messages have the 

following prefixes: 

v AES - generated by the Rational Asset Analyzer Proprietary Scanner 

v DMH - generated by all other Rational Asset Analyzer modules 

Represents the message number. Messages are listed in numeric order in 

this book. 

Represents the message severity. Rational Asset Analyzer messages have 

the following severity levels: 

v I - Informational message 

v W - Warning message 

v E - Error message 

v S - Severe message 

Other Message Sources 

Information provided for each message includes the following: 

Module 

The Rational Asset Analyzer program module that issues the message. 

Explanation 

What the message means. 

System Action 

What Rational Asset Analyzer does after the message is issued. Some 

errors may require Rational Asset Analyzer to stop processing, for 

example, while others may require it to skip the asset the message was 

issued for and continue processing the next asset. 

User Response 

How to recover from the error. 

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. 

One example of messages generated by other programs is the compiler messages 

generated by IBM ® Enterprise COBOL compiler and IBM Enterprise PL/I compiler. 

When you analyze your assets with the Rational Asset Analyzer Compiler Based 

Scanner, you may get some messages generated by the compiler. The length of 

© Copyright IBM Corp. 2011, 2013 1

AES1001E • AES1010E 

Messages begining with AES 

Rational Asset Analyzer messages is restricted to 133 bytes to prevent the size 

redundancy of the Rational Asset Analyzer database. Because of this length limit, 

compiler messages are sometimes truncated in the activity log. 

AES1001E 

Explanation: 

application. 

System action: 

User response: 

Module: 

AES1003E 

Memory error. 

This is an internal error of the 

Processing stops. 

Contact IBM Software Support. 

Asset Analyzer Proprietary Scanner 

Read error for 'filename'. 

Explanation: An error occurred while reading from 

file filename. Improper file access authority is the likely 

cause. 

System action: The scanner skips the current file, and 

processing continues. 


analysis. 

Module: 

Resolve the problem; reattempt the 


Explanation: 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. 



analysis. 

Module: 

AES1007E 

Explanation: 

application. 

The scanner continues the processing. 

Correct the source file; reattempt the 


There is no name for the data in line 

number. 


System action: The scanner skips the current file and 



Module: 



AES1004E 

Found unsupported syntax 'token' in line 

number. 

Explanation: Unsupported syntax has been found at 

token in line number. If the message shows ** 

UNKNOWN STRING ** in the token field, the scanner 

was unable to display the reserved word found to be in 

error for the line number indicated. 

System action: Scanning terminates for the current 

file, and processing continues. 

User response: Correct the source file for proper PL/I 

or COBOL syntax; reattempt the analysis. 

Module: 

AES1005E 


Found unsupported syntax 'token' in line 

number in copy/include file 'filename'. 

Explanation: Unsupported syntax has been found at 

token in line number of copy or include file filename. 



User response: Correct the copy or include file for 

proper COBOL or PL/I syntax; reattempt the analysis. 

Module: 

AES1006W 


There is an assignment to a nondata 

item in line number. 

AES1008E 

Explanation: 

application. 

There is no internal structure for the 

data in line number. 





Module: 

AES1009E 

Explanation: 

application. 



Stack overflow. 





Module: 

AES1010E 

Explanation: 

application. 



The file name is empty. 






2 Messages and Codes

AES1012E • AES1029W 

Module: 

AES1012E 

Explanation: 

opened. 


The source file 'filename' is not opened. 

The specified source file cannot be 



User response: Check that the file name is correct; 

reattempt the analysis. 

Module: 

AES1013W 


There is no data definition for 'dataitem' 

in line number. 

Explanation: 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. 




analysis. 

Module: 

AES1015E 



There are no executable statements. 

Explanation: The source program does not have any 

executable statements. 




analysis. 

Module: 

AES1016E 



There are no PROCEDURE statements. 

Explanation: The PROCEDURE division of the file 

cannot be located. This message occurs for COBOL 





analysis. 

Module: 

AES1017E 



Found unsupported syntax in file 

filename referred in line number in source 

file. 

Explanation: Unsupported syntax has been found in 

line number of the source file filename. 



User response: Correct the syntax in the source file; 


Module: 

AES1018E 


Found unsupported syntax in file 

'filename' referred in line number in 

copy/include file 'filename'. 

Explanation: Unsupported syntax has been found in 

line number of the copy or include file filename. This 

message occurs for PL/I components only. 



User response: Correct the syntax in the copy or 

include file; reattempt the analysis. 

Module: 

AES1019W 


There is an assignment to a nondata 

item 'name' in line number. 

Explanation: 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 


System action: The scanner ignores this assignment 

and continues processing. 


analysis. 

Module: 

AES1028W 



Call 'name' in line number has no 

function parameters. This call is 

ignored. 

Explanation: The name defined as the call interface on 

line number has been used, but there is no parameter 

corresponding to the defined function parameter. 

System action: This scanner ignores the call and 

continues processing. 

User response: Correct the call interface definition; 


Module: 

AES1029W 


Size of data item 'dataitem' in line 

number of file filename cannot be 

computed. The size is assumed to be 1 

byte. 

Explanation: The size of the data item declared on 

line number in file filename cannot be calculated. The 

data item is assumed to be 1 byte. 

System action: The scanner assumes a size of 1 byte 

for the data item and continues processing. 

Rational Asset Analyzer messages 3

AES1030W • AES1043W 

User response: Correct the source file; reattempt the 

analysis. 

Module: 

AES1030W 


Size of data item 'dataitem' in line 

number cannot be computed. The size is 

assumed as 1 byte. 

Explanation: The size of the data item declared on 

line number cannot be calculated. The data item is 

assumed to be 1 byte. 

System action: The scanner assumes a size of 1 byte 

for the data item and continues processing. 


analysis. 

Module: 

AES1031W 



The definition of 'dataitem' redefined in 

line number is not found. This 

REDEFINES clause is ignored. 

Explanation: 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. 

System action: The scanner ignores the REDEFINES 

clause and continues processing. 


analysis. 

Module: 

AES1032W 



There are no procedure-name 'name' in 

line number. 

Explanation: The process procedure name on line 

number has been referenced, but name cannot be found. 





analysis. 

Module: 

AES1035W 



There is no definition for built-in 

function/routine 'name' in line number. 

Explanation: The built-in function or routine used in 

line number cannot be processed. The function name or 

routine name may be incorrect. 




analysis. 

Module: 



AES1039E 

Declare of data item 'dataitem' cannot be 

processed. 

Explanation: The definition of name cannot be 

processed. This message occurs for PL/I components 

only. 



User response: The source file may be wrong. Correct 

the syntax, if necessary, and reattempt the analysis. 

Module: 

AES1040W 


Found unsupported EXEC statement in 

line number. It is ignored. 

Explanation: The line indicated contains an EXEC 

statement other than EXEC SQL, EXEC CICS ® , or EXEC 

DLI. 

System action: The scanner ignores the EXEC 

statement and continues processing. 


Module: 

None. 


AES1041W Member name was truncated to 8 

characters: name 

Explanation: Scanner encountered a long 

copy/include member name. 

System action: Scanner would truncate the name, and 


User response: Correct the copy/include member 

name, and reattempt the analysis. 

Module: 

AES1042E 


A recursive reference was found on the 

process of the include file '%1'. 

Explanation: Scanner encountered the same copybook 

on the preprocessing for a copybook. 

System action: The scanner terminated the current 

analysis, and continue the inventory process for the 

next programing asset. 

User response: Correct the source program, and 


Module: 

AES1043W 


An unresolved reference to table/view 

correlation name name was found on 

line number. It is ignored. 

Explanation: A scanner encountered a correlation 

name for table/view on the source line, but it was 

impossible to resolve the correlation name, because it 

referred to multiple tables/views. 


AES1045E • AES2002I 


Scanner would ignore the reference. 

User response: None. It is a limitation of the static 

program analysis. If you improve the analysis, 

explicitly qualify the reference with table/view name 

by modifying the source program. 

Module: 

AES1045E 

Explanation: 

application. 


There is no routine 'name'. 





Module: 

AES1048W 



There are multiple declarations in the 

same scope for symbol 'name' in line 

number. 

Explanation: Multiple declarations for the data item 

referenced in line number have been found. This 

message occurs for PL/I components only. 



the analysis. 

Module: 

AES1056W 


Correct the source program; reattempt 


DD name of file 'filename' is not found. 

This file is not handled as an IO file. 

Explanation: File filename has been referenced, but 

there is no DD name for it. This message occurs for 

COBOL components only. 



the analysis. 

Module: 

AES1057E 




File name 'filename' is not declared. 

Explanation: The file filename is not declared. This 

message occurs for COBOL components only. 




the analysis. 

Module: 



AES1121W 

The declare statement of 'dataitem' 

includes a DEFINE for an element of an 

array. This DEFINE is ignored. 

Explanation: 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 


System action: The scanner ignores the DEFINE 

clause and continues processing. 

User response: 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. 

Module: 

AES1124W 


There is a too long token in line number. 

Explanation: A token of more than 256 characters has 

been found on line number. Probably the closing 

apostrophe (')intheliteral has been omitted. 



analysis. 

Module: 

AES2000E 

Explanation: 

application. 




Memory Error. 





Module: 

AES2001I 



Start the syntax analysis for program 

'name'. [timestamp] 

Explanation: The scanner has begun the parsing 

process for program name at the time indicated. 



Module: 

AES2002I 

The system is functioning normally. 

None 


Complete the syntax analysis for 

program 'name'. [timestamp] 

Explanation: The scanner has successfully completed 

the parsing process for program name at the time 

indicated. 



Module: 


None 



AES2003I • AES2020W 

AES2003I 

Complete the syntax analysis for 

program 'name' with warnings. 

[timestamp] 

Explanation: The scanner has completed the parsing 

process for program name at the time indicated, but the 

scanner has issued a warning. 



User response: 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. 

Module: 

AES2004I 


Fail the syntax analysis for program 

'name'. [timestamp] 

Explanation: The parsing process for program name 

has failed in mid-execution at the time indicated. 



User response: Investigate the specific cause from 

other reported error messages. Correct the syntax; 


Module: 

AES2006W 

Explanation: 



analysis. 

Module: 

AES2007E 


Option 'name' is invalid. It is ignored. 

The start parameter shown is wrong. 


Correct the error; reattempt the 


Analysis target 'filename' is invalid. 

Explanation: There is an error in the specification of 

the source file that is the analysis target in the start 

parameter of the analysis program. 



User response: Correct the specification of the target; 


Module: 

AES2008E 


Open error for file 'filename'. 

Explanation: The file shown cannot be opened. 

Possible causes are: 

v The file does not exist. 

v The scanner does not have proper authority to access 

the file. 

v There is a network problem. 




analysis. 

Module: 

AES2009E 

Correct the cause; reattempt the 


Read error for file 'filename'. 

Explanation: An error occurred while reading the file 

shown. This error may be caused by network problems. 




analysis. 

Module: 

AES2010W 

Correct the cause; reattempt the 


Read error for the analysis option file. 

Explanation: 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 Rational Asset Analyzer. 




analysis 

Module: 

AES2011E 

Correct the problem; reattempt the 


Invalid language level for file 'filename'. 

Explanation: Either a language level for the extension 

of the file shown has not been specified or the 

specification is wrong. 




the analysis. 

Module: 

AES2020W 

Correct the analysis option; reattempt 


Read error for the interface information 

file of program 'filename'. This file is 

ignored. 

Explanation: An error occurred while reading the 

interface information file of the program shown. This 

error may be caused by a network problem. 




analysis 

Module: 





AES2021E 

Explanation: 

found. 

There is no analysis target 'filename'. 

The source file shown could not be 



User response: Correct the source program 

specification; reattempt the analysis. 

Module: 

AES2022E 


Write error for the interface information 

file of program 'name'. 

Explanation: An error occurred in writing the 

interface information file of program name to a file. 

Possible causes of this error include: 

v The application does not have proper authority to 

access the directory where analysis results are 

written. 

v A disk is full. 





analysis. 

Module: 

AES2023E 



Write error for the detailed information 


Explanation: An error has occurred in writing the 

detailed information of program name to a file. Possible 

causes of this error include: 



written. 






analysis. 

Module: 

AES2024E 



Read error for the detailed information 


Explanation: An error has occurred while reading the 

detailed information of program name from a file. 

Possible causes of this error include: 



written. 


v 

There is a network problem. 




analysis. 

Module: 

AES2025E 



Write error for the analysis summary 


Explanation: An error has occurred while writing the 

analysis summary information of program name to a 

file. Possible causes of this error include: 



written. 






analysis. 

Module: 

AES2026E 



Read error for the analysis summary 

information file of program 'name'. 


analysis summary information of program name from a 




written. 






analysis. 

Module: 

AES2027E 



Fail creation of target directory 'name'. 

Explanation: The directory specified could not be 

created. Possible causes of this error include: 

v The directory name is incorrect. 


create the directory. 


This error occurs only on the Windows version of 

Rational Asset Analyzer. 






analysis. 

Module: 

AES2029E 



Read error for the list of analyzed 

programs in 'name'. 


program list information of the program shown from a 



read the file. 





analysis. 

Module: 

AES2031E 



Write error for the analysis option file 

into directory 'name'. 


analysis option file. Possible causes of this error 

include: 


create the file. 





analysis. 

Module: 

AES2032E 



The entry name of program 'name1' is 

the same as the entry name of program 

'name2'. 

Explanation: The entry name defined in program 

name1 is also defined in program name2. This error 

occurs only on the Windows version of Rational Asset 

Analyzer. 

System action: The analysis result of program name1 

is cancelled because it is overwritten. 


groups. 

Module: 

Analyze the two programs as separate 


AES2034E 

Fail creation of import file directory 

'name'. 

Explanation: An error has occurred while creating the 

import file directory. Possible causes of this error 

include: 


create the directory. 


This error occurs only on the Windows version of 





analysis. 

Module: 

AES2035E 



Write error for the list of analyzed 

programs in 'directory'. 


list of programs. Possible causes of this error include: 


create files in the directory. 





analysis. 

Module: 

AES2036E 



Write error for import file of 'filename'. 


import file. This error may have occurred because the 

application does not have proper authority to access 

the directory. 




analysis. 

Module: 

AES2039E 



Option '%1' is too long. 

Explanation: Scanner encountered a long internal 

option. It includes the cases of a long path string for 

such as a target program, copy/include members. 


Scanner would skip the analysis. 

User response: When the problem was caused by a 

long path string, shorten it if possible. Otherwise, 

contact IBM Software Support. 

Module: 



DMH1000I • DMH1103I 

Messages begining with DMH 

DMH1000I . 

Explanation: This message provides white space when 

a series of messages is generated, allowing the 

messages to be more easily read. 




None 

Module: BMS macro definition scanner, File 

classification scanner, Impact analysis, JCL analyzer 

DMH1001I 

programname (compiledate compiletime) 

Explanation: This message is the first in a series of six 

that report a copyright notice. 



Module: 

DMH1002I 


None 

BMS macro definition scanner, JCL analyzer 

Licensed Materials - Property of IBM 

Explanation: This message is the second in a series of 

six that report a copyright notice. 



Module: 

DMH1003I 


None 


Copyright IBM Corp. year 

Explanation: 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). 



Module: 

DMH1004I 


None 


US Government Users Restricted Rights 

- Use, duplication 

Explanation: This message is the forth in a series of 




Module: 

DMH1005I 


None 


or disclosure restricted by GSA ADP 

Schedule Contract 

Explanation: This message is the fifth in a series of six 

that report a copyright notice. 




Module: 

DMH1006I 

None 


with IBM Corporation. 

Explanation: This message is the sixth in a series of 




Module: 

DMH1010E 


None 


DMH_ASSERT failure on line number of 

name compiled compiledate compiletime 

Explanation: This message occurs in debug mode 

only. The string pointer is null, and the job has stopped 

due to an assert error. 



Module: 

DMH1100I 

Explanation: 



Module: 

DMH1101I 


JCL analyzer 


*** Opened File List 

This message is an informational banner. 


None 

JCL analyzer 

parameter 

Explanation: 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. 



Module: 

DMH1102I 

Explanation: 



Module: 

DMH1103I 

Explanation: 



None 

Impact analysis, JCL analyzer 

*** End Opened File List 



None 

JCL analyzer 

*** Job Search List 





User response: None 

Module: JCL analyzer 

DMH1104I *** End Job Search List 

Explanation: This message is an informational banner. 

System action: The system is functioning normally. 



DMH1105I *** Default Search List 





DMH1106I *** End Default Search List 





DMH1107I *** Referenced List 





DMH1108I statusdata1 statusdata2 statusdata3 

Explanation: This message is informational status 

data. 



Module: Analysis queue processor, DB2 ® catalog 

scanner 

DMH1109I *** End Referenced List 





DMH1110I ----- SQL error report ----- 

Explanation: 



Module: 

DMH1111I 

Explanation: 




None 

Impact analysis 

ERROR occurred: CONNECT TO 

DATABASE. 

Connect to database failed. 


User response: Verify the database name, user ID and 

password are correct; try the operation again. 

Module: DB2 catalog scanner, Impact analysis, Import 

record loader, Queue processor 

DMH1112I 

ERROR occurred: CONNECT RESET. 

Explanation: Following disconnect from the database, 

a CONNECT RESET request failed. 



User response: Locate message DMH1101I for 

SQLSTATE information. 

Module: 

DMH1113I 


SQLCODE: returncode 

Explanation: This message provides a return code 

from DB2 following an SQL operation. 

SQLCODE values can be the following: 

0 The statement was successful. 

a positive integer 

The statement was successful, but with an 

exception condition. 

greater than 100 

Row not found or end of data. 

a negative integer 

A serious error was detected. 



User response: Refer to the DB2/SQL messages and 

codes reference for more information. 

Module: 


DMH1114I --- end SQL error report --- 

Explanation: 



Module: 



None 



DMH1115W • DMH1205E 

DMH1115W WARNING - CONTINUING 

PROGRAM WITH WARNINGS! 

Explanation: Unexpected error messages were 

returned from DB2; processing will continue, however. 



User response: 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. 

Module: DB2 catalog scanner, Impact analysis, Import 

record loader, Queue processor 

DMH1116I 

CONNECTING TO DATABASE: name 

Explanation: This is an informational message 

indicating CONNECT TO DATABASE name has been 

issued. 



Module: 

DMH1117I 


None 


CONNECTED TO DATABASE: name 


indicating CONNECT TO DATABASE name was 

successful. 



Module: 

DMH1118I 


None 


DISCONNECTING FROM DATABASE 


indicating CONNECT RESET has been issued. 



Module: 

DMH1119I 

Explanation: 

status data. 



None 


data 

This message provides informational 


User response: None. When paired with message 

DMH2114, this message provides additional detail data. 

Module: 

DB2 catalog scanner, Import record loader 

DMH1200I 

Has been identified as: filetype 

Explanation: 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. 



Module: 

DMH1201I 


None 

File classification scanner 

Container=name File=name 

Explanation: This message provides informational 

status indicating the container and file currently being 

processed. 



Module: 


None 


DMH1202W Has not been identified, classified as: 

filetype 

Explanation: 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). 



User response: 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. 

Module: 

DMH1204E 

Explanation: 

application. 



Module: 

DMH1205E 

Explanation: 

application. 



Hash table cannot be initialized 





Internal error, invalid record passed 




DMH1206E • DMH1217W 


Module: 

DMH1206E 



cannot open the source file 

Explanation: The file cannot be opened. Possible 

causes are: 


v The user does not have proper authority to access 

the file. 

v Source control/change management tool access is 

unavailable. 



User response: Verify and correct the cause; try the 

operation again. 

Module: 

DMH1209E 

Explanation: 

application. 



Module: 

DMH1210E 

Explanation: 

application. 



Module: 

DMH1211E 

Explanation: 

application. 




Internal error, wrong feature state 





Internal error, wrong language state 





Internal error, wrong token state 





classification scanner 

DMH1212E 

Explanation: 

application. 



Module: 

Bad weight ID in reserve word table 


Processing is stopped. 



DMH1213E 

Explanation: 

application. 



Module: 

DMH1214E 

Explanation: 

application. 



Module: 

DMH1216E 

Bad reserve word type in reserve word 

table 





cannot add item to hash table 





cannot open file DD:ATTRBOUT 

Explanation: The file cannot be opened. The DD 

statement for ATTRBOUT is a temporary data set 

established to hold Rational Asset Analyzer import 

records. Possible causes are: 

v The user does not have proper authority to allocate 

the file. 

v There is a system storage problem. 






classification scanner, IMS DBD scanner, IMS PSB 

scanner 

DMH1217W Line number, column number - Invalid 

character encountered: x'hexcode' 

Explanation: This message occurs in debug mode 

only. While reading the input file, Rational 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. 




again. 

Module: 

Correct the file; try the operation 



DMH1300E • DMH1307E 

DMH1300E 

Container name exceeds maximum 

Explanation: Rational Asset Analyzer supports the 

following container name maximum lengths: MVS = 

44, workstation = 254. 



User response: Reduce the length of the container 

name; try the operation again. 

Module: 

DMH1301E 

JCL analyzer 

File name exceeds maximum 


following file name length maximums: MVS = 10, 

workstation = 254. 



User response: Reduce the length of the file name; try 

the operation again. 

Module: 

DMH1302E 

JCL analyzer 

Open failure on DD:JCLLIB, specifies 

default concatenation list 

Explanation: No JCLLIB statement was specified in 

the JCL, or the data set specified for JCL INCLUDEs or 

procedures could not be opened. Rational Asset 

Analyzer will use its own default JCLLIB concatenation 

list (for example, DD DUMMY). 


Processing continues. 

User response: 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 Rational Asset Analyzer user 

data sets specified at the time of installation. Contact 

your Rational Asset Analyzer administrator. 

Module: 

DMH1303E 

JCL analyzer 

Number of containers exceeds default 

concatenation limit 

Explanation: For JCL scanner, the Rational Asset 

Analyzer container concatenation maximum is 32. The 

number of containers specified for JCLLIB DD * 

exceeds this limit. For COBOL/PLI proprietary scanner, 

the maximum byte length of a total concatenation path 

string (including path delimiters and default 

concatenation path strings) is 1023. For COBOL/PLI 

compiler-based scanner, the maximum byte length of 

the concatenation path string (including path delimiters 

and default concatenation path strings) is 2047. 


Scanning terminates for the current 


User response: Reduce the number of containers; try 


Module: 

DMH1304E 

JCL scanner, COBOL/PLI scanners 

Container name read from file too long 


following container name maximum lengths: MVS = 44, 




User response: Reduce the length of the container 


Module: 

DMH1305E 

JCL analyzer 

Number of containers on JCLLIB 

exceeds limit 

Explanation: The Rational Asset Analyzer container 

concatenation maximum is 32. The number of 

containers specified in the JCLLIB ORDER= statement 

cannot exceed this limit. 



User response: Reduce the number of containers listed 

in the JCLLIB ORDER= statement; try the operation 

again. 

Module: 

DMH1306E 

JCL analyzer 

Attempt to nest source too deeply 

Explanation: The Rational Asset Analyzer nested 

source file limit is 15. The processing of INCLUDE 

statements has exceeded this limit. 



User response: Reduce the nesting level; try the 


Module: 

DMH1307E 

JCL analyzer 

Number of source files used exceeds 

limit 

Explanation: The Rational Asset Analyzer include and 

procedure source file maximum is 200. The number of 

unique referenced source files cannot exceed this limit. 



User response: Reduce the number of unique 

referenced source files; try the operation again. 

Module: 

JCL analyzer 



DMH1308E 

File name for INCLUDE or external 

PROC name is too long 


following file name length maximums: MVS = 10, 




User response: Reduce the length of the file name; try 


Module: 

DMH1309E 

JCL analyzer 

INCLUDE file or cataloged PROC not 

found: name 

Explanation: The JCL analyzer 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. 


The scanner continues processing. 

User response: Verify the location of the named 

INCLUDE or PROC and ensure its container is 

represented in a concatenation set known to Rational 

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. 

Module: 

DMH1310E 

JCL analyzer 

INCLUDE file was not found: name 

Explanation: The COBOL or PL/I scanner detected a 

reference to a COPY, %INCLUDE, ++INCLUDE, or 

-INC name that was not found by searching the 

concatenation set of containers, if specified, or the user 

concatenation set of containers, if specified. 

System action: The scanner may terminate the 

analysis for the asset, but continues processing. 

User response: Verify the location of the named 

COPY, INCLUDE, ++INLCUDE, or -INC and ensure its 

container is represented in a concatenation set known 

to Rational Asset Analyzer. 

Module: 

DMH1311E 

COBOL and PL/I scanner 

Container Name parameter is not valid 

Explanation: The container name was not found in the 

input parameters, or it is an invalid container name. 




Module: 



DMH1312E 

File Name parameter is not valid 

Explanation: The file name was not found in the input 

parameters, or it is an invalid file name. 




Module: 

DMH1313E 



Open failure on DD:INFILE, specifies 

JCL file 

Explanation: The container and member specified for 

the INFILE DD could not be opened. Possible causes 

are: 

v The container or file does not exist. 


the container. 





Module: 

DMH1314E 

JCL analyzer 

Comment continuation flag was not 

followed by valid card 

Explanation: 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. 



User response: Verify the JCL comment statement is 

continued correctly. To continue a comment: 

v Interrupt the comment at a convenient place before 

column 72, up to and including column 71. 

v Code a nonblank character in column 72. 

v Code // in columns 1 and 2. 

v Code a blank character in column 3. 

v Continue the comments field beginning in any 

column after column 3. 

Verify and correct the syntax; try the operation again. 

Module: 

DMH1315E 

JCL analyzer 

End of file after comment continuation 

flag 

Explanation: An expected continuation of comment 

was not found. The last statement in the JCL contained 

a comment continuation flag. 





User response: Verify the JCL comment statement 

should be continued. To continue a comment: 

v Interrupt the comment at a convenient place before 

column 72, up to and including column 71. 

v Code a nonblank character in column 72. 

v Code // in columns 1 and 2. 


v Continue the comments field beginning in any 

column after column 3. 


Module: 

DMH1316E 

JCL analyzer 

Expected parameter continuation not 

found 

Explanation: 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. 



User response: Verify the parameter field is continued 

correctly. To continue a parameter field: 

v Interrupt the parameter field after a complete 

parameter or subparameter, including the comma 

that follows it, at or before column 71. 

v Code // in columns 1 and 2 of the following 

statement. 


v Continue the parameter beginning in any column 

from 4 through 16. 


Module: 

DMH1317E 

JCL analyzer 

Expected parameter continuation not 

found by col 16 

Explanation: 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. 




correctly. To continue a parameter field: 

v Interrupt the parameter field after a complete 

parameter or subparameter, including the comma 

that follows it, at or before column 71. 


statement. 


v Continue the parameter beginning in any column 

from 4 through 16. 


Module: 

DMH1318E 

JCL analyzer 

Record for continuation of quoted parm 

too short 

Explanation: 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. 




correctly. To continue a parameter field enclosed in 

apostrophes: 

v Extend the parameter to column 71. Do not code an 

apostrophe in column 71 of a JCL statement that is 

continued. 


statement. 

v Continue the parameter beginning in column 16 of 

the following statement even if this splits the 

parameter. Trailing blanks or commas within the 

apostrophes do not indicate a continued statement. 


Module: 

DMH1319E 

JCL analyzer 

DLM= delimiter not two characters 

Explanation: The DLM=delimiter did not specify the 

required two characters to indicate the end of this data 

set in the input stream. 



User response: 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. 

Module: 

JCL analyzer 

DMH1327E DLM= parameter on DD statement < 2 

chars 


required two characters to indicate the end of this data 

set in the input stream. 




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. 

Module: 

JCL analyzer 

DMH1328W DLM= contains & not followed by & 


required two ampersands. 




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. 

Module: 

DMH1334E 

JCL analyzer 

First statement was not JOB card 

Explanation: The JOB statement is expected to be the 

first statement to mark the beginning of a job. 



User response: Verify and correct the syntax; try the 


Module: 

DMH1336E 

JCL analyzer 

Illegal statement found in PROC 

definition 

Explanation: 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: 

For a cataloged procedure: 

//[name] PROC [parameter [comments]] 

//[name] PROC 

For an in-stream procedure: 

//name PROC [parameter [comments]] 

//name PROC 



User response: Verify and correct the syntax of the 

procedure; try the operation again. 

Module: 

JCL analyzer 

DMH1340E 

Illegal statement within include group 

Explanation: The scanner encountered unexpected 

syntax while processing an include group. Include 

groups cannot contain the following JCL statements: 

v JOB statements 

v PROC and PEND statements 

v JCLLIB statements 

v JES2 and JES3 statements and commands 

v DD * and DD DATA statements 




include group; try the operation again. 

Module: 

DMH1342E 

JCL analyzer 

PEND without matching procedure 

invocation 

Explanation: A PEND statement was identified and no 

corresponding procedure invocation was found. 



User response: Locate any missing files; try the 

operation again. Otherwise, verify and correct the 

syntax; try the operation again. 

Module: 

DMH1350E 

JCL analyzer 

Includes nested too deeply 

Explanation: The Rational Asset Analyzer include 

nesting maximum is 15. The nesting of INCLUDEs 

exceeds this limit. 



User response: Reduce the include nesting; try the 


Module: 

DMH1355E 

JCL analyzer 

Symbolic name too long 

Explanation: The Rational Asset Analyzer JCL name 

length maximum is 8. The symbolic name fields must 

not exceed this limit. 



User response: Reduce the length of the symbolic 


Module: 

JCL analyzer 



DMH1356E 

Multiple JOB cards 

Explanation: More than one JOB card was detected. 

Rational Asset Analyzer does not support multiple JOB 

cards; only a single job per file is allowed. 



User response: Split multiple (nested) JOBs into single 

files; try the operation again. 

Module: 

DMH1359E 

JCL analyzer 

Too many parms 

Explanation: The Rational Asset Analyzer parameter 

maximum is 400. The number of JCL parameters 

passed to a step exceeded this limit. 



User response: Reduce the number of parameters; try 


Module: 

DMH1360E 

JCL analyzer 

Parenthesis and apostrophe nesting 

exceeded 

Explanation: The Rational Asset Analyzer nesting 

maximum is 20. You can nest the delimiters up to the 

maximum. 



User response: Reduce the delimiter nesting level; try 


Module: 

DMH1363E 

JCL analyzer 

If nesting exceeds limit 

Explanation: The Rational 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. 



User response: Reduce the IF nesting level; try the 


Module: 

JCL analyzer 

DMH1365E 

ENDIF without IF 

Explanation: 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. 



User response: Verify and correct the 

IF/THEN/ELSE/ENDIF syntax; try the operation 

again. 

Module: 

DMH1367E 

JCL analyzer 

Keyword parameter or SET statement 

missing = 

Explanation: 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: 




SET statement parameter(s); try the operation again. 

Module: 

DMH1368E 

JCL analyzer 

JCLLIB missing ORDER= 

Explanation: 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: 




JCLLIB statement; try the operation again. 

Module: 

DMH1371E 

JCL analyzer 

EXEC card has null first parameter 

Explanation: 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: 






EXEC statement; try the operation again. 

Module: 

DMH1372E 

JCL analyzer 

EXEC card PGM= has null value 

Explanation: 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: 

v PGM= 

– {program_name} 

– {*.stepname.ddname} 

– {*.stepname.procstepname.ddname} 

– {JCLTEST} 

– {JSTTEST} 




PGM= parameter; try the operation again. 

Module: 

DMH1373E 

JCL analyzer 

DD concatenation without DD 

statement 

Explanation: The scanner was processing a DD 

concatenation and found no corresponding job step, 

JOBLIB or JOBCAT. 





Module: 

DMH1375E 

JCL analyzer 

Missing JOB card 

Explanation: 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). 



User response: Verify and correct the JCL to include a 

JOB card; try the operation again. 

Module: 

JCL analyzer 

DMH1376E 

Keyword parameter or SET statement 

missing = 

Explanation: The JCL analyzer detected a keyword or 

SET statement without a required equal sign. 



Module: 

DMH1377E 

The analysis scan is terminated. 

JCL analyzer 

Correct the invalid JCL and reanalyze. 

Multiple JOBCAT statements 

Explanation: The scanner supports one JOBCAT per 

job, appearing after the JOB statement, following the 

JOBLIB, if coded, and before the first EXEC. 



User response: Verify and correct the JCL to use a 

single JOBCAT; try the operation again. 

Module: 

DMH1378E 

JCL analyzer 

Multiple JOBLIB statements 

Explanation: The scanner supports one JOBLIB per 

job, appearing after the JOB statement, before the 

JOBCAT, if coded, and before the first EXEC. 



User response: Verify and correct the JCL to utilize a 

single JOBLIB; try the operation again. 

Module: 

DMH1380E 

JCL analyzer 

Illegal statement in procedure 

Explanation: Rational Asset Analyzer encountered an 

unknown statement while processing the syntax of the 

procedure. Syntax of the PROC statement is as follows: 

For a cataloged procedure: 

//[name] PROC [parameter [comments]] 

//[name] PROC 

For an in-stream procedure: 

//name PROC [parameter [comments]] 

//name PROC 




procedure; try the operation again. 

Module: 

JCL analyzer 



DMH1381E 

PROC nesting exceeded limit 

Explanation: The Rational 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. 





Module: 

DMH1382E 

Explanation: 

application. 

JCL analyzer 

Query empty context stack 





Module: 

DMH1383E 

Explanation: 

application. 

JCL analyzer 


PROC stack underflow 





Module: 

DMH1384I 

Explanation: 



Module: 

DMH1385I 

Explanation: 



Module: 

DMH1386I 

Explanation: 


JCL analyzer 


File Opened 



None 

JCL analyzer 

File Closed 



None 

JCL analyzer 

Read: 




Module: 

DMH1391I 

None 

JCL analyzer 

Statement: %1 %2 %3 statement 

Explanation: This message provides the status of a 

JCL statement being processed. 



Module: 


None 

JCL analyzer 

DMH1392I Substitution: %1 %2 %3 %4 


JCL statement being substituted. 



Module: 

DMH1393E 


None 

JCL analyzer 

Too many steps in job 

Explanation: The Rational 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. 



User response: Reduce the number of steps in the job; 

try the operation again. 

Module: 

DMH1395E 

JCL analyzer 

StepName.DDName too long 

Explanation: The JCL analyzer detected a step name 

syntax that exceeded allowed length. 



Module: 

DMH1396E 


JCL analyzer 

Correct the invalid JCL and reanalyze. 

Could not find step named on override 

DD 

Explanation: An override statement explicitly named a 

step that was not found in the expanded procedure. 



User response: Locate any missing files; try the 

operation again. Otherwise, verify and correct the 

syntax; try the operation again. 


DMH1397E • DMH1410I 

Module: 

DMH1397E 

JCL analyzer 

Could not add DD; no PGM= steps 

found 

Explanation: 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. 





Module: 

DMH1398I 

JCL analyzer 

Added to Proc: %1 %2 %3 statement 


JCL statement; a DD statement was added. 



Module: 

DMH1399I 


None 

JCL analyzer 

Override Proc: %1 %2 %3 statement 


JCL statement; a DD statement was overridden. 



Module: 


None 

JCL analyzer 

DMH1400E Fatal Error: %1 %2 %3 

Explanation: This message reports a fatal error while 

processing a JCL statement. 




Module: 

DMH1401S 

JCL analyzer 


Fatal DB2 Error: SQLCODE 

Explanation: This message reports a return value from 

DB2 following an SQL operation. 



User response: Refer to the DB2/SQL messages and 

codes reference. 

Module: 


DMH1402E 

Statement label is too long 

Explanation: The Rational Asset Analyzer JCL 

statement label length maximum is 18 (for example, 

StepName.DDNameXX). 



User response: Reduce the length of the statement 

label; try the operation again. 

Module: 

DMH1403E 

JCL analyzer 

Statement parameter text is too long 

Explanation: The Rational Asset Analyzer JCL 

statement parameter length maximum is 8192. The 

parameter text length exceeds this limit. 



User response: Reduce the length of the statement 

parameter text string; try the operation again. 

Module: 

DMH1406E 

JCL analyzer 

Instream PROC has no name 

Explanation: An in-stream procedure definition has no 

name in its PROC statement. 





Module: 

DMH1407E 

JCL analyzer 

Instream PROC PEND not found before 

end of file 

Explanation: 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. 





Module: 

DMH1410I 

JCL analyzer 

Input parameters: 

Explanation: This message reports the status of input 

parameters being processed. 



Module: 


None 

Impact analysis, JCL analyzer 



DMH1413E Internal error 

Explanation: This is an internal error of the 

application. 



User response: Contact IBM Software Support. 


DMH1419E 

Could not create unique Site Id 

Explanation: Rational Asset Analyzer could not 

generate a unique ID for the site. The site is not 

inserted in the DMH_SITE table. 



Module: 



DB2 catalog scanner, Import record loader 

DMH1414E 

Could not create unique Container ID 


generate a unique ID for the container. The container is 

not inserted in the DMH_CONTAINER table. 

System action: The loader skips the current asset and 



Module: 

DMH1415E 


Import record loader 

Could not create unique file ID 


generate a unique ID for the file. The file is not inserted 

in the DMH_FILE table. 




Module: 

DMH1417E 



Data set name is too long 


following data set name maximum lengths: MVS = 58, 

workstation = 510. The data set name exceeds this 

limit. 



User response: Reduce the length of the data set 


Module: 

DMH1418E 


Could not create unique run unit ID 


generate a unique ID for the run unit. The run unit is 

not inserted in the DMH_RUN_UNIT table. 




Module: 



DMH1420E 

Explanation: 

application. 



Module: 

Error reading component list for name 




PDS Member List Processing 

DMH1421W Could not process INCLUDE statement 

Explanation: The JCL analyzer has encountered an 

INCLUDE statement but was unable to detect the 

statement's MEMBER= phrase. This statement has two 

valid formats: 

v 

v 

System action: The JCL analyzer reports this message 

and ignores the INCLUDE statement. 

User response: 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 IBM Software Support. 

Module: 

DMH1442E 

Explanation: 

application. 



Module: 

JCL analyzer - DMH4000 

Internal error 



JCL analyzer 


DMH1443W Could not substitute DB2 run unit for 

SYSTSIN * 

Explanation: 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 cannot be read, no run unit 

name substitution is available. 




None 


DMH1444W • DMH1452W 

Module: 

JCL analyzer 

Module: 

JCL analyzer 

DMH1444W Could not open filename 

Explanation: 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. 



User response: 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. 

Module: 

JCL analyzer 

DMH1445W Could not find OUTPUT spec named 

name 

Explanation: The JCL analyzer detected output 

parameters associated with a SYSOUT DD statement 

(for example, OUTPUT=(*.name)), but could not find 

the associated //name output statement in the JCL to 

capture the parameters. 

System action: The JCL analyzer ignores the 

OUTPUT= parameter specification associated with the 

SYSOUT DD statement and continues processing. 


again. 

Module: 

JCL analyzer 

Correct the JCL; try the operation 

DMH1448W Could not read DD DDITV02 


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. 



Module: 


None 

JCL analyzer 

DMH1449W Could not substitute DB2 run unit for 

DSNMVT01 



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. 



Module: 


None 

JCL analyzer 

DMH1446E 

Could not create unique data set ID 

name 


generate a unique ID for the data set. The data set was 

not inserted in the DMH_DATASET table. 




Module: 

JCL analyzer 


DMH1447W Could not open DD DDITV02 for 

DB2/IMS 



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. 




None 

DMH1450E 

Explanation: 

application. 



Module: 

Memory allocation failure 




Analysis queue processor, JCL analyzer 

DMH1452W Could not find IMS program name 



to identify the run unit. No PARM= statement was 

found. DFSRRC00 is the run unit assigned to the job 

step. 



Module: 


None 

JCL analyzer 



DMH1453W Could not find IMS PSB name name 



to identify the run unit and PSB name. The scanner did 

not find a PSB name coded. 



Module: 

DMH1462E 

Explanation: 

application. 


None 

JCL analyzer 

Internal error 





Module: 

DMH1463E 

JCL analyzer 


Override not proceeded by named DD 

stmt 

Explanation: A JCL override statement was found 

which referred to a non-existent DD name. 



Module: 


JCL analyzer 

Correct invalid JCL and reanalyze. 

DMH1470I Warning found in %1 at line %2 

Explanation: This message documents for the user the 

location in the JCL source the following WARNING 

message was found. 



Module: 

The analysis scan continues. 

None 

JCL analyzer 

DMH1471I Error found in %1 at line %2 

Explanation: This message documents for the user the 

location in the JCL source the following ERROR 

message was found. 



Module: 

DMH1530E 

The analysis scan continues. 

None 

JCL analyzer 

MEMB record is missing 

Explanation: The loader did not find the required 

MEMB import record for processing a file. 




Module: 

DMH1546E 



Invalid UACP Reference to Ambiguous 

Data Element: name 

Explanation: DB2 returned an -811 SQLCODE when 

attempting to locate the data element. 



Module: 

DMH1547E 




MAPS record is missing 

Explanation: The loader did not find the required 

MAPS import record for processing a BMS mapset. 




Module: 

DMH1548E 



Could not create unique Mapset Id 


generate a unique ID for the BMS mapset. The mapset 

is not inserted in the DMH_MAPSET table. 




Module: 

DMH1549E 



Could not create unique Map Id 


generate a unique ID for the BMS map. The map is not 

inserted in the DMH_MAP table. 




Module: 

DMH1610E 



Cannot open Member List file DD 

MEMLIST 

Explanation: The loader could not open the file 

specified for MEMLIST DD. 



Module: 






DMH1617E 

Cannot open the source file 

Explanation: The file cannot be opened. Possible 

causes are: 



the file. 

v Source control/change management tool access is 

unavailable. 





Module: 

DMH1660E 

BMS macro definition scanner 

Insertion to DMH_CHANGE_IMPACT 

failed 

Explanation: Impact analysis was unable to insert a 

row into the DMH_CHANGE_IMPACT table. 



Module: 

DMH1663E 




Cannot open join cursor on 

RD_DATA_RECORD, 

RD_DATA_STORE 

Explanation: An OPEN request for cursor DMHD221 

failed. This is an internal error of the application. 



Module: 

DMH1667E 



Impact analysis, IMS analysis 

Cannot add record to linked list 

Explanation: Impact analysis was unable to record the 

impact. This is an internal error of the application. 



Module: 

DMH1668E 




Cannot open cursor on 

RD_FORMAL_PARM 

Explanation: An OPEN request for cursor 

DMHD223D failed. This is an internal error of the 

application. 



Module: 




DMH1669E 

Cannot open cursor on 

RD_ACTUAL_PARM 

Explanation: An OPEN request for cursor DMHD223 




Module: 

DMH1671E 




Update to DMH_CHANGE_FOCUS 

failed 

Explanation: Impact analysis was unable to update a 

row in the DMH_CHANGE_FOCUS table. 



Module: 

DMH1680E 




Cannot open file: name 

Explanation: An open failed for the FILELIST DD file 

(file classification scanner) or the INFILE DD file 

(import record loader). 



Module: 

loader 

DMH1702E 



File classification scanner, Import record 

Unable to create XREF name list, XREF 

IDs are sequential 

Explanation: The loader detected an inconsistency 

while processing the sequence number for a control 

transfer. 




Module: 



DMH1703W Truncated value for database: value 

Explanation: Processing detected a character string 

value was longer than expected; value was shortened as 

required for database processing (for example, 

UPDATE, INSERT). 




None 

Module: BMS macro definition scanner, Impact 

analysis, Import record loader 



DMH1708E 

Missing REGION card 

Explanation: 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. 



Module: 

DMH1713E 




Cannot generate unique identifier for 

region 


generate a unique ID for the region. The region is not 

inserted in the DMH_ONLINE_REGION table. 




Module: 

DMH1714E 




transaction 


generate a unique ID for the transaction. The 

transaction is not inserted in the 

DMH_TRANSACTION table. 




Module: 

DMH1715E 




CICS pipeline 


generate a unique ID for the pipeline. The pipeline 

asset is not inserted in the DMH_CICS_PIPELINE table. 




Module: 

DMH1716E 




CICS Web service 


generate a unique ID for the Web service. The Web 

service asset is not inserted in the 

DMH_CICS_WEBSERVICE table. 





Module: 

DMH1717E 



CICS URI map 


generate a unique ID for the URI map. The URI map 

asset is not inserted in the DMH_CICS_URIMAP table. 




Module: 

DMH1720S 



Unable to Insert Compile Unit 

Explanation: The loader was unable to insert a row 

into the DMH_COMPILE_UNIT table. 




Module: 

DMH1721I 



Did not understand passed parm: 

Explanation: The scan was started with a parameter it 

did not recognize, which is reported on the following 

message. 

System action: The parameter is reported, ignored, 

and the analysis scan continues. 

User response: Review the parameters entered, 

remove or correct the indicated parameter, and 

resubmit the analysis scan. 


classification scanner, Import record loader, JCL 

analyzer 

DMH1722S 

Unable to Update Compile Unit 

Explanation: The loader was unable to update a row 

in the DMH_COMPILE_UNIT table. 




Module: 



DMH1730I parm = %1 

Explanation: This message reports the parameter 

referred to by the DMH1721I message(s). 

System action: The parameter is reported, ignored, 

and the analysis scan continues. 


Review the parameters entered, 



remove or correct the indicated parameter, and 

resubmit the analysis scan. 

Module: 

Import file loader 


classification scanner, JCL analyzer 

DMH1731I 

Explanation: 



Module: 

DMH1732E 

DMH0731 entry 



None 


Container Type missing. Container types 

must be configured prior to scanning. 

Explanation: The loader found no matching container 

type in the DMH_CONT_TEMPLATE table. 


continues. 


administrator. 

Module: 

Processing skips the current record and 

Contact your Rational Asset Analyzer 


DMH1733W Container type does not match 

configured type. Configured container 

name is used. 

Explanation: The loader detected a mismatch between 

the input container type and the container type 

available in the DMH_CONT_TEMPLATE table. 



administrator. 

Module: 


Contact your Rational Asset Analyzer 


DMH1739W Unable to insert SQL component: 

sqlcomponent record 

Explanation: The loader could not insert a row for the 

referenced SQL component type. 

sqlcomponent types: 

v SQLC = column, not inserted in the 

DMH_SQL_COLUMN table 

v SQLCU = cursor, not inserted in the 

DMH_SQL_CURSOR table 

v SQLT = table, not inserted in the DMH_SQL_TABLE 

table 

v SQLP = stored procedure, not inserted in the 

DMH_SQL_PROC table 


continues. 




DMH1760E 

Unable to open cursor: cursorname 

Explanation: An OPEN request for cursor cursorname 




Module: 



Analysis queue processor 

DMH1761I Start processing queue type %1. %2. 

Explanation: The postprocessor has found a 

DMH_ANALYSIS_QUEUE row with an 

ANALYSIS_TYPE_CD of %1. 



Module: 


None 


DMH1762I Queue type=%1 RC=%2 for %3 %4. 

Explanation: The specified queue type processing 

completed for the asset and had a return code of %2. 



User response: If the return code was nonzero, use the 

RDPRINT output to determine if any correction is 

needed for the specified asset. 

Module: 

DMH1763I 


Stop processing queue type %1. Highest 

RC=%2. 

Explanation: The postprocessor has completed 

processing of the current queue type. The highest 

return code for the assets processed is %2. 



User response: If the highest return code is nonzero, 

there will also be one or more DMH1762I messages 

preceding it with a nonzero return code. Use the 

RDPRINT output to determine if any correction is 

needed for the assets with nonzero return codes. 

Module: 

DMH1764I 


The postprocessor stopped unexpectedly. 

See the RDPRINT output for details. 

Explanation: The postprocessor has encountered a 

severe error and cannot continue. 


The postprocessor terminates. 

User response: Check the RDPRINT output for details 

that caused the postprocessor to terminate. 

Module: 




DMH1765E 

Queue out of sync for call resolution 

CU: compunitid XFER: name 

Explanation: A postprocessing queue entry to resolve 

dynamic references contains an internal CALL 

statement identifier that is invalid. 

System action: The postprocessing queue entry is 

deleted, and postprocessing continues with next queue 

entry. 

User response: Contact IBM Software Support. Retain 

the postprocessing job output. 

Module: 

DMH1766E 


Queue out of sync Literal not found 

literalname 

Explanation: A postprocessing queue entry to resolve 

dynamic references contains an internal LITERAL 

identifier that is invalid. 


deleted, and postprocessing continues with next queue 

entry. 

User response: Contact IBM Software Ssupport. Retain 

the postprocessing job output. 

Module: 

DMH1767I 


The postprocessor completed. Highest 

RC=%1. 

Explanation: The postprocessor completed normally 

and the highest return code encountered for any 

processing was %1. 


Processing completes. 

User response: If the highest return code is nonzero, 

there will also be one or more DMH1762I and 

DMH1763I messages preceding it with a nonzero return 

code. Use the RDPRINT output to determine if any 

correction is needed for the assets with nonzero return 

codes. 

Module: 


DMH1769W Dynamic Concatenation Set Names limit 

reach. No new Concatenation sets can 

be generated. 

Explanation: Rational 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. 



User response: Verify the location of any missing 

COPY or INCLUDE files, as reported on the "File 

details" page, and ensure their owning container(s) are 


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. 

Module: 

DMH1770E 

Explanation: 

application. 



Module: 


Application chain longer than request 

allows - Internal restriction (DMH6006) 

This is an internal error or the 




DMH1773W Unable to create Concatenation Set 

Explanation: Rational 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. 




COPY or INCLUDE files, as reported on the "File 

details" page, and ensure their owning container(s) are 


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. 

Module: 

DMH1776E 


Ambiguous Concatenation Sets, User 

needs to Select correct set 


automatically determine the appropriate concatenation 

set to apply to resolve COPY or SQL INCLUDE 


DMH1777I • DMH1784W 

references, likely due to multiple files with the same 

name captured in the inventory or multiple 

concatenation sets that could satisfy the references. 


deleted, and postprocessing continues with the next 

queue entry. 


COPY or SQL 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 and/or SQL 

INCLUDE reference(s). One or two concatenation sets 

may have to be assigned, depending on the type of 

missing reference(s). COPY references are resolved by 

the language concatenation set, while SQL INCLUDE 

references are resolved by the SQL concatenation set. 

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. 

Module: 

DMH1777I 

Explanation: 



Module: 

DMH1778E 


CNTLCRDS input: parameters 

This message reports processing status. 


None 

DBDGEN scanner, PSBGEN scanner 

Invalid input: parameter 

Explanation: While processing control cards, the 

scanner found invalid parameter data parameter. No 

expected keyword was recognized. 



User response: None. This function is not active in the 

current release of the product. 

Module: 

DMH1779E 


System must be numeric 

Explanation: The scanner detected a system control 

card that was non-numeric. 





Module: 


DMH1780E 

PSB Library Name is Missing 

Explanation: 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. 




Module: 

DMH1781E 



DBD Library Name is Missing 

Explanation: 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. 




Module: 

DMH1782E 



ACB Library Name is missing 

Explanation: While processing import records for an 

IMS access control block (START ACBLIB), the loader 

detected a missing ACB container name. 




Module: 

DMH1783E 



No DBD ID for Segment: segmentname 

Explanation: While processing the import records, the 

loader detected a missing DBD ID for segment 

segmentname on the DSEG record. 




Module: 



DMH1784W Found Invalid Length for 

imscomponenttype compnentname 

Explanation: While processing the import records for 

imscomponenttype, the loader detected a zero length for 

componentname. The length must be greater than zero. 

System action: The current record is skipped, and 



Module: 





DMH1785W Missing Source Segment Name number 

for: sourcedbdname, segmentname 


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. 

System action: The current asset is skipped, and 



Module: 

DMH1786E 



No Segment ID for Field: 

fieldname,segmentname 


loader detected a missing segment ID for 

fieldname,segmentname on the IFLD record. 




Module: 



DMH1787W Found Invalid Field Position: 

fieldname,segmentname 


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. 




Module: 

DMH1788E 



No PSB ID for Segment: segmentname 


loader detected a missing PSB ID for segment 

segmentname on the PSEG record. 




Module: 



DMH1789E 

No PSB ID for PCB: 

psbname,pcbsequence,pcbtype 

Explanation: While processing import records, the 

loader detected a missing PSB ID for PCB 

psbbname,pcbsequence,pcbtype on the IPCB record. 




Module: 



DMH1790W Unable to insert IMS component: 

imscomponenttype componentname 


loader failed to successfully insert a row for 

imscomponenttype componentname in the DMH_IMS_* 

table of interest. 




Module: 



DMH1791W Truncating DD name to 8 characters: 

ddname 


loader detected DD name ddname was longer than 8 

characters. ddname was truncated to 8 characters and 

inserted into table DMH_IMS_DBD_DD. 



Module: 

DMH1792E 


None 


No DBD for DD name: record 


loader detected a missing DBD ID on the IDDN record. 




Module: 

DMH1793E 



Unable to add to DBD the DD name: 

ddname 


loader was unsuccessful at inserting a row in table 

DMH_IMS_DBD_DD for DD name ddname. 




Module: 





DMH1794E Subsys must be numeric 

Explanation: While processing control cards, the 

scanner found a non numeric subsys value. 

System action: Processing stops. 



Module: DBDGEN scanner, PSBGEN scanner 

context. For example, DFSTRA0T, IMSLOGR, and 

IMSMON are reported here but otherwise ignored. No 

further data is collected for the 

DMH_ONLINE_DSTORE and DMH_DATASET tables 

for filename. 



Module: 


None. 

IMS scanner - DMHMDA 

DMH1795W Unknown DFSPSBD type found 

in stage 2 records for PGM programname 

Explanation: During analysis of the macros used as 

input to IMS stage 2 generation for transaction and 

program information, a type other than BMP or TP was 

encountered. 

System action: The scanner skips the current record 



Module: 

DMH1796E 


IMS scanner - DMHSTG2 

Command file does not contain 

transaction data 

Explanation: The DISPLAY TRANSACTION ALL 

command issued in batch returned zero transaction 

records. 



Module: 

DMH1797I 

Explanation: 



Module: 

DMH1798I 

Explanation: 



Module: 



IMS scanner - DMHDIST 

File ( filename ) in MDAFILE will be 

interrogated 



None 


File ( filename ) in MDAFILE identifies a 

database dynamic allocation 



None 


DMH1799W MDAFILE file filename does not describe 

a database 

Explanation: Although dynamically allocated, the 

MDAFILE file filename is not of interest in the current 

DMH1800W Unable to determine DBDNAME from 

MDAFILE file filename 

Explanation: Analysis of the file filename indicates it 

is not a database dynamic allocation and therefore, the 

DBDNAME is not warranted. 



Module: 

DMH1801I 

Explanation: 



Module: 

DMH1802I 

Explanation: 



Module: 

DMH1803I 

Explanation: 



Module: 

DMH1812E 


None. 


EXCLUDE file is empty. No files have 

been excluded 



None 


IMS database dynamic allocation file 

scanner scandate 

This message reports processing status 


None 


Process finished, recursive call found 



None 


No source code found from the site for 

transfer target entrypointname 

Explanation: No matching entry point was found for 

the transfer target entrypointname. The run unit is 

identified as unresolved. 



User response: Locate the source code for entry point 

entrypointname. Collect inventory for the file to resolve 



run unit status. Alternatively, you can add entry points 

for which there is no source to the 

&hlq.SDMHDATA(DMHUTIL) file to exclude them 

from further analysis. You can include z/OS runtime 

modules in the DMHUTIL file. 

Module: 

DMH1817E 


Multiple EntryPoints for 

transfertargetentrypointname. 

Explanation: Multiple entry points matched the 

transfertargetentrypointname. The run unit is identified as 

unresolved. 



User response: Multiple entry points with the same 

name are preventing successful Run unit resolution. In 

order to correct the situation, the Run unit names must 

be unique per Site. As such, multiple programs with 

the same main entry point name should be isolated 

into separate Sites, or as applicable, the second+ 

duplicate programs should be permanently removed 

from the inventory. 

Module: 


DMH1819W Cannot get a RunUnitName from the 

input RunUnitId: rununitid. 

Explanation: The processor was unsuccessful at 

retrieving the run unit name from the 

DMH_EP_SYMBOL table for the corresponding 

EP_SYMBOL_ID associated with the run unit ID 

rununitid in the DMH_RUN_UNIT_TABLE. 



Module: 




DMH1822W Cannot open Alias file. DD:LOADMOD 

Explanation: Processing failed to successfully open the 

load module alias file DMHALIAS. 



User response: 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 

yourRational Asset Analyzer administrator. 

Module: 

DMH1823E 


List creation failed. 

Explanation: An attempt to build a linked list failed. 

This is an internal error of the application. 




Module: 

DMH1824E 



Add LoadModule Node failed. 

Explanation: An attempt to build a load module alias 

list failed. This is an internal error of the application. 



Module: 

DMH1826E 




Successor list cannot be created. 

Explanation: An attempt to build a linked list failed. 




Module: 

DMH1827E 




Successor failed to be added to list. 

Explanation: An attempt to add an item to a linked 

list failed. This is an internal error of the application. 



Module: 

DMH1830E 

Explanation: 

application. 



Module: 

DMH1831E 




Cannot create a memory block, abort. 





The 1st field in Alias File must be a 

load module name at line linenumber 

Explanation: An error was detected while processing 

the first field in the record on line number linenumber 

in the load module alias file. 



User response: Verify the record layout in the load 

module alias file DMHALIAS, found in data set 

&hlq.SDMHDATA;, is correct; reattempt postprocessing. 

Module: 




DMH1832E 

The 2nd field in Alias file must be an 

alias name at line linenumber 


the second field in the record on line number 

linenumber in the load module alias file. 






Module: 


DMH1833W The 3rd field in Alias File must be a 

container name or NONE at line 

linenumber 


the third field in the record on line number linenumber 



Processing continues 




Module: 


DMH1834W The 4th field in Alias File must be an 

Application id or NONE at line 

linenumber 


the fourth field in a record on line number linenumber 







Module: 

DMH1835I 


The RunUnitName, name, matched a 

utility name. 

Explanation: This message reports processing status 

indicating successful run unit resolution. 



Module: 


None 


DMH1836W Cannot open utility file. DD:UTILITY 

Explanation: Processing failed to successfully open the 

utility program list file DMHUTIL. 




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 Rational Asset 

Analyzer administrator. 

Module: 

DMH1837I 

Explanation: 



Module: 

DMH1838I 


Utility exclusion file read from DD: 

ddname 



None 


Number of records read from file: count 


indicating the number of records read from either the 

load module alias file (DMHALIAS) or utility program 

list file (DMHUTIL). 



Module: 

DMH1839I 


None 


Alias substitution file read from DD: 

ddname 


indicating successful open and read of the alias 

substitution file ddname. 



Module: 

DMH1850I 


None 


Resolved by alias. RU=rununitname 





Module: 

DMH1851I 


None 


Resolved by entry point name. 

RU=rununitname 





Module: 


None 




DMH1852E 

Cannot find an EntryPoint for 

transfertargetentrypointname. 

Explanation: No matching entry point was found for 

the transfertargetentrypointname. The run unit is 

identified as unresolved. 



User response: Locate source code for entry point 

transfertargetentrypointname; collect inventory for the file 

to resolve run unit status. 

Module: 


DMH1921E 

Source analyzer failed, no data collected 

from file: filename 

Explanation: Assembler source analysis for file 

filename failed. The analysis status for the compile unit 

is Error. 



User response: Locate message DMH1929W for return 

code data. Resolve the error and try the operation 

again. 

Module: 

REXX - DMHI630Z 

DMH1853I 

RD_RUN_UNIT_CNTNT Inserts for this 

Run Unit: insertedrowcount 

Explanation: This message appears in debug mode 

only. It reports processing status. 



Module: 

DMH1900E 

Explanation: 

application. 



Module: 

DMH1901E 

Explanation: 

application. 



Module: 


None 


Message interface called without any 

message number. 




DMHMINTF - Interface to LE messaging 

Message to be displayed is invalid 

message. 




DMHMINTF - Interface to LE messaging 

DMH1920W Unable to obtain Site Name from 

system: Using name '*default*' 

Explanation: 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. 



Module: 



REXX - DMHGTSTE 

DMH1922W BMS scanner failed, no Compile Unit 

rows generated for file: filename, Return 

Code: returncode 

Explanation: Assembler analysis for BMS file filename 

failed with return code returncode. The analysis status 

for the compile unit is Error. 



again. 

Module: 


Resolve the error and try the operation 

REXX - DMHI630Z 

DMH1929W scantype analyzer return code: returncode 

Explanation: Return code returncode was raised by 

scantype analysis. The analysis status for the compile 

unit will be Error. 



User response: Resolve scanning errors; try the 


Module: 

DMH1935E 

Assembler, BMS, COBOL and PL/I scanner 

No ADATA records produced by 

assembly 

Explanation: The IBM assembler did not produce any 

output for analysis. 



User response: Verify the file is valid assembler source 

and the ADATA option is enabled; reattempt the 

analysis. If the problem continues, contact IBM 

Software Support. 

Module: 

DMH1936E 

Assembler scanner 

ADATA is not from HLASM translator 

Explanation: The ADATA file being processed by the 

assembler analyzer is not from the assembler translator. 





User response: Verify the IBM translator is being used 

by the assembler scanner; reattempt the analysis. If the 

problem continues, contact IBM Software Support. 

Module: 

DMH1937E 


ADATA version is not supported 

Explanation: The ADATA file produced by the 

assembler analyzer is not from a supported version. 




Module: 

DMH1938E 



Unable to allocate assembler analyzer 

INCLUDE/MACRO libraries 

Explanation: The assembler analyzer is unable to 

allocate SYS1.MACLIB. 



User response: Verify SYS1.MACLIB is available and 

the user has the proper authority to access the 

container; reattempt the analysis. If the problem 

continues, contact IBM Software Support. 

Module: 

DMH1939E 


Unable to allocate assembler analyzer 

source file: filename 

Explanation: The assembler scanner is unable to 

allocate the input source file. 



User response: Verify the input source file is available 

and the user has the proper authority to access the 

container; reattempt the analysis. If the problem 


Module: 

DMH2000E 


Unable to open file filename. The file 

status code is statuscode. If the file status 

is 39, make sure the file attributes are 

correct (such as LRECL). 

Explanation: An OPEN request for file filename failed. 

The reported status code is statuscode. There are several 

interim work files utilized for creating and sorting 

CICS data of interest. 



User response: Reattempt the analysis. If the problem 


Module: 

CICS region analyzer 

DMH2001W Unable to close file filename. The file 

status code is statuscode. 

Explanation: A close request for file filename failed. 

The reported status code is statuscode. There are several 

interim work files utilized for creating and sorting 

CICS data of interest. 



User response: Reattempt the analysis. If the problem 

continues, contact IBM Software Support.. 

Module: 

DMH2002E 


Unable to write to file filename. The file 

status code is statuscode. 

Explanation: An attempt to write a record to file 

filename failed. The value for filename can be 

DMHCONN, DMHFILE, DMHMAPS, DMHPIPE, 

DMHRECS, DMHTRAN, DMHURMP, DMHWEBS or 

DD:TEMPLIST. The reported status code is statuscode. 



User response: Depending on the value of statuscode, 

insufficient disk space is generally the reason for a 

failure in this area. The following are default space 

allocations: 

v DMHCONN, DMHFILE, DMHMAPS, DMHPIPE, 

DMHTRAN, DMHURMP, and DMHWEBS: 

SPACE=(CYL,(1,1)) in &hlq.SDMHREXX;(DMH0733). 

v DMHRECS: SPACE=(CYL,(1,1)) in the region scan 

JCL. 

v TEMPLIST: SPACE=(1024,(1000,100)) in the catalog 

scan JCL. A of -1 is a direct indicator of write failure 

due to insufficient disk space for this data set. 

Increase the primary and/or secondary disk space 

parameters and run the job again. 

Module: 

DMH2003E 

DB2 Catalog Scanner, CICS region analyzer 

Sort of filename failed. 

Explanation: An attempt to sort file filename failed. 




Module: 

DMH2004I 




Number of files processed from JCL 

analyzer = number. 

Explanation: The CICS region analyzer calls the JCL 

analyzer to process the CICS start JCL. This message 

indicates that the JCL analyzer analyzed number data 

sets, as identified in the CICS start JCL Step executing 

PGM=DFHSIP. 






Module: CICS region analyzer 


Module: CICS region analyzer 

DMH2005E 

The recordnumber record in CICSYS1 

must be a value. 

Explanation: The analyzer detected a missing control 

record. SITE and CREG are required. 



Module: 

DMH2008E 




The OBJECTS keyword is required on 

the EXTRACT command. 

Explanation: Rational 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. 



Module: 

DMH2010E 




A job step that starts a CICS region 

cannot be found in the JCL specified 

(no job step is using PGM=DFHSIP). 


analyzer 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 

analyzer does not currently provide analysis support 

for the second scenario. 



User response: 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. 

Module: 

DMH2011E 


The maximum number of files has been 

exceeded. Maximum number of files 

supported is maxnum. 


analyzer to process the CICS start JCL. While 

processing the JCL, an internal table limit was exceeded 

before the end of file was reached. 



DMH2012E 

Missing records on CICSYS1. 


analyzer to process the CICS start JCL. While 

processing the output records from the JCL analysis, an 

unexpected end of file was encountered. 



Module: 




DMH2015W Duplicate file from the same source. 

Filename = filename. Source = sourcename. 

Explanation: 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. Rational Asset Analyzer is attempting to resolve 

data stores (files) and data sets. 

System action: The current file record is skipped, and 



Module: 

DMH2016I 



Data set name for file name came from 

the JCL. 


indicating that the data set resolution for file name was 

from the CICS start JCL. 



Module: 

DMH2017I 


None 



the CSD. 



from the CICS system definition (CSD). 



Module: 

DMH2018I 


None 



the FCT. 



from the CICS dynamically allocated data sets (FCT). 





Module: 


None 


DMH2019W Data set name for file name was NOT 

found. 

Explanation: No corresponding data set for file name 

was discovered in the start JCL, CSD or FCT. 



User response: None. This warning indicates that a 

corresponding data set will not be associated with the 

named CICS file in the user interface where CICS files 

are displayed, such as the "CICS online region details" 

page or the "Data store summary" page. 

Module: 

DMH2020I 

Explanation: 



Module: 

DMH2021E 


Processing region regionname 



None 


A GRP or LIST record is required for 

REGN regionname 

Explanation: The analyzer encountered an unexpected 

error processing the GRP control record. By default, all 

groups in the CSD are examined. 



Module: 

DMH2022E 




A CSD record is required for REGN 

regionname 


error processing the CSD control record for the region 

analysis. 



Module: 

DMH2023E 




A REGN record is missing the region 

name 


error processing the REGN control record for the region 

analysis. 





Module: 

DMH2024E 


More than one CSD record for REGN 

regionname 

Explanation: The analyzer encountered multiple CSD 

control records; only one CSD per region is supported. 



Module: 

DMH2025E 




More than one LIST record for REGN 

regionname 

Explanation: The analyzer encountered multiple LIST 

control records. Only one LIST record per region is 

supported. 



Module: 

DMH2026E 




More than one FCT record for REGN 

regionname 

Explanation: The analyzer encountered multiple FCT 

control records. Only one FCT record per region is 

supported. 



Module: 

DMH2027E 




More than one SJCL record for REGN 

regionname 

Explanation: The analyzer encountered multiple SJCL 

(start JCL) control records. Only one SJCL record per 

region is supported. 



Module: 

DMH2028E 




Temporary data set datasetname, already 

exists 

Explanation: The analyzer found that a temporary 

work file was previously allocated. 



User response: Locate data set datasetname and delete 

it. Reattempt CICS region analysis. 

Module: 




DMH2029I 

Temporary data set datasetname, already 

exists : deleting 

Explanation: The analyzer found that a temporary 

work file was previously allocated, and it has been 

deleted. 



Module: 

DMH2030E 


None 


Allocate failed for data set datasetname 

Explanation: The analyzer could not allocate a 

required temporary work file datasetname. 



User response: Ensure system resources are available, 

and verify that the user has authority to create a 

sequential data set named datasetname with the 

following attributes: 

v Space units: CYLS 

v Primary quantity: 1 

v Secondary quantity: 1 

v Record format: FB 

v Record length: 128 

Reattempt CICS region analysis. If the condition 

persists, contact IBM Software Support. 

Module: 

DMH2031I 


PROC without SJCL, PROC ignored 


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. 



User response: 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 IBM 


Module: 

DMH2032I 


Return code from JCL analyzer 

returncode 


indicating the return code from the JCL analyzer 

invoked to process the CICS start JCL. 




Module: 

DMH2033I 

None 


Return code from Import record builder 

returncode 


indicating the return code from the import record 

builder used to create CICS region import records. 



Module: 

DMH2034E 


None 


CICS CSD scan failed returncode 

Explanation: The analyzer encountered a fatal error 

during processing, as indicated by return code 

returncode. 



Module: 

DMH2035I 




CICS CSD scan ended with Return code 

returncode 


indicating the return code from the CICS region 

analyzer. 



Module: 

DMH2036I 


None 


Calling DFHCSDUP for extract of GRP 

and LIST names 


indicating that the CICS system definition utility 

program (DFHCSDUP) is being used to gather group 

and list object information. 



Module: 

DMH2037I 


None 


Return from DMHCSDUP scan ended 

with return code returncode 


indicating the return code from reading from the CICS 

system definition file (CSD) using the CICS system 

definition utility program (DFHCSDUP). 




None 



Module: 

DMH2038E 


Unable to create temporary CSD to 

analyze FCT name 

Explanation: The analyzer could not allocate a 

required temporary work file for processing the load 

library for CICS dynamically allocated data sets, FCT 

name. 



Module: 

DMH2040E 




Wrong SCM call type requested: calltype 

Explanation: While processing SCM call parameters, 

an unexpected call type was detected. Valid call types 

are: 

v Full List 

v Change List 

v Member 

v Include 



Module: 

DMH2041E 



SCM processor - DMHSCMI 

Invalid SCM identifier entered: calltype 

Explanation: While processing SCM call parameters, 

an unexpected SCM type was detected. Valid call types 

are: 

v ChangeMan 

v SCLM 

v Panvalet 

v Librarian 



Module: 

DMH2042E 



SCM processor - DMHSCMI 

ChangeMan Message: message 

Explanation: While processing a ChangeMan request, 

the processor encountered an unexpected condition. 



Module: 



SCM processor - DMHSABLL 

DMH2046W Return code from DBUTIL: returncode 

Explanation: While processing the output from the 

SCLM DBUTIL service, the processor encountered an 

unexpected condition. 



Module: 

DMH2047E 



SCLM processor - DMHCLIST, DMHFLIST 

Allocation error on output file filename, 

return code returncode 

Explanation: The processor could not allocate required 

output file filename. 



User response: Ensure system resources are available, 

and verify that the user has authority to create a data 

set named filename with the following attributes: 

v Space units: CYLS 

v Primary quantity: 10 

v Secondary quantity: 10 

v Record format: FB 

v Record length: 123 

v Block size: 24600 

Reattempt the job. If the condition persists, contact IBM 


Module: 

DMH2048E 


Error writing to DDname TEMPLC 

Explanation: The processor encountered an 

unexpected write error while processing the SCLM 

output for updated records. 



Module: 

DMH2049E 




No parameters were specified 

Explanation: The processor failed to locate any input 

parameters for the SCLM task. Expected parameters are 

as follows: 

For Change List: 

v HLQ= Work Data Set High-Level Qualifier (set at 

install time) 

v PROJECT= SCLM Project Qualifier 

v ALTPROJ= SCLM Alternate Project (optional) 

v GROUP= Group to be scanned (default '*') 

v FRMDATE= From Date (YYYYMMDD) 

For Full List: 



v HLQ= Work Data Set High-Level Qualifier (set at 

install time) 






Module: 

DMH2050E 




Invalid parameter format in parm: 

parameterposition parametername 

Explanation: 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: 




v FRMDATE= From Date (YYYYMMDD) 

For Full List: 






Module: 

DMH2051E 




Invalid parameter specified 

Explanation: 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: 

v PROJECT 

v ALTPROJ 

v GROUP 



Module: 

DMH2052I 



SCLM processor - DMHFLIST 

Valid parameters are 

PROJECT=,ALTPROJ=,GROUP=,HLQ= 


indicating that the processor detected an unexpected 

error while verifying the PROJECT, ALTPROJ, and/or 

GROUP input keyword parameters for a Full List 

request. 



Module: 

DMH2053I 




The project parameter is mandatory 


indicating that the processor detected an unexpected 

error while verifying the PROJECT input parameter 

keyword for a Full List request. 



Module: 

DMH2054E 




datasetname not found, run SPYFLIST 

first 

Explanation: Data set datasetname, containing the full 

scan output from module SPYFLIST, was not found. 



User response: You may need to process a Full List 

request in order to proceed. Contact IBM Software 

Support. 

Module: 

DMH2055I 

SCLM processor - DMHCLIST 

Valid parameters are PROJECT=, 

ALTPROJ=, GROUP=, HLQ=, 

FRMDATE= 

Explanation: 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: 

v PROJECT 

v ALTPROJ 

v GROUP 

v FRMDATE 



Module: 

DMH2056I 




The project and date (YYYYMMDD) 

Parameters are mandatory 

Explanation: The processor detected an unexpected 

error while verifying the PROJECT and/or FRMDATE 

input parameter keywords for a Change List request. 



Module: 





DMH2102I • DMH2114E 

DMH2102I 

Database Changes Committed 


only. It reports processing status indicating the database 

has been successfully updated. 



Module: 

DMH2103E 


None 


Database Changes Not Committed, 

because of Error 

Explanation: The loader experienced a fatal error 

while attempting to update the database. 




Module: 

DMH2104E 



Check Previous Error Messages 

Explanation: Locate message DMH2103E and prior 

message entries leading up to it to identify potential 

cause of the error condition. 




Module: 

DMH2106E 



Tool ID contains non-digit 


loader detected an invalid tool ID value on the TOOL 

record. 



Module: 

DMH2107E 




FMT record is missing 


loader did not detect a required FMT record. 



Module: 




DMH2108E FMT Version must be equal to 1 


loader detected an invalid value for the format version 

on the FMT record. 




Module: 

DMH2109E 



Invalid FMT record, Fatal Error 


loader detected an invalid value for the format name 

on the FMT record. 



Module: 

DMH2110I 




File information being stored in 

database: filename 

Explanation: The database has been updated with 

asset type file filename data. 



Module: 

DMH2111E 


None 


Record format invalid: parameter 

Explanation: 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: 

v SITE 

v REGN 

v CSD 

v GRP 

v LIST 

v FCT 

v SJCL 

v PROC 



Module: 

DMH2114E 




Record skipped because of error in this 

file 

Explanation: 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. 




Module: 





DMH2115E 

Invalid record type recordtype 


loader detected an unknown record type recordtype. 

System action: The invalid record is skipped, and 



Module: 

DMH2118I 



Input records read: number 


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. 



Module: 

update 

DMH2120E 


None 

Import record loader, DMH0700 - Batch 

cannot update LANGUAGE_CD 

Explanation: The loader was unable to update column 

LANGUAGE_CD in table DMH_FILE. 




Module: 

DMH2121E 



SITE record is missing 

Explanation: While processing input parameters, the 

analyzer did not detect a required SITE record. 



Module: 

DMH2122E 




Invalid SITE record, Fatal Error 


loader detected an invalid value for the site name on 

the SITE record. 



Module: 

DMH2123E 




Invalid LIBR record, Fatal Error 


loader detected an invalid value for the container name 

on the LIBR record. 



Module: 

DMH2124E 




LIBR record is missing 


loader did not detect a required LIBR record. 



Module: 

DMH2127E 




PROC record is missing 

Explanation: 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. 




Module: 

DMH2128E 



JOB record is missing 

Explanation: 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 






Module: 

DMH2129E 



START CU record is missing 

Explanation: 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. 




Module: 




DMH2130W • DMH2143I 

DMH2130W DMH_CU_STMT insert failed: data 

Explanation: The loader failed to successfully insert a 

row in table DMH_CU_STMT while processing a STMT 

record. 




Module: 



DMH2135W Duplication found in insertion. data 

Explanation: 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. 




Module: 



DMH2131W DMH_CU_DATA_USE insert failed: data 


row in table DMH_CU_DATA_USE while processing a 

REF record. 




Module: 



DMH2139I 

File char attributes deleted. 

Explanation: Row(s) in the DMH_MEM_CHAR_ATTR 

table have been deleted for the load module file being 

processed on the START LOMD record. 





Module: 


DMH2132E 

DEA record is missing 

Explanation: The loader detected a missing data 

element ID, implying that a DEA record was either 






Module: 



DMH2141I 

Unable to insert application: 

applicationname 


row in table DMH_APPLICATION for application 

applicationname while processing an APP record. 




Module: 



DMH2133I 

Debug record: importrecordtype value 


only. It echoes the import record type and value being 

processed. 



Module: 

DMH2134I 


None 


Debug record: data 


only. It echoes the work data being processed. 



Module: 


None 


DMH2142I 

Multiple parent applications found, 

application applicationname insert under 

first found. 

Explanation: 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. 



Module: 

DMH2143I 


None 


Unable to find application 

childapplicatonname with parent 

application id parentapplicationid. Trying 

to insert as primary application. 

Explanation: 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. 





Module: 

DMH2144I 


None 


New user attribute added: attributetypeid 

Explanation: A row has been inserted in the 

DMH_ATTR_NAME table for a new user-supplied 

attribute with type ID attributetypeid. 



Module: 

DMH2145E 


None 


Invalid FILE record, Skipping till the 

next FILE record. 

Explanation: While processing a FILE record, the 

loader detected missing data in a required attribute 

field: resource manager type, container name, file 

name, or language. 




Module: 



DMH2146E Invalid Resource Manager Name: %1. 

Must be defined in product 

configuration. 

Explanation: The import file loader or batch update 

program encountered an invalid resource manager 

name. 


The data base update is ignored. 

User response: Correct the resource manager name or 

add it to the product configuration, and rerun. 

Module: 

update 

Import record loader, DMH0700 - Batch 

DMH2207I Unable to load data into database: RC = 

returncode 

Explanation: Changes were not successfully written to 

the database, as indicated by return code returncode. 




Module: 


REXX - DMH650Z 

DMH2209I 

Unable to read file containing deep 

analysis request 

Explanation: No containers and files were found in 

the scan request file. 



Module: 




DMH2211W Number of containers specified (%1) 

does not match resource management 

type. Container names truncated. 

Explanation: A container scan was submitted without 

specifying the proper number of names to scan for the 

given resource manager. 


The container scan is terminated. 

User response: Correct the number of names, or the 

resource manager type, and resubmit the container 

scan. 

Module: 


DMH2212W Number of containers (%1) too few for 

resource management. Default values 

are attempted. LibName: %2 

Explanation: An SCLM container scan was submitted 

with more than 2 variables specifying the SCLM 

project. 



User response: SCLM projects are identified with 2 

names; resubmit the container scan with the proper 

SCLM name(s). 

Module: 

DMH2213E 


Number of containers (%1) too few for 

resource management. List attempts 

aborted. LibName: %2 

Explanation: An container scan was submitted 

without specifying the container to scan. 



User response: Container scan requests need to 

specify a container name. Resubmit the container scan 

with the proper name(s). 

Module: 

DMH2230E 


Unable to queue requested record for: 

schema name row 

Explanation: Processing was unable to insert a row 

into the DMH_ANALYSIS_QUEUE table. 


continues. 





Module: 

DMH2231I 


DMH0700 - Batch update 

Re-analyze request queued successfully 

for container name and file name 

Explanation: Processing successfully inserted a row 




Module: 

DMH2232I 


None 


Analyze new file queued successfully 

for container name and file name 





Module: 


None 


DMH2233W Re-analyze request for container name, 

file name does not belong to SCM 

application name 

Explanation: The referenced application was not 

found for the SCM. Batch reanalysis does not support 

queuing a new SCM application, container, and file. 


continues. 


User response: Verify and correct the input record 

supplied for &hlq.SDMHCNTL member DMHJCLBU; 

resubmit the job. 

Module: 


DMH2234W Re-analyze does not accept a request for 

a new container name 

Explanation: Batch reanalysis does not support 

queuing a new container. 


continues. 


User response: Use the Inventory function from the 

browser interface to add the new container to the 

database. 

Module: 


DMH2235W Re-analyze request with invalid Action 

type type Valid types are C, change or D 

Delete 

Explanation: Processing detected an invalid action 

type parameter on the input record. 


continues. 





Module: 


DMH2236W Site Name name does not exist in the 

database. 

Explanation: 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. 


continues. 





Module: 


DMH2237W Delete request for file that does not 

exist. Container name file name request 

rejected. 

Explanation: Processing detected a delete request for a 

file that does not exist in the referenced container. 


continues. 


Module: 


None 


DMH2238W Invalid input: input record 

Explanation: Processing detected an error or missing 

parameter on the input record. 


continues. 


User response: Verify and correct the indicated input 

record. Refer to valid format information in 

&hlq.SDMHCNTL member DMHJCLBU; resubmit the 

job. 

Module: 

DMH2239E 

Explanation: 



Could not open filename 

Open failure for the INFILE DD data set. 


User response: Verify and correct the data set 

information for the INFILE DD specified in 

&hlq.SDMHCNTL member DMHJCLBU; resubmit the 

job. 

Module: 




DMH2240I 

Delete request queued successfully for 

container name and file name 





Module: 

DMH2241E 


None 


Analyze new file for SCM is not 

allowed: container: name file name SCM 

parms: parms 

Explanation: Batch reanalysis does not support 

queuing a new SCM file. 


continues. 


User response: Use the Inventory function from the 

browser interface to add the SCM file to the database. 

Module: 

DMH2400I 

Explanation: 



Module: 

DMH2401I 

Explanation: 



Module: 

DMH2402I 


Inserted by SQL reference resolution 



None 

DB2 catalog scanner 

Inserted by DB2 catalog scan 



None 

DB2 catalog scanner 

Created by Batch Update interface 

Explanation: This message indicates that a 

DMH_APPLICATION or DMH_SITE row was added to 

the Rational Asset Analyzer database during the 

processing of a Batch Update interface request. 



Module: 

DMH2403I 


None 

DMH0700 

Inserted with RU import record 

Explanation: This message indicates that a 

DMH_DB2_SUBSYSTEM row was added during the 

processing of JCL analyzer import file records. 




Module: 

DMH2410I 

None 

DMH0731 

A schema name request for 

schema name record 

Explanation: This message provides specific 

information about DB2 assets as Rational Asset 

Analyzer scans DB2 catalogs. It can appear as part of a 

group of messages that provide details about the DB2 

assets scanned or the scanning process. Specifically, it 

indicates which schema name is currently being scanned. 



Module: 

DMH2411I 


None 

DMH0565 

Loading procedure: schema name proc 

name 






indicates which schema name proc name is currently 

being loaded. 



Module: 

DMH2412I 


None 

DMH0565 

Loading table: schema name table name 






indicates which schema name table name is currently 

being loaded. 



Module: 

DMH2413I 


None 

DMH0565 

Loading view: schema name view name 






indicates which schema name view name is currently 

being loaded. 




None 



Module: 

DMH2414I 

DMH0565 

Loading view's base table: schema name 

view name 







being loaded. 



Module: 

DMH2415I 


None 

DMH0565 

DB2 table schema names 





assets scanned or the scanning process. 



Module: 

DMH2416I 


None 

DMH0565 

DB2 procedure schema names 





assets scanned or the scanning process. 



Module: 


None 

DMH0565 

DMH2417W No DB2 schema names found 






indicates no schema names were found during the DB2 

scan. 



Module: 


None 

DMH0565 

DMH2418I 

Summary object counts 






indicates how many objects of each type were 

encountered during the DB2 scan. 



Module: 

DMH2419I 


None 

DMH0565 

Tables: number 

Explanation: This message is a continuation of 

message DMH2418I. 



Module: 

DMH2420I 


None 

DMH0565 

Columns: number 





Module: 

DMH2421I 


None 

DMH0565 

Views: number 





Module: 

DMH2422I 


None 

DMH0565 

View Base Tables: number 





Module: 

DMH2423I 


None 

DMH0565 

Procedures: number 






None 



Module: 

DMH2424I 

DMH0565 

Estimated SPACE for DMHR565B 

output data set 






indicates how much disk space may need to be 

allocated for the DB2 scans DD:TEMPLIST data set 

based on counts presented in message DMH2418I, in 

order for the DB2 scan to function properly. 



Module: 

DMH2425I 


None 

DMH0565 

DD:TEMPLIST for the DB2 catalog 

object counts 





Module: 

DMH2426I 


None 

DMH0565 

described above 





Module: 

DMH2427I 


None 

DMH0565 

TRK: number 





Module: 

DMH2428I 


None 

DMH0565 

or 





Module: 


None 

DMH0565 

DMH2429I CYL: number 





Module: DMH0565 

DMH2430I Use default setting for DMHR565B: 






DMH2431I SPACE=(1024,(1000,100)) 






DMH2432I None. There were zero DB2 objects 






DMH2433I of interest based on the DB2 catalog 






DMH2434I object counts described above. 








DMH2435I 

Scanning table: schema name table name 






indicates which schema name table name is currently 

being scanned. 



Module: 

DMH2436I 


None 

DMH0565 

Scanning procedure: schema name proc 

name 






indicates which schema name proc name is currently 




Module: 

DMH2437I 


None 

DMH0565 

Scanning view: schema name view name 










Module: 

DMH2438I 


None 

DMH0565 

Have completed processing number SQL 

column rows 






indicates the progress being made scanning number 

columns. 



Module: 


None 

DMH0565 

DMH2439I 

All SQL column rows processed 






indicates the column scanning is complete. 



Module: 

DMH2440I 


None 

DMH0565 


PROC rows 







procs. 



Module: 

DMH2441I 


None 

DMH0565 

All SQL PROC rows processed 






indicates the proc scanning is complete. 



Module: 

DMH2442I 


None 

DMH0565 


table rows 







tables. 



Module: 


None 

DMH0565 



DMH2443I 

All SQL table rows processed 






indicates the table scanning is complete. 



Module: 

DMH2444I 


None 

DMH0565 

There is 1 SQL table row to process 






indicates that there is only one table to process. 



Module: 

DMH2445I 


None 

DMH0565 

There are number SQL table rows to 

process 






indicates that there are number tables to process. 



Module: 

DMH2446I 


None 

DMH0565 

There is 1 SQL column row to process 






indicates that there is only one column to process. 



Module: 


None 

DMH0565 

DMH2447I 

There are number SQL column rows to 

process 






indicates that there are number columns to process. 



Module: 

DMH2448I 


None 

DMH0565 

There is 1 SQL PROC row to process 






indicates that there is only one proc to process. 



Module: 

DMH2449I 


None 

DMH0565 

There are number SQL PROC rows to 

process 






indicates that there are number procs to process. 



Module: 

DMH2450I 


None 

DMH0565 

SQL resolution completed, highest 

return code = return code 






indicates SQL loading has completed. 



Module: 


None 

DMH0565 



DMH2451W Multiple DB2 systems have table name, 

mapping to default 



Analyzer scans DB2 catalogs. It indicates a given table 

name was found in more than one DB2 system. The 

name is associated with the placeholder DB2 system. 



Module: 


None 

DMH0565 

DMH2452W Multiple DB2 systems have proc name, 

mapping to default 



Analyzer scans DB2 catalogs. It indicates a given proc 

name was found in more than one DB2 system. The 

name is associated with the placeholder DB2 system. 



Module: 

DMH2453I 


None 

DMH0565 

Cannot match SQL column ref, no 

symbol id 



Analyzer scans DB2 catalogs. It indicates a given 

column reference could not be found in the 

DMH_SYMBOL table. The reference is ignored. 



Module: 


None 

DMH0565 

DMH2454I Cannot match SQL column ref * 



Analyzer scans DB2 catalogs. It indicates the column 

reference * cannot be matched to the columns of a 

given DB2 table. The reference is ignored. 



Module: 

DMH2455I 


None 

DMH0565 

Cannot match SQL ref name, noSQL 

table ref 




reference name cannot be matched to a given DB2 table. 

The reference is ignored. 



Module: 

DMH2456I 


None 

DMH0565 

Cannot match SQL ref name, many SQL 

table refs 




reference name cannot be matched to a given DB2 table 

because there are many table matches. The reference is 

ignored. 



Module: 

DMH2457I 


None 

DMH0565 

Cannot match SQL ref name, SQL table 

ref not matched 





because there are no table matches. The reference is 

ignored. 



Module: 

DMH2458I 


None 

DMH0565 

Cannot match SQL column ref name to 

DB2 column in subsystem 





because there is no column match in subsystem. The 

reference is ignored. 



Module: 

DMH2459I 


None 

DMH0565 

Cannot match SQL proc ref name to 

specific DB2 system 



Analyzer scans DB2 catalogs. It indicates the proc 

reference name cannot be matched to a given DB2 

subsystem. The reference is ignored. 






Module: 

DMH2460I 

None 

DMH0565 

Cannot match SQL proc ref name to 

multiple DB2 systems 



Analyzer scans DB2 catalogs. It indicates the proc 


subsystem because there are many valid matches. The 




Module: 

DMH2461I 


None 

DMH0565 

Cannot match SQL table ref name to 

specific DB2 system 



Analyzer scans DB2 catalogs. It indicates the table 


subsystem. The reference is ignored. 



Module: 

DMH2462I 


None 

DMH0565 

Cannot match SQL table ref name to 

multiple DB2 systems 



Analyzer scans DB2 catalogs. It indicates the table 


subsystem because there are many valid matches. The 




Module: 

DMH3001E 


None 

DMH0565 

Program parameter is not found. 

Explanation: The program file name was not passed 

to the scanner. This is an internal error of the 

application. 



Module: 



Compiler Based Scanner 

DMH3002E 

Parameter name is invalid. 

Explanation: The parameter passed to the scanner is 

invalid. This is an internal error of the application. 



Module: 

DMH3003E 

Explanation: 

application. 



Module: 

DMH3004E 

Explanation: 

file. 



Module: 

DMH3005E 

Explanation: 

file. 



Module: 

DMH3007E 




Internal data error. 





Cannot open Options file filename. 

The scanner failed to open the options 




Cannot read Options file filename. 

The scanner failed to read the options 




The length of the combined compiler 

and SQL options was too long. 

Explanation: The COBOL or PL/I scanner was not 

able to pass all the configured options to the compiler 

because their total length was too long. The actual 

options are the ones assigned to the COBOL or PL/I 

source file. They are determined by the options 

configured for File, Application, Container, Site, and 

installation, in that order. When the scanner invokes the 

COBOL or PL/I compiler to generate ADATA, the SQL 

option string is first appended to the compiler option 

string with a comma delimiter. The total length of the 

string (including the SQL option string) is restricted to 

50 bytes. 

System action: Processing reports the error and 

continues the analysis for the next asset. 

User response: Verify the length of the actual option 

string. Configure the scanning options for the File, 

Application, Container, Site, or installation. Shorten the 

options so that when the compiler options are 



combined with SQL options, the total length is 50 bytes 

or fewer. 

Module: 

DMH3008E 

Explanation: 


DMH630 


Module: 

DMH3010E 

Explanation: 

application. 


Scanning option is invalid 

An invalid internal option was found. 

DMH630 


Module: 

DMH3011E 

Explanation: 

application. 



Module: 

DMH3020E 

Explanation: 

application. 



Module: 

DMH3021E 



Memory allocation failure. 





Memory allocation failure because the 

area is already allocated. 










Cannot open SYSADATA file filename. 

Explanation: The scanner failed to open the 

SYSADATA file. The compiler may fail to generate the 

SYSADATA file. 



User response: Verify the source program can be 

compiled. If not, fix the compile errors and run the 

inventory again. 

Module: 


DMH3022E 

Cannot close SYSADATA file filename. 

Explanation: The scanner failed to close the 




User response: Run the inventory again. If the same 

error occurs again, contact IBM Software Support. 

Module: 

DMH3023E 


Cannot read SYSADATA file filename. 

Explanation: The scanner failed to read the 






Module: 

DMH3024E 

Explanation: 

application. 



Module: 

DMH3025E 


Internal error while reading SYSADATA 

file. 





Data error in SYSADATA file. The 

process is stopped. 

Explanation: The scanner found invalid contents in 

the SYSADATA file. 





inventory again. If the source program can be 

compiled, contact IBM Software Support. 

Module: 


DMH3026W Data error in SYSADATA file. 

Explanation: The scanner found invalid contents in 

the SYSADATA file. 


the processing. 

Skip the invalid contents and continue 




Module: 




DMH3030E 

Object Oriented COBOL is not 

supported. 

Explanation: The scanner found that the source 

program includes syntax of Object Oriented COBOL. 




supported. 

Module: 


None. Object Oriented COBOL is not 


DMH3031W The source file has a sequence of 

programs. Only first program is 

supported. 

Explanation: The scanner found that another program 

structure starts after a program structure ends. This 

message occurs for COBOL components only. 


program. 


Module: 

DMH3032E 

Continue processing for the first 

None 


No SOURCE records in SYSADATA file. 

There is a possibility that some error 

occurred during compilation. 

Explanation: The Compiler Based Scanner did not 

detect required data records in a SYSADATA file. The 

compiler was not able to generate a proper SYSADATA 

due to compilation problems. 


The scanner terminates processing. 

User response: Refer to RDPRINT for further problem 

determination and analyze the assets again after 

resolving the problem. 

Module: 

DMH3040E 

Explanation: 

application. 



Module: 

DMH3041E 

Explanation: 

file. 








Cannot open import file filename. 

The scanner failed to open the import 




Module: 


DMH3042E 

Explanation: 

file. 


Cannot close import file filename. 

The scanner failed to close the import 




Module: 

DMH3043E 

Explanation: 

file. 



Cannot write import file filename. 

The scanner failed to write the import 




Module: 

DMH3044E 

Explanation: 

application. 



Module: 

DMH3100E 


Internal error while writing import file. 

(internalLocation) 





Invalid internal parameter. (name) 

Explanation: The parameter of the scanner is invalid. 




Module: 

DMH3101E 




Internal error. (internalLocation) 

Explanation: The parameter passed to the scanner is 

invalid. This is an internal error of the application. 



Module: 

DMH3110E 

Explanation: 





Fail to open file. (filename) 

The scanner failed to open the file. 


User response: Verify the file exists. If the file is a 

copy or include file, verify that the correct 

concatenation set is specified. 

Module: 




DMH3111E Fail to close file. (filename) 

Explanation: The scanner failed to close the file. 




Module: Compiler Based Scanner 

DMH3122E The module is not initialized. 


application. 




DMH3112E Fail to read file data. (filename) 

Explanation: The scanner failed to read the file. 





DMH3113E Fail to write file data. (filename) 

Explanation: The scanner failed to read the file. 





DMH3114E File is not opened. 


application. 




DMH3120E The module is already initialized. 


application. 




DMH3121E Fail to initialize. 


application. 




DMH3130E 

Syntax error. (line[number], File[filename]) 

Explanation: The scanner found invalid syntax in the 

macro definition file. 



User response: Correct the invalid syntax in the macro 

definition file and then execute the inventory again. 

Module: 

DMH3131E 


Detect invalid source mapping 

information. 

Explanation: The scanner found invalid information in 

the mapping file. This is an internal error of the 

application. 



Module: 

DMH3140I 




Dummy data element (name) for pointer 

was created. 

Explanation: No real data element was located by the 

pointer in this compile unit, and a dummy data 

element was created to replace the pointer on a PROC, 

CALL, or READ statement. 



Module: 


None 


DMH3141W BASED locator reference for pointer 

(name) was ignored. 

Explanation: The Compiler Based Scanner detected an 

unsupported expression in the BASED attribute clause 

for the pointer and was not able to resolve the locator 

reference for the pointer. 



User response: If you need to analyze the impact for 

the pointer, you have to manually investigate the data 

flow in the source code for the pointer. 

Module: 




DMH3142W No locator reference for pointer (name, 

line number) resolved. 

Explanation: The Compiler Based Scanner was not 

able to resolve the locator reference for the pointer. 






Module: 


DMH3143W Assignment to the locator referenced 

pointer (name) was ignored. 


unsupported substitution statement and was not able to 

resolve the locator reference for the pointer. 






Module: 


DMH3144W Multiple assignment to pointer (name) 

was ignored. 

Explanation: The Compiler Based Scanner detected 

multiple substitution statements that updated the 

pointer value and was not able to resolve the locator 







Module: 


DMH3145W INIT locator reference for pointer (name) 

was ignored. 


unsupported expression in the INIT attribute clause for 

the pointer and was not able to resolve the locator 







Module: 


DMH3146W Assignment to pointer (name) was 

ignored. 


unsupported substitution statement and was not able to 

resolve the locator reference for the pointer. 






Module: 

DMH3180E 

Explanation: 

application. 



Module: 

DMH3181E 

Explanation: 

application. 



Module: 


Fail to create internal data. 






Fail to modify internal data. 






DMH3190W SYSADATA has some invalid data. Skip 

EXEC statement parser. 

Explanation: 

in ADATA. 


processing. 

Found invalid data for EXEC statement 

Skip the EXEC statement and continue 




Module: 

DMH3202E 


An EXEC statement did not end in an 

include file. (name) 


EXEC statement that did not end in a file. The scanner 

was not able to handle the EXEC statement using 

regular INCLUDE scanning. 



User response: Correct the source file to avoid the 

problem and reattempt the analysis. Or, reattempt the 

analysis with the Compiler Based Scanner using 



enhanced INCLUDE scanning. 

Module: 

DMH3203E 


A CICS value data 

(DFHRESP,DFHVALUE) did not end in 

a file. (%1) 

Explanation: The Compiler Based Scanner detected a 

CICS value data on a statement that did not end in a 

file. The scanner was not able to handle the statement 

using regular INCLUDE scanning. 



User response: Correct the source file to avoid the 

problem and reattempt the analysis. Or, reattempt the 

analysis with the Compiler Based Scanner using 

enhanced INCLUDE scanning. 

Module: 


DMH3204W Member name was truncated to 8 

characters: name 

Explanation: Scanner encountered a long 

copy/include member name. 

System action: Scanner truncates the name, and 

continues processing 

User response: Correct the copy/include member 

name, and reattempt the analysis. 

Module: 

DMH3205E 


A recursive reference was found on the 

process of the include file. (%1) 

Explanation: Scanner encountered the same copybook 

on the preprocessing for a copybook. 

System action: The scanner terminates the current 

analysis and continues the inventory process for the 

next programing asset. 



Module: 

DMH3800E 

Explanation: 

application. 



Module: 


The stack of the EXEC parser is 

overflowed. 





DMH3801E 

Found an unsupported syntax at 'token'. 

Ignore this EXEC statement. 

Explanation: The scanner found unsupported syntax 

in an EXEC statement at the location indicated by token. 

System action: Ignore the EXEC statement and 

continue the processing. 

User response: Correct the EXEC statement if it is not 

valid. If the statement is valid, contact IBM Software 

Support. 

Module: 

DMH3802E 


Found unexpected end of statement. 

Ignore the EXEC statement. 

Explanation: The scanner found an invalid ending of 

an EXEC statement. 

System action: Ignore the EXEC statement and 

continue the processing. 

User response: Correct the EXEC statement if it is not 

valid. If the statement is valid, contact IBM Software 

Support. 

Module: 

DMH3803E 

Explanation: 

application. 



Module: 


Internal data error. 





DMH3804W Declaration of dataelement was not 

found. 

Explanation: The scanner found an undeclared data 

element in an EXEC statement. 



valid. 

Module: 

DMH3805E 

Explanation: 

application. 



Module: 


Correct the EXEC statement if it is not 


Memory error. 







DMH3806W Token name is too long. 

Explanation: 

long. 


continues. 


Module: 

The scanner found a token that is too 

The token is truncated and processing 

None 


DMH3807W Label name was not found. 

Explanation: 

found. 



valid. 

Module: 

DMH3808E 

The label in an EXEC statement was not 


Correct the EXEC statement if it is not 


Missing quotation mark. (line number, 

file name) 

Explanation: Scanner encountered a literal which was 

not properly enclosed with quotation 

marks/apostrophes. 

System action: Scanner terminates the analysis and 

continues the processing for the next programming 

asset. 



Module: 


DMH3809W An unresolved reference to table/view 

correlation name name was found. It is 

ignored. 

Explanation: A scanner encountered a correlation 

name for table/view on the source line, but it was 

impossible to resolve the correlation name, because it 

referred to multiple tables/views. 


Scanner ignores the reference. 

User response: None. It is a limitation of the static 

program analysis. If you improve the analysis, 

explicitly qualify the reference with table/view name 

by modifying the source program. 

Module: 

DMH5010E 


Resource is null: name 

Explanation: 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. 

User response: 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 Rational Asset 

Analyzer. 

Module: 

DMH5011E 

WsaaJar 

Errors occurred while loading and 

parsing file 'filename'. 

Explanation: At least one error occurred while loading 

and parsing the contents of 'filename'. 



Module: 

DMH5012E 

WsaaJar 

Stop request processing. 

Check the log file for the list of errors. 

Attempt to retrieve unknown 'type' 

model object with name 'name'. 

Explanation: The code attempted to retrieve an object 

of name 'name' and type 'type' which was not created 

during static initialization. Possible causes include: 

1. Problem loading external configuration files 

2. Misconfigured database 

3. Syntax error in the code 



information. 

Module: 

DMH5013I 

WsaaJar 

Stop request. 

Check the log file for more 

Annotation text has been updated for 

component. 

Explanation: The annotation text submitted was 

successfully added to the component. 

System action: The annotation text has been updated 

in the database. 


Module: 

DMH5014E 

Explanation: 

WsaaJar 

None 

Annotation text cannot exceed maximum 

annotation length characters. 

The annotation text is too long. 

System action: Processing stops and the annotation 

text is not added to the component. 

User response: Rewrite the annotation text to have 

less than maximum annotation length characters and 

submit the annotation again. 

Module: 

WsaaJar 



DMH5015E 

The character "invalid character" is 

invalid. Valid characters are: valid 

characters 

Explanation: Application names can contain uppercase 

letters, numbers, and the characters #, @, _, and $. 

System action: Processing stops. The user is prompted 

again for the application name. 

User response: Remove the "invalid character" character 

from the application name and try your operation 

again. 

Module: 

DMH5016E 

Explanation: 

WsaaJar 

No concatenation name was specified. 

A concatenation set requires a name. 


again for the concatenation set name. 

User response: Try your operation again after 

specifying a name for the concatenation set. 

Module: 

DMH5017E 

WsaaJar 

Invalid character "invalid character" at 

position invalid character position. 

Explanation: Concatenation set names can contain 

uppercase letters, numbers, and the characters #, @, and 

$. 




removing the invalid characters from the concatenation 

set name. 

Module: 

DMH5018E 

WsaaJar 

The first character cannot be numeric. 

Explanation: Concatenation set names cannot start 

with a number. 




removing the invalid characters from the concatenation 

set name. 

Module: 

DMH5019E 

Explanation: 

unique. 

WsaaJar 

The concatenation set "name" already 

exists. 

Concatenation set names must be 


again for a unique concatenation set name. 


specifying a unique concatenation set name. 

Module: 

DMH5020E 

WsaaJar 

Cannot get resource, zip: name inner 

path: pathname 

Explanation: The scanner cannot access the specified 

resource from the zip file. 

System action: Scanning of the current asset is 




Module: 

DMH5023E 

WsaaMain 

Verify that the zip file is not corrupted. 

The information of attribute in object is 

not available. 

Explanation: Information required to fully display 

graphics is not available from the database. 

System action: Processing stops and some or all of the 

graphic cannot be displayed. 

User response: The database is in an inconsistent 

state. Contact IBM Software Support. 

Module: 

DMH5024E 

WsaaJar 

The list of component is not available. 

Explanation: Information required to fully display 

graphics is not available from the database. 

System action: Processing stops and some or all of the 

graphic cannot be displayed. 



Module: 

DMH5025E 

Explanation: 

the request. 

WsaaJar 



Module: 

DMH5026E 

An unexpected error was encountered. 

error message 

WsaaJar 

An exception occurred while processing 

Request processing stopped. 


The following error was returned from 

DB2: sql error message 

Explanation: An exception occurred while interacting 

with the database. 



Request processing stopped. 




Module: 

DMH5027E 

WsaaJar 

No data set name specified. 

Explanation: In the "Collect inventory" wizard, the 

MVS library was not specified. 

System action: Processing stops and the user is 

prompted again for the location to be inventoried. 

User response: Enter in the location of data to be 

inventoried and try your operation again. 

Module: 

DMH5028E 

WsaaJar 

Invalid first character in the data set 

name. 

Explanation: Data set name must start with: 

v an alphabetic character (A to Z) 

v the special character @, #, or $ 

System action: Processing stops and the user is 

prompted again for the location to be inventoried. 

User response: Verify that the data set name starts 

with a valid character and try your operation again. 

Module: 

DMH5029E 

WsaaJar 

Invalid character "invalid character" inthe 

data set name. 

Explanation: Data set name must only contain: 

v an alphabetic character (A to Z) 

v the special characters @, #, or $ 

v a hyphen (-) 

v numeric (0 to 9) characters 

System action: The user is prompted again for the 

location to be inventoried. 

User response: Verify that the data set name contains 

only valid characters and try your operation again. 

Module: 

DMH5030E 

WsaaJar 

Exception while trying to analyze 

resource name 

Explanation: An I/O error occurred while trying to 

analyze the Java resource specified by name. 

System action: Analysis of the current asset is 



User response: 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. 

Module: 

WsaaJar 

DMH5031I 

Loading Scanner Manager scanner 

instance 

Explanation: Informational message logged to indicate 

that the appropriate scanner is being loaded so that 

scanning can begin. 



Module: 

DMH5032E 


None 

WsaaMain 

Encountered an unexpected error in 

scanner. Exception: returncode 

Explanation: An unexpected error occurred during the 

initialization of the schema or during the scanning 

operation itself. The exact error is indicated. 

System action: The scanning process is stopped for 

the current asset, and processing does not continue. 


User response: 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. 

Module: 

DMH5033E 

WsaaMain 

Unable to scan into name 

Explanation: 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. 

System action: The scanning process ends for the 

specified scanning root. The error is logged, and 

scanning will continue on the next scanning root. 

User response: Verify that the specified scanning root, 

directory, file, or resource is available, defined correctly, 

accessible, and contains valid content. Try the scanning 


Module: 

DMH5034I 

WsaaMain 

For more information, please refer to the 

error log file. 


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), problems with database access, or problems 



during scanning and analysis. 



User response: View information in one of several 

error and information log files on the distributed server 

in the \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. 

Module: 

DMH5035E 

WsaaMain 

Unique scanner letter already in use by 

another scanner; you should pick 

another one for this scanner: name 

Explanation: Rational 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 Rational Asset 

Analyzer. This error typically occurs after a new 

scanner has been added. 

System action: 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. 

User response: Ensure that you have correctly defined 

the specified scanner in /assetloc/config/ 

Scanners.cfg and attempt the scanning operation 

again. 

Module: 

DMH5036E 

Explanation: 

WsaaMain 

An asterisk (*) may only appear as the 

first or last character of the filter. 

The filter cannot have an inner wildcard. 


filter of the inventory. 

User response: Remove the wildcard asterisk (*) from 

the middle of the filter and submit again. 

Module: 

DMH5037E 

WsaaJar 

Scanner could not be loaded or 

instantiated: cause 

Explanation: 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 Rational ® Asset Analyzer installed 

code, or to the environment classpath. This error 

typically occurs when a new scanner has been added 

incorrectly. 

System action: 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. 


the specified scanner in the configuration file. If the 

error cannot be corrected, capture all logs related to the 

error and Contact IBM Software Support. 

Module: 

DMH5038E 

WsaaMain 

Error while trying to get an input stream 

for resource name 

Explanation: 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. 




User response: 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. 

Module: 

DMH5039I 

WsaaJar 

Deleting old resources from database 

Explanation: This is an informational message written 

to the logs indicating that old resources are being 

deleted from the database prior to writing new 

resources. 



Module: 

DMH5042E 


None 

WsaaMain 

Error encountered while trying to parse 

name 

Explanation: 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. 




User response: 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 IBM Software 

Support. 

Module: 

WsaaJar 



DMH5043I 

Succeeded in creating log files. 


to the logs indicating that the log files themselves were 

successfully created. 



Module: 

DMH5044I 


None 

WsaaMain 

Succeeded in initializing the database. 


to the logs indicating that the distributed scanner 

successfully initialized the Rational Asset Analyzer 

database so that processing can continue. 



Module: 

DMH5045I 


None 

WsaaMain 

Succeeded in fully initializing 

application. 


to the logs indicating that the distributed scanner has 

been successfully initialized. 



Module: 

DMH5046E 


None 

WsaaMain 

An unsupported character found in name 

Explanation: An unexpected error has occurred 

during parsing, which can be caused by the occurrence 

of an unsupported character in the specified resource. 




User response: Examine the resource for any 

unsupported characters and attempt the scanning 

operation again after correcting the error. 

Module: 

DMH5047E 

WsaaMain 

Error reading configuration file name 

Explanation: The specified configuration file could not 

be read for any of the following reasons: 

v It cannot be found in the search path identified by 

the configuration parameters set up during 

installation of . 

v It does not have the correct file permissions for read 

access. 

v It does not conform to its specification due to 

changes made by the user. 

System action: The scanning process stops for all 

assets. The scanner will not be able to function until the 

error is fixed. 

User response: 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 Rational 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. 

Module: 

DMH5048E 

WsaaMain 

Error creating log directory 

Explanation: An unexpected error has occurred while 

trying to create the log directory required for Rational 

Asset Analyzer. An attempt is made to create the log 

directory off of the Rational Asset Analyzer root 

installation directory, in \log. 




User response: Ensure that you have correctly 

installed Rational 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 Rational Asset Analyzer 

runtime. The directory in which Rational Asset 

Analyzer is installed must have the correct permissions 

so that Rational Asset Analyzer can create the directory 

and the logs. The directory name must be set in 

common.cfg using the logDir parameter. 

Module: 

DMH5049E 

WsaaJar 

Error creating log files 


trying to create the logs required for Rational 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. 





installed Rational Asset Analyzer according to 

directions in the Configuration and Migration Guide and 

that adequate space exists to create the logs during 

Rational Asset Analyzer runtime. The directory in 

which Rational Asset Analyzer is installed must have 

the correct permissions so that Rational Asset Analyzer 

can create the logs and Common.cfg must point to the 

correct log directory. 

Module: 

WsaaJar 



DMH5054E 

Exception while trying to create the 

database. 

Explanation: An unexpected error occurred while 

trying to connect to the Rational Asset Analyzer 

database. The logs will contain more specific 

information about the error. 




User response: 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. 

Module: 

DMH5056E 

WsaaJar 

An unexpected exception occurred 

during analysis of name. 

Explanation: 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 Rational Asset Analyzer logs. 




User response: Refer to the Rational 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. 

Module: 

DMH5057E 

WsaaJar 

An unexpected exception occurred 

during scanning. For more information 

please refer to the error log file. 


during the scanning process. The cause may be related 

to initialization and setup activities, problems removing 

existing resources from the Rational Asset Analyzer 

database, or problems scanning the resources 

themselves. More detailed information can be found in 

the Rational Asset Analyzer logs. 

System action: 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. 


logs to determine the problems, correct them, and 

attempt the scanning operation again. Contact your 

IBM technical-support representative if the problems 

persist. 

Module: 

DMH5058E 

WsaaJar 

An unexpected exception occurred while 

writing the file name to the database. 

Explanation: An unexpected error was encountered 

while attempting to write metadata about the specified 

resource to the Rational Asset Analyzer database. More 

information about this error can be found in the 

Rational Asset Analyzer logs. 


skipped, and processing continues for the next asset. 



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. 

Module: 

DMH5059I 

WsaaJar 

Scanner Manager finished. Next time to 

scan: timestamp 

Explanation: This is an information message 

documenting the status of the scanning process. 



Module: 

DMH5060I 

WsaaJar 


None 

Timer is set on; Scanner will scan at: 

timestamp 


documenting the status of the scanning process. 



Module: 

DMH5061E 

WsaaJar 


None 

Cron thread was interrupted 

Explanation: An exception occurred due to an 

unexpected interruption of the scanner while it is in 

sleep mode or otherwise paused by a user. 

System action: The scanning process, even in sleep 

mode, is stopped. 

User response: 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 Rational Asset Analyzer logs for 

further information and attempt the scanning operation 

again. 

Module: 

WsaaJar 



DMH5062I 

ShouldUseTimer is set to false; scanner 

will scan now! 


indicating that the ShouldUseTimer property in 

/assetloc/config/Admin.cfg is set to false so that 

scanning begins immediately upon invocation. 


The scanning will begin processing upon invocation. 

User response: If you wish to delay scanning, you 

must set the ShouldUseTimer property to true and set 

a value for the TimeToCrawl property. 

Module: 

WsaaJar 



Module: 

DMH5071I 

WsaaJar 


None 

Scanning... 


to the Rational Asset Analyzer log indicating that a 

resource is currently being scanned. 



Module: 

WsaaJar 


None 

DMH5063W Time to scan not found in configuration 

file; will scan now! 

Explanation: This is a warning message written to the 

Rational 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. 


Scanning will begin upon invocation. 

User response: If you wish to delay scanning, you 

must set the ShouldUseTimer property to true and set 

a value for the TimeToCrawl property. 

Module: 

WsaaJar 

DMH5064W Error while trying to compute the time 

to sleep...will scan now! 


Rational 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. 


Scanning will begin upon invocation. 

User response: If you wish to delay scanning, ensure 

that you have correctly specified the value for the 

TimeToCrawl property. 

Module: 

DMH5069I 

WsaaJar 

Application has been set up to run in 

mode 

Explanation: 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. 

DMH5073I 

analyze... 



resource is currently being analyzed. 



Module: 

DMH5074I 

WsaaJar 


None 

analyzed... 



resource has been analyzed. 



Module: 

DMH5075I 

WsaaJar 


None 

done. 


to the Rational Asset Analyzer log indicating that the 

scanning process has completed. 



Module: 

DMH5077I 

WsaaJar 


None 

skip. (not supported) 



analysis process has been skipped for a resource type 

that is not supported. 



Module: 

WsaaJar 


None 



DMH5078I 

Bad resource; skipping. 



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. 


scanning continues with the next asset. 

User response: Determine if the asset skipped is 

corrupted and attempt to correct it. If the problem 


Module: 

DMH5079I 

WsaaJar 

Softlink, will not scan into. 



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. 

System action: The softlink asset is skipped, and 

scanning resumes with the next asset. 


Module: 

DMH5080I 

WsaaJar 

None 

Extracting file name 



specified resource is being extracted for analysis. 



Module: 

DMH5081E 


None 

WsaaMain 

Extractor could not be loaded or 

instantiated 

Explanation: This is an unexpected error in which an 

extractor for use in obtaining resources of a specific 

type supported by Rational Asset Analyzer could not 

be instantiated. The error is related to an inconsistency 

in the Rational Asset Analyzer installed code or the 

environment classpath. 

System action: 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. 

User response: Verify that Rational 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 


Module: 

DMH5082E 

WsaaMain 

Bad resource; extracting stopped. 

Explanation: 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 Rational 

Asset Analyzer logs. 

System action: Scanning on the current asset is 

skipped, and the error is logged. Processing continues 

for the next asset. 


logs for details on the exception, correct any errors, and 


IBM technical-support representative if the problem 

persists. 

Module: 

DMH5083E 

WsaaMain 

Bad entry in an archive; skipping. 

Explanation: An exception was encountered during 

the extraction of a particular asset during the scanning 

process. 

System action: Extraction and scanning of the current 

asset is skipped, and the error is logged. Processing 

continues for the next asset. 


logs for specific details on the extraction process that 

encountered the error. Correct the problem, if possible, 

and attempt the scanning operation again. 

Module: 

DMH5084E 

WsaaMain 

The view is not a directory; skipping. 

Explanation: During scanning of resources in a 

ClearCase ® repository, a view has been specified or 

encountered that is not a valid directory. 

System action: Scanning of the current view is 

stopped, and the error is logged. Processing continues 

with the next scanning root. 


logs for more detail and correct the problem, if 

possible. Consult your Rational Asset Analyzer 

administrator or your ClearCase repository 

administrator for more information. 

Module: 

DMH5085E 

WsaaJar 

Exception while executing lsview 

command. 


ClearCase repository, an unexpected I/O error occurred 

or the process was interrupted while trying to invoke 

the ClearCase lsview command. 



System action: 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. 






Module: 

DMH5086E 

WsaaJar 

Exception while executing mkview 



ClearCase repository, an unexpected I/O error occurred 

or the process was interrupted while trying to invoke 

the ClearCase mkview command. 


stopped, and the error is logged. Scanning resumes 

with the next view. 






Module: 

DMH5087E 

WsaaJar 

mkview command failed. exit code: 

returncode 


ClearCase repository, the ClearCase mkview command 

was issued but failed to complete successfully, 

returning the specified error code. 





logs or consult your ClearCase documentation for more 

information on the specific error code. Consult your 

Rational Asset Analyzer administrator or your 

ClearCase repository administrator for more 

information. 

Module: 

DMH5088E 

WsaaJar 

Exception while executing setcs 



ClearCase repository, the ClearCase setcs command 

was issued but failed to complete successfully due to 

an exception. 









Module: 

DMH5089E 

WsaaJar 

setcs command failed. exit code: 

returncode 


ClearCase repository, the ClearCase setcs command 

was issued but failed to complete successfully, 

returning the specified error code. 









information. 

Module: 

DMH5090E 

WsaaJar 

Failed to create the views target 

directory name. 


ClearCase repository, Rational Asset Analyzer was 

unable to create the views target directory specified. 









information. 

Module: 

DMH5091I 

WsaaJar 

Signal end of scan to servlet 


indicating that the scanning process has completed. 



Module: 

WsaaJar 


None 



DMH5092E 

Unable to retrieve host info (name & IP) 

- see log for details. 

Explanation: During initialization of the scanner, 

Rational Asset Analyzer was unable to retrieve host 

information for the location of the Rational Asset 

Analyzer host system. 

System action: The scanning process cannot be 

initialized and is stopped. The error must be corrected 

before scanning can function properly. 

User response: Verify that you have correctly installed 

Rational Asset Analyzer, specifying all valid host 

information according to the instructions in the 

Configuration and Migration Guide. Correct the problem 


Module: 

DMH5093E 

WsaaJar 

Unknown module type: type 

Explanation: An invalid module type, as specified, 

was encountered during analysis of an ear file. Valid 

module types are war modules, Web modules, and ejb 

files. 


skipped, and the error is logged. Processing continues 

with the next asset. 

User response: Ensure that the resources being 

scanned contain valid modules. Correct any problems 


Module: 

WsaaJar 

DMH5095E 

Cannot open temp file to Archive File: 

name 

Explanation: 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. 



User response: Ensure that the temporary file exists 

and can be accessed. Consult the Rational Asset 

Analyzer logs for more detailed information on the 

error. 

Module: 

DMH5096E 

WsaaJar 

Illegal Load Strategy: strategy 

Explanation: 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. 



User response: This error reflects an unusual 

condition in the Rational Asset Analyzer scanner. 

Consult the Rational Asset Analyzer logs for more 

details on the exception. Contact your IBM 

technical-support representative if the problem persists. 

Module: 

WsaaJar 

DMH5094E 

Cannot read InputStream to temp file 

name 

Explanation: 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 Rational Asset 

Analyzer exceptions while attempting to read or parse 

the resource. 



User response: Ensure that your Rational Asset 

Analyzer Windows server has adequate space for 

creating temporary files and that the appropriate 

directory and file permissions exist. Your Rational Asset 

Analyzer logs may contain more detailed information 

about the exception. Contact your IBM 

technical-support representative if the problem persists. 

Module: 

WsaaJar 

DMH5097E 

Not an EJBJarFile: name 

Explanation: An exception occurred during scanning 

of the specified resource because an EJB was expected 

but the resource is not an EJB file. 



User response: Make sure that Rational Asset 

Analyzer is properly installed and the classpath is set 

correctly. 

Module: 

WsaaJar 

DMH5098E Unable to access Site in the database - 

see log for details. 

Explanation: During initialization of the scanner, 

Rational Asset Analyzer was unable to site information 

that should already exist in the database system. The 

process cannot continue. 




User response: Verify that you have correctly installed 

Rational 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 

Rational Asset Analyzer logs for more information. 

Module: 

DMH5099E 

WsaaJar 

Persistency object problems - see log for 

details. 

Explanation: 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. 




User response: Consult the Rational Asset Analyzer 

logs for more information related to possible database 

communications errors. Contact IBM Software Support. 

Module: 

DMH5100E 

WsaaJar 

Dependent analyzer(s): name not 

available or not configured to run. 


postprocessing because required analyzers could not be 

accessed. The most likely cause is that the analyzers are 

not configured properly. 

System action: Processing for the specified 

postprocessor is skipped, and the error is logged. 

Processing continues for the next postprocessor. 

User response: 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. 

Module: 

DMH5101E 

WsaaJar 

Dependent postprocessor name not 



postprocessing because required postprocessors could 

not be accessed. The most likely cause is that the 

postprocessors were not configured properly. 

System action: Processing for the specified 

postprocessor is skipped and the error is logged. 


User response: 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. 

Module: 

DMH5102E 

WsaaJar 

type categorization not performed due to 

an error 

Explanation: During postprocessing, an exception 

occurred while attempting to categorize the resources 

analyzed. 

System action: Postprocessing is skipped for the 

categorization type specified, and the error is logged. 

Processing continues for the next categorizer. 

User response: Consult your Rational Asset Analyzer 

administrator or your IBM technical-support 

representative. 

Module: 

DMH5103I 

WsaaJar 

Categorization was not set to be 

activated 

Explanation: During postprocessing, categorization 

was not performed because it was not activated. 


Categorizer postprocessors are skipped. 

User response: If you want the categorizer 

postprocessors to run, set the Java virtual machine 

property Categorizer to true. 

Module: 

DMH5104E 

Explanation: 

WsaaJar 


pattern. 

The file pattern cannot contain blanks. 

The file pattern cannot contain blanks. 

The user is prompted again for the file 

User response: Remove the blanks from the file 

pattern and submit the request again. 

Module: 

DMH5105E 

WsaaJar 

Unexpected exception in calling class: 

details 

Explanation: An unexpected condition occurred when 

trying to make a remote request. 

System action: The exception is logged and displayed 

to the user. Current ® processing stops. 

User response: Contact your system administrator to 

ensure that the Rational Asset Analyzer remote request 

server is properly configured. To verify, ensure that the 

DMHINSTL panel setup option has the correct 

information for the CGI Settings section. Verify that the 

Web server's httpd.conf file has the proper Web path 

for the Rational Asset Analyzer CGI (for example, 

dmh-cgi) and that the Web server has been started. 

Module: 

WsaaJar 



DMH5106E 

The SQL is not a SELECT statement. 

Explanation: The SQL statement did not have the verb 

SELECT in it. 



Module: 

DMH5107E 

Explanation: 

WsaaJar 

The SQL query was not executed. 


Container(s) not found: names. 

Valid containers must exist. 


again for the container names. 

User response: Try your operation again after adding 

only containers that exist. 

Module: 

DMH5108E 

Explanation: 

WsaaJar 

No container names specified. 

A container name must be specified. 


again for the container names. 

User response: Add a valid container name or click 

the cancel button. 

Module: 

DMH5109E 

WsaaJar 

Please specify the new application 

name. 

Explanation: The application name is required if the 

inventory is to be added to a new application. 


for the application name. 

User response: Specify a new application name, an 

existing application, or do not add the inventory to an 

application at this time. 

Module: 

DMH5110I 

Explanation: 

WsaaJar 



Module: 

DMH5111E 

Explanation: 

Impact analysis is being performed. 

WsaaJar 



Impact analysis is being performed. 


None 

An error occurred during impact 

analysis: error cause 

An unexpected exception was thrown. 

Impact analysis processing has halted. 


Module: 

DMH5112I 

Explanation: 

WsaaJar 



Module: 

DMH5113I 

The concatenation set has been 

assigned. 

WsaaJar 

The concatenation set has been assigned. 


None 

The default concatenation sets for the 

component have been updated. 

Explanation: The default concatenation sets for the 

component have been updated. 



Module: 

DMH5114I 

WsaaJar 


None 

Added the scanning request to the 

queue. 

Explanation: The scanning request has been queued 

and will be run when the scans in front of it have 

finished. 



Module: 

DMH5115E 

Explanation: 

WsaaJar 


None 

The impact analysis name "ia name" 

already exists. 

Impact analysis names must be unique. 


again for a unique impact analysis name. 


specifying a unique impact analysis name. 

Module: 

DMH5116I 

Explanation: 

WsaaJar 



Module: 

DMH5117E 

The impact analysis has been renamed. 

WsaaJar 

The impact analysis has been renamed. 


None 

The impact analysis cannot be renamed 

with "new name". 

Explanation: The new impact analysis name must not 

be blank, must not be the old name, and must be 

unique. 




again for a new impact analysis name. 


specifying a unique impact analysis name. 

Module: 

DMH5118I 

WsaaJar 

The description for impact analysis "ia 

name" has been updated. 

Explanation: The description of the impact analysis 

has been updated. 



Module: 

WsaaJar 


None 

System action: Processing stops. The impact analysis 

was not created successfully. 


Module: 

DMH5123E 

WsaaJar 


The description for impact analysis "ia 

name" cannot be updated. 

Explanation: The description for the impact analysis 

cannot be updated. 

System action: Processing stops. The description of 

the impact analysis remains the same. 


Module: 

WsaaJar 


DMH5119I 

Explanation: 

changed. 



Module: 

DMH5120I 

Explanation: 

The type of asset "ia name" tobe 

analyzed has changed. 

WsaaJar 



Module: 

The type of asset to be analyzed has 


None 

The impact analysis "ia name" has been 

created. 

WsaaJar 

The impact analysis has been created. 


None 

DMH5121W The impact analysis "ia name" has 

already been created. Update the name 

to create a new impact analysis. Click 

button to continue with the impact 

analysis. 

Explanation: The impact analysis "ia name" has already 

been created. 


for again. 

The impact analysis name is prompted 

User response: Update the name to create a new 

impact analysis. Click button to continue with the 

impact analysis. 

Module: 

DMH5122E 

WsaaJar 

The impact analysis name "ia name" 

could not be created. 

Explanation: There was an error while trying to create 

the impact analysis. This is most likely due to duplicate 

name for the current user. 

DMH5124E 

Explanation: 

name. 

Please specify the new impact analysis 

name. 

The impact analysis requires a nonblank 


again for an impact analysis name. 


specifying an impact analysis name. 

Module: 

DMH5125E 

WsaaJar 

Invalid character "char" at position pos. 

Explanation: The impact analysis has a character that 

is not allowed in the name. 



User response: Verify that the impact analysis name 

only contains valid characters and try your operation 

again. 

Module: 

DMH5126E 

Explanation: 

analysis 

WsaaJar 

Please specify a description for the 


Description is required for the impact 


again for an impact analysis description. 

User response: Enter a description and try your 


Module: 

WsaaJar 



DMH5127E 

Explanation: 

analysis. 

Please select a type of asset for the 


Asset type is required for the impact 


again for an asset type. 

User response: Fill in the asset type and try your 


Module: 

DMH5128E 

WsaaJar 

The impact analysis name is too long. 

Explanation: Impact analysis names must be less than 

or equal to 64 characters long. 




specifying a shorter impact analysis name. 

Module: 

DMH5129E 

WsaaJar 

The description is too long. 

Explanation: Impact analysis description must be less 

than or equal to 256 characters long. 


again for an impact analysis description. 


specifying a shorter impact analysis description. 

Module: 

DMH5130E 

WsaaJar 

Cannot link resources: analyzed 

asset-->new asset 

Explanation: During analysis, an unexpected SQL 

error has occurred while trying to add references 

between two assets managed by Rational Asset 

Analyzer. The assets that could not be related are 

specified. 





logs for more details on the SQL error. Ensure that you 

have installed Rational Asset Analyzer properly 

according to the Configuration and Migration Guide. 

Contact your IBM technical-support representative for 

more information. 

Module: 

WsaaJar 

DMH5132E 

The system property wsaaConfig is not 

defined. 

Explanation: The system property wsaaConfig must 

be defined. It points to the Rational Asset Analyzer 

configuration directory and is set during installation of 

the product. The value can be found in the JVM 

Custom properties for WebSphere ® Application Server. 

System action: The servlet initialization or scanning 

process stops and will not be able to function until the 


User response: Verify that you have successfully 

installed and configured Rational Asset Analyzer 

according to the instructions in the Configuration and 

Migration Guide. If you cannot verify that, check the 

value of wsaaConfig in the Custom properties of your 

WebSphere Application Server on MVS or Windows by 

using the Administrative Console. If you update the 

value, remember to restart WebSphere Application 

Server. 

Module: 

DMH5133E 

WsaaJar 

Analyzer could not be loaded or 

instantiated: analyzerType 

Explanation: This is an unexpected error in which an 

analyzer defined in /assetloc/config/Analyzers.cfg 


errors in specifying the postprocessor, or an 

inconsistency in the Rational Asset Analyzer installed 

code, or the environment classpath. 

System action: 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. 


the specified analyzer in the configuration file. If the 



Module: 

WsaaJar 

DMH5134W Warning - an analyzer of the following 

type does not exist: name. 

Explanation: An analyzer for the specified type does 

not exist because it has not been defined in 

/assetloc/config/Analyzers.cfg. 

System action: Analysis using this analyzer will not 

be performed. The error is logged, and processing 

continues for the next set of valid assets. 

User response: Add the analyzer definition to the 

Analyzers.cfg file and perform the scanning operation 

again. 

Module: 

WsaaJar 



DMH5135W Warning - a resource mapping already 

exists for extension fileextension. 

Explanation: This is a warning indicating that 

multiple analyzers have been defined in 

/assetloc/config/Analyzers.cfg for the same resource 

type. 

System action: The first analyzer encountered will be 

used, and subsequent analyzers will be ignored. 

Processing continues normally. 


the analyzers and their resource type mappings and 

perform the scanning operation again. 

Module: 

DMH5136E 

WsaaJar 

Error while trying to run the name 

postprocessor. 

Explanation: An unexpected error has been 

encountered while attempting to run the specified 

postprocessor. The specific cause of the error will be 

found in the Rational Asset Analyzer error logs. 

System action: Postprocessing is stopped for the 

specified postprocessor. The error is logged and 



error logs for specific information on the error. Correct 

any problems and perform the scanning operation 

again. 

Module: 

DMH5137E 

WsaaJar 

name postprocessor could not be loaded 

or instantiated. 


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 Rational Asset 

Analyzer installed code or the environment classpath. 



processing continues. Other postprocessors that depend 

on the one that could not be loaded may be affected. 


the specified postprocessor in the configuration file. If 

the error cannot be corrected, capture all logs related to 

the error and Contact IBM Software Support. 

Module: 

DMH5138I 

WsaaJar 

name postprocessor: started running 


indicating that the specified postprocessor has started. 




Module: 

DMH5139E 

WsaaJar 

None 

Unexpected exception occurred in name 



during postprocessing for the specified postprocessor. 

More specific information about the error can be found 

in the Rational Asset Analyzer error logs. 





error logs for specific information on the error. Contact 

your IBM technical-support representative if you 

cannot resolve the problems. 

Module: 

DMH5140E 

WsaaJar 

Dependent analyzer(s): name not 


Explanation: 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. 

System action: The postprocessor that caused the 

error is stopped. The error is logged and processing 

continues. 


specified all required analyzers in the configuration file 

and perform the scanning operation again. 

Module: 

DMH5141E 

WsaaJar 

Dependent postprocessor name not 


Explanation: While running postprocessing, the 

specified postprocessor is required but not configured 

in /assetloc/config/EColabraApplicaiton.cfg. 

Postprocessing cannot continue. 





specified all required postprocessors in the 

configuration file and perform the scanning operation 

again. 

Module: 

WsaaJar 



DMH5142E 

Dependent postprocessor name was 

defined to run after this post processor, 

although this postprocessor depends on 

it. Please rearrange the order of 

invoking the postprocessors in the 

configuration files. 

Explanation: The definition of the specified 

postprocessor is incorrect in /assetloc/config/ 

EColabraApplication.cfg. Postprocessing cannot 

continue. 


dependent. The error is logged and processing 

continues. 


specified the postprocessors in the configuration file 

and perform the scanning operation again. 

Module: 

DMH5143E 

WsaaJar 

Dependent postprocessor name failed. 

Explanation: During postprocessing, a dependent 

postprocessor failed to complete successfully. Details 

about the error can be found in the Rational Asset 

Analyzer error logs. 


dependent postprocessor. The error is logged and 



specified the postprocessors in the configuration file. 

Consult the Rational 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. 

Module: 

WsaaJar 

DMH5144W The following resource mapping will be 

ignored: resourcetype= analyzer. 


Rational 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. 





specified one, and only one, analyzer per resource type 

in the /assetloc/config/Analyzers.cfg file and 

attempt the scanning process again. 

Module: 

WsaaJar 

DMH5145I 

Deleting old resources from database 


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. 



Module: 

WsaaJar 


None 

DMH5146W Warning: Servlet may be down or 

unavailable exceptioncode. 

Explanation: This is a warning message that occurs 

when the scanning process has completed and attempts 

to notify the Rational Asset Analyzer servlet. The 

exceptioncode provides the reason for the unavailability. 

System action: 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. 


Module: 

DMH5147E 

WsaaJar 

None 

Tried to scan from multiple sites, now 

from "server1" while a previous site 

exists. 

Explanation: 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 

Rational Asset Analyzer does not support multiple sites 

at this time. Scanning must be performed on a single 

Rational Asset Analyzer Windows server. 


The scanning process is stopped. 

User response: Perform the scanning operation again 

on the Rational Asset Analyzer Windows server used 

previously as specified in the database. 

Module: 

DMH5148E 

WsaaJar 

Invalid first character for the file name: 

file name 

Explanation: The first character in a file name must be 

alphabetic, #, @, or $. 


name. 


request again. 

Module: 

WsaaJar 


Correct the file name and submit the 



DMH5149E 

Invalid character "invalid character" in file 

name "file name". 

Explanation: Valid characters are only upper case 

letters, numbers, special characters (#, @, and $), the 

asterisk (*) and the question mark (?). 


name. 



Module: 

DMH5150E 

WsaaJar 



ScannerManager was not initialized 

prior to access 

Explanation: This is an unexpected error indicating 

that the proper initialization could not be performed to 

start the distributed scanning processor. This error may 

be caused by a Rational Asset Analyzer installation 

error or a problem with the classpath. 

System action: The scanning process is stopped, and 

the error is logged. 

User response: Consult your Rational Asset Analyzer 

error logs and contact your IBM technical-support 

representative if the issue cannot be resolved. 

Module: 

DMH5151E 

WsaaJar 

name retriever could not be loaded 


scanner defined in /assetloc/config/Scanners.cfg 


errors in specifying the postprocessor, or an 


code or the environment classpath. 

System action: 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. 


the specified scanner in the configuration file. If the 



Module: 

DMH5152E 

WsaaJar 

File name too long: file name 

Explanation: File names can be only eight characters 

for PDS members and ten characters for Panvalet. 


name. 



Module: 

WsaaJar 



DMH5153E 

Explanation: 

The application name already exists. 

Application names must be unique. 


application name. 


try again. 

Module: 

DMH5154E 

WsaaJar 

Type in a unique application name and 

The application name is too long. 

Explanation: The application name must be less than 

64 characters. 




Module: 

DMH5155I 

WsaaJar 

Please type a shorter application name. 

No ChangeMan SERNET ids were 

found when searching the Rational 

Asset Analyzer applications. 

Explanation: No ChangeMan SERNET ids were found 

when searching the Rational Asset Analyzer 

applications. 



Module: 

DMH5156E 

WsaaJar 


None 

The container could not be found. 

Explanation: The container specified during inventory 

collection cannot be found on the target system. 



User response: Verify that the container specified 

exists, or specify an existing container, and try your 


Module: 

DMH5157E 

Explanation: 

WsaaJar 


information. 

You must specify the field. 

A required field was not filled in. 

The user is prompted for the required 

User response: Fill in the required field and submit 

the form again. 

Module: 

WsaaJar 



DMH5158E 

The date is incomplete. 

Explanation: The date has the wrong format or is 

invalid. Make sure the date format is YYYY-MM-DD. 


again. 


Module: 

DMH5159E 

WsaaJar 

The user is prompted for the date 

Fill in the date in the required format. 

The date is invalid. 

Explanation: The date has two many dashes. The 

format should be YYYY-MM-DD. 


again. 


Module: 

DMH5160E 

Explanation: 

WsaaJar 


again. 


Module: 

DMH5161E 



No date was specified. 

WsaaJar 

Date is required. 



Error deleting old links 

Explanation: 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 

Rational Asset Analyzer error logs. 

System action: The error is logged, and processing 

continues. It is likely that relationships have not been 

deleted from the database. 


error logs for details on possible DB2 connection or 

access problems. Consult your IBM technical-support 

representative if the issues cannot be resolved. 

Module: 

DMH5162E 

WsaaJar 

General error running the 

postprocessors 


during postprocessing. Details about the error can be 

found in the Rational Asset Analyzer error logs. 

System action: Postprocessing has stopped, and the 

error is logged. 


error logs. Fix any problems and attempt the scanning 

operation again. Contact your IBM technical-support 

representative if you cannot resolve the issue. 

Module: 

DMH5163I 

Explanation: 

unique. 

WsaaJar 

The concatenation set "duplicate 

concatenation set" already exists. 

Concatenation set names must be 

System action: The existing concatenation set 

properties are displayed and the user can update those 

properties. 

User response: Continue updating the concatenation 

set or click cancel to quit the wizard. 

Module: 

DMH5164I 

Explanation: 

WsaaJar 



Module: 

DMH5165E 

The concatenation set set name has been 

created. 

WsaaJar 

The concatenation set has been created. 


None 

Line line number does not start with // or 

/*. 

Explanation: Lines must start with // or /*. 




Module: 

WsaaJar 

The error is presented to the user. 

Correct the problem and submit the 

DMH5166E Line line number is greater than 80 

characters. 

Explanation: 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. 

System action: Queue processing continues with the 

next asset to be inventoried. The inventory being 

processed when the error was encountered is not 

processed. 

User response: Correct the problem and try your 

inventory collection process again. 

Module: 

DMH5167E 

WsaaJar 

No JCL JOB card was specified. 



encountered that does not contain a job card. 






processed. 



Module: 

DMH5168I 

WsaaJar 

The postprocessing is already running. 

Job job name at queue time. 


displayed when a user has selected the action to start 

postprocessing when it is already running. 



Module: 

DMH5169I 

Explanation: 

WsaaJar 



Module: 

Processing continues normally. 

None 

The postprocessing has been started. 

WsaaJar 

The postprocessing has been started. 

The user is notified of the status. 

None 

DMH5170W Impact analysis process has been 

interrupted. Results may be incomplete. 

Explanation: Impact analysis process has been 

interrupted. Results may be incomplete. 



Module: 

DMH5171E 

WsaaJar 


None 

Too many JCL JOB lines specified. Only 

4 are allowed. 



encountered that contains more than 4 lines in the job 

card. 




processed. 



Module: 

WsaaJar 

DMH5172I 

Explanation: 


updated. 


Module: 

DMH5173E 

The concatenation set has been updated. 

WsaaJar 

The concatenation set has been updated. 

The concatenation set has been 

None 

Problem storing to database in table 

tablename, name assetname, physicalId 

identifier 

Explanation: An error occurred while attempting to 

store metadata about scanned resources to the DB2 

database. The DB2 table, resource name, and identifier 

are specified. 

System action: Analysis for the asset specified stops, 

and the error is logged. Analysis continues for the next 

asset. 


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. 

Module: 

DMH5174E 

WsaaJar 

Field name is not found in table table. 

Explanation: 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 Rational Asset Analyzer installed and the schema 

defined to DB2 for the Rational Asset Analyzer 

database. 



asset. 


installed Rational 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 Rational Asset Analyzer 

installed exists in the Rational Asset Analyzer database. 

DDL used to create the database can be found in the 

/ddl directory. 

Module: 

DMH5175E 

WsaaJar 

External Semantic features are not 

compatible in table tablename; values 

have length of length1 and length2. 


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. 



asset. 










Module: 

DMH5176E 

WsaaJar 

Table name not found in database. 


into a nonexistent table in the DB2 schema. This error 

reflects a possible inconsistency between the level of 

Rational Asset Analyzer installed and the schema 

defined to DB2 for the Rational Asset Analyzer 

database. 



asset. 










Module: 

DMH5178E 

WsaaJar 

Authorization failed. 

Explanation: The user is not authorized to perform 

the action or the credentials are incorrect. 

System action: The user is not allowed to perform the 

specified action. 

User response: Type in the correct credentials to 

perform the action. 

Module: 

DMH5179E 

Explanation: 

WsaaJar 

The required field application name was 

empty. 

The application name is a required field. 



User response: Type in the application name and 

submit the request again. 

Module: 

DMH5180E 

WsaaJar 

No Logger defined, use 

setStatusReportInterface method 


attempting to instantiate the scanner and analyzer 

managers to begin the scanning process. This reflects 

an inconsistency in the installed Rational Asset 

Analyzer application. 

System action: The initialization of the distributed 

servlet cannot continue. This problem will cause errors 

starting your HTTP server if you are running 

WebSphere Application Server on MVS. If you are 

running WebSphere Application Server on Windows, 

WebSphere Application Server will likely start but the 

Rational Asset Analyzer distributed servlet will not be 

properly initialized. You must resolve the initialization 

issue before you can use the distributed scanner 

function. 

User response: Capture all pertinent Rational Asset 

Analyzer logs and Contact IBM Software Support. 

Module: 

DMH5181E 

WsaaJar 

Error while deleting old assets for 

container name 

Explanation: 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 Rational Asset Analyzer 

error logs. 



asset or scanning root. 


error logs for details on possible DB2 connection or 

access problems. Consult your IBM technical-support 

representative if the issues cannot be resolved. 

Module: 

DMH5182E 

WsaaJar 

The Analyzer manager was not 

initialized; call createSingelton method 


during initialization of the distributed scanner 

processes. This reflects an inconsistency in the installed 

Rational Asset Analyzer application. 












function. 

User response: Capture all pertinent Rational Asset 

Analyzer logs and Contact IBM Software Support. 

Module: 

DMH5183E 

WsaaJar 

Analyzer name does not exist 

Explanation: 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. 

System action: Deletion of the assets associated with 

the specified analyzer stops. Deletion continues for the 

next set of assets associated with a valid analyzer. 


the specified analyzer in the configuration file. If the 



Module: 

DMH5184E 

Explanation: 

WsaaJar 

Application with the specified name 

duplicate name already exists in the 

database. 

Application names must be unique. 

System action: The user is prompted again for an 


User response: Type in a unique application name and 

submit the request again 

Module: 

DMH5185E 

Explanation: 

empty. 

WsaaJar 

The required field full name was empty. 

The field full name is not allowed to be 

System action: The user is prompted for the full name 

of the application 

User response: Type the full application name into the 

field and submit the request again. 

Module: 

DMH5186I 

Explanation: 

WsaaJar 

Queued selected count asset(s) 

The assets selected have been queued. 

System action: The assets selected have been queued. 

Distributed assets were ignored. 


Module: 

WsaaJar 

None 

DMH5187I 

Explanation: 

analysis. 

Queued mvs count asset(s). Ignored 

distributed count distributed and binary 

count binary asset(s). 

Only text MVS assets can be queued for 

System action: The text MVS assets have been queued 

for postprocessing analysis. Any distributed assets or 

binary assets have been ignored. 


Module: 

DMH5188E 

WsaaJar 

None 

The child component with id = child id of 

the parent component with id = parent id is 

not found in the database. 

Explanation: An attempt was made to get information 

for the specified component, but metadata was not 

found in the Rational Asset Analyzer database. 

System action: Processing stops and some or all of 

information cannot be displayed. 



Module: 

DMH5189E 

WsaaJar 

The component with id = id is not found 


Explanation: An attempt was made to get information 

for the specified component, but metadata was not 

found in the Rational Asset Analyzer database. 

System action: Processing stops and some or all of 

information cannot be displayed. 



Module: 

DMH5190E 

WsaaJar 

Problem retrieving physical id for asset 

name 

Explanation: 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 

Rational Asset Analyzer application and the Rational 

Asset Analyzer database. 



asset. 


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. 



Module: 

DMH5191E 

WsaaJar 

Unable to load filename in module 

modulename 

Explanation: This is an unexpected error during 

Rational Asset Analyzer processing that could indicate 

an inconsistency in the installed product. The error 

occurs while trying to load configuration files packaged 

with Rational Asset Analyzer in the specified module. 



asset. 

User response: Ensure that you have properly 



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. 

Module: 

DMH5192E 

WsaaJar 

Unable to analyze elements in module 

modulename 

Explanation: An exception occurred while attempting 

to analyze elements in the specified module. The cause 

of this exception can be found in the Rational Asset 

Analyzer error logs. 



asset. 


error logs to determine the cause of the problem and 

potential solutions. Contact your IBM technical-support 

representative if the error persists. 

Module: 

DMH5193E 

WsaaJar 

Invalid resource descriptor resourcetype 

in module modulename 

Explanation: The resource type specified is not a valid 

type handled by the Rational Asset Analyzer scanner. 

The error was encountered while attempting to analyze 

resources in the specified module. Consult the Rational 

Asset Analyzer online help for a complete list of 

resources supported by the distributed scanner. 



asset. 

User response: Attempt the scanning operation again 

after removing the invalid resources from the scanning 

roots specified for the scanner. 

Module: 

WsaaJar 

DMH5194E 

Error getting resource resourcename input 

stream in module modulename 

Explanation: 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. 



asset. 

User response: 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. 

Module: 

DMH5195E 

WsaaJar 

Unable to analyze resource name in 

module modulename 


attempting to scan or analyze the specified resource in 

the module indicated. The exact cause of the error is 

indicated. 



asset. 

User response: Determine whether the cause of the 

analysis error can be corrected on site. Contact your 


cannot be resolved locally. 

Module: 

DMH5196E 

WsaaJar 

Unable to create resource in module 

modulename 

Explanation: 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 Rational Asset Analyzer in the specified 

module. 



asset. 







the problem. 

Module: 

WsaaJar 



DMH5197E 

Unable to analyze element name in 

module modulename. 


trying to analyze the specified element of a resource in 

the module indicated. 



asset. 


Module: 

DMH5198E 

WsaaJar 


The configuration file could not be read: 

file name 

Explanation: 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. 


displayed. 

Processing stops and the error is 

User response: Ensure that the specified file exists and 

Rational Asset Analyzer has the sufficient rights to 

access the file. 

Module: 

DMH5199E 

WsaaJar 

Unknown action "command" 

Explanation: An attempt was made to initiate an 

action that is not recognized by Rational Asset 

Analyzer. 


displayed. 


Module: 

DMH5200E 

WsaaMain 



Not a legal resource descriptor; got type 

resourcetype for resource name 

Explanation: An invalid resource was encountered. 

The resource must be a file or a directory. 



asset. 

User response: Verify that the resource specified is a 

valid type and attempt the scanning operation again. 

Module: 

DMH5201E 

WsaaJar 

Error allocating the internal reader for 

submitting JCL. RC=return code 

Explanation: An error occurred during the submission 

or processing of JCL. The return code is specified. 


displayed. 



Module: 

DMH5202E 

WsaaMain 


Cannot submit JCL on NT. 

Explanation: An attempt was made to submit a JCL 

job on the Windows platform. Windows does not use 

JCL to start processes. 


displayed. 


Module: 

DMH5203E 

WsaaMain 



The ALLOC command couldn't be run. 

Invalid container name "container name". 

RC=return code. 

Explanation: 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. 


displayed. 


User response: Resolve the error and try your 

operation again. Refer to the z/OS MVS user 

documentation for more help in resolving the issue. 

Module: 

DMH5204E 

WsaaMain 

Invalid MVS data set name: "data set 

name". 


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. 


displayed. 


Module: 

DMH5205E 

WsaaMain 



Dynamic allocation error. RC=return code 

details 

Explanation: 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. 


displayed. 







Module: 

DMH5206E 

WsaaMain 

Data set "data set name" is not a PDS or 

is not accessible. 

Explanation: Data set data set name could not be 

validated. It may not be a PDS, or you may not have 

the proper authority to access it. 


displayed. 


User response: Ensure that the data set is a PDS and 

that you have access to read it. 

Module: 

DMH5207E 

WsaaMain 

ChangeMan support is not enabled in 

the profile. 

Explanation: An attempt was made to inventory 

assets from a ChangeMan system, but ChangeMan as a 

valid asset management system is not enabled. 

System action: Processing stops and the error is 

displayed. ChangeMan features are disabled. 

User response: 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. 

Note: The ChangeMan interface provided with 

Rational Asset Analyzer is no longer being 

developed or supported and is provided as-is. 

Refer to http://www.serena.com for information 

about ChangeMan products. 

Module: 

DMH5208E 

WsaaMain 

Dynamic allocation error. RC=return code 

details 

Explanation: 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. 


displayed. 





Module: 

WsaaMain 

DMH5209E 

No configuration lines found: config file 


processing that requires information from the specified 

configuration file but that file is empty. 


displayed. 


User response: Ensure that the file exists and has 

content and try your operation again. 

Module: 

DMH5210E 

WsaaMain 

Common field(s) field were not defined 

for Analyzer name 

Explanation: A common field was not defined for the 

specified analyzer. User-defined columns are not 

supported for the tables defined by Rational Asset 

Analyzer. 










function. 

User response: Ensure that the table identified for the 

specified analyzer is consistent with respect to the 

Rational Asset Analyzer schema installed. Consult your 

IBM technical-support representative for further 

assistance. 

Module: 

DMH5211E 

WsaaJar 

There is no table for Analyzer name 

Explanation: The table defined as being associated 

with the specified analyzer in /assetloc/config/ 

Analyzers.cfg does not exist in the Rational Asset 

Analyzer database. 










function. 


your analyzer in the configuration file and verify that 

the table indicated exists in the Rational Asset Analyzer 

schema. Attempt the scanning operation again after 

fixing the inconsistency. 



Module: 

DMH5212E 

WsaaJar 

No implementing class for type analyzer 

Explanation: The class defined as being associated 

with the specified analyzer in /assetloc/config/ 

Analyzers.cfg does not exist in the Rational Asset 

Analyzer application. 










function. 


your analyzer in the configuration file and verify that 

the implementing class indicated exists in Rational 

Asset Analyzer. Attempt the scanning operation again 

after fixing the inconsistency. 

Module: 

DMH5213E 

WsaaJar 

No table name defined for type analyzer 

Explanation: There is no tableName defined for the 

specified analyzer in the /assetloc/config/ 

Analyzers.cfg file. Each analyzer must have all 

properties defined. 










function. 


the specified analyzer in the configuration file and 

attempt the scanning operation again. 

Module: 

DMH5214E 

WsaaJar 

Member not found or could not be read, 

possibly due to security: "data set name" 

Explanation: 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. 


displayed. 



Ensure that the data set exists and 

Rational Asset Analyzer has access to it. 

Module: 

DMH5215E 

WsaaMain 

Data set not found: data set name 


specified data set, but either the data set could not be 

found or it could not be accessed. 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. 


displayed. 


Module: 

DMH5216E 

WsaaMain 



Sequential data set could not be read: 

data set 


specified sequential data set but that data set could not 

be found or could not be accessed. 


displayed. 


Module: 

DMH5217E 

WsaaMain 



File not found: file name 


specified file, but it cannot be found. 


displayed. 


User response: Ensure that the file exists and can be 

read by Rational Asset Analyzer. 

Module: 

DMH5218E 

WsaaMain 

The file reading exit could not be 

found: read file exit 

Explanation: 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. 


displayed. 


Module: 

WsaaMain 





DMH5219E 

Bad URL path in request. The URL was 

"url". 

Explanation: 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. 


displayed. 


Module: 

DMH5220E 

WsaaJar 



URL mapping functor could not write 

the mapping requested resourcename 

Explanation: An exception occurred during an attempt 

to write the URL mapping for the specified resource to 

the DB2 metadata database. The Rational Asset 

Analyzer logs should have more specific information 

about the error. 



asset. 


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. 

Module: 

DMH5221E 

WsaaJar 

Cannot find hostname "hostname". 


specified host via the Web browser, but that host 

cannot be found or resolved. 


displayed. 


User response: Verify hostname is correct and the 

resolving service is functioning properly. 

Module: 

DMH5222E 

WsaaJar 

Not authorized to make request. 

Explanation: An attempt was made to access a Web 

page but the server specified denied the request. 


displayed. 


User response: Verify that the Rational Asset Analyzer 

server has authorization. 

Module: 

WsaaJar 

DMH5223E 

XML request server failed during 

response. Partial response was: response 

Explanation: An attempt was made to send XML as 

part of a Web browser request but the server failed to 

send XML over the connection. 


displayed. 


Module: 

DMH5224E 

WsaaJar 



You must enter text in the search field 

to perform a search. 

Explanation: The search Go button was pressed but 

no search criteria was entered. 

System action: No search is performed. The user is 

prompted for a search constraint. 

User response: Type a search constraint into the 

search field and press the Go button. 

Module: 

DMH5225I 

Explanation: 

WsaaJar 



Module: 

DMH5226I 

Explanation: 

Impact analysis has finished. 

WsaaJar 



Module: 

DMH5227I 

Impact analysis has finished. 


None 

Impact analysis is in progress... 

WsaaJar 

Impact analysis is in progress... 


None 

The set of assets chosen for impact 

analysis "ia name" has been updated. 

Explanation: The assets chosen for the impact analysis 

have been updated. 



Module: 

DMH5228I 

Explanation: 

analysis. 

WsaaJar 



None 

Asset will be added to the impact 

analysis. 

Asset will be added to the impact 





Module: 

DMH5229I 

Explanation: 

analysis. 

WsaaJar 



Module: 

DMH5230E 

None 

Asset will be removed from the impact 

analysis. 

WsaaJar 

Asset will be removed from the impact 


None 

Please select at least one asset as a 

starting point for the impact analysis. 

Explanation: Impact analysis requires at least one 

asset to analyze. 


again for the asset to be analyzed 

User response: Add an asset to the impact analysis 

and try your operation again. 

Module: 

DMH5231E 

Explanation: 

WsaaJar 

The resources passed resource is not 

supported. 

An internal error has occurred 

System action: The scanner skips the current asset and 



Module: 

DMH5232E 

Explanation: 

WsaaJar 


The resource passed is a non CVS 

resource, resource 





Module: 

DMH5233E 

Explanation: 

WsaaJar 


Bad CVSS root - root. skipping... 

The scanning root is not valid 

System action: The scanner skips the current scanning 

root and continues processing. 

User response: Fix the problematic scanning root and 

try the operation again 

Module: 

WsaaJar 

DMH5235E 

Explanation: 

The resource passed is a non PVCS 






Module: 

DMH5236E 

WsaaJar 


Unsupported attribute: attribute for asset 

type 

Explanation: The attribute attribute is unsupported by 

the asset type 



Module: 

DMH5237E 

Explanation: 

The attribute cannot be retrieved 


WsaaConfigMgr 

Soft link resource, resource, isnot 

supported 

A soft link resource was encountered. 

System action: The resource will be skipped and 

scanning will continue with the next resource. 

User response: Fix the scanning roots that have soft 

links in them, this includes the XML files of the 

WebSphere Application Server scanning roots. 

Module: 

DMH5238E 

WsaaJar 

Asset of type type and id id does not 

exist in database 

Explanation: An asset of type type and id id was 

requested but does not exist in database. 



Module: 

DMH5239E 

WsaaJar 

Processing for this asset stops. 


Illegal request for attribute value: 

requested for attrRequest but attribute 

contains attrType 

Explanation: The application requested a parameter of 

type attrRequest but the attribute contains type of 

attrType 



Module: 

WsaaJar 

The exception is thrown and logged 




DMH5240E 

An archive "name" with the .ear 

extension is not an ear file or is an 

unsupported ear version 

Explanation: 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 Rational Asset Analyzer. Either 

the EAR file contents do not represent an EAR file or 

the EAR is an unsupported version. 



asset. 

User response: Verify that the asset specified is a valid 

EAR file and a version supported by Rational Asset 

Analyzer, and attempt the scanning operation again. 

Module: 

DMH5241E 

WsaaJar 

An illegal nesting of J2EE archives 


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. 



asset. 

User response: Ensure that the specifications for the 

scanner, for example, the scanning root itself, contain 

all nested archives that are likely to be encountered and 



assistance. 

Module: 

DMH5242E 

WsaaJar 

Two Web modules appear with the same 

context root root in ear earfile. 


analysis of the EAR file indicated because multiple 

modules are defined with the same context root 

specified. This is an invalid EAR file. 



asset. 

User response: Ensure that the EAR file specified is a 

valid archive and attempt the scanning operation again. 

Module: 

WsaaJar 

DMH5243E 

Duplicate fieldName in DataObject 

metadata: fieldValue 

Explanation: The application tried to set duplicate 

fieldName in DataObject metadata: fieldValue 



Module: 

DMH5244E 

WsaaJar 

The exception is thrown and logged 


Index index out of bound for key of size 

size 

Explanation: The requested index index is out of 

bound for the key of size size 

System action: An exception is thrown and processing 

is stopped for this asset 


Module: 

DMH5245E 

WsaaJar 


Value value is not of type type even 

though it is expected to be 

Explanation: The value is not of the type it is 

expected to be. 

System action: An exception is thrown and processing 

is stopped for this asset. 


Module: 

DMH5246E 

Explanation: 

type. 

WsaaJar 



Module: 

DMH5247E 


No Metadata support for type type 

WsaaJar 

There is no metadata support for type 

This request is discarded. 


An compatible value of type valueType 

was tried to assign to Attribute of type 

attributeType 

Explanation: An compatible value of type valueType 

was tried to assign to Attribute of type attributeType. 



Module: 

WsaaJar 

The asset will be ignored. 


DMH5248E 

Impact Analysis asset for asset of type 

type does not exists 

Explanation: Impact Analysis asset for asset of type 

type does not exists. 





Module: 

DMH5249E 

Explanation: 

instantiated. 

WsaaJar 


is logged. 


Module: 

DMH5250E 

This asset will be ignored. 


Class className cannot be found or 

instantiated 

WsaaJar 

Class className cannot be found or 

The asset is been ignored and the error 


The full path name of the asset cannot 

be retrieved. The ID of the asset is id 

and its name is name 

Explanation: The full path name of the asset cannot be 

retrieved. The ID of the asset is id and its name is name. 



Module: 

DMH5252E 

WsaaJar 

The path name will not be retrieved. 


The data source named "datasource name" 

could not be located. Ensure that the 

name has been defined to WebSphere. 

Explanation: The data source name must be specified 

correctly in WebSphere Application Server's 



to the user. 

The exception stack trace is displayed 

User response: Ensure that WebSphere Application 

Server is set up correctly. 

Module: 

DMH5253E 

Explanation: 

to null. 

WsaaJar 

Could not find a rule set for analyzer 

name 

The rules manager for the analyzer is set 

System action: The rule set will not be reset for the 

analyzer. The analyzer for the JSP will not be 

initialized. 


Module: 

WsaaJar 


DMH5254E 

The pattern name patternName is not 

listed 

Explanation: The pattern name patternName is not 

listed in the patterns list. 



Module: 

DMH5255E 

WsaaJar 

This pattern will be ignored. 


Unexpected recursion level in 

JSP/HTML analysis 

Explanation: A ContextRegionContainer object 

contains a ContextRegionContainer object, which is not 

legal. 

System action: Analyzing is stopped for the JSP. The 


file. 

User response: Verify that the JSP is well formed. 


Module: 

DMH5256E 

WsaaJar 

An archive "name" with the .rar 

extension is not a rar file or is an 

unsupported rar version 



.rar file extension but it does not represent a valid 

RAR file supported by Rational Asset Analyzer. Either 

the RAR file contents do not represent an RAR file or 

the RAR is an unsupported version. 



asset. 


RAR file and a version supported by Rational Asset 

Analyzer, and attempt the scanning operation again. 

Module: 

DMH5257E 

Explanation: 

value. 

WsaaJar 

The EJB Jar relationship EJB Relation 

Name is undefined 

The relationship has at least one null 

System action: Analysis for the EJB specified stops, 


asset. 


Module: 

WsaaJar 




DMH5258E 

String comparison had a null string: 

string 1, string 2 

Explanation: For a string to be compared, it must be 

defined (not null). This is likely due to a corrupt asset. 

System action: Processing of the current SGML-based 

tag stops. Processing continues on the next tag. 

User response: Make sure that the SGML-based asset 

is valid. If the asset is valid, contact IBM Software 

Support. 

Module: 

DMH5259E 

Explanation: 

requested. 

WsaaJar 

Unsupported link type type 

An unsupported link type was 

System action: The error will be logged and continue 

to process next asset. 


Module: 

DMH5261E 

WsaaJar 


A Process state cannot be retrieved 

Explanation: The process state cannot be retrieved 

from the database or updated in the database. 


retrieved. 

The state will not be updated or 

User response: Verify there is a database connection 

and the database is up and running. Contact IBM 


Module: 

WsaaJar 

DMH5262W Cannot get assets matching filter: 

assetType assetType 

Explanation: No assets were found for the impact 

analysis project. 



User response: If assets were supposed to be 

analyzed, try correcting the specification of the impact 

analysis. Otherwise, no action is required. 

Module: 

DMH5263E 

WsaaJar 

Creating impact analysis failed. SQL=sql 

Explanation: Inserting a impact analysis project into 

the database failed. 


is not saved. 

The database is rolled back; the project 

User response: Examine the SQL and attempt to fix 

any problems. Try adding the project again or contact 

your IBM technical-support representative for 

assistance. 

Module: 

DMH5264E 

WsaaJar 

SQL error: SQLCODE=sql code 

SQLSTATE=sql state (See Impact 

Analysis log for SQL details.) 

Explanation: The SQLCODE is detailed in the DB2 

manual. The SQLSTATE is detailed in the XOPEN SQL 

spec. 


is not saved. 


User response: Examine the SQL error and attempt to 

fix any problems. Try the save again or contact your 

IBM technical-support representative for assistance. 

Module: 

DMH5265E 

WsaaJar 

Cannot create impact analysis: cause 

message 

Explanation: The original cause of the failed impact 

analysis project save is logged. 


is not saved. 


User response: Examine the error and attempt to fix 

any problems. Try the save again or contact your IBM 

technical-support representative for assistance. 

Module: 

DMH5266E 

WsaaJar 

Impact Analysis seed cannot be 

updated: cause message 

Explanation: The original cause of the failed impact 

analysis project update is logged. 

System action: The database is rolled back; the project 

is not updated. 

User response: Examine the error and attempt to fix 

any problems. Try the save again or contact your IBM 


Module: 

DMH5267E 

WsaaJar 

Analysis of seed encountered problems: 

asset (levels analyzed before 

failure=levels analyzed) 

Explanation: An error occurred during the analysis of 

the impacted assets. 


Processing for the current seed stops. 

User response: Check logs for detailed messages. If 

further help is needed, contact IBM Software Support. 

Module: 

WsaaJar 



DMH5268W Impact analysis interrupted. Analysis 

results may be incomplete. 

Explanation: The impact analysis has been interrupted 

or canceled. Analysis results may be incomplete. 

System action: The process for analyzing an asset's 

impact has been interrupted. 

User response: Depending on why the impact analysis 

was interrupted, the user may choose to restart the 

analysis at a later time. 

Module: 

WsaaJar 

Module: 

DMH5272E 

Explanation: 

WsaaJar 


previous state. 

Updating seed in project with id=project 

id failed. SQL=sql 

Saving the impact analysis project failed. 

The database is rolled back to the 



Module: 

WsaaJar 

DMH5269E 

Impact analysis stopped analyzing seed 

asset when maximum level of analysis 

was reached. 

Explanation: The maximum number of levels of 

analysis were reached before the asset was fully 

analyzed. 

System action: Processing for the current seed stops. 

The impact analysis project is saved. 


Module: 

DMH5270E 

WsaaJar 

None 

This method should not be called for 

Ejb as it does not have physical 

representation assetname 


encountered because a method that should not be 

invoked for the specified asset was invoked. This could 

reflect an inconsistency in the installed Rational Asset 

Analyzer product, or an environment or classpath 

problem. 



asset. 

User response: Ensure that you have installed 

Rational Asset Analyzer correctly according to 

instructions in the Configuration and Migration Guide. 

Consult your IBM technical-support representative if 

the problem cannot be resolved. 

Module: 

DMH5271E 

WsaaJar 

type type of assets cannot serve as an 

impact analysis starting point. The asset, 

asset, cannot be analyzed explicitly. 

Explanation: The asset type is not valid as a starting 

point for impact analysis. 


analysis stops. 

Processing for the current impact 

User response: Specify a valid starting point for 

impact analysis and start the analysis again. 

DMH5273E 

Impact Analysis of project with id=id 

encountered problems: cause message 

Explanation: An error occurred during the analysis of 

the impacted assets. 


Processing for the current seed stops. 



Module: 

DMH5274E 

Explanation: 

WsaaJar 


back. 

Cannot add impacts for project. 

The project save failed. 

The database transaction will be rolled 

User response: Verify the database connection and try 

again. If the problem persists, contact IBM Software 

Support. 

Module: 

DMH5275E 

Explanation: 

WsaaJar 


back. 

Cannot add impact analysis seed to 

project. 





Support. 

Module: 

DMH5276E 

WsaaJar 

Cannot delete project. SQL=sql 

Explanation: An exception occurred while trying to 

delete the project. 


database. 


Module: 

WsaaJar 

The project will remain in the 




DMH5277E 

Failed while deleting ImpactAnalysis 

with project id id: cause message 


delete the project. 


database. 


Module: 

DMH5278E 

Explanation: 

WsaaJar 


back. 

The project will remain in the 



project. SQL=sql 





Support. 

Module: 

DMH5279E 

Explanation: 

WsaaJar 


back. 


project: cause message 





Support. 

Module: 

DMH5280E 

Explanation: 

WsaaJar 

Clearing activity log for project with 

id=id failed. SQL=sql 

The activity log could not be removed. 

System action: The database transaction will be rolled 

back. The activity log will remain in the database. 



Support. 

Module: 

DMH5281E 

Explanation: 

WsaaJar 

Impact Analysis failed while clearing 

activity log: cause message 

The activity log could not be removed. 


back. The activity log will remain in the database. 



Support. 

Module: 

WsaaJar 

DMH5282E 

Impact Analysis failed while deleting 

project's impacts: cause message 

Explanation: An exception occurred during this 

database transaction. 


back. The impacts will remain in the database. 



Support. 

Module: 

DMH5283E 

WsaaJar 

Clearing impacts from project with id=id 

failed. SQL=sql 




back. The impacts will remain in the database. 



Support. 

Module: 

DMH5284E 

WsaaJar 

Clearing seeds from project with id=id 





back. The impact seeds will remain in the database. 



Support. 

Module: 

DMH5285E 

WsaaJar 

Impact Analysis failed while deleting 

project's seeds: cause message 




back. The impact seeds will remain in the database. 



Support. 

Module: 

DMH5286E 

WsaaJar 

Querying project with id=id failed. 

SQL=sql 




The current processing will stop. 





Support. 

Module: 

DMH5287E 

WsaaJar 

Cannot get Impact Analysis information: 

cause message 




The current processing will stop. 



Support. 

Module: 

DMH5288E 

WsaaJar 

Updating project timestamp with id=id 





back. The timestamp will remain unchanged. 



Support. 

Module: 

DMH5289E 

WsaaJar 

Impact Analysis cannot be updated: 

cause 




back. 




Support. 

Module: 

DMH5291E 

WsaaJar 

Updating project with id=id failed. 

SQL=sql 




back. 




Support. 

Module: 

WsaaJar 

DMH5292E 

Explanation: 



Module: 

DMH5293I 

Asset type cannot be analyzed directly 

IA: asset type 

WsaaJar 

The asset could not be found. 

The asset is not added to a project. 


Run unit "run unit name" has been 

queued. Run the postprocessing to build 

it. 

Explanation: A request to create a run unit for 

program program name has been added to the analysis 

queue. 


queue. 

The request is added to the analysis 

User response: 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. 

Module: 

DMH5294I 

WsaaJar 

Distributed postprocessor successfully 

started. 

Explanation: User initiated the distributed 

postprocessor on the runtime. 

System action: Distributed postprocessor started in a 

separate thread. 


Module: 

WsaaJar 

None 

DMH5295W Distributed postprocessor could not be 

started. Another instance was already 

running. 

Explanation: User initiated the distributed 

postprocessor on the runtime, but the distributed 

postprocessor was already running. 



Module: 

DMH5296I 

Explanation: 

action. 

WsaaJar 



Module: 

Ignore request. 

Retry at a later time. 

Action [action] successfully completed. 

WsaaJar 

User successfully initiated the [action] 

Action performed. 

None 



DMH5297E 

Explanation: 

the servlet. 



Module: 

DMH5298I 

Invalid value specified for GET 

parameter [paramName]: [paramVal] 

extraInfo 

WsaaJar 

An invalid GET parameter was passed to 

URL processing aborted. 

Fix the URL. 

Current distributed postprocessor status: 

[status] 

Explanation: User queried for the distributed 

postprocessor status. 



Module: 

DMH5299E 

Explanation: 

WsaaJar 


analysis. 


Module: 

DMH5300E 

Explanation: 

None 

None 

Cannot find asset with type=name and 

key=asset key 

WsaaJar 

The impact asset could not be found. 

The impact asset is not added to an 


Cannot add Asset with key selected key to 

Impact Analysis. 

The asset's value does not exist. 

System action: The impact asset is not added to the 

Impact Analysis. 


Module: 

DMH5301E 

Explanation: 

WsaaJar 


Impact analysis does not recognize an 

asset of type type name 

The asset is not a scanned-in asset. 

System action: Current processing stops. The impact 

asset is not created. 


Module: 

DMH5303E 

Explanation: 

WsaaJar 



Cannot access data object with type type, 

with key key 

The asset cannot be accessed. 

The data object will not be accessed. 


again. 

Module: 

DMH5304E 

Explanation: 

WsaaJar 



Module: 

DMH5305E 

Verify sufficient authority and try 

Impact analysis encountered 

unrecognized type of asset. 

WsaaJar 

The asset is not a scanned-in asset. 

Current processing stops. 


Cannot get asset factory for assetType 

assetType 

Explanation: The impact asset could not be found or 

the asset factory could not be found. 



Module: 

DMH5306I 

Explanation: 

completed. 

WsaaJar 



Module: 

DMH5307E 

Current analysis stops. 


Done Analyzing project project id 

WsaaJar 

The impact analysis project has 


Check logs for any errors. 

Impact Analysis encountered an 

EXCEPTION processing Analysis with 

project id=project id: cause message 

Explanation: There was a stopping error while 

performing the impact analysis. 


The impact analysis is not complete. 

User response: Check logs for errors and fix as 

necessary. If further assistance is needed, contact IBM 


Module: 

DMH5308E 

WsaaJar 

Asset analysis failed: Level analysis level, 

type: type (asset) 

Explanation: There was a stopping error while 

performing the asset analysis. 


The asset analysis is not complete 

User response: Check logs for errors and fix as 

necessary. If further assistance is needed, contact IBM 


Module: 

WsaaJar 



DMH5309E 

Adding impact to project failed. 

SQL=sql 

Explanation: There is a problem communicating with 

the database. 


back. 


connection. 

Module: 

WsaaJar 


Verify the database configuration and 

Module: 

DMH5314E 

Explanation: 

is not valid. 

WsaaJar 



Module: 

Class factory class name is not an 

ImpactAssetFactory 

WsaaJar 

The currently set impact analysis factory 

Current analysis stops. 


DMH5310E 

An archive "name" with the .war 

extension is not a war file or is an 

unsupported war version. 



.war file extension, but it does not represent a valid 

WAR file supported by Rational Asset Analyzer. Either 

the WAR file contents do not represent a WAR file or 

the WAR is an unsupported version. 



asset. 


WAR file and a version supported by Rational Asset 

Analyzer and attempt the scanning operation again. 

Module: 

DMH5312E 

WsaaJar 

Current context already exists for this 

resourcename 


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. 



asset. 

User response: Ensure that the specified resource is a 

valid WAR file and attempt the scanning process again 

after correcting any errors. 

Module: 

DMH5313E 

WsaaJar 

Impact Analysis failed while saving an 

impact: cause message 

Explanation: There is a problem communicating with 

the database. 


back. 


connection. 


Verify the database configuration and 

DMH5315E 

Impact Analysis wizard encountered an 

exception setting up to analyze 

information: exception 

Explanation: The "Impact analysis" wizard may not be 

set up correctly. 

System action: The "Impact analysis" wizard may 

display incorrectly. 

User response: Start the wizard again. If the problem 


Module: 

DMH5316E 

WsaaJar 


exception updating analysis 








Module: 

DMH5317E 

WsaaJar 


exception displaying analysis 

information for update: exception 







Module: 

DMH5318E 

WsaaJar 


exception updating analysis seed 










Module: 

DMH5319E 

WsaaJar 

Impact Analysis cannot determine the 

existing status of the analysis: exception 

Explanation: The "Impact analysis" wizard 

encountered an error while initializing the page. 





Module: 

DMH5320E 

WsaaJar 

Missing URL space 

Explanation: 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. 



asset. 


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. 

Module: 

DMH5321E 

WsaaJar 

Error writing to servlet mapping table 

name 


attempting to write metadata about the servlet being 

analyzed to the DB2 table specified. Check the Rational 

Asset Analyzer error logs for information related to 

DB2 communications problems. 



asset. 

User response: Verify that the specified DB2 table 

exists. If it does not, you must ensure that you properly 



Migration Guide, including the step for creating the 

database. If the table does exist, examine the Rational 

Asset Analyzer error logs for information related to 

DB2 access problems. Attempt the scanning operation 

again after correcting any errors. 

Module: 

WsaaJar 

DMH5322E 

Impact Analysis cannot be finalized: 

exception 




display incorrectly. The project is not finalized. 



Module: 

DMH5323E 

WsaaJar 

Impact Analysis status cannot be 

determined: exception 

Explanation: There was a problem while rendering the 

page. The "Impact analysis" wizard may not be set up 

correctly. 





Module: 

DMH5324E 

WsaaJar 


exception setting up for analysis of 

specific assets: exception 

Explanation: There was a problem while initializing 

the page. The "Impact analysis" wizard may not be set 

up correctly. 





Module: 

DMH5325E 

WsaaJar 


exception processing set up information 

for analysis of specific assets: exception 

Explanation: There was a problem while processing 

the page. The "Impact analysis" wizard may not be set 

up correctly. 


display incorrectly. The impact analysis might not be 

initialized. 



Module: 

WsaaJar 



DMH5326E 


exception setting up information for 

analysis: exception 


encountered an error while processing the page. 





Module: 

DMH5327E 

WsaaJar 


exception displaying information: 

exception 


encountered an error while rendering the page. 





Module: 

DMH5328E 

WsaaJar 

Cannot display asset name: exception 

Explanation: There was a problem accessing the 

details of an asset. This could be caused by a corrupt 

asset or a database inconsistency. 




Module: 

DMH5329E 

WsaaJar 



exception initializing for analyzing 

assets: exception 


encountered an error while initializing the page. 





Module: 

DMH5330E 

WsaaJar 


Servlet, as it does not have physical 

representation methodname 



an inconsistency in the installed product. 


Analysis for the asset specified stops, 


asset. 







the problem. 

Module: 

DMH5331E 

WsaaJar 


byte code members, as it does not have 

physical representation id 






asset. 







the problem. 

Module: 

DMH5332E 

WsaaJar 


exception displaying information: 

exception 


encountered an error while rendering the page. 





Module: 

DMH5333E 

WsaaJar 

Unsupported source container type: type 

Explanation: Unsupported source container type: type, 

the supported types are EJB, EJB JAR and WAR. 



Module: 

WsaaJar 

This pattern will be ignored. 




DMH5334E 

Illegal number of asset1 mapped to the 

asset2 in name : size 

Explanation: Illegal number of asset1 mapped to the 

asset2 in name : size There should be only 1:1 mapping. 

System action: The inference for the current pattern 

will be ignored. 


Module: 

DMH5335E 

WsaaJar 


Parameters not specified correctly. 

Explanation: The servlet did not receive the parameter 

AssetTypeIdProp. 



Module: 

DMH5336E 

WsaaJar 

Processing of the current request stops. 


Initialization error occurred in servlet. 

Explanation: During initialization of the servlet, an 

exception occurred. 


The servlet will not display. 

User response: Correct the problem and restart the 

Rational Asset Analyzer Web application. 

Module: 

WsaaJar 

Explanation: During computation of EJB ref, the 

system had a problem. 


ignored. 


Module: 

DMH5340I 

WsaaJar 

This reference computation will be 


ppName Link postprocessor finished. 

Files processed=[filesProcessed], Links 

processed=[linksProcessed], Broken 

links=[brokenRefs], Total 

time=[totalTime)s] 

Explanation: An information message about the 

postprocessor activity after completion. 



Module: 

DMH5341I 

WsaaJar 


None 

ppName Link postprocessor started... 

Explanation: An information message about the 

postprocessor starting 



Module: 

WsaaJar 


None 

DMH5337E 

Invalid variable type variable 

encountered: variable type{variable 

arguments} 

Explanation: The XML variable was not formatted 

correctly in the XML file. 



Module: 

DMH5338E 

WsaaJar 

Current request processing stops. 


Invalid field number [field number] 

specified in DataSet.setField(fieldNum). 

DataSet columns are [valid columns] 

Explanation: The field number is greater than the 

number of fields. 



Module: 

WsaaJar 

Current request processing stops. 


DMH5342E 

Unable to store record into the database 

Explanation: There was an error in storing a record of 

data into the database. 


The data did not get stored. 

User response: Please refer to the log for more details, 

and Contact IBM Software Support. 

Module: 

DMH5344E 

Explanation: 

exception. 

WsaaJar 


stop. 

Logger failed to initialize. 

The main logger initialization caused an 

Initialization failed. Processing will 

User response: Verify the configuration is correct and 

try the operation again. If the problem persists, contact 

IBM Software Support. 

Module: 

WsaaJar 

DMH5339E 

Problem in getting or computing 

aRefType for asset id bAsetId of assetType 

type 

DMH5345E 

Explanation: 

exception. 

Database failed to initialize. 

Initializing the database caused an 



System action: Initialization failed. Processing will 

stop. 

User response: Verify the configuration is correct and 

verify the database is properly set up and configured. If 

the problem persists, contact IBM Software Support. 

Module: 

DMH5346I 

Explanation: 

WsaaJar 

Postprocessing starting. 


System action: This is an informational message 

written to the Rational Asset Analyzer log indicating 

that a postprocessor is starting. 


Module: 

DMH5347E 

WsaaJar 

None 

Database connection is down. 

Explanation: The system was unable to retrieve a 

table from the database. This error could be caused by 

the database going down. 

System action: Processing stops. The user will not be 

allowed to log in. 



Module: 

DMH5348E 

WsaaJar 

Check the database status and try the 

Unable to store the resource into the 

database, it is probably too long or 

placed too deep in the scanning root 

Explanation: 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. 

System action: The resource will not get scanned into 

the system. Processing continues with the next 

resource. 

User response: 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 IBM Software Support. 

Module: 

WsaaJar 

DMH5349W MVS postprocessor is running. Search 

results may not be accurate. 

Explanation: 

results. 


The postprocessor might affect the 


User response: Wait for the operation to complete for 

accurate results. 

Module: 

WsaaJar 

DMH5351E 

Problem setting value to column 

columnName in table tableName. The 

value type is valueType and the value is 

value 

Explanation: There is a problem storing a value in a 

prepared statement. 

System action: The store of this record will be skipped 

and the error is logged. 


Module: 

WsaaJar 


DMH5352W Distributed postprocessor is running. 

Search results may not be accurate. 

Explanation: 

results. 


The postprocessor might affect the 




Module: 

WsaaJar 

DMH5353W Distributed scanner is running. Search 

results may not be accurate. 

Explanation: 


The scanner might affect the results. 




Module: 

WsaaJar 

DMH5354W Unknown XML node type: type node 

type, parent parent string 

Explanation: The node was not of type element or 

text. No other node types are supported. 


logged. 


Module: 

DMH5355E 

Explanation: 

SQL: sql. 

WsaaJar 



Module: 

This node is ignored. The error is 


An unexpected SQL exception occurred. 

SQL: sql 

WsaaJar 


The current action is stopped. 




DMH5356W The SQL query does not appear to be 

valid. Please re-enter the query. 

msg=[msg] 

Explanation: The user-entered query returned an SQL 

exception: msg=[msg], sql=[sql]. 



Module: 

DMH5357I 

Explanation: 

WsaaJar 



Module: 

DMH5358I 

Explanation: 

successfully. 

The current action is stopped. 

Re-enter the query. 

Successfully bookmarked page as 'name' 

WsaaJar 



Module: 

DMH5359E 

Explanation: 

The bookmark was created successfully. 


None 

Successfully created custom query as 

'name' 

WsaaJar 



Module: 

The custom query was created 


None 

Bookmark create failed. See log file for 


WsaaJar 

The bookmark create failed. 

The action is stopped. 

None 

Module: 

DMH5362I 

Explanation: 

WsaaJar 



Module: 

DMH5363I 

Explanation: 

Deleted num rows. 

WsaaJar 



Module: 

DMH5364E 

Explanation: 

encountered. 

The specified delete operation succeeded. 


None 

Deleted cached counts. 

WsaaJar 



Module: 

DMH5366I 

The specified delete operation succeeded. 


None 

Unexpected exception occurred. 

Message=[msg] 

WsaaJar 

An unexpected exception was 



Site "name" was created. 

Explanation: The site "name was successfully created 

and is now available for use. 

System action: The site is added to the database and 

available for use. 


Module: 

WsaaJar 

None 

DMH5360E 

Explanation: 



Module: 

DMH5361E 

Custom query create failed. See log file 

for more information. 

WsaaJar 

The custom query create failed. 


None 

Error occurred while trying to 

instantiate objectName. See log file for 


Explanation: An unexpected exception occurred while 

trying to instantiate the specified object type. Exception 

msg=[msg]. 




None 

DMH5367I 

Site "name" was updated. 

Explanation: The details of site "name were 

successfully updated. 

System action: The site definition is updated in the 

database and available for use. 


Module: 

WsaaJar 

None 

DMH5368W Files are being ignored: count 

Explanation: Of the files that were selected for this 

action, count will be ignored. The language and type 

can only be changed if 1) the file language is 

Assembler, COBOL, Easytrieve, JCL, PL/I, Text, 

Unknown, or blank, and 2) the file type is Batch job, 

Include, Macro, Program source, Procedure, Unknown, 

or blank, and 3) the file is not in an archive or the 



result of a remote z/OS scan. 

System action: Some files are not included in the list 

of files to be updated. 


Module: 

DMH5369E 

Explanation: 

WsaaJar 



operation. 

Module: 

DMH5370E 

None 

A name must be specified for the site. 

WsaaJar 

A site cannot be created without a name. 

The site is not created. 

Specify the site name and retry the 


Tag as it does not have physical 







asset. 







the problem. 

Module: 

DMH5371E 

Explanation: 

database. 

WsaaJar 



the operation. 

Module: 

DMH5372I 

Duplicate site name "name". Specify a 

different name. 

WsaaJar 

The site name already exists in the 

The site is not created. 

Specify a unique site name and retry 

There are too many assets to display. 

Please enter a more specific search 

argument to narrow your search. 

Explanation: The results of searching for assets that 

match the search argument are too many to display. 



argument. 

Module: 

WsaaJar 


Specify a more restrictive search 

DMH5373I 

Explanation: 

has changed. 



Module: 

DMH5374E 

The range of statements for impact 

analysis "ia name" has changed. 

WsaaJar 

The range of statements to be analyzed 


None 

Invalid value specified for the statement 

range. 

Explanation: The impact analysis has a non-numeric 

statement start or end value, or the statement start is 

beyond the statement end in the file. 


again for a valid statement range. 

User response: 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 


Module: 

DMH5375E 

WsaaJar 

Cannot access the list of assets selected 

as starting points for this impact 

analysis: error message 

Explanation: 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 Rational Asset Analyzer logs. 

System action: The impact analysis may be modified 

or remain unchanged. 

User response: Exit the impact analysis creation or 

modification process and try to access and update the 

impact analysis again. Refer to the Rational 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 


Module: 

WsaaJar 

DMH5377W WARNING: Annotation type defined in 

Database but not in 

wsaa-annotation-types.xml: 

name=[name], id=[id] 

Explanation: 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. 

User response: Add the missing annotation type to 

wsaa-annotation-types.xml. 

Module: 

DMH5378E 

WsaaJar 

The temporary file file name could not be 

created. 

Explanation: The directory may not exist or you may 

not be authorized to create a file in the directory. 

System action: The temporary file is not created, so 

the current action that involves getting an MVS file is 

not successful. 

User response: Have the system administrator check 

Rational Asset Analyzer's settings using the 

DMHINSTL command. Ensure that the directory 

specified for temporary HFS files exists and that all 

Rational Asset Analyzer users have the authority to 

create files there. Once corrected, retry this action. 

Module: 

DMH5379E 

WsaaJar 

Failed while committing impact analysis 

details 

Explanation: Impact analysis failed because it could 

not commit the analysis details for the analysis with 

id=projId to the database. 

excMsg 

System action: Impact analysis stopped processing 

without completing. A rollback was attempted. 

User response: Verify that a connection to the 

database can be established. Issue the impact analysis 


Module: 

DMH5381E 

WsaaJar 

Impact analysis starting points are not 

valid. 

Explanation: Either no starting points have been 

designated for the impact analysis or an asset 

designated as the starting point cannot be found or 

accessed in the database. 


Impact analysis is disabled. 

User response: Try the action again when the 

connection to the database has been verified. If the 

problem persists, delete the selected impact analysis. If 

the starting-point asset or assets are in the inventory, 

you can analyze them again to create a new impact 

analysis. 

Module: 

WsaaJar 

DMH5382I Product Information 

Explanation: This message is the title of the 

distributed scanner's About dialog. 



Module: WsaaJar 

DMH5383I Error Log 


distributed scanner error log. 




DMH5384I Event Log 


distributed scanner event log. 




DMH5385I Scanner 

Explanation: This message is the label for a 

distributed scanner menu item. 




DMH5386I Help 






DMH5387I Clear log 








DMH5388I 

About Rational Asset Analyzer... 


distributed scanner menu item and tool tip. 



Module: 

DMH5389I 

WsaaJar 

Exit 


None 





Module: 

DMH5390I 

WsaaJar 


None 

Start scanning 


distributed scanner tool tip. 



Module: 

DMH5391I 

WsaaJar 


None 

Stop scanning 





Module: 

DMH5392I 

WsaaJar 


None 

Pause scanning 





Module: 

DMH5393I 

WsaaJar 


None 

Rational Asset Analyzer Administrator 

GUI 


distributed scanner's main window. 



Module: 

WsaaJar 


None 

DMH5394I 

Exit Rational Asset Analyzer 

Administrator GUI? 

Explanation: This message prompts the user to 

confirm a distributed scanner GUI exit request. 



Module: 

DMH5395I 

WsaaJar 


None 

Exit Confirmation 


distributed scanner's Exit Confirmation dialog. 



Module: 

DMH5396I 

WsaaJar 

OK 


None 


distributed scanner dialog button. 



Module: 

DMH5397I 

WsaaJar 


None 

Analyzing 

Explanation: This is a status message for the 

distributed scanner. It is analyzing assets. 



Module: 

DMH5398I 

WsaaJar 


None 

Scanning 


distributed scanner. It is scanning assets. 



Module: 

DMH5399I 

WsaaJar 


None 

Deleting 


distributed scanner. It is deleting assets. 



Module: 

WsaaJar 


None 



DMH5400I Current status 

Explanation: This message is a label for the current 

status of the distributed scanner. 




DMH5406I FINISHED 

Explanation: The distributed scanner has finished 

processing assets. 




DMH5401I Current asset 

Explanation: This message is a label for the asset 

currently being processed by the distributed scanner. 




DMH5407I POST PROCESSING 

Explanation: The distributed scanner postprocessor is 

running. 




DMH5402I Current activity 

Explanation: This message is a label for the current 

activity of the distributed scanner. 




DMH5408I Scanner Manager is FINISHED... 

Explanation: The distributed scanner has finished 

processing assets. 




DMH5403I RUNNING 

Explanation: The distributed scanner is running. 




DMH5404I STOPPED 

Explanation: The distributed scanner has been 

stopped. 




DMH5405I PAUSED 

Explanation: The distributed scanner has been paused. 




DMH5409I Resume scanning 

Explanation: The distributed scanner is resuming 

processing after a pause. 




DMH5410I User has pressed START 

Explanation: A user has pressed the START button on 

the distributed scanner. 




DMH5411I User has pressed STOP 

Explanation: A user has pressed the STOP button on 

the distributed scanner. 






DMH5412W The control flow for program program 

name was too complex to fully compute. 

This partial diagram is the result of 

iteration limit iterations. 

Explanation: The algorithm for computing the control 

flow has to follow all possible instruction paths in the 

user program. In a very complex program it could 

require a lot of resources. The user configurable 

iteration limit has been imposed. 


Partial results displayed. 

User response: If a more complete control flow 

diagram is needed, have your Rational Asset Analyzer 

administrator update the Common.cfg (section: 

ControlFlow; value: maxIterations) to allow more 

iterations. 

Module: 

DMH5413I 

WsaaJar 

Now processing scan root scan root 

Explanation: This message displays the scan root 

being processed by the product. 



Module: 

DMH5414E 

WsaaJar 


None 

Unexpected exception exception, in 

scanner scanner, while scanning scan 

root scan root. 

Explanation: The scanner shown in the message 

produced an unexpected exception while scanning the 

scan root shown. Exception details are shown in 

exception. 

System action: The scanner skips the current scan root 


User response: Correct the scan root parameters or 

scanner information in the configuration and reinsert 

the scan root. 

Module: 

DMH5415E 

WsaaJar 

Exception thrown in post processor: 

type=[className], message=[message] 

Explanation: An exception was thrown from the class 

shown with the message shown during the 

postprocessing phase. 

System action: The scanner skips the current scan root 



representative 

Module: 

WsaaJar 

Contact your IBM technical-support 

DMH5416W Graph cannot be displayed 

Explanation: The SVG graph cannot currently be 

displayed. The most likely cause is that the distributed 

postprocessor has not been run. 



Module: 

WsaaJar 

Graph display aborted. 

Run the distributed postprocessor. 

DMH5417W Required attribute [attributeName] not 

specified. 

Explanation: The user needs to enter a value for the 

specified attribute before the requested summary page 

can be displayed. 



the page. 

Module: 

WsaaJar 

Processing for the query is stopped. 

Enter the required value and resubmit 

DMH5418W Value for required attribute 

[attributeName] is not valid: 

problemStatement 

Explanation: The user-entered value for the specified 

attribute is not valid. 



page. 

Module: 

DMH5419E 

WsaaJar 

Processing for the query is stopped. 

Enter a valid value and resubmit the 

The parenthesis at index is not preceded 

by an option. 

Explanation: An open parenthesis can only follow the 

name of an option. 



operation. 

Module: 

WsaaJar 

Processing the options stops. 

Correct the syntax error and retry the 

DMH5420W Value specified for field 'fieldName' 

exceeds the maximum length of 'length' 

characters 

Explanation: 

long. 



Module: 

WsaaJar 

The value of the field specified is too 

Waiting for valid input. 

Enter a shorter value. 



DMH5421E 

Action aborted because autocommit is 

enabled on database connection. 

Explanation: Autocommit is enabled on the database 

connection in an area of the code where autocommit 

must be disabled (e.g. using table locks or global 

temporary tables). 


stopped. 


Module: 

WsaaJar 

Processing of the current action is 


DMH5422W Impact analysis is on the work queue, 

waiting to start... 

Explanation: Impact analysis is on the work queue, 

waiting to start. It cannot start immediately due to the 

limit imposed on concurrent analyses. 



Module: 

DMH5423I 

WsaaJar 


None 

Reanalysis of impact was attempted. Try 

again when fewer analyses are running. 

Explanation: Impact analysis could not be started due 

to the limit imposed on how many concurrent analyses 

can be running. Any existing results remain the same 

until analysis is restarted. 

System action: The system is functioning normally, 

based on a configurable limit on concurrent impact 

analyses. 

User response: Try the impact analysis again when 

there are fewer concurrent analyses running. 

Module: 

WsaaJar 

DMH5424W Impact analysis forced to stop. Results 

may be incomplete. 

Explanation: Impact analysis was forced to stop. 

Results may be incomplete. The stop was forced by the 

user or automatically by a configurable limit imposed 

on how many impacts can be investigated. 

System action: If the user requested to stop or cancel 

the impact analysis, then the system is functioning 

normally. Otherwise, the system has encountered a 

long-running analysis (based on a configurable limit of 

how many impacts should be investigated) and has 

been instructed to automatically stop analysis. 

User response: If the impact analysis was not forced 

to stop by the user, investigate why the impact analysis 

might be finding so many impacts. Notify your 

Rational Asset Analyzer administrator to determine if 

the configurable limit of how many impacts to 

investigate should be altered. 

Module: 

WsaaJar 

DMH5425W Asset of type type and id id does not 

exist in database. 

Explanation: An asset of type type and id id was 

requested for impact analysis but does not exist in the 

database. 


interrupted. 

Impact analysis processing is 

User response: Delete the impact analysis. If the 

starting asset with the original name still exists (the id 

may be different), then a new impact analysis may be 

created with it. 

Module: 

DMH5426E 

WsaaJar 

Impact analysis of a type type of asset is 

not supported. 

Explanation: Impact analysis of a type type of asset 

was requested, but this type of analysis is not 

supported 


interrupted. 


Module: 

WsaaJar 

Impact analysis processing is 


DMH5427W Impact analysis was interrupted 

processing type name in level level. 

Analysis results may be incomplete. 

Explanation: Impact analysis has been interrupted or 

canceled while processing type name in level level. 

Analysis results may be incomplete. 

System action: The process for analyzing an asset's 

impact has been interrupted. 

User response: Depending on why the impact analysis 

was interrupted, the user may choose to restart the 

analysis at a later time. 

Module: 

DMH5428I 

WsaaJar 

End-to-end postprocessor successfully 

started 

Explanation: Distributed postprocessor started in a 

separate thread 



Module: 

System is functioning normally 

None 

WsaaConfigMgr 



DMH5429W End-to-end postprocessor could not be 

started. Another process was already 

running. 

Explanation: A user initiated the end-to-end 

postprocessor on the runtime. 

System action: The request is ignored because 

scanning or postprocessing is occurring. 


Module: 

DMH5431E 

WsaaJar 

Retry the request at a later time 

Summary page invoked with 

unsupported type cmpntType 

Explanation: The component type specified in the 

URL parameter "cmpntType="cmpntType invoking the 

summary page is not recognized 


An error message is displayed. 

User response: Make sure the URL is correct. This 

error usually occurs if the URL is stored in an external 

locale or when external UrlApi syntax is used to launch 

the browser with the summary page. Notify the author 

of the document or vendor providing the URL link. 

Module: 

DMH5432E 

WsaaConfigMgr 

Custom query ID was set to zero when 

Cq.retrieveFromDb() was called. 

Explanation: While processing a custom query 

request, Rational Asset Analyzer set the query ID to an 

invalid value. 

System action: The attempt to retrieve a custom query 

from the database failed. 


Module: 

DMH5433E 

WsaaJar 


Attempting to retrieve custom query 

with unknown ID. cq_ID=[cqId] 

Explanation: While processing a custom query 

request, Rational Asset Analyzer attempted to retrieve a 

custom query with anunknown ID; cq_ID=[cqId]. 

System action: An attempt to retrieve a custom query 

from the database failed. 


Module: 

DMH5434E 

Explanation: 

WsaaJar 


Custom query could not be persisted to 

database because autocommit was 

enabled on the connection. 

CQ_ID=[cqId] 

While processing a request to save a 

custom query, Rational Asset Analyzer detected an 

invalid autocommit setting. 

System action: An attempt to save a custom query to 

the database failed. 


Module: 

DMH5435E 

WsaaJar 


Problem encountered while trying to 

parse export-cq file: errMsg=[errMsg] 

Explanation: The export-cq file could not be properly 

parsed by the DOM parser. 

System action: The attempt to retrieve export-cq file 

into memory failed. 

User response: Verify that the content of the export-cq 

file is valid XML. 

Module: 

DMH5436E 

WsaaJar 

Duplicate column name encountered: 

[columnName]. Please rename one of the 

columns (using the SQL syntax 

'COLUMN AS X'). 

Explanation: Custom queries are not allowed to 

contain duplicate column names. 


The user is prompted for new input. 

User response: Modify the SQL query so that it no 

longer contains duplicate column names. 

Module: 

DMH5437E 

WsaaJar 

Column [columnName] contains an 

invalid character. Names cannot contain 

the following characters: [-|+=,&] 

Explanation: Custom queries are not allowed to 

contain columns with the characters specified. 



User response: Modify the SQL query so that the 

column no longer contains any invalid characters. 

Module: 

DMH5438E 

Explanation: 

column. 

WsaaJar 



Module: 

At least one column must be specified 

as a view column. 

WsaaJar 

You must specify at least one view 


Specify one or more view columns. 



DMH5439E 

Temporary restriction: You are only 

allowed to select a single column as the 

main search column. 

Explanation: Rational Asset Analyzer supports 

specifying only a single column as the main search 

column. 



search column. 

Module: 

DMH5446E 

WsaaJar 


Specify only one column as the main 

Invalid link type: linktype 

Explanation: 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 Rational 

Asset Analyzer product. 

System action: Analysis for the asset stops, and the 

error is logged. Analysis continues for the next asset. 







the problem. 

Module: 

DMH5447E 

WsaaJar 

Invalid table name: table 

Explanation: The specified DB2 table name is invalid 

or is not defined in the Rational Asset Analyzer 

database. 

System action: Analysis for the asset associated with 

the specified table stops, and the error is logged. 

Analysis continues for the next asset. 



instructions in the Configuration and Migration Guide 

and that the Rational Asset Analyzer database was 

created successfully. If the specified table name is not in 

the Rational 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. 

Module: 

DMH5448E 

WsaaJar 

Invalid field name: table:table, field field 

Explanation: The specified field name for a DB2 

column in the DB2 table indicated is not found in the 

Rational 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. 






the Rational Asset Analyzer schema or the column 

indicated does not exist for that table, ensure that you 


/assetloc/config/Analyzers.cfg. Contact your IBM 


Module: 

DMH5449E 

WsaaJar 

Invalid field type: table:table name, 

field:field name, type: type name 

Explanation: 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. 

System action: Analysis for the asset associated with 

the specified table and field stops, and the error is 

logged. Analysis continues for the next asset. 






the Rational Asset Analyzer schema or the column 

indicated does not exist for that table, ensure that you 


/assetloc/config/Analyzers.cfg . Contact your IBM 


Module: 

DMH5450E 

WsaaJar 

You are not allowed to mix columns of 

different data types for the main search 

field. 

Explanation: Because the search argument format is 

different for text/numeric/timestamp search fields, you 

are not allowed to combine different column types for 

the main search field. 



type. 

Module: 

DMH5451E 

WsaaJar 


Specify only columns of the same data 

You must specify one or more default 

view columns. 

Explanation: When creating a custom query, you must 

specify one or more default view columns. 





User response: Specify one or more default view 

columns. 

Module: 

DMH5452E 

WsaaJar 

You must select at least one 

JavaProcessor pattern 

Explanation: Distributed runtime environments 

require at least one JavaProcessor pattern to be valid. 



pattern. 

Module: 

DMH5453E 

WsaaJar 


Select at least one JavaProcessor 

$Map var could not be resolved, and no 

default value was specified: $Map{arg} 


resolve the specified variable, and no default was 

supplied. 



Module: 

DMH5454E 

Explanation: 

WsaaJar 



XML file. 

Module: 

DMH5455E 

Explanation: 

Current processing is stopped. 


Must enter a valid custom query XML 

file 

WsaaJar 



XML file. 

Module: 

DMH5456E 

The specified path was not valid. 


Enter a valid path to a custom query 

Must enter a valid URL to a custom 

query XML file 

WsaaJar 

The specified URL was not valid. 


Enter a valid URL to a custom query 

I/O exception encountered trying to 

download file 

Explanation: An I/O exception occurred while trying 

to download the custom query XML file. This error is 

likely caused by a network problem. 



time. 

Module: 

WsaaJar 


Try downloading the file at a later 

DMH5457E 

No custom queries defined in the 

specified document 

Explanation: No custom query definitions could be 

found in the file specified. 



User response: Update the URL/path to point to a 

valid custom query XML file. 

Module: 

DMH5458E 

WsaaJar 

At least one custom query must be 

selected 

Explanation: You must select at least one custom 

query to import or click Cancel. 



User response: Select at least one custom query to 

import or click Cancel. 

Module: 

DMH5459E 

WsaaJar 

Invalid site passed to 

QueryService.addDistScanRoot(). 

Site=[site] 

Explanation: The site passed to 

QueryService.addDistScanRoot() could not be located in 

the database. 



Module: 

DMH5460E 

WsaaJar 

The action is cancelled. 


Invalid resource manager passed to 

QueryService.addDistScanRoot(). 

Resource manager=[resourceMgr] 

Explanation: The resource manager passed to 

QueryService.addDistScanRoot() could not be located in 

the database. 



Module: 

DMH5461E 

Explanation: 

WsaaJar 



Module: 



SQL exception occurred while trying to 

insert values into global temporary table 

[tempTableName]. sqlCode=[sqlCode] 

WsaaJar 






DMH5462E 

NumberFormatException occurred while 

trying to insert values into global 

temporary table [tempTableName]. id=[id], 

errMsg=[errMsg] 

Explanation: A NumberFormatException was thrown 

while trying to parse an ID part as the data type 

expected. 



Module: 

DMH5463E 

Explanation: 

WsaaJar 



Module: 



SQL exception occurred while trying to 

create global temporary table 

[tempTableName]. 

sqlCode=[e2.getErrorCode()], 

sqlMsg=[e2.getMessage()] 

WsaaJar 




DMH5464W Source file not found. 

Explanation: Source file [pathName] cannot be located. 

The file could be deleted or temporarily inaccessible. 



Module: 

DMH5465E 

WsaaJar 


Rescan the affected scan root. 

The container "container name" cannot be 

added to this concatenation set. This 

concatenation set is used for SQL. 

Explanation: Concatenation sets that are used for SQL 

resolution can have only PDS or NTFS containers. 

System action: The container is not added to the 

concatenation set. 

User response: To add the container to the 

concatenation set, you must first unassign the 

concatenation set from any other files that use it for 

SQL resolution. 

Module: 

WsaaJar 

User response: To add the container to the 

concatenation set, you must first unassign the 

concatenation set from any sites, applications, or 

containers that use it for default SQL resolution. 

Module: 

DMH5467E 

WsaaJar 

The concatenation set "concatenation set 

name" cannot be used for SQL. It has 

number of containers container(s) of type 

"container type". 

Explanation: A concatenation set used for SQL can 

only have containers that are of type PDS or NTFS. The 

following container(s) were the incorrect type: container 

names 


The concatenation set is not assigned. 

User response: Either remove the invalid container(s) 

from the concatenation set and then retry or create a 

different concatenation set with containers that are all 

valid for use as an SQL concatenation set. 

Module: 

DMH5468E 

WsaaJar 

The application description can only be 

maximum length characters. 

Explanation: The application description is too long 

by length character(s). The maximum length is maximum 

length. 


The application is not updated. 

User response: Shorten the application description 

and retry the request. 

Module: 

DMH5469E 

WsaaJar 

No HLQ parameter specified on Remote 

Request URL. 

Explanation: The Remote Request URL did not 

include the HLQ parameter to indicate the Rational 

Asset Analyzer installation high-level qualifier. 


The Remote Request is canceled. 

User response: Ensure that the Common.cfg file has 

an HLQ property in the MVS section and that it 

correctly identifies the high-level qualifier where the 

product is installed. 

Module: 

WsaaJar 

DMH5466E 

The container "container name" cannot be 

added to this default concatenation set. 

This concatenation set is used for SQL. 

Explanation: Concatenation sets that are used for SQL 

resolution can have only PDS or NTFS containers. 

System action: The container is not added to the 

concatenation set. 

DMH5471E 

Installation parameter data set dsn not 

found or cannot be accessed. 

Explanation: The Remote Request server attempted to 

read data set dsn but either the data set or member 

does not exist, or you do not have the authority to read 

it. 


The Remote Request is canceled. 



User response: Ensure that the product configuration 

step was completed, including the setup option in 

DMHINSTL. Ensure that the Common.cfg file has the 

correct HLQ property value in the MVS section. Make 

sure WebSphere Application Server is restarted after 

updating Common.cfg. 

Module: 

WsaaJar 

DMH5472W Ignoring count asset type assets. 

Explanation: Scanning options can only be specified 

for the following assets: 

v File and program assets whose language is COBOL, 

PL/I or unknown 

v containers 

v Sites 

v Applications 

All others are ignored. 

System action: The assets are ignored. The scanning 

options will be applied to the remaining assets. 


Module: 

DMH5473E 

None 

WsaaConfigMgr 

The options token has no text. 

Explanation: While reading the options, a token was 

encountered that has no text. 



operation. 

Module: 

DMH5474E 

WsaaJar 



The value of "option" must be a number. 

The value found was: value. 

Explanation: The option is required to be a number, 

but some other type of data was specified. 



operation. 

Module: 

DMH5475E 

WsaaJar 



"option" requires a single suboption. 

Explanation: The option requires that a single 

suboption be specified. 



operation. 

Module: 

WsaaJar 



DMH5476E 

The value of "option" must be a quoted 

literal. The value found was: value. 

Explanation: The option is required to be literal text 

surrounded by quotes, but some other type of data was 

specified. 



operation. 

Module: 

DMH5477E 

WsaaJar 



The value of "option" must be a number. 

The value found was: value. 

Explanation: The option is required to be a number, 

but some other type of data was specified. 



operation. 

Module: 

DMH5478E 

WsaaJar 



The value of "option" must be a number 

or a number followed by K. The value 

found was: value. 

Explanation: The option is required to be a number or 

a number followed by K (for example, 100K), but some 

other type of data was specified. 



operation. 

Module: 

DMH5479E 

WsaaJar 



"option" has an invalid value. The value 


Explanation: The option does not support the 

specified value. 



operation. 

Module: 

DMH5486E 

Explanation: 

another. 

WsaaJar 



operation 

Module: 



Unbalanced single-quotes found at 

index index. 

WsaaJar 

Each single-quote must be paired with 





DMH5487E 

An error occurred while executing the 

SQL statement "sql" with 

parameters=parms 

Explanation: An error occurred attempting to execute 

the SQL statement with the specified parameters. 

SQL error information: SQLCODE=sqlCode 

SQLSTATE=sqlState 

The SQLCODE and SQLSTATE are detailed in the DB2 

manual. 

System action: If applicable, no database updates are 

made and the database is rolled back. 

User response: Examine any SQL error and attempt to 

fix any problems. Retry the action or contact your IBM 


Module: 

DMH5488E 

Explanation: 

WsaaJar 



operation. 

Module: 

DMH5489E 

The option "option" requires a value. 

WsaaJar 

The option is required to have a value. 



The value of "option" must be text. The 

value found was: value. 

Explanation: The option is required to be text, but 

some other type of data was specified. 



operation. 

Module: 

DMH5490E 

WsaaJar 




Tag as it does not have physical 







asset. 







the problem. 

Module: 

WsaaJar 

DMH5491E 

Explanation: 

parenthesis. 



operation. 

Module: 

DMH5492E 

Explanation: 

Unbalanced parentheses found at index 

index. 

WsaaJar 



operation. 

Module: 

DMH5493E 

Each open parenthesis must have a close 



No value was specified for the option at 

index index. 

WsaaJar 

The option must specify a value. 



The comma is not followed by a value 

at index index. 

Explanation: A comma can only be specified if it is 

followed by another value for the option. 



operation. 

Module: 

DMH5494E 

WsaaJar 



The comma is not preceded by a value 

at index index. 

Explanation: A comma can only be specified if it is 

preceded by another value for the option. 



operation. 

Module: 

DMH5495E 

WsaaJar 



An embedded blank character was 

found at index index. 

Explanation: Blank characters are not allowed in the 

options except within quoted strings. 



operation. 

Module: 

WsaaJar 





DMH5496E 

Explanation: 

another. 



operation. 

Module: 

DMH5497E 

Explanation: 

Unbalanced double-quotes found at 

index index. 

WsaaJar 



operation. 

Module: 

DMH5498E 

Explanation: 

option. 

Each double-quote must be paired with 



Missing comma before token. 

WsaaJar 



operation. 

Module: 

DMH5499E 

Explanation: 

option. 

A comma must precede the token. 



Option "option" requires a value of 

MAX, a number, or a number followed 

by K. The value found was: value. 

WsaaJar 



operation. 

Module: 

DMH5500E 

An invalid value was specified for the 



Option "option" requires a 1- to 

4-character value. The value found was: 

value. 

WsaaJar 

An invalid value was specified for the 



Unable to add JNDI mappings: 

=exceptioncode 

Explanation: The DB2 exception specified has been 

encountered while attempting to add the JNDI 

mappings to the Rational Asset Analyzer database. The 

Rational Asset Analyzer logs may contain more 

information on the context of this exception. 



asset. 

User response: Ensure that the Rational Asset 

Analyzer application can correctly communicate with 

DB2 to write information to the database. Correct any 

issues and attempt the scanning operation again. 

Module: 

DMH5501E 

WsaaJar 

Unable to add Install Infos: asset 

Explanation: This is an unexpected error related to an 

inconsistency in the defined Rational 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 Rational 

Asset Analyzer during creation of the Rational Asset 




asset. 




Migration Guide. Capture all logs related to the error 

and Contact IBM Software Support. 

Module: 

DMH5502E 

Explanation: 

value. 

WsaaJar 



operation. 

Module: 

DMH5503E 

Option "option" cannot have a value. The 

value found was: value. 

WsaaJar 

The option does not support having a 



Option "option" is not supported. 

Explanation: An unsupported option was specified, or 

the option was specified in the wrong context. 



operation. 

Module: 

DMH5504E 

WsaaJar 



Option "option" only supports a 

PROCESS(filename) value. The value 


Explanation: An unsupported option was specified, or 

the option was specified in the wrong context. 



operation. 

Module: 

WsaaJar 





DMH5505E 

Option "option" has too few values 

specified. At least min are required, but 

count were found. 

Explanation: The option has an invalid number of 

values specified. 



operation. 

Module: 

DMH5506E 

WsaaJar 



Option "option" has too many values 

specified. No more than max are 

allowed, but count were found. 

Explanation: The option has an invalid number of 

values specified. 



operation. 

Module: 

DMH5507E 

WsaaJar 



A type of asset for the user-defined 

relationship must be selected. 

Explanation: A type of asset must be specified for the 

source and target of a user-defined relationship. 



continue. 

Module: 

DMH5508E 

WsaaJar 


Select an asset type in order to 

A user-defined relationship named 

"name" already exists. 

Explanation: A unique name must be specified for the 

user-defined relationship. 



User response: Enter a unique name for the 

user-defined relationship. 

Module: 

DMH5510E 

WsaaJar 

User-defined relationship cannot be 

found. 

Explanation: The user-defined relationship cannot be 

found. No user-defined relationship with the specified 

name or ID exists: "nameOrId" 



relationship. 

Module: 

WsaaJar 


Select an existing user-defined 

DMH5511W No assetType matches the search criteria. 

Explanation: No assetType matches the search criteria. 

The search criteria results in filtering based on: 

searchCriteria. 



User response: Update the selected search criteria, or 

keep it as is for future refreshes of the user-defined 

relationship. The relationship will be considered stale 

until the search criteria match one or more assetTypes. 

Module: 

DMH5512I 

WsaaJar 

User-defined relationship refresh has 

occurred. 


indicating that at least one user-defined relationship 

has been refreshed. 



User response: Verify that the user-defined 

relationships are not stale. (Relationships will continue 

to be stale if no assets matching the search criteria were 

found.) 

Module: 

WsaaJar 

DMH5513W User-defined relationship refresh did 

not occur. 

Explanation: This is a warning message alerting the 

user that a user-defined relationship could not be 

refreshed because it is no longer defined. 



User response: Verify that the user-defined 

relationship does exist. If it exists, delete it and 

re-create it. 

Module: 

WsaaJar 

DMH5514W Invalid date entered [seg]. 


user that an invalid date was entered. 



Module: 

WsaaJar 

Query aborted. 

Enter a valid date. 

DMH5515W Numeric value did not match pattern: 

[arg]. 


user that a numeric value did not match the pattern in: 

[arg]. 




Enter a valid numeric value. 



Module: 

WsaaJar 

DMH5516W Unknown operand encountered: [op]. 


user that an unknown operand was encountered. 



Module: 

DMH5517E 

WsaaJar 


Enter a valid operand. 

The wsaaConfig directory [wsaaConfig] 

does not exist, or is not readable. 

Explanation: This is an error message alerting the user 

that the wsaaConfig directory [wsaaConfig] does not 

exist, or is not readable. 

System action: Rational Asset Analyzer was not 

initialized; processing is stopped. 

User response: Examine the settings in Common.cfg 

to determine whether you have specified an existing 

directory in the wsaaConfig parameter. If it exists, 

ensure that it can be read from. 

Module: 

WsaaJar 

DMH5518W Problems encountered with end-to-end 

definition file; see Warnings for details. 


user that there are problems associated with the 

end-to-end definition file. See work queue warnings for 

details. 


System is functioning as expected. 

User response: View work queue warnings to see 

what problems were encountered. Correct problems in 

the definition file. 

Module: 

DMH5519I 

WsaaJar 

End-to-end definition file processed; see 

Messages for details. 


indicating that the end-to-end definition file was 

processed. See work queue messages for details. 


System is functioning as expected. 

User response: View work queue messages to see 

end-to-end definition file details. 

Module: 

DMH5520I 

WsaaJar 

Exception occurred while scanning 

resource name; database rollback 

performed. 

Explanation: 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. 

System action: The error is logged, and the next asset 

is scanned. The Rational Asset Analyzer error logs 

contain information on the state of the scanner. The 

system is functioning normally. 


logs for information on the errors encountered during 

scanning. Correct all problems and attempt the 

scanning operation again. 

Module: 

DMH5521I 

WsaaMain 

Exception occurred while analyzing 

resource name; database rollback 

performed. 

Explanation: 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. 

System action: The error is logged, and the next asset 

is scanned. The Rational Asset Analyzer error logs 

contain information on the state of the scanner. The 

system is functioning normally. 


logs for information on the errors encountered during 

analysis. Correct all problems and attempt the scanning 


Module: 

DMH5522I 

WsaaMain 

found-in-DB. 


to the Rational Asset Analyzer logs indicating that the 

scanning process has been invoked for a resource that 

already exists in the Rational Asset Analyzer database. 

The information stored in the database related to that 

resource will be updated. 



Module: 

DMH5523I 


None 

WsaaMain 

scan... 


to the Rational Asset Analyzer logs indicating that the 

scanning process has started for the specified resource. 



Module: 


None 

WsaaMain 



DMH5524E 

Resource not found name 

Explanation: 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. 

System action: Scanning on the specified resource is 

stopped. Processing continues for the next scanner. 

User response: Ensure that the resource exists within 

the scope of the scanning root indicated in 

/assetloc/config/Admin.cfg and attempt the scanning 


Module: 

DMH5525E 

WsaaMain 

Data set 'data set name' was not found or 

cannot be accessed. 

Explanation: This is an error message indicating that 

the requested data set could not be found, or you do 

not have the authority to access it for reading. 


displayed. 


User response: Make sure that the data set exists and 

that you have the authority to access it for reading. 

Module: 

DMH5526E 

WsaaJar 

Data set 'data set name' has an 

unsupported type 'type.' 


that the data set type is not supported. The following 

types are supported: PO and PS (PDS, PDS/E, and 

sequential). In addition, the GDG base is supported if 

the GDG consists of sequential data sets. Generation 

data sets are supported if they are PO or PS data sets. 


displayed. 


Module: 

DMH5527E 

WsaaJar 


None 

Member 'member' not found in data set 

'data set name.' 


that the member does not exist in the named data set. 


displayed. 


Module: 

WsaaJar 


None 

DMH5528E 

Data set 'data set name' has unsupported 

record format 'recfm.' 


the record format of the data set is not supported, so 

the data set cannot be read. The supported record 

formats begin with F or V. 


displayed. 


Module: 

DMH5529E 

WsaaJar 


None 

Generation 'generation' not found for 

GDG 'data set name.' 


that the generation data group does not have the 

specified generation. 


displayed. 


Module: 

DMH5530E 

WsaaJar 


None 

Authorization error accessing data set 



you do not have the authority to access the data set. 


displayed. 


Module: 

DMH5531E 

WsaaJar 


None 

Unknown error 'error' accessing data set 


Explanation: An unknown error occurred while trying 

to access the data set. 


displayed. 


Module: 

DMH5532E 

WsaaJar 



The following error occurred while 

accessing data set 'data set name:' error 

message 

Explanation: The specified error occurred while trying 

to access the data set. 


displayed. 


User response: Use the detail from the displayed error 

message to correct the problem and retry. 



Module: 

WsaaJar 

Module: 

WsaaJar 

DMH5533E 

Data set 'data set name' is not partitioned. 

The DSORG is 'DSORG.' 


that the data set is not partitioned. It must be 

partitioned in order to determine the members. 


displayed. 


Module: 

DMH5534E 

WsaaJar 


None 

The GDG 'data set name' does not consist 

of sequential data sets. The type found 

was 'type.' 


that a request was made to view the contents of the 

GDG base; however, that action can only be performed 

for generation data groups that consist of sequential 

data sets. 


displayed. 


Module: 

DMH5536E 

WsaaJar 


None 

Invalid character "invalid character" in 

name "name". 

Explanation: An invalid character was found in the 

name entered. To proceed, the name must be corrected. 


name. 



Module: 

DMH5540E 

WsaaJar 

The user is prompted again for the 

Correct the name and submit the 

Method not implemented 

Explanation: An attempt was made to obtain 

resources directly from a ClearCase repository, but that 

function is not yet supported by Rational Asset 

Analyzer. The error may indicate an inconsistency in 

the Rational Asset Analyzer installed code or the 


System action: Scanning is stopped. Processing 

continues for the next scanner. 


installed and configured the Rational 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 IBM 


DMH5580E 


Explanation: An attempt was made to obtain 

resources directly from a CVSS repository, but that 

function is not yet supported by Rational Asset 

Analyzer. The error may indicate an inconsistency in 

the Rational Asset Analyzer installed code or the 


System action: Scanning is stopped. Processing 








Module: 

DMH5582E 

WsaaJar 

Trouble performing checkout for: name 


of resources in a CVSS repository while attempting to 

check out data. Details about why the checkout 

operation failed can be found in the Rational Asset 

Analyzer error logs. It may be that the Rational Asset 

Analyzer application cannot communicate with CVSS 

or that user logon information is incorrect. 

System action: Scanning is stopped for the specified 

resource. The error is logged, and processing continues 

for the next scanning root. 


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 


Module: 

DMH5583E 

WsaaJar 

Trouble getting a CVS key for name 

Explanation: A key allowing Rational 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. 


resource. The error is logged, and processing continues 

for the next scanning root. 

User response: Ensure that CVSS can be accessed for 

the resource name specified and attempt the scanning 


Module: 

WsaaJar 



DMH5601E 

The file was not found name 

Explanation: An attempt was made to scan a file 

system but the specified file was not found in the 

scanning root. 

System action: Scanning is skipped for the asset 

indicated. Processing continues for the next asset. 

User response: Ensure that the specified file exists 

within the scanning root identified for file system 

scanning in /assetloc/config/Admin.cfg and attempt 


Module: 

DMH5610E 

WsaaJar 

More than one instance found in the 

database for Version Extension [Table = 

tablename and ID = id] 


attempting to retrieve metadata for an asset from the 

table specified using the identifier specified because 

multiple instances exist for this same identifier. Rational 

Asset Analyzer expects a single instance to be returned. 

This error may indicate an inconsistency in the 

metadata stored for Rational Asset Analyzer. 


associated with the table and ID indicated. The error is 

logged, and processing continues for the next asset. 


Module: 

DMH5620E 

WsaaJar 



database for [Path name = pathname, File 

name = filename, and Scanner ID = id]. 


attempting to retrieve metadata for an asset specified 

by path, file, and scanner identifier in the Rational 

Asset Analyzer database because multiple instances 

exist matching these criteria. Rational Asset Analyzer 

expects a single instance to be returned. This error may 

indicate an inconsistency in the metadata stored for 



associated with the specified search criteria. The error is 



Module: 

DMH5621E 

WsaaJar 


File resource with ID = id has a parent 

container with ID = parentid but a null 

parent was used to access the resource. 


attempting to retrieve metadata for an asset with the 

database identifier specified in the Rational 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 Rational 

Asset Analyzer. 





Module: 

DMH5622E 

WsaaJar 


File resource with ID = id has a parent 

container with ID = parentid but a 

different parent id = parentid2 was used 

to access the resource. 


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 Rational Asset Analyzer. 





Module: 

DMH5630E 

WsaaJar 



database for [IP = ipaddress and Name = 

sitename] 

Explanation: An attempt was made to retrieve a single 

site instance from the Rational Asset Analyzer database 

using the specified search criteria, but more than one 

site was returned. Rational Asset Analyzer expects only 

a single site with the same IP address, name, and 

platform identifier. This error may indicate an 

inconsistency in the Rational Asset Analyzer database. 

System action: The distributed servlet cannot be 

initialized, so processing is stopped. The errors are 

logged. 


Module: 

DMH5640E 

WsaaJar 



database for [Path name = pathname and 

Scanner ID = scannerid]. 


container instance from the Rational Asset Analyzer 

database using the specified search criteria, but more 

than one matching asset was returned. This error may 

indicate an inconsistency in the Rational Asset Analyzer 

database. 




currently being processed. The error is logged, and 

processing continues for the next asset. 


Module: 

DMH5650E 

WsaaJar 



database for [Site ID = siteid, Name = 

name, and Type = type]. 


scanner instance from the Rational Asset Analyzer 


than one matching scanner was returned. This error 

may indicate an inconsistency in the Rational Asset 



currently being processed by this scanner. The error is 



Module: 

DMH5651E 

WsaaJar 



database for [Name = name and Type = 

type]. 


scanner instance from the Rational Asset Analyzer 


than one matching scanner was returned. This error 




currently being processed by this scanner. The error is 



Module: 

DMH5660E 

WsaaJar 



database for [Path name = pathname, File 

name = filename, and Scanner ID = 

scannerid]. 


asset instance from the Rational Asset Analyzer 




database. 


currently being processed. The error is logged, and 

processing continues for the next asset. 


Module: 

WsaaJar 


DMH5670E 


database for [Name = name, Access URL 

= url, and Scanner ID = scannerid]. 






database. 

System action: Scanning is skipped for the current 

scanner being used. The error is logged, and processing 



Module: 

DMH5700E 

WsaaJar 



database for [Repository = repository, 

Module = module, Revision = revision, 

and Scanner ID = scannerid ] 






database. 

System action: Scanning is skipped for the current 

scanning root. The error is logged, and processing 

continues for the next scanning root. 


Module: 

DMH5710E 

WsaaJar 



database for [Name = name and Short 

Name = shortname] 






database. 

System action: 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. 


Module: 

WsaaJar 




DMH5715E 


database for [Platform platform]. 


platform instance from the Rational Asset Analyzer 


than one platform was returned. This error may 


database. 

System action: The distributed servlet and scanner 

cannot be initialized, so processing is stopped. The 

errors are logged. 


Module: 

DMH5720E 

WsaaJar 


Files are found in the tablename table 

with no parent connection using 

tablename table. 


during scanning of file assets because some assets are 

found in the Rational Asset Analyzer database without 

containing parent assets. This error may indicate an 

inconsistency in the Rational Asset Analyzer database. 

System action: Scanning of these assets is skipped. 

The error is logged, and processing continues for the 

next asset. 


Module: 

DMH5740E 

WsaaJar 



Explanation: 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 Rational Asset Analyzer 

installed code or the environment classpath. 

System action: Scanning of the asset is skipped. 

Processing continues for the next asset. This error 

message may recur for all assets associated with the 

scanner. 







Module: 

DMH5742E 

WsaaJar 

Trouble performing get command for: 

name 


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 Rational Asset 

Analyzer error logs. It may be that the Rational Asset 

Analyzer application cannot communicate with PVCS 

or that user logon information is incorrect. 





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 


Module: 

DMH5743E 

WsaaJar 

Trouble getting a PVCS key for name 

Explanation: An attempt was made to retrieve a key 

manager for the PVCS scanner from the Rational Asset 

Analyzer database, but it was not found. This error 


Analyzer database or an internal code error. 



User response: Ensure that PVCS can be accessed for 

the scanning root as specified in /assetloc/config/ 

Admin.cfg and attempt the scanning operation again. 


Module: 

DMH5744I 

WsaaJar 

Bad PVCS root - scanningroot. skipping... 


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. 



continues for the next scanning root or scanner. 

User response: Ensure you have correctly specified 

the PVCS scanning root in /assetloc/config/Admin.cfg 


Module: 

DMH5745E 

WsaaJar 

Trouble extracting the release to the 

base directory for the PVCS scanner for 

the project project location 

Explanation: An attempt was made to extract a release 

to the base directory, but failure was reported. 



User response: Ensure that PVCS can be accessed for 

the scanning root as specified in /assetloc/config/ 

Admin.cfg and attempt the scanning operation again. 




Module: 

DMH5760E 

WsaaJar 

Trouble performing XMLConfig 

command from: wasbindir 

Explanation: An attempt was made to execute the 

XMLConfig command from the specified WebSphere 

Application Server, but an error occurred. An incorrect 

WebSphere Application Server directory may have been 

specified during installation or configuration of 


System action: Scanning is skipped for the WAS4AE 


continues with the next scanning root. 

User response: Ensure that the XMLConfig command 

can be issued by verifying the correct WebSphere 

Application Server directory is being used or fixing any 

other problem identified in the Rational Asset Analyzer 

or WebSphere Application Server error logs. Verify that 

the correct WebSphere Application Server directory is 

specified in Common.cfg. Attempt the scanning 


Module: 

DMH5762I 

WsaaJar 

Bad WAS4AE root - scanningroot 

skipping... 


indicating that an attempt was made to scan 

WebSphere Application Server for the scanning root 

specified, but scanning root does not have the correct 

format. 




User response: 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. 

Module: 

DMH5763E 

WsaaJar 

Cannot find xmlConfig file name 

Explanation: An error has occurred while attempting 

to find the specified XMLConfig file. This error could 

indicate a problem with the WebSphere Application 

Server directory specified during installation and 

configuration of Rational Asset Analyzer, or it may 

indicate that the file does not exist in the specified 


System action: Scanning is skipped for the specified 




specified the location of WebSphere Application Server 

on your Rational Asset Analyzer server and that the 

XMLConfig file exists in the location specified. Examine 

the settings in Common.cfg to determine what you have 

specified for WebSphere Application Server. Examine 

the specified scanning root file to ensure the correct 

location of the XMLConfig file. 

Module: 

DMH5780E 

WsaaJar 


Explanation: This message indicates an internal error 

caused by an incompatible combination of classes or an 

internal code error. The error may indicate an 


code or the environment classpath. 

System action: 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. 







Module: 

DMH5800I 

WsaaJar 

Context urlcontext already exists. 


indicating that an attempt was made to set a URL 

context that already exists. 

System action: The message is logged, and analysis 

continues normally. 


Module: 

DMH5801E 

WsaaJar 


Context urlcontext not found. 

Explanation: An unexpected error occurred. The 

specified context could not be found or is not defined 

for the current analysis process. 

System action: Analysis is skipped for the current 

asset. The error is logged, and processing continues for 

the next asset. 


Module: 

DMH5810E 

WsaaJar 


Not a legal call for method in class 

classname 


that a method that should not have been invoked has 

been called for the class specified. This error could 

indicate an inconsistency in your Rational Asset 

Analyzer installation. 





Module: 

DMH5811E 

WsaaJar 



Not an Integer stored in the IdsMapping 

classname 


that an Integer value was expected, but the specified 

object type was used instead. This error could indicate 

an inconsistency in your Rational Asset Analyzer 

installation. 



Module: 

DMH5830E 

WsaaJar 




Extracted resource as it does not have 

physical representation methodname 


encountered because a method that should not be 

invoked was called. This error could reflect an 

inconsistency in the installed Rational Asset Analyzer 

product, or an environment or classpath problem. 

System action: The scanning process is stopped, and 

the error is logged. 

User response: Ensure that you have installed 

Rational Asset Analyzer correctly according to 

instructions in the Configuration and Migration Guide. 


the problem cannot be resolved. 

Module: 

DMH5840E 

WsaaJar 

Unable to fully load the XML message 

file: xmlfile 

Explanation: Some messages might not be fully 

loaded into memory. When a message cannot be 

accessed, DMH5841E will be logged instead. 


been aborted. 

Reading the XML message file has 

User response: Make sure that the XML message file 

(xmlfile) is accessible to Rational Asset Analyzer. 

Module: 

DMH5841E 

WsaaJar 

Message number msgnum was not 

found; parameters: parms 

Explanation: 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. 


is accessible. 

Module: 

DMH5850E 

WsaaJar 

Make sure that the XML message file 

Unexpected exception while adding ref 

Explanation: A DB2 exception has occurred while 

attempting to create reference links in the metadata as a 

result of postprocessing. 


current link, and the error is logged. Processing 

continues for the next defined link. 

User response: Examine the Rational 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. 

Module: 

DMH5856I 

WsaaJar 

Found Pattern patterntype - class 


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. 

System action: This message is logged. The system is 

functioning normally. 


Module: 

DMH5870E 

WsaaJar 

None 

No temporary directory defined in 

system properties 


temporary directory specified by the tempDir parameter 

in Common.cfg, but no value has been specified for that 

property. 

System action: Postprocessing cannot continue. The 

error is logged. 

User response: Ensure that you have specified a valid 

and accessible temporary directory value in Common.cfg. 

Module: 

DMH5890E 

WsaaJar 

Cannot extract file filename to dir dirname 

using command. 


extract assets from the file specified. 

System action: Postprocessing for the current 

processor is skipped, and the error is logged. 



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. 

Module: 

DMH5900E 

WsaaJar 

Duplicate values for resource name 

Explanation: An unexpected error occurred because 

the same resource has been found to be the source for 

multiple target references in the metadata. Rational 

Asset Analyzer expects this source to be referenced by 

only one target. This error may indicate an 

inconsistency in the metadata stored in the Rational 

Asset Analyzer database. This message displays only 

when the system is run in debug level 3 or above. 

System action: Postprocessing for the specified 

resource is skipped. The error is logged, and processing 

continues for the next asset. The system continues to 

function normally. 

User response: Contact your IBM technical-support 

representative for further assistance. 

Module: 

DMH5910E 

WsaaJar 

Cannot get URL space for table table 

asset name 


retrieve the URL space for a WAR table asset. The 

source or target component is not found. 

System action: Postprocessing for the specified pattern 

is skipped. The error is logged, and processing 

continues for the next pattern. 


logs for any errors related to DB2 access problems. 


further assistance is required. 

Module: 

DMH5920E 

WsaaJar 

Cannot find pathname for physical asset 

id 


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. 

System action: Postprocessing for the current asset is 

skipped. Processing continues for the next asset. 





Module: 

WsaaMain 

DMH5921E 

Field not found name 

Explanation: An unexpected error occurred 


field or column specified in the asset's associated DB2 

table. This serious error indicates that the Rational 

Asset Analyzer schema may not have been created 

correctly during installation and configuration of the 

product. 




User response: Verify whether your Rational 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 


Module: 

DMH5922E 

WsaaMain 

No Physical Id for asset asset id in table 

table name 


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. 

System action: Pattern detection for the current asset 

is skipped. Processing continues for the next asset. 





Module: 

DMH5923E 

WsaaJar 

Asset not found: path name 





process. 







Module: 

WsaaMain 



DMH5924E 

Value not found: colname in table: 

tablename, for asset: name 



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. 




User response: Examine your Rational 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. 

Module: 

DMH5925E 

WsaaMain 

No asset for Physical Id physical id 





process. 







Module: 

DMH5930E 

WsaaJar 

No Class Implemented for name 


trying to find the implementing class for a servlet in 

DB2. Rational Asset Analyzer expects the class to be 

found in the database. 







Module: 

DMH5931E 

WsaaJar 

Duplicate values for name 


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 Rational 

Asset Analyzer database. 

System action: Pattern detection for the specified 

resource is skipped. The error is logged, and processing 



logs to determine if the problem was caused by an 

unexpected error accessing DB2. Contact your IBM 

technical-support representative for further assistance. 

Module: 

DMH5950E 

WsaaJar 

File name not found in database. 


trying to retrieve the identifier for the specified asset 

from the Rational Asset Analyzer database. Rational 

Asset Analyzer expects the asset to be in the database. 

System action: Pattern detection for the specified asset 






Module: 

DMH5951E 

WsaaJar 

Asset was not found in location 

exceptioncode 


trying to retrieve metadata for an asset during 

postprocessing. The cause of the exception is indicated. 







Module: 

DMH5973E 

WsaaJar 

Asset was not found in location location 


trying to retrieve metadata for an asset during 

postprocessing. The asset was expected to be in the 

location indicated. 







Module: 

WsaaJar 



DMH5974E 

Problem getting Ear for module name 


trying to retrieve metadata for an EAR file related to 

the specified asset during postprocessing. The cause of 

the exception is indicated. 







Module: 

DMH5975E 

WsaaJar 

No cell defined for table tablename index 

resourceid 

Explanation: An unexpected error occurred trying to 

retrieve metadata for the resource identifier in the 

specified table. Rational Asset Analyzer expects the cell 

to exist in the metadata. This message likely indicates 

an error in the WebSphere Application Server topology 

link postprocessor. 







Module: 

DMH5976E 

WsaaJar 

Could not resolve JNDI name refname 

Explanation: An unexpected error occurred trying to 

resolve the JNDI name associated with the specified 

reference in the Rational Asset Analyzer database. 







Module: 

DMH5977E 

WsaaJar 

Invalid Table Name: name 


attempting to retrieve a metadata identifier from the 

specified DB2 table, but that table is not defined in the 

Rational Asset Analyzer schema. 





according to instructions in the Configuration and 

Migration Guide and that the Rational Asset Analyzer 

database was created successfully. If the specified table 

exists in the schema, contact your IBM 


Module: 

DMH5978E 

WsaaJar 

Cannot get EJB JARs for server 

table:table index indexname 

Explanation: An unexpected DB2 exception has 

occurred while attempting to retrieve metadata for EJB 

JAR file assets that have been previously scanned and 

analyzed. 

System action: Postprocessing for the current 

processor is skipped. The error is logged, and 

processing continues for the next postprocessor. 


logs for errors related to DB2 access that can be 

corrected locally and attempt the operation again. 


further assistance. 

Module: 

DMH5980E 

WsaaJar 

No Servers Available 


determine the set of analyzable runtime servers defined 

in the Rational Asset Analyzer database. No servers 

have been defined, or they do not exist in the database. 

System action: Pattern detection is skipped for the 

current asset. Processing continues for the next asset, 






Module: 

DMH5981E 

WsaaJar 

Cannot instantiate bridge for analyzer 

name 


trying to instantiate an analyzable server based on the 

server analyzer class name specified. The name is 

retrieved from the Rational Asset Analyzer database, so 

it should be valid. This error may indicate an 


product, the environment, or the metadata. 


current asset, and the error is logged. Processing 




unexpected error accessing DB2 or by an inappropriate 

classpath or other path environment setting. Ensure 

that you have correctly installed and configured 



Rational Asset Analyzer according to instructions in the 

Configuration and Migration Guide. Contact your IBM 


Module: 

DMH5982E 

WsaaJar 

No Name for table: name 


to retrieve an analysis server name for the specified 

table. Rational Asset Analyzer expects a name to be 

associated with this table. 








Module: 

DMH5983E 

WsaaJar 

Incorrect database URL specified in 

Common.cfg: 'URL' 

Explanation: The setting 'Database.url' in Common.cfg 

does not appear to be a valid database. 


Servlet initialization is stopped. 

User response: Fix the specified configuration setting 

and restart the web application. 

Module: 

DMH5984E 

WsaaJar 

Incorrect database username and/or 

password specified in Common.cfg. 

Explanation: The setting 'Database.username' and/or 

'Database.password' in Common.cfg does not appear to 

be valid. 



User response: Fix the specified configuration 

setting(s) and restart the web application. 

Module: 

DMH5985E 

WsaaJar 

Database username specified in 

Common.cfg lacks necessary 

permissions. 

Explanation: The setting 'Database.username' in 

Common.cfg does not refer to a database user with 

permissions necessary for Rational Asset Analyzer. 



User response: Refer to the documentation on the 

permissions required, fix the specified configuration 

setting, and restart the web application. 

Module: 

WsaaJar 

DMH5986E 

A database connection could not be 

made. SQL error code = [ErrorCode] 

Explanation: An unknown error condition occurred 

while trying to create a connection to the database. 



User response: Check the log file for more 

information. Restart the web application after the 

problem has been fixed. 

Module: 

DMH5987E 

WsaaJar 

JDBC driver class could not be loaded: 

ClassName. 

Explanation: The JDBC driver class specified by the 

'Database.driver' setting in Common.cfg could not be 

loaded by the JVM. 



User response: Update the specified setting, or add 

the JDBC driver to classpath, and restart the Web 

application. 

Module: 

DMH5988E 

WsaaJar 

An SQL query unexpectedly returned 

zero rows. SQL=[SqlQuery] 

Explanation: The SQL query shown in the message 

was supposed to return 1 row, but instead returned 0 

rows. 



Module: 

DMH5989E 

WsaaJar 

The servlet request is stopped. 


SQL errors occurred. View log file for 


Explanation: One or more SQL errors occurred while 

trying to retrieve data for this page. 


The servlet request is stopped. 

User response: Try running distributed 

postprocessing. If the problem persists, contact IBM 


Module: 

DMH6000E 

WsaaJar 

No Parent Node for: resourcename 


attempting to retrieve node metadata for the specified 

resource when node data is expected. 





Examine the Rational Asset Analyzer 






Module: 

DMH6020E 

WsaaJar 

Logger passed as null to the Developed 

Assets Bridge Manager. 

Explanation: An unexpected error occurred because a 

null or invalid logger was used to initialize the 

specified Bridge Manager. This error could indicate an 


product. 

System action: Pattern detection is skipped for this set 

of assets. Processing continues for the postprocessor 

defined. 


Module: 

DMH6021E 

WsaaJar 


No temporary directory defined in 

system properties 


temporary directory specified in thetempDir parameter 

of the Common.cfg file, but no value has been specified 

for that property. 

System action: The pattern detector cannot continue. 


User response: Ensure that you have specified a valid 

and accessible temporary directory value in Common.cfg. 

Module: 

DMH6022E 

WsaaJar 

No Scanning Root given for the Bridge 

Manager. 


null or invalid scanning root was used to initialize the 

Bridge Manager. This error could indicate an 


product. 

System action: Postprocessing is skipped for this set 


defined. 


Module: 

DMH6023E 

WsaaJar 


No Configuration Object given for the 

Bridge Manager. 


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 


defined. 

User response: Review your runtime declaration 

configuration in admin.cfg and the runtime 

configuration definition. Attempt to scan the assets 

again. 

Module: 

DMH6024E 

WsaaJar 

No Location found in the Scanning Root 

given for the Bridge Manager. 


the scanning root used to initialize the Bridge Manager 

did not have a location defined. This error could 

indicate an inconsistency in the installed Rational Asset 

Analyzer product. 



defined. 


Module: 

DMH6030E 

WsaaJar 


No Class Path given for the Server 

Bridge. 


the configuration object used to initialize the Server 

Bridge did not have a classpath defined. This error 

could indicate an incorrect runtime configuration 

definition. 



defined. 

User response: Correct the runtime configuration file, 

define the classpath for the runtime, and attempt to 

scan the assets again. 

Module: 

DMH6031E 

WsaaJar 

No Location Path given for the Server 

Bridge. 


the Server Bridge was initialized without a location for 

the scanning root. This error could indicate an 


product. 



defined. 


Module: 

WsaaJar 




DMH6050E 

Null default value given for 

non-nullable field: fieldname in table 

tablename 

Explanation: An attempt was made to set a null value 

for a column specified in the indicated table when a 

null value is not allowed. 

System action: The metadata resulting from 

postprocessing for the current asset cannot be 

completed and will be skipped. Processing continues 



logs to determine if the error is related to the asset 

itself. Contact your IBM technical-support 

representative if the problem cannot be resolved. 

Module: 

DMH6051E 

WsaaJar 

Got more than one result in 

getTableValues() 


trying to retrieve metadata for a specific asset in the 

Rational Asset Analyzer database. Multiple results were 

returned when only one result was expected. 

System action: Scanning or analysis for the current 

asset is skipped. Processing continues for the next asset. 


Module: 

DMH6052E 

WsaaJar 


Field fieldname does not exist in table 

tablename. 


the specified column does not exist in the table 

indicated in the Rational Asset Analyzer schema. This 

error could indicate an inconsistency in the installed 

Rational Asset Analyzer product. 









Module: 

DMH6053E 

WsaaJar 

Column name not given to table 

tablename. 

Explanation: An unexpected error occurred during an 

attempt to retrieve metadata from the Rational Asset 

Analyzer database because no column name was 

specified. 


Scanning or analysis for the current 



Module: 

DMH6054E 

WsaaJar 


Connection to the database is not open. 


to communicate with the DB2 database for Rational 

Asset Analyzer because the connection was not opened. 





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 


Module: 

DMH6055E 

WsaaJar 

Transactions already exist in the system. 

Explanation: An error occurred during an attempt to 

start a DB2 transaction because one or more DB2 

transactions are still active. 







assistance. 

Module: 

DMH6056E 

WsaaJar 

Error while executing query 

Explanation: An error occurred during an attempt to 

set or retrieve values from the Rational Asset Analyzer 

database. The specific SQL exception is indicated. 







assistance. 

Module: 

DMH6057E 

WsaaJar 

Field/s fieldname does not exist in table 

tablename 


the specified column does not exist in the table 

indicated in the Rational Asset Analyzer schema. This 

error could indicate an inconsistency in the installed 



Rational Asset Analyzer product. 









Module: 

DMH6058E 

WsaaJar 

An illegal or non-real filter was used 

[filter]. 

Explanation: An exception occurred because the 

specified invalid filter was used to query metadata in 

the Rational Asset Analyzer database. 

System action: Scanning or analysis on the current 


User response: Examine the filter specified and the 

Rational 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. 

Module: 

DMH6059E 

WsaaJar 

Field name [length len] cannot hold data 

"value". 

Explanation: 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. 

System action: The string is truncated and inserted 

into the database. 


Module: 

DMH6060E 

WsaaJar 

None 

Cannot get configuration information 

Explanation: The /assetloc/config/ 

EColabraApplication.cfg configuration file cannot be 

found or opened for read access. 

System action: Scanning or analysis cannot continue 

because the persistency framework cannot be 

initialized. The scanning process ends. 

User response: Ensure that the 

EColabraApplication.cfg file exists with the correct file 

permissions for read access. 

Module: 

WsaaJar 

DMH6061E 

Cannot instantiate persistency helper 

name: phname implementing class: 

classname 

Explanation: The persistency help specified cannot be 

instantiated using the indicated class defined for that 

persistency helper in the /assetloc/config/ 

EColabraApplication.cfg configuration file. 

System action: Scanning or analysis cannot continue 

because the persistency framework cannot be 

initialized. The scanning process ends. 


the persistency helper in the EColabraApplication.cfg 

file. 

Module: 

DMH6070E 

WsaaJar 

Could not store record into the database, 

Hash retry failed [Table = tablename, Try 

range = rangestart..rangeend] 

Explanation: An unexpected error occurred during an 

attempt to store metadata in the Rational Asset 


System action: Analysis for the existing asset is 



Module: 

DMH6090E 

WsaaJar 


Two links were found from the same 

tag library to the same name of tag 

Explanation: 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. 


current asset. Processing continues for the next asset. 


Module: 

DMH6092E 

WsaaJar 


Found a negative asset id in scope 

space, search for jsp scriptlet class 


to create a reference link in the Rational Asset Analyzer 

database because one of the linked assets has an 

invalid identifier. 




Module: 

WsaaJar 




DMH6093E 

No scope space found 

Explanation: An invalid scope space for an asset was 

specified during postprocessing. 




logs to determine whether the asset scoping is invalid 

as specified by the scanning root for the scanning 

process. Contact your IBM technical-support 


Module: 

DMH6110E 

WsaaJar 

Two targets found in searching for the 

right table for a reference 

Explanation: An exception occurred during 

postprocessing because multiple targets used for 

analysis were found in the Rational 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. 

System action: Postprocessing on the current asset is 

stopped. The exception is logged, and postprocessing 


User response: Examine the log for information on the 

asset being analyzed. Consult your IBM 

technical-support representative if the problem cannot 

be corrected locally. 

Module: 

DMH6111E 

WsaaJar 

Error retrieving scope space search 

results for main class classname 

Explanation: The specified class found in the archive 

manifest being analyzed was not found among the set 

of assets already analyzed. Rational Asset Analyzer 

expects that this class has been analyzed within the 

scope of the archive. 


stopped. The error is logged, and processing continues 


User response: 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. 

Module: 

DMH6113E 

WsaaJar 

No scope space found for archive manifest 


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 



User response: Examine the log for details about the 

asset being analyzed and the error itself. Consult your 



Module: 

DMH6120E 

WsaaJar 

Two classes found for same EJB asset 

assetname 


postprocessing for the specified EJB asset because more 

than one class was found to be associated with this 

EJB. 

System action: Postprocessing for the specified asset is 



User response: 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. 

Module: 

DMH6121E 

WsaaJar 

No scope space found for EJB name 

Explanation: An invalid scope space for the specified 

EJB asset was used during postprocessing. 




logs to determine whether the asset scoping is invalid 

as specified by the scanning root for the scanning 

process. Contact your IBM technical-support 


Module: 

DMH6130E 

WsaaJar 

No scope space was found for a given 

asset assetname 


postprocessing for the specified asset because a scope 

for analysis was defined but not found. 




User response: 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. 

Module: 

WsaaJar 



DMH6140E 


asset assetname 


postprocessing for the specified asset because a scope 

for analysis was defined but not found. 




User response: 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. 

Module: 

DMH6141E 

WsaaJar 

The implementing jsp filename jspfile is 

incorrect/missing. 


postprocessing for the specified asset. The JSP specified 

as implementing this asset cannot be found in the set of 

metadata for Rational Asset Analyzer. Either the JSP 

asset has not been analyzed or it has been analyzed 

under a different asset name. 




User response: Ensure that the specified JSP is part of 

the set of assets being analyzed and try the operation 

again. 

Module: 

DMH6150I 

WsaaJar 

postprocessor finished. Total 

time=[elapsed time in seconds] 


signalling that the postprocessor has completed. 



Module: 

DMH6151I 

WsaaJar 


None 

postprocessor 


indicating that the postprocessor is running. 



Module: 

WsaaJar 


None 

DMH6152I 

postprocessor started... 


signalling that the postprocessor has started. 



Module: 

DMH6170I 

WsaaJar 


None 

WebSphere Application Server 4 AE 

Pattern Detector 


indicating that the WebSphere Application Server 4 

pattern detector is running. 



Module: 

DMH6171E 

WsaaJar 


None 

No Servers to Analyze 

Explanation: This message indicates that 

postprocessing will not continue because there are no 

WebSphere Application Servers accessible for analysis. 

System action: Postprocessing stops for this asset 

type. Processing continues for the next type of asset. 

User response: Ensure that the WebSphere Application 

Server you intend to analyze is accessible and can be 

reached by your Rational Asset Analyzer Windows 

server and try the operation again. Make sure that the 

Rational Asset Analyzer scanner is configured to scan 

the proper WebSphere Application Server assets and 

that there were no errors during the analysis phase of 

scanning. 

Module: 

DMH6172I 

WsaaJar 

WebSphere Application Server 5 Pattern 

Detector 


indicating that the WebSphere Application Server 5 

pattern detector is running. 



Module: 

DMH6180I 

WsaaJar 


None 

Developed Assets Pattern Detector 


indicating that the developed assets pattern detector is 

running. 



Module: 

WsaaJar 


None 



DMH6181E 

No Assets to Analyze 

Explanation: Postprocessing for developed assets has 

stopped because no assets were identified for 

processing. 

System action: Postprocessing stops for this set of 

assets. The error is logged, and processing continues for 

the next postprocessor. 

User response: 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. 

Module: 

DMH6182E 

WsaaJar 

No scanning roots bound with 

Developed Runtime Environment set in 

the configuration file. 


stopped because no scanning roots were identified for 

processing. 





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. 

Module: 

DMH6183E 

WsaaJar 

No Patterns given to analyze in the 

configuration file. 


stopped because no patterns were specified for 

detection during postprocessing in the development 

environment bound to the scanning root processed. 





postprocessor did not have any patterns identified. 

Consult your IBM technical-support representative for 

help diagnosing and correcting the problem. 

Module: 

DMH6190I 

WsaaJar 

Assembled Assets Pattern Detector 


indicating that the assembled assets pattern detector is 

running. 




None 

Module: 

DMH6191E 

WsaaJar 

No scanning roots bound with 

Assembled Runtime Environment set in 

the configuration file. 



detection during postprocessing in the assembled 

environment bound to the scanning root processed. 





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 


Module: 

DMH6192E 

WsaaJar 

No Patterns given to analyze in the 




detection in the assembled environment bound to the 

scanning root processed. 





postprocessor did not have any patterns identified. 

Consult your IBM technical-support representative for 

help diagnosing and correcting the problem. 

Module: 

DMH6193E 

WsaaJar 

No Resources found to run Java Pattern 

Detector on under the scanning root 

[root]. 


stopped because no resources could be found under the 

specified scanning root for pattern detection. 





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 


Module: 

WsaaJar 



DMH6200E 

The asset type type is not supported; 

please check the config file. 

Explanation: The specified invalid asset type was 

encountered while validating the scanning roots 

indicated for postprocessing in the Rational Asset 

Analyzer configuration files. 

System action: Postprocessing on the particular asset 

type is stopped. The error is logged, and 

postprocessing continues for the next asset in the 


User response: 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. 

Module: 

DMH6220E 

WsaaJar 

Cannot locate target table, 

Table[tablename]. 

Explanation: During an attempt to add links to 

metadata during postprocessing, the specified DB2 

table could not be found in the Rational Asset Analyzer 

metadata schema. This error could be due to an invalid 

specification in the postprocessor configuration file, an 

inconsistency in the Rational Asset Analyzer database, 

or an error in the user input specification defined by 

the user. 

System action: The updates to the metadata were not 

made. The error is logged, and postprocessing 

continues on the current asset. 

User response: Ensure that you have correctly created 

your Rational 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 Rational Asset Analyzer version 

installed. Attempt the operation again after correcting 

the problem. 

Module: 

DMH6240E 

WsaaJar 

SQL command parameter not supplied 


invocation of the distributed query servlet due to 

invalid URL parameters. In this particular case, the 

SQL= parameter was not specified on the URL. 

System action: The distributed functionality cannot be 

invoked from the browser. The error is displayed. 

User response: 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 Rational Asset 

Analyzer to issue the URLs correctly by selecting a link 

from the user interface. Contact your IBM 


Module: 

DMH6241E 

WsaaJar 

Invalid SQL command: command 




SQL= parameter was specified but did not contain a 

valid value. The invalid value is indicated in the error 

message. 




URL in the browser, you must specify a valid SQL= 

parameter. Try using the browser Back button to return 





Module: 

DMH6242E 

WsaaJar 

analyzername analyzer is not supported 




ANALYZER= parameter was specified but contained 

either a null or invalid value for this parameter. The 

invalid value is indicated in the error message. 




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 Rational Asset Analyzer to issue the URLs 

correctly by selecting a link from the user interface. 


assistance. 

Module: 

DMH6243E 

WsaaJar 

flagtype type is not supported 



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. 




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 

Rational Asset Analyzer to issue the URLs correctly by 

selecting a link from the user interface. Contact your 


Module: 

DMH6245E 

WsaaJar 

name option is not supported 




SQL=DESCRIBE was used but the OPTION= parameter 

specified is invalid. 




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 Rational Asset Analyzer to issue the URLs 

correctly by selecting a link from the user interface. 


assistance. 

Module: 

DMH6250E 

WsaaJar 

Missing parameter: name 


invocation of the distributed query servlet due to a 

missing value for the parameter specified. 




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 Rational Asset Analyzer to issue the 

URLs correctly by selecting a link from the user 

interface. Contact your IBM technical-support 


Module: 

DMH6251E 

WsaaJar 

Attempt to query a forbidden column 

Explanation: 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. 




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 Rational Asset Analyzer 

to issue the URLs correctly by selecting a link from the 

user interface. Contact your IBM technical-support 


Module: 

DMH6252E 

WsaaJar 

Invalid value for JOIN parameter: urlval 


browser by a URL, an invalid JOIN value was 

specified. Valid values are INNER and LEFT. 




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 Rational Asset Analyzer to issue 

the URLs correctly by selecting a link from the user 



Module: 

DMH6253E 

WsaaJar 

Invalid value for 

ELIMINATEDUPLICATES parameter: 

urlval 


browser by a URL, an invalid 

ELIMINATEDUPLICATES value was specified. Valid 

values are TRUE and FALSE. 




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 




Module: 

DMH6254E 

WsaaJar 

An internal error occurred: error 


invocation of the distributed query servlet because an 

attempt was made to access a DB2 table in the Rational 

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 Rational Asset Analyzer 

configuration files for an analyzer or scanner, or to an 

invalid specification on the URL itself. 






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 Rational Asset Analyzer to issue the 

URLs correctly by selecting a link from the user 



Module: 

DMH6255E 

WsaaJar 

No scanner manager defined for 

scanner: name 


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. 




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 Rational Asset Analyzer to 

issue the URLs correctly by selecting a link from the 



Module: 

DMH6256E 

WsaaJar 

Expected file filename was not found 

Explanation: 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 Rational 

Asset Analyzer. 

System action: The browser action to retrieve the file 

contents is stopped and the error is displayed. 

User response: Ensure that the file exists and can be 

accessed from the Windows server where Rational 

Asset Analyzer is installed, and try the operation again. 

Module: 

DMH6261E 

WsaaJar 

Unsupported feature 

Explanation: 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. 


displayed. 

The query cannot be run. The error is 

User response: Use the browser's Back button to 





Module: 

WsaaJar 

DMH6264E Invalid value for resultsnum parameter: 1 


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. 

System action: The browser action is stopped, and the 

error is displayed. 



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 Rational Asset Analyzer 

to issue the URLs correctly by selecting a link from the 



Module: 

DMH6269E 

WsaaJar 

Unable to create error log file; errors 

will not be logged. 

Explanation: During initialization of the distributed 

query servlet, the logs could not be created properly. 

System action: Processing continues as usual, but 

errors cannot be logged. 

User response: 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 


Module: 

DMH6270E 

WsaaJar 

Unable to initialize mgrname 


query servlet, an exception occurred while trying to 

initialize the database, scanner manager, or analyzer 

manager identified in the configuration files. 

System action: Processing stops. The query servlet 

cannot be initialized, thus preventing the Rational Asset 

Analyzer product itself from being loaded when HTTP 

or WebSphere Application Server is started. This is a 

critical error preventing any operation of the product. 



User response: 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 


Module: 

DMH6272E 

WsaaJar 

Unable to read the forbidden query 

columns 


query servlet, an exception occurred while trying to 

read the forbiddenQueryColumns located in the 

/assetloc/config/EColabraApplication.cfg file. 

System action: Processing stops. The query servlet 

cannot be initialized, thus preventing the Rational Asset 

Analyzer product itself from being loaded when HTTP 

or WebSphere Application Server is started. This is a 

critical error preventing any operation of the product. 

User response: 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 


Module: 

DMH6273E 

WsaaJar 

Problems occurred in processorname 

Explanation: An exception occurred during execution 

of a query from the distributed user interface. 

System action: The query execution is stopped, and 

the error is displayed in the browser. 


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. 

Module: 

DMH6274E 

WsaaJar 

featurename is not yet implemented 


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. 


displayed. 

The query cannot be run. The error is 

User response: Use the browser's Back button to 





Module: 

DMH6276E 

WsaaJar 

viewmgrname is not available 


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. 



User response: Use the browser Back button to return 





Module: 

DMH6278E 

WsaaJar 

Table not found for type 

Explanation: 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 

Rational 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. 

System action: The distributed query cannot be 

executed. The error is displayed. 


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 Rational Asset Analyzer 

database. Try the operation again after correcting any 

errors. Consult your IBM technical-support 


Module: 

DMH6295E 

WsaaJar 

WRONG DATE FORMAT 

Explanation: 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. 

System action: The distributed query cannot be run. 

The error is displayed. 



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 Rational Asset 






Module: 

DMH6296E 

WsaaJar 

Column name does not exist in the 

analyzer table or in the scanner table 


while attempting to run a distributed search because 

one or more column names specified for that search are 

not valid for the asset type. 

System action: The search request is stopped. 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. 

Module: 

DMH6297E 

WsaaJar 

: Invalid value argval specified 



one or more search values specified are not valid. 







product and try your search request again. Contact 


assistance. 

Module: 

DMH6298E 

WsaaJar 

There is no analyzer defined 


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 Rational Asset Analyzer metadata schema. 




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 Rational Asset Analyzer 

database. Try the operation again after correcting any 

errors. Consult your IBM technical-support 


Module: 

WsaaJar 

DMH6299E 

Attribute value AND|OR|NOT 

character is wrong 


executing a distributed search because the boolean 

operators specified are invalid. 


displayed. 

The search is stopped. The error is 

User response: Consult your IBM technical-support 


Module: 

DMH6300E 

WsaaJar 

Column name does not exist in the 

analyzer table 



one or more column names specified for that search are 

not valid for the asset type. 







product and try your search request again. 

Module: 

DMH6301E 

WsaaJar 

Type db2type not presentable 

Explanation: 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. 


Search results are returned, but values that cannot be 

presented properly have this message displayed. 


Module: 

DMH6303E 

WsaaJar 

None 

PathName ccpath not legal for ClearCase 


view source from a ClearCase repository, because the 

path name specified for access is not a valid ClearCase 

path name. 

System action: The source cannot be retrieved, so 

processing stops. The error is displayed. 

User response: 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 Rational Asset 

Analyzer. Also verify that source exists at that path. Try 



the operation again after fixing any problems. 

Module: 

WsaaJar 


Module: 

WsaaJar 

DMH6322E 

Cannot read file filename 


view the source specified. The source could not be 

found using that path name. 

System action: The source cannot be retrieved, so 

processing stops. The error is displayed. 

User response: 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. 

Module: 

WsaaJar 

DMH6324W The postprocessor has not completed. 

Results may not be accurate. 

Explanation: 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. 

System action: The system is functioning normally, 

but all results are not yet committed, because scanning 

and analysis are not complete. 

User response: Wait for postprocessing to finish for 

the assets you are exploring in the browser before 

continuing the exploration. 

Module: 

WsaaJar 

DMH6341E 

Cannot initialize System tables 


attempting to initialize the product tables used during 

Rational Asset Analyzer processing. These tables are 

used during the scanning, analysis, postprocessing, and 

exploration activities. 

System action: 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 Rational Asset 

Analyzer can function normally. The errors are logged. 

User response: 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. 

Module: 

DMH6350E 

WsaaJar 

Just one parameter for refs is supported 

Explanation: During postprocessing, an invalid 

attempt was made to add reference links because 

multiple parameters were specified when only one was 

expected. 


stopped. Processing continues for the next asset. 



Module: 

WsaaJar 

DMH6325E 

The query is too complex. Please select 

fewer properties to scope your search. 

Explanation: An exception occurred during a search 

for assets from the browser because too many columns 

were selected as search criteria. 

System action: The search cannot be performed. The 


User response: Select fewer columns for the search 

criteria and attempt the search again. 

Module: 

DMH6326E 

WsaaJar 

An SQL error occurred: sqlerr 

Explanation: An exception occurred during a search 

for assets from the browser because of an SQL error. 

The exact error is shown. 

System action: The search cannot be performed. The 


User response: Examine the SQL error and attempt to 

fix any problems. Try the search again or contact your 

DMH6351E 

Just string parameter is supported for 

refs 

Explanation: 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. 





Module: 

DMH6352E 

WsaaJar 

Duplicate contained entities, parents, for 

entity in table tblname index idxname 


postprocessing while attempting to find the container 

for the asset being processed. Multiple containers were 

found when only one is expected. 







Module: 

DMH6353E 

WsaaJar 

Table does not exist tblname 


postprocessing because the specified table could not be 

found in the Rational Asset Analyzer metadata schema 






Module: 

DMH6370E 

WsaaJar 

Table does not exist tblname 


postprocessing because the specified table could not be 

found in the Rational Asset Analyzer metadata schema 


System action: Table initialization fails and 

postprocessing for the current asset is stopped. The 


asset. 



Module: 

DMH6380E 

WsaaJar 

An error has occurred determining the 

new URL space id 

Explanation: 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. 

System action: Initialization fails and analysis and 

postprocessing stops for the current asset. The error is 


User response: 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 


Module: 

DMH6381E 

WsaaJar 

Bad containment type 

Explanation: During postprocessing for an EAR or 

WAR file asset, an invalid containment for the URL was 

encountered. 

System action: Storing of the asset fails. Analysis 



Module: 

DMH7014I 

WsaaJar 


No Layer Manager is running 


indicating that there is no Java Processor Layer 

Manager running, but a request to stop it has been 

issued. 



Module: 

DMH7015E 

WsaaJar 

The system is functioning properly. 

None 

Failed to validate bridge 

Explanation: During initialization of the Java 

processor, a failure occurred while validating the data 

for initialization. 

System action: Processing stops for the current pattern 

detector. Processing continues with the next pattern 

detector. 

User response: Validate that the pattern detector 

configuration files and the runtime environment are 

correct. Try to reactivate Rational Asset Analyzer. 



Module: 

DMH7016E 

WsaaJar 

Problem running layer: layermgr 

Explanation: An exception occurred while running the 

specified pattern detector during postprocessing. 


detector instance. Processing continues with the next 

pattern detector instance. 


Module: 

DMH7020I 

WsaaJar 


PatternDetector - Start Engine name 

Explanation: This is an informational message logged 

when the specified pattern detector engine is started. 



Module: 

DMH7021I 

WsaaJar 


None 

PatternDetector - End Engine name 


when the specified pattern detector engine is finished. 




None 



Module: 

DMH7022I 

WsaaJar 

PatternDetector - Start Server: 

serverName - Server i/total 


when the pattern detector server is started. 



Module: 

DMH7023I 

WsaaJar 


None 

PatternDetector - End Server 


when the pattern detector server is finished. 



Module: 

DMH7024I 

WsaaJar 


None 

PatternDetector - Start Scope i/total 


when entering the scope of a pattern detection 

operation. 



Module: 

DMH7025I 

WsaaJar 


None 

PatternDetector - End Scope 


when entering the scope of a pattern detection 

operation. 



Module: 

DMH7060I 

WsaaJar 


None 

\n\n------------------------ a pattern was 

found !!! ------------------------\n 


to the log indicating that a pattern was found during 

pattern detection processing. More information on the 

results follows this message in the log. 



Module: 

WsaaJar 


None 

DMH7061I 

Containing class jar/dir:name 


to the log indicating that the specified JAR file or 

directory was found to contain a pattern instance 

undergoing pattern detection processing. 



Module: 

DMH7062I 

WsaaJar 


None 

Containing class location: name 


to the log indicating that the specified class was found 

to contain a pattern instance undergoing pattern 

detection processing. 



Module: 

DMH7080E 

WsaaJar 


None 

No Servers defined 


to retrieve the servers for processing using the pattern 

detector. There were no servers to retrieve. 





configured the system to perform pattern detection by 

specifying servers for processing. Try the operation 

again or contact your IBM technical-support 


Module: 

DMH7081I 

WsaaJar 

Stopping the analysis 

Explanation: During postprocessing analysis, a signal 

was received to stop processing. 


Processing is stopped and the message is logged. 


Module: 

DMH7082E 

WsaaJar 

None 

Problem analyzing server: name 

Explanation: An error was encountered during pattern 

detector analysis. 

System action: The current server analysis using the 

pattern detector is stopped and the error is logged. 

Processing continues with the next server. 

User response: Examine the error logs to determine if 

the issue can be resolved locally and try the operation 



again. Contact your IBM technical-support 


Module: 

DMH7083E 

WsaaJar 

Problem analyzing server 




pattern detector is stopped, and the error is logged. 

Processing continues with the next server. 





Module: 

DMH7120E 

WsaaJar 

No Parent allowed here 

Explanation: An unexpected error occurred when an 

attempt was made to set parent information where it is 

not allowed. 

System action: Processing for the current scope using 

the pattern detector is stopped. Processing continues 

with the next scope. 


Module: 

DMH7140E 

WsaaMain 


Not legal as Source name 


method was called during pattern detection 

postprocessing but this method is not supported for the 

class specified. 






Module: 

DMH7150E 

WsaaJar 

Consult your IBM technical-support 

Not legal as Source name 


method was called during pattern detection 

postprocessing, but this method is not supported for 

the class specified. 






Module: 

WsaaJar 


DMH7181E 

Class not found in repository name 


an attempt was made to find a class in Rational Asset 

Analyzer during pattern detection postprocessing, but 

the class name is invalid or the class does not exist. 






Module: 

DMH7200E 

WsaaMain 


Cannot report pattern 

Explanation: An error occurred during pattern 

detection postprocessing while attempting to report a 

pattern found. 






Module: 

DMH7201E 

WsaaJar 


Problem while trying to find source 


detection postprocessing while attempting to find the 

source component for a found pattern. 

System action: The pattern detector is stopped for the 





Module: 

DMH7202E 

WsaaJar 


Problem while trying to find target 


detection postprocessing while attempting to find the 

target component for a found pattern. 

System action: The pattern detector is stopped for the 





Module: 

WsaaJar 




DMH7204E 

Problem with link 


detection postprocessing while attempting to store a 

found link in the Rational Asset Analyzer database. 




User response: Verify database access. Consult your 


assistance. 

Module: 

DMH7220E 

WsaaJar 

Cannot load components configuration 

file 


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. 

System action: The postprocessor for pattern detection 

cannot be initialized. Processing is stopped, and the 

error is logged. Processing continues for the next 


User response: Ensure that the pattern detection 

configuration files located in /assetloc/config/ 

patterns exist and are accessible to Rational Asset 

Analyzer. Consult your IBM technical-support 


Module: 

DMH7222E 

WsaaMain 

No pattern for name: name 


detection postprocessing because the specified pattern 

has not been defined. 

System action: Postprocessing is stopped, and the 

error is logged. Processing continues for the next asset. 



Module: 

DMH7223E 

WsaaMain 


Cannot instantiate verifier with class 

name 


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 





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 Rational Asset Analyzer. Consult your IBM 


Module: 

DMH7224E 

WsaaMain 

This pattern is already defined name 


detection postprocessing because the specified pattern 

has already been defined in another pattern 





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 Rational Asset 

Analyzer. Consult your IBM technical-support 


Module: 

DMH7260E 

WsaaMain 

Cannot create War ClassLoaderInfo: 

warfile 

Explanation: An error occurred during postprocessing 

for pattern detection because the specified WAR file 

details cannot be accessed by Rational Asset Analyzer 

or the data in the database is in an inconsistent state. 





Module: 

DMH7261E 

WsaaJar 

Cannot get ear location for ear: 

earlocation filetype: filelocation 


for pattern detection because the location of the EAR is 

not correct. The scope for pattern detection cannot be 

established for the current asset. 





Module: 

WsaaJar 



DMH7262E 

Cannot create EJB JAR ClassLoaderInfo: 

ejbjarname 


for pattern detection because the specified EJB JAR file 

details cannot be accessed by Rational Asset Analyzer 

or the data in the database is in an inconsistent state. 





Module: 

DMH7280E 

WsaaJar 

No servers defined 


to retrieve the servers for processing using the pattern 

detector. There were no servers to retrieve. 





configured the system to perform pattern detection by 

specifying servers for processing. Try the operation 

again or contact your IBM technical-support 


Module: 

DMH7281I 

WsaaJar 

Stopping the analysis 

Explanation: During postprocessing analysis, a signal 

was received to stop processing. 


Processing is stopped and the message is logged. 


Module: 

DMH7282E 

WsaaJar 

None 

Problem analyzing server: name 




pattern detector, and the error is logged. Processing 

continues with the next server. 





Module: 

WsaaJar 

DMH7290E 

Problem parsing XML 

Explanation: An error has occurred while parsing the 

pattern detection XML during postprocessing. The 

reason for the error is specified. 



User response: 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 Rational Asset Analyzer and try the 

operation again. Consult your IBM technical-support 


Module: 

DMH7291E 

WsaaJar 

Unable to load file 

Explanation: An error has occurred while attempting 

to access a pattern detection XML configuration file 

specified during postprocessing. 



User response: 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 Rational 

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 


Module: 

DMH7310I 

WsaaJar 

PatternDetector - Start prepare structure 


to the log indicating that the pattern detector has 

started preparing the structure. 



Module: 

DMH7311I 

WsaaJar 


None 

PatternDetector - End Prepare structure 



finished preparing the structure. 



Module: 

WsaaJar 


None 



DMH7312I 

PatternDetector - End searching patterns 



finished searching patterns. 



Module: 

DMH7313I 

WsaaJar 


None 

PatternDetector - Start searching 

patterns 



started searching patterns. 



Module: 

DMH7330E 

WsaaJar 


None 

Cannot get config from configuration 

file 


attempting to read configuration information during 

analysis of Java assets. 

System action: Postprocessing for the set of Java 

assets is stopped. Processing continues with the next 



Module: 

DMH7331E 

WsaaJar 


There is a problem with analyzing 

scopes: name 

Explanation: 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. 

System action: Pattern detection for the current scope 

is stopped. Processing continues with the next pattern 

detector scope. 

User response: Examine the logs to determine 

whether the error can be resolved and try the operation 

again. Consult your IBM technical-support 


Module: 

DMH7332E 

WsaaJar 

Missing Classes in Scope: classlist 

Explanation: 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. 

User response: Ensure that the set of classes identified 

exists and can be accessed for the scope defined to 

Rational 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 


Module: 

DMH7340E 

WsaaJar 

No such Export: name 

Explanation: 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 Rational Asset Analyzer. 

System action: Pattern detection for the scope is 

stopped. Processing continues with the next scope. 


Module: 

DMH7341E 

WsaaJar 


Not a legal BlackBox Name: name 

Explanation: An unexpected internal error occurred 

during Java analysis pattern detection. 

System action: Pattern detection for the set of Java 


scope. 


Module: 

DMH7351E 

WsaaJar 


No extractable resources found in config 

file 


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. 





Module: 

DMH7352E 

WsaaJar 


No value for type: name 



because the configuration does not contain a value for 



the property specified. The cause of the exception is 

detailed in the message. 

System action: Pattern detection for the set of Java 


scope. 


Module: 

DMH7353E 

WsaaJar 


Cannot create configuration: cfgerror 



because the configuration could not be created. The 

cause of the error is included in the message. 





Module: 

DMH7380E 

WsaaJar 


Method not found name 

Explanation: During Java pattern detection processing, 

the specified method was not found when expected 

within the call graph. 

System action: The error is logged and postprocessing 

continues for the current asset. The resulting 

information may not be complete. 

User response: 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 


assistance. 

Module: 

DMH7381E 

WsaaMain 

Not a method type 


a method was found, but it was not a valid method 

type as expected. 




User response: 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 


assistance. 

Module: 

WsaaMain 

DMH7382E 

No appropriate Type nodetype 


a node specified was found with an invalid type. 





Module: 

DMH7410E 

WsaaMain 


Problems with the XML pattern 

definition. 

Explanation: 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. 

System action: Processing continues, but no results 

will be produced for the current pattern because it 

cannot be constructed. 


Module: 

DMH7411E 

WsaaJar 


In this version, there should be only 

one instructions sequence per pattern. 

Explanation: 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. 





Module: 

DMH7412E 

WsaaJar 


The following type is illegal for 

operand-resolution element: name 

Explanation: 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. 





Module: 

WsaaJar 




DMH7425I 

Was Not Resolved 

Explanation: This message records the fact that a 

pattern was not resolved during pattern detection 

processing. 



Module: 

DMH7440E 

WsaaJar 


None 

The new ClassLoader is already in a 

chain of existing ClassLoader; new CL: 

newclassloader existingCL: 

existingclassloader 

Explanation: 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. 


current pattern detector operation, and the error is 

logged. Processing continues with the next 



Module: 

DMH7441E 

WsaaMain 


One of the existing ClassLoaders is in 

the chain of the new ClassLoader; new 

CL: newclassloader existingCL: 

existingclassloader 

Explanation: During construction of the scopes for 

pattern detection, an existing class loader was detected 

within the chain of new class loaders. 


current pattern detector operation, and the error is 

logged. Processing continues with the next 



Module: 

DMH7490E 

Explanation: 

created. 

WsaaMain 


Failed to create log file filename 

The specified log file could not be 

System action: Processing continues without the 

logging function. 

User response: 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 Rational Asset 

Analyzer. Contact your IBM technical-support 


Module: 

DMH7500E 

WsaaJar 

Failed to create log writer 

Explanation: An attempt was made to obtain write 

access to Rational Asset Analyzer log files but an error 

occurred. 

System action: Processing continues without the 

logging function. 

User response: 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 Rational Asset Analyzer. 



Module: 

DMH7520E 

WsaaJar 

Cannot locate asset; number of columns 

is zero 


to search for an asset. The number of columns specified 

in the search is zero. 

System action: Processing for the current asset is 

stopped, and the errors are logged. Processing 


User response: 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. 

Module: 

DMH7521E 

WsaaDbUtil 

Invalid table name, Table[tablename] 


to search on Rational Asset Analyzer metadata, because 

the specified table name is invalid or cannot be found 

in the Rational Asset Analyzer database schema. 





on the error. Ensure that you have correctly installed 


Configuration and Migration Guide. If the table does exist 

in the schema, you may have inaccurate information in 

one or more of the Rational Asset Analyzer 

configuration files. Contact your IBM technical-support 


Module: 

WsaaDbUtil 



DMH7522E 

Invalid column name, Table[tablename] 

Column[colname] 


to search on Rational Asset Analyzer metadata because 

the specified column in the table indicated is invalid or 

cannot be found in the Rational Asset Analyzer 

database schema. 








in the schema with the column specified, you may have 

inaccurate information in one or more of the Rational 

Asset Analyzer configuration files. Contact your IBM 


Module: 

DMH7523E 

WsaaDbUtil 

Invalid column type, Table[tablename] 

Column[colname] Type[coltype] 


to search on Rational 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 Rational Asset Analyzer. 








in the schema with the column specified, and the type 

of column is valid, contact your IBM technical-support 


Module: 

DMH7524E 

WsaaDbUtil 

Ambiguous asset, Table[tablename]: 

assetname 


attempting to search for the asset specified in the table 

indicated. Rational Asset Analyzer expects a single 

result, but multiple results were returned. This error 

could indicate an inconsistency in the metadata. 





on the error. Contact your IBM technical-support 


Module: 

WsaaDbUtil 

DMH7525E 

Cannot locate asset: table tablename asset 

assetname 


attempting to search for the asset specified in the table 

indicated. Rational 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. 





on the error. Contact your IBM technical-support 


Module: 

DMH7540E 

WsaaDbUtil 

Unable to instantiate the class classname. 

Explanation: During initialization of the analyzers for 

processing, Rational Asset Analyzer was unable to 

instantiate the specified class associated with an 

analyzer as identified in /assetloc/config/ 

Analyzers.cfg. 

System action: Analysis processing associated with 

the invalid class will not be performed. Processing 

continues normally. 


specified the implementingClass value for analyzers in 

/assetloc/config/Analyzers.cfg and try the operation 

again. 

Module: 

DMH7560E 

WsaaJar 

XPath name must correspond to XML 

Elements 

Explanation: An error occurred during analysis 

because an invalid XML node was encountered in the 

specified path. 

System action: Analysis for the current asset is 

stopped. Processing continues with the next asset. 

User response: 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 


assistance. 

Module: 

DMH7561E 

WsaaJar 

Error while processing xpath: name 


because of an exception while processing the XML file 

specified. The cause of the error is contained in the 

message. 






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 


assistance. 

Module: 

DMH7571E 

WsaaJar 

Error while parsing 


because of an exception while parsing an XML file. The 

cause of the error is contained in the message. 




processed may be invalid. Contact your IBM 


Module: 

DMH7600E 

WsaaJar 

Message key is null 

Explanation: While attempting to construct a message 

for logging or display on the browser, a null message 

identifier was passed to the message framework. 

System action: The message cannot be displayed 

properly, but information is logged. 


Module: 

DMH7601E 

WsaaJar 


Cannot find message associated with 

key: message 

Explanation: While attempting to construct a message 

for logging or display on the browser, an invalid 

message identifier specified was passed to the message 

framework. 

System action: The message cannot be displayed 

properly but information is logged. 


Module: 

DMH7611E 

Explanation: 

WsaaJar 


Expected scope space id was not found 

Scope Space id id was not found. 

System action: The links computation for this scope 

space will be ignored. 


Module: 

WsaaJar 


DMH7612E 


asset asset type 

Explanation: No scope space was found for a given 

asset asset type even though there should be one. 

System action: The links computation for this scope 

space will be ignored. 


Module: 

DMH7613E 

WsaaJar 


Wrong type of an element element string 

in array concatenation 

Explanation: An element of an object array was not 

the same as all the other element in the array. 

System action: Processing stops. The object arrays 

cannot be concatenated. 


Module: 

DMH7614E 

WsaaJar 


Error while trying to search class class 

name for patterns, skipping it. 

Explanation: 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. 

System action: The class will not be considered in the 

pattern detector calculation. 


Module: 

DMH7615E 

WsaaJar 


Unable to load fileName in module 

module at path relative url. 

Explanation: Unable to load required file fileName for 


System action: This is a severe error and the Pattern 

Detector needs to stop. 

User response: Verify your installation. Contact IBM 


Module: 

DMH7616E 

WsaaJar 

Illegal WebSphere Application Server 

version: was version, must be 4 or 5 

Explanation: Only WebSphere Application Server 

version 4 and 5 are supported at this time. 

System action: The Pattern detector for this server 

will be skipped. 

User response: Change the configuration to only scan 

WebSphere Application Server version 4 or version 5 

servers. 

Module: 

WsaaJar 



DMH7617E 

Cannot create ClassLoader for Ear: ear 

location, skipping it. 

Explanation: Cannot create ClassLoader for Ear: ear 

location, skipping it. 


detector 


Module: 

DMH7618E 

WsaaJar 

This Ear will be skipped for pattern 


File retrieval error, retriever not 

supported for Scanner type scanner type. 

Explanation: File retrieval error, retriever not 

supported for Scanner type scanner type. 



Module: 

DMH7619E 

WsaaJar 

The asset will not be retrieved. 


Link type type does not exist between 

assets source asset and target asset 

Explanation: 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 

Rational Asset Analyzer installation 

System action: This link will not be added to the 

metadata repository. 

User response: Verify your installation. Contact IBM 


Module: 

DMH7620E 

WsaaJar 

Error while trying to run Pattern 

Detector on Cell [cell], skipping it. 

Explanation: Error while trying to run Pattern 

Detector on Cell [cell], skipping it for pattern detection. 

System action: This cell will be skipped for pattern 

detection and the next cell will start. 


Module: 

WsaaJar 


DMH7621W Cell [cell] has no servers, skipping it. 

Explanation: A cell requires a server to be analyzed. 

The cell [cell] has no server and is skipped. 

System action: The WebSphere Application Server cell 

will not be processed. 


Module: 

WsaaJar 

None 

DMH7622E 

Multiple archive manifests found for 

RAR file rar id 

Explanation: RAR files require only one manifest file; 

the application found more. 



Module: 

DMH7623I 

Explanation: 

WsaaJar 

The RAR will be skipped. 


Start postprocessor on non incremental 

postprocessors 

Informational message for status. 

System action: Runs all the postprocessors that belong 

to this runtime and that are not incremental. 


Module: 

DMH7624E 

WsaaJar 

None 

postprocessor name does not support 

incremental postprocessing 

Explanation: The postprocessor does not support 

incremental postprocessing but is defined to be 

incremental in the configuration file. 


The postprocessor will be skipped. 

User response: Change the incremental attribute for 

this postprocessor in eColabraApplication.cfg. 

Module: 

DMH7625E 

Explanation: 

WsaaJar 

Illegal state for scanning root changed 

flag: The scanning root state is old flag 

and the runtime is runtime 

The change flag is unknown. 

System action: The state will be set to changed to 

force the postprocessor to run next time a scan is 

performed. 


Module: 

DMH7626I 

Explanation: 

WsaaJar 



Module: 


Start postprocessing on scanning root 

scanning root name 

WsaaJar 

System is functioning normally. 

Postprocessing has started. 

None 



DMH7627E 

Cannot get scanning roots to run 

postprocessors on them 

Explanation: The query to get all the scanning roots in 

order to perform postprocessing on them has an 

Exception 


The postprocessing will abort 

User response: Verify that you have Database 

connection. Contact IBM Software Support. 

Module: 

DMH7628E 

WsaaJar 

Collection value received for a non-string 

field: information field in table table name 

Explanation: Since the collection's type isn't a string of 

some sort, the mapping to the database is illegal. 


database 


Module: 

DMH7629E 

WsaaJar 

The asset will not be stored in the 


Can't get Web modules (WAR) for server 

[server resource] 

Explanation: Can't get Web modules (WAR) for server 

[server resource]. 


will stop. 



Module: 

DMH7630E 

WsaaJar 

The Pattern Detector for this server 

Verify the runtime configuration in the 

Can't get EJB JAR modules for server 

[server resource] 

Explanation: Can't get EJB JAR modules for server 

[server resource]. 


will stop. 



Module: 

DMH7631E 

WsaaJar 

The Pattern Detector for this server 

Verify the runtime configuration in the 

Initializing server bridge [server resource] 

failed, skipping it. 

Explanation: Initializing server bridge [server resource] 

failed, skipping it. 


Detection. 

The server will be skipped for Pattern 

User response: Verify that the configuration files for 

the scanning root and runtime is correct and try to run 

the scan again. 

Module: 

DMH7632E 

WsaaJar 

Couldn't create Classloader and Scope 

for EJB Jar [file location], skipping it. 

Explanation: Couldn't create Classloader and Scope 

for EJB Jar [file location], skipping it. 

System action: This EJB JAR will be skipped for 

pattern detection. 

User response: Verify that the configuration files for 

the scanning root and runtime is correct and try to run 

the scan again. 

Module: 

DMH7633E 

Explanation: 

EAR. 

WsaaJar 


detection. 


Module: 

DMH7634E 

Explanation: 

current EAR. 

No Deployed Ear found for ear location 

WsaaJar 

No deployed ears found for the current 

This Ear will be skipped for pattern 


More than one Deployed Ear found for 

ear location, using first instance. 

Multiple deployed ears found for the 

System action: Continue processing with the first 

deployed EAR. 


Module: 

DMH7635E 

WsaaJar 


The extracted resource "asset id" that was 

passed is not a file 

Explanation: The extracted resource is a collection. It 

is most likely a directory. 



Module: 

DMH7636E 

WsaaJar 

The resource will be skipped. 


The extracted resource "asset id" that was 

passed is not a directory 

Explanation: The extracted resource is not a collection. 

It is most likely a file. 



Module: 

WsaaJar 

Resource will be skipped. 




DMH7637E 

Cannot create a resource from the 

scanning root "scanning root", file "file", 

and WebSphere Application Server 


Explanation: Cannot create a resource in order to 

analyze it. This is usually as a result of illegal values in 

the scan root definition of WebSphere Application 

Server scanners. 

System action: The scanning root is ignored and 

processing is done for the next scanning root. 

User response: Verify the WebSphere Application 

Server scanning root definition. 

Module: 

DMH7639E 

WsaaJar 

Wrong resource type 'bad resource type' 

was passed to method that expected 

'expected resource type'. 

Explanation: A resource type was different than what 

was expected. 



Module: 

DMH7640E 

Explanation: 

a directory. 

WsaaJar 



Module: 

DMH7641E 

Explanation: 

likely a file. 



The resource "location" that was passed 

is not a file 

WsaaJar 



Module: 

DMH7642E 

The resource is not a file. It is most likely 



The resource "location" that was passed 

is not a directory 

WsaaJar 

The resource is not a directory. It is most 



The resource passed is a non-file-system 


Explanation: The resource passed is a non-file-system 

resource, It is probably belongs to another scanner. 



Module: 

WsaaJar 



DMH7643E 

The resource passed is not a ClearCase 


Explanation: The resource passed is a non-ClearCase 

resource, It is probably belongs to another scanner. 



Module: 

DMH7644E 

WsaaJar 



Bad ClearCase scanning root defined, 

root 

Explanation: The ClearCase scanning root definition is 

not correct or the ClearCase client is not installed 

correctly. 



again. 

Module: 

DMH7645E 

Explanation: 

is missing. 

WsaaJar 



Module: 

DMH7646E 

The scanning root will be skipped. 

Correct the configuration and scan 

No implementing class for scanner 

scanner name 

WsaaJar 

The implementation class for the scanner 

The scanner will be skipped. 


The java code parsing for a JSP file 

failed on file resource id 

Explanation: There is a parsing error when trying to 

parse the Java part of the JSP file. 

System action: The Java information from the JSP will 

not be collected. 

User response: Verify if this JSP is well formed. If so, 

contact IBM Software Support. 

Module: 

DMH7647E 

Explanation: 

WsaaJar 


Error writing to filter mapping table 

filter name 

Unable to add filter to SRVLMAP table. 

The resource is skipped. 

User response: Verify that configuration is correct and 

database connection is working correctly. 

Module: 

WsaaJar 



DMH7648E 

An error occurred when extracting 

parameter from the message driven bean 

description class for bean bean name 

Explanation: Transaction type, message selector, 

acknowledge mode, subscription durability, 

subscription durability, or destination type is unknown. 



Module: 

DMH7649E 

WsaaJar 


Verify sources are valid. 

An invalid resource descriptor was 

passed for an EJB resource 

Explanation: EjbAnalyzer expected for an 

EjbDescriptor but got another descriptor. 



Module: 

DMH7650E 

WsaaJar 



Attribute value column attribute column 

name not found in table table name for 

rule rule name 

Explanation: The column was not found for a rule of 

HTML/JSP analyzer and thus the rule is not legal. 



Module: 

DMH7651E 

WsaaJar 

The rule is skipped for all resources. 


Constant value column constant column 

name not found in table table name for 

rule rule name 

Explanation: The column was not found for a rule of 

HTML/JSP analyzer and thus the rule is not legal. 



Module: 

DMH7652E 

WsaaJar 



Functor semantic functor name defined but 

no content field specified for rule rule 

name 

Explanation: An illegal implementation for rule in 

HTML/JSP analyzer. 



Module: 

WsaaJar 



DMH7653E 

Could not find the functor class semantic 

functor name specified for rule rule name 

Explanation: An illegal implementation for of one of 

the parts in HTML/JSP analyzer rules. 



Module: 

DMH7654E 

WsaaJar 



Could not find the location external table 

name specified for rule rule name 

Explanation: A declared external table was not found 

and thus the data cannot be set in it. 

System action: All resources of the external table's 

asset will be skipped. 


Module: 

DMH7655E 

WsaaJar 


Content column content column name not 

found in table table name for rule rule 

name 

Explanation: An illegal implementation for rule in 

HTML/JSP analyzer. 



Module: 

DMH7656E 

WsaaJar 



Failed to parse tag bad tag name 

Explanation: A parsing error occurred in one of the 

HTML/JSP tags. 



Module: 

DMH7657E 

WsaaJar 

The tag will be skipped. 

Verify that the tag is well formed. 

Cannot add to table table name under 

column key, the value is a non-list 

Explanation: Illegal type of attribute tries to put in a 

column in external asset table 



Module: 

DMH7658E 

Explanation: 

WsaaJar 


The asset is skipped. 


Called getId method for instance 

without id resource name 

The method was called in illegal state. 





Module: 

WsaaJar 


DMH7659W postprocessor postprocessor name was not 

run due to dependency problem 

Explanation: One of the dependent analyzers and/or 

dependent postprocessors does not exist. 



User response: Verify dependencies in 

eColabraApplication.cfg. Contact your IBM 


Module: 

WsaaJar 

DMH7660W Postprocessor name was not run due to 

dependent postprocessor dependent name 

Explanation: The dependent postprocessor did not 

succeed because a dependent analyzer or postprocessor 

did not exist or failed. 



Module: 

WsaaJar 

This postprocessor will not be run. 


DMH7661W Dependent postprocessor dependent 

postprocessor does not exists or not active 

therefore postprocessor postprocessor name 

will not be activated 

Explanation: A dependent postprocessor does not 

exists or not activated as a result another postprocessor 

will not run. 



User response: Verify the dependency in 



Module: 

WsaaJar 

DMH7662W Postprocessor postprocessor name was not 

run due to missing dependent analyzer: 

analyzer name 

Explanation: A dependent Analyzer does not exists as 

a result the postprocessor will not run. 



User response: Verify the dependency in 



Module: 

WsaaJar 

DMH7663I 

Postprocessor postprocessor name is not 

active 

Explanation: The active property in the postprocessor 

section of the configuration is not set to "true". 



User response: 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. 

Module: 

DMH7664E 

WsaaJar 

Postprocessor number for postprocessor 

name does not exist. 

Explanation: The section number for this 

postprocessor does not exist in the configuration. 



User response: Add the required section to the 

postprocessor configuration. 

Module: 

DMH7665E 

WsaaJar 

Postprocessor running place is not 

scanner and not runtime 

Explanation: Each postprocessor should run either in 

the 'scanner' or the 'servlet' but this postprocessor is not 

defined as either of them in eColabraApplication.cfg 



User response: Correct configuration to only have 

valid postprocessor section. 

Module: 

DMH7666E 

WsaaJar 

Unexpected initialization exception 

occurred in servlet 'servletName'. 

Message='exceptionMessage' 

Explanation: Servlet initialization failed because of an 

unexpected exception. 



Module: 

DMH7667I 

Explanation: 

actions. 

WsaaJar 



Module: 

Initialization aborted 


Available actions: 'availableActions' 

WsaaJar 

Request for information on available 


None 



DMH7668I 

Explanation: 



Module: 

DMH7669I 

Explanation: 

the user. 

Added 'numRows' rows to analysis 

queue. 

WsaaJar 



Module: 

DMH7770I 

Rows were added to the analysis queue. 


None 

Count caching has been manually 

stopped. 

WsaaJar 

Count caching was manually stopped by 


None 

Count caching has been manually 

started. Cachingenabled='isCachingEnabled' 

Explanation: Count caching was manually started by 

the user. Caching enabled flag is specified in 

Common.cfg 



Module: 

WsaaJar 


None 

DMH7771W Could not save new log level to 

Common.cfg. New setting will be lost 

when web app is restarted. 

Explanation: User changed log level through UI, but 

new log level could not be persisted to Common.cfg for 

some reason. 


The system is funtioning normally. 

User response: Manually update Common.cfg to 

persist change when servlet restarts. 

Module: 

DMH7772I 

Explanation: 

WsaaJar 



Module: 

Log level changed to 'levelNum'. 

WsaaJar 

User changed log level through UI. 


None 

DMH7773W 'fieldName' is a required field. 

Explanation: The specified field name is required to 

have a value, but was left empty. 




Module: 

DMH7774E 

WsaaJar 

Fill the field. 

Configuration manager intitialization 

exception occurred: Message='message' 


initialize the configuration manager. 



Module: 

DMH7775E 

WsaaJar 

Common initialization stopped. 


Database version could not be 

determined. 

Explanation: The schema level on the database could 

not be determined. An incorrect 'Database.schema' 

name in Common.cfg is the likely cause. 



User response: Verify that the Database section 

properties in Common.cfg are correct. 

Module: 

DMH7776E 

WsaaJar 

Version of Rational Asset Analyzer 

'expectedVersion' does not match detected 

database version 'detectedVersion'. 

Explanation: The database schema level does not 

match the required level for this version of the product. 


stops. 

The common initialization process 

User response: Migrate the database to the current 

Rational Asset analyzer schema level. After migration is 

complete, stop and restart the web application to 

refresh the settings. 

Module: 

DMH7777E 

WsaaJar 

Configuration setting 

'Common.isDistEnabled' indicates that 

distributed support is enabled, but 

database does not contain distributed 

tables. 

Explanation: Configuration settings do not match 

what is being observed. 



User response: Either update configuration setting, or 

add necessary tables to the database. 

Module: 

WsaaJar 



DMH7778E 

Configuration setting 

'Common.Database.os' with value 

'expectedOs' does not match what was 

detected on the database 'detectedOs'. 

Explanation: The OS setting specified in Common.cfg 

does match what was actually detected. 



Module: 

WsaaJar 


Update configuration setting. 

DMH7779W At least one column must be specified 

as a default column. 

Explanation: At least one column must be specified as 

a default column on the custom query. Otherwise, the 

page will be blank. 



Module: 

DMH7880E 

WsaaJar 


Specify at least one default column. 

Out-of-range[range] error occurred trying 

to insert row into table 'tableName' 

Explanation: The specified range of numbers has been 

used up in the specified table. 



Module: 

DMH7882E 

WsaaJar 

Action aborted. 

Resize range. 

Unknown access method 

'accessMethod''specified by setting 

'Common.Database.accessMethod' 

Explanation: An access method specified by 

Common.Database.accessMethod is not a known access 

method. 



User response: Update 

Common.Database.accessMethod setting. 

Module: 

WsaaJar 

DMH7884E 

Could not find table 

DMH_SYSTEM_ATTR. An incorrect 

'Database.schema' name in Common.cfg 

is the likely cause. 

Explanation: The specified table could not be found in 

the database. 



User response: Verify that the settings in the Database 

section of Common.cfg are correct. 

Module: 

DMH7885E 

WsaaJar 

Default value specified for column 

'columnName', type 'columnType' was not 

valid: 'defaultValue'. 

Explanation: Initialization aborted because of a data 

type mismatch. 



Module: 

DMH7886E 

WsaaJar 

Initialization aborted 


Found unknown table 'tableName' in 

SYSIBM.SYSINDEXES for index 

'indexName'. 

Explanation: An index was found in SYSINDEXES for 

a table that could not be found in SYSTABLES. 



Module: 

DMH7887E 

WsaaJar 

Database version verification aborted. 



SYSIBM.SYSTRIGGERS for trigger 

'indexName'. 

Explanation: A trigger was found in SYSTRIGGERS 

for a table that could not be found in SYSTABLES. 



Module: 

WsaaJar 



DMH7883E 

Could not find an appropriate method 

to access the database. 

Explanation: The database could not be accessed 

through any known method. 



User response: Update the 

Common.Database.accessMethod to specify a valid 

method. 

Module: 

WsaaJar 

DMH7888E 


SYSIBM.SYSKEYCOLUSE for column 

'indexName'. 

Explanation: A primary key was found in 

SYSKEYCOLUSE for a table that could not be found in 

SYSTABLES. 



Module: 

WsaaJar 





DMH7889W One or more required fields are 

missing. 

Explanation: The wizard page has one or more 

required fields that have been left blank. 



Module: 

DMH7890I 

WsaaJar 


Specify values for the required fields. 

Successfully created 'objectType' with 

name 'objectName'. 

Explanation: The specified object was successfully 

added to the database. 



Module: 

DMH7891E 

Explanation: 

WsaaJar 



Module: 

DMH7892E 

Explanation: 


None 

Creation of 'objectType' with name 

'objectName' failed. See log file for more 

information. 

WsaaJar 



Module: 

DMH7893I 

Explanation: 

queue. 

The creation of the specified object type. 

Action aborted. 


Attempting to assign non-numerical 

value 'value' to column 'columnName'. 

WsaaJar 



Module: 

DMH7894I 

Programmatic error. 

Action stopped. 


Successfully added scan root 

'scanRootName' to analysis queue. 

WsaaJar 

Object successfully added to analysis 


None 

Custom query validation work added to 

work queue. 

Explanation: A work item has successfully been added 

to the work queue to validate one or more custom 

queries. 




Module: 

DMH7895I 

WsaaJar 

None 

Deleted numDeletes expired Bookmark 

objects. 

Explanation: The CleanupBookmarks action has been 

executed from the user interface. 



Module: 

DMH7896I 

WsaaJar 


None 

Deleted numDeletes expired Custom 

Query objects. 

Explanation: The CleanupCqs action has been 

executed from the user interface. 



Module: 

DMH7897E 

WsaaJar 


None 

Could not locate asset of type 

[ObjectType] with id [Id] in the database. 

Explanation: The specified asset could not be located 




Module: 

DMH7898E 

WsaaJar 

The current action is aborted. 


Column #ColNum in the SQL query 

must be associated with a unique 

column name. 

Explanation: The specified column in the SQL query 

does not have a name. DB2 on z/OS does not provide 

default column names. 


The user is prompted for correct input. 

User response: Alter the query to specify a name for 

the column (for example, by appending 'as MyColumn' 

to the column definition). 

Module: 

DMH7899E 

WsaaJar 

Invalid Var variable encountered: 

[VarName] 

Explanation: The specified variable name does not 

exist in the current context. 



Module: 

WsaaJar 


Specify a correct value. 



DMH7900E 

A value for an entry on this page is 

missing. Values must be specified for all 

entries. 

Explanation: A value was not specified for one or 

more entries on this page. All entries must have a value 

associated with it. 



Module: 

DMH7901E 

WsaaJar 


Specify a value for all entries. 

Work rules not found for work name 

[WorkName] 

Explanation: The system could not find work rules 

defined in WorkRules.cfg for the work item with the 

specified name. 



Module: 

DMH7902I 

WsaaJar 

The current action is aborted. 

Add work rules to WorkRules.cfg. 

TestName work processor test started. 

Explanation: The specified test work item has been 

successfully added to the work request queue. 



Module: 

DMH7903I 

WsaaJar 


None 

Num work items canceled in queue. 

Explanation: The specified number of work items 

were successfully canceled in the work request queue. 



Module: 

DMH7904I 

WsaaJar 


None 

Num work items removed from queue. 

Explanation: The specified number of work items 

were successfully removed from the work request 

queue. 



Module: 

DMH7905E 

WsaaJar 


None 

ID parameter in URL was not a valid 

integer. 

Explanation: The specified parameter was expected to 

be an integer, but was not. 


The action is aborted. 


Module: 

DMH7906I 

WsaaJar 


Work rules successfully reloaded. 

Explanation: The work rules in WorkRules.cfg were 

successfully reloaded into memory. 



Module: 

DMH7907E 

WsaaJar 

The system is functioning properly. 

None 

Could not locate XML config file (or any 

derivatives) with base name [BaseName] 

in search path [SearchPath] 

Explanation: Could not locate the specified XML file 

in the specified search path. 



Module: 

DMH7908E 

WsaaJar 

The current activity is stopped. 


Exception encountered while loading 

XML config file with base name 

[BaseName]. 


trying to load the specified XML file into memory. 



Module: 

WsaaJar 

The current activity is aborted. 


DMH7909W Warnings occurred while loading XML 

file. Base name=[BaseName]. 

Warnings:Warnings 

Explanation: The specified warnings occurred while 

loading the specified XML file into memory. 



Module: 

WsaaJar 

The current activity continues. 


DMH7916W A warning occurred while running a 

scan: message. 

Explanation: The warning specified in the message 

occurred while performing a scan. 


No action. 

User response: Review the warning message for 

additional details. 

Module: 

WsaaJar 



DMH7917W The system PATH does not contain 

REXX. 

Explanation: The system PATH environment variable 

requires the location of the REXX program. 



User response: Ensure that REXX is on the system 

PATH environment variable and that the PATH is not 

being overwritten by the WebSphere Application Server 

Java virtual machine (JVM). 

Module: 

WsaaJar 

Module: 

DMH7922E 

WsaaJar 

An error occurred in the name processor: 

message. 

Explanation: An exception occurred in the specified 

queue processor handler while performing a scan. 



information 

Module: 

WsaaJar 

Scan is stopped. 

Check log file for additional 

DMH7918W The name specified for the custom 

query is not unique. Specify a different 

name for the query. 

Explanation: The name specified for the custom query 

already exists. Each custom query must have a unique 

name. 


name. 

Issue a prompt for another query 

User response: Enter a different name for the 

customer query. 

Module: 

DMH7919E 

Explanation: 

failed. 

WsaaJar 



information. 

Module: 

DMH7920E 

Attempt to submit DMH6000 as a batch 

job failed 

WsaaJar 

The batch job for DMH6000 process 

The queue processor stopped 

Review the job queue for additional 

An error occurred processing 

HandleContainerScan: message. 

Explanation: An error occurred in the 

HandleContainerScan function while running a scan. 



accuracy. 

Module: 

WsaaJar 

The scan is stopped. 

Check the analysis queue entry for 

DMH7923W A data integrity error detected: message. 

Explanation: An error occurred while performing a 

database integrity check. 


information. 


information. 

Module: 

WsaaJar 

Update the log file with the error 

Review the log file for additional 

DMH7924W A data integrity error detected and fixed: 

message. 

Explanation: An error was detected while performing 

a database integrity check. 

System action: Updated the log file with the error and 

fix the problem. 


information. 

Module: 

DMH7925E 

WsaaJar 


A non-zero return code received from a 

call to DMH6000: rc=[return_code], 

cmd=[command]. 

Explanation: A non-zero return code received on a call 

to DMH6000. The message contains the return code 

and command being processed. 



information 

Module: 

WsaaJar 

Stop the queue processor. 


DMH7921E 

Explanation: 


information. 


information. 

An error occurred processing 

HandleContainerScan: message. 

An error occurred while running a scan. 

Update the activity log with the error 

Review the Jscan log file for more 

DMH7926E 

The number of members matching 

found exceeds the maximum number 

that can be returned. The number of 

members matching [search_pattern] is 

return_size. The maximum return value 

defined by the maxAsmScans 

configuration value is 

[maximun_return_size]. 



Explanation: The number of members matching found 

that match the search pattern exceeds the maximum 

number that can be returned. The maxAsmScans 

configuration attribute defines the maximum return 

size. 


Stop the wizard. 

User response: Increase the maxAsmScans value in 

Common.cfg file or specify a more selective file pattern 

for searching. 

Module: 

DMH7927E 

WsaaJar 

The dsnTemp data set must be a 

sequential data set or partition data set 

member. 

Explanation: The data set specified on the DSORG 

variable is not the correct type. It must be a sequential 

data set or partition data set member. 


message. 

Stop processing and display an error 

User response: Specify a sequential data set name or 

partitioned data set with a member. 

Module: 

WsaaJar 


Module: 

DMH9992E 

Various 


message_text 

Explanation: This is a message used by product 

development and debug function. The message is 

intended for product developers and is not issued 

when using the product. However, it is possible to see 

this message when logging is set to the debug level. 



Module: 

Various 

None. 


DMH7928E 

The component_type asset type with an 

ID of id cannot be deleted: message. 

Explanation: An error occurred while deleting the 

asset specified in the message. 



information 

Module: 

WsaaJar 

Postprocessing is stopped. 


DMH9990I 

message_text 








Module: 

Various 

None. 


DMH9991W message_text 







None. 



Appendix. Notices 

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 grant you 

any license to these patents. You can send license inquiries, in writing, to: 

IBM Director of Licensing 

IBM Corporation 

North Castle Drive 

Armonk, NY 10504-1785 

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-0032, 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 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. 

Licensees of this program who wish to have information about it for the purpose 

of enabling: (i) the exchange of information between independently created 


158 Messages and Codes 

programs and other programs (including this one) and (ii) the mutual use of the 

information which has been exchanged, should contact: 

Intellectual Property Dept. for Rational Software 

IBM Corporation 

3600 Steeles Avenue East 

Markham, ON Canada L3R 9Z7 

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. 

Any performance data contained herein was determined in a controlled 

environment. Therefore, the results obtained in other operating environments may 

vary significantly. Some measurements may have been made on development-level 

systems and there is no guarantee that these measurements will be the same on 

generally available systems. Furthermore, some measurements may have been 

estimated through extrapolation. Actual results may vary. Users of this document 

should verify the applicable data for their specific environment. 

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. 

All statements regarding IBM's future direction or intent are subject to change or 

withdrawal without notice, and represent goals and objectives only. 

This information contains examples of data and reports used in daily business 

operations. To illustrate them as completely as possible, the examples 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 

illustrate 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. 

Each copy or any portion of these sample programs or any derivative work, must 

include a copyright notice as follows: 

© (your company name) (year). Portions of this code are derived from IBM Corp. 

Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights 

reserved.

If you are viewing this information softcopy, the photographs and color 

illustrations may not appear. 

Programming interface information 

Programming interface information is intended to help you create application 

software using this program. 

General-use programming interfaces allow you 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. 

Trademarks and service marks 

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of 

International Business Machines Corp., registered in many jurisdictions worldwide. 

Other product and service names might be trademarks of IBM or other companies. 

A current list of IBM trademarks is available on the Web at “Copyright and 

trademark information” at www.ibm.com/legal/copytrade.shtml. 

Linux is a trademark of Linus Torvalds in the United States, other countries, or 

both. 

Microsoft and Windows are trademarks of Microsoft Corporation in the United 

States, other countries, or both. 

Java and all Java-based trademarks and logos are trademarks or registered 

trademarks of Oracle and/or its affiliates. 

Appendix. Notices 159


Index 

T 

trademarks 159

Messages and Codes - IBM

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?