BS2000 Jobs

This subtype of the JOBS object is used to run scripts on BS2000 platforms and to define how runtime options, reports and protocols must be processed. Like all other job objects (JOBS), BS2000 jobs can run independently or they can be added to a group (JOBG) or to a workflow.

The page contains the BS2000-specific execution parameters:

Runtime Options Section

The following table describes the available options:

Field Description
Priority

The priority with which the job should be executed. It is a value between 1 and 255, where 1 is the highest and 255 the lowest priority.

The priority does not affect the processing order of tasks, it only serves to define their starting order. The task with the higher priority is started first. For tasks with the same priority, the Fist In/First Out (FIFO) principle applies.
Maximum CPU Time Maximum CPU time (in seconds) that is available for the job. If the value that is specified here is exceeded, the OS cancels the job, which then gets the ENDED_VANISHED status.
Express

If a batch limit has been defined on the agent, this can prevent the job from being started. Activate this checkbox to ignore this setting. As a result, the job is started immediately regardless of the batch limit.
Job Class It can contain up to 8 characters.
Order Name It can contain up to 8 characters.
Enter Parameter

You can specify any number of enter parameters separated by commas.

The parameters that are allowed depend on the BS2000 version. A detailed description is available in the BS2000/OSD Commands manual under the /ENTER-JOB command.

For example:

TIME=NTL, RERUN-AFTER-CRASH=YES

Parameters that have already been defined cannot be used again (max. CPU time, priority, express, job class, order name).

You can enter up to 255 characters here.

Job Report Section

The following table describes the available options:

Field Description
Store to
  • Database: As soon as the job has been processed, the process log available on the target system is stored in the database.
  • File: The process log is stored as a file on the target system.

You can select one option or both of them simultaneously.
Generate

Define when the operating system process log is written.

  • Always: The process log is always written.
  • On error only: The process log is written only when an error occurs, for example, when the job is canceled or aborted.

SysLst Section

The following table describes the available options:

Field Description
Store to
  • Database: As soon as the job has been processed, the SysLst protocol is transferred to the database via a file transfer.
  • File: As soon as the job has been processed, the SysLst protocol is available as a file in the target system.

You can select one option or both of them simultaneously.
Generate

Define when the operating system process log is written.

  • Always: The process log is always written.
  • On error only: The process log is written only when an error occurs, for example, when the job is canceled or aborted.

Freely Defined Port Numbers

Free port number are usually supplied in the DCSOF with the Freeport parameter. By default, the first free port number is 4096.

The BS2000 agent does not work with a fixed port number that is written in to its INI file, but it requests a free port number when it establishes a connection to the Automation Engine.

If the BS2000 agent is automatically loaded after a successful agent test start, make sure that its required free port number does not conflict with other settings.

Example

The test results in the following constellation:

  1. An application that uses the 4096 port number via /BCMAP command is already running.
  2. The BS2000 agent is started manually and obtains the next free port number (e.g. 4097).

In this case, both, the application and the agent work correctly.

After the tests, the BS2000 agent starts automatically and is loaded before the application. The BS2000 agent obtains the first free port number 4096.

As a result, the application to which this port number has been assigned on a fixed basis via a /BCMAP command cannot start.

The list below tries to depict a possible road-map to define and work with Job objects and provides short descriptions of the actions you can take, additional information that can help you understand how they work and links to topics that further describe them:

  1. Define the job general settings, which include the following:

    • The basics, on the General Page.
    • If required, apply a Sync object to the job; You do so on the Sync Page.
    • On the Runtime Page specify the job runtime settings.
    • Fine-tune access rights at object level on the Authorization Page.
    • Specify the object Attributes on the Attributes Pages of Executable Objects.
    • Register the output files that will be produced when processing them on the Output Page.
    • To be able to carry out searches in those output files and, if required, perform follow-up actions, specify these settings on the Output-Scan Page.
    • You may want to use variables or prompts. You do so on the Variables & Prompts Pages.
    • You may want to define the settings to backup and restore a job task when included in a workflow. This is useful to recover the last successful status in case of failed processes. You do this on the Rollback Page.
    • The Version Management Page lists all the versions of an object and allows you to restore it to an older version in case of a misconfiguration.
    • Enter information on the job you are defining on the Documentation Page.

  2. Job objects (JOBS) have three pages on which you enter the scripts to be processed. They provide a number of convenience functions to help you with your work. If you enter scripts on all of them, they are processed in the following order:

    1. Pre-Process Page
    2. Process Pages
    3. Post-Process Page
    4. Child Post-Process (SAP and PeopleSoft only), see Child Post-Process Page.
  3. You can easily reuse code using Include Object (JOBI), which saves time and helps you keep your scripts consistent.

  4. Execute the job.

    There are multiple ways to do this that can be grouped as follows:

    • By a parent task.

      This is the case of jobs that are included in a parent object (for example a Workflow or a Group). When defining them, take into account that their activation time can be different from their start time; the latter usually depends on the parent object.

      See Superordinate Tasks (Parents).

    • Stand alone

      This is the case when the job is not part of a parent object or, even if it is, you execute it independently of its parent. You have three possibilities:

    When executable objects are processed, they go through the following four stages: 1. Activation, 2. Generation, 3. Processing and 4. Completion. Take a look at these topics to understand what happens with every processing stage.

  5. When processing jobs, the Automation Engine generates output files and reports that guarantee traceability and auditability. Have a look at the following topics to learn more about this:

  6. In the Process Monitoring perspective a number of functions are available, depending on the status of the job. See Working with Tasks.