How to prevent that RQM command line adapter (CLA) always adds "com.ibm.rqm.adapter.resultAttachmentsFile=VALUE" to the command line argument list?

Hi guys,

today I stumbled across the following behaviour: whenever RQM executes a script or executable via a CLA script, the system always adds a command line argument to the command specified in the test script:

E.g., setting up a command line test script using:

Command: printargs
Arguments: arg1 arg2

the command arguments will evaluate to:

argc = 4
argv[0] = printarg
argv[1] = arg1
argv[2] = arg2
argv[3] = com.ibm.rqm.adapter.resultAttachmentsFile=/tmp/QMAdapter3942443898107188090.attach

The CLA test I am currently working on uses a command which is very strict with respect to command line parameters it receives, i.e., when parsing the command line arguments the command always exists with error

Error: Invalid option 'com.ibm.rqm.adapter.resultAttachmentsFile'

which effectively breaks the test.

Thus my question:
Is there any way to prohibit that the system adds the option 'com.ibm.rqm.adapter.resultAttachmentsFile=VALUE' to the command line arguments of the called script?

Also, as contained in the documentation, the process environment contains the environment variable  qm_AttachmentsFile:

qm_AttachmentsFile = /tmp/QMAdapter3942443898107188090.attach

which refers to the same attachments file as the one passed as a command line argument to the CLA command. This makes me wonder, why the system auto-appends this value as a command line argument in the first place.

As always, any input is greatly appreciated. Thanks a lot in advance & Cheers
Timo