Problem

- How to control the size of  XMS2STL.out file ?
- How to disable huge logging of XMS2STL.out file.

Resolution

1. Check the XMS2STL_TRACE and XMS2STL_API_TRACE dynconfig parameters using "xmssel config" command. 

Both values should be on 0 in order to disable xms2stl tracing.
2. Check XMS_TRKCONF_ENV_VAR by "env | grep XMS_" command. If it is not defined then XMS will have trouble connecting to sentinel. This variable points to a file. In that file you should look for the TRKTRACE parameter.
3. Chances are the trace is not written by XMS, it is written by trkapi.

NOTE 

XMS2STL.out file is a trace file. The trace file for the Sentinel connector of XMS. It should be empty most of the time, unless some problem occurs or the trace level is increased. At each XMS restart, a copy of all trace files is saved and the new trace file begins from 0. Unless essential information for debugging some problems are present in the trace files, those files can be gradually removed as a part of the server maintenance/admin process. There is no way to set a limit on the trace file size. Unless you want to diagnose something, in production all processes should run with trace level 0.