This operation provides a mechanism to
launch an existing OneWorld report on to a particular server or to run locally.
SLIK calls a JDE API to submit the
report to the nominated server and then polls the remote server’s report queue
waiting for the completion of the report. If
the report completes with an ‘E’ (error) status then the standard processing
option is to log the error and to stop further processing of jobs in the batch.
This can be overridden using the Jobs Processing options.
By default the system waits up to 60
minutes before considering the report timed-out. However you can specify the
expected wait period at the time you define the OneWorld report operation.
One World operations are created using
the following form:

|
The Report ID field holds the
system generated unique identifier. The
Report ID field automatically populates on creation of the Report
Properties record. The Report
record is created when you click on
OK to save and close the new record. Field value type: system
generated |
|
|
This field defines the server
the report will be run on. To add a new server click on the
|
|
|
This field indicates what report
is to be run from a set of pre-defined reports. If a report name is not
shown in the drop down list you can enter the value directly. |
|
|
This field indicates the version
number associated with the report selected. If a report version is not
shown in the drop down list you can enter the value directly. |
|
|
This field defines how long SLIK
will wait for the report to complete.
If the wait period is exceeded an error will be reported. (This can
be overridden using the Job Processing Options) Note: if no value is entered –
SLIK will default to a one hour period.
|
|
|
The Asynchronous check box is
applicable to on a local UBE and is used to indicate that no return code
is necessary until the report completes. |
|
|
The Adobe Acrobat check box
dictates that the report will be opened in Adobe Acrobat format. |
|
|
DLL
Name – if a OneWorld Sub-system report is
being generated this field is used to specify the custom DLL file to call
to provide any report interconnect details. Entry
Function – The name of the function to
call in the DLL to return an appropriate report interconnect structure for
the sub-system report. |