[psamman]

Hi there,

Can someone please explain how to enable User Exits for a specific Remote Site / protocol?
Where would the output from a "printf" in a User Exit end up? In log.dat?
Is it ok for .c User Exits not to have a main() entry?!

Any help appreciated.

[coincoin]

Hi,


Can someone please explain how to enable User Exits for a specific Remote Site / protocol?
I think you must select the right user exit and add a condition when there is a specific action to do.

Where would the output from a "printf" in a User Exit end up? In log.dat?

the Printf output goes to STDOUT
the LogPrintf output goes to log.dat
Example :
LogPrintf(ITP_LOG_INFO, "Obtaining port number from: in->login_sap=%s", in->login_sap);

Is it ok for .c User Exits not to have a main() entry?!
I don't know ! Sorry !

[Mario128]

hi
there is no main, because Exits are functions called by Gateway itself ( that mean main has been already called by Gateway startup )
By default all exits are called, but they do nothing, until you write your own code to do what you want

[psamman]

Thank you coincoin & Raphael, that helps !

I'm still a little confused as of how my code (in an exituser.c for example) would be called.
Say I define a function f(){...} and compile. Is f executed automatically, or do I have to add the call
"f();" at the end of the source file?

[DELORME ALAIN - ...]

Thank you coincoin & Raphael, that helps !

I'm still a little confused as of how my code (in an exituser.c for example) would be called.
Say I define a function f(){...} and compile. Is f executed automatically, or do I have to add the call
"f();" at the end of the source file?

Hi,

The entry point of user exit are specifics functions indicated on file src/exituser/exitProtocol.c
The list and description of these functions are indicated on the documentation (search internal user exits)

The gateway's User exits, unlike CFT exits, are hooks to hack the defaut behavior of the Gateway (for instance, to indicate the IP adress to use for a FTP PASV command)
If you want to execute a C program when a transfer for a specific Remote Site is ended (like CFT exits), I suppose that you must use a decision rule. To acces transfer parameters on a external C program I suppose you must use the getenv to retrieve x_parameters.

regards,

alain

[psamman]

The entry point of user exit are specifics functions indicated on file src/exituser/exitProtocol.c

The gateway's User exits, unlike CFT exits, are hooks to hack the defaut behavior of the Gateway (for instance, to indicate the IP adress to use for a FTP PASV command)

Oh ! I think I got it this time: you mean User Exits are called systematically if the .o exists in obj/ directory, even if they are dummy?
Because they are dummy by default, the "#if 0" makes them: basically, functions have no bodies.
If that is true, if I remove the "#if 0" from ExitFtpRespPasv() in exitftp.c for example, I do not need to add a call to this function "ExitFtpRespPasv();" at the bottom of exitftp.c? This only makes sense, because I don't see what arguments I would be passing!

Please somebody confirm/correct me.

I know how to use decision rules to trigger a processing after a transfer. That's not what I need. I'm specifically interested in User Exits for they allow actions during a transfer.

Thanks, people.