Re: Broken date support on old releases? V5R4 problem also!

[Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>]

I will be testing v5r2 and up just to be able to amend our service
procedures.
Will post my findings.

On Fri, 4 Jan 2019, 21:30 midrange <franz9000@xxxxxxxxx wrote:

> I've not read every part of this thread, but would ask those reporting an
> issue if they are up to date with the ptfs IBM provided for those releases.
> IBM did fix a lot of date stuff, spread over many years.
> Jim Franz
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> DrFranken
> Sent: Friday, January 04, 2019 4:31 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: Re: Broken date support on old releases? V5R4 problem also!
>
> Just discovered that V5R4M5 has the same issue in SAL (Service Action
> Log). No date in ??19 is valid nor ??20.
>
> ??21 works but the question now is that 1921? And where do you suppose we
> will find any new errors that pop up with the machine?
>
> Oddly PAL (Product Activity Log) does not exhibit this issue. Hmmm.
>
>          - Larry "DrFranken" Bolhuis
>
> www.Frankeni.com
> www.iDevCloud.com - Personal Development IBM i timeshare service.
> www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
>
> On 1/2/2019 3:43 PM, Roberto José Etcheverry Romero wrote:
> > 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