Re: httpapi debug file appending not replacing

I just ran the process in debug and verified the unlink process was being
executed and the path/filename were correct but the file still existed
after that.

Since then I have now run from IFSEBOOK CH3RENDEL which did successfully
delete the file and it uses exactly the same method.

I am really confused now.

In httpapi the file name is trimmed into the variable passed to unlink eg

eval HTTP_DEBUG_FILE = %trimr(peFilename)
callp unlink(HTTP_DEBUG_FILE)

Whereas in CH3RENDEL

unlink(%trimr(path)) < 0

But that should not make any difference ?

I am obviously missing something :-(

Thanks


Don Brown





From: "B Stone" <bvstone@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 02/12/2019 08:23 AM
Subject: Re: httpapi debug file appending not replacing
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



Is there anything in the job log? I know Scott puts a lot of debugging
messages in his code.

Are you running backups or are backups in MSGW? That can lock
files/folders in the IFS from being deleted.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #4 <https://www.bvstools.com/mailtool.html>: Easily add
attachments of any type from the IFS to outgoing emails.

On Sun, Dec 1, 2019 at 3:30 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

The debug file should be created each tine I call for example
http_url_post_xml not appended to.

It would appear the unlink is failing but there is nothing in the job

log

and the job does not abend/crash and require a response.

I ran the process in debug and the debug file exists, the
unlink(HTTP_DEBUG_FILE) was executed and the file still exists, there

was

no error and the value in HTTP_DEBUG_FILE is the correct file name and
path.

How do I determine why the stream file is not being deleted ?

Thanks for any suggestions


Don Brown




From: "Patrik Schindler" <poc@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 01/12/2019 09:16 PM
Subject: Re: httpapi debug file appending not replacing
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



Hello Don,

Am 01.12.2019 um 02:16 schrieb Don Brown via MIDRANGE-L
<midrange-l@xxxxxxxxxxxxxxxxxx>:

The result of unlink is not being checked - would this be logged to

the

job log ?

I guess no, but certainly your program will be sent an exception. If

it's

unhandled, the user get's the usual screen about
cancel-continue-debug-whatever or if it's a batch job, it will
abend/crash.

How can I determine why the stream file is growing rather than being

recreated on each call to httpapi ?

I don't understand your question. It's a debug log, so it's growing
because of debugging output. If you want to know what's in it, have a
look. If you don't need the debugging, turn debugging off. Or did I miss
something in your question? Maybe you can rephrase your question?

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud

service.

______________________________________________________________________





______________________________________________________________________
This email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email,

MSD

cannot accept responsibility for any loss or damage arising from the use

of

this email or attachments.
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com