Merge pull request EnterpriseDB#1865 from EnterpriseDB/bugfix/epas/DF-262-dbms-job-extension-update

DF-262 DBMS_JOB Extension update

Author: drothery-edb

product_docs/docs/epas/11/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx

@@ -10,7 +10,7 @@ The `DBMS_JOB` package provides for the creation, scheduling, and managing of jo
 
 This package relies on the `pgAgent` scheduler. By default, the Advanced Server installer installs `pgAgent`, but you must start the `pgAgent` service manually prior to using `DBMS_JOB`. If you attempt to use this package to schedule a job after un-installing `pgAgent, DBMS_JOB` will throw an error. `DBMS_JOB` verifies that `pgAgent` is installed, but does not verify that the service is running.
 
-The following table lists the supported `DBMS_JOB` procedures:
+Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. The following table lists the supported `DBMS_JOB` procedures:
 
 | Function/Procedure                                               | Return Type | Description                                                                                                                                                 |
 | ---------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -23,12 +23,11 @@ The following table lists the supported `DBMS_JOB` procedures:
 | `SUBMIT(job OUT, what [, next_date [, interval [, no_parse ]]])` | n/a         | Creates a job and stores its definition in the database.                                                                                                    |
 | `WHAT(job, what)`                                                | n/a         | Change the stored procedure run by a job.                                                                                                                   |
 
-Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table above are supported.
-
-Before using `DBMS_JOB`, a database superuser must create the `pgAgent` extension. Use the `psql` client to connect to a database and invoke the command:
+Before using `DBMS_JOB`, a database superuser must create the `pgAgent` and `DBMS_JOB` extension. Use the `psql` client to connect to a database and invoke the command:
 
 ```text
 CREATE EXTENSION pgagent;
+CREATE EXTENSION dbms_job;
 ```
 
 When and how often a job is run is dependent upon two interacting parameters – `next_date` and `interval`. The `next_date` parameter is a date/time value that specifies the next date/time when the job is to be executed. The `interval` parameter is a string that contains a date function that evaluates to a date/time value.

product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx

@@ -10,7 +10,7 @@ The `DBMS_JOB` package provides for the creation, scheduling, and managing of jo
 
 This package relies on the `pgAgent` scheduler. By default, the Advanced Server installer installs `pgAgent`, but you must start the `pgAgent` service manually prior to using `DBMS_JOB`. If you attempt to use this package to schedule a job after un-installing `pgAgent, DBMS_JOB` will throw an error. `DBMS_JOB` verifies that `pgAgent` is installed, but does not verify that the service is running.
 
-The following table lists the supported `DBMS_JOB` procedures:
+Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. The following table lists the supported `DBMS_JOB` procedures:
 
 | Function/Procedure                                               | Return Type | Description                                                                                                                                                 |
 | ---------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -23,12 +23,11 @@ The following table lists the supported `DBMS_JOB` procedures:
 | `SUBMIT(job OUT, what [, next_date [, interval [, no_parse ]]])` | n/a         | Creates a job and stores its definition in the database.                                                                                                    |
 | `WHAT(job, what)`                                                | n/a         | Change the stored procedure run by a job.                                                                                                                   |
 
-Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table above are supported.
-
-Before using `DBMS_JOB`, a database superuser must create the `pgAgent` extension. Use the `psql` client to connect to a database and invoke the command:
+Before using `DBMS_JOB`, a database superuser must create the `pgAgent` and `DBMS_JOB` extension. Use the `psql` client to connect to a database and invoke the command:
 
 ```text
 CREATE EXTENSION pgagent;
+CREATE EXTENSION dbms_job;
 ```
 
 When and how often a job is run is dependent upon two interacting parameters – `next_date` and `interval`. The `next_date` parameter is a date/time value that specifies the next date/time when the job is to be executed. The `interval` parameter is a string that contains a date function that evaluates to a date/time value.

product_docs/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx

@@ -10,7 +10,7 @@ The `DBMS_JOB` package provides for the creation, scheduling, and managing of jo
 
 This package relies on the `pgAgent` scheduler. By default, the Advanced Server installer installs `pgAgent`, but you must start the `pgAgent` service manually prior to using `DBMS_JOB`. If you attempt to use this package to schedule a job after un-installing `pgAgent, DBMS_JOB` will throw an error. `DBMS_JOB` verifies that `pgAgent` is installed, but does not verify that the service is running.
 
-The following table lists the supported `DBMS_JOB` procedures:
+Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. The following table lists the supported `DBMS_JOB` procedures:
 
 | Function/Procedure                                               | Return Type | Description                                                                                                                                                 |
 | ---------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -23,12 +23,11 @@ The following table lists the supported `DBMS_JOB` procedures:
 | `SUBMIT(job OUT, what [, next_date [, interval [, no_parse ]]])` | n/a         | Creates a job and stores its definition in the database.                                                                                                    |
 | `WHAT(job, what)`                                                | n/a         | Change the stored procedure run by a job.                                                                                                                   |
 
-Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table above are supported.
-
-Before using `DBMS_JOB`, a database superuser must create the `pgAgent` extension. Use the `psql` client to connect to a database and invoke the command:
+Before using `DBMS_JOB`, a database superuser must create the `pgAgent` and `DBMS_JOB` extension. Use the `psql` client to connect to a database and invoke the command:
 
 ```text
 CREATE EXTENSION pgagent;
+CREATE EXTENSION dbms_job;
 ```
 
 When and how often a job is run is dependent upon two interacting parameters – `next_date` and `interval`. The `next_date` parameter is a date/time value that specifies the next date/time when the job is to be executed. The `interval` parameter is a string that contains a date function that evaluates to a date/time value.