Access Control List: Located in the JAMS Shortcuts, the Access Control list is used to define user restrictions for a variety of JAMS features and functions, including Jobs, Sequences and Variables.
ACE: Access control entries (ACE's) are used in Access Control Lists. ACL's grant or deny specific access rights to users or groups of users.
Agent:
Agents allow users to define specific actions that can run locally or remotely throughout a JAMS network.
Configuration:
These setting define many of the JAMS system-wide options are accessed from the Configuration shortcut on the Shortcut Bar.
Dashboard:
The Dashboard presents a graphical summary of information and trends within the JAMS environment.JAMS provides a variety of built-in Dashboards from which to install.
Date Types:
Date Types define the various classes of dates that are significant to your organization’s environment. This is not where you define the specific dates for these classes; rather, it is where you define the classes themselves. For example, JAMS always converts "FIRST DAY OF APRIL" to April 1st for the current calendar year. However, if your organization uses fiscal accounting periods, you may use different date structure. See Specifying Dates Using Natural Language for more details.
Dates:
Dates are definitions used to mark or schedule significant dates for batch processing.The specific dates are defined using the Dates shortcut.
Dependencies:
Dependencies are a defined precondition for running defined Jobs and Sequences. In other words, before a Job or Sequence can run, all Dependencies must be fulfilled.
Execution Method:
Defines how a Job runs in the JAMS environment. JAMS ships with dozens of predefined Execution Methods that run Jobs on Windows, UNIX, OpenVMS, and compliant operating systems. In addition, users can customize their own Execution Methods. See the topic: Execution Methods for more details.
Folder:
Contains a logical group of Jobs and Variables listed in the Definitions group. Folders can be defined by department (Accounting, IS, Sales), or by function (EDI, Web, Security, Audit), or any other way that is meaningful. At least one Folder must exist in order for JAMS to function properly.
History:
JAMS is designed to monitor all batch Jobs, even Jobs that were not submitted by JAMS. Use the History function to review what Jobs have run, their execution statistics and completion status.
JAMS:
Job Access and Management System (JAMS) is an application designed to automate and enhance all aspects of batch processing. JAMS incorporates several software components working together to provide stability, cross platform flexibility and solid security. These components include: the JAMS Client, JAMS Scheduler and Database, plus the JAMS Server.
JAMS Client:
The JAMS Client is a Windows-based ccomponent that allows users to interact with the JAMS Scheduler and JAMS Database. For more information, refer to the topic: The JAMS Client Interface.
JAMS Database:
The Database is a critical element of the JAMS Scheduler and is where all JAMS definitions are stored.
JAMS Scheduler:
This is the JAMS component that manages and submits batch processing Jobs that run on your organization’s servers. The Scheduler is also is responsible for keeping track of all Jobs and communicating their status to the JAMS Client.
JAMS Server:
The JAMS Server is a middle-tier software application service that facilitates communications between one to many JAMS Clients, the JAMS Scheduler, and JAMS Database.
Job:
A JAMS Job is a command or command procedure. Jobs contain a number of properties to ensure they run at the correct time and under the right set of circumstances. For more details, refer to the topic: Working with Jobs.
Monitor:
Displays a continually updated list of current Jobs known to the JAMS Scheduler. The Monitor also includes comprehensive Job management capabilities.
Named Times:
Provides a flexible window of times when Jobs can be scheduled and completed. JAMS can prevent Jobs from starting until their Named Time window is enabled and take various actions when a Job’s window closes before the Job completes. Named Times are defined from a Job’s property window in the Submit Times section.
Parameter:
A Parameter is a component of a JAMS Job. Parameters are similar to JAMS Variables but remain local to a Job while Variables are globally defined for all JAMS Jobs. Parameters are referred in the Job Source tab using the following syntax: <<ParameterName>> A Job can have zero or more parameters. However, if a Job does contain one or more parameters, the submitting user is presented with a fill in the blanks form with which to enter parameters values for the Job.
Parsed:
In a parsed Job, commands or batch files are generated by merging a text-based template with Job attributes, resulting in a final command or batch file which is then executed. Parsed Jobs have the added ability of embedding predefined Parameters, Variables, and Job parameter values within command or batch files.
PowerShell:
Windows PowerShell is a task automation framework from Microsoft consisting of a command-line shell and an associated scripting language built on the .NET Framework. PowerShell tasks are generally perfomed using cmdlets or specialized .NET classes implementing a particular operation. JAMS provides robust support for PowerShell allowing it to create scripts and executables. In addition, JAMS includes a PowerShell snap-in that contains over 50 JAMS-specific cmdlets, making it easy to manage, manipulate and control JAMS
Pre-Check Job:
A Pre-check Job is used to check for user defined prerequisites for a Job. When a Pre-check Job is submitted, the main JAMS Job remains in a pending state until the Pre-check Job completes successfully. JAMS automatically submits the Pre-check Job only when the main JAMS Job is ready to run.
Projected Schedule:
The Projected Schedule displays a day or week's worth of pending Jobs and Dependencies. This feature can provide managers and users with a forecasted schedule that can be helpful when a Job fails or if an ad hoc Job needs to be inserted in order to avoid interfering with other scheduled Jobs.
Queues:
Queues contain a listing of first-in-first out Jobs or Sequences that have not yet run. Queues are either in a started or stopped state and can be set to run multiple Jobs simultaneously.
Resources:
Resources are a powerful scheduling tool that allows users to define the requirements for all Jobs and Sequences and then letting JAMS decide what Jobs can run together or how many Jobs can run simultaneously.
Scheduler Tasks:
This is a shortcut that allows users to view information about scheduled Jobs running on both local and networked machines.
Sequence:
A Sequence is the best way to group multiple Jobs to run in sequence. With sequences, parameters may be passed between Jobs.
Shortcut:
A shortcut refers to objects located in the Shortcut List. The Shortcuts in the list and their order can be easily customized.
Submit window:
Is used to submit “on-demand” JAMS Jobs. This window includes a default or user defined menu hierarchy that displays all JAMS Folders. Expanding a Folder lists all Jobs and Sequences.
Triggers:
Triggers are used to define event-based schedules. A Trigger consists of events and corresponding actions. When JAMS sees that all the Trigger events are true it performs a list of defined actions.
Users:
Usernames are defined as Credentials and assigned to JAMS Folders, Jobs, and Sequences. When a Job is submitted it runs under its specified Credential and is secured via the Access Control List (AC
Variable:
Is a single piece of data that can be used as part of batch scheduling and/or processing. A Variable is similar to an environment variable, which goes away after rebooting. A JAMS Variable, on the otherhand maintains its value after a reboot.
View:
A data grid containing columns and rows of items that are opened using a shortcut. Views can provide quick access to other related JAMS elements such as: Sequences, Jobs, History, and Variables. Similar to Windows, Views can be sorted by clicking a column header.
Workflow Execution Method:
The JAMS Workflow Execution Method mirrors the type of functionality available from Sequences and is designed for Job scenarios using decision logic and branching that require different execution paths. Workflows are created and edited using the Workflow Designer which includes a menu of building blocks (Activities) for submitting Jobs, updating JAMS Variables, and many more JAMS specific tasks.