OS 2200 Job Details
What Is It?
An OS 2200 job defines a Unisys ECL (Executive Control Language) runstream for OpCon to start and monitor on an OS 2200 Agent. The OS 2200 job details are organized into tabs: Job Information, Tokens, and either File Dependencies or Prerun Information, depending on the dependency type you select.
Text fields in the graphical interfaces support OpCon token replacement. For additional information about this platform, refer to OS 2200 Agent and BIS LMAM Configuration in the OS 2200 Agent online help.
Job Information
The Job Information tab defines the runstream OpCon submits to the Exec. It contains the Start Command and Run Card Control groups, the completion status settings, and the dependency type selector.
Start Command
| Field | What It Does |
|---|---|
| Qualifier | Qualifier of the ECL file. |
| File Name | Filename of the ECL file. |
| Element Name | Element name of the file containing the ECL. Include the version when needed (for example, ELT/VERSION). |
| Priority | Priority placed on the start statement when submitting the job to the Exec. Accepts alphabetic characters. |
| Options | Valid options for inclusion on the start statement. Accepts the characters B D N O P R S T W X Y (uppercase or lowercase). |
| Condition Word (Octal) | Octal number placed in the middle third of the condition word for this job. Sets T2 of the run's condition word — the "set" parameter of the start statement. Defaults to 0000. |
Run Card Control
| Field | What It Does |
|---|---|
| Run ID | Identifies the run to the Exec and replaces the Run ID on the @RUN card of the ECL. |
| Account | Account code used for billing purposes and on the start statement. |
| User ID | User of the account, used with the account code on the start statement. When User ID is -SECURITY-, the Agent issues an ST <ELT> to start the job, allowing security officer jobs to start from SYS$LIB$*RUN$ when Auto Answer for Security is on. |
| Project | Project for file access and accounting purposes, used on the start statement. |
| Max Pages | Maximum value for page generation, used on the start statement. Defaults to 0000. |
| Max Cards | Maximum value for card generation, used on the start statement. Defaults to 0000. |
Qualifier, File Name, and Element Name are required.
Agent Resolved Dependencies
The Agent Resolved Dependencies field indicates whether the job includes a Prerun job or a file dependency. The available values are:
| Value | What It Does |
|---|---|
| <None> | No Agent-resolved dependency. |
| File | The job depends on one or more files. Define them on the File Dependencies tab. |
| Pre Run | The job runs a Prerun ECL first. Define it on the Prerun Information tab. |
Prerun Information
When Agent Resolved Dependencies is set to Pre Run, the Prerun Information tab uses the same fields as Start Command, Run Card Control, and the completion status settings described for Job Information.
- The Prerun ECL is an ECL that runs immediately before the job defined in Job Information.
- When the Prerun ECL terminates with an error, it is rescheduled at a user-defined interval. See Time Settings.
- The Prerun ECL continues running at the defined interval until it succeeds, after which the Job Information ECL runs. The primary purpose of a Prerun is to test required preconditions for the job.
File Dependencies
When Agent Resolved Dependencies is set to File, define up to eight file dependencies on the File Dependencies tab. Each dependency uses the following fields:
| Field | What It Does |
|---|---|
| Qualifier | Qualifier for the file dependency. Placing # before or after the qualifier directs the Agent to search the SHARED File Directory; without #, the Agent searches the STD File Directory. |
| Filename | Filename the ECL depends on. |
| Type | Type of dependency the ECL has on the file. See the table below. |
| Size | File size value. Required when Type is Size. Accepts up to three digits. |
The Type field offers the following values:
| Type | What It Does |
|---|---|
| Exists | The file must exist. |
| Created | The file must exist and have been catalogued today. |
| Deleted | The file must not exist. |
| Size | The file exceeds the entered Size value. |
| Referenced | The file has been referenced today. |
| Assigned | The file is currently assigned. |
| Backed Up | The file has a current backup (backed up and not yet modified). |
| Unloaded | The file is currently unloaded. |
Completion Status Based on Condition Word
Upon termination of an Agent-started job, the run condition word is evaluated for completion status. You can define up to four condition tests, plus a default status that applies when no test matches. User-defined values can be used for range testing of any standard division of the condition word.
| Field | What It Does |
|---|---|
| And/Or | Determines the association between multiple tests. Available on the second through fourth tests. Values: None, OR, AND. |
| Word Part | Portion of the word to analyze. Values: S1, S2, S3, S4, S5, S6, T1, T2, T3. |
| Condition | Condition code specifying how the word part is tested. See the table below. |
| Value | Value associated with the Condition, entered as a four-digit decimal value. When Condition is Range, this is the starting decimal value (the decimal equivalent of the octal value). |
| End Value | Ending decimal value when Condition is Range. Must be greater than Value. Enabled only when Condition is Range. |
| Fin Status | Whether the condition word test describes a GOOD FIN or a BAD FIN. |
| Anything Else | Final status for the job when a received error code is not defined in this section. Undefined conditions are treated as GOOD FIN or BAD FIN based on this value. |
The Condition field offers the following values:
| Condition | What It Does |
|---|---|
| LAND | Logical AND between the associated Value and the run's condition word. |
| EQ | Equal. |
| NE | Not equal. |
| GT | Greater than. |
| LT | Less than. |
| GE | Greater than or equal to. |
| LE | Less than or equal to. |
| Range | Range of values, from Value to End Value. |
The following example is a LAND (Logical AND) condition. A job has the run condition word test defined as follows:
S6 LAND 0016 (decimal equivalent of an octal 20) = BAD FIN
or ANYTHING ELSE = GOOD FIN.
If S6 = 0001 (octal)
000 001 Bits in S6 part of run's condition word
010 000 Logical AND of bits by the Agent (octal 20, decimal 16)
000 000 Result of Logical AND
The job terminated normally (GOOD FIN)
If S6 = 0020 (octal)
010 000 Bits in S6 part of run's condition word
010 000 Logical AND of bits by the Agent (octal 20, decimal 16)
010 000 Result of Logical AND
The job terminated abnormally (BAD FIN)
If S6 = 0063 (octal)
110 011 Bits in S6 part of run's condition word
010 000 Logical AND of bits by the Agent (octal 20, decimal 16)
010 000 Result of Logical AND
The job terminated abnormally (BAD FIN)
Tokens
Tokens substitute variable data into a job's runstream when the job runs. On the Tokens tab, associate literal tokens or OpCon tokens with strings that are matched and replaced in the ECL. Separate multiple token equations with a comma (,). The Tokens field accepts up to 250 characters.
?SCHEDNAME?=[[$SCHEDULE NAME]],?MY TOKEN?=[[MYVALUE]]
- When the ECL contains
?SCHEDNAME?, those characters are replaced with the schedule name by equating it to the OpCon Schedule Name token:?SCHEDNAME?=[[$SCHEDULE NAME]]. - OpCon replaces
[[$SCHEDULE NAME]]with the literal schedule name. The OS 2200 Agent searches the ECL for?SCHEDNAME?and replaces the string character by character with the resolved schedule name from the SAM. Ensure the resulting ECL statement does not violate ECL syntax rules.
The following tokens are resolved by the OS 2200 Agent and do not require definition:
| Token String | Equates To |
|---|---|
????????OPCON-JOBID???????? | Full OpCon Job ID (27 characters) |
???JOB-ID??? | OpCon Job ID (first 12 characters) |
?JOB-ID? | OpCon Job ID (first 8 characters) |
?RNID? | Job's Run ID (6 characters) |
FAQs
Q: What is the basic information needed to define an OS 2200 job?
An OS 2200 job requires a Qualifier, File Name, and Element Name for the ECL file, plus an optional Priority, Options, and Condition Word (Octal) value.
Q: Does the OS 2200 job type support OpCon token replacement?
Yes. Text fields in the graphical interfaces support OpCon token replacement. Tokens are resolved as the SAM prepares to send the job to the Agent.
Q: What special tokens are available for OS 2200 jobs?
OS 2200 supports tokens such as ???JOB-ID??? (OpCon Job ID, first 12 characters), ?JOB-ID? (first 8 characters), and ?RNID? (the job's 6-character Run ID).
Q: How many file dependencies and completion status tests can a job have?
A job can define up to eight file dependencies and up to four completion status tests, plus a default completion status.
Glossary
SAM (Schedule Activity Monitor): The logical processor for OpCon workload automation. SAM monitors schedule and job start times, dependencies, and user commands to determine when jobs run, and processes OpCon events.
Agent: An application installed on a target platform that runs jobs in the native language of that platform and reports results back to OpCon. Agents are defined as Machines in OpCon.
Token (Global Property): A named value stored in the OpCon database, referenced in job definitions and events using [[PropertyName]] syntax. Tokens pass dynamic values — such as dates, file paths, or counts — into automation.
Schedule: A named container for jobs in OpCon, built for a specific date to create that day's automation. Schedules define build settings, frequencies, and the jobs that run within them.
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.
OpCon: Continuous' workload automation platform. The OpCon server includes the database, SAM and Supporting Services (SAM-SS), and graphical user interfaces. Agents installed on target platforms run jobs and report results.