JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

The JS7 Controller, Agents and JOC Cockpit make use of Unicode. When files are created or used then UTF-8 encoding applies.

  • Unicode support works across any supported JS7 - Platforms.
  • Limitations have to be considered in mixed environments that include the Windows OS without Unicode support.

JOC Cockpit

When designing workflows with the Configuration -> Inventory view users can make use of any Unicode characters within the scope of JS7 - Object Naming Rules.

Configuration View

The Configuration -> Inventory view allows to specify object names and job scripts using Unicode characters:

  • JOC Cockpit requires the JS7 - Database to support UTF-8 encoding in order to store objects that hold such characters.
  • The same applies to the JDBC Driver in use. All vendors of supported DBMS offer Unicode support.

Workflows View

The Workflows view displays workflows using Unicode characters accordingly:

  • The below example makes use of Japanese object names.
  • In addition the JOC Cockpit interface language is switched to Japanese by use of JS7 - Profiles - Preferences.

Log View

The Log view window displays output of jobs and instructions.

  • Partly output is created from JOC Cockpit and is qualified with markers such as [MAIN], [SUCCESS], [DETAIL].
  • Partly output is created from job scripts executed with an OS shell. Such output is marked as [STDOUT] and [STDERR].


Explanation:

  • Output from Unix Operating Systems
    • Unix OS have built-in support for Unicode and UTF-8 encoding.
  • Output from Windows Operating Systems
    • Windows does not offer Unicode. Instead the OS ships with different codepages preinstalled depending on the location in which the OS is used.
    • Some experimental support is available starting from Windows 10, however, as most Windows programs are not aware of Unicode there can be side-effects.
    • Therefore the encoding of output created by jobs depends on the codepage in use for the respective Windows OS for which an Agent is operated.

Controller



Agent





  • No labels