Capturing CA Deliver Output Management History

Document ID : KB000028198
Last Modified Date : 14/02/2018
Show Technical Document Details

CA Deliver allows you to capture Basic and Detail History records for all reports and bundles.   Do you know whether you are using Detail History or just Basic History?  How does capturing Detail History affect CA Deliver?

How to determine if you are using Detail History

The first thing that determines if you are using Detail History is the RMOPARM HDETAIL. If HDETAIL=YES, Detail History is turned on; however, this does not mean that it is being used. For Detail History of Bundles, you will need the RMOPARM BNDLHDTL=YES.  This parameter requires that you also set BNDLMOUT=YES.  In addition to having the HDETAIL, BNDLHDTL and BNDLMOUT parameters set to YES, there are several user exits that must be installed. These exits are required so that the print information is passed back to CA Deliver from JES when the files are printed. Depending on your needs, you will need one or more of these exits: RMOJ2XIT, RMOFFSUX, RMOJ3X21 and RMOJ3X23.

RMOJ2XIT is required if you are using JES2 and channel-attached impact or channel-attached IBM 3800 printers in compatibility mode.  Use the BRNSJ2X member of the CAI.CVDEJCL library to install RMOJ2XIT as a usermod. The detail instructions for installing this exit are in the CA Deliver Installation Guide.   

RMOFSSUX allows you to capture the print status of jobs printed by PSF to AFP devices for both JES2 and JES3.  This exit is optional and is located in the CAI.CVDEOPTN library.  Sample job BRNJFSSX in the CAI.CVDEJCL library can be used to install RMOFSSUX.

RMOJ3X21 and RMOJ3X23 are used to capture the print status for jobs when using JES3.  Instructions for installing these exits are in the CA Deliver Installation Guide.   

What is the difference between Basic and Detail History?

CA Deliver always captures Basic History when a report or bundle is processed. To browse the history record for each report,  go to the Active Report List (Option A R) or Report Selection List (Option R) and tab next to the Report ID that you wish to view. Place an 'H' next to the Report ID and hit [Enter]. To view a history record for any bundle, go to the Active Bundle List (Option A B), or the Bundle Selection List (Option B), and place an 'H' next to the Bundle ID you wish to view.

The Basic History screen lists the following information about the report or bundle:

Figure 1

This history screen provides the number of lines, pages, date and time that CA Deliver processed the file. You may notice that it does not give the actual date, time, lines and number of pages that were physically printed.

 

To view the Detail History, place an 'S' next to the history record you wish to view. Below is an example of the Detail History for the first report in the above list.

Figure 2

Notice that the Detail History screen displays the actual date and time the file was physically printed. It also shows the number of pages printed, as well as the printer location where the file was printed.

How does capturing Detail History affect CA Deliver?

If the HDETAIL parameter is set to "YES", a history record is generated for each report and bundle that is processed by CA Deliver.  If the exits are not installed, the record will not contain any information, but will still take up space in the database.    

If the Detail History records are not required, it is a good idea to ensure the RMOPARM parameters HDETAIL and BNDLHDTL are set to "NO", so that only the Basic History records are stored in the database.  Storing History Detail records, especially if they do not contain usuable information, can unnecessarily increase the database size and its  utilization percentages.   This is especially important if your MAXHIST parameter is set to retain a high number of generations for each history record, potentially filling your CA Deliver database.