Customising JSM trace folders based on Application groupings

Date:	7 May 2012
Product/Release:	LANSA Integrator - All Versions
Abstract:	Its possible to create custom folders for JSM traces in order to easily access the trace files.
Submitted By:	LANSA Technical Support

Many organizations have a requirement to constantly audit/check the trace files. There can be many reasons to do this; for instance to confirm transactions. When JSM application(s) are generating a large number of trace files, it can become a task to locate the required trace file(s).

JSM provides a way to control or name folders into “transaction groups/types". This makes navigating through the generated trace files easier.

In the SERVICE_LOAD command, in addition to TRACE(*YES), put TRACE_NAME(myGroup1).
This will concatenate the specified trace name to the folder name. i.e. CLIENT000001_myGroup1 or CLIENT00001_ePayment …etc

You can use a literal naming convention as above, or any of the following special values:
>-- TRACE_NAME ------ name ------------------------|
*SERVICE
*PROCESS
*FUNCTION
*JOBNAME
*JOBUSER
*JOBNUMBER

Refer to the LANSA Integrator Guide for further details.