JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 7

changes.mady.by.user Robert Ehrlich

Saved on

compared with

New Version 8

changes.mady.by.user Robert Ehrlich

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SettingDefaultExplanation
workflowConfig.default.timezoneEtc/UTC

Specifies the default time zone that is added to converted workflows. This time zone for example is applied to JS7 - Admission Times for Jobs.

See List of tz database time zones

Section: Workflow Job

SettingDefaultExplanation
jobConfig.forced.GraceTimeout
15

Specifies the grace timeout after which a running job is terminated if the cancel/force operation is used, see JS7 - Job Instruction.
jobConfig.forced.parallelism
1

Specifies the number of parallel tasks that a job can be running for, see JS7 - Job Instruction.

jobConfig.forced.failOnErrWrittenfalseSpecifies the handling of job output to the stderr channel. If set to true then output to stderr is considered an error, otherwise such output is logged and no error is raised, , see JS7 - Job Instruction.
jobConfig.forced.warnOnErrWrittenfalse

Specifies the handling of job output to the stderr channel. If set to true then output to stderr is considered a warning, otherwise such output is logged and no warning is raised, , see JS7 - Job Instruction.

jobConfig.forcedV1Compatiblefalse

JS7 workflows can be operated in a JS1 compatibility mode. If set to true then

  • for order variables and workflow variables in shell jobs respective environment variables are created that are prefixed with SCHEDULER_PARAM_ followed by the uppercase variable name.
  • for job arguments of shell jobs accordingly environment variables are created.

Consider that environment variables are not added by the Converter but are created on-the-fly by the Controller and Agents.

jobConfig.forced.retry.maxTries

Forces use of the indicated maximum for use of the JS7 - Retry Instruction. Without this setting the AutoSys® n_retrys option is used to specify the maximum number of retries. 

jobConfig.forced.retry.delays

Forces the indicated delay between retries.

jobConfig.forced.shell.unix.commandPrefix

Forces a prefix to be used for Unix shell jobs.

Example:

jobConfig.forced.shell.unix.commandPrefix = source

jobConfig.forced.shell.windows.commandPrefix

Forces a prefix to be used for Windows shell jobs.

jobConfig.default.shell.unix.shebang#!/bin/bash

Specifies the shebang to be inserted to the begin of job scripts:

Example:

jobConfig.default.shell.unix.shebang = #!/bin/sh

Section: Agent

SettingsDefaultExplanation
agentConfig.forced.forcedControllerIdcontrollerId
Forces use of the given ControllerId for all generated agents.
agentConfig.defaultControllerIddefault.controllerId
Specifies This setting specifies the ControllerId to be used for generated agents if the Master ID in JS1 (process_class.spooler_id) is emptyno ControllerId is provided in the agentConfig (forced.agent, default.agent, mappings) for a specific agent.
agentConfig.forcedAgentforced.agent

Forces use of the given Agent for all converted jobs.

Agent definition:

  • Expects a JSON value.
  • The JSON can be provided as:
    • JSON text
      or
    • JSON include file (relative to the properties file)
  • JSON elements:
    • NameDefaultExplanation
      platformUNIXForces use of the UNIX or WINDOWS platform.
      subagentClusterId
      		Forces use the given subagentClusterId for converted jobs when an agentCluster is used.
      standaloneAgent
      		See agent-schema.json.
      agentCluster
      		See clusterAgent-schema.json.
  • Examples:
    • {"platform":"UNIX"}
      • Forces use of the UNIX platform for all converted jobs.
    •  {"standaloneAgent":{"url":"http://localhost:4445"}}
      • Forces use of the standalone Agents in all converted jobs with the given url.
    •  {"platform":"UNIX", "standaloneAgent":{"agentName":"forced_agent", "url":"http://localhost:4445"}}
      • Forces use of a standalone Agent forced_agent in all converted jobswith the given url.
agentConfig.default.defaultAgentagent
NameURL
default_agenthttp://localhost:4445

Without an Agent being specified the JS1 executes jobs with the Master. In JS7 an Agent has to be used. This setting specifies an Agent that is used for jobs that are executed with a Master in JS1.

The syntax for assignments: see agentConfig.forcedAgent Agent definition.

agentConfig.mappings

By default the Converter handles the mapping of Agent Names found in JS1 process classes (<process_class>) like this:

  • Agents are determined by the unique URL assigned the Agent in existing process classes.
  • The name of a process class is mapped
    • to a Standalone Agent if it includes a single Agent
    • to a Cluster Agent if it includes more than one Agent

The syntax for mapping includes:

<js1-agent-name>=<Agent definition>

<js1-agent-name> is the name of the JS1 Agent.
<Agent definition> see agentConfig.forcedAgent Agent definition..

Example:

js1_agent1={"platform":"UNIX", "standaloneAgent":{"agentName":"primaryAgent", "url":"http://unix:4445"}};js1_agent2={"platform":"WINDOWS", "standaloneAgent":{"agentName":"secondaryAgent", "url":"http://win:4445"}}

  • The process class js1_agent1 is mapped to the JS7 Agent with the name primaryAgent that is operated for Unix.
  • The process class js1_agent2 is mapped to the JS7 Agent with the name secondaryAgent that is operated for Windows.

or

 js1_agent1=examples/agent_standalone.json; js1_agent2=examples/cluster_agent.json

  • The process class js1_agent1 is mapped to the JS7 Agent defined in the examples/agent_standalone.json file.
  • The process class js1_agent2 is mapped to the JS7 Agent defined in the examples/cluster_agent.json file.

Any number of mappings are specified separated by a semicolon. This setting can be split across a number of lines by use the "\" line continuation character at the end of each line that should be continued.

...