Setup should provide database script report_procedure.sql but not execute

Current Situation

• The database scripts are located in the path [InstallationPath]/db/[DBMSName]
• For the reporting feature the following scripts are executed in the JobScheduler database by the installer:
  • inventory.sql
  • report.sql
  • report_map_insert.sql
• The following script currently is NOT executed by the installer:
  • report_procedure.sql

Desired Behavior

• The sql script report_procedure.sql is intended as a sample for customizing. It is provided as an example how to to pull data from the JobScheduler Reporting Interface and can be adjusted for individual use.
• The reporting interface is not available for all JobScheduler DBMS. Therefore the installer does not run the report_procedure.sql script.
• The Reporting Interface can (and should) be used with a database that is different from the JobScheduler database. The main reason for this is the recommendation that users should no longer access the JobScheduler database for reporting purposes as this database will move to other DBMS in future JobScheduler releases.
• All reporting sql scripts should be available from the [InstallationPath]/db/[DBMSName]/custom folder for manual installation with a different reporting database.

Workaround

• For manual installation use the DBMS command line client such as

  mysql -D jobscheduler < /opt/js/master.110.1/jsmaster_4444/db/mysql/report_procedure.sql