This is possibly my fault or a bug. STAX reuses job IDs, which I understand, but it appears to cause problems with the logs. Basically, my newer job log contains data from the old job which used the same job ID. It looks like it is simply appending the new data onto the old log file.
Is this expected?
Yes, since the default value for the CLEARLOGS parameter for the STAX service is Disabled. There are parameters (CLEARLOGS and RESETJOBIDS) that you can specify when registering the STAX service in your STAF.cfg file to change the default settings for these parameters. The STAX User's Guide talks about these options in the "Installation and Configuration" section for the STAX service at http://staf.sourceforge.net/current/STAX/staxug.html#Header_StaxServiceMach. For example, to clear the STAX job logs before starting a new STAX job you can enable the CLEARLOGS parameter when registering the STAX service. For example:
SERVICE STAX LIBRARY JSTAF EXECUTE C:\STAF\services\stax\STAX.jar \
PARMS "CLEARLOGS Enabled"
You can also change these settings for the STAX service dynamically via the SET request for the STAX service. For example:
STAF local STAX SET CLEARLOGS Enabled
Note that dynamic changes to service settings only apply to the current registration of the STAX service. So, if you always want to clear the STAX logs, you'll also want to add the "CLEARLOGS Enabled" parameter when registering the STAX service in the STAF.cfg file. For more information about the SET request, see http://staf.sourceforge.net/current/STAX/staxug.html#Header_Set.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.