2.4.1 Time zones
When you use JP1/AJS3 - View to log in to JP1/AJS3 - Manager, and you check the jobnet execution statuses and execution results, the time displayed obeys the time zone set in the OS of the computer where JP1/AJS3 - View is installed.
- In Windows:
-
When running JP1/AJS3 - Manager in Windows, you cannot set time zones for individual processes (a manager host cannot handle more than one time zone). If your system operates across time zones, set up manager hosts and JP1/AJS3 - View hosts separately for each time zone.
- In UNIX:
-
UNIX allows you to set time zones in process units, so you can set a TZ environment setting variable for each registered user to execute jobnets registered for execution at JP1/AJS3 - Manager (you can use multiple time zones at a single manager host).
However, the following restrictions apply to operations on units:
-
When working from JP1/AJS3 - View, since you can only handle one time zone, prepare unit definitions for each time zone and start JP1/AJS3 - View separately for each of these time zones.
-
When you register jobs for execution, use the ajsentry command in an environment where a TZ environment variable is set for each time zone.
-
Only relative specifications can be made for times (e.g. time changes).
-
If you want to use a command to check the jobs registered for execution, use the ajsshow command in the environment with the same TZ environment variable that was used when the jobs were registered for execution.
-
When JP1/AJS3 - View is set up to display Japanese time for execution statuses and execution results, even if the jobnet is actually executed in another country, the time displayed will be Japan time, not the local time in that country. In Windows, to check jobnet execution statuses and execution results from a region with a different time zone in the local time, you have to prepare a computer set to the local time and running JP1/AJS3 - View. For example, to display the execution statuses from New York in New York time, prepare a JP1/AJS3 - View computer with its clock set to New York time.
The following figure shows a system configuration that allows you to check execution statuses on multiple hosts for administrative tasks in different time zones.
|
|
![[Figure]](GRAPHICS/ZH020160.GIF)
See the following cautionary notes when manager hosts and agent hosts operate in different time zones.
These cautionary notes apply when a scheduled job is executed, not when defining a jobnet execution schedule.
Jobnets are scheduled for execution based on the manager's time zone setting.
- Cautionary notes
-
-
Jobs are executed based on the agent's time zone setting. Times logged in the standard output file and standard error output file are based on the agent's time zone setting.
-
The job timeout period is governed by the elapsed time, and does not conform to the time zone.
-
Time data included in the event job passing information (EVDATE, EVTIME, FLCTIME, and MLRCVTIME) has the time zone of the agent host on which the event occurred. When a JP1 event reception monitoring job detects a JP1 event that has been transferred from another host, the time data included in the passing information (EVDATE and EVTIME) is expressed in the time zone of the transfer source. It is not expressed in the manager host's time zone or in the time zone used for other jobs that use the passing information.
-
When Set next power-on time is set to Change next power-on time for the remote power control job, the next specified power-on time operates according to the time specified in the time zone of the execution user on the host that is executing the job.
-
The time set in the Valid range of start condition operates according to the time zone on the manager host.
-