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.
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.
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.................................................
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...........................................................
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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: .
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.
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.
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.
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 Fa
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
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 Er
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.
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
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.
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.
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.
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 mes
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.
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
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.
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.
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.
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.
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 res
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.
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
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.
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.
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.
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 them
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 g
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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’.
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’.
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.
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’
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’ .
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 C
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.
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.
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.
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.
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.
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 s
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.
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.
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.
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.
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.
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.
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.
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 ad
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
