Every time the server is started and for each hour thereafter, a date and time check occurs. An invalid date can be one of the following:
• Earlier than the server installation date and time.
• More than one hour earlier than the last time the date was check
• More than 30 days later than the last time the date was checked.
As a preventive measure, when TSM detects an invalid date or time, server sessions become disabled so that the TSM server does not perform undesired actions based on the new system date/time. For example, expiration processing uses the system date/time to determine when to purge files from server storage.
An error message (ANR0110E) is displayed and expiration, migration, reclamation, and volume history deletion operations are not allowed. You may either change the system date if it is in error, or issue the ACCEPT DATE command to force the server to accept the current system date as valid. Use the ENABLE SESSIONS command after you issue the ACCEPT DATE command to re-enable the server for client node activity.
In order to correct this problem, perform the following commands on the TSM server:
• Run the QUERY STATUS command and check for the availability parameter value, which should say 'disabled'
• Run the ACCEPT DATE command, which tells the TSM Server that you are aware of and accept the date/time change.
• Run the ENABLE SESSIONS command, which re-enables the TSM Server again for normal operations.
• Re-run the QUERY STATUS command and check for the availability parameter value, which should say 'enabled'
For the PDF version of this document, send a blank email, with subject line "System date/time change causes ANR0110E unexpected date sessions disabled", to TSM Assist