What is a Concurrent Program ?
An
instance of an execution file, along with parameter definitions and
incompatibilities. Several concurrent programs may use the same
execution file to perform their specific tasks, each having different
parameter defaults and incompatibilities.
What is a Concurrent Program Executable ?
An
executable file that performs a specific task. The file may be a
program written in a standard language, a reporting tool or an operating
system language.
What is a Concurrent Request ?
Request to run a concurrent program as a concurrent process.
What is a Concurrent Process ?
An instance of a running concurrent program that runs simultaneously with other concurrent processes.
What is a Concurrent Manager ?
program
that processes user’s requests and runs concurrent programs. System
Administrators define concurrent managers to run different kinds of
requests.
What is a Concurrent Queue ?
its of concurrent requests awaiting processing by a concurrent manager.
What is a Spawned Concurrent program ?
Concurrent
program that runs in a separate process than that of the concurrent
manager that starts it.PL/SQL stored procedures run in the same process
as the concurrent manager; use them when spawned concurrent programs are
not feasible.
LIFE CYCLE OF CONCURRENT REQUESTS
What are the phases and statuses through which a concurrent prequest runs through?
A concurrent request proceeds through three, possibly four, life cycle stages or phases:
Pending Request is waiting to be run
Running Request is running
Completed Request has finished
Inactive Request cannot be run
Within
each phase, a request's condition or status may change. Below appears a
listing of each phase and the various states that a concurrent request
can go through.
Concurrent Request Phase and Status
Phase Status Description
PENDING Normal Request is waiting for the next available manager.
Standby Program
to run request is incompatible with other program(s) currently running.
Scheduled Request is scheduled to start at a future time or date.
Waiting A
child request is waiting for its Parent request to mark it ready to
run. For example, a report in a report set that runs sequentially must
wait for a prior report to complete.
RUNNING Normal Request is running normally.
Paused Parent
request pauses for all its child requests to complete. For example, a
report set pauses for all reports in the set to complete.
Resuming All
requests submitted by the same parent request have completed running.
The Parent request is waiting to be restarted.
Terminating Running
request is terminated, by selecting Terminate in the Status field of
the Request Details zone.
COMPLETED Normal Request completes normally.
Error Request failed to complete successfully.
Warning Request
completes with warnings. For example, a report is generated
successfully but fails to print.
Cancelled Pending
or Inactive request is cancelled, by selecting Cancel in the Status
field of the Request Details zone.
Terminated Running
request is terminated, by selecting Terminate in the Status field of
the Request Details zone.
INACTIVE Disabled Program
to run request is not enabled. Contact your system administrator.
On
Hold Pending request is placed on hold, by
selecting Hold in the Status field of the Request Details zone.
No
Manager No manager is defined to run the
request. Check with your system administrator.
What is the difference between Request group and request set ?
REQUESTS GROUPS AND REQUEST SETS
Reports and concurrent programs can be assembled into request groups and request sets.
1. A
request group is a collection of reports or concurrent programs. A
System Administrator defines report groups in order to control user
access to reports and concurrent programs. Only a System Administrator
can create a request group.
2. Request
sets define run and print options, and possibly, parameter values, for a
collection of reports or concurrent program. End users and System
Administrators can define request sets. A System Administrator has
request set privileges beyond those of an end user.
Standard Request Submission and Request Groups
Standard
Request Submission is an Oracle Applications feature that allows you to
select and run all your reports and other concurrent programs from a
single, standard form. The standard submission form is called Submit
Requests, although it can be customized to display a different title.
3. The
reports and concurrent programs that may be selected from the Submit
Requests form belong to a request security group, which is a request
group assigned to a responsibility.
4. The
reports and concurrent programs that may be selected from a customized
Submit Requests form belong to a request group that uses a code.
In
summary, request groups can be used to control access to reports and
concurrent programs in two ways; according to a user's responsibility,
or according to a customized standard submission (Run Requests) form.
Standard Request Submission
- Provides standard interface for running and monitoring reports.
- Single form to submit any request, concurrent program. Another form to see report's progress and to review report online.
- Submit Request form: easy-to-use interface.
- Automatic Resubmission.
- Request Sets: define sets of reports, Submit an entire set at same time.
- Request Set options: Run order, printer, no. of copies etc.
- Request Set Log File:Single log file containing the completion status of all reports in set.
- Viewing Requests: Monitor report's progress using View Request form.
- Child Request: or a sub-request submitted by any other concurrent request(Parent Request)
- Parameter: A value you specify when you run a request.
Value Set: A set of values against which AOL validates values, the ned user enters when running a concurrent program.
Controlling Access to Reports:
- Create related group of reports and request sets.
- Define responsibility and assign a report security group to that responsibility.
- A collection of reports/programs that are grouped together. Allow to submit reports or programs in a request set all at once using a single transaction.
- Request set can be defined to submit requests depending on the completion status of previously submitted requests in the set.
- Component of a request set used to group requests within a set. All requests in a stage are executed in parallel. Request set executes one stage at a time., following links from stage to stage.
- Links that are followed depend on the completion status of the individual stages. A stage completes when all the requests contained in the stage have completed.
- PL/SQL functions calculate the completion status of a stage
- Three status of a stage:
- Success
- Warning
- Error
- Provided by AOL, computes the stage completion status from the completion statuses of the specified requests in set.
- Function returns a
- Success: If all requests completed with a status of "Success".
- Warning: If one or more requests in set completed with warning and no request completed with error.
- Error: If any request in set completed with error.
*****************************************************END**********************************
No comments:
Post a Comment