cciUserTrace

void cciUserTrace(
  int*              returnCode,
  CciObject*        object,
  const CciChar*    messageSource,
  int               messageNumber,
  const char*       traceText,
                    ...
);

returnCode

Receives the return code from the function (output). A NULL pointer input signifies that the user-defined node does not want to deal with errors. Any exceptions thrown during the execution of this call are re-thrown to the next upstream node in the flow. If input is not NULL, output signifies the success status of the call. If an exception occurs during execution, *returnCode is set to CCI_EXCEPTION on output. A call to CciGetLastExceptionData provides details of the exception.

object

The address of the object that is to be associated with the trace entry (input). This object can be a CciNode* or a CciParser*. If it is a CciNode*, the name of that node is written to trace. If it is a CciParser*, the name of the node that created the parser is written to trace. This object is also used to determine if the entry should be written to trace. The entry is only written if trace is active for the node. Currently, nodes inherit their trace setting from the message flow.

If this parameter is NULL, the trace level for the integration server is returned.

messageSource

The fully-qualified location and name of the Windows message source, or the Linux, UNIX, or z/OS® message catalog (input).

To use the current broker message catalog, specify BIPmsgs on all operating systems. Alternatively, you can create your own message catalog.

When trace is formatted, a message from the NLS version of this catalog is written. The locale used is that of the environment where the trace is formatted.

You can run the broker on one operating system, read the log on that operating system, then format it on a different operating system. For example, if the broker is running on Linux, but no .cat file is available, you could read the log, then transfer it to Windows, where the log can be formatted by using the .properties file.

If this parameter is NULL, the effect is the same as specifying an empty string. That is, all other information is written to the log, and the catalog field has an empty string value. Therefore, the log formatter cannot find the message source. Consequently, the log formatter fails to format this entry.

messageNumber

The number that identifies the message within the specified messageSource (input). If the messageSource does not contain a message that corresponds to this messageNumber, the log formatter fails to format this entry.

traceText

A string of characters that ends with NULL (input). This string is written to service trace, and provides an easy way to correlate trace entries with paths through the source code. For example, if several paths through the code result in the same message (messageSource and messageNumber) being written to trace, you can specify traceText to distinguish between these different paths. That is, the traceText string is a static literal string in the source, and therefore the same string appears in both the source code file and the formatted trace file.

...

A C variable argument list that contains any message inserts that accompany the message (input). These inserts are treated as character strings, and the variable arguments are assumed to be of type pointer to char.

The last argument in this list must be (char*)0.

• For user-defined extensions that are running on distributed platforms, the char* arguments must be in ISO-8859-1 (ibm-918) code page.
• For user-defined extensions that are running on z/OS platforms, the char* arguments must be in EBCIDIC (1047).

These requirements include all char* arguments in traceText and the variable argument list of inserts (...).