http://itknowledgeexchange.techtarget.com/itanswers/as400-system-time-and-date/ Tue, 18 Jun 2013 20:45:14 +0000 hourly 1 http://itknowledgeexchange.techtarget.com/itanswers/as400-system-time-and-date/#comment-111887 rajeshece Fri, 05 Oct 2012 04:04:55 +0000 http://itknowledgeexchange.techtarget.com/itanswers/as400-system-time-and-date/#comment-111887 CHGSYSVAL. But chk once whether you are having authority or not to use this command

]]> http://itknowledgeexchange.techtarget.com/itanswers/as400-system-time-and-date/#comment-111878 TomLiotta Fri, 05 Oct 2012 00:44:50 +0000 http://itknowledgeexchange.techtarget.com/itanswers/as400-system-time-and-date/#comment-111878 The CHGSYSVAL command can be used, or the option to ‘Change’ from the WRKSYSVAL command is also available.
 
But those are only “how” to make the actual change. A procedure for making such a change can be much more complex.
 
The system date and time is a critical part of auditing/tracking events that happen on the system. If date/time is reset backwards, there are system elements that might need attention. Journals, for example, are strongly tied to timestamps. Message queues also have timestamp relationships. (That includes joblog messages.)
 
Changes might require system downtime in order to avoid creating duplicate timestamps that would mess up recovery or restore efforts or would confuse any programs or reports that process according to timestamps.
 
Also, changes to system date/time should be done with consideration to system timezone. Make sure the timezone is correct before changing time. If you’re simply changing the hour, it might be that the timezone is wrong.
 
In order to know what an appropriate procedure would be, you should describe the reason for making the change, including how large the change will be. It might be that you’ll be better off running an “attended IPL” and setting the values during that process.
 
Tom

]]>