|
Rob,
AFAIK, QUTCOFFSET is settable. Check IBM's KB.
Regards,
Luis
Sent from my Moto G phone. Please excuse my brevity.
On Thu, Jun 28, 2018, 06:20 Rob Berendt <rob@xxxxxxxxx> wrote:
<snip>list
Well, the system values are all *settable*, not just gettable.
</snip>
<buzzer sound>
False. The system values are NOT all *settable*.
WRKSYSVAL QUTCOFFSET
2=Change
System value QUTCOFFSET cannot be changed.
But maybe you were meaning to say these system values are *settable*:
WRKSYSVAL *DATTIM
Well, most of them. Including QDATETIME
Thought about changing that on our sandbox lpar but I think I would want
to only do that in restricted state so as not to screw up any logs and
journals.
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: "John Yeung" <gallium.arsenide@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx
Date: 06/28/2018 01:27 AM
Subject: Re: QCENTURY and other date-related system values
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On Thu, Jun 28, 2018 at 1:07 AM, Dan <dan27649@xxxxxxxxx> wrote:
To the best of my knowledge, QDATETIME will return a valid date all theway
through the year 9999.
Well, the system values are all *settable*, not just gettable. So
let's say you set QDATETIME to 4018-06-28. What do you get when you
retrieve QDATE and QCENTURY?
Obviously, I'm not going to try this on any actual machine!
More to the point, any date data type with a
4-digit year will correctly support any year up to 9999. The 54-99 and
00-24 century crap only applies if you are using date data types with a
2-digit year.
I wouldn't be so sure. Why does the documentation say that the years
1928 through 2053 are supported? Why not a 100-year window? Why not
1901 through 2099?
There are sometimes other constraints besides the number of base-10
digits. I don't know if that's the case here, but I don't know that
it's not.
John Y.
--
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: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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: http://amzn.to/2dEadiD
On Thu, Jun 28, 2018, 06:20 Rob Berendt <rob@xxxxxxxxx> wrote:
<snip>list
Well, the system values are all *settable*, not just gettable.
</snip>
<buzzer sound>
False. The system values are NOT all *settable*.
WRKSYSVAL QUTCOFFSET
2=Change
System value QUTCOFFSET cannot be changed.
But maybe you were meaning to say these system values are *settable*:
WRKSYSVAL *DATTIM
Well, most of them. Including QDATETIME
Thought about changing that on our sandbox lpar but I think I would want
to only do that in restricted state so as not to screw up any logs and
journals.
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: "John Yeung" <gallium.arsenide@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx
Date: 06/28/2018 01:27 AM
Subject: Re: QCENTURY and other date-related system values
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On Thu, Jun 28, 2018 at 1:07 AM, Dan <dan27649@xxxxxxxxx> wrote:
To the best of my knowledge, QDATETIME will return a valid date all theway
through the year 9999.
Well, the system values are all *settable*, not just gettable. So
let's say you set QDATETIME to 4018-06-28. What do you get when you
retrieve QDATE and QCENTURY?
Obviously, I'm not going to try this on any actual machine!
More to the point, any date data type with a
4-digit year will correctly support any year up to 9999. The 54-99 and
00-24 century crap only applies if you are using date data types with a
2-digit year.
I wouldn't be so sure. Why does the documentation say that the years
1928 through 2053 are supported? Why not a 100-year window? Why not
1901 through 2099?
There are sometimes other constraints besides the number of base-10
digits. I don't know if that's the case here, but I don't know that
it's not.
John Y.
--
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: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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: http://amzn.to/2dEadiD
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: http://amzn.to/2dEadiD
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
