ebl Rename JobStat to JobHistory

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index c3b2671067f4c12cf2b496114599945192659cdd..f929f7d8fd17c8cbac4778fc046991f2f47938d8 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -872,11 +872,11 @@ than your statistics period. Ie, if jobs are purged from the catalog, you won't
 be able to use them. 
 
 Now, you can use the \textbf{update stats [days=num]} console command to fill
-the JobStat table with new Job records. If you want to be sure to take in
+the JobHistory table with new Job records. If you want to be sure to take in
 account only \textbf{good jobs}, ie if one of your important job has failed but
 you have fixed the problem and restarted it on time, you probably want to
 delete the first \textit{bad} job record and keep only the successful one. For
-that simply let your staff do the job, and update JobStat table after two or
+that simply let your staff do the job, and update JobHistory table after two or
 three days depending on your organization using the \textbf{[days=num]} option.
 
 These statistics records aren't used for restoring, but mainly for
@@ -887,7 +887,7 @@ can also use tools like Talend or extract information by yourself.
 
 The {\textbf Statistics Retention = \lt{}time\gt{}} director directive defines
 the length of time that Bacula will keep statistics job records in the Catalog
-database after the Job End time. (In \texttt{JobStat} table) When this time
+database after the Job End time. (In \texttt{JobHistory} table) When this time
 period expires, and if user runs \texttt{prune stats} command, Bacula will
 prune (remove) Job records that are older than the specified period.
 

diff --git a/docs/manuals/en/console/bconsole.tex b/docs/manuals/en/console/bconsole.tex
index 7d43c8429bc93f79c2541f81f0e44a47da36a8d7..008d12d8ca0fffb4ca455c3386c041c30da6670c 100644 (file)
--- a/docs/manuals/en/console/bconsole.tex
+++ b/docs/manuals/en/console/bconsole.tex
@@ -1047,9 +1047,8 @@ setdebug level=nn [trace=0/1 client=\lt{}client-name\gt{} | dir | director |
    information about current jobs like average speed or file accounting. The
    full form of this command is:
 
-status [all | dir=\lt{}dir-name\gt{} | director | 
-  client=\lt{}client-name\gt{} | [slots] storage=\lt{}storage-name\gt{} |
-  days=nnn]
+status [all | dir=\lt{}dir-name\gt{} | director [days=nnn] | 
+  client=\lt{}client-name\gt{} | [slots] storage=\lt{}storage-name\gt{}]
 
    If you do a {\bf status dir}, the console will list any currently
    running jobs, a summary of all jobs scheduled to be run in the next 24

diff --git a/docs/manuals/en/install/dirdconf.tex b/docs/manuals/en/install/dirdconf.tex
index 0f9c227c3df4b5799f385660d2c3a25f318da129..b7adfac30b2f6464463a5c28591af28dadc740f6 100644 (file)
--- a/docs/manuals/en/install/dirdconf.tex
+++ b/docs/manuals/en/install/dirdconf.tex
@@ -315,9 +315,9 @@ resource.
 
    The \texttt{Statistics Retention} directive defines the length of time that
    Bacula will keep statistics job records in the Catalog database after the
-   Job End time. (In \texttt{JobStat} table) When this time period expires, and
-   if user runs \texttt{prune stats} command, Bacula will prune (remove) Job
-   records that are older than the specified period.
+   Job End time. (In \texttt{JobHistory} table) When this time period expires,
+   and if user runs \texttt{prune stats} command, Bacula will prune (remove)
+   Job records that are older than the specified period.
 
    Theses statistics records aren't use for restore purpose, but mainly for
    capacity planning, billings, etc. See \ilink{Statistics chapter} for