[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SV: FTP_LOG(*OFF) doesn't work??
There is nothing new in this.
I reported the same problem and the solution on 17 July 2015 but got no
response for it.
It was this:
I have discovered an error in the procedure FTP_logging in FTPAPIR4 in
the statements
c eval wkDebug = peSetting
B01 c if savSessionIdx <> -1
c callp cmd_occurSession(savSessionIdx)
E01 c endif
The problem is that wkDebug is a field in the multiple-occurrence data
structure wkSession and the
actual occurrence is set in the procedure cmd_occurSession !
This way wkDebug is set for the false session.
It should be
B01 c if savSessionIdx <> -1
c callp cmd_occurSession(savSessionIdx)
E01 c endif
c eval wkDebug = peSetting
Kind regards
Peder Udesen
-----Oprindelig meddelelse-----
Fra: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] P�egne af Nicola Brion
Sendt: 6. april 2016 12:20
Til: HTTPAPI and FTPAPI Projects
Emne: Re: FTP_LOG(*OFF) doesn't work??
Just dig more inside the package...
the problem appear to be when Handle = *Zero, so FTP_Logging() will
call
cmd_occurSession(DFT_SESSION_IDX)
and after setting wkDebug it calls cmd_occurSession(savSessionIdx) and
revert back wkDebug.
If i perform a dummy open, so that handle is 1 instead of 0, (or, i
suppose, any other handle grater than 0) then wkDebug is correct and
loggin won't happen.
I'm not sure i changing row 936 from
B01 c if peSession <= 0
to
B01 c if peSession < 0
would generate more problems that it solved (also, i'm not happy to do
custom modify on a external project...)
HTH
2016-04-06 11:31 GMT+02:00 Nicola Brion <[1]obelix.it@xxxxxxxxx>:
>
>
> 2016-04-05 19:14 GMT+02:00 Julius Kaj <[2]Kaj.Julius@xxxxxx>:
>
>> Hi Nicola,
>>
>>
>> Messages sent to the job log is often sent by system objects and not
>> the application itself. You must therefore control the level of
>> logging you want at the job level.
>
> Julius, my question was about the message sent by the logging
facility
> of the FTPAPI, not system message.
>
> my joblog looks like:
>
> 0: FTPAPI version 2.3 released on 2010-05-27
> 0: 220-QTCP at LOOPBACK.
> 0: 220 Connection will close if idle more than 5 minutes.
> 0: > USER nicola
> 0: 331 Enter password.
> 0: > PASS **********
> 0: 230 NICOLA logged on.
> 0: > TYPE A
> 0: 200 Representation type is ASCII nonprint.
> 0: > PORT 127,0,0,1,130,73
> 0: 200 PORT subcommand request successful.
> 0: > NLST /ivri/unicredit/output/IV*.*
> 0: 125-NAMEFMT set to 1.
> 0: 125 No files found in directory /ivri/unicredit/output/IV*.*
> 0: 250 List completed.
>
> where last 8 rows are repeted every 30 sec or so.
>
> All are CPF9897 which i supposed are sent by the DiagMsg() function
of
> FTPAPI. I appreciate to be able to send diag message to JobLog when
> needed, but if i ask to stop, i expect them to stop
>
> i debugged the function, and wkDebug appear to be still *on even
after
> i ask it to be off....
>
>
--
Nicola Brion
Tech Fossil (Often called a Dinosaur) - ancient animal that make
things to work.
This email and any files transmitted with it may be confidential and
intended solely for the use of the individual or entity to which they
are addressed. If you have received this email in error please notify
the sender.
References
1. mailto:obelix.it@xxxxxxxxx
2. mailto:Kaj.Julius@xxxxxx
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------