Publishing Reports to the Web - Downloads - Oracle

Debugging Applications that Use the Event-Driven Publishing API
You can use the returned status record for fetching information about the status of
your job.
17.1.5 Using the Servers' Status Record
The status record contains processing information about your job. It contains the same
information found in the server queue (SHOWJOBS). Additionally, it contains
information about the files produced for finished jobs and the lineage for scheduled
jobs.
The most important information in the status record is the current job status and the
status text, used in turn to check for runtime errors and their causes.
You can use timing information to determine if a job is subject to cancellation because
it has exceeded its predicted time for completion.
One way to use the status record is to cancel a job. The Event-Driven Publishing API
offers a method for cancelling a job that has been submitted to the server. This might
be handy if you want to remove a job that has exceeded its allowed time to run or if
you simply have scheduled jobs you want to cancel.
To cancel a job, use the following procedure:
DECLARE
myPlist SRW_PARAMLIST;
myIdent SRW.JOB_IDENT;
myStatus SRW.STATUS_RECORD;
BEGIN
myPlist := SRW_PARAMLIST(SRW_PARAMETER('',''));
SRW.ADD_PARAMETER(myPlist,'GATEWAY','http://…');
SRW.ADD_PARAMETER(myPlist,'SERVER','mySVR');
SRW.ADD_PARAMETER(myPlist,'REPORT','myReport.RDF');
SRW.ADD_PARAMETER(myPlist,'USERID','me/secret');
myIdent := SRW.RUN_REPORT(myPlist);
myStatus := SRW.REPORT_STATUS(myIdent);
if myStatus.StatusCode != srw.RUNNING then
SRW.CANCEL_REPORT(myIdent);
END;
As evident in this example, you cancel a report by calling the CANCEL_REPORT
procedure (SRW.CANCEL_REPORT) and passing it the job_ident record of the job
you want to cancel. The procedure takes an optional parameter list to enable you to
pass any additional parameters you might need.
17.2 Debugging Applications that Use the Event-Driven Publishing API
Because these processes all run behind the scenes, there is no actual place where
debugging information is produced during normal execution. Therefore, the API has
two procedures that toggle a special debugging mode that produces extensive
debugging information via DBMS_OUTPUT:
■ SRW.START_DEBUGGING
■ SRW.STOP_DEBUGGING
To switch on debugging mode simply call SRW.START_DEBUGGING and to stop it call
SRW.STOP_DEBUGGING. The debugging-mode must be started immediately before
you run your actual logic. It stays on as long as the current instance of the package is
loaded.
Using Event-Driven Publishing 17-5