Scribd
Upload
15 views2 pages

DQ Report Generation Logic

The document outlines the process for assigning jobs to a worker queue and executing them, including wait times based on data availability and server status. It details the responsibilities of the cash credit client in unholding jobs and the execution of ReleasePanel jobs in batches. Additionally, it provides suggestions for capturing logs of job execution times and conditions for log generation based on application settings.

Uploaded by

vinoddaggumati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
15 views2 pages

DQ Report Generation Logic

The document outlines the process for assigning jobs to a worker queue and executing them, including wait times based on data availability and server status. It details the responsibilities of the cash credit client in unholding jobs and the execution of ReleasePanel jobs in batches. Additionally, it provides suggestions for capturing logs of job execution times and conditions for log generation based on application settings.

Uploaded by

vinoddaggumati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Worker Queue Assignment

1. After releasing the panel job gets created in DQ. AssignWorkerQueue.srv is


responsible for assigning the jobs to service queue.
2. AssignWorkerQueue srv will run for every 10 seconds, this is configured in the
srv file.
3. Whenever there is no data available, the wait time is set to be 60 seconds,
and after 60 seconds wait time the worker queue starts running.

4. Whenever the main server is set to be inactive, the wait time is set to 900
seconds i.e., 15 mins, after completing 15 mins wait time the worker queue
starts running.

Cash/Credit client check


1. Initially after assigning the jobs, the cash credit client is responsible for
unholding the jobs based on the data available for the job in the credit client
temp table.
2. After the jobs gets unhold, then the report will be executed in the next
procedure.

Release Panel Job Execution


1. After inserting the data into service queue table ReleasePanelWorker.srv is
responsible for executing the jobs which has been assigned by assign worker
queue.
2. Jobs will be executed for ReleasePanel export type and 20jobs per batch, this
will be configured in the srv file.
3. Whenever there is no data available, the wait time is set to be 60 seconds,
and after 60 seconds wait time the worker queue starts running.
4. In between assign worker queue and release panel job, there will be

Suggestion for Capturing the logs


1. By using limsnetconnect function we can capture the start time and end time
of jobs execution for each job, the logs will only be written in the user log file.
2. For capturing the start and end time in the user log folder we can use a
specified keyword where we can filter it based on the keyword and can check
the time taken.
3. Start and end time of job execution can also be inserted into temporary table,
and it can be filtered based on jobid as unique field.
4. Flag will be provided in the application setting for capturing the logs and
inserting the data into a temporary table.
5. If the flag is set to Y logs will be generated and inserted into temporary table,
if it is set to N no logs will be generated.

You might also like