-- The following transfer definition will not send these parameters to the PESIT partner:
peltrans -type TRANS -dir O -mode I -oa PART_1 -da PART_2 -fc d:\aaa -fn FILENAME -appli FTP_A -snd_user USER1234 -snd_appli APPLI123

-- In this case, in the originating Gateway, the transfer appears as if these parameters were sent (-snd_user USER1234 -snd_appli APPLI123)

-- However, on partner side these parameters are not received and checking the PESIT logs one can confirm that these variables were not sent

-- The objective is to explain how to correctly send these types of parameters from a Gateway to another Pesit partner.

* The parameters "snd_user", "snd_appli", "rcv_user" and "rcv_appli" are specific to a Store and Forward transfer (PeSIT HS E Store-and-Forward only)

* In order to successfully send this type of parameters from a Gateway one should create a Store and Forward transfer:

peltrans -type TRANS -dir O -mode I -oa PART_1 -da PART_2 -dest PART_3 -fc d:\aaa -fn FILENAME -appli FTP_A -snd_user USER1234 -snd_appli APPLI123

* It is important to note the new parameter added: -dest PART_3
This means that the final destination of this transfer is PART_3.
PART_2 is an intermediary: it will receive the transfer and it may forward it to the PART_3