OS 2200 Job Details

Theme: Configure
Who Is It For? Automation Engineer

What Is It?

This section applies to defining an OS 2200 job. Text fields in the graphical interfaces support OpCon token replacement. For additional information about this platform, refer to OS 2200 LSAM and BIS LMAM Configuration in the OS 2200 LSAM online help.

Job Information

Start Command

• Qualifier: Qualifier of the ECL file
• File Name: Filename of the ECL file
• Element Name: Element name of the file containing the ECL; include Version when needed (e.g., ELT/VERSION)
• Priority: Priority placed on the start statement when submitting the job to the Exec
• Options: Valid options for inclusion on the start statement
• Condition Word (octal): Octal number placed in the middle third of the condition word for this job (sets T2 of run's condition word, the "set" parameter of the start statement)

Run Card Control

• 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 = "-SECURITY-", 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 and Max Cards: Maximum values for page and card generation, used on the start statement

agent Resolved Dependencies

Indicates whether the job includes a Prerun job or a File dependency. Valid values: <None>, Pre Run, File.

Prerun Information

If Pre Run is set for agent Resolved Dependencies, define the Prerun Information using the same fields as Start Command and Run Card Control (see Job Information above).

• Specifies an ECL to run 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, then the Job Information ECL runs. The primary purpose of a Prerun is to test required preconditions for job execution

File Dependencies

If File is set for agent Resolved Dependencies, define the following fields:

• Qualifier: Qualifier for the file dependency. Placing # before or after the qualifier directs the agent to search the SHARED File Directory; without # indicates the STD File Directory
• File Name: Filename the ECL depends on
• Type: Type of dependency the ECL has on the file:
  • Exists: The file must exist
  • Created: The file must exist and was 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
  • BackedUp: 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. User-defined values can be used for range testing of any standard division of the condition word.

• And/Or: Determines the association between multiple tests
• Word Part: Portion of the word to analyze. Valid values: S1–S6 and T1–T3
• Condition: Condition codes specifying how the word part is tested:
  • Streamlined workflow: Logical AND between the associated Value and the run's condition word
  • LT: Less than
  • EQ: Equal
  • GE: Greater than or equal to
  • NE: Not equal
  • LE: Less than or equal to
  • GT: Greater than
  • Range: Range of values

Example

The following example is an "L AND" condition. A job has the run condition word test defined as follows:

S6 L AND 0016 (decimal equivalent of an octal 20) = BAD FI
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 LSAM (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 LSAM (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 LSAM (octal 20, decimal 16)
010 000 Result of Logical AND
The job terminated abnormally (BAD FIN)

• Value: Value associated with the Condition. When Range is the Condition, enter the starting decimal value (decimal equivalent of the octal value)
• End Value: Ending decimal value when Range is the Condition. Must be greater than Value
• Fin Status: Whether the condition word test describes a GOOD FIN or 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 option

Tokens

Tokens substitute variable data into a job's runstream at execution time. Associate literal tokens or OpCon tokens with strings matched and replaced in the ECL. Separate multiple token equations with a comma (,).

Example

?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 LSAM 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 LSAM 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)

  : OS 2200 Token Resolution

Configuration Options

Setting	What It Does	Default	Notes
Qualifier	Qualifier of the ECL file	—	—
File Name	Filename of the ECL file	—	—
Element Name	Element name of the file containing the ECL; include Version when needed (e.g., ELT/VERSION)	—	—
Priority	Priority placed on the start statement when submitting the job to the Exec	—	—
Options	Valid options for inclusion on the start statement	—	—
Condition Word (octal)	Octal number placed in the middle third of the condition word for this job (sets T2 of run's condition word, the "set" parameter of the start statemen...	—	—
Run ID	Identifies the run to the Exec and replaces the Run ID on the \@RUN card of the ECL	—	Valid values: <None>, Pre Run, File.
Account	Account code used for billing purposes and on the start statement	—	Valid values: <None>, Pre Run, File.
User ID	User of the account, used with the account code on the start statement.	—	Valid values: <None>, Pre Run, File. ## Prerun Information
Project	Project for file access and accounting purposes, used on the start statement	—	Valid values: <None>, Pre Run, File. ## Prerun Information
Max Pages and Max Cards	Maximum values for page and card generation, used on the start statement	—	Valid values: <None>, Pre Run, File. ## Prerun Information If Pre Run is set for agent Resolved
Type	Type of dependency the ECL has on the file:	—	—
And/Or	Determines the association between multiple tests	—	Valid values: S1–S6 and T1–T3. - Condition: Condition codes specifying how the word part is tested: - **L AN
Word Part	Portion of the word to analyze.	—	Valid values: S1–S6 and T1–T3. - Condition: Condition codes specifying how the word part is tested: - **L AN
Condition	Condition codes specifying how the word part is tested:	—	—
Value	Value associated with the Condition.	—	Must be greater than Value. - Fin Status: Whether the condition word test descri
End Value	Ending decimal value when Range is the Condition.	—	Must be greater than Value. - Fin Status: Whether the condition word test descri
Fin Status	Whether the condition word test describes a GOOD FIN or BAD FIN	—	—
Anything Else	Final status for the job when a received error code is not defined in this section.	—	—

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 like ???JOB-ID??? (OpCon Job ID, first 12 characters), ?JOB-ID? (first 8 characters), and ?RNID? (the job's 6-character Run ID).

Glossary

SAM (Schedule Activity Monitor): The logical processor for OpCon workflow automation. SAM monitors schedule and job start times, dependencies, and user commands to determine job execution timing, and processes OpCon events.

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.

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 workflows.

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' workflow 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.