This tab includes basic identification properties including: the method name, description and date and time of the Execution Method's last revision.

Method Name

This is the unique identifier for the Execution Method parameter.

Description

This reference property is used to summarize the Execution Method definition.

Last Changed

Indicates the date and time this Execution Method parameter was last modified.

The Source tab is used to specify certain values for a Job, including Job Modules, which reference macros in a template file.

Job Module

This is the name of a text module in the template library which is used as the starting point for parsing the Job's command procedure. Entering a value in this property implies that this Job is parsed.

The template library is a combination of the macros in the BaseMacros.xml file, the file specified in the "DefaultMacroFile" configuration setting and the macros in the xml file specified in the Job's Folder definition. The BaseMacros.xml file is replaced when installing a JAMS upgrade.

Caution: If you want to add custom macros you should avoid putting them in the BaseMacros.xml so that you don't lose them during an upgrade.

Note: that you can specify the starting point for parsing using either the Job Module property or the Template tab. However, you cannot use both.

Default File Extension

Enter the default file extension for the Job's command procedure.

Options (Checkboxes)

• Interactive: when enabled, this Execution Method can interact with the desktop. Caution: this setting is not recommended since it can lead to potential security issues. The Interactive property has been included here because some applications require access to the desktop in order run properly.
• Single Command: when activated, the Execution Method uses a command instead of a command procedure.
• Snapshot Source: If enabled, the option allows JAMS to grab a copy of the source when submitting a Job.
• Host Locally: Indicates that the Job should only be hosted by the machine running the JAMS Scheduler. This setting is used for Execution Methods that need to manage connection to the Agent machine. An example would be the SSH Execution Method which executes locally and uses SSH to connect to the Agent in order to run the actual job.
• Allow Edit on Submit: when activated, this checkbox permits the source to be edited when manually submitting the Job.
• Allow Edit After Start: when activated, this setting permits the source to be edited after a manually submitted Job has started.

This tab incorporate several sections that are detailed below:

Type

This dropdown allows you to choose the Execution Method type. The supported types are:

• Agent runs a Job using a JAMS Agent.
• Batch runs a Job by creating a process with a Job or Command.
• Routine executes a Job using the specified class from a specified assembly using the IJAMSHost interface.
• Rexec runs a Job by connecting to a rexec daemon.
• SSH Agent executes a Job using a secure shell commands with JAMS AgentX.

Options

This property specifies options unique to the Execution Method and IJAMSHost implementation.

Create Process

Includes values that are passed to CreateProcess as the application or command argument.

• Application: is the value passed to CreateProcess as the application argument.
• Command: is the value passed to CreateProcess as the command argument.

Routine Location

This is used when the type is set to Routine. When JAMS executes the Job it loads the specified assembly, class and call methods from the IJAMSHost interface.

• Assembly: the assembly name containing the class.
• Class: the class that executes the job. This class must implement IJAMSHost.

Source Editor

The Source Editor is used by the JAMS Client to edit the Job’s source code. When using a text editor make sure to leave the Assembly and Class properties empty. You can create custom editors for each custom Execution Method. Each editor displays on the Job definition’s Source tab.

Viewer

This is used for viewing the progress of an executing Job, which is often a Workflow Job.

• Assembly: the assembly name containing the class.
• Class: the class that executes the job. This class must implement IJAMSHost.

Exit Code Handling

This dropdown controls how a processed exit code should be interpreted. Depending on the Exit Code Handling selection, choose the specific parameter values listed below:  

• ZeroIsGood
• OneIsGood
• EvenIsGood
• OddIsGood
• PositiveIsGood
• MessageCode
• OpenVMSMessageCode
• SpecificGood
• SpecificBad
• MinimumValue

 Enter the Minimum, Informational and Warning values.

Regular Expression Patterns

Specify a regular expression pattern that is matched against both success and error log file outputs.

Execution Method parameters work the same way as Parameters within Job definitions and apply to all Jobs using this Execution Method. To insert a new Parameter, select the Add button on the Parameters tab to access the Add a Parameter wizard.

Note: if a Job has a Parameter with the same name as the Execution Method Parameter, the Job definition is used.

For a description of Parameters, go the topic: Job Properties – Parameters.

Templates provide an easy way to include standard pre and post processing for your Jobs.

At submit time JAMS parses a Job source using either the template defined on this tab or the module defined in the Job Module property for the Job’s source code. Use the built-in text editor to edit the template for this Execution Method.

The example below sets up a simple template that maps two network drives, inserts the Job’s source code and executes a LogJobComplete program:

NET USE E: \\MyServer\EShare
NET USE F: \\MyServer\FShare
<<JAMS.Current.Source>>
C:\LogJobComplete.exe <<JAMS.Job.JobName>>

Dashboards and Reports