SCO UNIX and Filepro 4.05

[Nancy Palmquist]

Cesar,
I have to say it depends on what kinds of dates you are keeping. If you 
are tracking birthdates, you had better change them to 4 digit well 
before now.

If you are tracking transaction dates, which are likely to be well 
within a 100 year window, you will have some time before you need to 
shift PFCMARK.

I have built into my programming a warning if the setting for PFCMARK is 
missing or too low.  We have had times when one user caused issues with 
their system date or a config file which was not in sync with everyone else.
2249 -------   -   -   -   -   -   -   -   -   -   -   -   -   - -   -   
-           
  If:        'this is part of the logic in @once or @entsel 
                                                           
  Then: declare PFCMARK(2)                                                
2250 -------   -   -   -   -   -   -   -   -   -   -   -   -   - -   -   
-            If: 
Then: PFCMARK=getenv("PFCMARK") 
2251 -------   -   -   -   -   -   -   -   -   -   -   -   -   - -   -   
-           
  If: @td eq "/OV" or @td ne @t4 or addmonth(@td,"12") eq "/OV"         
Then: beep; errorbox "PFCMARK is not set correctly.  Call Support 
"<@td<<"PFCMARK="<getenv("PFCMARK"); exit
2252 -------   -   -   -   -   -   -   -   -   -   -   -   -   - -   -   
-           
If: @td lt doedit("01/01/1995","mdyy/","10")  or @td gt 
doedit("01/01/20"{PFCMARK,"mdyy/","10")
Then: beep; errorbox "YOUR SYSTEM DATE SEEMS INCORRECT.... Call Support 
"<@td<"-"<PFCMARK; exit


I have found it best to set PFCMARK in the most central location 
possible.  So only one entry needs to be managed.
I can not speak to issues with the clock in a computer.  I would expect 
that computer would no longer be useful if the OS did not support the 
current time.  I think with the moves between Daylight and regular time, 
your computer may need to be manually updated when those changes happen, 
anyway.

I can appreciate your "IF IT IS NOT BROKE - DON'T FIX IT" response from 
the customer.  I have done many of these conversions over the years, and 
it can be problematic.  You not only have to correct all the maps and 
shuffle files, you have to make sure all the sorts are lengthened in 
indexes and reports.  You have to make sure all the data fits on screens 
and reports.  You may have to make other programming changes, but it is 
nice that if a dummy field has a 2 digit year and you write it to a 4 
digit year it will convert as long as PFCMARK is correct.

Depending on the project - changing all that stuff can be time consuming 
- and will require the system be out of service for some time.  Although 
you can prep for most of it on a copy system and then install the 
programming and shuffle files at the last minute.

Good luck with this.  I know I still have some hold outs also.

Nancy


On 7/23/2020 8:48 AM, Cesar Baquerizo via Filepro-list wrote:
> Good morning,
>
>   
>
> This is my every few years dilemma. Long story short.Due to possible lack of
> support for SCO UNIX on newer hardware, Y2K patches in older software
> (filepro and RealWorld), much more and, etc., etc. I have been recommending
> that we move off to a modern system. However, things "currently work" so
> that does not provide an "impending event".  FIlepro upgrade is not up for
> consideration.
>
>   
>
> I am looking to see if anyone knows enough about the filepro Y2K "patch"
> that can tell me how long we can expect filepro to work properly. I.e.
> PFCMARK is currently set to 25. Is there a max number that this can be set
> to? Any other issues anyone is aware of?
>
>   
>
> RealWorld Version 8 is another issue, but I assume this won't be discussed
> here. That said if anyone has comments about this, feel free to respond
> privately.
>
>   
>
> Thanks for any help.
>
>   
>
> Regards
> ---------------------
>
>
>
>
>
>
> ********************************************************************
>
> This message and any attachments are solely for the intended recipient. If
> you are not the intended recipient, disclosure, copying, use or distribution
> of the information included in this message is prohibited. If you received
> this message in error, please notify the sender and permanently delete.
>
>   
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20200723/9f916a5c/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 20179 bytes
> Desc: not available
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20200723/9f916a5c/attachment.png>
> _______________________________________________
> 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/20200820/5879cce8/attachment.html>