Regional settings

Missing or incorrect code page and time zone settings might cause unexpected results, such as garbage in retrieved job logs or incorrect job run times. The following sections provide a simple check list to prevent this kind of problems.

Code page

At host side, you can set the code page by specifying TOPOLOGY(CODEPAGE()) in the server and batch initialization statements. The input translator and the fault tolerant agent (FTA) use the specified value to convert received data, from UTF-8 format to EBCIDIC format and conversely.

At distributed side, to verify the active code page you can use operating system specific commands, for example the chcp command for Windows and locale for UNIX. Moreover:

• Verify that the TWS_TISDIR environment variable is set to the name of the Tivoli® Workload Scheduler home directory.
• To handle jobs containing some national characters on a Windows workstation, add the chcp code_page command to the TWS_home\jobmanrc file, where code_page is the code page including those national characters.

Time zone

In an end-to-end with fault tolerance capabilities environment, the work is scheduled in terms of controller local time. When adding time-dependent jobs to the Symphony™ file, the scheduler converts that time to the local time of the FTA. The conversion is first from controller local time to GMT, then from GMT to FTA local time. The conversion succeeds only if the following conditions occur:

• At host side:
  • You correctly set the local and GMT clocks.
  • The USS $BINDIR/zoneinfo directory contains correct time zone definitions.
  • For each workstation referenced through the TPLGYMEM statement, server and batch initialization statements contain a CPUREC(CPUTZ()) value matching the time zone value of the operating system where the agent runs.
• At distributed side, you correctly set clock and time zone values for the operating system hosting each agent.