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: printargsthe command arguments will evaluate to: argc = 4The 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.attachwhich 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 |
Accepted answer
we saw this a long time ago - this has been fixed but I don't remember in which level.
Timo Reiss selected this answer as the correct answer
Comments
Timo Reiss
commented Aug 31 '15, 10:26 a.m.
David,
Look at this defect https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=125876
Timo Reiss
commented Sep 01 '15, 3:33 a.m.
David,
I think you can request the APAR which I believe is in an iFix somewhere. We are running on 5.0.2 and we don't have to use a wrapper script
Timo Reiss
commented Sep 01 '15, 9:40 a.m.
David,
With that, my problem is solved. Hopefully, no compatibility issues will come up with the CLA 6.0 in a 5.0.2 environment. At least until now, everything looks fine.
Thanks again for your help, which I really appreciate.
Cheers
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Forgot to mention the version of RQM we are running: it is RQM 5.0.2 iFix007