FilePro and dates

[Fairlight]

Realising that this is all a workaround for completely inadequate
storage and handling from the very inception of the program...

2-digit dates never should have been 'a thing'.  There should have been
translation functions for display, but never allow it to be stored that
way.  :(

m->


On Fri, Jan 10, 2020 at 01:28:57PM -0600, Richard D. Williams via Filepro-list thus spoke:
> I too have had to deal with this pesky problem.
> 
> What about a script like this;
> 
> #This script will continually set and reset PFCMARK
> #to ten years advance of this year.
> #
> YEAR=`date '+%G'`;
> YEAR=$((YEAR + 10));
> PFCMARK="${YEAR:2:2}";
> export PFCMARK
> 
> It works, but the issue is where to put.  It may require multiple places.
> 
> Maybe /etc/profile.d/filepro.sh, this would work on a re-boot.
> 
> How about the /appl/fp/p script, so whenever you use regular filepro, it
> wold work.
> 
> Save it as /appl/fp/lib/SET_PFCMARK to be used inside any scripts.
> i.e. . /appl/fp/lib/SET_PFCMARK
> 
> Of course one would have to remove all other PFCMARK references.
> 
> I have not acted on this yet. Looking for feed back.
> 
> Richard D. Williams
> 
> 
> 
> 
> This would require a re-boot
> On 1/7/2020 1:12 PM, Michael Schwartz (PC Support & Services) via
> Filepro-list wrote:
> > > FP Tech sent out an email the other day about resetting the pfcmark
> > variable
> > 
> > [snip]
> > 
> > > Richard Kreiss
> > > GCC Consulting
> > Hi Richard:
> > 
> >       I recommend you set the PFCMARK as far ahead as possible.  For most of
> > my customers, I've set it to "50".  (Hopefully I will be retired by 2050...)
> > <grin>
> > 
> >      For a few customers, especially in the insurance industry, I've had to
> > set PFCMARK as low as "23".
> > 
> >      After you change PFCMARK in the config file:
> > 
> > Rebuild any indexes that have "short" dates (mdy, mdy/, etcetera) in the
> > indexes.  If you don't do this, you may get very odd results.  (I'm sure
> > *ALL OF YOU* rebuild all your indexes and freechains anyway on a regular
> > basis.  I can't count the number of hours of troubleshooting that I've spent
> > because of corrupt indexes or freechains...)
> > 
> > Look through the customer's code (especially Linux cron jobs or Windows .bat
> > files) for anyplace that PFCMARK is set to some different date that would
> > override the PFCMARK setting in the config file.
> > 
> > As long as you are looking through all their processing tables for PFCMARK,
> > you may want to note any places where there are any other hard-coded dates
> > that will eventually cause you problems.
> > 
> > Happy 2020!
> > 
> > Mike Schwartz
> > 
> > 
> > _______________________________________________
> > 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
> 

-- 
Audio panton, cogito singularis.