TibrvStatus

Cannot create the network transport.

The transport has been destroyed, or is otherwise unusable.

An argument is invalid. Check arguments other than messages, subject names, transports, events, queues and queue groups (which have separate status codes).

The method cannot run because the Rendezvous environment is not initialized (open).

Two arguments that require a specific relation are in conflict. For example, the upper end of a numeric range is less than the lower end.

Transport creation failed; cannot match the service name using getservbyname().

Transport creation failed; cannot match the network name using getnetbyname().

Transport creation failed; cannot match the daemon port number.

The method could not allocate dynamic storage.

The method received a subject name with incorrect syntax.

The Rendezvous daemon process (rvd) exited, or was never started. This status indicates that the program cannot start the daemon and connect to it.

The library, header files and Rendezvous daemon are incompatible.

It is illegal to create two certified worker events on the same CM transport with overlapping subjects.

A virtual circuit terminal was once complete, but is now irreparably broken.

1. The program attempted an illegal operation.

2. Cannot create ledger file.

The field name is too long; see Field Name Length.

1. The field type is not registered.

2. Cannot update field to a type that differs from the existing field’s type.

The explicit size in the field does not match its explicit type.

The explicit field count does not match its explicit type.

The program attempted to add data to a message field, but the datatype is not supported.

Could not find the specified field in the message.

Cannot add this field because its identifier is already present in the message; identifiers must be unique.

After field search by identifier fails, search by name succeeds, but the actual identifier in the field is non-null (so it does not match the identifier supplied).

Found the specified field, but could not convert it to the desired datatype.

The datatype handler number is reserved for Rendezvous internal datatype handlers.

The program’s datatype encoder failed.

The program’s datatype decoder failed.

The method received a message argument that is not a well-formed message.

The program supplied an invalid field as an argument.

The program supplied zero as the field instance number (the first instance is number 1).

The method detected a corrupt message argument.

A timed dispatch call returned without dispatching an event.

A send request call returned without receiving a reply message.

A virtual circuit terminal is not yet ready for use.

Interrupted operation.

The method received an event queue or queue group that has been destroyed, or is otherwise unusable.

The dispatcher thread is invalid or has been destroyed.

The method received an event that has been destroyed, or is otherwise unusable.

The method received NULL instead of a callback method.

The method received a queue that has been destroyed, or is otherwise unusable.

The method received a queue group that has been destroyed, or is otherwise unusable.

The method received a negative timer interval.

The operation failed because of an operating system socket limitation.

Tibrv.open() encountered an operating system error.

End of file.

1. A certificate file or a ledger file is not recognizable as such.

2. TibrvSdContext.setUserCertWithKey() or TibrvSdContext.setUserCertWithKeyBin() could not complete a certificate file operation; this status code can indicate either disk I/O failure, or invalid certificate data, or an incorrect password.

Rendezvous software could not find the specified file.

Cannot write to ledger file.

The program cannot open the specified file because another program owns it.

For example, ledger files are associated with correspondent names.

The call is not available because the IPM library is not linked (that is, the call is available only when the IPM library is linked).

Default error when the error cannot be specified more precisely.

The JNI library is not present.

SecurityException while opening TIBCO Rendezvous machinery; the JNI library is required, but not properly loaded.

Attempted to open the native (JNI) implementation, but failed; opened the Java implementation instead.