Message Class 0020 - EntireX ACI - User Error in the API

This message class is returned when invalid arguments are specified in the API (ACI) or invalid EntireX Broker function sequences are issued. It is usually an error made by the application programmer. The situation can be examined using the error number returned. The messages have the format:

0020nnnn

where 0020 is the message class, and
nnnn is the message number in the range 0000 - 9999

Overview of Messages

00200004 | 00200006 | 00200031 | 00200044 | 00200047 | 00200048 | 00200052 | 00200070 | 00200094 | 00200098 | 00200134 | 00200149 | 00200181 | 00200182 | 00200183 | 00200184 | 00200185 | 00200186 | 00200187 | 00200188 | 00200189 | 00200190 | 00200191 | 00200192 | 00200193 | 00200194 | 00200195 | 00200199 | 00200200 | 00200203 | 00200208 | 00200210 | 00200211 | 00200212 | 00200216 | 00200218 | 00200226 | 00200228 | 00200229 | 00200252 | 00200267 | 00200268 | 00200302 | 00200311 | 00200312 | 00200314 | 00200335 | 00200336 | 00200362 | 00200371 | 00200372 | 00200377 | 00200379 | 00200380 | 00200400 | 00200401 | 00200419 | 00200420 | 00200421 | 00200422 | 00200424 | 00200449 | 00200450 | 00200451 | 00200452 | 00200453 | 00200454 | 00200478 | 00200482 | 00200505 | 00200532 | 00200533 | 00200538 | 00200539 | 00200540 | 00200563 | 00200566 | 00200573 | 00200574 | 00200613 | 00200614 | 00200639 | 00200781 | 00200782 | 00200786 | 00200787 | 00200788 | 00200789 | 00200790 | 00200801 | 00200816 | 00200901 | 00200906 | 00200908 | 00200911 | 00200912 | 00200924 | 00200941 | 00209400 | 00209401 | 00209402 | 00209403 | 00209404 | 00209405 | 00209406 | 00209407 | 00209410 | 00209413 | 00209416 | 00209417 | 00209418 | 00209419 | 00209420 | 00209421 | 00209422 | 00209423 | 00209424 | 00209450 | 00209451 | 00209452 | 00209453 | 00209454 | 00209455 | 00209456 | 00209457

00200004 API: No Function Possible After EOC
Explanation

The user has tried to access a conversation after finishing it with a previous EOC call.

Action

This is a user error. Perhaps an invalid conversation ID was specified. Check the program and correct the error.


00200006 API: Last Message Not Found
Explanation

This response is given to a RECEIVE call with OPTION=LAST when no data/messages have yet been received. It is not possible to look at the last message if you have not read the first one.

Action

This is a user error. Check the program and correct the error.


00200031 API: Invalid value for :1:
Explanation

This response is given when invalid values for the WAIT or UWTIME or UWSTATP-ADDER fields of the API are specified (for example, non-digits are given or the last character is not one of the valid time units S,M,H).

Action

This is a user error. Check the value for the field in the API of your program.


00200044 API: Invalid error buffer ptr or length
Explanation

The user has set the errtext_length in the Broker control block but has not provided an error buffer.

Action

This is a user error. The user should either provide an error buffer or set the errtext_length to 0.


00200047 API: QUIESCE invalid for Attach Manager
Explanation

Because a service registered with the option ATTACH does not run normal conversations, the DEREGISTER cannot wait for them to finish. In fact, the attachable service is no longer attachable after the DEREGISTER.

Action

Do not use the DEREGISTER option QUIESCE for services that are registered as attach manager (option ATTACH).


00200048 API: Already registered with ATTACH
Explanation

An application can register a service either with the option ATTACH or as a normal server (without option ATTACH). The error occurs when an application attempts to do both.

Action

Do not try to register a single server as an attach manager and as a normal server simultaneously.


00200052 API: Already registered without ATTACH
Explanation

An application can register a service either with the option ATTACH, or as a normal server (without option ATTACH). The error occurs when an application attempts to do both.

Action

Do not try to register a single server as a normal service and as an attach manager simultaneously.


00200070 Unknown host
Explanation

BROKER-ID contains an unknown host.

Action

Enter valid host in BROKER-ID.


00200094 API: MSG Truncated To Fit Receive-Buffer
Explanation

The data/message retrieved is larger than the supplied receive buffer. The data/message has been truncated to the actual length given in RECEIVE-LENGTH field of the API if API version 2 or above is used.

Action

See Error Cases for information on how to respond to this error code.


00200098 API: Function not possible if LOGON only
Explanation

The performed function is not valid if only a LOGON call has been performed. This applies to a RECEIVE, DEREGISTER or EOC function. They are not allowed right after a LOGON call.

Action

Do not perform the listed function right after a LOGON. Perform a REGISTER before running the DEREGISTER, perform a SEND or a RECEIVE before running an EOC and accept or establish a conversation before running a RECEIVE.


00200134 LOGON required
Explanation

If AUTOLOGON=NO is defined in the attribute file, all participant applications must perform a LOGON call as the very first Broker call and a LOGOFF call when they have finished communicating with the Broker. If the user is using UOW, clients and servers must do a LOGON. If AUTOLOGON=YES and a LOGON is not done, this error will occur when a SEND with OPTION=SYNC is done. See AUTOLOGON under Broker-specific Broker Attributes.

Action

Make LOGON the very first call and LOGOFF the last call. If necessary, define the attribute AUTOLOGON=YES in order to support automatic LOGON. However, the recommended definition is to force an explicit LOGON call.


00200149 No Error Text
Explanation

The broker stub was unable to initialize the environment.

  • Under z/OS, the EXX load library was not concatenated to the STEPLIB chain.

  • Under BS2000, the EXX load library was not assigned to LINK-NAME ETBLIB.

Action

Depends on the operating system:


00200181 API: Invalid User-ID
Explanation

The value for the USER-ID field of the API is missing. The USER-ID is a mandatory parameter.

Action

This is a user error. Check the value for the USER-ID field in the API of your program.


00200182 API: Invalid Function
Explanation

The value for the FUNCTION field of the API is invalid.

Action

This is a user error. Check the value for the FUNCTION field in the API of your program.


00200183 API: Invalid CLASS/NAME/SERVICE
Explanation

The service is missing or invalid in a broker call that requires a service, that is, a REGISTER/DEREGISTER or a SEND/RECEIVE/EOC call with no CONV-ID specified.

Action

This is a user error. Make sure that at least one of the following fields has been provided: SERVER-CLASS, SERVER-NAME or SERVICE. Together, these fields define the service.


00200184 API: Invalid SEND-LENGTH
Explanation

The value for the SEND-LENGTH field of the API is missing.

Action

This is a user error. A SEND call always requires a send-length. Check the program and correct the error.


00200185 API: Invalid FUNCTION/CONVID Combination
Explanation

The value for the CONV-ID field of the API is invalid, missing, or invalid in combination with the desired function.

Action

This is a user error. A SEND/RECEIVE/EOC/UNDO call requires a valid value for the CONV-ID (CID) field. Check the program and correct the error.


00200186 API: Char '.'or',' not allowed in ACI CB
Explanation

The character fields within the EntireX Broker ACI must not contain the metacharacter '.' or ','. These characters are used as special characters in the communication protocol between the Broker stub and the Broker.

Action

Correct the wrong character in the EntireX Broker ACI.


00200187 API: Invalid FUNCTION/OPTION Combination
Explanation

The FUNCTION / OPTION combination is invalid.

Action

This is a user error. Check the value for the OPTION field in conjunction with the FUNCTION field in the API of your program and correct the error.


00200188 API: Invalid Option
Explanation

The OPTION field of the API contains an unknown value.

Action

This is a user error. Check the value for the OPTION field in the API of your program and correct the error.


00200189 API: Invalid RECEIVE-LENGTH
Explanation

The value for the RECEIVE-LENGTH field of the API is missing. RECEIVE calls and blocked SEND calls always require a valid RECEIVE-LENGTH.

Action

This is a user error. Check the program and correct the error.


00200190 API: Invalid Cmd/Info Services Version
Explanation

The EntireX Broker kernel does not recognize the Command and Information Services API version requested.

Action

This is a user error. Check the following:

  • If you are using ETBINFO, ETBCMD or any other Software AG-provided Command and Information Services application: Check that the version of ETBINFO or ETBCMD is the same or earlier than the version of the Broker kernel.

  • If you are using your own Command and Information Services application: verify that the Command and Information Services API version will work with the version of EntireX. The following table shows the maximum CIS API version for the respective version of EntireX:

    Broker/EntireX Version Max. CIS API Version
    ETB 1 or ETB 2 1
    EXX 3, 4, 5, 6 2
    EXX 7.1 3
    EXX 7.2 4
    EXX 7.3 5
    EXX 8.0 or 8.1 6
    EXX 8.2 7
    EXX 9.0, 9.5, 9.6, 9.7, 9.9 8
    EXX 9.10, 9.12 9
    EXX 10.1, 10.3 10
    EXX 10.5 11
    EXX 10.7, 10.8, 10.9 12
  • A possible cause for this error is a SEND-LENGTH that is too short. Increase this value if necessary.


00200191 API: Invalid OPTION/CONV-ID Combination
Explanation

The OPTION / CONV-ID combination in the API is invalid. For example, a SEND was issued with OPTION=EOC and CONV-ID=NONE, or a RECEIVE with OPTION=LAST and no specific conversation ID (CONV-ID) was given.

Action

This is a user error. Check the program and correct the error.


00200192 API: Invalid parameter count
Explanation

More than four pointers have been supplied in the parameter list used to call the broker stub.

Action

Correct the program. A maximum of four pointers can be supplied.


00200193 API: Invalid FUNCTION/WAIT Combination
Explanation

The FUNCTION / WAIT combination in the API is invalid. A WAIT value in the API can be specified for the SEND, RECEIVE and RECEIVE_PUBLICATION functions only.

Action

This is a user error. Check the program and correct the error.


00200194 API: Invalid OPTION/WAIT Combination
Explanation

The OPTION / WAIT combination in the API is invalid, that is, a SEND with OPTION=EOC, HOLD or SYNC, or a RECEIVE with OPTION=LAST was issued.

Action

This is a user error. Check the program and correct the error.


00200195 API: Deregister not allowed from clients
Explanation

This response is given when a client tries to issue a deregister call to EntireX Broker.

Action

Do not issue a DEREGISTER call for clients. Check the program and correct the error.


00200199 API: Receive/CID=ANY Invalid For Clients
Explanation

A client issued a RECEIVE call for new conversations.

Action

This is a user error. Clients cannot issue a RECEIVE with CONV-ID=ANY because a RECEIVE with CONV-ID=ANY must be preceded by a REGISTER call. Check the program and correct the error.


00200200 API: RECEIVE/CID=NEW Invalid For Clients
Explanation

A client has issued a RECEIVE call for new conversations.

Action

This is a user error. Clients cannot issue a RECEIVE with CONV-ID=NEW because a RECEIVE with CONV-ID=NEW must be preceded by a REGISTER call. Check the program and correct the error.


00200203 API: No RECEIVE -BUFFER Address
Explanation

The address of the receive buffer is missing for the Broker call. That is, a RECEIVE or a blocked SEND was issued without the receive buffer address.

Action

This is a user error. Check the program and correct the error.


00200208 API: Invalid version number
Explanation

One of the following errors occurred: Invalid API-TYPE or API-VERSION supplied by user when calling the broker stub. Invalid version supplied by user in internal control blocks when calling the broker stub. Broker detected an invalid or unsupported prefix version specified by stub. Broker does not support the API-VERSION supplied by user.

Action

This is a user error. Check version of broker stubs and broker kernel. Determine the stub version by using function FCT_VERSION. Determine the kernel version by using function FCT_KERNELVERS. Correct API-TYPE or API-VERSION in the Broker control block.


00200210 API: No Send Buffer Address
Explanation

A SEND was issued without the send buffer address. Therefore, no address is given to the broker stub as the second parameter.

Action

This is a user error. Check the program and correct the error.


00200211 API: No API Control Block Address
Explanation

The ACI control block is missing for the call. No address is given to the broker stub as the first parameter.

Action

This is a user error. Check the program and correct the error.


00200212 API: (*) In SN/SC/SV Invalid For Function
Explanation

The FUNCTION / SERVICE combination provided by the SERVER-CLASS, SERVER-NAME, and SERVICE fields of the API is invalid. That is, a SEND function is used with an asterisk (*) in any of the SERVICE fields.

Action

This is a user error. Check the program and correct the error.


00200216 API: Invalid BROKER-ID
Explanation

The BROKER-ID field in the API does not contain a valid numeric node ID.

Action

The BROKER-ID in the API should be the same as the BROKER-ID in the Broker attribute file.


00200218 SEND/RECV-LEN :1: exceeds max (:2:)
Explanation

The maximum length possible for the send buffer/receive buffer depends on the Broker API version and the transport method (TCP/IP or Entire Net-Work) used, and on the configuration of the EntireX Broker.

  • :1: is replaced by the current message length requested in bytes.

  • :2: is replaced by an extended reason description for the length. See Action below for list of reasons.

Action

Check the API version and the transport method (TCP/IP or Entire Net-Work) used, and the possible maximum length of send buffer/receive buffer for the transport method. See the field SEND-LENGTH of the Broker ACI control block. See SEND-LENGTH under Broker ACI Fields. Additional actions depend on the extended reason description:

  • 'MAX-MESSAGE-LENGTH exceeded': Check the Broker attribute MAX-MESSAGE-LENGTH. See MAX-MESSAGE-LENGTH under Broker-specific Broker Attributes.

  • 'IUBL or NABS exceeded': Check the Broker attributes NABS and IUBL. See NABS and IUBL under NET-specific Broker Attributes.

  • 'No ACBX support': Check the Broker attribute EXTENDED-ACB-SUPPORT is set to 'YES' to allow buffers greater than 32 KB to be transmitted. See EXTENDED-ACB-SUPPORT under NET-specific Broker Attributes.

  • 'APIV1 max 32K': API version 1 does not support messages greater than 32 KB. Use a higher ACI API.


00200226 API Invalid STATUS
Explanation

The Broker has returned an invalid status.

Action

Contact Software AG Support.


00200228 API Invalid CONV-STAT
Explanation

The Broker has returned an invalid conversation status.

Action

Contact Software AG Support.


00200229 API Invalid value for STORE
Explanation

There are two possible error sources:

  1. The application has supplied an invalid value for STORE in the Broker ACI control block. See STORE under Broker ACI Fields.

  2. The Broker has returned an invalid value for STORE from the kernel.

Action

In situation 1, ensure that the application assigns only a valid value to the field.

In situation 2, contact Software AG Support.


00200252 CID=NONE required for this service
Explanation

The application tried to start a conversation when issuing an EntireX Broker command operation. The internal service should be used in non-conversational mode only (CID=NONE).

Action

Change your code.


00200267 API: CID=NEW required for this service
Explanation

An INFO service request has been started with CID not equal NEW. Because INFO services are conversational, a new conversation must be started with every initial SEND command. The returning information can be spread across several messages which must be received separately.

Action

Always send INFO requests with CID=NEW.


00200268 API: REGISTER internal service rejected
Explanation

The service that you specified is already registered as an internal service. All service definitions with the class SAG are reserved.

Action

Choose another service name


00200302 EOC error: must back out unit of work
Explanation

EOC commands are not allowed while a UOW is being built.

Action

Do not issue an EOC command before a UOW is committed. This message is for diagnostic purposes only.


00200311 API: Invalid Numeric Field
Explanation

The API field must be numeric.

Action

Correct the field value.


00200312 API: Out of Range
Explanation

The value of a field is incorrect.

Action

Correct the field value.


00200314 API: UOW status invalid
Explanation

Returned status of UOW is not valid.

Action

Check the CONVID and UOWID in the Broker control block.


00200335 No Mixed Message with UOW on the Same CONVID
Explanation

You cannot have UOW and non-UOW messages in the same conversation, that is, the same CONVID.

Action

Check the application and correct the error.


00200336 No Mixed UOW with MSG on the Same CONVID
Explanation

You cannot have UOW and non-UOW messages in the same conversation, that is, the same CONVID.

Action

Check the application and correct the error.


00200362 API: Broker Stub De-Initialized
Explanation

The Broker stub was initialized but had to be de-initialized because none of the shared library pointers (TCP or ADALNK) was available.

Action

Check for any serious errors that may have caused library cleanup.


00200371 API: Cannot Specify arch w/o codepage
Explanation

You cannot specify a DATA-ARCH to which a codepage applies without also specifying the codepage itself, using LOCALE-STRING.

Action

Check the application and correct the error.


00200372 API: Error converting locale to codepage
Explanation

The locale string sent by a client/server component could not be mapped to a codepage by the broker's built-in locale string mapping. See Broker's Built-in Locale String Mapping.

Action

Identify the locale string that could not be mapped to a codepage. The value of the LS keyword (LS=locale-string) in the broker trace may be helpful in identifying the erroneous locale string. Use a valid locale string or define a new mapping in the broker attribute file. See the relevant attribute under locale-string for information on how to customize the mapping of locale strings to codepages.


00200377 API: Character Conversion Overflow
Explanation

The data/message retrieved after character conversion is larger than the supplied receive buffer. Conversion can increase the amount of your data. No data is provided in the receive buffer. The minimum buffer length required to receive the converted data is returned in the RETURN-LENGTH field of the API if API version 2 or above is used. The client or server should reread the message using a larger buffer with the required length.

Action

For RPC components, the error can be ignored because the reread of the message is handled inside the RPC layer.
Exception: for older Natural RPC versions you may need to increase the MAX-BUFF parameter.

For ACI programming, see Error Cases for information on how to respond to this error code.


00200379 API: Inconsistent security installation
Explanation

The setting for security in the Broker kernel is different from the settings in one or more of the Broker stubs. Either the Broker kernel and all stubs must be configured to operate with security, or the kernel and all stubs must be configured to operate without security.

For ACI version 8 and above, this error can be caused by an application not setting the correct value of KERNELSECURITY in the EntireX Broker control block field; see KERNELSECURITY under Broker ACI Fields. The correct value is set automatically by the KERNELVERS command and this value must be maintained in the EntireX Broker control block field. If the application is unable or unwilling to perform the KERNELVERS command, configure the stub so that the security setting is consistent with the Broker kernel. See KERNELVERS under Broker ACI Functions and also EntireX Security.

Action

Ensure the security settings are consistent for Broker kernel and all the stubs.


00200380 Some Characters Could not Be Converted
Explanation

When receiving a message, the Broker's CONVERSION exit determined that at least one character in the incoming message had no equivalent in the receiver's character set. The possibilities for this incomplete conversion:

  • The sender's message contained a data value with no corresponding character in the sender's character set.

  • All the sender's characters are valid, but at least one of them has no corresponding character in the receiver's character set.

If this condition occurs, the application should consider the received data to be potentially incomplete or missing.

Action

Ensure that both sender and receiver are using the correct locale string and that all character values being sent have a corresponding character in the receiver's character set.


00200400 Invalid SSL parameter specified
Explanation

The Broker ACI call FCT_SETSSLPARMS failed due to invalid specifications.

Action

Check the 2nd parameter of this broker call and the length specified in the Broker ACI control block.


00200401 Invalid value specified for EL
Explanation

Only values of 0, 1 or 2 are valid encryption levels.

Action

Correct the setting in the Broker ACI control block.

Note:
For encrypted transport we strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.


00200419 Mismatch of EL and current encryption
Explanation

An inconsistency has been detected. The actual security setting to encrypt the payload buffer does not match the specification of the EL parameter in the current broker call.

Action

Verify the EL parameter in the Broker ACI control block and/or verify the correct installation of the security exit.

Note:
For encrypted transport we strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.


00200420 Mismatch of client encryption and ATTR
Explanation

The encryption settings of the EntireX client program do not match the settings in the Broker attribute file.

Action

Check the ENCRYPTION-LEVEL specification in the Broker attribute file and adapt the settings to your client program (with respect to the security setting and/or the EL parameter).

Note:
For encrypted transport we strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.


00200421 Mismatch of server encryption and ATTR
Explanation

For servers with API version below 6, a mismatch was found between the current security settings and the ENCRYPTION-LEVEL specification in the Broker attribute file.

Action

Change the security settings:

  • Activate / deactivate the security exit on the server side, or

  • Amend the ENCRYPTION-LEVEL specification for this service in the Broker attribute file.

Note:
For encrypted transport we strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.


00200422 Server EL and ATTR not identical
Explanation

For servers with API version 6 or above, the setting of EL and the specification for ENCRYPTION-LEVEL in the Broker attribute file is not identical.

Action

Either

  • Correct the EL parameter (and security setting) in the server program, or

  • Change the ENCRYPTION-LEVEL for this service in the Broker attribute file.

Note:
For encrypted transport we strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.


00200424 SETSSLPARMS only valid for transport=SSL
Explanation

ACI function FCT_SETSSLPARMS was set for a non-SSL Broker connection.

Action

Either change the BROKER-ID to use SSL or do not issue the ACI function FCT_SETSSLPARMS.


00200449 API: Invalid Compress option
Explanation

Compression is supported, but an invalid option was specified.

Action

Correct the compress option.


00200450 Error during data compression
Explanation

Compression of the data was attempted, but resulting size was equal to or greater than original data.

Action

The compress option is turned OFF for this transmission of data; data will not be compressed.


00200451 Error during data decompression
Explanation

Failure occurred during a decompress operation. The most likely cause is insufficient memory for the process.

Action

Increase available memory for process, if possible.


00200452 Unexpected error during comp/decomp
Explanation

Error resulted from a compress or decompress operation, and is not accounted for by errors 0450 or 0451.

Action

Save trace information. Contact Software AG Support.


00200453 Decompressed data corrupt
Explanation

When decompressing a compressed data stream, the integrity of the data was compromised.

Action

Save trace and data. Contact Software AG Support.


00200454 API: Compression is not available
Explanation

Compression was requested but is not available

Action

Retry the operation without compression.


00200478 EOC Error: Still Unread Unit of Work
Explanation

Participant issues the function EOC, but unprocessed UOWs exist for the conversation. The EOC request is rejected.

Action

Read the unprocessed UOWs first and issue function EOC afterwards.


00200482 API: CONV-ID NONE not supported
Explanation

Value NONE is not supported for the requested EntireX Broker function.

Action

Correct application.


00200505 Illegal operation due to wrong UOW type
Explanation

The specified UOWID does not contain a unit of work

Action

Correct the UOWID.


00200532 API: Error code missing in REPLY-ERROR
Explanation

Stub application did not provide a numeric value in the ERROR-CODE field in Broker control block while making a REPLY_ERROR function call.

Action

Send a valid numeric value in the ERROR-CODE field of the Broker control block.


00200533 API: Invalid error code in REPLY-ERROR
Explanation

Stub application provided an invalid error code in the Broker control block, while making REPLY_ERROR function call. User-defined error codes should not begin with number 8, and should contain only numeric values.

Action

Make sure that error code in the Broker control block does not start with '8' and contains only numerals.


00200538 API: Specify locale to do CONVERSION
Explanation

Receiving application did not provide its codepage information in LOCALE-STRING field of the Broker control block.

Action

Supply codepage information in the LOCALE-STRING field of the Broker control block. If you want the Broker to supply default codepage information, specify MAP=YES in CONVERSION attribute. See CONVERSION under Service-specific Broker Attributes.


00200539 API: Sender did not specify locale info
Explanation

Sender application did not provide codepage information in LOCALE-STRING field of the Broker control block.

Action

Supply codepage information in the LOCALE-STRING field of the Broker control block. If you want the Broker to supply default codepage information, specify MAP=YES in CONVERSION attribute. See CONVERSION under Service-specific Broker Attributes.


00200540 API: :1: value truncated
Explanation

The value for RETURN-LENGTH was truncated. This occurs if the value is greater than 99,999,999 and ACI version 8 or below is used.

Action

Upgrade to ACI version 9 or above.


00200563 DEREGISTER not completed due to UOWs
Explanation

There are still open units of work that have not been committed, cancelled, or backed out yet. The ACI function DEREGISTER was not completed successfully.

Action

Finish the open units of work first before calling DEREGISTER.


00200566 API: Invalid value for COMPRESSION TYPE
Explanation

The supplied value is invalid. Broker supports compression types GZIP and ZLIB.

Action

Correct the program to supply a valid value.


00200573 API: Invalid EXTENSION-SEND-LENGTH
Explanation

An invalid extension send length was specified.

Action

Enter a vaild extension send length value.


00200574 API: Invalid EXTENSION-RECEIVE-LENGTH
Explanation

An invalid extension receive length was specified.

Action

Enter a vaild extension receive length value.


00200613 API: Filter already active
Explanation

Command and Information Services were unable to add a command log filter as the specified filter was already active.

Action

Specify a filter that is not already active.


00200614 API: Filter not found
Explanation

Command and Information Services were unable to delete a command log filter as the specified filter did not exist.

Action

Specify a filter that does exist.


00200639 API: Protected UOWID has been specified
Explanation

An application has specified a protected unit of work ID in an API request. Protected unit of work IDs are 0000000000000000 and 0000000000000001.

Action

Specify a non-protected unit of work ID.


00200781 <sc/sn/sv> already registered with CONVERSION=SAGTRPC
Explanation

A mixture of ACI and RPC communication using the same broker service (CLASS, SERVER and SERVICE) was detected.

Action

Use either RPC-based Components or ACI-based Programming.


00200782 <sc/sn/sv> already registered with CONVERSION=SAGTCHA.
Explanation

A mixture of ACI and RPC communication using the same broker service (CLASS, SERVER and SERVICE) was detected.

Action

Use either RPC-based Components or ACI-based Programming.


00200786 CONVERSION=SAGTRPC ignored. CONVERSION=SAGTCHA used.
Explanation

An incorrect character conversion configuration for a broker service (CLASS, SERVER and SERVICE) was detected and corrected. The broker service is logged in the preceding message.

Action

Correct the Broker attribute file. See Broker's Mechanism for Choosing the Character Conversion Approach under Introduction to Internationalization.


00200787 CONVERSION=SAGTCHA ignored. CONVERSION=SAGTRPC used.
Explanation

An incorrect character conversion configuration for a broker service (CLASS, SERVER and SERVICE) was detected and corrected. The broker service is logged in the preceding message.

Action

Correct the Broker attribute file. See Broker's Mechanism for Choosing the Character Conversion Approach under Introduction to Internationalization.


00200788 CONVERSION=NO,TRANSLATION=NO ignored. CONVERSION=SAGTRPC used.
Explanation

An incorrect character conversion configuration for a broker service (CLASS, SERVER and SERVICE) was detected and corrected. The broker service is logged in the preceding message.

Action

Correct the Broker attribute file. See Broker's Mechanism for Choosing the Character Conversion Approach under Introduction to Internationalization.


00200789 TRANSLATION=SAGTCHA ignored. CONVERSION=SAGTRPC used.
Explanation

An incorrect character conversion configuration for a broker service (CLASS, SERVER and SERVICE) was detected and corrected. The broker service is logged in the preceding message.

Action

Correct the Broker attribute file. See Broker's Mechanism for Choosing the Character Conversion Approach under Introduction to Internationalization.


00200790 TRANSLATION=SAGTCHA ignored. CONVERSION=SAGTCHA used.
Explanation

An incorrect character conversion configuration for a broker service (CLASS, SERVER and SERVICE) was detected and corrected. The broker service is logged in the preceding message.

Action

Correct the Broker attribute file. See Broker's Mechanism for Choosing the Character Conversion Approach under Introduction to Internationalization.


00200801 Unsecure shutdown broker not allowed
Explanation

The user is not authorized to shut down EntireX Broker.

Action

A security violation has occurred. This message and the related user ID are written to the Broker log.


00200816 API: Invalid Data Collector Call
Explanation

The stub was unable to issue the send request to the data collector.

Action

Rerun the application with stub log and check the messages when this error occurs. If the cause cannot be determined, contact Software AG Support.


00200901 User did not request SINGLE-CONV-MODE
Explanation

A mismatch was detected between settings of service and user regarding the mode chosen to send or receive ARF data. The single conversation mode (one conversation per service) has to be requested by the user before sending or receiving ARF data. It is not possible to change the mode if there are still conversations active that have been created with the old mode.

Action

ARF can be configured to use or not to use the ETBSCONV feature (single conversation mode). We strongly recommend using this feature, but it requires a service without any conversations created with the old mode. If the ETBSCONV feature was specified and conversations still exist, these conversations have to be consumed before you change to single conversation mode.


00200906 Value starts with an invalid character
Explanation

A blank has been deteced as the first character of SERVER-CLASS, SERVER-NAME or SERVICE.

Action

Correct the value and retry.


00200908 ARF SOURCE/TARGET Same USER-ID and TOKEN
Explanation

This indicates a configuration problem with ARF. Adabas Event Replication provides parameters DETBUSERID and DETBTOKEN to define USER-ID/TOKEN of the source side and parameters IQETBUSERID and IQETBTOKEN to define USER-ID/TOKEN of the target side. The source side of the Adabas Event Replication is using the same USER-ID/TOKEN pair as the target side, but source and target side must use different and unique USER-ID/TOKEN pairs.

Action

Define different USER-ID/TOKEN pairs for the source and the target side of the Adabas Event Replication.


00200911 ARF SEND Mismatching USER-ID and TOKEN
Explanation

This indicates a configuration problem with ARF. Adabas Event Replication provides parameters DETBUSERID and DETBTOKEN to define USER-ID/TOKEN of the source side. This source side of the Replication is using a new USER-ID/TOKEN pair now but this is not allowed as long as an active conversation exists.

Action

Revert the configuration to the previously defined values of USER-ID/TOKEN.


00200912 ARF RECV Mismatching USER-ID and TOKEN
Explanation

This indicates a configuration problem with ARF. Adabas Event Replication provides parameters IQETBUSERID and IQETBTOKEN to define USER-ID/TOKEN of the target side. This target side of the Replication is using a new USER-ID/TOKEN pair now but this is not allowed as long as an active conversation exists.

Action

Revert the configuration to the previously defined values of USER-ID/TOKEN.


00200924 STUB: TCB mode required
Explanation

The stub is running in SRB mode but needs to execute functionality that requires TCB mode.

Action

Contact Software AG Support.


00200941 STUB: TCP/IP not permitted
Explanation

The stub does not support the requested TCP/IP transport.

Action

Change transport type to NET.


00209400 FUNCTION NOT SUPPORTED
Explanation

An unsupported function (UNDO or DELETE) has been issued.

Action

Check the program and correct the error.


00209401 CONV-ID VALUE NOT SUPPORTED
Explanation

An unsupported value has been specified for the CONV-ID field.

Action

This is a user error. Check the program and correct the error.


00209402 WAIT VALUE NOT SUPPORTED
Explanation

An unsupported value has been specified for the WAIT operand.

Action

This is a user error. Check the program and correct the error.


00209403 OPTION NOT SUPPORTED
Explanation

An unsupported value has been specified for the OPTION field.

Action

This is a user error. Check the program and correct the error.


00209404 :1: - ADAPTER ERROR
Explanation

An error has occurred in the EntireX Broker Services protocol adapter. Depending on the protocol in use, it may be an SNA sense code or an MQM reason code.

Action

Obtain the error code from the first 8 bytes of the error message (:1:) or the ADAPTER-ERROR field. Then refer to the appropriate SNA or MQM documentation to determine the actual error.


00209405 INVALID BROKER API REQUEST
Explanation

An unsupported value has been specified for CLASS or SERVICE, e.g., APPC is not specified for CLASS.

Action

This is a user error. Check the program and correct the error.

Action

No action is required.


00209406 CONV-ID REQUIRED FOR DEREGISTER
Explanation

No CONV-ID, or an incorrect CONV-ID, was specified for the DEREGISTER function.

Action

This is a user error. Check the program and correct the error.


00209407 INVALID REMOTE ATTACH FUNCTION
Explanation

OPTION=ATTACH was specified for a function that is not a REGISTER, DEREGISTER, or RECEIVE function.

Action

Check the program and correct the error.


00209410 NO ATTACH REQUESTS AVAILABLE
Explanation

A Remote Attach Manager program has issued a non-blocked RECEIVE request with WAIT=NO, but there are no pending attach requests.

Action

This is an informational message.


00209413 CONV-ID REQUIRED FOR RECEIVE
Explanation

An ACI RECEIVE request has been issued without a valid CONV-ID value. All ACI RECEIVE requests must specify a CONV-ID value.

Action

Check the program and correct the error.


00209416 MODELQ REQUIRES SPECIFIC CONV-ID=
Explanation

An ACI RECEIVE request has been issued by a client program that specified CONVID=OLD or ANY while an MQI MODEL queue was in use.

Action

Change the program to use a specific, existing CONVID, or remove the REPLYTOQ specification from the directory entry.


00209417 INVALID MSGTYPE=, WAIT= COMBINATION
Explanation

A SEND request has been issued with an invalid combination of MSGTYPE=, WAIT= and CONFIRMATION operands. For example, specifying WAIT=YES when sending a DATAGRAM or a REPLY type message is invalid.

Action

Correct the program logic.


00209418 SERVER CANNOT ISSUE SEND CONVID=NONE
Explanation

A server program attempted to issue a SEND request with CONVID=NONE, which is not allowed. Server programs must use a specific CONVID when issuing a SEND.

Action

Correct the program logic.


00209419 INVALID MESSAGE TYPE FOR SERVER SEND
Explanation

A server program attempted to issue a SEND request with MSGTYPE=DATAGRAM or REQUEST, which is not allowed. Server programs are allowed to issue SEND MSGTYPE=REPLY only.

Action

Correct the program logic.


00209420 INVALID MESSAGE TYPE FOR CLIENT SEND
Explanation

A client program attempted to issue a SEND request with MSGTYPE=REPLY, which is not allowed. Client programs are allowed to issue SEND MSGTYPE=REQUEST or DATAGRAM only.

Action

Correct the program logic.


00209421 OPT=SYNC INVALID WITH SEND WAIT=
Explanation

A request was issued with OPTION=SYNC and WAIT=YES. It is not possible to issue a "blocking" request (WAIT=YES) within a unit of work.

Action

Correct the program logic.


00209422 SYNCPOINT REQUIRES OPTION=COMMIT/BACKOUT
Explanation

A SYNCPOINT request was issued without a valid OPTION= specification. Either OPTION=COMMIT or OPTION=BACKOUT must be specified with the SYNCPOINT function.

Action

Correct the program logic.


00209423 MSGID REQUIRED WITH CONVID=ANY/NEW/NONE
Explanation

A client program must use a specific MSGID when issuing a RECEIVE request with CONVID=ANY, NEW, or NONE.

Action

Correct the program logic.


00209424 UNIT FIELD OF WORK NOT SUPPORTED
Explanation

An ACI request was received that has specified a value for one of the unit-of-work fields.

Action

Programmer: Ensure no unit-of-work fields have been specified in the ACI request. If API Version=3 has been specified in the Broker control block (ETBCDEF.H), ensure that the unit-of-work fields have all been cleared.


00209450 INTERNAL ERROR - GETMAIN FAILED
Explanation

An internal buffer shortage has occurred that prevents the function from executing.

Action

Review the JES JOBLOG and external trace for error messages that might give additional information on the problem.


00209451 RECEIVE FAILED - tpname NOT REGISTERED
Explanation

A Remote Attach Manager has issued a RECEIVE request for a TP that is not currently REGISTERED to its SERVICE-ID.

Action

Modify the Remote Attach Manager program to REGISTER this tpname.


00209452 REGISTER REJECTED - function ACTIVE
Explanation

A Remote Attach Manager has issued a REGISTER request for a TPNAME that already issued a REGISTER.

Action

A TPNAME must be unique and can be registered under one and only one SERVICE-ID.


00209453 UNKNOWN FUNCTION REQUESTED function
Explanation

A request was received using the ATTACH-MANAGER DDM, but the request was not a REGISTER, RECEIVE, or DEREGISTER.

Action

Correct the Remote Attach Manager program and retry. The external trace may contain additional information for debugging.


00209454 ENTIREX BROKER SERVICES TERMINATED BY OPERATOR
Explanation

EntireX Broker Services have been shut down by the computer operator.

Action

No action required; normal processing continues.


00209455 function REJECTED, MISSING value
Explanation

A Remote Attach Manager has issued a verb that is invalid.

Action

The message text will contain the function and missing value. Correct the request and retry.


00209456 tpname NOT DEFINED VIA CONTROL OPERATOR
Explanation

A REGISTER request from a Remote Attach Manager is being rejected because of conflicts with Control Operator Interface definitions (RESTRICT-PARTNERS=PROFILE has been specified).

Action

Add the TPNAME in the message to the appropriate local LU definitions and retry the Remote Attach Manager program.


00209457 servername STOPPED BY OPERATOR COMMAND
Explanation

An Attach Manager RECEIVE was issued, but the specified servername has been stopped by an operator command. The message contains the actual server name.

Action

The Remote Attach Manager Dispatcher program may be restarted after using the RESUME, D6 servername operator command to reactivate the servername.