Page History
Introduction
The JS7 - Lock Instruction specifies the number of jobs for mutual exclusion to prevent such jobs from parallel execution. Exclusive Locks in the workflow block the resource and wait before executing another job until the locks are not released by the processmutually exclusive jobs, i.e. it limits parallel execution of jobs. Resource Locks in a workflow are used to limit job access to resources and to force orders to wait before executing a job. Orders wait until the Resource Lock is released by other jobs holding the Resource Lock. There are two types of locks Resource Locks available in the with JS7:
- Exclusive Resource Lock: only one Lock Instruction can hold the Resource Lock at any given time. Any further Lock Instructions that try to acquire the same Resource Lock have to wait.
- Shared Resource Lock: the Resource Lock is assigned a limit that can be shared by a number of Lock Instructions. Each Lock Instruction carries a weight that counts towards the Resource Lock's limit.
Workflow
In the jdExclusiveLockSerial workflow exclusive lock an Exclusive Resource Lock is used. In the workflow, lock instruction this workflow the Lock Instruction holds the lock, Resource Lock and other jobs with the lock instruction who acquire the same lock trying to acquire this Resource Lock need to wait until the lock Resource Lock is not released.
To execute the workflow in the folder 06_MutualExclusion please follow the steps described below
...
:
- Click
...
- the folder 06_MutualExclusion
...
- and expand the jdExclusiveLockSerial workflow.
- To add
...
- an order
...
- to the workflow
...
- click the action menu of the workflow and
...
- use Add
...
- Order
...
- from the drop-down menu.
...
- When clicking Add Order
...
- a popup window will appear.
...
- You can add
...
- an Order ID or leave the Order
...
- ID value
...
- empty, it will
...
- then use a default Order
...
- ID. Click
...
- the Submit button
...
- .
- If you add a second order to the workflow, you can see that the Resource Locks are acquired and retained by the jobs executing the first order and that any jobs for the second order have to wait until the Resource Locks are released..
- To check the status of the
...
- order click
...
- the
...
- name of the workflow. This will make the Order History panel appear.
- From the Order
...
- History panel
...
- you can
...
- verify if the
...
- order is successful and
...
- hasfinished. Click
...
- the Order ID to
...
- see log output created by jobs executed for this order.
- A log view window will open and the order log will be displayed.
...
- This log contains
...
- output to stdout/stderr from all jobs executed by the order.
...
- You can download the log file by clicking the Download button
...
- in the upper right-hand corner of the log view window. Also, you can expand and collapse
...
- all job output using the
...
- chevron icons in the upper left-hand corner of the log view window.
Overview
Content Tools