YADE should consider the result_set_file_name parameter when used with jade4DMZ

Current Situation

• The parameter result_set_file_name is not considered if YADE is used with a jump host and is invoked by jade4DMZ.cmd|sh
• Configuration Example

  [protocol_fragment_jump@london_uk_jumphost]
  jump_host                           = uk.sos-berlin.com
  jump_port                           = 22
  jump_user                           = london
  jump_ssh_auth_method                = publickey
  jump_ssh_auth_file                  = C:\users\ap\jade_demo\id_rsalondon
  jump_command                        = /home/london/sos-berlin.com/jade_client/jade_snapshots/jade_client.1.8.2-SNAPSHOT/bin/jade.sh
  jump_proxy_protocol                 = http
  jump_proxy_host                     = homer.sos
  jump_proxy_port                     = 3128
  jump_proxy_user                     = proxy_user
  jump_proxy_password                 = 12345
  
  [protocol_fragment_sftp@tokyo_japan_targethost]
  protocol                            = sftp
  
  host                                = japan.sos-berlin.com
  port                                = 22
  user                                = tokyo
  ssh_auth_method                     = publickey
  ssh_auth_file                       = /home/london/.ssh/id_rsatokyo
  
  
  [profile@jump_copy_to_internet_proxy]
  operation                           = copytointernet
  
  source_protocol                     = local
  source_host                         = localhost
  file_spec                           = ^(test)(_)[0-9]\.txt$
  source_dir                          = ${USERPROFILE}\jade_demo\b
  
  target_include                      = protocol_fragment_sftp@tokyo_japan_targethost
  target_dir                          = /home/tokyo/data/to_tokyo
  
  include                             = protocol_fragment_jump@london_uk_jumphost
  
  result_set_file_name                    = c:\tmp\result_list_file.log
  

Desired Behavior

• The list of files available for transfer in a file as specified by the above configuration