Output no matter what's happening (-RO not Working)
Richard D. Williams
richard at appgrp.net
Sun Aug 3 12:06:05 PDT 2014
Please ignore this post.
Thanks,
Richard
On 8/3/2014 1:59 PM, Richard D. Williams wrote:
> Top Post:
>
> Mike,
>
> You have changed this thread so it is coming from
> filepro-list at lists.celestial.com.
>
> I have files with millions of records and there is no limit associated
> with the -RO flag.
>
> If you want, attach you code on a reply and I will review it.
>
> I am sure the issue is code oriented. Sometimes a fresh pair of eyes is
> a good thing.
>
> Richard
>
>
> On 7/31/2014 6:02 PM, FilePro List wrote:
>> Geez, I have no idea if this is even going to get to the list cause I
>> just got a message saying this...
>>
>> Your membership in the mailing list Filepro-list has been disabled due
>> to excessive bounces The last bounce received from you was dated
>> 31-Jul-2014. You will not get any more messages from this list until
>> you re-enable your membership. You will receive 3 more reminders like
>> this before your membership in the list is deleted.
>>
>>
>> Anyhow, I changed the output line to say this and it took a whole three
>> seconds to run through every record without any issues.
>>
>> \fp\dreport invy -f expIslk -y none -z none -a -u -ro
>>
>>
>> There's not much processing going on here and without the -ro flag it
>> only takes about 15 seconds to run
>>
>>
>> Mike
>>
>>
>>
>> On 7/31/2014 5:35 PM, Kenneth Brody wrote:
>>> On 7/31/2014 5:11 PM, FilePro List wrote:
>>>> After watching it again, the output starts out okay when using the -RO
>>>> flag but then just starts slowing way down until it just stops all
>>>> together. There are 49619 records in the file and it stops on 36128
>>>> every time. I wouldn't think there would be a limit on the number of
>>>> output records when using the -RO flag.
>>> There isn't any limit to the number of records, beyond the filePro
>>> limit of 2 billion records per file. The -RO flag has no effect on this.
>>>
>>> You say this is in the output phase. As a quick test, run the report
>>> without any processing ("-y none -z none") and see if this makes a
>>> difference. If so, then there's probably something that your
>>> processing is doing, perhaps a getnext loop, which is causing the
>>> problem.
>>>
>>>> This is the command line and the output is on about 45,000 records but
>>>> it hangs on 36,000 or so every time I try running it and the file is not
>>>> locked, nobody is using the computer other than me when I tried it.
>>>>
>>>> \fp\dreport invy -f expIslk -a -RO -u
>>>>
>>>> Filepro 5.0.09 (DN9 whatever that means)
>>> The "DN9" means:
>>>
>>> "D" - dreport, rather than rreport.
>>> "N" - the "network aware" version, because long ago where was
>>> an MS-DOS version which wasn't.
>>> "9" - the Windows native version, again to distinguish it from
>>> one of the no-longer-available MS-DOS versions.
>>>
>>> [...]
>>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>>
>>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>
More information about the Filepro-list
mailing list