|
Dr,--
I have checked on a v5r3m5 machine and, inputting 21 as the "to" year
the system DOES reply with errors from 2019. So that's that and
fortunately it's an easy workaround.
Best Regards
Roberto
On Mon, Jan 7, 2019 at 5:45 PM DrFranken <midrange@xxxxxxxxxxxx> wrote:
So it works out that neither 19 or 20 are valid years in SAL. HOWEVER
21 is. So entering a date range of 12/31/18 to 01/01/21 does display
errors in that range expecting that date range is 2018 to 2021. So
far however we have not seen an error with a '19' date so that may
yet be a sticking point.
Also FYI I have though about 'breaking something' on purpose but it
needs to be on something expendable. :-)
- 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/4/2019 4:30 PM, DrFranken wrote:
Just discovered that V5R4M5 has the same issue in SAL (Servicev4r5).
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
--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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
