Business Function GetRuntimeInfo

The Business function GetRuntimeInfo (B986110R) allows access from the report ER to information related to the batch job processing environment at runtime. The data available includes:

1. Report Name
2. Version Name
3. User Name (short)
4. EnterpriseOne Environment Name
5. Time stamp when the spec load completed and Execution begins, in UTC (no timezone applied)
6. Job Queue – This value is blank on a Dev Client.
7. Execution Host Name – This is either the Virtual Host name of a VBQ configuration, or the Actual Hostname. It is always “WinClient” on a Dev Client.
8. Actual Host Name – This is the actual Enterprise Server host name.
9. Job Number (as a math numeric) – The current job number. Always 0 on dev clients.
10. Parent Job Number (as a math numeric) – This is the value is 0 if called in top-level UBE, otherwise this is the job number of UBE which called this function. Always 0 on dev clients.
11. Oldest Parent Job Number (as a math numeric) – This is the value is 0 if called in top-level UBE, otherwise this is the job number of topmost UBE of synchronous job chain. Always 0 on dev clients.
12. Job Number (as a string) – The current job number. Always “0” on dev clients.
13. Parent Job Number (as a string) – This is the value is “0” if called in top-level UBE, otherwise this is the job number of UBE which called this function. Always “0” on dev clients.
14. Oldest Parent Job Number (as a string) – This is the value is “0” if called in top-level UBE, otherwise this is the job number of topmost UBE of synchronous job chain. Always “0” on dev clients.
15. Printer Name
16. PDF File Name – This name is assigned only at completion of End Report Event. BI Publisher reports do not have a valid PDF name.
17. CSV File Name – This name is assigned only at completion of End Report Event, and is only valid for reports that have CSV output activated.
18. OSA filename – This name is assigned only at completion of End Report Event, and is only valid for reports that have an OSA output stream activated.

For reports running on a Development Client or Deployment Server, the server name will always be "WinClient". Further, on these machines the job numbers will always be 0. This is because jobs that run locally on these machines are not tracked using a job number in the WSJ (P986110B) application.

The files the filenames refer to are only guaranteed to be available at the End Report event. After this point, this information may be stored in the database and removed from disk according to the setting in the P98617 Output location application.

A typical event to put the ER to call the BSFN would be on the InitSection event of the main driver section of the report passing in section-level or report-level variable to be populated by the function.