PFLOGFILE and logtext

[Nancy Palmquist]

Eureka - I have figured out the silly thing.


BTW - The log append only affects the next time the user tries to open 
that log.  It indicates whether a new file is started or if it should 
add to the end of the existing file. Either way I would have a file.

But I did discover what caused the issue.  I had added a LOGTEXT command 
prior to assigning the PFLOGFILE name.

Filepro has a default log name that it will assign if none is given.  
And once a LOG is started you can not change the name during that 
process.  That is what I did.  Once I removed the LOGTEXT command that 
was prior to the putenv to set the PFLOGFILE name it worked as it should.

Somewhere out on my computer are the log files it was making by default, 
I have no idea where they went or what to look for to clean them up.

Nancy

On 8/6/2020 5:22 PM, Fairlight via Filepro-list wrote:
> What happens if you set PFLOGAPPEND -before- launching your filePro
> binary, rather than setting it inside processing?
>
> My suspicion is that it's not seeing it at the time it needs to.
>
> m->
>
>
> On Thu, Aug 06, 2020 at 05:04:13PM -0400, Nancy Palmquist via Filepro-list thus spoke:
>> filepro experts,
>> HELP - PLEASE.  Working on a WIN SERVER system, with filepro 5.0 (Sorry we
>> keep working toward an update to current but it has not happened.)
>>
>> I use PFLOGFILE and logtext all the time.  But it is driving me nuts today.
>>
>> One particular process table does not seem to be writing the expected logs.
>> Well it did write one for one user at least during the @once processing then
>> nothing else was added.
>>
>> Ok here I will try to explain.
>>
>> @once processing
>> PUTENV "PFLOGAPPEND", "ON"
>>
>> Logname=getenv("USERNAME"){-"INTHCB-"{doedit(@td,"YMD","6"){".log"
>> logpath="P:/tmp/";logpath=xlate(logpath,"/",chr("92"))
>>
>> putenv "PFLOGFILE",logpath{logname{""
>>
>> If I run the debugger at this point and ask for the getenv("PFLOGFILE") it
>> reports correctly.
>>
>> I do a few logtext command to write something in this logfile. Close the
>> processing,  But there is nothing added.  The log file is not  created at
>> all.
>>
>> I use logtext  all the time. I have never had it not work like this.  I
>> tried hardcoding the name, I can not figure out why this one process will
>> not write a log file when all the others work fine.
>>
>> Any ideas what else I can try?  I depend on these log files, since error
>> reporting is worthless with these users.
>>
>> Just another weird thing: the command line includes a -tf 200000 to increase
>> form size but if I getenv("PFFORMTOKSIZE") I get 125000 which is what is in
>> the config file.
>>
>>
>> Nancy
>>
>>
>> - -
>>
>> Nancy Palmquist         MOS & filePro Training Available
>> Virtual Software Systems    Web Based Training and Consulting
>> PHONE: (412) 835-9417           Web site:  http://www.vss3.com
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20200806/53b2b61b/attachment.html>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>

-- 
Nancy Palmquist         MOS & filePro Training Available
Virtual Software Systems    Web Based Training and Consulting
PHONE: (412) 835-9417           Web site:  http://www.vss3.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20200807/cc89ba10/attachment.html>