2.2.3 Tasks that become necessary as a result of a system date/time change

(a) Resetting the manager's system date/time back to the original date/time

1. Stop JP1/IM - Manager.

2. If the IM database is being used, stop the IM database.

3. Stop JP1/Base.

4. Reset the system to an earlier time.

5. When the system reaches the original time, start JP1/IM - Manager.

   For example, if the system was reset from 02:00 to 01:00 in step 2, start JP1/IM - Manager when the system reaches 02:00.

   However, if the IM database is being used, perform the following steps to start JP1/IM - Manager in step 4.

   1. JP1/Base

   2. IM database

   3. JP1/IM - Manager

Alternatively, you can use the method described below to reset the system date and time. However, note that if you use this method, the information shown in step 5 and the event and host information in the IM database must be deleted.

Steps 3 and 6 are required only if you are using the IM database. To reset the date/time back to the original date/time:

1. Stop JP1/IM - Manager.

2. Stop JP1/Base.

3. Perform unsetup for the IM database.

   For Windows, you need to start the JP1/IM-Manager DB Server service beforehand.

   If the integrated monitoring database and IM configuration management database have been set up, you must remove both of those setups.

4. Reset the system date/time to the current date/time.

5. Delete the action information file, action hosts file, event database, and command execution log file.

   The tables below show where the files to delete are stored.

   In Windows:

   Table 2‒1: Files to delete (Windows)

   File name	Storage location
   Action information file	Console-path\log\action\actinf.log
   	shared-folder\jp1cons\log\action\actinf.log
   Action hosts file	Console-path\log\action\acttxt{1|2}.log
   	shared-folder\jp1cons\log\action\acttxt{1|2}.log
   Command execution log file	All files under Base-path\log\COMMAND\
   	All files under shared-folder\jp1base\log\COMMAND\
   Event database	IMEvent*.* files under Base-path\sys\event\servers\default\#
   	IMEvent*.* files under shared-folder\jp1base\event\ #

   #: If a different path was specified in the event server index (index) file, the files under the specified path need to be deleted.

   In UNIX:

   Table 2‒2: Files to delete (UNIX)

   File name	Storage location
   Action information file	/var/opt/jp1cons/log/action/actinf.log
   	shared-directory/jp1cons/log/action/actinf.log
   Action hosts file	/var/opt/jp1cons/log/action/acttxt{1|2}.log
   	shared-directory/jp1cons/log/action/acttxt{1|2}.log
   Command execution log file	All files under /var/opt/jp1base/log/COMMAND/
   	All files under shared-directory/jp1base/log/COMMAND/
   Event database	IMEvent*.* files under /var/opt/jp1base/sys/event/servers/default/ #
   	IMEvent*.* files under shared-directory/jp1base/event/ #

   #: If a different path was specified in the event server index (index) file, the files under the specified path need to be deleted.

6. Set up the IM database.

7. Start JP1/Base.

8. Start JP1/IM - Manager.

This completes resetting of the system data/time of the manager. If you are using Central Scope, perform the following tasks.

1. From JP1/IM - View, log on to JP1/IM - Manager (JP1/IM - Central Scope).

2. From the Monitoring Tree window, choose the highest-order monitoring group and set its state to the initial state.

   Resetting all monitored nodes to their initial states eliminates inconsistencies in the data managed by Central Scope.

(b) Resetting the agent's system date/time back to the original date/time

When you reset the agent's system date/time back to the original date/time, you must reset both the event database of the JP1/Base on the applicable host and the JP1/Base time on the host at the event forwarding destination. For details such as the relevant procedure, see the explanation on necessary tasks when the system date/time is changed in the chapter about changing settings during operation of JP1/Base in the Job Management Partner 1/Base User's Guide.