So we’re currently running the command-line validator and I’m trying to update our procedure to use validator-cli-2.0.0.jar. In our reports for TS, we’re getting notices that indicate that the validator is not seeing the UNII and NDF-RT files that are provided with the system:
| S:\Submissions\tools\OpenCDISC\opencdisc-validator-2.0\components\config/data/UNII/%System.UNII.Version%/UNIIs Names.txt is missing or lacks necessary variables and cannot be used for this cross-dataset validation |
|---|
| S:\Submissions\tools\OpenCDISC\opencdisc-validator-2.0\components\config/data/NDF-RT/%System.NDF-RT.Version%/NDF-RT.txt is missing or lacks necessary variables and cannot be used for this cross-dataset validation |
|---|
I’m assuming that there should be some -config: option to specify UNII and NDF-RT versions, but my naive attempts (-config:unii adn -config:ndf-rt) don’t work, and the documented -help option produces nothing but:
Picked up JAVA_TOOL_OPTIONS: -Djdk.lang.Process.allowAmbigousCommands=true
when used with validator-cli-2.0.0.jar.
I can see how these options are set in the interactive front end, but we’d really like to be able to specify them in a command-line invocation.
Any suggestions?