You can most easily access the Processing Sequence Log page for a selected run by clicking or tapping a history item on the Process Monitor Page.

However, you can also use a direct URL link if you understand how to format the URL. LANSA Composer's email event notifications, for example, can contain such links. (For more information refer to Event Maintenance.)

A typical URL to access the Processing Sequence Log page for a particular run looks like this:

In this URL, particular parts to note are:

  • 'LANSA01:7015' identifies the LANSA Composer Web Server instance. On your system it will be different to this example, however, it will be the same for all LANSA Composer Management Console pages on your system.
  • '+f(dxl1no)=482' identifies the run number of the Processing Sequence Log to be displayed. In this example, the run number is 157 (displayed in run history as 000000000000157)

This URL results in LANSA Composer displaying the log in the most appropriate manner for most purposes:

  • If there were no errors, it will be displayed in summary mode with parts relating to iterative directives and activities collapsed. The collapsed entries can be manually expanded as desired. If detailed log entries are available, a Show detailed button at the top-right permits them to be displayed.
  • If there were errors, the part of the log containing the error is expanded and detailed log entries are shown, if available. Other parts relating to iterative directives and activities are collapsed. The collapsed entries can be manually expanded as desired.

This default mode of presentation is optimised to show the most pertinent information initially as well as to minimise the load times, since some Processing Sequence Logs can be very large indeed.

If you wish, you can generate and use URLs to alter LANSA Composer's default manner of presentation, by adding one or both of the following keywords to the standard URL form:

  • '+expandall' causes the initial log load and display to have all parts relating to iterative directives and activities expanded.
Warning: Depending on what a Processing Sequence does, some Processing Sequence Logs can be very large. Consider, for example, a Processing Sequence that runs for an extended period using, say, the WATCH_DIRECTORY activity to monitor for new files in a directory. If you attempt to load such large logs in fully expanded mode, they may take a very long time to load, or, in some instances, the load may fail. LANSA Composer's default mode of presentation is designed to avoid such issues while still showing the most pertinent information.
  • No labels