Skip to main content
Version: OpCon 26.0 (On-Prem)

Viewing, Adding, and Editing Windows Job Details

Theme: Configure
Who Is It For? System Administrator, Automation Engineer

What Is It?​

Windows job details define how OpCon executes a job on a Windows agent, including the command line, working directory, run in command shell setting, and failure criteria. These details are configured in the Task Details panel of a Windows master job in Solution Manager.

To view, add, or edit a Windows job, you must have the required privileges as defined in Required Privileges.

Viewing Windows Job Details​

  1. Go to Library > Master Jobs
  2. Select a Windows job in the list
  3. Select Edit
  4. Expand the Task Details panel

Adding Windows Job Details​

To add Windows Job Details, complete the following steps:

  1. Create the job and general info as described in Adding a Job
  2. Expand the Task Details section
  3. Select a User Id for Windows security authentication
  4. From the Machines or Machine Group list, select the machine where the agent is installed. To use a machine group instead, toggle the Machines switch to Machine Group and select the group. The switch appears green when toggled
  5. Select a Job Action:

Editing Windows Job Details​

To edit Windows Job Details, complete the following steps:

  1. Go to Library > Master Jobs
  2. Select a Windows job and select Edit
  3. Select the lock icon to switch modes. The button appears gray and locked (Master Job Definition Read-only Button) in Read-only mode and green and unlocked (Job Definition Admin Button) in Admin mode
  4. Expand the Task Details panel
  5. From the Machines or Machine Group list, select the machine where the agent is installed. To use a machine group, toggle the Machines switch to Machine Group and select the group. The switch appears green when toggled Green Enabled Switch
  6. Select a User Id for Windows security authentication
  7. Select a Job Action:

Run Program​

In the Prerun frame:

To run Program, complete the following steps:

  1. Optional: Enable the Prerun switch Green Enabled Switch
    1. Enter the command line detail for the prerun process (up to 4000 characters)
    2. Enter the working directory for the prerun job (up to 255 characters)
  2. Specify failure criteria by selecting an operator and entering an exit code integer
  3. Enter the command line detail with the full path to the executable on the agent machine (up to 4000 characters)
  4. Enter the working directory for the job (up to 255 characters)
  5. Enter the full path to the Exit Code Override File (E.C.O.F) (up to 255 characters)
  6. Set the Windows process priority: Idle, Normal, High, or Real Time
  7. Specify failure criteria for the job by selecting an operator and entering an exit code integer
  8. Specify whether the criteria determine if the job Failed or Finished OK
  9. Select the green Add button (+) to define parsing criteria:
    1. Select the Search Operation
    2. Enter the String to Search (Windows wildcards supported; up to 255 characters)
    3. Select or enter the Exit Code
  10. Select the green Add button (+) to define environment variables:
    1. Enter a name in the Name field
    2. Enter a value in the Value field. To remove a variable, select Delete at the end of the row
    3. Select OK to add the name/value pair
  11. Select Save

File Arrival​

  1. Enter the file path and name in the File Name field (Windows wildcards supported, e.g., C:\Folder\Filename?ABC*.txt; up to 4000 characters)
  2. Specify the Start Time and End Time within which the file must arrive
  3. Specify the Duration in seconds that the file size must remain stable
  4. Specify failure criteria by selecting an operator and entering an exit code integer
  5. Specify whether the criteria determine if the job Failed or Finished OK
  6. Select Save

Embedded Script​

For conceptual information, refer to Embedded Scripts in the Concepts online help.

note

If you do not have the Script Privilege for the script, you will not be able to see the task details or edit the daily job definition (the Lock button will be disabled).

  1. Select the script to associate with the job. The Type field populates automatically
  2. Select the version (or revision) of the script to run. The Comments field populates with any notes about the script
  3. Select the runner (interpreter). The Run Command Template field populates with the runner syntax
  4. Enter any arguments to pass to the script at runtime (up to 4000 characters)
  5. Enter the working directory for script execution (up to 255 characters)
  6. Select an operator and enter or select the exit code integer
  7. Specify whether the criteria determine if the job Failed or Finished OK
  8. Select the green Add button (+) to define environment variables:
    1. Enter a name in the Name field
    2. Enter a value in the Value field. To remove a variable, select Delete at the end of the row
    3. Select OK to add the name/value pair
  9. Select Save

More Information​

For conceptual information, refer to Windows Jobs in the Concepts online help.

Configuration Options​

SettingWhat It DoesDefaultNotes

FAQs​

Q: How many steps does the Viewing, Adding, and Editing Windows Job Details procedure involve?

The Viewing, Adding, and Editing Windows Job Details procedure involves 42 steps. Complete all steps in order and save your changes.

Q: What does Viewing, Adding, and Editing Windows Job Details cover?

This page covers Viewing Windows Job Details, Adding Windows Job Details, Editing Windows Job Details.

Q: What are the three job actions available for a Windows job in Solution Manager?

Windows jobs in Solution Manager support three job actions: Run Program (executes a command or application), File Arrival (monitors for an incoming file within a specified time window), and Embedded Script (runs a script stored in the OpCon Script Repository).

Glossary​

LSAM (Local Schedule Activity Monitor): An agent installed on a target platform that runs jobs in the native language of that platform and communicates results back to SAM via SMANetCom over TCP/IP.

Embedded Script: A script stored and versioned directly within the OpCon database. Embedded scripts can be assigned to Windows jobs and run at runtime without requiring the script file to exist on the target machine.

Resource: A numeric variable in OpCon representing a finite pool. Jobs can be configured to require a set number of resource units to run, limiting concurrent executions and preventing resource contention.

Privilege: A specific permission granted through an OpCon role that controls access to a feature, function, or object type. Privileges are organized into categories such as Function Privileges, Machine Privileges, Schedule Privileges, and Access Codes.

Machine: A platform defined in the OpCon database that has an agent installed. OpCon routes job execution requests to machines via SMANetCom, and machines report job completion status back to SAM.

Job: The fundamental unit of work in OpCon. A job defines what to run, on which machine, when to start, and what conditions must be met. Job results are tracked and can trigger events and notifications.