x

Records documenting the start and stop (including abnormal termination) of JSCOM3 processes are written to the edaprint server log. All error paths write error line(s) to edaprint. Common error paths (for example, unsupported release level) provide more helpful diagnostics.

x

The edaprint server log now shows timestamps in milliseconds.

x

In case of abnormal agent termination, the server produces better diagnostic information in the edaprint server log and event e-mails. A memory dump file is also produced. The dump is saved by the Savediag procedure for the delivery to Information Builders Customer Support. The production of the dump file can be suppressed.

There are two new optional environment variables:

• EDA_IBISNAP2={OFF/ON}

  This disables the ibisnap2 dump feature. The default is ON.

• EDA_IBISNAP2_TIMEOUT=nnn

  Sets the maximum processing time in seconds for each ibisnap2. The default is 60.

The detail level of the ibisnap2 diagnostic information is achieved by including build .pdb files and doing an immediate dump read after an abnormal termination (which is the portion displayed in the edaprint log). These additional files produce very complete dump information and provide the ability to find and respond to abnormal terminations immediately where the originating event may have been unclear. So while the files do increase the size of the product, they provide a significant benefit.

x

The Reporting Server can now send and receive e-mails using SMTP Servers with only MX (mail exchange) records.