Originally posted by: SystemAdmin

Hi All,
We have a requirement to prune the logs generated from a particular msl. At present it generates log for each and every transaction starting from MQ to DB update - so for each transaction its filling in the disk space.

Our requirement is to get the warnings/ errors only logged for thar particular MSL. We tried -TE option but it doesn't minimize the number of logs file albeit the size of the log file generated.

Any help/pointers are much appreciated here.

Cheers
Sid
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Hi All
Browsing thru the docs - i got one function lasterrorcode() -can we tweak that - in layman logic

if lasterrorcode() !=0 then write the logs or else do not write

Please may i know if some one has implemented this logic.

cheers
Sid
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

What's actually generating the log / trace file? What kind of log / trace file is it?
it sounds like it's coming from the map rather than the msl.

if you're getting lots of them it could be the map audit log - switch this off in the map settings (you can also tell it only to generate in the event of an error).
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender