Re: Broken date support on old releases?

[Bruce Vining <bruce.vining@xxxxxxxxx>]

The System supported date range is from August 23, 1928, 12:03:06.314752 to
May 10, 2071, 11:56:53.685240. Setting an input date that is outside this
range will result in a date within this range.

This is not related to application date ranges such as 1940 to 2039 for
interpretation of 2-digit years (in some places) or DB2 date ranges. It's
the date range you can set the system to.

On Wed, Jan 2, 2019 at 3:27 PM Rob Berendt <rob@xxxxxxxxx> wrote:

> In 7.3 the service action logs I tried a from date of 01/01/15 and a to
> date of 01/02/71 and that works fine.  But if I change the To date to
> 01/02/72 it dies with
>    The 'FROM' date should be earlier than the 'TO' date.
>
> And this is fine:
> From . . : 12/31/72 23:59:31   To . . : 01/01/71 00:00:31
> therefore 71 = 2071 and 72 = 1972
>
> This "window" may have nothing to do with DB2's window.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   "Roberto José Etcheverry Romero" <yggdrasil.raiker@xxxxxxxxx>
> To:     "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Date:   01/02/2019 03:44 PM
> Subject:        Broken date support on old releases?
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> Hi,
> We have customers that are really backlevel (I think the oldest is v4r5).
> On at least 3 v5r3 machines we noticed that trying to access the Service
> Action Log in the SST/DST gives an error regarding the date. It won't
> accept any date in 2019. Product Activity log on the other hand does work.
> Has anyone seen this?
> My only worry is whether this quirk is affecting only that particular menu
> or if the systems will suddenly start failing at the OS level.
> A quick google search didn't turn up what the date range is for the OS's 2
> digit date, So I don't know if 19 means 2019 or 1919...
> Any thoughts?
> BTW, I've been trying to migrate these customers to current machines, even
> hosting them on current hardware, but the longevity and self-management
> features of the system lead to some customers not even thinking of
> upgrading...
>
> Roberto
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> 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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> 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