HDETAIL - PREVRUN
This page describes the initialization parameters from HDETAIL through PREVRUN:
This page describes the initialization parameters from HDETAIL through PREVRUN:
Specifies whether the detailed historical data is maintained for reports and bundles.
- If you specify NO, only basic report data is provided.
- If you specify YES, history detail information are recorded for all reports and bundles (if BNDLHDTL is specified as YES).
To post lines and pages back to CA Deliver by JES, you must install the exits RMOJ2XIT, RMOFSSUX, and/or RMOJ3X21 as appropriate (depending on your environment).
If you specify YES, history detail data can significantly increase the size of your database.
Specifies how the line and page counts in the basic history records are represented.
- HISTCNT=xxx (ALL/ONE) represents the line and page counts as follows:
- ALL - The total of all copies printed.
- ONE - The values for one copy of the report.
Specifies that CA Deliver is to interface with CA Balancing (CA Balancing Report Control).
Include the 4-digit or 4-character (alphanumeric) CA L-Serv Database Manager identifier (xxxx) that identifies the subsystem name of the CA L-Serv that manages the CA Balancing database.
For more information about balancing, see your
Specifies a list of 1 - 38 classes of jobs to which report processing is limited.
This initialization parameter is required.
The job classes for TSO sessions and started tasks are specified as @ and $, respectively.
Assume the following:
- That production jobs run in classes P and Q
- That production jobs are sometimes run using the same job name for test purposes in a class other than P and Q.
To limit processing only to the times the production jobs are run in production, specify the following statement:
JOBCLSL works with the initialization parameter SYSCLSL.
Default:You must enter a value. An asterisk (*) means all classes are defined for the product.
Indicates whether pre-spool and post-spool collection must query the database for an alternate job definition based on the external writer or forms name of the SYSOUT data set.
An initial query is always performed based on the job name of the creating job. If that job name is not found in the database or if a matching step name, procedure step name, and data definition name is not found within the job definition, the alternate job definition can be retrieved and scanned for a matching step name, procedure step name, and data definition name.
- WRITER to use the external writer name of the SYSOUT data set for referencing the alternate job definition
- FORM to use the forms name of the SYSOUT data set for referencing the alternate job definition.
- Blank to indicate that CA Deliver is not to query the database for an alternate job definition.
The initial product logo panel is to display when you enter through an online interface.
The maximum number of generations of a report or a bundle of reports for which historical data is maintained.
The maximum time in minutes to wait for a bundle holding copy on the JES spool queued by JES and available for bundling.
The default value is sufficient in most cases.
The high-level, 1- to 17-byte name of the database.
The database name is associated with the specified or defaulted SYSID. The database name must only be associated with one SYSID.
To prevent any residual effects, association changes must be made only when the system image is being IPLed.
Specifies a list of 1 - 8 classes of SYSOUT data (
cccccccc) to be used to select SYSOUT data sets for processing from the JES spool.
Follow the selection classes with a list of 1 - 8 new SYSOUT classes (
nnnnnnnn), which positionally correspond to the selection classes assigned to the SYSOUT (only if a match for JOBNAME is not found in the database).
You must separate selection classes from new classes with a slash (/). The options NETCLSL, NETDEST, and NETFORM are used together to define a unique set of network input criteria. If you omit all three options, the product does not perform network input processing.
NETCLSL must be unique within a single MVS image. Using network input attributes on multiple systems running the product is described in
The selection destination (
dddddddd) that is used to select reports for processing from the JES spool.
Follow the selection destination with the new destination (
nnnnnnnn) assigned to the reports. You must separate the selection destination from the new destination with a slash (/).
NETDEST must be unique within a single MVS image. Using network input attributes on multiple systems running the product is described in
The forms name (
ffffffff) that is used to select reports for processing from other nodes in the network.
The selection forms name is followed by the new forms name (
nnnnnnnn) assigned to the reports. The selection forms name is separated from the new forms name by a slash (/).
NETFORM must be unique within a single MVS image. Using network input attributes on multiple systems running the product is described in
Specifies whether network input is the only method of operation for the product.
When you specify NETONLY=YES, the real-time operation of the product cannot be used since no dynamic interface is installed; when you specify NETONLY=NO, both the real-time and network input operations of the product can be used.
Indicates which function the network input SAPI collector is to do:
- Requeue a JES SYSOUT data set
- Copy the JES SYSOUT data set to a new SYSOUT data set when the job name, step name, procedure step name, and ddname do not match database definitions
- When you specify NETREQUE=YES, the JES SYSOUT data sets are to be requeued to the new network input class, destination, and forms and retain the original job name, job number, and accounting information.
- When you specify NETREQUE=NO, JES SYSOUT data sets are to be copied to a new SYSOUT data set under the started task name.
- The NETREQUE initialization parameter is ignored if the NETUNDEF initialization parameter is set to YES and an UNDEF report is defined to the CA Deliver database. The NETREQUE initialization parameter is also ignored for cloned SYSOUT data sets that are created from jobs that have /*JOBPARM COPIES= specified.
Notifies the product that you are running CA 11 Workload Automation Restart and Tracking (CA 11) at a different destination.
- To indicate that you are not running CA 11 at a different destination, specify NETRERUN=NO
- To indicate that you are running CA 11 at a remote destination, specify NETRERUN=YES
Indicates whether the network input collectors are to create UNDEF reports for JES SYSOUT data sets that do not match job name, step name, procedure step name, and ddname database definitions.
The UNDEF reports are only created if an UNDEF report is defined to the database.
- If you specify YES, UNDEF reports are created.
- If you specify NO, UNDEF reports are not created.
The password that a user must provide to withdraw CA Deliver from an operating system.
Default:No Password Required
Specifies whether the product processes OUTPUT JCL statements.
You must specify OUTPUT=NO if your release of the operating system does not support the OUTPUT JCL statement.
Specifies whether pre-spool processing must also pass the report through to the report’s normal output specification.
When you specify PASSTHRU=YES, the report is dynamically intercepted and the report is allowed to be written to the normal output allocation. This feature provides a method for parallel testing. During the implementation of CA Deliver, the PASSTHRU=YES allows the reports to be processed normally and processed by CA Deliver. With PASSTHRU=YES, the output is written another time to the output DDNAME incurring additional CPU and I/O.
The default of PASSTHRU=NO causes the report to be dynamically intercepted and the original output DDNAME is not created.
The number (
nn) of external service requests that the product processes concurrently.
Enter a value between 1 and 16 inclusive for
Reports from the most recently run job for the product are to be flagged, deleted, or left unprocessed as follows:
The first value is for reports that have not been archived by CA View. The second value is for reports that have been archived. The second value takes precedence over the first value.
- FLAG is used in the exception code column to indicate that the report has been rerun.
- DELETE is used only when a report is stored in the CA View database or is a bundle holding copy in the JES spool.
- KEEP is used when a report is to be left unprocessed.
Explicitly specify the value for unarchived reports first, then a slash (/), then the value for archived reports, for example:
This initialization parameter works only if you set up the interface between CA 11 and CA Deliver. For more information about setting up this interface, see
Installing and Upgrading.