BEA Logo BEA eLink Data Integration Option 1.3

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

  e-docs.beasys.com   |  Search   |  PDF Files   |  Contact  

 BEA eLink Data Integration Option Home |  Prev |  Next |  Table of Contents |


Error and Informational Messages

Error and Informational Messages

This document contains the following descriptions of error, informational, and warning messages that can be encountered while using the BEA eLink DIO component.


201


ERROR: Cannot open `<filename>' (errno=<os-errno-value> - `<os-errno-text>'



Description:

The specified Meta-Type Information file cannot be opened.



Action:

A Meta-Type Information file must exist and be located in the application directory identified by the APPDIR environment variable defined in the ubbconfig file (or the ENV file referenced in the ubbconfig file). Verify its presence and that `USER' has read permissions.



See Also:

None.


202


ERROR: Cannot restore type description from `<buffer-type>' (rc=<response-code>)'



Description:

The buffer's data type cannot be determined because its definition is not available. Refer to the supplemental code for details.



Action:

Examine the supplemental code and correct the problem.



See Also:

None.


203


ERROR: Cannot translate input FML data `(rc=<response-code>)'



Description:

FML data could not be translated into an internal format and made available to the Mercator mapping engine. Refer to the supplemental code for details.



Action:

Examine the supplemental code and correct the problem.



See Also:

None.


204


ERROR: Cannot open `<filename>' (APPDIR not set)



Description:

The specified Meta-Type Information file <filename> cannot be opened because the APPDIR environment variable is either not available or incorrectly initialized.



Action:

A Meta-Type Information file must exist and be located in the application directory identified by the APPDIR environment variable defined in the ubbconfig file (or the ENV file referenced in the ubbconfig file). Verify the definition of the APPDIR environment variable.



See Also:

None.


205


ERROR: Illegal buffer type `<buffer-type>' (tperrno=<tuxedo-errno-value> - `<tuxedo-errno-text>')



Description:

The buffer received by the eLink DIO service handler is not a TUXEDO buffer type.



Action:

Examine the TUXEDO error response code (tperror) along with its brief explanation text to determine the nature of the programming error. More detailed information may be available in the TUXEDO documentation.



See Also:

None.


206


ERROR: INTERNAL ERROR: Invalid parameters



Description:

The eLink DIO has reached an unexpected state and may possibly become unstable.



Action:

Contact Technical Support.



See Also:

None.


207


ERROR: Failure to map input buffer type `<buffer-type>' (rc=<response-code>)



Description:

The eLink DIO is unable to convert the input buffer specified as <buffer-type> into an internal byte stream. Refer to the supplemental code for details.



Action:

Examine the supplemental code and correct the problem.



See Also:

None


208


ERROR: Failure to map named (<field-name>) input buffer type `<buffer-type>' (rc=<response-code>)



Description:

The eLink DIO is unable to convert the input buffer whose <buffer-type> is specified by the named FML field <field-name> into an internal byte stream. Refer to the supplemental code for details.



Action:

Examine the supplemental code and correct the problem. <buffer-type> is displayed "<invalid-buffer-type>" if <field-name> is not found or out of range.



See Also:

None.


209


ERROR: Data mapping failure (rc=<merc-code> - `<merc-message-text>')



Description:

This is a general data mapping response diagnostic. <merc-code> and <merc-message-text> are detailed in the Mercator documentation.



Action:

Examine <merc-code> and <merc-message-text> for the cause of the failure and correct the problem.



See Also:

None.


210


ERROR: Invalid or missing control information (rc=<response-code>)



Description:

The control information in output record data is missing or contains one or more invalid values. It cannot be processed by the eLink DIO. Refer to the supplemental code for the cause.



Action:

The common cause for this failure is the value assigned to the FORMAT field of the Control information. Refer to this diagnostic code for details for correct assignment values.



See Also:

None.


212


ERROR: Failure to map output buffer, type not specified



Description:

The eLink DIO could not process the result received from the Mercator mapping engine because no output buffer is specified.



Action:

Specify an output buffer, either by using tpalloc(3) and sending this together with the request in the tpcall(3), or by defining it in the control information header in the output record type tree.



See Also:

None.


213


ERROR: Failure to map output byte stream to FML (rc=<response-code>)



Description:

The eLink DIO is unable to convert the output buffer from the internal byte stream received from the Mercator mapping engine.



Action:

Examine the supplemental code and correct the problem.



See Also:

None.


214


ERROR: Failure to map output byte stream to `<buffer-type>' (rc=<response-code>)



Description:

The eLink DIO is unable to convert the output buffer from the internal byte stream received from the Mercator mapping engine to the specified <buffer-type>.



Action:

Examine the supplemental code and correct the problem.



See Also:

None.


215


ERROR: Illegal buffer type `<buffer-type>'



Description:

The output buffer type is not one of the supported types and cannot be used to complete the mapping operation.



Action:

Refer to diagnostic 225 for a list of supported buffer types.



See Also:

None.


216


ERROR: Memory allocation error



Description:

A general memory allocation failure has occurred.



Action:

Call Technical Support.



See Also:

None.


217


WARN: Cannot load shared library `<filename>'



Description:

The eLink DIO cannot load its shared library. The eLink DIO uses a method in this library to obtain map execution status from the Mercator engine.



Action:

If this condition is not corrected, the eLink DIO reports successful engine status regardless of the actual operation status. This library is expected to be installed in the TUXEDO lib directory (UNIX installations) or bin directory (Windows NT installations).



See Also:

None.


218


WARN: Failed to find function in TUXEDO adapter



Description:

The eLink DIO cannot obtain its status reporting method from its shared library. The eLink DIO uses this method to obtain map execution status from the Mercator engine.



Action:

Contact Technical Support.



See Also:

None.


220


INFO: Translation server started



Description:

This diagnostic reports the ELINKDIO TUXEDO server is ready to service requests.



Action:

None.



See Also:

None.


222


ERROR: Missing `filename'



Description:

The Meta-Type Information disassembler requires the name of an existing Meta-Type Information file.



Action:

Repeat the command using the name of an existing Meta-Type Information file.



See Also:

None.


223


ERROR: Cannot restore type from `<filename>' (rc=<response-code>)



Description:

The Meta-Type Information disassembler is unable to disassemble <filename>. <response-code> indicates the nature of the failure.



Action:

Refer to the diagnostic <response-code> for a detailed reason.



See Also:

None.


224


INTERNAL ERROR: TUXEDO API failure (tperrno=<tuxedo-code> - `<tuxedo-message>')



Description:

The eLink DIO encountered a failure response from TUXEDO when performing the requested operation. The <tuxedo-code> is the numeric value of the diagnostic code. <tuxedo-message> is a brief description of the diagnostic response.



Action:

None.



See Also:

None.


225


ERROR: Illegal FORMAT value `<value>' specified in control header



Description:

The value of the FORMAT field of the control information in the output buffer is missing or out of range.



Action:

The possible values are "CARRAY" (or "C"), "STRING" (or "S"), "FML" (or "F") and "FMLV" (or "FV"). Correctly assign this field in the control information of the output buffer.



See Also:

None.


226


WARN: Cannot locate `<filename>' (TUXDIR not set)



Description:

The Adapter cannot load its shared library. The eLink DIO uses a method in this library to obtain map execution status from the Mercator engine.



Action:

If this condition is not corrected, the eLink DIO reports successful engine status regardless of the actual operation status. This library is expected to be installed in the TUXEDO lib directory (UNIX Installation) or bin directory (Windows NT installations).



See Also:

None.


227


INFO: Service servicename advertised



Description:

Service servicename has been advertised by TUXEDO.



Action:

None.



See Also:

None.


228


ERROR: Service servicename tpadvertise failed



Description:

An attempt to advertise Service servicename has failed.



Action:

Determine the cause of the failure and restart eLink DIO.



See Also:

None.


229


ERROR: Configuration file is required for ELINKDIO



Description:

The configuration file parameter was not specified or was specified incorrectly in the command line arguments for ELINKDIO server in the TUXEDO UBBCONFIG file.



Action:

Correct the UBBCONFIG file command line arguments for the ELINKDIO server and restart the ELINKDIO server.



See Also:

None.


230


ERROR: NOMTI option not allowed with the configuration file



Description:

The NOMTI parameter was specified in addition to an eLink DIO configuration file.



Action:

Remove the NOMTI parameter or the eLink DIO configuration file specification and restart the ELINKDIO server.



See Also:

None.


231


ERROR: Unable to open configuration file filename



Description:

An attempt to open configuration file filename failed.



Action:

Verify that the filename exists and that the file permissions allow for read access.



See Also:

None.


232


ERROR: Unable to locate SERVICE_LIST for server



Description:

The SERVICE_LIST parameter is not present in the SERVER section of the eLink DIO configuration file.



Action:

Add the SERVICE_LIST parameter to the SERVER section of the eLink DIO configuration file. Verify configuration file syntax.



See Also:

None.


233


ERROR: Service servicename not found



Description:

The SERVICE section of the eLink DIO configuration file for servicename is not found. The ELINKDIO server has tried to find a SERVICE section for one of the services listed in the SERVICE_LIST of the SERVER section of the eLink DIO configuration file and is unable to find it.



Action:

Verify that each service in the SERVICE_LIST in the SERVER section of the eLink DIO configuration file has a corresponding SERVICE section.



See Also:

None.


234


ERROR: Unable to open map file filename for service servicename



Description:

The ELINKDIO server has failed in an attempt to open the map file filename listed in the SERVICE section of the eLink DIO configuration file for servicename.



Action:

Verify the map file filename exists and that the filename permissions allow for read access.



See Also:

None.


235


ERROR: Unable to open mti file filename for servicename



Description:

The ELINKDIO server has failed in an attempt to open the MTI file filename listed in the SERVICE section of the eLink DIO configuration file for servicename.



Action:

Verify that the MTI file filename exists and that the filename permissions allow for read access.



See Also:

None.


236


ERROR: No FML32_VAL_FLD found for service servicename



Description:

The FML32_VAL_FLD parameter has not been specified for service servicename and a buffer type of FML32_VAL has been specified for servicename.



Action:

Verify that FML32_VAL is the correct buffer type. If so, add the FML32_VAL_FLD parameter to the SERVICE configuration to specify the field name of the FML32 field containing the input data.



See Also:

None.


237


ERROR: No MAP_FILE found for service servicename



Description:

A MAP_FILE parameter has not been found for service servicename in the eLink DIO configuration file.



Action:

Add the MAP_FILE parameter to the SERVICE section of the eLink DIO configuration file for service servicename.



See Also:

None.


238


ERROR: No BUFFER parameter specified for service servicename



Description:

A BUFFER parameter has not been found for service servicename in the eLink DIO configuration file.



Action:

Add the BUFFER parameter in the SERVICE section of the eLink DIO configuration file for service servicename.



See Also:

None.


239


ERROR: Configuration Load Failed rc=rcvalue



Description:

An attempt to load the configuration file failed, with return code rcvalue.



Action:

Determine the cause of the failure and restart eLink DIO.



See Also:

None.


240


ERROR: No MTI_FILE found for service servicename



Description:

A service servicename using the FML32 buffer type did not have an MTI_FILE specified in the configuration.



Action:

Correct the configuration file for this service.



See Also:

None.


241


ERROR: Invalid buffer type buffertype for service servicename



Description:

An invalid buffer type buffertype was specified for service servicename in the eLink DIO configuration file.



Action:

Verify that the buffer type for servicename is either FML32, FML32_VAL, CARRAY, or STRING.



See Also:

None.


242


ERROR: Unable to locate data for server



Description:

Unable to locate the SERVER section in the eLink DIO configuration file.



Action:

Verify the configuration file syntax and restart eLink DIO.



See Also:

None.


401


ERROR: Fieldname <name> not found in FML file



Description:

An FML Field name referenced in this FML Group Format file is not defined in the FML Field Definition File.



Action:

Provide field names in the FML Field Definition file.



See Also:

None.


402


ERROR: FieldName <name> has a different type from the FML file



Description:

The data type specified for the FML field is not the same as the data type in the FML Field Definition file.



Action:

Modify the information so that the field name and data type in the FML Field Definition file match.



See Also:

None.


403


ERROR: Fieldname <name> occurs multiple times in the FGF file



Description:

This field name occurs multiple times in the FGF file, it should occur only once.



Action:

Edit the FGF file so that the field name occurs only once.



See Also:

None.


404


ERROR: Cannot create MTI file (rc=<response-code>)



Description:

This error occurs when the Meta-Type Information file cannot be saved.



Action:

Check directory write permissions or disk space. If the error persists, contact Technical Support.



See Also:

None.


410


ERROR: Outermost GROUP in the FGF file must have exactly one occurrence



Description:

The outermost GROUP in the FGF file cannot have an OCCURS clause with any number other than 1.



Action:

Remove the OCCURS clause in the outermost group or set OCCURS=1.



See Also:

None.


411


ERROR: Found duplicate Group name <name> in FGF file



Description:

Group Names within FGF file must be unique.



Action:

Modify the group Names so that they are unique.



See Also:

None.


420


ERROR: Syntax Error at line <line number>



Description:

There is a syntax error in the FML group format file.



Action:

Correct the syntax and recompile. Some guidelines for correcting the syntax follow:



See Also:

Section "Creating an FML Group Format File" on page 5-2


3001


INTERNAL ERROR: Program argument value null



Description:

An eLink DIO contract has been violated; the eLink DIO may be in an unreliable state.



Action:

Contact Technical Support.



See Also:

None.


3002


INTERNAL ERROR: Type descriptor unreliable



Description:

Type descriptor reference unreliable.



Action:

Contact Technical Support.



See Also:

None.


3003


INTERNAL ERROR: Filename argument out of range



Description:

An eLink DIO contract has been violated; the eLink DIO may be in an unreliable state.



Action:

Contact Technical Support.



See Also:

None.


3004


ERROR: Cannot open file for read



Description:

The eLink DIO is unable to open a Meta-Type Information file for read access.



Action:

Verify this filename prefix matches the prefix of the corresponding Mercator map file. For example, if the name of the Mercator map file is ToCOBOL.mmc, then the filename for the corresponding Meta-Type Information file must be ToCOBOL.mti. This file must be located in the application's directory (APPDIR environment variable) and have appropriate read permissions.



See Also:

None.


3005


ERROR: Cannot open file for writing



Description:

The eLink DIO is unable to open a Meta-Type Information file for write access.



Action:

Verify the file access permissions of the application directory (APPDIR environment variable). Appropriate write permissions must be enabled.



See Also:

None.


3006


INTERNAL ERROR: Null persistence file pointer



Description:

An eLink DIO contract has been violated; the eLink DIO may be in an unreliable state.



Action:

Contact Technical Support.



See Also:

None.


3007


INTERNAL ERROR: Null member name argument



Description:

An eLink DIO contract has been violated; the eLink DIO may be in an unreliable state.



Action:

Contact Technical Support.



See Also:

None.


3008


ERROR: Field `<field-name>' not found



Description:

The FML buffer does not contain the field specified by <field-name>.



Action:

Verify the buffer data, Meta-Type Information and Mercator map files are correct for the requested operation. This will likely occur if either one of these files or the buffer are incorrect.



See Also:

None.


3009


ERROR: Field `<field-name>' missing matching value



Description:

The FML buffer does not contain the value for the field specified by <field-name>.



Action:

Correct the buffer initialization step and proceed.



See Also:

None.


3010


ERROR: Field `<field-name>' value not found



Description:

The FML buffer does not contain the value for the field specified by <field-name>.



Action:

Correct the buffer initialization step and proceed.



See Also:

None.


3011


INTERNAL ERROR: Unsafe copy



Description:

An eLink DIO contract has been violated; the eLink DIO may be in an unreliable state.



Action:

Contact Technical Support.



See Also:

None.


3012


ERROR: Failure reading Meta-Type Information



Description:

The Meta-Type Information file could not be read into process memory.



Action:

The Meta-Type Information file may have become corrupted, or possibly it is not a Meta-Type Information file. Verify and regenerate this file.



See Also:

None.


3013


ERROR: Cannot grow persistence file



Description:

The Meta-Type Information cannot be loaded into memory due to resource exhaustion.



Action:

Contact Technical Support.



See Also:

None.


3014


ERROR: Cannot allocate heap space for object persistence



Description:

This is a general memory allocation failure due to resource exhaustion.



Action:

Contact Technical Support.



See Also:

None.


3015


ERROR: Not a Meta-Type Information file



Description:

The eLink DIO does not recognize this file as a Meta-Type Information file.



Action:

The Meta-Type Information file may have become corrupted, or possibly it is not a Meta-Type Information file. Verify or regenerate this file.



See Also:

None.


3016


ERROR: Meta-Type Information file contents unreliable



Description:

The Meta-Type Information file contents could be read but not processed.



Action:

The Meta-Type Information file may have become corrupted, or possibly it is not a Meta-Type Information file at all. Verify or regenerate this file.



See Also:

None.


3017


INTERNAL ERROR: Program argument out of range



Description:

An eLink DIO contract has been violated; the eLink DIO may be in an unreliable state.



Action:

Contact Technical Support.



See Also:

None.


 [Table of Contents] [Prev] [Next]