HP NonStop Data Transformation Engine
Return Codes and Errors
Reference Guide
Abstract
This document contains reference information about the codes and messages that
provide status information about map execution for the HP NonStop™ Data
Transformation Engine (NonStop DTE).
Product Version
NonStop Data Transformation Engine 6.7.1
Version Updates (RVUs)
N/A
Part Number
522436-002
Published
June 2004
Document History
Part
Number
Product Version
Published
427645-001
NonStop Data Transformation
Engine 1.0
December 2000
522436-001
NonStop Data Transformation
Engine 5.0.3
November 2001
522436-002
NonStop Data Transformation Engine
6.7.1
June 2004
Return Codes and Error Messages Reference Guide
2
Contents
Contents
About This Document
Related Documents........................................................................................... 5
Chapter 1 – RUN Function and Platform API
Messages........................................................................................................ 7
Chapter 2 – MEJBADPI
Client-Side Messages ........................................................................................ 11
Server-Side Messages........................................................................................ 11
Chapter 3 – UNIX Platform Environmental Layer
Messages....................................................................................................... 13
Chapter 4 – Adapters
All Adapters................................................................................................... 17
Database ...................................................................................................... 18
Archive (Tar) ................................................................................................. 23
Archive (Zip).................................................................................................. 25
Batch File and Shell Script ................................................................................. 26
BEA MessageQ ................................................................................................ 27
BEA Tuxedo ................................................................................................... 29
E-mail.......................................................................................................... 31
FTP ............................................................................................................. 32
HTTP ........................................................................................................... 33
J2EE Connector Architecture (JCA) Gateway........................................................... 35
Java Class ..................................................................................................... 36
LDAP ........................................................................................................... 37
MSMQ........................................................................................................... 37
Oracle8 AQ.................................................................................................... 38
R/3 ............................................................................................................. 40
Roma BSP...................................................................................................... 42
SOAP ........................................................................................................... 44
TIB/Rendezvous Release 5 ................................................................................. 45
TIB/Rendezvous Release 6 and TX........................................................................ 46
WebSphere MQ ............................................................................................... 47
XML Data ...................................................................................................... 49
Chapter 5 – Maps
Map Execution Error and Warning Messages ............................................................ 50
Map Execution Warning Messages......................................................................... 54
Map Build Error Messages................................................................................... 55
Map Build Warning Messages............................................................................... 60
Map Compile Error Messages............................................................................... 60
Audit Log Status Codes ..................................................................................... 64
Valid Audit Log Status Codes ......................................................................... 64
Warning Audit Log Status Codes ..................................................................... 64
Error Audit Log Status Codes ......................................................................... 65
Contents
Chapter 6 – Type Tree Analysis
Type
Type
Type
Type
Type
Tree Analyzer.......................................................................................... 66
Tree Analysis Logic Error Messages ................................................................ 67
Tree Analysis Logic Warning Messages ............................................................ 83
Tree Analysis Structure Error Messages........................................................... 84
Tree Analysis Structure Warning Messages ....................................................... 85
Chapter 7 – Type Tree Generation
Type Tree Generation Error Messages ................................................................... 88
Type Tree Generation Logic Warning Messages ........................................................ 91
COBOL Copybook............................................................................................. 93
Chapter 8 – System Analysis
System Analyzer ............................................................................................. 97
System Analysis Structure Error Messages............................................................... 97
Systems Using Wildcards Analysis Structure Error Messages ....................................... 100
Index
About This Document
This document contains reference information about the codes and messages that
provide status information about map execution.
This document assumes that the reader knows the Windows environment, has
used the Design Studio, and understands words such as mapping, type trees, and
other basic terminology.
Related Documents
The Mercator Online Library and the SDK Online Library contain information about
all products. Refer to the following documents for more information on topics
discussed frequently in this document.
Related Reference
Description
Execution Commands Reference
Guide
Using executions commands to control
how a map is run by the Command Server
or through the Platform API.
Event Server Reference Guide
Using the Event Server to help you
automate the execution of your systems
of maps. (Mercator Online Library only)
Integration Flow Designer Reference
Guide
Using the Integration Flow Designer as a
Design Studio companion and graphical
facility to manage collections of related
maps. Also graphically organizing these
maps, based upon your requirements,
into logical collections called systems.
(Mercator Online Library only)
Map Designer Reference Guide
The Map Designer user interface and
instruction on specifying mapping rules,
configuring map sources and targets,
defining map-level settings, and executing
a compiled map. (Mercator Online Library
only)
Platform API Reference Guide
Using a platform-specific API with your
application. (SDK Online Library only)
Return Codes and Error Messages Reference Guide
5
About This Document
Related Documents
Related Reference
Description
Resource Adapters Reference Guide
Using adapters as map sources and map
targets in general. More specific
information can be found in the respective
reference guides for each adapter.
Type Designer Reference Guide
Using the Type Designer to create and
edit type trees that describe your data.
(Mercator Online Library only)
Type Tree Maker Reference Guide
Generating type trees from existing data
files. (Mercator Online Library only)
Chapter 1 – RUN Function and
Platform API
The RUN function and Platform API return codes and messages may result when
using the RUN function or when an invalid command line is specified for the
Platform API.
Messages
The following table lists the return codes and messages that can result when using
the RUN function or Platform API.
Note The return codes marked with an asterisk (*) are displayed with the x replaced
with the specific option associated with the error.
Return Code
Message
50
Memory allocation failure
Occurs when memory fails.
51
Card override failure
Occurs when memory fails.
52
I/O initialization failure
Occurs when memory fails.
53
Open audit failure
The audit log file is not accessible.
54
No command line
There is nothing to process.
55
Recursive command files
More than one command file is included in the command line.
56
Invalid command line option –x
The option is invalid for the command.
Return Codes and Error Messages Reference Guide
7
Chapter 1 – RUN Function and Platform API
Return Code
Message
57
Invalid ‘W’ command line option
Messages
The Work file option is invalid.
58
Invalid ‘B’ command line option
The Batch (close) file option is invalid.
59
Invalid ‘R’ command line option
The Refresh Rate option is invalid.
60
Invalid ‘A’ command line option
The Audit option is invalid.
61
Invalid ‘P’ command line option
The Paging option is invalid
62
Invalid ‘Y’ command line option
The General I/O Retry option is invalid.
63
Invalid ‘T’ command line option
The Trace option is invalid.
64
Invalid ‘G’ command line option
The Ignore option is invalid
65
Invalid ‘I’ command line option for input x
The Source option is invalid for the identified input.
66
Invalid size in echo command line for input x
The size specified using the Size option is greater than memory
allowed.
67
Invalid adapter type in command line for input x
The adapter is not of a known adapter type. Includes –IMxxx
where xxx is an unknown adapter alias.
68
Invalid ‘O’ command line option for output x
The target option is invalid for output x. The number of
characters between the single quotes that represent the options
for an adapter exceed 258 characters in the adapter override.
Chapter 1 – RUN Function and Platform API
Messages
Return Code
Message
69
Invalid adapter type in command line for output x
The adapter is not of a known adapter type. Includes –OMxxx
where xxx is an unknown adapter alias.
70
Command line memory failure
Occurs when memory is exceeded during echo or override card
commands.
71
Invalid ‘D’ command line option
The Date option is invalid.
72
Invalid ‘F’ command line option
The Failure option is invalid.
73
Resource manager failure
(Event Server only) The Resource manager is not used, possibly
a memory failure.
74
Invalid ‘Z’ command line option
The Ignore option is invalid.
75
Adapter failed to get data on input
Enable the adapter trace to record the adapter activity to
discover the cause of the error.
76
Adapter failed to put data on output
Enable the adapter trace to record the adapter activity to
discover the cause of the error.
Chapter 1 – RUN Function and Platform API
Return Code
Message
77
Invalid map name
Messages
This message can occur in two different cases. First, this message
occurs when the map name specified on the command line is
more than 32 characters long. Also, this message can occur when
there is an error in the command line such that text for another
execution command is erroneously being interpreted as the map
name. For example, in the command line below, the number
representing the size of the echoed data is missing.
mymap.mmc -IE1S
HereIsMyDataButIForgotToSpecifyTheSize -AED
Because the size is missing, it is interpreted to be 0, such that
there is no echoed data. The next string encountered on the
command line
(HereIsMyData…)
Because it does not start with a hyphen (-), it is assumed to be
the name of the next map to execute. Because the text is longer
than 32 characters, the Invalid Map Name message is
returned.
Chapter 2 – MEJBADPI
The following is a listing of all the codes and messages that can be returned as a
result of using the Mercator Enterprise JavaBean Adapter Programming Interface
(MEJBADPI) to communicate between Mercator resource adapters deployed on the
server-side and maps located on the client-side.
Client-Side Messages
The following table lists the messages that result from adapter activity on the
client-side:
Return Code
Message
-401
Invalid command line option
-402
Missing argument in command line option
-403
Missing command line option
-404
Invalid argument in command line option
-405
Too many arguments in command line option
-406
Failed to read command file
-407
Failed to get JNDI Initial Context
-408
Failed to create session bean
Server-Side Messages
The following table lists the messages that result from adapter activity on the
sever-side:
Return Code
Message
-451
Remote object not found
-452
Remote object type mismatch
-453
Runtime exception occurred
Return Codes and Error Messages Reference Guide
11
Chapter 3 – UNIX Platform
Environmental Layer
UNIX platform environmental layer return codes and messages may result when
an error occurs in the environmental layer. These codes are not an indication of
map execution results. They are results of a condition encountered in the
operating system environmental layer.
Messages
The following table lists the return codes and messages that result on a UNIX
execution platform.
Note Contact Mercator technical support if these errors occur and assistance is required
in determining the problem.
Return Code
Message
101
IO Error
Memory Allocation Failure In IO.
102
IO Error
No memory Left To Read Input Stream.
103
IO Error
Unable To Open Batch File.
104
IO Error
Unable To Read Batch File.
105
IO Error
Invalid Command Line.
106
IO Error
In Executing Merc Exit Command.
107
IO Error
Invalid Map Directory Problem.
108
IO Error
Unable To Open Map.
109
IO Error
Unable To Generate TEMP File Name.
110
IO Error
Unable To Create ‘TEMP’ File.
111
IO Error
Unable To Open ‘TEMP’ File.
112
IO Error
Unable To Read ‘TEMP’ File.
113
IO Error
Unable To Write To TEMP File.
114
IO Error
Unable To Create File: MERCEXIT.COM.
115
IO Error
Unable To Read File: MERCEXIT.COM.
Return Codes and Error Messages Reference Guide
12
Chapter 3 – UNIX Platform Environmental Layer
Messages
Return Code
Message
116
IO Error
In Executing Command File: MERCEXIT.COM.
117
IO Error
Unable To Open File: merc.exit.
118
IO Error
Unable To Read ‘merc.exit’ File.
119
IO Error
Unable To Open Pipe.
120
IO Error
On Pipe Closure.
121
IO Error
Unable To Create File:[mercexit.cm].
122
IO Error
Unable To Write ‘mercexit.cm’ File.
123
IO Error
Unable To Execute ‘mercexit.cm’ File.
124
IO Error
Unable To Redirect Screen IO.
125
IO Error
Unable To Redirect Screen IO to Console.
Not Used
126
127
IO Error
Unable To Process Tmp IO File(s)
Correctly.
128
IO Error
File Is Inaccessible:
129
IO Error
Unable To Rename Tmp IO File.
130
IO Error
Search For Tmp IO File Failed.
131
IO Error
Search For Map Input File Failed.
132
IO Error
Unable To Produce Shadow File.
133
IO Error
Unable To Get Adapter Shadow.
134
IO Error
Unable To Init Shared Memory.
135
IO Error
Unable To Acquire Resource Semaphore.
Not Used
136
138
IO Error
Invalid EXITPARM Structure Size.
139
IO Error
Unable To Write SHMID To File.
140
IO Error
Unable To Read SHMID From File.
141
IO Error
Read Empty SHMID From File.
142
IO Error
Unable To Get Current Directory.
143
IO Error
File Path Too Long.
144
IO Error
Unable To Add ID To Shared Memory.
145
IO Error
OverrideCards() Failure.
146
IO Error
AddRunEntry() Failure.
Chapter 3 – UNIX Platform Environmental Layer
Messages
Return Code
Message
147
IO Error
Unable To Set/Reset File: .mercShm
148
IO Error
doOpenShm(); Unable To Cleanup From
Previous Core Dump.
149
IO Error
openShm(); Unable To Process UID
Information.
150
IO Error
openShm(); Unable To Acquire Process
Resource Lock.
151
IO Error
openShm(); Unable To Release Process
Resource Lock.
152
IO Error
closeShm(); Unable To Acquire Process
Resource Lock.
153
IO Error
closeShm(); Unable To Release Process
Resource Lock.
154
IO Error
closeShm(); General Closure Error.
155
IO Error
Unable To Open Shm ID File: .mercShm
156
IO Error
Unable To Verify Shared Memory.
157
IO Error
Unable To Update Shared Memory.
158
IO Error
Unable To Open PID File: .mercPid
159
IO Error
Unable To Open Info Log: mercinfo.log
160
IO Error
Unable To Open Semaphore Log:
mercsem.log
161
IO Error
Unable To Open Mutex Log: mercmutex.log
162
IO Error
Involving Shared Memory Processing.
163
IO Error
Unable To Install Control C Handler.
164
IO Warning
No Map Found To Process.
165
IO Error
Invalid Environmental MERC_DEBUG Value.
166
IO Error
Invalid Environmental MERC_FILE_LOCKS
Value.
167
IO Error
Invalid Environmental MERC_TMP_DIR
Value.
168
IO Error
Invalid Environmental MERC_HOME_DIR
Value.
169
IO Error
Unable To Create Shared Memory.
170
IO Error
Unable To Attach To Shared Memory.
Chapter 3 – UNIX Platform Environmental Layer
Messages
Return Code
Message
171
IO Error
Unable To Detach From Shared Memory.
172
IO Error
Detected In Shared Memory Cleanup.
173
IO Error
Shared Memory Corruption
174
IO Error
Unable To Delete Shared Memory.
175
IO Error
Unable To Get Shared Memory Status.
176
IO Error
Invalid User Id For Shm Deletion.
177
IO Error
Unable To Update PID File: .mercPid
178
IO Error
Unable To Read PID File: .mercPid
179
IO Error
Unable To Do API Initialization.
180
IO Error
Unable To Update Uid In File: .mercShm
181
IO Error
Unable To Update Uid For Shared Memory
182
IO Error
Missing Shm Id Or Invalid Uid In File:
.mercShm
183
IO Error
Invalid Shm Id In File: .mercShm
184
IO Error
Invalid Uid In File: .mercShm
185
IO Error
In Doing Old Shm Cleanup
186
IO Error
Unable To Open Debug Log
Event Server only
187
IO Error
Unable To Open Debug5 Log
Event Server only
Chapter 4 – Adapters
Adapter return codes and messages provide information on the adapter
operations, adapter command syntax errors, and reasons for unsuccessful
transactions.
All Adapters
The following is a listing of all the codes and messages that are common among
all adapters.
Return Code
Message
-1
Unknown error code
-2
Exception occurred
-3
Function failed
-4
Invalid property specified
-5
Property type mismatch
-6
Property not set
-7
Invalid index
-8
Null argument
-9
Invalid argument
-10
Failed to allocate memory
-11
No properties defined for the object
-12
Invalid type specified
-13
Connection failed
-14
File open failed
-15
File write failed
-16
File read failed
-17
File position function failed
-18
Invalid object specified
-19
Null object specified
Return Codes and Error Messages Reference Guide
16
Chapter 4 – Adapters
Database
Return Code
Message
-20
Illegal function call
-21
Unexpected end-of-file
-22
Only one top level element allowed
-23
Not a top level element
-24
3rd party function failed
-25
Attempt was made to resize non-resizable memory
-26
Running map failed
-27
Loading map failed
-28
Item requested does not exist
-29
Failed to load library
-30
Invalid seek performed
-31
Buffer too small - data truncated
-600
Internal error
Message indicates nature of problem.
Database
After database adapter activity completes, messages display indicating the results.
These messages may also be recorded in the appropriate files as specified, which
may include audit logs, trace files, and execution summary. These codes and
messages can be returned for the following database adapters:
♦ DB2 (MVS (CL1))
♦ DB2 (MVS)
♦ DB2 (Windows/UNIX)
♦ Informix
♦ Microsoft SQL Server
♦ ODBC
♦ OLE DB
♦ Oracle
♦ Sybase SQL Server
Chapter 4 – Adapters
Database
The following is a listing of all the codes and messages that can be returned as a
result of using the database adapters for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
Success
12
Database -b argument is required with arguments
mdqfile -m and query -q
1001
One or more records could not be processed
1002
No data found
-1001
Memory allocation error
-1002
Failed to allocate ODBC environment
-1003
Failed to allocate ODBC statement
-1004
Failed to allocate ODBC connection
-1005
Failed to connect to the database
-1006
Failed to prepare the SQL statement
-1007
Failed to obtain definition of column
-1008
Failed to bind parameters to the SQL statement
-1009
Failed to execute the SQL statement
-1010
Failed to open a cursor
-1011
Failed to insert a row into the database
-1012
Failed to read file
-1013
Failed to open file
-1014
The input buffer was of incorrect form
-1015
Failed to write to file
-1016
Database type is unknown
-1017
Failed to parse SQL statement
-1018
Failed to define host variables
-1019
Failed to logoff the database
Chapter 4 – Adapters
Database
Return Code
Message
-1020
Failed to close the cursor
-1021
Failed to bind parameters to the SQL statement
-1022
Failed to fetch a long data value
-1023
Failed to perform a file seek
-1024
Failed to create file
-1025
The specified query could not be found
-1026
The specified database could not be found
-1027
Failed to load DLL
-1028
Failed to get address of function
-1029
Failed to fetch a row of data
-1030
Failed to get data from the database
-1031
Failed to get data from the database
-1032
No rows were updated
-1033
The number of rows affected was undeterminable
-1034
The supplied statement was syntactically invalid
-1035
Failed to create an execution thread
-1036
Failed to get extended error text
-1037
Table is not accessible
-1038
Failed to disconnect from the database
-1039
Failed to free the database connection
-1040
Failed to free the environment
-1041
MDQ file is invalid
-1042
Failed to close file
-1043
No database connection could be found
-1044
No database type was specified with -DBTYPE
-1045
Failed to find column attributes
-1046
Failed to get the number of result columns
-1047
Failed to get large data
-1048
Failed to cleanup the database connection
-1049
Databases are not supported
Chapter 4 – Adapters
Database
Return Code
Message
-1050
Failed to load DLL
-1051
Failed to get address of function
-1052
Failed to commit or rollback the transaction
-1053
Failed to free the statement
-1054
Insufficient data was provided
-1055
Failed to bind parameters to the SQL statement
-1056
Failed to define large data value
-1057
Failed to put large data value
-1058
Failed to commit the transaction
-1059
Failed to rollback the transaction
-1060
The update statement was invalid
-1061
No type could be found to match column name
-1062
No suitable presentation could be found for a
column
-1063
No suitable presentation could be found for a
column
-1064
No suitable presentation could be found for a
column
-1065
Internal error
-1066
No more rows were returned
-1067
No trigger was defined for the input
-1068
Data was unexpectedly terminated
-1069
Required command line options missing
-1070
The database command line was invalid
-1071
Could not find environment variable
-1072
Failed to attach to database
-1073
Failed to convert datatype to native database type
-1074
Failed to get list of SQL servers
-1075
Failed to get list of databases
-1076
Failed to initialize stored procedure
Chapter 4 – Adapters
Database
Return Code
Message
-1077
Failed to set parameter to stored procedure
-1078
Failed to execute stored procedure
-1079
Failed to get column information
-1080
Failed to declare host variables
-1081
Command line token could not be found
-1082
Failed to create an event
-1083
The command line is too long
-1084
The function/procedure has no return value
-1085
A variable length binary column is not permitted
-1086
Error occurred writing to a LOB column
-1087
Error occurred reading from a LOB column
-1088
Connection to Open Server failed
-1089
Poll to Open Server failed
-1090
The map contains outdated DB parameters. Rebuild
the map
-1091
An output date was of an incorrect format
-1092
Internal error occurred
-1093
Burst complete
-1094
Type already exists and override was not specified
-1095
No Row or ProcedureCall group can be found
-1096
Failed to format output from an object type
-1097
Failed to create an object
-1098
An object is not permitted in fixed type tree
-1099
Failed to convert database parameters from ASCII to
EBCDIC
-1100
One or more columns/parameters are of an
unsupported datatype
-1101
Failed to configure run-time environment.
-1102
Failed to Allocate context structure, unknown
reason or not enough memory
-1103
A trigger could not be defined for a watch event
Chapter 4 – Adapters
Archive (Tar)
Return Code
Message
-1104
Unique table columns are required for row-based
watch events
-1105
Procedure is not accessible
-1106
The configured transaction manager is not supported
-1107
System error occurred while waiting for a watch
event
-1108
Triggering is not supported for this adapter.
-1109
User terminated database access
-1110
The trace file name too long, or the running
directory too deep
The database trace file name and/or the directory name in which
the failed map is located, may be longer than 128 characters.
Ensure the file and/or directory name is shorter than 128
characters.
-1302
A trigger event could not be registered
-2002
Insufficient data passed to output card
Archive (Tar)
The following is a listing of all the codes and messages that can be returned as a
result of using the Archive (Tar) adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
0
-1
-1
-1
-1
-1
GetArchive succeeded
PutArchive succeeded
Can’t open the file %s
Unable to allocate %d bytes
‘%s’ does not exist
‘%s’ name too long
‘%s’ not a file
Chapter 4 – Adapters
Archive (Tar)
Return Code
Message
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
‘%s’ not found
‘%s’ seek error
‘%s’ unknown file type ‘%c’
Data not available from Mercator
Failed to open archive (%s)
Insufficient memory: allocation of %d bytes failed
Insufficient memory: allocation of %d bytes failed
Invalid command line – missing data file name
Invalid command line – missing entry name
Invalid option (-a, -c, or –u) request for
M4TAR_GetArchive
Member ‘%s not found in archive
Out of memory
Unable to allocate memory (%Id bytes)
Unable to create directory %s
Unable to read archive
Archive read error
Bad directory structure
Can’t create ‘%s’
Can’t delete ‘%s’
Can’t delete scratch file
Can’t link ‘%s’ – data stay in ‘%s’
Can’t open directory ‘%s’
Can’t append ‘%s’
Delete option (-d) is for file archives only
Directory checksum error
Error extracting ‘%s’
Error reading ‘%s’
Tape blocksize error
Tape close error
Tape read error
Tape read failed
Tape seek failed
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
Chapter 4 – Adapters
Archive (Zip)
Return Code
Message
-1
Tape write error
The following is a listing of all the codes and messages that can be returned as a
result of using the Archive (Tar) adapter on RS/6000 AIX only:
Return Code
Message
-2
Invalid Entry Point. Must specify M4TAR_GetArchive
or M4TAR_PutArchive.
Archive (Zip)
The following is a listing of all the codes and messages that can be returned as a
result of using the Archive (Zip) adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
-1
OK
Invalid command line: missing zip file name after
'file' keyword.
Invalid command line: missing zip file name after
'memory' keyword.
Invalid command line: missing zip file name after
'echo' keyword.
Invalid command line: missing zip member name (after
zip file name).
Invalid command line: expected 'file', 'memory', or
'echo' as first argument.
Invalid command line: missing zip file name.
Internal Error: Resource Manager Error
ZIP_ADD: DynaZip error occurred (????).
ZIP_MEMTOFILE: DynaZip error occurred (????).
UNZIP_COUNTALLZIPMEMBERS: DynaZip error occurred
(????).
-1
-1
-1
-1
-1
-600
-?
-?
-?
Chapter 4 – Adapters
Batch File and Shell Script
Return Code
Message
-?
UNZIP_COUNTNAMEDZIPMEMBERS: DynaZip error occurred
(????).
UNZIP_GETNEXTNAMEDZIPINFO: DynaZip error occurred
(????).
UNZIP_FILETOMEM: DynaZip error occurred (????).
-?
-?
-? is a DynaZip API error return (non-zero) made negative if > 0
and where ???? is a DynaZip API supplied error message.
Batch File and Shell Script
The following is a listing of all the codes and messages that can be returned as a
result of using the Batch File and the Shell Script adapters for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
OK
-1
Insufficient memory to continue
-1
Library Initialization Failed
-2
Invalid Entry Point. (AIX adapters only)
-3BATCH
Could not load adapter
-3
Error Sending Data
-4
Error Receiving Data
-5
BATCH: Insufficient memory to continue
1
No data provided. Create on content specified:
command not executed.
7
Command Still Executing
Applies to adapter target.
-1
Incorrect Arguments
-2
Error Writing Output Files
-2
Error Reading Input Data
Chapter 4 – Adapters
BEA MessageQ
Return Code
Message
-5
Insufficient Memory to Continue
-6
Error Executing Command (Return Code XX) XX is
return code from command
-7
Command Still Executing
Applies to adapter source.
-600
Internal Error: Resource Manager Error
BEA MessageQ
In addition to the following return codes, the BEA MessageQ adapter can return
BEA MessageQ error codes. Consult the BEA MessageQ documentation for
descriptions of these codes.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
Success
1
One or more messages were removed from the queue but
not processed
2
Timeout period has expired
3
No messages were found
4
No message was sent (zero content)
-1
Can't use this option on input
-2
Can't use this option on output
-3
Queue type specified missing or not valid
-4
Message Priority specified missing or not valid
-5
Timeout specified missing or not valid
-6
Target queue name missing on output
-7
Message class specified but not provided
-8
Message type specified but not provided
Chapter 4 – Adapters
BEA MessageQ
Return Code
Message
-9
Bogus delivery mode specified
-10
Bogus UMA mode specified
-11
Incomplete header information specified
-12
Buffer size specified but not provided
-13
Command option not recognized
-14
Memory allocation error
-15
Adapter called with invalid parameters
-16
Q type specified with no Q name
-17
Invalid header found
-18
Order key in selection array not correct
-19
Operator in selection array not correct
-20
Can't attach to BMQ message bus
-21
Error setting up selection array
-22
Error creating a handle for an SDM message on input
-23
Error on Get of SDM message
-24
Failure on call to confirm delivery of message
-25
No SDM tags in message from Get
-26
Requested SDM tag not in message from Get
-27
SDM tag requires too much memory for adapter
-28
Failure decoding SDM tag
-29
Error on Get of buffer style message
-30
Failure on locate call for target queue name
-31
Error creating a handle for an SDM message on output
-32
Failure on encode of SDM tag field on output
-33
Put of message on output failed
-34
Failure of Unrecoverable Message Action
-35
Internal error (exit parameters)
-36
Error pams_exit can't kill queues
Chapter 4 – Adapters
BEA Tuxedo
Return Code
Message
-37
Error can't free allocated memory
-38
Message quantity specified but not provided
BEA Tuxedo
In addition to the following return codes, the BEA Tuxedo adapter can return BEA
Tuxedo error codes. Consult the BEA Tuxedo documentation for descriptions of
these codes.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
1
2
3
4
Success
Timeout period has expired
No messages were found
No message was sent (zero content)
One or more messages were removed from the queue but
not processed
Caller mode must be C or S
An option on the command line is not valid for
output
An option on the command line is not valid for input
Syntax of the –B option is invalid
Data format is not one of recognized values
An option on the command line is unrecognized
Memory allocation error
Failed to allocate Tuxedo buffers
Tuxedo system error occurred: see adapter trace file
Failed to convert data to/from Tuxedo type
Adapter called with invalid parameters
Tuxedo service call failed
FML conversion failed
-1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
Chapter 4 – Adapters
BEA Tuxedo
Return Code
Message
-14
-15
-16
-17
-18
-19
-20
-21
-22
-23
Tuxedo service does not exist
Input buffer type not supported by service
Output buffer type not supported by service
The service does not support transactions
No service name or /Q details were specified
No queue space was specified
No queue name was specified
No data format was specified
No view name was specified
FML Value format was specified but no field was
named
/Q QSPACE name does not exist
/Q queue name is invalid
/Q message ID is invalid
No message was available with specified attributes
The /Q queue is full
Input data supplied from both in GET and in adapter
command
No value provided with the Message Quantity option
View adapter’s trace file for diagnostic messages
Timeout missing or not valid
Address of the message list is missing
A message with the given ID could not be found
Conversion error: STRING type is not NULL terminated
More than one watch is defined for the same queue
Event server is supported for /Q only
Transaction already started, couldn’t start the new
one!
Invalid value for Message Quantity option if Listen
command not specified
-24
-25
-26
-27
-28
-29
-30
-31
-32
-33
-34
-35
-36
-37
-38
-40
*Applies only to BEA Tuxedo Release 7.1
-41
Invalid context, check MAXDISPATCHTHREADS value, it
should be greater than 1, see adapter trace file
*Applies only to BEA Tuxedo Release 7.1
Chapter 4 – Adapters
E-mail
Return Code
Message
-42
User data properties not set
*Applies only to BEA Tuxedo Release 7.1
-43
MPI Stream Error
*Applies only to BEA Tuxedo Release 7.1
-44
MPI Call Error
*Applies only to BEA Tuxedo Release 7.1
E-mail
The following is a listing of all the codes and messages that can be returned as a
result of using the E-mail adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
OK
-1
Insufficient memory to continue
-1
Library Initialization Failed
-2
Invalid Entry Point. (AIX adapters only)
-3MAPI
Could not load adapter
-3CCMAIL
Could not load adapter
-3NOTES
Could not load adapter
-3INET
Could not load adapter
-3
Error Sending Data
-4
Error Receiving Data
-5
MAPI: Insufficient memory to continue
-5
CCMAIL: Insufficient memory to continue
-5
NOTES: Insufficient memory to continue
-5
INET: Insufficient memory to continue
0
No Messages
Chapter 4 – Adapters
FTP
Return Code
Message
1
No data provided. Create on content specified: no
data sent.
-1
Unsupported protocol
-1
Insufficient memory to continue
-1
Invalid protocol selection.
for Put)
-5
Memory Error
-600
Internal Error: Resource Manager Error
-?
Mail Error
where -? is an API-specific error code, made
negative if >0
-???
???? (SMTP only)
where -??? is an error code returned from the
server, made negative and where ???? is a serversupplied error message
(SMTP for Get/POP3
FTP
The following is a listing of all the codes and messages that can be returned as a
result of using the FTP adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
OK
-1
Insufficient memory to continue
-1
Library Initialization Failed
-2
Invalid Entry Point. (AIX adapters only)
-3FTP
Could not load adapter
-3
Error Sending Data
-4
Error Receiving Data
-5
FTP: Insufficient memory to continue
Chapter 4 – Adapters
HTTP
Return Code
Message
1
No data provided. Create on content specified: no
data sent.
2
Could not interpret STOU response!
not be renamed.
-1
FTP Setup failed
-1
FTPRecv() failed
-1
FTPSend() failed
-101
No URL was specified
-600
Internal Error: Resource Manager Error
-???
????
where -??? Is an error code returned from the
server, made negative and where ???? is a serversupplied error message
Target file will
HTTP
The following is a listing of all the codes and messages that can be returned as a
result of using the HTTP adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-???
-1
Sever specific error message
doHTTP failed
Chapter 4 – Adapters
J2EE Connector Architecture (JCA) Gateway
J2EE Connector Architecture (JCA) Gateway
The following is a listing of all the codes and messages that can be returned as a
result of using the J2EE Connector Architecture (JCA) Gateway adapter for sources
or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-1001
Invalid command line option
-1002
Missing argument in command line option
-1003
Missing command line option
-1004
Invalid argument in command line option
-1005
Too many arguments in command line option
-1006
Missing command file
-1007
Invalid command file option
-1008
Missing argument in command file option
-1009
Missing command file option
-1010
Invalid argument in command file option
-1011
Missing XML tag in command file
-1012
Empty record name must be specified
-1013
Unknown XML data passed
-1014
Unknown record type received
-1015
Unsupported JCA functionality
-1016
Failed to get Record Factory
-1017
Failed to instantiate object
-1018
Failed to set one or more object properties
-1019
Failed to create Connection factory
-1020
Connect failed
-1021
XML parsing failed
Chapter 4 – Adapters
Java Class
Return Code
Message
-1022
Failed to create interaction
-1023
Failed to execute interaction
-1024
Record factory failed to create Record
-1025
Failed to load Plug-in
-1026
Plug-in streamToRecord failed
-1027
Plug-in recordToStream failed
-1028
Failed to begin local transaction
-1029
Failed to commit local transaction
-1030
Failed to rollback local transaction
Java Class
The following is a listing of all the codes and messages that can be returned as a
result of using the Java Class adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-1001
Java exception occurred: exception_description
The variable exception_description represents the exception
error returned by the Java language.
Chapter 4 – Adapters
LDAP
LDAP
The following is a listing of all the codes and messages that can be returned as a
result of using the LDAP adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-???
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
libLDAP error
Failed to initialize writer object
Failed to write output data
Failed to initialize reader object
Failed to read input data
DN too long
No DN specified
Too many attributes to modify
Attribute too long
Too many values to modify
Memory allocation failed
MSMQ
In addition to the following return codes, the MSMQ adapter can return MSMQ
error codes. Consult the MSMQ documentation for descriptions of these codes.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-1001
Trace file could not be accessed
-1002
Adapter command is incorrect
-1003
Failed to load and initialize MSMQ library
Chapter 4 – Adapters
Oracle8 AQ
Return Code
Message
-1004
Queue could not be opened
-1005
Message could not be stored on the queue
-1006
Message could not be retrieved from the queue
-1007
Transaction could not be rolled back explicitly
-1008
Transaction could not be committed
-1009
Queue could not be closed
-1010
Invalid message format
-1011
Transaction monitor not supported
-1012
Problem occurred on the queue cursor
-1013
New transaction could not be started
-1014
Queue path could not be translated to the format
name
-1015
Machine name could not be translated to the machine
GUID
-1016
Transaction usage was required for a nontransactional queue
Oracle8 AQ
In addition to the following return codes and messages, the Oracle8 AQ adapter
can return Oracle8 AQ error codes. Consult the documentation from Oracle
Corporation about the AQ messaging system for descriptions of these codes.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-1001
Invalid command line option
-1002
Missing command line argument
-1003
Invalid command line argument
-1004
Command line processing failed
Chapter 4 – Adapters
Return Code
Message
-1005
Invalid queue name
-1101
Unsupported data type
-1102
Invalid release character position
Chapter 4 – Adapters
R/3
R/3
The following is a listing of all the codes and messages that can be returned as a
result of using the R/3 adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
OK
1
No data provided. Create on content specified: no
connection attempted.
2
Map execution failed, data not sent
-1
Error in data prep
-1
Error: cannot get function definition
-1
RFC Open failed
-1
Put Data failed
-1
Unknown Error
-1
Error in setup
-1
TID sent twice so not processed
-1
R/3 may try again later
-1
Couldn’t init adapter.
New_semaphore() failed.
-1
Couldn’t init adapter.
Watch count exceeded.
-1
Couldn’t init watchpoint. New_thread() failed.
-1
Error in data prep (invalid Idocs).
-1
Error in data prep (invalid BAPI data or Idoc
missing EDI_DC)
-1
Connection Test failed
-1
Connection Test not possible, handle is invalid
-1
RFC Accept Failed
-1
Install Function Failed
-1
InitRfcConn Failed
Chapter 4 – Adapters
R/3
Return Code
Message
-1
XXXXX = FAILURE(0)
For API’s that return non-zero on success.
-?
XXXXX = FAILURE(?)
For API’s that return non-zero on success.
-1
XXXXX = RFC_FAILURE: Error occurred.
-2
XXXXX = RFC_EXCEPTION: Exception raised.
-3
XXXXX = RFC_SYS_EXCEPTION: System exception raised,
connection closed.;
-4
XXXXX = RFC_CALL: Call received.
-5
XXXXX = RFC_INTERNAL_COM: Internal communication,
repeat
For internal use only.
-6
XXXXX = RFC_CLOSED: Connection closed by the other
side.
-7
XXXXX = RFC_RETRY: No data yet (RfcListen or
RfcWaitForRequest only).
-8
XXXXX = RFC_NO_TID: No Transaction ID available.
-9
XXXXX = RFC_EXECUTED: Function already executed.
-10
XXXXX = RFC_SYNCHRONIZE: Synchronous Call in
Progress (only for Windows).;
-11
XXXXX = RFC_MEMORY_INSUFFICIENT: Memory
insufficient.
-12
XXXXX = RFC_VERSION_MISMATCH: Version mismatch.
-13
XXXXX = RFC_NOT_FOUND: Function not found
For internal use only.
-14
XXXXX = RFC_CALL_NOT_SUPPORTED: This call is not
supported on WINDOWS.
-15
XXXXX = RFC_NOT_OWNER: Caller does not own the
specified handle.
-16
XXXXX = RFC_NOT_INITIALIZED: RFC not yet
initialized.
-?
XXXXX = RFC_UNKNOWN: Unknown result code ?.
Chapter 4 – Adapters
Roma BSP
Return Code
Message
-?
Is an API-specific error code, made negative if >0
XXXXX
is a SAP API or TID Mgmt Function
-464
Initialization failure.
-600
Internal Error: Resource Manager Error
-1000
Initialization failure.
(program arguments)
-2000
Initialization failure.
(backup/log init)
(sanity check failed)
Roma BSP
The following is a listing of all the codes and messages that can be returned as a
result of using the Roma BSP adapter for sources or targets.
For the return code –25, the variable error_string will be replaced with the
Roma adapter command that caused an error. Usually, this is a syntax error or a
misspelled command.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
Successful operation
1
Queue is not opened
2
Time has expired
3
One or more messages were removed from the queue
but not processed
4
One or more messages were found on the queue but
not processed
5
No messages were found
6
No message body was provided
-1
-CN command specified but value not provided
-2
-BE command specified but value not provided
-3
-BS command specified but value not provided
Chapter 4 – Adapters
Return Code
Message
-4
-MID command specified but value not provided
-5
-CID command specified but value not provided
-6
-LSN command specified but value not provided
-7
-P command specified but value not provided
-8
-QTY command specified but value not provided
-9
-TY command specified but value not provided
-10
-REQ command specified but value not provided
-11
Memory allocation error
-12
Problem initializing server
-13
Invalid header definition
-14
Invalid theme handle
-15
Problem initializing client
-16
Problem with server GetRequest
-17
Problem with client GetResponse
-18
Problem with client PutRequest
-19
Problem with server PutResponse
-20
Missing both client name and business element
-21
Cannot specify both server and client
-22
Client with no business service
-23
Incompatible commands
-24
Empty command line
-25
Adapter command error: error_string
-26
Error in transaction management
-27
Specified connection does not exist
-28
Specified connection is not valid
-600
Internal Error: Resource Manager Error
Chapter 4 – Adapters
SOAP
SOAP
The following is a listing of all the codes and messages that can be returned as a
result of using the SOAP adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-2001
General internal adapter error
-2002
Invalid command line option
-2003
Missing argument in command line option
-2004
Missing command line option
-2005
Invalid argument in command line option
-2006
FC
A fault code has been generated.
-2007
Xpath data not found
-2008
Xpath duplicate data found
-2009
Stream error
-2010
XML invalid
Chapter 4 – Adapters
TIB/Rendezvous Release 5
TIB/Rendezvous Release 5
In addition to the following return codes, the TIB/Rendezvous Release 5 adapter
can return TIB/Rendezvous error codes. Consult the TIBCO/Rendezvous
documentation for descriptions of these codes.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
0
Successful operation
1
Could not close session
2
Extraneous data in the complex message found
3
WARNING: Extra messages were fetched and not
processed
-1
Command line is in error
-2
Could not open session
-3
Unknown error encountered
-4
Could not put message
-5
Could not get message
-6
Could not delete message from cache
-7
Failed to allocate memory
-8
Triggering failed
-9
Error in specified number of watches
-10
Function could not initialize: improper parameter
-11
Could not add node
-13
Message not in the cache
-14
Exceeded the max thread count
-15
Failed to create a thread
-16
Failed to create a socket
-17
Invalid socket handle
Chapter 4 – Adapters
TIB/Rendezvous Release 6 and TX
Return Code
Message
-18
Could not find socket/pipe: no byte match
-19
Timed out waiting for rvcm_Confirm
TIB/Rendezvous Release 6 and TX
In addition to the following return codes, the TIB/Rendezvous Release 6 and TX
adapters can return TIB/Rendezvous error codes. Consult the TIBCO/Rendezvous
documentation for descriptions of these codes.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
1
Could not close RV
2
Extraneous data in the complex message found
3
WARNING: Extra messages were fetched and not
processed
4
WARNING: Timeout period has expired
-1
Command line is in error
-2
Could not open RV
-3
Could not connect to RV transport
-4
Unknown error encountered
-5
Could not publish message
-6
Could not retrieve message
-7
Failed to allocate memory
-8
Triggering failed
-9
Error in specified number of watches
-10
Function could not initialize: improper parameter
-13
Message not in the cache
-14
Exceeded the max thread count
-19
Timed out waiting for rvcm_Confirm
Chapter 4 – Adapters
WebSphere MQ
Return Code
Message
-20
Overflowed buffer
WebSphere MQ
In addition to these codes, the WebSphere MQ adapter can return WebSphere MQ
error codes. Consult the WebSphere MQ documentation for descriptions of these
codes.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-1001
Trace file could not be accessed
-1002
Adapter command is incorrect
-1003
Queue could not be opened
-1004
Message could not be stored on the queue
-1005
Message could not be retrieved from the queue
-1006
Connection could not be closed
-1007
Global transaction could not be started
-1008
Transaction could not be rolled back explicitly
-1009
Transaction could not be committed
-1010
Queue could not be closed
-1011
Invalid message format
-1012
Transaction monitor not supported
-1013
Error queue operation could not complete
-1015
Unable to Begin Commitment Control (Tandem)
-1016
Unable to Backout(Tandem)
-1017
Unable to Commit(Tandem)
-1018
Segmentation not supported(Tandem)
Chapter 4 – Adapters
XML Data
XML Data
The following is a listing of all the codes and messages that can be returned as a
result of using the XML Data adapter for sources or targets.
Note Adapter return codes with positive numbers are warning codes that indicate a
successful operation. Adapter return codes with negative numbers are error codes
that indicate a failed operation.
Return Code
Message
-??
-1
-1000
-1001
-1002
-1100
-1101
RunMap return code (see Platform API reference)
MERC_HOME_DIR not set
MAF: Failed to initialize implementation
MAF: Implementation not initialized
MAF: Unexpected error occurred
MAF: Unknown exception raised
MAF: Internal error occurred
Chapter 5 – Maps
This chapter discusses map error and warning messages.
Map Execution Error and Warning Messages
After a map is executed, map execution messages indicate the execution results.
If audit is enabled, these messages are also recorded in the appropriate audit log
for the map.
The following is a list of all the codes and messages that can be returned as a
result of running a map:
Note The return codes marked with an asterisk (*) are warning codes. See Map
Execution Warning for a consecutive list of the warning codes for a map.
Return Code
Message
0
Map completed successfully
1
User aborted map
If you cancel the Server before the map completes, this message
is displayed.
2
Not enough memory to execute map
Close all other running applications
3
Could not open map
The .mmc file cannot be found. Insure the file name or path is
correct.
4
Could not read map
If you have ported your map and sent it with FTP to another
platform, make sure you have done so using the BINARY option so
the map’s contents will not be corrupted.
5
Could not read inputs
Contact Mercator Technical Support.
Return Codes and Error Messages Reference Guide
47
Chapter 5 – Maps
Map Execution Error and Warning Messages
Return Code
Message
6
Invalid map handle
Contact Mercator Technical Support.
7
Invalid card number was specified
Your map may be corrupt. Contact Technical Support
8
One or more inputs was invalid
Turn the input trace on, run the map again and read the trace file.
9
Source not available
An incorrect file name or path for a source may be specified.
10
Internal error
Contact Mercator Technical Support.
11
Could not build one or more outputs
An attempt may have been made to write to a read-only directory,
or an output file directory may be missing.
12
Target not available
An incorrect file name or command for a target may be specified.
13
Could not open work files
An invalid path for work files may be specified.
14*
One or more outputs was invalid
A number produced an overflow condition. Enable the Trace
Output option, re-run the map, and read the trace file.
15
Map must be recompiled
You may be trying to run a map with a server that has a different
version from the Map Designer version used to compile the map.
Make sure the Map Designer and the Server versions match.
16
Disk write error
An attempt may have been made to write to a read-only directory
or file. Also, check the amount of available disk space.
Chapter 5 – Maps
Map Execution Error and Warning Messages
Return Code
Message
17
Disk read error
An attempt may have been made to access a file on a shared
resource that is not accessible. Also, check the amount of available
disk space.
18*
Page usage count error
Your data mapped correctly; however, an internal paging problem
exists. Contact Mercator Technical Support.
19
Internal calling error
Contact Mercator Technical Support.
20
Reopen file failed
Your map did not run correctly. Contact Mercator Technical
Support.
21*
Input valid but unknown data found
Enough of the input data to conform to the card definition was
recognized, but there was more data at the end of the input
stream. Enable the Trace Input setting, re-run the map and read
the map trace file (.mtr). For an explanation of the trace file, see
the Map Designer Reference Guide.
22
Page size too small
Increase the page size or decrease the number of types in the
type tree that are used to define the input.
23
Unable to reuse work file
Use the same page settings that were used when you created the
existing work file. For information about page settings, see the
Map Designer Reference Guide.
24
Database error
A problem was encountered attempting to write to an output
database. Read the database trace file (.dbl) for information about
possible causes.
25
File attribute error
When running an AS/400 Command Server, if you use the OS/400
data definition to create a file, check the definition of the output
card to see if it matches.
Chapter 5 – Maps
Map Execution Error and Warning Messages
Return Code
Message
26*
Output type in error
The entire card object is in error.
27*
Output type contains errors
One or more components failed restrictions or a component rule.
28*
Input type contains errors
This occurs when mapping data of a component that has a
RESTART assigned to it, and at least one instance of the
component in the input data is invalid.
29*
Output valid, but unknown data found
This occurs when enough of the output data is recognized to
conform to the card definition, but there was more data at the end
of the output stream.
30
FAIL function aborted map
This occurs when the FAIL function is used within the map to
cause map execution to cease. The return message specified as
the second argument of the FAIL function appears in place of the
xxx in the Execution Audit section of the Audit Log. See the
Functions & Expressions Reference Guide for more information
about using the FAIL function.
31
This map requires a Command Server for Japan
This map used Japanese characters and must be executed using a
Command Server for Japan.
32
Invalid map instance handle
Contact Mercator Technical Support.
33
Map instance handle in use
Contact Mercator Technical Support.
Chapter 5 – Maps
Map Execution Warning Messages
Map Execution Warning Messages
The following table lists the return codes that are warnings only – meaning that
the map did complete, but some problems occurred. You can change the default
behavior for the warning codes by specifying Fail on Warnings or Ignore Warnings
through the map settings or by using the –F or –Z execution command. See the
Map Designer Reference Guide, Integration Flow Designer Reference Guide, and
Execution Commands Reference Guide for more information.
Note The warning codes marked with an asterisk (*) are returned only when at least
one output is listed in the Data Audit Settings of the Organizer and in the Map
Settings dialog, MapAudit is enabled with Data enabled for the Log setting.
Return Code
Message
14
One or more outputs was invalid
A number produced an overflow condition. Enable the Trace
Output option, re-run the map, and read the trace file.
18
Page usage count error
Your data mapped correctly; however, an internal paging problem
exists. Contact Mercator Technical Support.
21
Input valid but unknown data found
Enough of the input data to conform to the card definition was
recognized, but there was more data at the end of the input
stream. Enable the Trace Input setting, re-run the map and read
the map trace file (.log). For information, see the Map Designer
Reference Guide.
26*
Output type in error
The entire card object is in error.
27*
Output type contains errors
One or more components failed restrictions or a component rule.
28
Input type contains errors
This occurs when mapping data of a component that has a
RESTART assigned to it, and at least one instance of the
component in the input data is invalid.
Chapter 5 – Maps
Map Build Error Messages
Return Code
Message
29*
Output valid, but unknown data found
This occurs when enough of the output data is recognized to
conform to the card definition, but there was more data at the
end of the output stream.
Map Build Error Messages
Build errors prevent a map from being compiled. If build errors occur, view the
errors, correct the problem(s), and build the map again. A map cannot be run if it
has not been built.
In the following build messages; these letters are used as variables:
x = the map where the error occurred
y = the output that contains the rule in error
w, z = numbers
Words used as variables are in italics. For example, map-name represents the
name of a map.
Return Code
Message
M100
Analysis aborted by user.
M101
Map: x
Unresolved rules exist.
Hint: Go to map x. If you want to use the unresolved rules, copy
and paste them. Delete any unwanted unresolved rules.
M102
Map: x Output: y
Functional map referenced in rule must have one
(and only one) output.
Map referenced: map-name.
Hint: Go to the functional map. Delete the extra card(s).
Chapter 5 – Maps
Map Build Error Messages
Return Code
Message
M103
Map: x Output: y
Number of arguments for functional map map-name is
incorrect.
Number specified: #specified Number required: #required
Hint: Add or delete arguments from the rule, or add or delete
input cards in the functional map.
M104
Map: x Output: y
Empty rule cell. Rule required.
Hint: Go to map x. Enter rules in each empty rule cell.
M105
Map: x Output: y
Rule references unknown type: type name.
Hint: You may have made a change in the type tree. If the card
object is unknown, edit the card, and choose a valid type. You
may have incorrectly typed in the name. If you drag and drop the
type, the correct name is automatically entered.
M106
Map: x
Circular map reference from map map-name.
Analysis must terminate.
Hint: Two different maps contain rules that reference each other.
Remove the reference from one of the maps.
M107
Map: x Output: y
Rule syntax is invalid starting at character
position: position#.
Rule
Hint: This error may occur if a previous Mercator version did not
catch the syntax error. Generally, syntax errors are caught as
rules are entered. Please see the Release Notes for any changes in
rule syntax.
Chapter 5 – Maps
Map Build Error Messages
Return Code
Message
M108
Map: x Output: y
Rule references unknown map: map-name.
Hint: Re-enter the map name in the rule. You may have typed the
map name incorrectly. Map names are case-sensitive. You may
have forgotten to create the functional map. If so, create it.
M109
Map: x Card: cardname
Card is invalid.
Hint: The type name is either misspelled or you may have made a
change in the type tree by deleting or renaming the type. Edit the
card, and choose a valid type.
M110
Map: x Card: cardname
Card type is not a group or item.
Hint: You probably changed your type tree. Edit the card, and
choose a group or item.
M111
Map: x Output: y
Argument #w for map map-name does not match type of
input card #z.
Hint: Change argument #w so that it matches the type of input
card #z, or change the type of input card #z so that it matches
argument #w.
M112
Map: x Output: y
Argument #w for map map-name does not match item
sub-class of card #z.
Hint: Change argument #w so that it matches the item sub-class
of input card #z, or change the type of input card #z so that its
item sub-class matches argument #w.
Chapter 5 – Maps
Map Build Error Messages
Return Code
Message
M113
Map: x Output: y
Argument #w for function function name is invalid.
Hint: Select the rule for output, y. Right-click the map rule and
choose Properties from the context menu. The Rule Properties
dialog box allows you to view function arguments and object
properties. You have either referenced an invalid object, or used
the wrong type of argument.
M114
Map: x Output: y
Output argument of rule does not match output type:
rule.
Hint: The map rule is resulting in a data object of the wrong type.
Check the functions and the maps used within the map rule and
make sure that the entire rule evaluates to the correct type.
You may have dragged and dropped a group that is a different
type to this output. Use a functional map instead. If the rule
contains the name of a functional map, go to the functional map
and edit the output card. Make sure the type of the output card is
the output y.
M115
Map: x Output: y
Output argument of rule does not match output item
sub-class: rule.
Hint: Notice the output y. The output argument of the rule must
have the same item sub-class as y.
M116
Map: x Output: y
Type Tree for this card is not used in executable map.
Hint: Edit the card and select a type tree that is used in the
executable map. Each type tree used each functional map must be
one of the trees used in the executable map.
M117
Map: x Output: y
Cannot assign an output to itself.
Hint: You might have accidentally dragged and dropped an output
into its own rule cell. Edit the rule.
Chapter 5 – Maps
Map Build Error Messages
Return Code
Message
M118
Map: x Output: y
Rule references unknown comment: commentname @
inputname
Hint: The input card type does not have a floating component, or
you have incorrectly typed in the name. If the input card has a
floating component, on the Card menu, the Show Floating
Component Type option will be activated.
M119
Map: x Output: y
Output argument of rule is not a partition of
output type.
Hint: If the rule contains the name of a functional map, go to the
functional map and edit the output card. Make sure the type of the
output card is the output y, or a partition of the output y.
M120
Map: x Output: y
Operand is an invalid operand.
Hint: For information on operands, see the Functions &
Expressions Reference Guide.
M121
Map: x
Input card #cardnumber uses invalid tree.
Hint: You may have moved the type tree or map source from its
original location. You may have incorrectly entered the name of
the type tree.
M122
Map: x
Output card #cardnumber uses invalid tree.
Hint: You may have moved the type tree or map source from its
original location. You may have incorrectly entered the name of
the type tree.
M123
Map: x Card: cardname
Card updates input, but card type and data file do
not match an input.
Hint: Edit the card and re-define the update information.
Chapter 5 – Maps
Map Build Warning Messages
Return Code
Message
M124
Map: x Output: y
Rule references type later in output: rule
Hint: If possible, enter an equivalent rule in a later output. An
output referenced in a rule must appear above the rule within the
output card.
M125
Map: x
Invalid audit: audit statement
Hint: Look at the Audit Settings window. An asterisk * appears
next to any invalid audit statement. Re-enter the audit statement.
Map Build Warning Messages
A build warning alerts you of a condition that might be problematic. If you build a
map and there are warnings, but no errors, the map is compiled. You can ignore
warnings. To ignore warnings, from the Tools menu, choose Options, and select
General. Enable the Suppress build warnings check box.
Return Code
Message
M200
Map: x Output: y
Size of input item is greater than size of output
item.
Map Compile Error Messages
The compile errors display on the Build Results tab of the Organizer. Maps with
compile errors may not be run. Correct all compile errors to run a map.
The following table lists the errors than can result when a map is built:
Return Code
Message
M1001
Compile aborted by user.
Hint: You cancelled the build process before it completed.
Chapter 5 – Maps
Map Compile Error Messages
Return Code
Message
M1002
Not enough memory available to compile.
Hint: Close other applications that you have open, and build the
map again.
M1003
Couldn’t open the map source file.
Hint: The map may be corrupt. Please contact Technical Support.
M1004
Couldn’t find the executable map.
Hint: The map source file may be corrupt. Please contact
Technical Support.
M1005
Duplicate map names in output file.
Hint: If you get this error, please contact Technical Support.
M1006
Tree used in functional map not used by executable
map.
Hint: Edit the card in the functional map or the executable map so
both cards reference the same tree.
M1007
No delimiter defined for delimited type.
Hint: In the Type Designer, specify the delimiter value for the
given type.
M1008
Unable to open the type tree for input card.
Hint: The type tree may not exist in the directory specified, or the
type tree may be corrupt. If your type tree is corrupt, please
contact Technical Support.
M1009
Unable to open the type tree for output card.
Hint: The type tree may not exist in the directory specified or the
type tree may be corrupt.
M1010
Unable to find a type in an input tree.
Hint: If you get this error, please contact Technical Support.
M1011
Unable to find a type in an output tree.
Hint: If you get this error, please contact Technical Support.
M1012
Could not retrieve query information.
Hint: Either you have not installed the Database Interface
Designer or the .mdq file is incorrect.
Chapter 5 – Maps
Map Compile Error Messages
Return Code
Message
M1013
Could not retrieve database information.
Hint: Either you have not installed the Database Interface
Designer or the .mdq file is incorrect.
M1014
Input data file for executable map missing or
invalid.
Hint: Check the file names used for sources and targets.
M1015
Output data file for executable map missing or
invalid.
Hint: Check the file names used for sources and targets.
M1016
Parser found an invalid rule.
Hint: If you get this error, please contact Technical Support.
M1017
Output card referenced in rule not found.
Hint: If you get this error, please contact Technical Support.
M1018
Invalid component or partition subtype encountered.
Hint: If you get this error, please contact Technical Support.
M1019
Unable to resolve type references in rule.
Hint: If you get this error, please contact Technical Support.
M1020
Couldn’t open the compiled map file.
Hint: The compiled map file may be corrupt. Please contact
Technical Support.
M1021
Error writing to the compiled map file. (Disk
full?)
Hint: Delete unnecessary files from your hard disk.
M1022
Unable to resolve type references in audit.
Hint: If you get this error, please contact Technical Support.
M1023
Unable to open .MDQ file.
Hint: The .mdq file does not exist or is otherwise inaccessible.
M1024
Database not found.
Hint: The named database is not defined in the specified .mdq
file.
Chapter 5 – Maps
Map Compile Error Messages
Return Code
Message
M1025
Database Error.
Hint: An unexpected error occurred while processing and .mdq
file.
M1026
Input MDQ file not found.
Hint: The .mdq file does not exist or is otherwise inaccessible.
M1027
Input query not found.
Hint: The named query is not defined in the specific .mdq file.
M1028
Output MDQ file not found.
Hint: The .mdq file does not exist or is otherwise inaccessible.
M1029
Output database not found.
Hint: The named database is not defined in the specified .mdq
file.
M1030
At least one syntax object literal is too long.
Hint: Type Designer analysis is required.
Chapter 5 – Maps
Audit Log Status Codes
Audit Log Status Codes
The status attribute in the Audit Log is a letter followed by a code number. The
letter of the status attribute tells whether the data is valid V, or caused an error E,
or caused a warning W.
Valid Audit Log Status Codes
The following table explains the number in the status code if the letter is V.
Status Code
Description
V00
The object and all contained objects are valid
V01
The object is valid, but it contains invalid object(s)
Warning Audit Log Status Codes
The following table explains the number in the status code if the letter is W.
Status Code
Description
W01
Object failed restriction
W02
Object failed presentation
W03
Object failed size check
Error Audit Log Status Codes
The following table explains the number in the status code if the letter is E.
Status Code
Description
E00
Object is an unidentified foreign object (UFO) - data not
associated with any particular type
E01
Object failed restriction
E02
Object failed presentation
Chapter 5 – Maps
Audit Log Status Codes
Status Code
Description
E03
Object failed size check
E04
Invalid or missing initiator
E05
Invalid or missing terminator
E06
Object missing required component
E07
Object is invalid because it contains components in error
E08
Object failed partitioning
E09
Object failed component rule
E10
This required object is missing
E11
Invalid or missing delimiter
E12
More instances of an object exist than have been specified (Only
implemented for unordered groups)
Chapter 6 – Type Tree Analysis
This chapter discusses error and warning messages that result from an analysis of
a type tree.
Type Tree Analyzer
The Type Tree Analyzer checks the logic and internal consistency of your data
definitions. Type tree analyzer error and warnings messages are issued on the
type of analysis that is performed: logic and structural.
♦ Logical analysis addresses the integrity of the relationships that you define in
the type tree.
♦ Structural analysis addresses the integrity of the underlying database.
Warnings indicate a successful analysis and are relatively insignificant. Warning
messages provide information about inconsistencies that occurred and were
automatically resolved when the type tree was changed.
Errors are important. Error messages provide information about errors in your
type definitions that you should correct. An error may result in unpredictable
results in your mapping.
Words in italics represent information that varies, indicating information specific to
the type for which the message is generated.
Return Codes and Error Messages Reference Guide
63
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Type Tree Analysis Logic Error Messages
The following table lists the logic error messages that result from a logical analysis
of a type tree:
Return Code
Message
L100
COMPONENT neither inherited nor local: ‘type name’
of TYPE: ‘type name’
Hint: Look at the super-type’s component list. The component is a
valid type, but the supertype has a component list that restricts
you from using this type as a component. You may have added
subtype components before adding supertype components. Either
remove all supertype components or add the components in error
to the component list of the supertype.
L101
This GROUP must have at least one component – TYPE:
‘type name’
Hint: If you want to map this group, add components. If you do
not want to map it, make it a category.
L102
Circular reference found in COMPONENT # (‘type
name’) – TYPE: ‘type name’
Hint: Look at the type of the component in error. It is probably
missing an initiator or terminator.
L103
Circular reference found in Floating Component type
– TYPE: ‘type name’
Hint: Look at the floating component type in error. It is probably
missing an initiator or terminator.
L104
DELIMITER for TYPE – ‘type name’ must have a value
Hint: All delimited groups need a delimiter. Edit delimited group
properties to insert the missing delimiter.
L105
DELIMITER type neither inherited nor local – TYPE:
‘type name’
Hint: The delimiter name has been entered incorrectly. It should
be the name of a local type, or the name of an inherited delimiter,
or the name of a type in the sub-tree of the inherited delimiter.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L106
Default DELIMITER not specified – TYPE: ‘type name’
Hint: This Type was specified with a FIND option for its delimiter.
Please add a default value to define what to use for building
outputs.
L107
Default DELIMITER not in restriction list – TYPE:
‘type name’
Hint: This delimiter was specified as a syntax item. Add the
default value to the restriction list for that syntax item.
L108
DELIMITER type is not a SYNTAX ITEM – TYPE: ‘type
name’
Hint: Delimiters specified as an item must be specified to be
interpreted as SYNTAX to set the value of the delimiter if it
appears as a component in a data stream.
L109
DELIMITER type has no restriction list – TYPE:
‘type name’
Hint: All syntax items need a restriction list.
L110
RELEASE CHARACTER neither inherited nor local –
TYPE: ‘type name’
Hint: The release character name has been entered incorrectly. It
should be either the name of a local type, the name of an
inherited release character, or the name of a type in the sub-tree
of the inherited release character.
L111
Default RELEASE CHARACTER not specified – TYPE:
‘type name’
Hint: This Type was specified with a syntax item for its release
character. Please add a default value to define a value for the
release character that has not been encountered in the data.
L112
Default RELEASE CHARACTER not in restriction list –
TYPE: ‘type name’
Hint: This Type was specified with a syntax item for its release
character. Please add the default value to the restriction list of
that syntax item.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L113
RELEASE CHARACTER type is not a SYNTAX ITEM – TYPE:
‘type name’
Hint: Release characters specified as an item must be specified to
be interpreted as SYNTAX to set the value of the release character
if it appears as a component in a data stream.
L114
RELEASE CHARACTER type has no restriction list –
TYPE: ‘type name’
Hint: All syntax items need a restriction list.
L115
Floating Component TYPE neither inherited nor local
– TYPE: ‘type name’
Hint: The floating component name has been entered incorrectly.
It should be either the name of a local type, the name of an
inherited floating component, or the name of a type in the subtree of the inherited floating component.
L116
INITIATOR type neither inherited nor local – TYPE:
‘type name’
Hint: The initiator name has been entered incorrectly. It should be
either the name of a local type, the name of an inherited initiator,
or the name of a type in the sub-tree of the inherited initiator.
L117
Default INITIATOR not specified – TYPE: ‘type name’
Hint: This Type was specified with a syntax item for its initiator.
Add a default value to define a value for that initiator has not
been encountered in the data.
L118
Default INITIATOR not in restriction list – TYPE:
‘type name’
Hint: This Type was specified with a syntax item for its initiator.
Add the default value to the restriction list of that syntax item.
L119
INITIATOR type is not a SYNTAX ITEM – TYPE: ‘type
name’
Hint: Initiators specified as an item must be specified to be
interpreted as SYNTAX to set the value of the initiator if it appears
as a component in a data stream.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L120
INITIATOR type has no restriction list – TYPE:
‘type name’
Hint: All syntax items need a restriction list.
L121
TERMINATOR type neither inherited nor local – TYPE:
‘type name’
Hint: The terminator name has been entered incorrectly. It should
be either the name of a local type, the name of an inherited
terminator, or the name of a type in the sub-tree of the inherited
terminator.
L122
Default TERMINATOR not specified – TYPE: ‘type
name’
Hint: This Type was specified with a syntax item for its
terminator. Add a default value to define a value for that
terminator has not been encountered in the data.
L123
Default TERMINATOR not in restriction list – TYPE:
‘type name’
Hint: This Type was specified with a syntax item for its
terminator. Please add the default value to the restriction list of
that syntax item.
L124
TERMINATOR type is not a SYNTAX ITEM – TYPE: ‘type
name’
Hint: Terminators specified as an item must be specified to be
interpreted as SYNTAX to set the value of the terminator if it
appears as a component in a data stream.
L125
TERMINATOR type has no restriction list – TYPE:
‘type name’
Hint: All syntax items need a restriction list.
L126
COMPONENT range minimum (#) greater than range
maximum (#) – COMPONENT ‘type name’ – TYPE: ‘type
name’
Hint: The minimum range must be less than or equal to the
maximum range.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L127
COMPONENT range minimum (#) less than inherited
range minimum(#) – COMPONENT ‘type name’ – TYPE:
‘type name’
Hint: The component in error has been inherited. Look at the
range of the component with the same name in the super-type’s
component list.
L128
COMPONENT range maximum (#) greater than inherited
range maximum(#) – COMPONENT ‘type name’ – TYPE:
‘type name’
Hint: The component in error has been inherited. Look at the
range of the component with the same name in the super-type’s
component list.
L129
COMPONENT RULE references a COMPONENT later in the
component list – ‘type name’ – TYPE: ‘type name’
Hint: Move the component rule to the component later in the list.
L130
COMPONENT RULE references undefined type –
COMPONENT # of TYPE: ‘type name’
Hint: Verify the spelling of the data object name. The rule should
reference a data object name of the component or a data object
name of a component earlier in the component list.
L131
Reserved for future use.
L132
Invalid partitioning: TYPE has no SUBTYPES – TYPE:
‘type name’
Hint: Remove the partitioned option from the class window or add
sub-types to the Type in error.
L133
Type of COMPONENT exists, but its relative name is
not valid: ‘type name’ in TYPE: ‘type name’
Hint: To get the correct relative name, drag the type you want to
use as a component and drop it in the component list of the Type.
(Remember to delete the invalid component!)
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L134
Reference to ‘ANY’ not allowed: COMPONENT number #
of TYPE: ‘type name’
Hint: In this case, the Type in error is a group and it is not the
root of a partitioned tree. ANY cannot be used if that component
needs to be validated. So, if that group is partitioned, you cannot
use ANY for a component up to and including the identifier (if
there is one). If that group is not partitioned, you cannot use ANY
at all.
L135
COMPONENT number # cannot reference a CATEGORY in
TYPE: ‘type name’ (because group is not
partitioned)
Hint: In this case, the Type in error is a group and it’s not the root
of a partitioned tree. A category cannot be used if the component
must be validated. So, if that group is partitioned, you cannot use
a category for a component up to and including the identifier (if
there is one). If that group is not partitioned, you cannot use a
category as a component at all.
L136
COMPONENT ‘type name’ occurs more than once in list
– TYPE: ‘type name’
Hint: Each component in the same component list must have a
unique type name. Try to make sub-types of the type name in
error and replace each non-unique component with one of the
new sub-types.
L137
COMPONENT ‘type name’ and its super-type cannot be
in same COMPONENT LIST (in TYPE: ‘type name’)
Hint: Try making another sub-type of the super-type and replace
the super-type reference with the new sub-type.
L138
COMPONENT ‘type name’ is same type as delimiter –
TYPE: ‘type name’
Hint: A component and a delimiter cannot have the same name.
You may need to add sub-types to the type name used in error to
resolve this one.
L139
COMPONENT ‘type name’ is sub-type of delimiter –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify a
delimiter. You can add another sub-type to the syntax item and
replace the delimiter name with the new sub-type name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L140
COMPONENT ‘type name’ is super-type of delimiter –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify a
delimiter. You can add another sub-type to the syntax item and
replace the component name with the new sub-type name.
L141
COMPONENT ‘type name’ is same type as initiator –
TYPE: ‘type name’
Hint: A component and an initiator cannot have the same name.
You can add sub-types to the type name used in error and replace
both the component name and the initiator name.
L142
COMPONENT ‘type name’ is sub-type of initiator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify an
initiator. You can add another sub-type to the syntax item and
replace the initiator name with the new sub-type name.
L143
COMPONENT ‘type name’ is super-type of initiator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify an
initiator. You can add another sub-type to the syntax item and
replace the component name with the new sub-type name.
L144
COMPONENT ‘type name’ is same type as terminator –
TYPE: ‘type name’
Hint: A component and a terminator cannot have the same name.
Try adding sub-types to the type name used in error and replace
both the component name and terminator name with one of the
new sub-types.
L145
COMPONENT ‘type name’ is sub-type of terminator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify a
terminator. You can add another sub-type to the syntax item and
replace the terminator name with the new sub-type name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L146
COMPONENT ‘type name’ is super-type of terminator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify a
terminator. You can add another sub-type to the syntax item and
replace the component name with the new sub-type name.
L147
COMPONENT ‘type name’ is same type as Floating
Component – TYPE: ‘type name’
Hint: Make both the floating component name and the component
name sub-types of the floating component.
L148
COMPONENT ‘type name’ is sub-type of Floating
Component – TYPE: ‘type name’
Hint: Make both the floating component name and the component
name sub-types of the floating component.
L149
COMPONENT ‘type name’ is super-type of Floating
Component – TYPE: ‘type name’
Hint: Make both the floating component name and the component
name sub-types of the floating component.
L150
COMPONENT ‘type name’ is same type as release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify a release
character. You can add sub-types to the syntax item and replace
both the component name and the release character name with
the new sub-type names.
L151
COMPONENT ‘type name’ is sub-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify a release
character. You can add another sub-type to the syntax item and
replace the release character name with the new sub-type name.
L152
COMPONENT ‘type name’ is super-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify a release
character. You can add sub-types to the syntax item and replace
the component name with the new sub-type name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L153
DELIMITER ‘type name’ is same type as initiator –
TYPE: ‘type name’
Hint: A delimiter and an initiator cannot have the same name. You
may need to add sub-types to the type name used in error and
replace both the delimiter and initiator names to refer to the new
sub-types.
L154
DELIMITER ‘type name’ is sub-type of initiator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a delimiter. You can add another sub-type to the
syntax item and replace the initiator name with the new sub-type
name.
L155
DELIMITER ‘type name’ is super-type of initiator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a delimiter. You can add another sub-type to the
syntax item and replace the delimiter name with the new subtype name.
L156
DELIMITER ‘type name’ is same type as terminator –
TYPE: ‘type name’
Hint: A delimiter and a terminator cannot have the same name.
You may need to add sub-types to the type name used in error
and replace both the delimiter and terminator names to refer to
the new sub-types.
L157
DELIMITER ‘type name’ is sub-type of terminator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
delimiter and a terminator. You can add another sub-type to the
syntax item and replace the terminator name with the new subtype name.
L158
DELIMITER ‘type name’ is super-type of terminator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
delimiter and a terminator. You can add another sub-type to the
syntax item and replace the delimiter name with the new subtype name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L159
DELIMITER ‘type name’ is same type as release
character – TYPE: ‘type name’
Hint: A delimiter and a release character cannot have the same
name. You may need to add sub-types to the type name used in
error and replace both the delimiter and release character names
to refer to the new sub-types.
L160
DELIMITER ‘type name’ is sub-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
delimiter and a release character. You can add another sub-type
to the syntax item and replace the release character name with
the new sub-type name.
L161
DELIMITER ‘type name’ is super-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
delimiter and a release character. You can add another sub-type
to the syntax item and replace the delimiter name with the new
sub-type name.
L162
DELIMITER ‘type name’ is same type as Floating
Component – TYPE: ‘type name’
Hint: A delimiter and a floating component cannot have the same
name. Try adding sub-types to the type name used in error and
replace both the delimiter and floating component names to refer
to the new sub-types.
L163
DELIMITER ‘type name’ is sub-type of Floating
Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
delimiter and a floating component. You can add another sub-type
to the syntax item and replace the floating component name with
the new sub-type name.
L164
DELIMITER ‘type name’ is super-type of Floating
Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
delimiter and a floating component. You can add another sub-type
to the syntax item and replace the delimiter name with the new
sub-type name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L165
INITIATOR ‘type name’ is same type as terminator –
TYPE: ‘type name’
Hint: An initiator and a terminator cannot have the same name.
You may need to add sub-types to the type name used in error
and replace both the initiator and terminator names to refer to
the new sub-types.
L166
INITIATOR ‘type name’ is sub-type of terminator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a terminator. You can add another sub-type to the
syntax item and replace the terminator name with the new subtype name.
L167
INITIATOR ‘type name’ is super-type of terminator –
TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a terminator. You can add another sub-type to the
syntax item and replace the initiator name with the new sub-type
name.
L168
INITIATOR ‘type name’ is same type as release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a release character. You can add sub-types to the
syntax item and replace both the initiator name and the release
character name with a new sub-type name.
L169
INITIATOR ‘type name’ is sub-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a release character. You can add another sub-type to
the syntax item and replace the release character name with the
new sub-type name.
L170
INITIATOR ‘type name’ is super-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a release character. You can add another sub-type to
the syntax item and replace the initiator name with the new subtype name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L171
INITIATOR ‘type name’ is same type as Floating
Component – TYPE: ‘type name’
Hint: An initiator and a floating component cannot have the same
name. Try adding sub-types to the type name used in error and
replace both the initiator and floating component names with the
new sub-types.
L172
INITIATOR ‘type name’ is sub-type of Floating
Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a floating component. You can add another sub-type
to the syntax item and replace the floating component name with
the new sub-type name.
L173
INITIATOR ‘type name’ is super-type of Floating
Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both an
initiator and a floating component. You can add another sub-type
to the syntax item and replace the initiator name with the new
sub-type name.
L174
TERMINATOR ‘type name’ is same type as release
character – TYPE: ‘type name’
Hint: A terminator and a release character cannot have the same
name. You may need to add sub-types to the type name used in
error and replace both the terminator and release character
names with the new sub-types.
L175
TERMINATOR ‘type name’ is sub-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
terminator and a release character. You can add another sub-type
to the syntax item and replace the release character name with
the new sub-type name.
L176
TERMINATOR ‘type name’ is super-type of release
character – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
terminator and a release character. You can add another sub-type
to the syntax item and replace the terminator name with the new
sub-type name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L177
TERMINATOR ‘type name’ is same type as Floating
Component – TYPE: ‘type name’
Hint: A terminator and a floating component cannot have the
same name. You may need to add sub-types to the type name
used in error and replace both the terminator and floating
component names with the new sub-types.
L178
TERMINATOR ‘type name’ is sub-type of Floating
Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
terminator and a floating component. You can add another subtype to the syntax item and replace the floating component name
with the new sub-type name.
L179
TERMINATOR ‘type name’ is super-type of Floating
Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
terminator and a floating component. You can add another subtype to the syntax item and replace the terminator name with the
new sub-type name.
L180
RELEASE CHARACTER ‘type name’ is same type as
Floating Component – TYPE: ‘type name’
Hint: A release character and a floating component cannot have
the same name. You may need to add sub-types to the type name
used in error and replace both the release character and floating
component names to refer to the new sub-types.
L181
RELEASE CHARACTER ‘type name’ is sub-type of
Floating Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
release character and a floating component. You can add another
sub-type to the syntax item and replace the floating component
name with the new sub-type name.
L182
RELEASE CHARACTER ‘type name’ is super-type of
Floating Component – TYPE: ‘type name’
Hint: This occurs when a syntax item is used to specify both a
release character and a floating component. You can add another
sub-type to the syntax item and replace the release character
name with the new sub-type name.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L183
COMPONENT NAME ambiguous: ‘type name’ in TYPE:
‘type name’
Hint: This type has a component whose relative name can be
associated with more than one type in the type tree. Rename the
conflicting types.
L184
RESTRICTION longer than max TYPE size – RESTRICTION
# of TYPE: ‘type name’
Hint: The Type in error is an item. Either change the maximum
size of the item or remove the restriction.
L185
RESTRICTION used in an earlier partition –
RESTRICTION # of TYPE: ‘type name’
Hint: Item Partitions must have mutually exclusive restrictions.
Remove the restriction from one of the partition restriction lists.
L186
Type of COMPONENT does not exist – ‘type name’ in
TYPE: ‘type name’
Hint: You probably entered an incorrect type name. Try the drag
and drop approach to get the correct one.
L187
TYPE must be partitioned (since in a partitioned
tree and has sub-types) – TYPE: ‘type name’
Hint: All types in a partitioned sub-type must have mutually
exclusive data objects. Set the partitioned property for the type in
error.
L188
Reserved for future use.
L189
TYPE is FIXED, but COMPONENT # is not fixed – TYPE:
‘type name’
Hint: If the component is not intended to be fixed in size, change
the group format for the Type to implicit. If the group format is
intended to be fixed, check the component: if that component is
an item, make sure it has a Padded To length; if that component
is a group, change its type to be of fixed syntax.
L190
BINARY text ITEM used as COMPONENT neither FIXED
nor SIZED – COMPONENT # of TYPE: ‘type name’
Hint: The size of a binary text item must either have a Padded To
length or it must be sized by the previous component.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L191
COMPONENT with SIZED attribute is not an UNSIGNED
INTEGER ITEM TYPE – COMPONENT # of TYPE: ‘type
name’
Hint: A component used to size the component that follows it
must be defined as an unsigned integer item type.
L192
The last COMPONENT in the COMPONENT LIST may not
have a SIZED attribute: TYPE: ‘type name’
Hint: Specify a component to follow the one with the sized
attribute.
L193
Range of COMPONENT # must have a maximum value to
indicate how many placeholders are needed for its
series in TYPE: ‘type name’.
Hint: Change the range maximum to a specific value (not “s”) if
you may re-define the data this way.
L194
Cannot distinguish delimiter from terminator in
TYPE: ‘type name’.
Hint: Make the range of the last component in the type fixed or
make the delimiter of the type different from its terminator.
L195
Cannot distinguish delimiter contained in COMPONENT
# from terminator of TYPE: ‘type name’.
Hint: Make that component bound or make that contained
delimiter different from the type terminator.
L196
Cannot distinguish delimiter of COMPONENT # from
delimiter of TYPE: ‘type name’.
Hint: Make that component bound or make that component’s
delimiter different from the type delimiter.
L197
Cannot distinguish delimiter of COMPONENT # from
delimiter of TYPE: ‘type name’.
Hint: Make that component bound, or make that component’s
delimiter different from the type delimiter, or specify a range
maximum that has a specific value (not “s”) for the last
component of COMPONENT #.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Error Messages
Return Code
Message
L198
Cannot distinguish delimiter contained in COMPONENT
# from delimiter of TYPE: ‘type name’.
Hint: Make that contained component bound or make that
contained component’s delimiter different from the type delimiter.
L200
Cannot distinguish delimiter contained in COMPONENT
# from delimiter of TYPE: ‘type name’.
Hint: Either make that contained component bound, make that
contained component’s delimiter different from the type delimiter,
or specify a range maximum that has a specific value (not “s”) for
the last component of the contained component.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Logic Warning Messages
Type Tree Analysis Logic Warning Messages
The following tables list the logic warning messages that result from a logic
analysis of a type tree. The following table lists the warnings than can result when
a map is compiled:
Warnings should be resolved because they may produce unpredictable results at
mapping time.
Return Code
Message
L199
COMPONENT # is not distinguishable from COMPONENT #
that may follow in TYPE: ‘type name’.
Hint: Make the first COMPONENT bound, or look at the tables in
the Type Designer Reference Guide see how you can define the
two component types as distinguishable.
L201
Different data objects of COMPONENT # are not
distinguishable in TYPE: ‘type name’.
Hint: See the Type Designer Reference Guide for more information
on distinguishable objects.
L202
RESTRICTION list deleted: TYPE is not an ITEM –
TYPE: ‘type name’
Hint: Type class was changed from an item to a group or category,
so the restriction list was deleted. If this was not your intent,
change it back to the way it was.
L203
COMPONENT list deleted: TYPE is an ITEM – TYPE:
‘type name’
Hint: Type class was changed from a group to a item or category,
so Mercator deleted its component list. If this was not your intent,
change it back to the way it was.
L204
DELIMITER deleted: TYPE is not a DELIMITED GROUP –
TYPE: ‘type name’
Hint: Group format was changed from delimited to something else,
so Mercator deleted its delimiter. If this was not your intent,
change it back to the way it was.
Chapter 6 – Type Tree Analysis
Type Tree Analysis Structure Error Messages
Return Code
Message
L205
COMPONENT RULE deleted: TYPE is a CATEGORY – TYPE:
‘type name’ (warning)
Hint: Type class was changed from a group to a category, so its
component rule was deleted. If this was not your intent, change it
back to the way it was.
L206
DELIMITER cannot be found (because first component
is not required) – TYPE: ‘type name’ (warning)
Hint: If the delimiter is missing, a previously set initiator value or
the default value is used.
Type Tree Analysis Structure Error Messages
The following table lists the structure error messages that result from a structural
analysis of a type tree:
Return Code
Message
S100
Invalid TYPE Name: SubTYPE # of TYPE: ‘type name’
S101
Invalid TYPE chain: SubTYPE # of TYPE: ‘type name’
S118
Invalid TYPE NAME WhereUsed chain – TYPE NAME: ‘type
name’ (error).
S133
Referenced COMPONENT not ‘InUse’ – COMPONENT # of
TYPE: ‘type name’ (error).
S134
COMPONENT previously referenced – COMPONENT # (COMP
#) of TYPE: ‘type name’ (error).
S149
Bad Parent COMPONENT Index – COMPONENT ‘type name’ –
TYPE: ‘type name’ (error)
Chapter 6 – Type Tree Analysis
Type Tree Analysis Structure Warning Messages
Type Tree Analysis Structure Warning Messages
The following table lists the structure warning messages that result from a
structural analysis of a type tree:
Return Code
Message
S102
Unused DELIMITER deleted: ‘type name’ (at index #)
S103
Invalid DELIMITER pointer deleted – TYPE: ‘type
name’
S104
Invalid default DELIMITER pointer deleted – TYPE:
‘type name’
S105
Invalid RELEASE Char pointer deleted – TYPE: ‘type
name’
S106
Invalid default RELEASE Char pointer deleted – TYPE:
‘type name’
S107
Invalid INITIATOR pointer deleted – TYPE: ‘type
name’
S108
Invalid default INITIATOR pointer deleted – TYPE:
‘type name’
S109
Invalid TERMINATOR pointer deleted – TYPE: ‘type
name’
S110
Invalid default TERMINATOR pointer deleted – TYPE:
‘type name’
S111
Resetting DELIMITER Use Count (was # now #) –
DELIMITER: ‘type name’
S112
Unused DESCRIPTION deleted: ‘type name’ (at index #)
S113
Invalid DESCRIPTION pointer deleted – TYPE: ‘type
name’
S114
Resetting DESCRIPTION Use Count (was # now #) –
DESCRIPTION: ‘type name’
S115
Invalid Floating Component TYPE pointer deleted –
TYPE: ‘type name’
S116
Invalid TYPE UsedInComp chain repaired – TYPE: ‘type
name’
Chapter 6 – Type Tree Analysis
Type Tree Analysis Structure Warning Messages
Return Code
Message
S117
Unused TYPE NAME deleted – TYPE NAME: ‘type name’
(at index #)
S119
Resetting TYPE NAME use count (was # now #) – TYPE
NAME: ‘type name’
S120
Repaired empty TYPE NAME WhereUsed chain – TYPE
NAME: ‘type name’
S121
Unused RESTRICTION NAME deleted: ‘type name’ (at
index #)
S122
Invalid RESTRICTION NAME deleted no DESCRIPTION was
available – TYPE: ‘type name’ .
S123
Invalid RESTRICTION NAME deleted DESCRIPTION was
‘type name’ – TYPE: ‘type name’
S124
Resetting RESTRICTION NAME Use Count (was # now #) –
RESTRICTIONS: ‘type name’
S125
Unused RESTRICTION DESCRIPTION deleted: ‘type name’
(at index #)
S126
Invalid RESTRICTION DESCRIPTION deleted – TYPE:
‘type name’
S127
Resetting RESTRICTION DESCRIPTION Use Count
(was # now #) – RESTRICTIONS: ‘type name’
S128
Unused RULE deleted: ‘type name’ (at index #)
S129
Invalid RULE pointer deleted – COMPONENT # of TYPE:
‘type name’
S130
Resetting RULE Use Count (was # now #) – RULE: ‘type
name’
S131
Invalid COMPONENT TYPE Description pointer –
COMPONENT #
S132
COMPONENT marked ‘InUse’ found in Free Chain–
COMPONENT #
S135
COMPONENT in Free Chain referenced by a TYPE –
COMPONENT #
S136
COMPONENT recovered and added to Free Chain –
COMPONENT #
S137
TYPE in Free Chain referenced by another TYPE – TYPE
#
Chapter 6 – Type Tree Analysis
Type Tree Analysis Structure Warning Messages
Return Code
Message
S138
TYPE recovered and added to Free Chain – TYPE
X’%04X’
S139
TYPE marked ‘InUse’ but not referenced – TYPE #
S140
Referenced TYPE not marked ‘InUse’ – TYPE #
S141
TYPE Free Chain not in order: sorting
S142
COMPONENT Free Chain not in order: sorting
S143
Overlap found in LIST Free Chain
S144
Free Chain extends into unallocated region
S145
Overlap found in COMPONENT LIST SPACE: list cleared
COMPONENTS will be deleted
S146
Invalid COMPONENT LIST pointer: all COMPONENTS
DELETED – TYPE: ‘type name’
S147
Resetting COUNT in COMPONENT LIST: some COMPONENTS
may be lost
S148
RULE truncated (due to internal error): ‘type name’
(at index #)
S150
CATEGORY ‘type name’ was missing GROUP and/or ITEM
attributes
S151
GROUP ‘type name’ was missing GROUP attributes
S152
ITEM ‘type name’ was missing ITEM attributes
Chapter 7 – Type Tree Generation
This chapter discusses error and warning messages that result when generating a
type tree using the Type Tree Maker.
When the Type Tree Maker finds a problem with a command, it returns either an
error message or a warning message, depending on the severity of the problem.
These error and warning messages, viewable from the Type Tree Maker, are also
stored in the install_dir/ttmaker.log file.
The ttmaker.log file record contains the line number of the command that caused
the error or warning message, followed by a message. An example of a warning
message is Warning 34 at line 3: Overwrote existing type (and possible
subtree).
Type Tree Generation Error Messages
The error and warning messages are listed in the following tables. The hints show
some likely causes for the error message.
Note A general hint is to always check the spelling and syntax of the commands.
Message
Description
Command line too long
Correct the command line. The maximum
size of a command line is 4096 bytes.
Invalid syntax in command
line
Correct the command.
Cannot create type tree
A directory may not exist. All directory
names in the path must conform to 8.3
rules: a maximum of eight characters for
file name and a three-character extension.
Cannot set root type
The definition of the root type is incorrect.
Cannot set description
The type was not created properly.
Cannot set current type
(Type does not exist.)
The type was not created properly.
Return Codes and Error Messages Reference Guide
85
Chapter 7 – Type Tree Generation
Type Tree Generation Error Messages
Message
Description
Cannot create type (already
exists?)
The type cannot fit under the active type
(for example: a group cannot be placed
under an item), the active type name is too
long, or the number of types exceeds the
maximum number of types allowed in a
type tree.
Invalid reserved word
Check the command line and correct.
Memory failure
Close applications and run Type Tree Maker
again.
[ ] mismatch
Check the command line syntax and correct.
Cannot open type tree
The type tree file does not exist.
Cannot set type information
The type was not created properly.
Cannot set character
attributes
The active type is not a character item.
Cannot set binary
attributes
The active type is not a binary item.
Cannot set delimited format
The active type is not a delimited group.
Cannot set implied format
The active type is not an implied group.
Cannot add component
The active type is an item that cannot have
a component list.
User aborted
The user pressed Cancel.
Cannot set initiator
The type was not created properly.
Cannot set terminator
The type was not created properly.
Cannot set release
character
The type was not created properly.
Cannot delete restriction
list
The active type is not an item.
Cannot delete component
list
The active type is an item that cannot have
a component list.
Cannot add restriction
The active type is not an item. Only items
can have restrictions.
Cannot propagate
The type was not created properly.
Chapter 7 – Type Tree Generation
Type Tree Generation Error Messages
Message
Description
Cannot get type information
The type was not created properly.
Cannot get initiator
The type was not created properly.
Cannot get terminator
The type was not created properly.
Cannot get release
character
The type was not created properly.
Cannot get delimited format
The active type is not a delimited group.
Cannot get implied format
The active type is not an implied group.
Cannot get character
attributes
The active type is not a character item.
Cannot get binary
attributes
The active type is not a binary item.
Cannot replace type - class
of type is incorrect
The active type does not match the class.
Cannot get type name
The type was not created properly or the
path name was specified incorrectly.
Cannot get type information
to replace type
The type was not created properly.
Hex value is not valid
The valid Hex characters are 0-9 and A-F.
Cannot save type tree
specified in last NEWTREE=
command
The path name is invalid.
Component rule is invalid
Check the syntax of the component rule.
Cannot delete subtype
The type does not exist.
Analysis errors occurred
The tree did not analyze correctly.
Invalid file name specified
Check for invalid characters or the size of
the file name.
Invalid type name
Check the type name for reserved
characters or reserved words.
Overwrote existing type
(and possible subtree)
The type already existed in the tree and was
overwritten.
Chapter 7 – Type Tree Generation
Type Tree Generation Logic Warning Messages
Message
Description
Separator option has Find
set but no default
For the Separator option, you must specify
Default when you specify Find.
Analysis warnings occurred
The Type Tree Analyzer produced warnings.
Type Tree Generation Logic Warning Messages
The following messages are generated if you use the Type Tree Maker to create a
type tree. For more information about the Type Tree Maker, see the Type Tree
Maker Reference Guide.
Return Code
Message
L202
RESTRICTION list deleted: TYPE is not an ITEM –
TYPE: ‘type name’
Hint: Type class was changed from an item to a group or category,
so the restriction list was deleted. If this was not your intent,
change it back to the way it was.
L207
Root of TYPE Tree is not a CATEGORY – TYPE: ‘type
name’
L208
DELIMITER location not specified – TYPE: ‘type name’
L209
SYNTAX ERROR in COMPONENT RULE – COMPONENT # of
TYPE: ‘type name’
L210
TYPE created from an ITEM or a GROUP is a CATEGORY –
TYPE: ‘type name’
L211
TYPE created from an ITEM is a GROUP – TYPE: ‘type
name’
L212
TYPE created from a GROUP is an ITEM – TYPE: ‘type
name’
L213
Floating Component TYPE deleted because TYPE has an
Explicit format – TYPE: ‘type name’ (warning)
L214
Invalid ITEM presentation. Presentation set to
defaults – TYPE: ‘type name’ (warning)
Chapter 7 – Type Tree Generation
Type Tree Generation Logic Warning Messages
Return Code
Message
L215
DELIMITER length greater than maximum allowed in
TYPE: ‘type name’
Hint: Delimiters, initiators, and terminators are limited to 120
bytes.
L216
The Padded To length for item - ‘type name’ was less
than the maximum content size.
L217
Fixed TYPE - ‘type name’ must include white space or
have a terminator.
L218
RELEASE CHARACTER for TYPE - ‘type name’ must have a
value.
L219
INITIATOR for TYPE - ‘type name’ must have a value.
L220
TERMINATOR for TYPE - ‘type name’ must have a value.
L221
Name for TYPE - ‘type name’ contains reserved
characters. Please rename.
L222
DELIMITER for TYPE - ‘type name’ had no value. The
group format has been set to Implicit with No
syntax. (warning)
L223
No syntax item specified as DELIMITER for TYPE ‘type
name’
L224
No syntax item specified as RELEASE CHARACTER for
TYPE ‘type name’
L225
No syntax item specified as INITIATOR for TYPE ‘type
name’
L226
No syntax item specified as TERMINATOR for TYPE
‘type name’
L227
No syntax item specified as 1000’s separator for
TYPE ‘type name’
L228
No syntax item specified as decimal separator for
TYPE ‘type name’
L229
1000’s separator for TYPE ‘type name’ has no value
L230
Decimal separator for TYPE ‘type name’ has no value
L231
1000’s separator type neither inherited nor local
TYPE ‘type name’
Chapter 7 – Type Tree Generation
COBOL Copybook
Return Code
Message
L232
Default 1000’s separators not specified TYPE ‘type
name’
L233
Default 1000’s separator not in restriction list
TYPE ‘type name’
L234
1000’s separator type is not a SYNTAX ITEM TYPE
‘type name’
L235
1000’s separator type has no restriction list TYPE
‘type name’
L236
Decimal separator type neither inherited nor local
TYPE ‘type name’
L237
Default separator type is not a SYNTAX ITEM TYPE
‘type name’
L238
Default decimal separator not in restriction list
TYPE ‘type name’
L239
Decimal separator type is not a SYNTAX ITEM TYPE
‘type name’
L240
Decimal separator type has no restriction list TYPE
‘type name’
COBOL Copybook
Error messages and return codes provide information on errors that occur while
generating type trees from COBOL Copybook data using the Importer Wizard.
If the COBOL copybook input file specified to the Importer Wizard contains
incorrect or invalid COBOL copybook statements, the Importer Wizard maps will
attempt to skip the erroneous statements and continue on with the next valid
statement. Invalid statements are reported in the COBOL Copybook Importer error
and warning report.
Trying to import a file that contains a large number of errors or is not a valid
COBOL copybook definition may result in the failure of the Importer Wizard to
create a type tree. When this situation occurs, the maps executed by the Importer
Wizard may report warning and error messages when you run the COBOL
Copybook importer wizard.
Chapter 7 – Type Tree Generation
COBOL Copybook
The following is a list of return codes and messages along with hints or
instructions for trying to resolve the problem:
Return Code
Message
Unable to rename …
An attempt may have been made to write to a read-only
directory, an output file directory may be missing, or there may
not be sufficient disk space on the output drive.
1
User aborted map
If you cancel execution before the map completes, this message
is displayed.
2
Not enough memory to execute map
Close other running applications and re-try
3
Could not open map
One of the map executable files (.mmc) cannot be found. Check
that the following four files are present in the install directory:
UnBlock.mmc, NormalizeCopyBook.mmc, TranslatFile.mmc,
BuildTTMakerScript.mmc
4
Could not read map
Contact Mercator Technical Support.
5
Could not read inputs
Contact Mercator Technical Support.
6
Invalid map handle
Contact Mercator Technical Support.
7
Invalid card number was specified
Your map may be corrupt. Contact Mercator Technical Support.
8
One or more inputs was invalid
Check to make sure a proper copybook input file was specified.
Chapter 7 – Type Tree Generation
Return Code
Message
9
Target not available
COBOL Copybook
This may be a security/authorization problem. Verify that you
have authorization for read access for the input copybook file and
write access for the specified output directory and the Mercator
install directory.
10
Internal error
Contact Mercator Technical Support.
11
Could not build one or more outputs
An attempt may have been made to write to a read-only
directory, an output file directory may be missing, or there may
not be sufficient disk space on the output drive.
12
Source not available
An incorrect file name or path for the copybook input file may
have been specified.
13
Could not open work files
There may not be sufficient disk space on the drive where the
install directory exists to create necessary importer work files.
15
Map must be recompiled
You may have an outdated version of the Importer maps versus
the installed version of the Command Server. Re-install the
correct version of the Importer.
16
Disk write error
An attempt may have been made to write to a read-only directory
or file. Also, check the amount of available disk space.
17
Disk read error
An attempt may have been made to access a file on a shared
resource that is not accessible. Also, check the amount of
available disk space.
18
Page usage count error
An internal paging problem exists. Contact Mercator Technical
Support.
19
Internal calling error
Contact Mercator Technical Support.
Chapter 7 – Type Tree Generation
Return Code
Message
20
Reopen file failed
COBOL Copybook
A map did not run correctly. Contact Mercator Technical Support.
21
Input valid but unknown data found
The input specified is likely not a valid copybook. Check to make
sure a proper copybook input file was specified.
22
Page size too small
Contact Mercator Technical Support.
28
Input type contains errors
Invalid copybook statement(s) were found in the specified input—
the COBOL Copybook Importer error report file should contain
details on the problem statement(s).
50
Type exists and is not overwritten
A duplicate definition was found in the .mts file. The COBOL
Copybook Importer uses the first definition found for a given field
or group name and ignores or warns about any duplicate names.
Chapter 8 – System Analysis
This chapter discusses error and warning messages that result from an analysis of
a system.
System Analyzer
The System Analyzer checks the internal consistency of your systems to assure
that they can be executed.
System Analysis Structure Error Messages
The following table lists the structure error messages that result from a structural
analysis of a system:
Return Code
Message
SE100
Map, name1, cannot be a component because system,
name2, is distributed.
A distributed system cannot have maps as components.
SE101
System, name1, contained in system, name2, must
have a server.
Each component of a distributed system must be distributed or
have a server assigned (i.e., the server for a component of a
distributed server cannot be "None").
SE102
System name has unresolved settings that must be
resolved – (error).
Unresolved settings must be resolved.
SE103
Wildcards are used in map source/target name, but
map will be run by Command Server - Map Component
name1, Card Name name2 (error).
Wildcards cannot be used in map source or target names if a
Command Server will execute the map.
Return Codes and Error Messages Reference Guide
94
Chapter 8 – System Analysis
System Analysis Structure Error Messages
Return Code
Message
SE104
Wildcards are used in directory name that is
specified in source/target name - Map Component
name1, Card Name name2 (error).
Directories cannot have wildcards in their names.
SE105
Wildcards are used in database source name – Map
Component name1, Card Name name2 (error).
A database source name cannot contain wildcards.
SE106
Wildcard must be used in at least one source
trigger because wildcards are defined for nontrigger sources and/or targets – Map Component name
(error).
If wildcards are used as sources and/or targets, at least one
source trigger must have a wildcard.
SE107
Question mark wildcard is used in a target name Map Component name1, Card Name name2 (error).
Question marks cannot be used in target names. A target name
can contain at most one asterisk.
SE108
Question mark wildcard is used in a source name
that is not a trigger - Map Component name1, Card
Name name2 (error).
Question marks cannot be used in sources that are not event
triggers. A source that is not an event trigger can contain at most
one asterisk.
SE109
Multiple wildcard characters are used in a source
trigger name, but other source triggers are defined
- Map Component name1 (error).
Multiple wildcards can be used in a source trigger name of a map
as long as there are no other source triggers.
SE110
More than one source trigger name contains a
wildcard character and the wildcard character used
is different - Map Component name1 (error).
If more than one source trigger name contains a wildcard, that
wildcard must be the same wildcard.
Chapter 8 – System Analysis
Return Code
Message
SE111
Wildcards are used in queue manager name and/or
queue name specified for WebSphere MQ name - Map
Component name1, Card Component name1 (error).
SE112
Source map component name references a non-existent
MMS file - (error).
Unresolved MMS reference by source map components must be
resolved.
SE113
Compiled map component name references a nonexistent MMC file – (error).
Unresolved MMC reference by compiled map components must be
resolved.
SE114
Subsystem component name references a non-existent
system - (error).
Unresolved system reference by subsystem components must be
resolved.
SE115
A system contains itself as a component – System
name1, Subsystem name2 (error).
A system cannot contain itself as a component.
SE116
Invalid source/target name – Map Component name1,
Card Name name2 (error).
Database, messaging and application adapters must have valid
source/target names as checked by the individual adapter.
SE117
Asterisk wildcard is used multiple times in a
target name – Map Component name1, Card Name name2
(error).
Only one wildcard per target name is permitted.
Chapter 8 – System Analysis
Systems Using Wildcards Analysis Structure Error Messages
Systems Using Wildcards Analysis Structure Error Messages
Wildcards can be used to specify a variable name for a source or target. The
asterisk and question mark characters are used according to the conditions
described in the SE103 thru SE110 error messages detailed in the System Analysis
Structure Error Messages section. The System Analyzer verifies that these
conditions are satisfied. If a condition is not satisfied, then it is flagged as an
error.
Return Code
Message
SE500
Map component name has no triggers. [Warning].
Maps that will be executed by an Event Server should have a
trigger, otherwise the map will never run.
SE501
System name has no components. [Warning].
A system should have at least one component.
SE502
Pseudo map component name1 exists in system name2.
[Warning].
Pseudo maps should be converted to source map components.
SE503
Triggers are defined for a map that will be
executed by a Command Server - Map Component name1.
[Warning].
Triggers should not be defined for a map that will be executed by
a Command Server.
SE504
The execution mode of system name does not match
the execution mode of subsystems that it contains.
[Warning].
The execution mode specified for a system should be the same as
the execution modes specified for its subsystems.
SE505
Drive letters should not be used in UNIX paths Map Component name1, Card Name name2. [Warning].
Drive letters should not be used in UNIX paths.
Index
A
B
adapters
MSMQ, 35
adapters
all, 16
Archive (Tar), 22
Archive (Zip), 24
Batch File, 25
BEA MessageQ, 26
BEA Tuxedo, 28
database, 17
DB2 (MVS (CL1)), 17
DB2 (MVS), 17
DB2 (Windows/UNIX), 17
E-mail, 30
FTP, 31
HTTP, 32
Informix, 17
Java Class, 34
JCA, 33
LDAP, 35
Microsoft SQL Server, 17
ODBC, 17
OLE DB, 17
Oracle, 17
Shell Script, 25
Sybase SQL Server, 17
adapters
Oracle8 AQ, 36
adapters
R/3, 38
adapters
SOAP, 42
adapters
TIB/Rendezvous release 5, 43
adapters
TIB/Rendezvous release 6 and TX, 44
adapters
WebSphere MQ, 45
adapters
XML Data, 46
Archive (Tar) adapter, 22
Archive (Zip) adapter, 24
audit log
error status codes, 61
valid status codes, 61
warning status codes, 61
Batch File adapter, 25
BEA MessageQ adapter, 26
BEA Tuxedo adapter, 28
C
COBOL Copybook
type tree generation messages, 90
D
database adapters, 17
DB2 (MVS (CL1)) adapter, 17
DB2 (MVS) adapter, 17
DB2 (Windows/UNIX)) adapter, 17
documentation
overview, 5
related references, 5
E
E-mail adapter, 30
environmental layer for UNIX, 12
error audit log status codes, 61
F
FTP adapter, 31
H
HTTP adapter, 32
I
Informix adapter, 17
J
Java Class, 34
JCA, 33
L
LDAP adapter, 35
logic errors
type tree analysis, 64
logic warnings
type tree analysis, 80
type tree generation, 88
M
map build
Return Codes and Error Messages Reference Guide
98
Index
O
errors, 52
warnings, 57
map compile errors, 57
map execution
errors and warnings, 47
warnings, 51
maps
audit log status codes, 61
error audit log status codes, 61
map build errors, 52
map build warnings, 57
map compile errors, 57
map execution errors and warnings, 47
map execution warnings, 51
messages, 47
valid audit log status codes, 61
warning audit log status codes, 61
MEJBADPI, 11
Mercator Enterprise JavaBean Adapter
Programming Interface, 11
Microsoft SQL Server adapter, 17
MSMQ adapter, 35
O
ODBC adapter, 17
OLE DB adapter, 17
Oracle adapter, 17
Oracle8 AQ adapter, 36
P
Platform API, 7
R
R/3 adapter, 38
RUN function, 7
S
Shell Script adapter, 25
SOAP adapter, 42
status codes for audit log
error, 61
valid, 61
warning, 61
structure errors
system analysis, 94
wildcards, 97
type tree analysis, 81
structure warnings
type tree analysis, 82
Sybase SQL Server adapter, 17
system analysis
structure errors, 94
wildcards, 97
System Analyzer, 94
T
TIB/Rendezvous release 5 adapter, 43
TIB/Rendezvous release 6 and TX adapters, 44
type tree analysis
logic errors, 64
logic warnings, 80
structure errors, 81
structure warnings, 82
Type Tree Analyzer, 63
type tree generation
COBOL Copybook, 90
errors, 85
logic warnings, 88
U
UNIX environmental layer, 12
V
valid audit log status codes, 61
W
warning audit log status codes, 61
WebSphere MQ adapter, 45
X
XML Data adapter, 46