Sentinel-1 calibration produces undesired target.dim/data

Calibrate is required to produce Beta0 from Sentinel-1 for input to Terrain-Flattening. Regardless of settings, Calibrate produces undesired target.dim/target.data files. Either or both createBetaBand or outputBetaBand are required to be set as true for Terrain-Flattening to not error with: Error: [NodeId: Terrain-Flattening(2)] TerrainFlattening requires beta0 or T3, C3, C2 as input

I believe that setting one of the parameters createBetaBand or outputBetaBand to false should disable output of the full calibrated images into the default target.dim/data

  <outputImageInComplex>false</outputImageInComplex>
  <outputImageScaleInDb>false</outputImageScaleInDb>
  <createGammaBand>false</createGammaBand>
  <createBetaBand>true</createBetaBand>
  <selectedPolarisations/>
  <outputSigmaBand>false</outputSigmaBand>
  <outputGammaBand>false</outputGammaBand>
  <outputBetaBand>false</outputBetaBand>

This behavoir changed after 6.0 upgrade. The above graph entries now result in an abort with
Error: [NodeId: Terrain-Flattening(2)] TerrainFlattening requires beta0 or T3, C3, C2 as input.

Switching the settings for BetaBand in Calibration, as shown below, resolves the failure/abort, but still produces the undesired target.dim output.

  <createBetaBand>false</createBetaBand>
  <outputBetaBand>true</outputBetaBand>